Pop-up retention mechanism for safe charging of smart glasses in a self-assembling charging case and system of use thereof

Abstract

An example foldable charging case for smart glasses includes a foldable component configured to operate in two states: a folded state defining a first internal volume, and an unfolded state defining a second internal volume larger than the first internal volume, the second internal volume being configured to accommodate smart glasses. The foldable charging case also includes an unfolding mechanism configured to contact a nose bridge portion of the smart glasses, and the unfolding mechanism is configured to operate in two states: an unfolded state occurring when the foldable component of the foldable charging case is in the first folded state, and an unfolded state occurring when the foldable component of the foldable charging case is in the second folded state.

Description

[0001] Related applications This application claims priority to U.S. Provisional Patent Application No. 63 / 561,606, filed March 5, 2024, and U.S. Non-Provisional Patent Application No. 19 / 069,622, filed March 4, 2025. Technical Field

[0002] This application generally relates to a foldable charging case configured to accommodate and charge smart glasses (e.g., augmented reality glasses or smart glasses), and the foldable charging case is configured such that it has a total volume when the smart glasses are stored therein, and a further total volume smaller than that total volume when the smart glasses are not stored therein. Background Technology

[0003] Portable electronic devices that typically do not include large batteries (e.g., headphones) generally benefit from carrying a case that includes an additional battery that can be used to charge the portable electronic device when out and about (e.g., away from a power source). However, for larger portable electronic devices, these charging cases may prove too bulky and cumbersome to carry, reducing the likelihood that the end user will take the charging case with them when out and about. Thus, a large, bulky, and difficult-to-carry charging case may prevent users from intermittently charging their portable electronic devices, thereby shortening the device's overall usage time when out and about.

[0004] Therefore, it is necessary to address one or more of the challenges mentioned above. Summary of the Invention

[0005] The foldable charging case described herein addresses one or more of the aforementioned problems, particularly by reducing the overall volume of the foldable charging case when it is not used to store or charge smart glasses. The benefit of this foldable charging case changing its volume when not used to charge or store smart glasses is that it allows for a more convenient form factor for carrying around (e.g., fitting into a pocket or not taking up space in a bag).

[0006] According to a first aspect of this disclosure, a foldable charging case for smart glasses is provided, the foldable charging case including a foldable component configured to operate in at least two states, the at least two states including: a folded state partially defining a first internal volume, and an unfolded state partially defining a second internal volume larger than the first internal volume, the second internal volume being configured to accommodate smart glasses; and the foldable charging case including an unfolding mechanism configured to contact a nose bridge portion of the smart glasses, the unfolding mechanism being configured to operate in at least two states, the at least two states including: an unfolded state occurring when the foldable component of the foldable charging case is in the folded state, and an unfolded state occurring when the foldable component of the foldable charging case is in the unfolded state, wherein the unfolding mechanism is configured to contact the nose bridge portion of the smart glasses in the unfolded state.

[0007] In some embodiments, the foldable charging case for smart glasses may further include another foldable component located on the opposite side of the foldable component relative to the foldable component, wherein the other foldable component may be a mirror image of the foldable component.

[0008] In some embodiments, the foldable charging case for smart glasses may further include another foldable component perpendicular to the foldable component, and the other foldable component may be configured to cause the foldable component to enter the unfolded state when the other foldable component enters the unfolded state.

[0009] In some embodiments, the deployable mechanism may be configured to enter the deployable state in response to the other foldable component entering the unfolded state.

[0010] In some embodiments, the deployable mechanism may include a spring, and the spring may be in a compressed state when the foldable component is in the folded state and in an uncompressed state when the foldable component is in the unfolded state.

[0011] In some embodiments, the deployable mechanism may include a retaining bracket, which may be configured to engage with the nose pad of the smart glasses to hold the smart glasses within the foldable charging case.

[0012] In some embodiments, the deployable mechanism may include a nose bridge interface portion, which may include one or more charging contacts, and the nose bridge may be configured to contact the smart glasses.

[0013] In some embodiments, the deployable mechanism may be partially covered by a cover.

[0014] In some embodiments, the foldable charging case may include a battery and one or more electrical components configured to charge the smart glasses.

[0015] In some embodiments, the folded state may have a rectangular cross-sectional shape, while the unfolded state may have a triangular cross-sectional shape.

[0016] In some embodiments, the smart glasses may be augmented reality glasses.

[0017] In some embodiments, the foldable charging case may include one or more magnets to maintain the shape of the folded state and the undisturbed state.

[0018] According to a second aspect of this disclosure, a system is provided that includes at least (i) a foldable charging case and (ii) smart glasses, wherein the foldable charging case includes a foldable component configured to operate in at least two states, the at least two states including: a folded state partially defining a first internal volume, and an unfolded state partially defining a second internal volume larger than the first internal volume, the second internal volume being configured to accommodate smart glasses; and the foldable charging case includes an unfolding mechanism configured to contact a nose bridge portion of the smart glasses, and the unfolding mechanism is configured to operate in at least two states, the at least two states including: an unfolded state occurring when the foldable component of the foldable charging case is in the folded state, and an unfolded state occurring when the foldable component of the foldable charging case is in the unfolded state, wherein the unfolding mechanism is configured to contact the nose bridge portion of the smart glasses in the unfolded state.

[0019] In some embodiments, the foldable charging case may include another foldable component located on the opposite side of the foldable component relative to the foldable component, wherein the other foldable component may be a mirror image of the foldable component.

[0020] In some embodiments, the foldable charging case may include another foldable component perpendicular to the foldable component, and the other foldable component may be configured to cause the foldable component to enter the unfolded state when the other foldable component enters the unfolded state.

[0021] In some embodiments, the deployable mechanism may include a retaining bracket, which may be configured to engage with the nose pad of the smart glasses to hold the smart glasses within the foldable charging case.

[0022] According to a third aspect of this disclosure, a method for charging smart glasses is provided, the method comprising receiving the smart glasses in a foldable charging case, wherein the foldable charging case includes a foldable component configured to operate in at least two states, the at least two states including: a folded state partially defining a first internal volume, and an unfolded state partially defining a second internal volume larger than the first internal volume, the second internal volume being configured to accommodate the smart glasses; and the foldable charging case includes an unfolding mechanism, the unfolding mechanism... The method includes a method configured to contact the nose bridge portion of smart glasses, and the unfolding mechanism is configured to operate in at least two states, including: an unfolded state when the foldable component of the foldable charging case is in the folded state, and an unfolded state when the foldable component of the foldable charging case is in the unfolded state, wherein the unfolding mechanism is configured to contact the nose bridge portion of the smart glasses in the unfolded state; and the method includes transferring charge from the foldable charging case to the smart glasses in response to receiving the smart glasses at the unfolding mechanism.

[0023] In some embodiments, the foldable component may include another foldable component located on the opposite side of the foldable component in the foldable charging case, wherein the other foldable component may be a mirror image of the foldable component.

[0024] In some embodiments, the foldable component may include another foldable component perpendicular to the foldable component, and the other foldable component may be configured to cause the foldable component to enter the unfolded state when the other foldable component enters the unfolded state.

[0025] In some embodiments, the deployable mechanism may include a retaining bracket, which may be configured to engage with the nose pad of the smart glasses to hold the smart glasses within the foldable charging case.

[0026] It will be understood that any feature described herein that is suitable for incorporation into one or more aspects or embodiments of this disclosure is intended to be generalizable in any and all aspects and embodiments of this disclosure. Other aspects of this disclosure will be understood by those skilled in the art based on the specification, claims, and drawings of this disclosure. The foregoing general description and the following detailed description are exemplary and illustrative only, and not intended to limit the scope of the claims.

[0027] The features and advantages described in the specification are not necessarily all-encompassing; in particular, certain additional features and advantages will be apparent to those skilled in the art from the drawings, specification, and claims. Furthermore, it should be noted that the language used in the specification has been chosen primarily for readability and instruction purposes.

[0028] Having outlined the examples above, a brief description of the accompanying figures will now be given. Attached Figure Description

[0029] To better understand the various embodiments described, reference should be made to the following detailed description in conjunction with the accompanying drawings, in which the same reference numerals refer to corresponding parts throughout the drawings.

[0030] Figure 1A and Figure 1B A foldable charging case for smart glasses according to one or more embodiments of the present disclosure is shown, the foldable charging case including an unfoldable mechanism configured to contact a nose bridge portion of a portion of the smart glasses.

[0031] Figure 2 The present disclosure illustrates that when the foldable charging case is transitioned from an open state to a closed state, and vice versa, the unfolding mechanism transitions from an unfolded state to an open state, according to one or more embodiments of the present disclosure.

[0032] Figure 3 A portion of a foldable charging case according to one or more embodiments of the present disclosure is shown, the portion including an unfoldable mechanism, on-board devices (e.g., a lithium-ion battery), and one or more electrical components for facilitating charging of the smart glasses and the on-board battery.

[0033] Figure 4A , Figure 4B , Figure 4C-1 , Figure 4C-2 , Figure 4D-1 and Figure 4D-2 An example artificial reality system according to one or more embodiments of the present disclosure is shown.

[0034] Figures 5A to 5B An example wrist-worn wearable device 500 according to one or more embodiments of the present disclosure is shown.

[0035] Figure 6A , Figure 6B-1 , Figure 6B-2 and Figure 6C An example head-mounted wearable device according to one or more embodiments of the present disclosure is shown.

[0036] Figures 7A to 7B An example handheld intermediate processing device according to one or more embodiments of the present disclosure is shown.

[0037] Figures 8A to 8C Examples of smart clothing based on textiles according to one or more embodiments of the present disclosure are shown.

[0038] Figure 9 A multidimensional knitting machine is shown, configured to automatically produce multidimensional knitted smart garments based on textiles, according to one or more embodiments of the present disclosure.

[0039] Figure 10 Alternative deployable mechanisms for securing smart glasses to a foldable charging case are shown according to one or more embodiments of the present disclosure.

[0040] Figure 11 The process of a deployable mechanism according to one or more embodiments of the present disclosure switching between a closed state, an open state, and an open state with smart glasses inserted is illustrated.

[0041] Figures 12A to 12C Three types of deployable mechanisms according to one or more embodiments of the present disclosure are shown for controlling the movement of the portion holding the smart glasses.

[0042] Figure 13 This illustration shows how a foldable charging case according to one or more embodiments of the present disclosure utilizes strategically placed magnets to cause the foldable charging case to "automatically" open when partially opened by a user.

[0043] Figure 14 A cross-sectional view of a wing rotating about a bottom portion 1404 according to one or more embodiments of the present disclosure is shown.

[0044] By convention, the various features shown in the accompanying drawings may not be drawn to scale. Therefore, for clarity, the dimensions of the various features may be arbitrarily enlarged or reduced. Furthermore, some of these drawings may not depict all parts of a given system, method, or apparatus. Finally, the same reference numerals may be used to denote the same features throughout the specification and the drawings. Detailed Implementation

[0045] Numerous details are described herein to provide a thorough understanding of the exemplary embodiments illustrated 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 the features and aspects specifically recited in the claims. Furthermore, well-known processes, components, and materials need not be described exhaustively to avoid obscuring relevant aspects of the embodiments described herein.

[0046] Embodiments of this disclosure may include various types of artificial reality systems or various embodiments of artificial reality systems, or combinations thereof. As described herein, artificial reality (AR) is any overlay of functionality and / or sensory-detectable presentation provided by an artificial reality system within a user's physical environment. Such artificial reality may include and / or represent virtual reality (VR), augmented reality, mixed artificial reality (MAR), or some combination and / or variation thereof. For example, a user may perform an air swipe gesture to skip a song via an API provided, for example, at a home speaker. AR environments described herein include, but are not limited to: VR environments (including non-immersive VR environments, semi-immersive VR environments, and fully immersive VR environments); augmented reality environments (including marker-based augmented reality environments, markerless augmented reality environments, location-based augmented reality environments, and projection-based augmented reality environments); mixed reality; and other types of mixed reality environments.

[0047] Artificial reality content can include entirely generated content or generated content combined with acquired (e.g., real-world) content. Artificial reality content can include video, audio, haptic events, or some combination thereof, any one of which can be presented in a single channel or multiple channels (e.g., stereoscopic video that produces a three-dimensional effect for the viewer). Furthermore, in some embodiments, artificial reality can also be associated with applications, products, accessories, services, or some combination thereof for purposes such as creating content in artificial reality and / or otherwise using it in artificial reality (e.g., performing activities in artificial reality).

[0048] As described herein, gestures can 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., single-handed gestures performed by the user's hand detected by one or more sensors of a wearable device (e.g., electromyography (EMG) and / or inertial measurement unit (IMU) of a wrist wearable device) and / or detected via image data acquired through imaging devices of a wearable device (e.g., a camera of a head wearable device) and other gestures that can be detected and determined based on a combination of movements of the user's two hands. 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 communication-coupled device, such as a wrist wearable device); in other words, the gesture is performed in open space in 3D space and does not contact a surface, object, or electronic device. More generally, surface contact gestures (contacts on surfaces, objects, user body parts, or electronic devices) are also conceivable, in which contact (or the intention to contact) is detected at the surface (e.g., a single or two-finger tap on a table, on the user's hand or another finger, on the user's leg, on a sofa, on a steering wheel, etc.). The various 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 (such as proximity sensors, time-of-flight (ToF) sensors, sensors of inertial measurement units, etc.) detected by wearable devices worn by the user and / or other electronic devices owned by the user (e.g., smartphones, laptops, imaging devices, intermediate devices, and / or other devices described herein)).

[0049] This article describes a foldable charging case configured to charge glasses (e.g., smart glasses, extended reality glasses (e.g., AR glasses, VR glasses, MR glasses)). The foldable charging case is designed to have the appearance of a traditional glasses case and provide a familiar user experience for the end user (e.g., placing the glasses in the case when not in use).

[0050] Figure 1A and Figure 1B A foldable charging case for smart glasses is shown according to some embodiments, the foldable charging case including an unfoldable mechanism configured to contact a nose bridge portion of a part of the smart glasses. Figure 1ASequence 100 is shown illustrating how a foldable charging case 102 transitions from its folded state to a folded state, the folded state being configured to house (and charge) smart glasses (which are partially obscured) within its internal space. In a first sequence 104, the foldable charging case 102 is shown in a folded state 106, configured to house and charge the smart glasses. In some embodiments, the folded state is maintained by using magnets to allow the foldable charging case to maintain its shape. In some embodiments, the folded state is maintained by using hook-and-loop fasteners alone or in combination with magnets.

[0051] The second sequence 108 illustrates an intermediate state 110 in which the foldable charging case 102 transitions from an open state 106 to a folded state 112. As shown in intermediate state 110, the foldable charging case 102 is shown to include an unfolding mechanism 114 configured to contact the nose bridge portion of the smart glasses (see reference). Figure 2 (To be discussed in further detail). In some embodiments, the unfoldable mechanism 114 is spring-loaded, such that when the foldable charging case 102 is in the folded state, the unfoldable mechanism 114 is in a position that better contacts the smart glasses, and when the foldable charging case 102 is in the folded state, the unfoldable mechanism 114 is in another flattened position to improve portability during transport (i.e., the smaller volume in the folded state improves comfort and convenience when transported in a pocket or bag). The second sequence 108 also shows at least six movable parts relative to each other, and these movable parts include four rectangular pieces 116A to 116D and two triangular pieces 118A and 118B. In some embodiments, the two triangular pieces 118A and 118B are hinged and automatically flip open to provide structure.

[0052] Figure 1A A third sequence 120 is also shown, in which the foldable charging case 102 is in a folded state 112, in which the smart glasses are not in the foldable charging case 102, and the unfolding mechanism 114 (as shown) Figure 2 (As shown) the foldable charging case 102 is in an unfolded state, which reduces the volume occupied by the unfoldable mechanism 114. In some embodiments, the foldable charging case 102 is maintained in an unfolded state by using a magnet. In some embodiments, the magnet used to hold the foldable charging case 102 in its folded state is the same as the magnet used to hold the foldable charging case 102 in its unfolded state.

[0053] Figure 1BThe sequence of how the foldable charging case 102 transitions from a folded state 126 to an open state 124 is illustrated. In some embodiments, two triangular pieces 118A and 118B are hinged, and these two triangular pieces automatically flip open to provide structure when the foldable charging case 102 is opened by a user. In some embodiments, magnets hold the two triangular pieces in the open state, and once the magnets are disengaged (e.g., by the user initiating the opening of the foldable charging case 102), springs release their compressive energy to cause the foldable charging case 102 to automatically unfold to the open state. Magnets are also positioned such that at least one of the four rectangular pieces 116A to 116D moves to engage with the unfolded triangular pieces (e.g., 116D moves to engage with the unfolded triangular pieces 118A to 118B).

[0054] Figure 2 It is shown that, according to some embodiments, when the foldable charging case transitions from an unfolded state to an unfolded state, and vice versa, the unfolding mechanism transitions from an unfolded state to an unfolded state. Figure 2 The first pane 200 shows the deployable mechanism 202 in its fully deployed state, protruding a predetermined distance 205 (e.g., 5 mm to 15 mm) from the surface 204, such that charging contacts 206A and 206B can contact corresponding charging contacts located on the nose bridge of the smart glasses. As shown in the first pane 200, the deployed state occurs when the foldable charging case 208 is in an open state 210 or an intermediate state 212.

[0055] As shown in the first pane, a cross-sectional view 214 is displayed, illustrating an example system for controlling the movement of the deployable mechanism. As shown, the deployable mechanism includes a hinge member 216, which includes a portion 218 located at its distal end. This portion 218 is configured to secure smart glasses (e.g., by using spring-loaded contacts 220A and 220B (obscured) that slide on a pair of nose pads on the smart glasses) within a foldable charging case 208. This portion 218 is also configured to contact a charging contact subassembly 222 and is configured to slide about the charging subassembly 222 to allow movement between the portion 218 and the charging subassembly 222.

[0056] Sub-assembly 222 includes a charging contact portion 224, which includes charging contacts 220A and 220B configured to provide charge to the smart glasses. The sub-assembly includes two rotatable arms 226A and 226B that rotatably connect the charging contact portion 224 to a fixing member 228 of the foldable charging case 208. The sub-assembly also includes one or more torsion springs 230 that bias the deployable mechanism 202 to its deployed state. While a torsion spring is shown, other types of springs (e.g., coil springs, leaf springs, etc.) are interchangeable. In some embodiments, unconventional biasing systems are conceivable, such as those using materials with certain elastic characteristics, electrical systems, pressure struts, etc.

[0057] The deployable mechanism 202 also includes a rotation limiter 234, which is configured to limit the distance the hinge member can extend from the surface 236.

[0058] The first pane 200 also shows a portion of the deployable mechanism surrounded by a flexible cover 232 (e.g., silicone, fabric, etc.) configured to cover the various parts of the deployable mechanism, which reduces the entry of dust and debris into these parts while also providing an aesthetically pleasing appearance (i.e., covering these parts so that they are not visible to the end user).

[0059] Figure 2 The second pane 238 shows the unfoldable mechanism 202 in a fully unfolded state, and it does not protrude from or only slightly protrudes from surface 204 (e.g., 1 mm to 5 mm), so that the foldable charging case 208 can be folded and its overall volume reduced, as discussed with reference to FIG1. ​​As shown in the second pane, the unfolded state occurs when the foldable charging case 208 is in the folded state 240.

[0060] As shown in the second pane 238, a cross-sectional view 242 is presented, illustrating an example system for controlling the movement of a deployable mechanism in its undeployed state. Cross-sectional view 242 shows two rotatable arms 226A and 226B in a distinct position, substantially parallel to the fixing member 228 of the foldable charging housing 208. In this state, one or more torsion springs 230 are in their compressed state and contain additional spring potential energy for biasing the deployable mechanism 202 to its deployed state.

[0061] The second pane 238 also shows a flexible cover 232 (e.g., silicone, fabric, etc.) that elastically deforms as the deployable mechanism 202 transitions to the undeployed state. In some embodiments, the flexible cover 232 is configured to partially bias the deployable mechanism 202 into the deployed state.

[0062] Figure 3 A portion 300 of a foldable charging case 302 according to some embodiments is shown. The portion 300 includes an unfoldable mechanism 304, an onboard device 306 (e.g., a lithium-ion battery), and one or more electrical components 308 for facilitating charging of the smart glasses and the onboard battery. Figure 3 A portion 310 of the unfoldable mechanism 304 is also shown, configured to hold the smart glasses in place and contact the charging pins 312A and 312B. In some embodiments, one or more electrical components 308 may include computing components, such that the foldable charging case 302 acts as an intermediate processing device for the smart glasses typically housed within the foldable charging case 302. For further details regarding the intermediate processing device, see, for example... Figure 7A and Figure 7B In other words, the foldable charging case 302 acts as an intermediate processing device when the user wears the smart glasses. In some embodiments, this mode is activated in response to detecting that the smart glasses have been removed from the housing and / or when the foldable charging case 302 is in a folded state. In some embodiments, the foldable charging case 302 may include one or more controls for interacting with the extended reality displayed on the smart glasses.

[0063] According to some embodiments, a foldable charging case for smart glasses (e.g., Figures 1A to 3 The foldable charging case shown includes a foldable component. The foldable charging case is configured to operate in at least two states (e.g., the foldable component is hingedly coupled to the charging case and may include a spring (e.g., a torsion spring) to automatically switch between at least two states) (e.g., the four rectangular pieces 116A to 116D and two triangular pieces 118A and 118B shown in FIG. 1). The at least two states include (i) a folded state that partially defines a first internal volume (e.g., the folded state shown in FIG. 1), and (ii) an unfolded state that partially defines a second internal volume larger than the first internal volume, and the second internal volume is configured to accommodate smart glasses (e.g., the unfolded state shown in FIG. 1) (e.g., the second state is configured such that the foldable component is positioned at a right angle (e.g., perpendicular to the other surface) to another surface of the foldable charging case). The foldable charging case also includes an unfoldable mechanism (e.g., unfoldable mechanism 114 shown in FIG. 1) configured to contact the nose bridge portion of the smart glasses. Figure 2 The deployable mechanism 202 shown (for example, the nose bridge portion of the smart glasses includes one or more electrical contacts configured to receive charge from another set of one or more electrical contacts located on the deployable mechanism), and the deployable mechanism is configured to operate in at least two states (e.g., Figure 2The diagram illustrates the operation of the deployable mechanism in two different states: an deployed state and a non-deployed state. These two states are (i) the non-deployed state, which occurs when the foldable component of the foldable charging case is in the first foldable state. Figure 2 The second pane 238 shows the deployable mechanism 202 in its fully unfolded state, and the unfolded state that occurs when the foldable component of the foldable charging case is in a second foldable state, wherein the deployable mechanism is configured to contact the nose bridge portion of the smart glasses in the unfolded state (e.g., Figure 2 The deployable mechanism 202 is shown in its fully deployed state in the first pane 200. The components described above and below are applicable to reference. Figure 10 The foldable charging case and unfoldable mechanism are described in Figure 15.

[0064] In some embodiments, the foldable charging case includes one or more electrical components that act as intermediate processing devices to reduce the computational load on the smart glasses. By offloading operations to the foldable charging case, the smart glasses can operate for longer periods compared to smart glasses without offloading operations.

[0065] In some embodiments, the foldable charging case for smart glasses includes another foldable component located on the opposite side of the foldable charging case relative to the foldable component, wherein the other foldable component is a mirror image of the foldable component (e.g., the other foldable component is hingedly coupled to the charging case and may include a spring (e.g., a torsion spring) to automatically switch between at least two states). For example, Figure 1 shows four rectangular pieces 116A to 116D having similar or identical shapes, and two triangular pieces 118A and 118B having similar or identical shapes.

[0066] In some embodiments, the foldable charging case for smart glasses includes another foldable member perpendicular to the foldable member, and this other foldable member is configured to cause the foldable member to enter an unfolded state when the other foldable member is in an unfolded state. In some embodiments, the surface area of ​​the other foldable member is larger than the surface area of ​​the foldable member. For example, Figure 1 shows four rectangular pieces 116A to 116D and two triangular pieces 118A and 118B. In some embodiments, the foldable charging case for smart glasses has another foldable component with a different shape than the foldable component (e.g., the other foldable component is rectangular, while the foldable component is triangular). For example, Figure 1 shows four rectangular components 116A to 116D and two triangular components 118A and 118B.

[0067] In some embodiments, the deployable mechanism is configured to enter an deployed state in response to another foldable component entering an open state. For example, a magnet on the other foldable component can pull the deployable mechanism into the deployed state.

[0068] In some embodiments, another foldable component has a rectangular shape. For example, Figure 1 shows four rectangular components 116A to 116D.

[0069] In some embodiments, the deployable mechanism includes a spring that is compressed when the foldable component is in a folded state and uncompressed when the foldable component is in an open state. For example, Figure 2 It is shown that when the deployable mechanism 202 is in the deployed state, the torsion spring 320 is in an uncompressed or semi-compressed state, and when the deployable mechanism 202 is in the undeployed state, the torsion spring 320 is in a compressed state.

[0070] In some embodiments, the spring is a torsion spring (e.g., a torsion spring). Figure 2 The torsion spring 320 shown.

[0071] In some embodiments, the spring is a leaf spring.

[0072] In some embodiments, the deployable mechanism includes a retaining bracket configured to engage with the nose pad of the smart glasses to hold the smart glasses within the foldable charging case. For example, Figure 2 A portion 218 located at the distal end of the hinge member is shown, which is configured to secure the smart glasses within the foldable charging case 208.

[0073] In some embodiments, the deployable mechanism includes a nose bridge interface portion that includes one or more charging contacts, and the nose bridge is configured to contact the smart glasses. Figure 2 Spring-loaded contacts 220A and 220B, which are part of the deployable mechanism, are shown. Figure 3 Charging pins 312A and 312B are also shown.

[0074] In some embodiments, the silicone cover partially covers the deployable mechanism. For example, Figure 2 In the first pane 200, a portion of the deployable mechanism is shown to be surrounded by a flexible cover 232 (e.g., silicone, fabric, etc.) configured to cover the various parts of the deployable mechanism.

[0075] In some embodiments, the foldable charging case includes a battery and one or more electrical components configured to charge the smart glasses. For example, Figure 3A portion 300 of a foldable charging case 302 is shown, which includes an unfoldable mechanism 304, onboard devices 306 (e.g., a lithium-ion battery), and one or more electrical components 308.

[0076] In some embodiments, the cross-sectional shape in the folded state is rectangular (e.g., a rounded rectangular shape). Figure 2 The foldable charging case 102 is shown to have a rectangular shape or a rounded rectangular shape when it is in the folded state 106.

[0077] In some embodiments, the cross-sectional shape in the undisturbed state is triangular (e.g., a rounded triangular shape). For example, Figure 2 The foldable charging case 102 is shown to have a triangular shape or a rounded triangular shape when it is in the folded state 106.

[0078] In some embodiments, the smart glasses are augmented reality glasses. For example... Figure 2 The foldable charging case 102 is shown to have a rectangular shape or a rounded rectangular shape when it is in the folded state 112.

[0079] In some embodiments, the foldable charging case includes one or more magnets to maintain its shape in both the folded and undisturbed states.

[0080] According to some embodiments, a system includes at least (i) a foldable charging case and (ii) smart glasses, wherein the foldable charging case is configured according to any embodiment of these embodiments of the present disclosure.

[0081] In some embodiments, smart glasses are augmented reality glasses.

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

[0083] As described herein, a processor (e.g., a central processing unit (CPU) or microcontroller unit (MCU)) is an electronic component responsible for executing instructions and controlling the operation of electronic devices (e.g., a wrist-worn wearable device 500, a head-worn wearable device, a handheld intermediary processing device (HIPD) 700, a textile-based smart garment 800, or other computer systems). Various types of processors exist that are interchangeable or specifically required by the embodiments described herein. For example, the processor can be: (i) a general-purpose processor designed to perform a variety of tasks, such as running software applications, managing operating systems, and performing arithmetic and logical 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., virtual reality animations such as 3D 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; and (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 understand that one or more processors of one or more electronic devices can be used in the various embodiments described herein.

[0084] 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) microcontrollers, which include small, low-power controllers typically used in embedded systems and Internet of Things (IoT) devices; (ii) programmable logic controllers (PLCs), which can be configured for use in industrial automation systems to control and monitor manufacturing processes; (iii) system-on-a-chip (SoC) controllers, which integrate multiple components such as processors, memory, I / O interfaces, and other peripherals onto a single chip; and / or DSPs. As described herein, a graphics module is a component or software module designed to handle graphics operations and / or processes, and may include hardware and / or software modules.

[0085] As described herein, memory refers to electronic components in a computer or electronic device that store data and instructions for access and operation by a processor. 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-rate RAM (DDR RAM), or other random access solid-state memory devices) configured to temporarily store data and instructions; (ii) read-only memory (ROM) configured to permanently store data and instructions (e.g., one or more portions of system firmware, and / or boot loader); (iii) flash memory, disk storage devices, optical disc storage devices, or other non-volatile solid-state storage devices (e.g., universal serial bus (USB) drives, memory cards, and / or solid-state drives (SSDs)) which may be configured to store data in electronic devices; and (iv) cache memory configured to temporarily store frequently accessed data and instructions. As described herein, storage may include structured data (e.g., Structured Query Language (SQL) databases, MongoDB databases, GraphQL data, or JSON data). Other examples of storage may include: (i) data data, including 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 acquired; (iii) media content data, including stored image data, audio data, documents, etc.; (iv) application data, which may include data collected and / or otherwise acquired and stored during use of the application; and / or any other types of data described herein.

[0086] As described herein, the power system of an electronic device is configured to convert input power into a form usable for operating 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 wired and / or wireless connections (which may be part of a peripheral device interface, such as USB, micro-USB, near-field magnetic coupling, magnetic induction and magnetic resonance charging, and / or radio frequency (RF) charging); (iii) a power management integrated circuit configured to distribute power to various components of the device and ensure that the device operates within safety limits (e.g., regulating voltage, controlling current, and / or managing heat dissipation); and / or (iv) a battery configured to store power to provide usable power to components of one or more electronic devices.

[0087] 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 peripheral devices and can provide 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 configured to connect a device to an electronic device; (ii) a Bluetooth interface configured to allow devices to communicate with each other, including Bluetooth Low Energy (BLE); (iii) a near field communication (NFC) interface configured as a short-range wireless interface for operations such as access control; (iv) POGO pins, which may be small spring-loaded pins configured to provide a charging interface; (v) a wireless charging interface; (vi) a global positioning system (GPS) interface; (vii) a Wi-Fi interface for providing connectivity between a device and a wireless network; and (viii) a sensor interface.

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

[0089] As described herein, applications (e.g., software) stored in the memory of an electronic device include 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 applications that may be stored in memory. Applications may operate in conjunction with one or more components of a data and / or device or communication-coupled device to perform one or more operations and / or functions.

[0090] As described herein, a communication interface module may include hardware and / or software capable of data communication 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 those not yet 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 hardware and software. For example, a communication interface may refer to a physical connector and / or port on a device that enables communication with other devices (e.g., USB, Ethernet, HDMI, 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), such as protocols like HTTP and TCP / IP).

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

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

[0093] Example AR System Figure 4A , Figure 4B , Figure 4C-1 , Figure 4C-2 , Figure 4D-1 and Figure 4D-2 An example artificial reality system according to some embodiments is shown. Figure 4A The first AR system 400a and a first example user interaction using a wrist wearable device 500, a head wearable device (e.g., AR device 600) and / or a handheld middle processing device (HIPD) 700 are shown. Figure 4B The second AR system 400b and a second example user interaction using a wrist wearable device 500, an AR device 600 and / or a HIPD 700 are shown. Figure 4C-1 and Figure 4C-2 The third AR system 400c and a third example 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. Figure 4D-1 and Figure 4D-2 A fourth AR system 400d and a fourth example user interaction using a wrist-worn wearable device 500, a virtual reality (VR) device 610, and / or a textile-based smart garment 800 (e.g., a wearable glove, a haptic glove) are illustrated. As those skilled in the art will understand upon reading the description provided herein, the above-described example AR system (described in detail below) can perform various functions and / or operations.

[0094] The following text is for reference only. Figures 5A to 5B The wrist-worn wearable device 500 and its components are described below; see references below. Figure 6A Figure 6D describes the head-mounted wearable device and its components; and references below. Figures 7A to 7B The HIPD 700 and its components are described. See below for reference. Figures 8A to 8CA textile-based smart garment 800 and one or more of its components are described. A wrist-worn wearable device 500, a head-worn wearable device, and / or a HIPD 700 can be communicatively coupled via a network 425 (e.g., cellular, near-field, Wi-Fi, personal area network, wireless LAN, etc.). Furthermore, the wrist-worn wearable device 500, the head-worn wearable device, and / or the HIPD 700 can also be communicatively coupled via the network 425 to one or more servers 430, computers 440 (e.g., laptops, computers, etc.), mobile devices 450 (e.g., smartphones, tablets, etc.), and / or other electronic devices. Similarly, the textile-based smart garment 800, when in use, can also be communicatively coupled via the network 425 to the wrist-worn wearable device 500, the head-worn wearable device, the HIPD 700, one or more servers 430, computers 440, mobile devices 450, and / or other electronic devices.

[0095] Go to Figure 4A The illustration shows a user 402 wearing a wrist-worn wearable device 500 and an AR device 600, with a HIPD 700 placed on their table. The wrist-worn wearable device 500, AR device 600, and HIPD 700 facilitate user interaction with the AR environment. Specifically, as shown in the first AR system 400a, the wrist-worn wearable device 500, AR device 600, and / or HIPD 700 enable the presentation of one or more avatars 404, digital representations of contacts 406, and virtual objects 408. As described below, the user 402 can interact with one or more avatars 404, digital representations of contacts 406, and virtual objects 408 via the wrist-worn wearable device 500, AR device 600, and / or HIPD 700.

[0096] User 402 may use any of the following to provide user input: wrist wearable device 500, AR 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 reference below) Figures 5A to 5B One or more EMG sensors and / or IMUs and / or AR devices 600 (e.g., using the references below) are described. Figure 6A(To one or more image sensors or cameras depicted in Figure 6B). Alternatively or additionally, user 402 may provide user input via one or more touch surfaces of the wrist wearable device 500, AR device 600, and / or HIPD 700, and / or voice commands collected by the microphones of the wrist wearable device 500, AR device 600, and / or HIPD 700. In some embodiments, the wrist wearable device 500, AR device 600, and / or HIPD 700 includes a digital assistant to assist the user in providing user input (e.g., completing a sequence of actions, suggesting different actions or commands, providing reminders, confirming commands, etc.). In some embodiments, user 402 may provide user input via one or more facial gestures and / or facial expressions. For example, the cameras of the wrist wearable device 500, AR device 600, and / or HIPD 700 may track the user 402's eyes to navigate the user interface.

[0097] The wrist-worn wearable device 500, AR device 600, and / or HIPD 700 can operate individually or in combination to allow user 402 to interact with the AR environment. In some embodiments, HIPD 700 is configured to operate as a central hub or control center for the wrist-worn wearable device 500, AR device 600, and / or another communication-coupled device. For example, user 402 can provide input to interact with the AR environment at any of the wrist-worn wearable device 500, AR device 600, and / or HIPD 700, and HIPD 700 can identify one or more backend and frontend tasks to perform the requested interaction and distribute instructions to cause one or more backend and frontend tasks to be performed at the wrist-worn wearable device 500, AR device 600, and / or HIPD 700. In some embodiments, backend tasks are user-insensible background processing tasks (e.g., rendering content, decompressing, compressing, etc.), while frontend tasks are user-insensible user-facing tasks (e.g., presenting information to the user, providing feedback to the user, etc.). See below for further details. Figures 7A to 7B As described, the HIPD 700 can perform backend tasks and provide runtime data corresponding to the performed backend tasks to the wrist-worn wearable device 500 and / or AR device 600, enabling the wrist-worn wearable device 500 and / or AR device 600 to perform frontend tasks. Thus, compared to the wrist-worn wearable device 500 and / or AR device 600, the HIPD 700, with its greater computing resources and thermal headroom, performs computationally intensive tasks and reduces the computer resource utilization and / or power consumption of the wrist-worn wearable device 500 and / or AR device 600.

[0098] In the example shown in the first AR system 400a, HIPD 700 identifies one or more backend and frontend tasks associated with a user request to initiate an AR video call with one or more other users (represented by avatar 404 and contact digital representation 406), and distributes instructions to cause one or more backend and frontend tasks to be executed. Specifically, HIPD 700 performs backend tasks for processing and / or rendering image data (and other data) associated with the AR video call, and provides the AR device 600 with runtime data associated with the performed backend tasks, causing the AR device 600 to perform frontend tasks for presenting the AR video call (e.g., presenting avatar 404 and contact digital representation 406).

[0099] In some embodiments, the HIPD 700 can operate as a focus or anchor point for presenting information. This allows the user 402 to generally know where the information is presented. For example, as shown in the first AR system 400a, an avatar 404 and a digital representation 406 of a contact are presented above the HIPD 700. Specifically, the HIPD 700 and AR 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 AR system 400a, a virtual object 408 is presented on a table at a distance from the HIPD 700. Similar to the examples above, the HIPD 700 and AR device 600 can operate in conjunction 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, avatar 404, contact digital representation 406, and virtual object 408 do not need to be displayed within the predetermined distance of HIPD 700.

[0100] The user input provided at the wrist wearable device 500, AR device 600, and / or HIPD 700 is coordinated so that the user can use any device to initiate, continue, and / or complete an operation. For example, user 402 can provide user input to AR device 600 to cause AR device 600 to render virtual object 408, and when virtual object 408 is rendered by AR device 600, user 402 can provide one or more gestures via wrist wearable device 500 to interact with and / or manipulate virtual object 408.

[0101] Figure 4BThe illustration shows user 402 wearing wrist-worn wearable device 500 and AR device 600 while holding HIPD 700. In the second AR system 400b, wrist-worn wearable device 500, AR device 600, and / or HIPD 700 are used to receive one or more messages and / or provide one or more messages to user 402's contacts. Specifically, wrist-worn wearable device 500, AR device 600, and / or HIPD 700 detect and coordinate one or more user inputs to initiate a messaging application and prepare a response to messages received via the messaging application.

[0102] In some embodiments, user 402 launches an application on a wrist-worn wearable device 500, an AR device 600, and / or a HIPD 700 via user input, which causes the application to launch on at least one device. For example, in a second AR system 400b, user 402 executes a gesture associated with a command (represented by a messaging user interface 412) for launching a messaging application; the wrist-worn wearable device 500 detects the gesture; and based on determining that user 402 is wearing the AR device 600, causes the AR device 600 to present the messaging user interface 412 of the messaging application. The AR device 600 may present the messaging user interface 412 to user 402 via its display (e.g., as shown in user 402's field of view 410). In some embodiments, the application is launched and runs on a device (e.g., the wrist-worn wearable device 500, the AR device 600, and / or the HIPD 700) that detects user input to launch the application, and that device provides runtime data to another device to present the messaging application. For example, the wrist-worn wearable device 500 can detect user input to launch a messaging application, launch and run the messaging application, and provide operational data to the AR device 600 and / or HIPD 700 to enable the presentation of the messaging application. Alternatively, the application can be launched and run on a device other than the one that detects the user input. For example, the wrist-worn wearable device 500 can detect gestures associated with launching the messaging application and enable the HIPD 700 to run the messaging application and coordinate its presentation.

[0103] Furthermore, user 402 can provide user input at the wrist wearable device 500, AR 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 the wrist wearable device 500, and when the AR device 600 presents the messaging user interface 412, user 402 can provide input at HIPD 700 to prepare a reply (e.g., indicated by a swipe gesture performed on HIPD 700). The gesture performed by user 402 on HIPD 700 can be provided and / or displayed on another device. For example, a swipe gesture performed by user 402 on HIPD 700 is displayed on the virtual keyboard of the messaging user interface 412 displayed by AR device 600.

[0104] In some embodiments, the wrist wearable device 500, AR device 600, 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, incoming call, application update, status update, etc. The user 402 may select the notification via the wrist wearable device 500, AR device 600, or HIPD 700, causing the application or action associated with the notification to be presented on at least one device. For example, the user 402 may receive a notification that a message has been received at the wrist wearable device 500, AR device 600, HIPD 700, and / or other communication coupling devices, and provide user input at the wrist wearable device 500, AR device 600, and / or HIPD 700 to view the notification. 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, AR device 600, and / or HIPD 700.

[0105] While the examples above describe coordinated input for interaction with messaging applications, those 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, AR 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-worn wearable device 500 to activate the camera of AR device 600, and the user can use wrist-worn wearable device 500, AR device 600, and / or HIPD 700 to manipulate (e.g., zoom in or out, apply filters, etc.) image capture and acquire image data.

[0106] Go to Figure 4C-1 and Figure 4C-2The image shows a user 402 wearing a wrist-worn wearable device 500 and a VR device 610, and holding a HIPD 700. In the third AR system 400c, the wrist-worn wearable device 500, the VR device 610, and / or the HIPD 700 are used for interaction within an AR environment (e.g., a VR game or other AR application). When the VR device 610 presents a representation of a VR game (e.g., a first AR game environment 420) to the user 402, the wrist-worn wearable device 500, the VR 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.

[0107] In some embodiments, user 402 may provide user input via wrist-worn wearable device 500, VR device 610, and / or HIPD 700, which causes action to occur in the corresponding AR environment. For example, a third AR system 400c (such as...) Figure 4C-1 In the example shown, user 402 raises HIPD 700 in preparation for swinging it in the first AR game environment 420. VR device 610 responds to user 402 raising HIPD 700 by causing the AR representation of user 422 to perform a similar action (e.g., raising a virtual object such as a virtual sword 424). In some embodiments, each device uses its own sensor data and / or image data to detect user input and provide an accurate representation of user 402's movement. For example, the image sensor of HIPD 700, such as IMU 758 (e.g., hereinafter referred to as...). Figure 7A and Figure 7B Simultaneous Localization and Mapping (SLAM) (using a camera or other cameras) discussed in the text can be used to detect the position of HIPD 700 relative to the user 402's body, so that virtual objects can be properly positioned within the first AR game environment 420; sensor data from the wrist wearable device 500 can be used to detect the speed at which the user 402 raises HIPD 700, so that the AR representation of the user 422 and the virtual sword 424 is synchronized with the user 402's movement; and the imaging sensor 626 of the VR device 610 ( Figures 6A to 6C () can be used to represent the body, boundary conditions, or real-world objects of the user 402 within the first AR game environment 420.

[0108] exist Figure 4C-2In this scenario, user 402 swings downwards while holding HIPD 700. Wrist wearable device 500, VR device 610, and / or HIPD 700 detect the downward swing and execute a corresponding action within the first AR game environment 420. In some embodiments, data collected by each device is used to improve the user experience within the AR environment. For example, sensor data from wrist wearable device 500 can be used to determine the speed and / or force of the downward swing, and image sensors from HIPD 700 and / or VR device 610 can be used to determine the location of the swing and how it should be represented in the first AR game environment 420, which can then be used as input to the AR environment (e.g., a game mechanic) that can use the detected speed, force, location, and / or aspects of user 402's action to classify the user's input (e.g., a light strike, a heavy strike, a critical strike, a blitzkrieg, a miss, etc.) or calculate an output (e.g., damage amount).

[0109] Although the wrist-worn wearable device 500, VR device 610, and / or HIPD 700 are described as detecting user input, in some embodiments, user input is detected at a single device (wherein the single device is responsible for distributing signals to other devices to execute the user input). For example, HIPD 700 can be used to generate an application running a first AR game environment 420 and to provide the VR device 610 with corresponding data for causing the presentation of the first AR game environment 420, and to detect movement of 402 (when the user holds HIPD 700) to cause corresponding actions to be performed within the first AR game environment 420. Additionally or alternatively, in some embodiments, operational data from one or more devices (e.g., sensor data, image data, application data, device data, and / or other data) is provided to a single device (e.g., HIPD 700) to process the operational data and cause the corresponding device to perform actions associated with the processed operational data.

[0110] exist Figure 4D-1 and Figure 4D-2 The image shows a user 402 wearing a wrist-worn wearable device 500, a VR device 610, and a textile-based smart garment 800. In the fourth AR system 400d, the wrist-worn wearable device 500, the VR device 610, and / or the textile-based smart garment 800 are used in an AR environment (e.g., as described above). Figures 4A to 4C-2 Interaction can occur within any AR system described. When VR device 610 presents a representation of a VR game (e.g., a second AR game environment 435) to user 402, wrist wearable device 500, VR device 610, and / or textile-based smart clothing 800 detect and coordinate one or more user inputs to allow user 402 to interact with the AR environment.

[0111] In some embodiments, user 402 may provide user input via a wrist-worn wearable device 500, a VR device 610, and / or a textile-based smart garment 800, which causes action to occur in the corresponding AR environment. For example, user 402 in a fourth AR system 400d (such as...) Figure 4D-1 (As shown) The user 402 raises their hand, wearing a textile-based smart garment 800, in preparation for casting a spell or throwing an object within a second AR game environment 435. In response to the user 402 raising their hand (wearing the textile-based smart garment 800), the VR device 610 causes the user 422's AR representation to perform a similar action (e.g., grasping a virtual object, such as throwing a fireball 434). In some embodiments, each device uses its own sensor data and / or image data to detect user input and provide an accurate representation of the user 402's movements.

[0112] exist Figure 4D-2 In this scenario, user 402 performs a throwing motion while wearing a textile-based smart garment 800. The wrist-worn wearable device 500, VR device 610, and / or the textile-based smart garment 800 detect the user 402's throwing motion and execute corresponding actions within a second AR game environment 435. As described above, data collected by each device is used to improve the user experience within the AR environment. Although not shown, the textile-based smart garment 800 can be used in conjunction with VR device 610 and / or HIPD 700.

[0113] The example AR systems, devices for interacting with such AR systems, and other computing systems have already been discussed more generally, and will now be discussed in more detail below. For ease of reference, this document defines some of the devices and components that may be included in some or all of the example devices discussed below. It will be understood by those skilled in the art 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 as included in the provided definitions.

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

[0115] 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 containing electronic components such as transistors, resistors, capacitors, diodes, and integrated circuits. Examples of electronic devices include smartphones, laptops, digital cameras, televisions, game consoles, and music players, as well as the example electronic devices discussed herein. As described herein, an intermediate electronic device is a device situated between subsets of components of two other electronic devices and / or one or more electronic devices, facilitating communication and / or data processing and / or data transmission between the respective electronic devices and / or electronic components.

[0116] Example wrist wearable devices Figure 5A and Figure 5B An example wrist-worn wearable device 500 according to some embodiments is shown. Figure 5A Multiple components of a wrist-worn wearable device 500 are shown. These components can be used individually or in combination, and include combinations containing other electronic devices and / or electronic components.

[0117] Figure 5A A wearable band 510 and a watch body 520 (or a pouch) are shown coupled (as discussed below) to form a wrist wearable device 500. The wrist wearable device 500 can perform various functions and / or operations associated with browsing and selectively opening applications through a user interface.

[0118] As will be described in more detail below, the operations performed by the wrist-worn wearable device 500 may include: (i) presenting content to the user (e.g., displaying visual content via display 505); (ii) detecting (e.g., sensing) user input (e.g., sensing touches on peripheral buttons 523 and / or touches on the touchscreen of display 505, gestures detected by sensors (e.g., biopotential sensors); (iii) sensing biometric data (e.g., neuromuscular signals, heart rate, temperature, sleep, etc.) via one or more sensors 513; sending and receiving messages (e.g., text, voice, video, etc.); image acquisition via one or more imaging devices or cameras 525; wireless communication (e.g., cellular, near-field, Wi-Fi, personal area network, etc.); location determination; financial transactions; providing haptic feedback; alarms; notifications; biometric authentication; health monitoring; and sleep monitoring.

[0119] The example functions described above can 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, the functions can be performed on the wrist wearable device 500 when an AR environment is presented (e.g., via one of the AR systems 400a to 400d). As those skilled in the art will understand upon reading the description provided herein, the novel wearable device described herein can be used with other types of AR environments.

[0120] The wearable band 510 can be configured to be worn by a user such that the inner (or inner) 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, body temperature, sweat level, neuromuscular signals, or combinations thereof. The sensor 513 can also sense data about the user's environment, including the user's motion, height, position, orientation, gait, acceleration, localization, or combinations thereof. In some embodiments, the sensor 513 is configured to track the localization and / or motion of the wearable band 510. One or more sensors 513 may include those defined above and / or those described below. Figure 5B Any sensors discussed.

[0121] One or more sensors 513 may be distributed on the inner and / or outer surface of the wearable band 510. In some embodiments, the one or more sensors 513 are evenly spaced along the wearable band 510. Alternatively, in some embodiments, the 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 defined as sheet-like (e.g., sensor 513a), elliptical, circular, square, 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 sensor pairs (e.g., for sensing neuromuscular signals based on differential sensing within each respective 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 sensor pairs. Alternatively, in some embodiments, the wearable band 510 has a predetermined number of sensor pairs (one pair, three pairs, four pairs, six pairs, sixteen pairs, etc.).

[0122] The wearable band 510 may include any suitable number of sensors 513. In some embodiments, the number and arrangement of the sensors 513 depend on the specific application using the wearable band 510. For example, a wearable band 510 configured as an armband, wristband, or chest band may include a plurality of sensors 513, which may have a different number of sensors 513 and a different arrangement for each use case (e.g., a medical use case compared to gaming or general everyday use cases).

[0123] According to some embodiments, the wearable band 510 also includes an electrically grounding electrode and a shielding electrode. Similar to the sensor 513, the electrically grounding electrode and the shielding electrode may be distributed on the inner surface of the wearable band 510 such that they contact a portion of the user's skin. For example, the electrically grounding electrode and the shielding electrode may be located on the inner surface of the coupling mechanism 516 or the inner surface of the wearable structure 511. The electrically grounding electrode and the shielding electrode may be formed as in the sensor 513, and / or use the same components as the sensor 513. In some embodiments, the wearable band 510 includes more than one electrically grounding electrode and more than one shielding electrode.

[0124] Sensor 513 may be formed as part of the wearable structure 511 of the wearable band 510. In some embodiments, sensor 513 is flush or substantially flush with the wearable structure 511 such that it does not extend beyond the surface of the wearable structure 511. Even when sensor 513 is flush with the wearable structure 511, sensor 513 is still configured to contact the user's skin (e.g., via a skin-contact surface). Alternatively, in some embodiments, sensor 513 extends beyond the wearable structure 511 by a predetermined distance (e.g., 0.1 mm to 2 mm) to contact and press against the user's skin. In some embodiments, sensor 513 is coupled to an actuator (not shown) configured to adjust the extension height of sensor 513 (e.g., distance from the surface of the wearable structure 511) such that sensor 513 contacts and presses against the user's skin. In some embodiments, the actuator adjusts the extension height between 0.01 mm and 1.2 mm. This allows users to customize the position of sensor 513 to improve 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.

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

[0126] Wearable structure 511 may include flexible electronic connectors that will enclose sensors 513, electronic circuitry, and / or (hereinafter referred to as...) within wearable band 510. Figure 5B Other electronic components (as described) are interconnected. In some embodiments, the flexible electronic connector is configured to interconnect the sensor 513, electronic circuitry, and / or other electronic components of the wearable band 510 with corresponding sensors and / or other electronic components of another electronic device (e.g., the watch body 520). The flexible electronic connector is configured to move with the wearable structure 511 such that adjustments made by the user to the wearable structure 511 (e.g., resizing, pulling, folding, etc.) do not stress or strain the electrical coupling of the components of the wearable band 510.

[0127] As described above, the wearable band 510 is configured to be worn by a user. Specifically, the wearable band 510 can be shaped or otherwise manipulated for wear by a user. For example, the wearable band 510 can be shaped to have a substantially circular shape, such 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, hook-and-loop fastener, etc.) for securing 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 (referred to as sensor data) from the user's skin. Specifically, the sensor 513 of the wearable band 510 acquires (e.g., senses and records) neuromuscular signals.

[0128] The sensed data (e.g., sensed neuromuscular signals) can be used to detect and / or determine a user's intention to perform certain motor actions. Specifically, sensor 513 senses and records neuromuscular signals from the user when the user performs muscle activation (e.g., movement, gestures, etc.). The detected and / or determined motor actions (e.g., phalanges (or fingers) movement, wrist movement, hand movement, and / or other muscle intentions) can be used to determine control commands or control information (instructions to execute 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-worn wearable device 500, and / or can be transmitted to a device responsible for rendering an artificial reality environment (e.g., a head-mounted display) to perform actions within the associated artificial reality environment, such as controlling the movement of virtual devices displayed to the user. User-performed muscle activation can include: static gestures, such as placing a user's palm down on a table; dynamic gestures, such as grasping a physical or virtual object; and covert gestures imperceptible to another person, such as slightly tightening a joint by co-contracting opposing muscles or using submuscular activation. User-performed muscle activation can also include symbolic gestures (e.g., gestures mapped to other gestures, interactions, or commands based on a gesture vocabulary that maps specified gestures to commands).

[0129] Sensor data sensed by sensor 513 can be used to provide users with enhanced interaction with physical objects (e.g., devices communicatively coupled to wearable band 510) and / or virtual objects in artificial reality applications generated by artificial reality systems (e.g., user interface objects presented on display 505 or another computing device (e.g., smartphone)).

[0130] In some embodiments, the wearable band 510 includes one or more tactile devices 546. Figure 5B For example, a vibratory haptic actuator), one or more haptic devices are configured to provide haptic feedback to a user's skin (e.g., skin and / or kinesthetic sensations). Sensor 513 and / or haptic device 546 may be configured to operate in conjunction with multiple applications (including but not limited to health monitoring, social media, games, and artificial reality (e.g., applications associated with artificial reality)).

[0131] The wearable band 510 may also include a coupling mechanism 516 for detachably coupling a capsule (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., the bracket or shape of the coupling mechanism may correspond to the shape of the watch body 520 of the wrist wearable device 500). Specifically, the coupling mechanism 516 may be configured to receive a coupling surface of the watch body 520 near its bottom side (e.g., the side of the watch body 520 opposite the front side where the display 505 is located), allowing a user to push the watch body 520 downwards 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., the side near the front side where the display 505 is located), which is pushed upwards into a bracket rather than downwards into the coupling mechanism 516. In some embodiments, the coupling mechanism 516 is an integrated component of the wearable strap 510, such that the wearable strap 510 and the coupling mechanism 516 are a single integral structure. In some embodiments, the coupling mechanism 516 is a type of frame or shell, which allows the coupling surface of the watch body 520 to remain inside or on the coupling mechanism 516 of the wearable strap 510 (e.g., a bracket, tracker strap, support base, buckle, etc.).

[0132] The coupling mechanism 516 allows the watch body 520 to be detachably coupled to the wearable strap 510 via friction engagement, magnetic coupling, rotation-based connectors, shear pin couplings, retaining springs, one or more magnets, clips, pins, hook-and-loop fasteners, or combinations thereof. A user can perform any type of movement to couple the watch body 520 to and detach it from the wearable strap 510. For example, a user can twist, slide, rotate, push, pull, or rotate the watch body 520 relative to the wearable strap 510, or combinations thereof, to attach the watch body 520 to and detach it from the wearable strap 510. Alternatively, as discussed below, in some embodiments, the watch body 520 can be detached from the wearable strap 510 via an actuated release mechanism 529.

[0133] 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, adding additional sensors to improve sensed data, etc.). As described above, the wearable band 510 (and coupling mechanism 516) is configured to operate independently of the watch body 520 (e.g., to 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.

[0134] Users can detach the watch body 520 (or the pouch) from the wearable strap 510 to reduce the burden of the wrist wearable device 500 on the user. In embodiments where the watch body 520 is detachable, the watch body 520 may be referred to as a detachable structure, such that in these embodiments, the wrist wearable device 500 includes a wearable portion (e.g., the wearable strap 510) and a detachable structure (the watch body 520).

[0135] Turning to the watch body 520, the watch body 520 may have a substantially 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 size of the watch body 520 is configured for easy carrying by the user, attachment to a part of the user's clothing, and / or coupling to a wearable strap 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 strap 510. In some embodiments, the watch body 520 includes a single release mechanism 529 or multiple release mechanisms (e.g., two release mechanisms 529 located on opposite sides of the watch body 520, such as spring-loaded buttons) for separating the watch body 520 and the wearable strap 510. The release mechanism 529 may include, but is not limited to, buttons, knobs, plungers, handles, levers, fasteners, buckles, dials, latches, or combinations thereof.

[0136] A user can actuate the release mechanism 529 by pushing, rotating, lifting, pressing, shifting, or performing other actions on the release mechanism 529. Actuating the release mechanism 529 can release (e.g., detach) 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, detaching the watch body 520 from the wearable band 510 allows the user to use the rear camera 525B to capture images. Although the coupling mechanism 516 is shown as being located at a corner of the watch body 520, the release mechanism 529 can be located anywhere on the watch body 520 that is convenient for the user to actuate. Furthermore, in some embodiments, the wearable band 510 may also include a corresponding release mechanism for detaching 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 detached from the coupling mechanism 516 as described above (e.g., by twisting, rotating, etc.).

[0137] 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, peripheral buttons 523 and 527 may be used to turn on or wake up the display 505 (e.g., switch from sleep to 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, etc. Additionally or alternatively, in some embodiments, the display 505 functions as a touchscreen and allows the user to provide one or more inputs for interacting with the watch body 520.

[0138] 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 strap 510. The sensors 521 of the watch body 520 may be distributed on the inner and / or outer surfaces 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 sensors 521 may be placed on the underside of the watch body 520, and the coupling mechanism 516 may be a bracket with an opening that allows the underside of the watch body 520 to directly contact the user's skin. Alternatively, in some embodiments, the watch body 520 does not include sensors configured to contact the user's skin (e.g., sensors located inside and / or outside the watch body 520 configured to sense data about the watch body 520 and its surrounding environment). In some embodiments, the sensors 513 are configured to track the position and / or movement of the watch body 520.

[0139] The watch body 520 and the wearable band 510 can share data using wired communication methods (e.g., Universal Asynchronous Receiver / Transmitter (UART), USB transceiver, etc.) and / or wireless communication methods (e.g., Near Field Communication, Bluetooth, etc.). For example, the watch body 520 and the wearable band 510 can share data sensed by sensors 513 and 521, as well as application and device-specific information (e.g., active and / or available applications), output devices (e.g., display, speaker, etc.), and input devices (e.g., touchscreen, microphone, imaging sensor, etc.).

[0140] In some embodiments, the watch body 520 may include, but is not limited to, a front camera 525A and / or a rear camera 525B, a sensor 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, and an optical sensor (e.g., an imaging sensor 563). Figure 5B(e.g., touch sensors, sweat sensors, etc.). In some embodiments, the body 520 may include one or more tactile devices 576 configured to provide tactile feedback (e.g., skin and / or kinesthetic sensations, etc.) to a user. Figure 5B (Vibration haptic actuator). Sensor 521 and / or haptic device 576 may also be configured to operate in conjunction with multiple applications, including but not limited to health monitoring applications, social media applications, gaming applications, and artificial reality applications (e.g., applications associated with artificial reality).

[0141] As described above, the watch body 520 and wearable strap 510, when coupled, can form a wrist wearable device 500. When coupled, the watch body 520 and wearable strap 510 operate as a single device to perform the functions described herein (operation, detection, communication, etc.). In some embodiments, specific instructions are provided to each device for performing one or more operations of the wrist wearable device 500. For example, depending on whether the watch body 520 includes a neuromuscular signal sensor, the wearable strap 510 may include alternative instructions for performing related instructions (e.g., providing sensed neuromuscular signal data to the watch body 520 via different electronic devices). Operation of the wrist wearable device 500 can be performed by the watch body 520 alone or in conjunction with the wearable strap 510 (e.g., via a corresponding processor and / or hardware component), or vice versa. In some embodiments, operation of the wrist wearable device 500, the watch body 520, and / or the wearable strap 510 can be combined with another communication coupling device (e.g., HIPD 700; Figures 7A to 7B It is executed by one or more processors and / or hardware components.

[0142] See below for reference Figure 5B As described in the block diagram, the wearable band 510 and / or the watch body 520 may each include independent resources required to perform independent functions. For example, the wearable band 510 and / or the watch body 520 may each include a power source (e.g., a battery), a memory, a data storage device, a processor (e.g., a central processing unit (CPU)), a communication device, a light source, and / or an input / output device.

[0143] Figure 5B Block diagrams are shown of a computing system 530 corresponding to a wearable strap 510 and a computing system 560 corresponding to a watch body 520, according to some embodiments. According to some embodiments, the computing system of the wrist wearable device 500 includes a combination of components of the computing system 530 of the wearable strap and components of the computing system 560 of the watch body.

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

[0145] The computing system 560 of the table may include one or more processors 579, controllers 577, peripheral device interfaces 561, power systems 595, and memory (e.g., memory 580), each of which has been defined above and is described in more detail below.

[0146] The power system 595 may include a charging input 596, a power-management integrated circuit (PMIC) 597, and a battery 598, each of which has been defined above. In some embodiments, the watch body 520 and the wearable band 510 may have their own charging inputs (e.g., charging inputs 596 and 557), their own batteries (e.g., batteries 598 and 559), and may share power with each other (e.g., the watch body 520 may power and / or charge the wearable band 510, and vice versa). Although the watch body 520 and / or the wearable band 510 may include their own charging inputs, a single charging input can charge both devices when they are coupled. The watch body 520 and the wearable band 510 may be charged using various technologies. In some embodiments, the watch body 520 and the wearable band 510 may be charged using a wired charging component (e.g., a power cord). Alternatively or additionally, the watch body 520 and / or the wearable band 510 may be configured for wireless charging. For example, a portable charging device can be designed to mate with a portion of the watch body 520 and / or wearable band 510 and wirelessly deliver available power to the battery of the watch body 520 and / or wearable band 510. The watch body 520 and 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 wearable band 510 can also share power via their respective PMICs (e.g., PMICs 597 and 558) (e.g., one can charge the other), which can share power via power and ground conductors and / or via a wireless charging antenna.

[0147] In some embodiments, the peripheral interface 561 may include one or more sensors 521, many of which are listed below and defined above. These sensors 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). These sensors 521 may include imaging sensors 563 (one or more cameras 525 and / or individual imaging sensors 563 (e.g., thermal imaging sensors)). In some embodiments, these sensors 521 include one or more SpO2 sensors 564. In some embodiments, these sensors 521 include one or more biopotential signal sensors (e.g., EMG sensors 565 that may be located on the user-facing portion of the watch body 520 and / or the wearable band 510). In some embodiments, these sensors 521 may include one or more capacitance sensors 566. In some embodiments, these sensors 521 include one or more heart rate sensors 567. In some embodiments, these sensors 521 include one or more IMUs 568. In some embodiments, one or more IMUs 568 may be configured to detect movement of the user's hand or other positions where the watch body 520 is placed or held.

[0148] In some embodiments, the peripheral device interface 561 includes an NFC component 569, a Global Positioning System (GPS) component 570, a Long-Term Evolution (LTE) component 571, and / or Wi-Fi and / or Bluetooth (BT) communication components 572. In some embodiments, the peripheral device interface 561 includes one or more buttons 573 (e.g., Figure 5A The peripheral buttons 523 and 527 in the interface cause an operation to be performed at the body 520 when selected by the user. In some embodiments, the peripheral interface 561 includes one or more indicators, such as light-emitting diodes (LEDs), to provide visual indications to the user (e.g., a message has been received, low battery, activated microphone and / or camera, etc.).

[0149] The watch body 520 may include at least one display 505 for displaying a visual representation of information or data to a user, including user interface elements and / or three-dimensional (3D) virtual objects. The display may also include a touchscreen for inputting user input, such as touch gestures, swipe 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 input from the user. The user can provide user input through the microphone 575 and can also receive audio output from the speaker 574 as part of a haptic event provided by a haptic controller 578. The watch body 520 may include at least one camera 525, including a front-facing camera 525A and a rear-facing 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.

[0150] 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 (e.g., vibrational sensations or audio outputs in response to events at the watch body 520) at the watch body 520. The haptic controllers 578 may communicate with one or more haptic devices 576, such as electroacoustic devices including a speaker from one or more loudspeakers 574 and / or other audio components and / or electromechanical devices (e.g., motors, solenoids, electroactive polymers, piezoelectric actuators, electrostatic actuators) that convert energy into linear motion, or other tactile output generating components (e.g., components that convert electrical signals into tactile outputs on the device). The haptic controllers 578 may provide haptic events perceptible to 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 a plurality of applications 582.

[0151] In some embodiments, computing system 530 and / or computing system 560 may include memory 580, which may be controlled by a memory controller from one or more controllers 577 and / or one or more processors 579. In some embodiments, software components stored in memory 580 include one or more applications 582 configured to perform operations at table body 520. In some embodiments, one or more applications 582 include games, word processors, messaging applications, calling applications, web browsers, social media applications, media streaming applications, financial applications, calendars, clocks, etc. In some embodiments, software components stored in memory 580 include one or more communication interface modules 583 as defined above. In some embodiments, software components stored in memory 580 include one or more graphics modules 584 for rendering, 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 together to perform various tasks at table body 520.

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

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

[0154] Turning to the computing system 530 of the wearable strap, one or more components that may be included in the wearable strap 510 are shown. The computing system 530 of the wearable strap 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 different configurations and / or arrangements having some or all of the components. In some embodiments, all or most of the components of the computing system 530 of the wearable strap are included in a single integrated circuit. Alternatively, in some embodiments, the components of the computing system 530 of the wearable strap are included in multiple communication-coupled integrated circuits. As described above, in some embodiments, the computing system 530 of the wearable strap is configured (e.g., via a wired or wireless connection) to be coupled to the computing system 560 of the watch body, which allows these computing systems (individually or as a single device) to share components, distribute tasks, and / or perform other operations described herein.

[0155] The wearable band's computing system 530, similar to the watch body's computing system 560, may include one or more processors 549, one or more controllers 547 (including one or more haptic controllers 548), a peripheral device interface 531 (which may include one or more sensors 513 and other peripheral devices), a power supply (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 data data 588B and sensor data 589B), and one or more modules (e.g., a communication interface module 552, a data management module 553, etc.).

[0156] Based on the above definition, one or more sensors 513 may be similar to sensor 521 of computing system 560. For example, multiple sensors 513 may include one or more coupled 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.

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

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

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

[0160] The above technology can be used with any device for sensing neuromuscular signals (including...). Figures 5A to 5B It can be used with arm-worn wearable devices, but it can also be used with other types of wearable devices for sensing neuromuscular signals, such as body wearable devices or head wearable devices that may have neuromuscular sensors closer to the brain or spine.

[0161] In some embodiments, the wrist wearable device 500 may be used in conjunction with head-mounted wearable devices (e.g., AR device 600 and VR device 610) and / or HIPD 700 as described below; and the wrist wearable device 500 may also be configured to allow a user to control aspects of the artificial reality (e.g., by controlling user interface objects in the artificial reality using EMG-based gestures and / or by allowing a user to interact with a touchscreen on the wrist wearable device). In some embodiments, the wrist wearable device 500 may also be used with wearable clothing (e.g., referred to below). Figures 8A to 8C The described smart clothing based on textiles (800) is used in combination. Having described an example wrist-worn device in this way, attention now turns to example head-worn devices, such as AR device 600 and VR device 610.

[0162] Example of a head-mounted wearable device Figure 6A , Figure 6B-1 , Figure 6B-2 and Figure 6C An example head-mounted wearable device according to some embodiments is illustrated. The head-mounted wearable device may include, but is not limited to, an AR device 610 (e.g., an AR or smart eye-wearing device, such as smart glasses, smart monocles, smart contact lenses, etc.), a VR device 610 (e.g., a VR headset, head-mounted display (HMD), etc.), or other eye-coupled devices. AR device 600 and VR device 610 are described herein with reference to... Figures 1A to 3 The examples of head-mounted wearable devices described are such that head-mounted wearable devices should be understood as having the characteristics of AR device 600 and / or VR device 610, and vice versa. AR device 600 and VR device 610 can perform various functions and / or operations associated with browsing and selectively opening applications through a user interface.

[0163] In some embodiments, the AR system (e.g., AR system 400a to 400d); Figures 4A to 4D-2 ) including AR devices 600 (such as Figure 6A (as shown) and / or VR device 610 (such as Figures 6B-1 to 6B-2 As shown). In some embodiments, AR device 600 and VR device 610 may include one or more simulation components (e.g., components for presenting an interactive artificial reality environment, such as a processor, memory, and / or a presentation device including one or more displays and / or one or more waveguides), some of which will refer to Figure 6C For a more detailed description, the head-mounted wearable device may use a display projector (e.g., display projector components 607A and 607B) and / or a waveguide to project data representations to a user. Some embodiments of the head-mounted wearable device do not include a display.

[0164] Figure 6A An example visual description of an AR device 600 (e.g., which may also be described herein as augmented reality glasses and / or smart glasses) is shown. The AR device 600 can be used with... Figure 6AAdditional electronic components (e.g., wearable accessory devices and / or intermediate processing devices configured for use with AR device 600, either electronically or otherwise) not shown in the diagram, will work together. In some embodiments, the wearable accessory device and / or intermediate processing device may be configured to be coupled to AR device 600 via a coupling mechanism in electrical communication with coupling sensor 624, wherein coupling sensor 624 can detect when the electronic device becomes physically or electronically coupled to AR device 600. In some embodiments, AR device 600 may be configured to be coupled to a housing (e.g., a frame 604 or a portion of temple arm 605), which may include one or more additional coupling mechanisms configured to be coupled to the additional accessory device. Figure 6A The components shown 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).

[0165] AR device 600 includes mechanical eyewear components, including a frame 604 configured to hold one or more lenses (e.g., one or two lenses 606-1 and 606-2). Those skilled in the art will understand that AR device 600 may include additional mechanical components, such as hinges configured to allow multiple portions of frame 604 of AR device 600 to fold and unfold, a bridge configured to span the gap between lenses 606-1 and 606-2 and rest against the user's nose, a nose pad configured to rest on the nose bridge and provide support for AR device 600, temple tips configured to rest on the user's ears and provide additional support for AR device 600, temple arms 605 configured to extend from the hinges to the temple tips of AR device 600, etc. Those skilled in the art will further understand that some examples of AR device 600 may not include any of the mechanical components described herein. For example, smart contact lenses configured to present artificial reality to a user may not include any components of AR device 600.

[0166] Lenses 606-1 and 606-2 can be separate displays or display devices (e.g., waveguides for projecting representations). Lenses 606-1 and 606-2 can 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 can operate in conjunction with one or more display projector assemblies 607A and 607B to present image data to a user. Although AR device 600 includes two displays, embodiments of this disclosure can be implemented in AR devices having a single near-eye display (NED) or more than two NEDs.

[0167] AR device 600 includes electronic components, many of which will be discussed below. Figure 6C To describe in more detail. Figure 6A Some example electronic components are shown, including sensors 623-1, 623-2, 623-3, 623-4, 623-5, and 623-6, which can be distributed along most of the frame 604 of the AR device 600. See below for reference. Figure 6C The description includes different types of sensors. The AR device 600 also includes a left camera 639A and a right camera 639B located on different sides of the frame 604. The eye-wearing device includes one or more processors 648A and 648B (e.g., integrated microprocessors, such as ASICs) embedded in a portion of the frame 604.

[0168] Figure 6B-1 and Figure 6B-2 An example visual description of a VR device 610 (e.g., a head-mounted display (HMD) 612, also referred to herein as an artificial reality head-mounted device, head-wearable device, VR head-mounted device, etc.) is shown. The HMD 612 includes a front body 614 and a frame 616 (e.g., a strip or band) shaped to fit around a user's head. In some embodiments, the front body 614 and / or frame 616 include one or more electronic components for facilitating the presentation and / or interaction with AR and / or VR systems (e.g., displays, processors (e.g., processor 648A-1), IMUs, tracking transmitters or detectors, sensors, etc.). In some embodiments, the HMD 612 includes an output audio transducer (e.g., an output audio transducer 618), such as... Figure 6B-2 As shown. In some embodiments, as Figure 6B-2 As shown, one or more components, such as one or more output audio converters 618 and frame 616 (e.g., part or all of frame 616 and / or output audio converters 618), can be configured to attach and detach (e.g., detachably attach) to HMD 612. In some embodiments, coupling a detachable component to HMD 612 enables the detachable component to communicate electronically with HMD 612. VR device 610 includes electronic components, many of which will be discussed below. Figure 6C To describe in more detail.

[0169] Figures 6B-1 to 6B-2The VR device 610 is also shown to have one or more cameras, such as left camera 639A and right camera 639B, which may resemble the left and right cameras on the frame 604 of the AR device 600. In some embodiments, the VR device 610 includes one or more additional cameras (e.g., cameras 639C and 639D), which may be configured to enhance the image data obtained by cameras 639A and 639B by providing more information. For example, camera 639C may be used to provide color information that cameras 639A and 639B cannot recognize. In some embodiments, one or more of cameras 639A to 639D may include an optional infrared (IR) cutoff filter configured to remove IR light received at the respective camera sensor.

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

[0171] Alternatively or additionally, in some embodiments, head-worn wearable devices such as VR device 610 and / or AR device 600 include or are communicatively coupled to another external device (e.g., a pairing device), such as HIPD 7 (hereinafter referred to as...). Figures 7A to 7B (Discussion) and / or an optional neckband. An optional neckband may be coupled to the head-wearable device via one or more connectors (e.g., wired or wireless connectors). The head-wearable device and the neckband may operate independently without any wired or wireless connection between them. In some embodiments, components of the head-wearable device and components of the neckband may be located on one or more additional peripheral devices, neckbands, or some combination thereof paired with the head-wearable device. Furthermore, the term "neckband" is intended to represent any suitable type or form of paired device. Therefore, the following discussion of neckbands can also be applied to a variety of other paired devices, such as smartwatches, smartphones, wristbands, other wearable devices, handheld controllers, tablet computers, or laptops.

[0172] In some cases, pairing an external device, such as a mid-processing device (e.g., HIPD 700, optional neckband, and / or wearable accessory device), with a head-worn device (e.g., AR device 600 and / or VR device 610) allows the head-worn device to achieve glasses-like form factors while still providing sufficient battery power and computing power for extended capabilities. Some or all of the head-worn device's battery power, computing resources, and / or additional features can be provided by the paired device or shared between the paired device and the head-worn device, thus reducing the overall weight, heat distribution, and form factor of the head-worn device while still allowing it to retain its desired functionality. For example, a mid-processing device (e.g., HIPD 700) can allow components originally included in the head-worn device to be included in the mid-processing device (and / or the wearable device or accessory device), thereby transferring weight load from the user's head and neck to one or more other parts of the user's body. In some embodiments, the mid-processing device has a large surface area on which heat is diffused and distributed to the surrounding environment. Therefore, compared to standalone head-mounted wearables, mid-processor devices can allow for greater battery capacity and computing power. Because the weight carried in the mid-processor device is less invasive to the user than that carried in the head-mounted wearable device, users can tolerate wearing lighter eye-mounted devices and carrying or wearing paired devices for longer periods of time, compared to tolerating wearing a heavier eye-mounted device alone. This allows users to more fully integrate artificial reality into their daily activities.

[0173] In some embodiments, the intermediate processing device is communicatively coupled to the head-mounted wearable device and / or other devices. These other devices may provide certain functions to the head-mounted wearable device (e.g., tracking, localization, depth map construction, processing, storage, etc.). 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-mounted wearable device in an electronic format (analog or digital).

[0174] The controller of the intermediate processing device processes information generated by the intermediate processing device and / or sensors on the head-mounted wearable device. An intermediate processing device like the HIPD 700 can process information generated by one or more of its sensors and / or information provided by other communication-coupled devices. For example, the head-mounted wearable device may include an IMU, and the intermediate processing device (neckband and / or HIPD 700) can perform all inertial and spatial calculations from the IMU located on the head-mounted wearable device. See below for reference. Figure 7A and Figure 7B Additional examples of processing performed by communication-coupled devices such as the HIPD 700 are provided.

[0175] Artificial reality systems can include various types of visual feedback mechanisms. For example, the display device in AR device 600 and / or VR device 610 can include one or more liquid-crystal displays (LCDs), light-emitting diode (LED) displays, organic LED (OLED) displays, and / or any other suitable type of display. Artificial reality systems can include a single display for each eye, or can provide one display for each eye, which can provide additional flexibility for zoom adjustment or correction of refractive errors associated with the user's vision. Some artificial reality systems also include an optical subsystem with one or more lenses (e.g., conventional concave or convex lenses, Fresnel lenses, or adjustable liquid lenses) through which the user views the display. In addition to using displays, or instead of using displays, some artificial reality systems include one or more projection systems. For example, the display device in AR device 600 and / or VR device 610 can include (e.g., using waveguides) miniature LED projectors that project light into the display device, such as transparent combiner lenses that allow ambient light to pass through. Display devices can refract projected light toward the user's pupils, allowing the user to simultaneously view both artificial reality content and the real world. Artificial reality systems can also be configured with any other suitable type or form of image projection system. As mentioned above, some AR systems essentially replace one or more of the user's sensory perceptions of the real world with virtual experiences, rather than combining artificial reality with actual reality.

[0176] Although the example head-worn devices are described herein as AR device 600 and VR device 610 respectively, any one or both of the example head-worn devices described herein may be configured to present a fully immersive VR scene in substantially all of the user's field of view, or additionally or alternatively, a more subtle augmented reality scene in a portion (less than all) of the user's field of view.

[0177] In some embodiments, AR device 600 and / or VR device 610 may include a haptic feedback system. The haptic feedback system can provide various types of skin feedback, including vibration, force, traction, shear, texture, and / or temperature. The haptic feedback system can also provide various types of kinematic feedback, such as motion and compliance. Haptic feedback can be implemented using motors, piezoelectric actuators, fluid systems, and / or various other types of feedback mechanisms. The haptic feedback system can be implemented independently of other artificial reality devices, within other artificial reality devices, and / or in conjunction with other artificial reality devices (e.g., wrist-worn devices that can be integrated into headwear, gloves, bodysuits, handheld controllers, environmental devices (e.g., chairs or footrests), and / or any other type of device or system (such as wrist-worn device 500, HIPD 700, textile-based smart clothing 800, etc.)) and / or other devices described herein.

[0178] Figure 6C A computing system 620 and an optional housing 690 are shown, each illustrating components that can be included in a head-mounted wearable device (e.g., AR device 600 and / or VR device 610). In some embodiments, the optional housing 690 may include more or fewer components depending on the actual constraints of the respective head-mounted wearable device described. Additionally or alternatively, the optional housing 690 may include additional components that extend and / or enhance the functionality of the head-mounted wearable device.

[0179] In some embodiments, the computing system 620 and / or optional housing 690 may include one or more peripheral interfaces 622A and 622B, one or more power systems 642A and 642B (including a charging input 643, a PMIC 644, and a 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 the examples provided), and memories 650A and 650B, all of which can communicate electronically with each other. For example, one or more processors 648A and / or 648B may be configured to execute instructions stored in memories 650A and / or 650B, which may cause controllers in one or more controllers 646A and / or 646B to perform operations at one or more peripheral devices of the peripheral interfaces 622A and / or 622B. In some embodiments, each of the described operations may occur based on power supplied by power systems 642A and / or 642B.

[0180] In some embodiments, the peripheral device interface 622A may include one or more devices configured as part of the computing system 620, many of which have already been described above. Figure 5A and Figure 5B The wrist-worn wearable device shown is defined and / or described. For example, the peripheral device interface may include one or more sensors 623A. Some example sensors include: one or more coupled 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, these sensors 623A also include a depth sensor 667, a light sensor 668, and / or any other type of sensor defined above or described with respect to any other embodiments discussed herein.

[0181] 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 WiFi and / or Bluetooth (BT) devices 633, one or more buttons 634 (e.g., including slide-able 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 first cameras 639-1 to nth cameras 639-n similar to left camera 639A and / or right camera 639B), one or more haptic devices 640, and / or any other type of peripheral device as defined above or described with respect to any other embodiments discussed herein.

[0182] Head-mounted wearable devices can include various types of visual feedback mechanisms (e.g., presentation devices). For example, the display devices in AR device 600 and / or VR device 610 can 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. Head-mounted wearable devices can include (e.g., configured to be viewed by both eyes) a single display, and / or can provide a separate display for each eye, which can provide additional flexibility for zoom adjustment or correction of refractive errors associated with the user's vision. Some embodiments of head-mounted wearable devices 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 views the display. For example, each display 635A can be coupled to each of the lenses 606-1 and 606-2 of AR device 600. The displays 635A coupled to each of the lenses 606-1 and 606-2 can act together or independently to present an image or a series of images to the user. In some embodiments, AR device 600 and / or VR device 610 include a single display 635A (e.g., a near-eye display) or more than two displays 635A.

[0183] In some embodiments, a first set of one or more displays 635A may be used to present an augmented reality environment, and a second set 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 artificial reality content to a user of AR device 600 and / or VR 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 wholly or partially integrated into AR device 600 and / or VR device 610. In addition to using displays, or instead of using displays, some artificial reality systems may include one or more projection systems. For example, the display devices in AR device 600 and / or VR device 610 may include (e.g., using waveguides) miniature LED projectors that project light into the display devices, such as transparent combiner lenses that allow ambient light to pass through. The display devices may refract the projected light toward the user's pupil, allowing the user to simultaneously view both artificial reality content and the real world. Head-mounted wearable devices may also be configured with any other suitable type or form of image projection system. In some embodiments, one or more waveguides are additionally or alternatively provided to one or more displays 635A.

[0184] In some embodiments of the head-mounted wearable device, ambient light and / or a real-time view of the real world (e.g., a real-time feed of the user's surroundings) can pass through the display elements of the respective head-mounted wearable device that present aspects of the AR system. In some embodiments, ambient light and / or a real-time view of the real world can pass through a portion (not all) of the AR environment presented within the user's field of view (e.g., a portion of the AR environment is located in the same location as physical objects in the user's real-world environment, which is within a designated boundary (e.g., a guardian boundary) configured for use by the user when interacting with the AR environment). For example, visual user interface elements (e.g., notification user interface elements) can be presented on the head-mounted wearable device, and a certain amount of ambient light and / or a real-time view (e.g., 15%-50% of the ambient light and / or real-time view) can pass through the user interface elements, allowing the user to distinguish at least a portion of the physical environment on which the user interface elements are displayed.

[0185] The head-mounted wearable device may include one or more external displays 635A for presenting information to a user. For example, the external display 635A may be used to display current battery level, network activity (e.g., connected, disconnected, etc.), current activity (e.g., playing games, making calls, attending meetings, watching movies, etc.), 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-mounted wearable device may cause the external display 635A to display a Do Not Disturb notification. The user may also use the external display 635A to share any information acquired by one or more components of the peripheral device interface 622A and / or generated by the head-mounted wearable device (e.g., during the operation and / or execution of one or more applications).

[0186] Memory 650A may include instructions and / or data executable by a memory controller of one or more processors 648A (and / or processor 648B of housing 690) and / or one or more controllers 646A (and / or controller 646B of housing 690). 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 AR processing modules 655A, and / or any other type of module or component defined above or described with respect to any other embodiments discussed herein.

[0187] The data 660 stored in memory 650A can be used in conjunction with one or more of the applications and / or programs discussed above. Data 660 may include data 661, sensor data 662, media content data 663, AR application data 664, and / or any other types of data defined above or described with respect to any other embodiments discussed herein.

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

[0189] In some embodiments, physical electronic connectors can transmit information between the head-worn device and another electronic device, and / or between one or more processors 648A and controllers 646A within the head-worn device. This information can be in the form of optical data, electrical data, wireless data, or any other transmissible data format. Moving the processing of information generated by the head-worn device to an intermediate processing device can reduce weight and heat in the eyewear device, making it more comfortable and safer for the user. In some embodiments, optional accessory devices (e.g., electronic neckbands or HIPD 700) are coupled to the head-worn device via one or more connectors. Connectors can be wired or wireless and can include electronic components and / or non-electronic (e.g., structural) components. In some embodiments, the head-worn device and accessory devices can operate independently without any wired or wireless connection between them.

[0190] Head-mounted wearable devices can include various types of computer vision components and subsystems. For example, AR device 600 and / or VR device 610 can include one or more optical sensors, such as two-dimensional (2D) cameras or three-dimensional (3D) cameras, time-of-flight depth sensors, single-beam or scanning laser rangefinders, 3D LiDAR sensors, and / or any other suitable type or form of optical sensor. The head-mounted wearable device can 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 within the real-world physical environment. In some embodiments, the methods described herein are used to map the real world, provide the user with context 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 an AR environment), and various other functions. For example, Figure 6B-1 and Figure 6B-2 A VR device 610 with cameras 639A to 639D is shown. These cameras can be used to provide depth information for creating voxel fields and two-dimensional meshes to provide the user with object information to avoid collisions.

[0191] Optional housing 690 may include components similar to those described above with respect to computing system 620. For example, optional housing 690 may include a corresponding peripheral interface 622B, which includes more or fewer components than those described above with respect to peripheral interface 622A. As mentioned above, the components of optional housing 690 can be used to enhance and / or expand the functionality of the head-mounted wearable device. For example, optional housing 690 may include corresponding sensors 623B, speakers 636B, displays 635B, microphones 637B, cameras 638B, and / or other components for acquiring and / or presenting data. Similarly, 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 AR processing modules 655B, etc.), and the one or more processors, controllers, and / or memory may be used individually and / or in combination with the components of computing system 620.

[0192] The above text is in Figures 6A to 6C The technologies described herein can be used with various head-worn wearable devices. In some embodiments, the head-worn wearable device (e.g., AR device 600 and / or VR device 610) can be used with devices such as wrist-worn wearable device 500 (or components thereof) and / or textile-based smart clothing 800. Figures 8A to 8COne or more wearable devices, such as the HIPD 700, can be used in conjunction with the HIPD 700. Having described an example of a head-mounted wearable device, let’s now turn our attention to example handheld middleware devices such as the HIPD 700.

[0193] Example handheld intermediate processing device Figure 7A and Figure 7B An example handheld intermediate processing device (HIPD) 700 according to some embodiments is shown. The HIPD 700 can perform various functions and / or operations associated with browsing and selectively opening applications through a user interface.

[0194] Figure 7A Top view 705 and side view 725 of HIPD 700 are shown. HIPD 700 is configured to communicatively couple to one or more wearable devices (or other electronic devices) associated with a user. For example, HIPD 700 is configured to communicatively couple to a user's wrist wearable device 500 (or components thereof, such as watch body 520 and wearable strap 510), AR device 600, and / or VR device 610. 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, in their bag, etc.), placed near the user (e.g., on their desk when seated, on a charging dock, etc.), and / or placed at or within a predetermined distance from or within of the wearable device or other electronic device (e.g., in some embodiments, the predetermined distance is the maximum distance at which HIPD 700 can successfully communicatively couple with electronic devices such as wearable devices (e.g., 10 meters)).

[0195] The HIPD 700 can perform various functions independently and / or in conjunction with one or more wearable devices (e.g., wrist wearable device 500, AR device 600, VR device 610, etc.) to perform various functions. The HIPD 700 is configured to enhance and / or improve the functionality of communication-coupled devices such as wearable devices. The HIPD 700 is configured to perform one or more functions or operations associated with: interacting with the user interface and applications of the communication-coupled device, interacting with an AR environment, interacting with a VR environment, and / or operating as a human-machine interface controller. Furthermore, as will be described in more detail below, the functions and / or operations of the HIPD 700 may include, but are not limited to, task offloading and / or handover; hot offloading and / or handover; 6 degrees of freedom (6 DoF) raycasting and / or gaming (e.g., using imaging devices or cameras 714A and 714B, which may be used for simultaneous localization and mapping (SLAM) and / or in conjunction 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, personal area network, etc.); location determination; financial transactions; providing haptic feedback; alarms; notifications; biometric authentication; health monitoring; sleep monitoring, etc. The example functions described above may be performed independently within the HIPD 700 and / or independently in communication between the HIPD 700 and another wearable device described herein. In some embodiments, the functions of the HIPD 700 can be performed in conjunction with an AR environment. As those skilled in the art will understand upon reading the description provided herein, the novel HIPD 700 described herein can be used with any type of suitable AR environment.

[0196] When the HIPD 700 is communicatively coupled to wearable devices and / or other electronic devices, the HIPD 700 is configured to perform one or more operations initiated at the wearable device and / or other electronic device. Specifically, 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 executes one or more operations of the wearable device and / or other electronic device and provides data corresponding to the completed operation to the wearable device and / or other electronic device. For example, a user can initiate a video stream using an AR device 600, and backend tasks associated with executing the video stream (e.g., video rendering) can be offloaded to the HIPD 700. The HIPD 700 executes the backend task and provides the corresponding data to the AR device 600 to execute the remaining frontend tasks associated with the video stream (e.g., presenting the rendered video data via the display of the AR device 600). In this way, the HIPD 700, with more computing resources and greater thermal headroom compared to the wearable device, can perform computationally intensive tasks for the wearable device, thereby improving the performance of the operations performed by the wearable device.

[0197] The HIPD 700 includes a multi-touch input surface 702 located on a first side (e.g., the front surface), configured to detect one or more user inputs. Specifically, the multi-touch input surface 702 can detect single-click input, multi-click input, swipe gestures and / or inputs, force-based and / or pressure-based touch input, held 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 surface recesses and a second touch input surface 706 defined by substantially flat portions. The first touch input surface 704 may be positioned 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 portions of the multi-touch input surface 702. For example, the first touch input surface 704 may be substantially circular, while 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 in manipulating the HIPD 700. Specifically, the surface recess is configured such that the user holds the HIPD 700 vertically when holding it with one hand (e.g., such that the imaging device or cameras 714A and 714B being used are pointed towards the ceiling or sky). Furthermore, the surface recess is configured such that the user's thumb is positioned within the first touch input surface 704.

[0198] In some embodiments, different touch input surfaces include multiple touch input areas. For example, a 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 of these touch input areas are optional and / or user-defined (e.g., a user can specify touch input areas based on their preferences). In some embodiments, each touch input surface and / or touch input area is associated with a predetermined set of commands. For example, user input detected in the first touch input area 708 causes the HIPD 700 to execute a first command, while 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 area 708 can be configured to detect force touch input (e.g., the magnitude of a user's press) and capacitive touch input, and the second touch input area 706 can be configured to detect capacitive touch input.

[0199] 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 used in conjunction with a camera 714 for manipulating 3D objects in an AR or VR environment (e.g., zooming in on an object, moving an object, destroying an object, etc.). Non-limiting examples of sensors 751 included in HIPD 700 include light sensors, magnetometers, depth sensors, pressure sensors, and force sensors. See below for reference. Figure 7B Additional examples of sensor 751 are provided.

[0200] The 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 may serve as a privacy light to notify the user and / or other people nearby that imaging devices and / or microphones are active. In some embodiments, the light indicator is located near one or more touch input surfaces. For example, a light indicator may be placed around a first touch input surface 704. The light indicator may illuminate with 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 may 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 so on.

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

[0202] Side view 725 of the HIPD 700 shows a sensor group 720 and a camera 714B. The sensor group 720 includes one or more cameras 722A and 722B, a depth projector 724, an ambient light sensor 728, and a depth receiver 730. In some embodiments, the sensor group 720 includes a light indicator 726. The light indicator 726 can be used as a privacy indicator to let the user and / or those around them know that the camera and / or microphone is active. The sensor group 720 is configured to capture the user's facial expressions, allowing the user to manipulate a customized avatar (e.g., displaying emotions such as smiling or laughing on the avatar or the user's digital image). The sensor group 720 can be configured as a side stereo RGB system, a post-indirect time-of-flight (iToF) system, or a post-stereo RGB system. As those skilled in the art will understand upon reading the description provided herein, the novel HIPD 700 described herein can be constructed and / or positioned using different sensor group 720 configurations.

[0203] In some embodiments, the HIPD 700 includes one or more haptic devices 771 configured to provide haptic feedback (e.g., kinesthetic sensation). Figure 7B (e.g., a vibration haptic actuator). Sensor 751 and / or haptic device 771 may be configured to operate in conjunction with multiple application and / or communication-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)).

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

[0205] As described above, the HIPD 700 can 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 can 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 can (e.g., via one or more processors, such as a Central Processing Unit (CPU) 777); Figure 7B The HIPD 700 can perform backend and frontend tasks. It can be used, but is not limited to, to perform enhanced calling (e.g., receiving and / or sending 3D or 2.5D real-time volumetric calling, real-time digital human avatar calling, and / or avatar calling), discreet messaging, 6DoF portrait / landscape gaming, AR / VR object manipulation, AR / VR content display (e.g., presenting content via a virtual display), and / or other AR / VR interactions. The HIPD 700 can perform these operations alone or in conjunction with wearable devices (or other communication-coupled electronic devices).

[0206] Figure 7B A block diagram of a computing system 740 for 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 HIPD computing system 740. The HIPD 700 will be understood to include the components for the HIPD computing system 740 shown and described below. In some embodiments, all or most of the components of the HIPD computing system 740 are included in a single integrated circuit. Alternatively, in some embodiments, the components of the HIPD computing system 740 are included in multiple communication-coupled integrated circuits.

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

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

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

[0210] Similar to the reference above Figure 5B The computing system 560 of the described watch body and the computing system 530 of the wearable strap, the computing system 740 of the HIPD may include one or more haptic controllers 776 and associated components (e.g., haptic devices 771) for providing haptic events at the HIPD 700.

[0211] 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. Access to the memory 778 by other components of the HIPD 700 (e.g., one or more processors and peripheral interface 750) may be controlled by the memory controller of the controller 775.

[0212] In some embodiments, the software components stored in the memory 778 include one or more operating systems 779, one or more applications 780, one or more communication interface modules 781, one or more graphics modules 782, and one or more data management modules 785, which are similar to those described above. Figure 5B The software component described.

[0213] In some embodiments, software components stored in memory 778 include a task and processing management module 783, which is configured to identify one or more front-end and back-end tasks associated with an operation performed by a user, execute one or more front-end and / or back-end tasks, and / or provide 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, the task and processing 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 margin, ongoing operation, and / or other factors of the communication-coupled device. For example, the task and processing management module 783 may cause one or more back-end tasks (operations performed at the communication-coupled AR device 600) to be executed at HIPD 700 based on the determination that an operation is utilizing a predetermined amount (e.g., at least 70%) of the computing resources available at AR device 600.

[0214] In some embodiments, the software components stored in memory 778 include an interoperability module 784 for exchanging and utilizing information received and / or provided to different communication coupling 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 memory 778 include an AR module 785 configured to process signals based at least on sensor data used in AR and / or VR environments. For example, the AR processing module 785 can be used for 3D object manipulation, gesture recognition, face recognition, and facial expression recognition, etc.

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

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

[0217] The above text is in Figures 7A to 7BThe technology described herein can be used with any device used as a human-machine interface controller. In some embodiments, HIPD 700 can be used in conjunction with one or more wearable devices, such as head-mounted wearable devices (e.g., AR device 600 and VR device 610) and / or wrist-mounted wearable devices 500 (or components thereof). In some embodiments, HIPD 700 can also be used in conjunction with wearable clothing, such as textile-based smart clothing 800. Figures 8A to 8C The example HIPD 700 has already been described in this way; now let’s turn our attention to example feedback devices, such as the textile-based smart clothing 800.

[0218] Examples of smart clothing based on textiles Figure 8A and Figure 8B Example textile-based smart garments according to some embodiments are shown. Textile-based smart garments 800 (e.g., wearable gloves, shirts, headbands, wristbands, socks, etc.) are configured to communicatively couple to one or more electronic devices, such as wrist wearable devices 500, head wearable devices, HIPD 700, laptops, tablets, and / or other computing devices. Textile-based smart garments 800 can perform various functions and / or operations associated with browsing and selectively opening applications through a user interface.

[0219] Smart clothing based on textiles 800 can be an AR system (e.g., see above reference). Figure 4D-1 and Figure 4D-2 This is part of the described AR system 400d. The textile-based smart garment 800 is also configured to provide feedback (e.g., tactile feedback or other haptic feedback) to the user based on user interactions with the computing system (e.g., browsing of the user interface, application operations (e.g., game vibration, media responsive haptics), device notifications, etc.) and / or user interactions within the AR environment. In some embodiments, the textile-based smart garment 800 receives instructions from a communication coupling device (e.g., a wrist-worn wearable device 500, a head-worn wearable device, and a HIPD 700, etc.) to induce the execution of a feedback response. Alternatively or additionally, in some embodiments, the textile-based smart garment 800 determines one or more feedback responses to provide to the user. The textile-based smart garment 800 may be based on feedback from one or more of its sensors (e.g., sensor 851; Figure 8C Sensor data acquired by sensors (e.g., sensors in a wrist-worn wearable device 500, a head-mounted device, a HIPD 700, and / or other computing devices) or communication-coupled sensors (e.g., sensors in a wrist-worn wearable device 500, a head-mounted device, a HIPD 700, and / or other computing devices) is used to determine one or more feedback responses.

[0220] Non-limiting examples of feedback determined by the textile-based smart garment 800 and / or communication coupling devices include visual feedback, audio feedback, tactile (e.g., tactile, kinematic, etc.) feedback, thermal or temperature feedback, and / or other sensory-perceptible feedback. The textile-based smart garment 800 may include corresponding feedback devices (e.g., tactile devices or tactile components 862 or other feedback devices or components) to provide feedback responses to the user. Similarly, the textile-based smart garment 800 may be communicationally coupled to another device (and / or the feedback devices of other devices) to coordinate the feedback provided to the user. For example, a VR device 610 may present an AR environment to the user, and the textile-based smart garment 800 provides a corresponding response to the user when the user interacts with objects within the AR environment (e.g., a virtual cup). In particular, the textile-based smart garment 800 may provide tactile feedback to simulate the feeling of touching a hard cup by preventing one or more of the user's fingers (or at least hindering / resisting their movement) from bending beyond a specific point, and / or provide thermal feedback to simulate the feeling of a cold or hot beverage.

[0221] Additionally or alternatively, in some embodiments, the textile-based smart garment 800 is configured to operate as a controller, which is configured to perform one or more functions or operations associated with: interacting with a user interface and application of a communication-coupled device, interacting with an AR environment, interacting with a VR environment, and / or operating as a human-machine interface controller.

[0222] Figure 8A One or more tactile components 862 (e.g., first tactile component 862-1 to fourth tactile component 862-4) are shown on the palm side of a textile-based smart garment 800 adjacent to the user's hand. Figure 8BAn additional tactile component (e.g., a fifth tactile component 862-5) is shown on the back of the hand of a textile-based smart garment 800 adjacent to the user's hand. In some embodiments, the tactile component 862 includes a mechanism that provides resistance at least when each tactile component 862 transitions from a first state (e.g., a first pressurized state (e.g., at atmospheric pressure or when deflated)) to a second state (e.g., a second pressurized state (e.g., inflated to a threshold pressure)). In other words, the described tactile component 862 can transition between a first pressurized state and a second pressurized state to provide tactile feedback to the user. The tactile component 862 can be integrated into various devices configured to contact or approach the user's skin, including but not limited to devices such as glove-wearing devices, body-wearing garment devices, and head-mounted devices. Each of these tactile components 862 can be included in or physically coupled to a garment part 804 of the textile-based smart garment 800. For example, each of the haptic components 862-1, 862-2, 862-3, ... 862-N is physically coupled to the garment 804 and configured to contact the corresponding phalanges of the user's thumb and other fingers.

[0223] Due to the constantly changing nature of artificial reality, the haptic component 862 may need to transition between multiple states hundreds or possibly thousands of times during a single use. Therefore, the haptic component 862 described herein is durable and designed to transition rapidly between states. For some background, in a first pressurized state, the haptic component 862 does not impede the free movement of a part of the wearer's body. For example, one or more haptic components 862 incorporated into a glove are made of a flexible material (e.g., an electrostatic zipper actuator) that does not impede the free movement of the wearer's hand and fingers. The haptic component 862 is configured to conform to the shape of a part of the wearer's body when in the first pressurized state. However, once in a second pressurized state, the haptic component 862 may be configured to restrict and / or impede the free movement of that part of the wearer's body (e.g., appendages of the user's hand). For example, when the haptic component 862 is in the second pressurized state, the corresponding haptic component 862 (or multiple corresponding haptic components) may restrict the movement of the wearer's fingers (e.g., prevent fingers from curling or extending). Furthermore, once in the second pressurized state, the tactile components 862 can take different shapes, some of which are configured to take a planar, rigid shape (e.g., flat and rigid), while others are configured to be at least partially bent or folded.

[0224] Smart clothing based on textiles 800 can be an AR system (e.g., Figures 4A to 4D-2One of multiple devices in an AR system. For example, a user could wear a pair of gloves (e.g., a first-type textile-based smart garment 800), wear the tactile component of a wrist-worn device 600 (… Figures 5A to 5B Wearing a headband (e.g., a second type of textile-based smart garment 800), holding a HIPD 700, etc. As described above, the haptic component 862 is configured to provide haptic simulation to the wearer of the textile-based smart garment 800. The garment 804 of each textile-based smart garment 800 can be one of various clothing items (e.g., gloves, socks, shirts, trousers, etc.). Therefore, a user can wear multiple textile-based smart garments 800, each configured to provide haptic stimulation to various parts of the body wearing the textile-based smart garment 800. Although the textile-based smart garment 800 is described as a standalone device, in some embodiments, the textile-based smart garment 800 can be combined with other wearable devices described herein. For example, the textile-based smart garment 800 can form part of the VR device 610 (e.g., a headband portion).

[0225] Figure 8C A block diagram of a computing system 840 for a haptic component 862 according to some embodiments is shown. The computing system 840 may include one or more peripheral device interfaces 850, one or more power systems 895 (including a charging input 896, a PMIC 897, and a battery 898), one or more controllers 875 (including one or more haptic controllers 876), one or more processors 877 (as described above, including any of the examples provided), and a memory 878, all of which can communicate electronically with each other. For example, one or more processors 877 may be configured to execute instructions stored in the memory 878, which may cause controllers in one or more controllers 875 to perform operations at one or more peripheral devices of the peripheral device interface 850. In some embodiments, each described operation may occur based on power provided by the power system 895.

[0226] In some embodiments, the peripheral device interface 850 may include one or more devices configured as part of the computing system 840, many of which have already been defined above and / or discussed. Figures 5A to 7BThe wrist-worn wearable device shown is described. For example, the peripheral device interface 850 may include one or more sensors 851, such as one or more pressure sensors 852, one or more EMG sensors 856, one or more IMUs 858, one or more position sensors 859, one or more capacitive sensors 860, one or more force sensors 861; and / or any other type of sensor defined above or described with respect to any other embodiments discussed herein. In some embodiments, the peripheral device interface may include one or more additional peripheral devices, including one or more WiFi and / or Bluetooth (BT) devices 868; LTE components 869; GPS components 870; microphones 871; one or more haptic components 862; one or more support structures 863 (which may include one or more bladders 864); one or more manifolds 865; one or more pressure changing devices 867; one or more displays 872; one or more buttons 873; one or more speakers 874; and / or any other type of peripheral device defined above or described with respect to any other embodiments discussed herein. In some embodiments, the computing system 840 includes a comparison Figure 8C The number of components shown may be more or less.

[0227] In some embodiments, each tactile component 862 includes a support structure 863 and at least one bladder 864. The bladder 864 (e.g., a membrane) is a sealed, inflatable bag made of a durable and puncture-resistant material, such as thermoplastic polyurethane (TPU) or a flexible polymer. The bladder 864 contains a medium (e.g., a fluid such as air, an inert gas, or even a liquid) that can be added to or removed from the bladder 864 to change the pressure (e.g., fluid pressure) within the bladder 864. The support structure 863 is made of a material that is stronger and more rigid than the material of the bladder 864. The corresponding support structure 863 coupled to the corresponding bladder 864 is configured to reinforce the corresponding bladder 864 when the corresponding bladder changes shape and size due to changes in the pressure (e.g., fluid pressure) within the bladder. The example tactile components 862 described above are non-limiting. The tactile component 862 may include an eccentric rotating mass (ERM), a linear resonant actuator (LRA), a voice coil motor (VCM), a piezoelectric tactile actuator, a thermoelectric device, a solenoid actuator, an ultrasonic transducer, a thermal resistance heater, a Peltier device, and / or other devices configured to produce a perceptible response.

[0228] The textile-based smart garment 800 also includes a haptic controller 876 and a pressure-changing device 867. Alternatively, in some embodiments, a computing system 840 is communicatively coupled to the haptic controller 876 and / or the pressure-changing device 867 (e.g., electronically communicating with one or more processors 877 of the computing system 840). The haptic controller 876 is configured to control the operation of the pressure-changing device 867, and consequently, the operation of the textile-based smart garment 800. For example, the haptic controller 876 sends one or more signals to the pressure-changing device 867 to activate the pressure-changing device 867 (e.g., turn it on and off). The one or more signals may specify a desired pressure (e.g., pounds per square inch) to be output by the pressure-changing device 867. The generation of one or more signals and, consequently, the pressure output by the pressure-changing device 867 may be based on information collected by sensors 851 of the textile-based smart garment 800 and / or other communicatively coupled devices. For example, the haptic controller 876 can provide one or more signals based on collected sensor data to cause the pressure changing device 867 to increase the pressure (e.g., fluid pressure) within the first haptic component 862 at a first time, and to provide one or more additional signals to the pressure changing device 867 based on additional sensor data to further increase the pressure within the second haptic component 862 at a second time after the first time. Furthermore, the haptic controller 876 can provide one or more signals to cause the pressure changing device 867 to inflate one or more bladders 864 in a first portion (e.g., a first finger) of the textile-based smart garment 800, while one or more bladders 864 in a second portion (e.g., a second finger) of the textile-based smart garment 800 remain unchanged. Additionally, the haptic controller 876 can provide one or more signals to cause the pressure changing device 867 to inflate one or more bladders 864 in the first textile-based smart garment 800 to a first pressure, and to inflate one or more other bladders 864 in the first textile-based smart garment 800 to a second pressure different from the first pressure. Depending on the number of textile-based smart garments 800 served by the pressure changing device 867 and the number of sacs in the textile-based smart garments, many different inflation configurations can be achieved through one or more signals, and the examples above are not intended to be limiting.

[0229] The textile-based smart garment 800 may include an optional manifold 865 located between a pressure-changing device 867, haptic components 862, and / or other portions of the textile-based smart garment 800. The manifold 865 may include one or more valves (not shown) that pneumatically couple each haptic component 862 to the pressure-changing device 867 via fittings. In some embodiments, the manifold 865 communicates with a controller 875, and the controller 875 controls one or more valves of the manifold 865 (e.g., the controller generates one or more control signals). The manifold 865 is configured to switchably couple the pressure-changing device 867 to one or more haptic components 862 of the textile-based smart garment 800. In some embodiments, one or more textile-based smart garments 800 or other haptic devices may be coupled in a network of haptic devices, and the manifold 865 may distribute fluid between the coupled textile-based smart garments 800.

[0230] In some embodiments, a textile-based smart garment 800 may include a plurality of pressure-changing devices 867, wherein each pressure-changing device 867 is directly pneumatically coupled to a single (or multiple) haptic component 862, rather than using a manifold 865 to pneumatically couple the pressure-changing device 867 to the haptic component 862. In some embodiments, the pressure-changing device 867 and optional manifold 865 may be configured as part of one or more textile-based smart garments 800 (not shown), while in other embodiments, the pressure-changing device 867 and optional manifold 865 may be configured external to the textile-based smart garment 800. In some embodiments, a single pressure-changing device 867 may be shared by multiple textile-based smart garments 800 or other haptic devices. In some embodiments, the pressure-changing device 867 is a pneumatic device, a hydraulic device, a pneumatic-hydraulic device, or some other device capable of adding and removing media (e.g., fluids, liquids, gases) from one or more haptic components 862.

[0231] Memory 878 includes instructions and data, some or all of which may be stored within memory 878 as a non-transitory computer-readable storage medium. For example, memory 878 may include one or more operating systems 879, one or more communication interface modules 881, one or more interoperability modules 884, one or more AR processing modules 885, one or more data management modules 886, and / or one or more specific specification modules 887 for [...], and / or as defined above or regarding Figures 5A to 7B Any other type of data described.

[0232] The memory 878 also includes data 888 that can be used in conjunction with one or more of the applications discussed above. Data 888 may include: device data 890, sensor data 891, and / or data defined above or related to... Figures 5A to 7B Any other type of data described.

[0233] Figures 8A to 8C The different components of the computing system 840 (and the textile-based smart garment 800) shown can be coupled via wired connections (e.g., via a bus). Alternatively, Figures 8A to 8C One or more of the devices shown can be wirelessly connected (e.g., via short-range communication signals).

[0234] Example system for weaving smart textile-based garments Now let's turn our attention to... Figure 9 , Figure 9 A multidimensional knitting machine according to some embodiments is illustrated, configured to produce multidimensional knitted garments in an automated manner (e.g., requiring no manual knitting or other user intervention after the knitting process is initiated, including integrated components that allow electronic components to be automatically woven into multidimensional knitted garments). Multidimensional knitting machine 900 is a computer-controlled and user-programmable garment production device to allow the production of complex knitted structures (e.g., textile-based smart garments 800). Figures 8A to 8CExamples include gloves, tubular fabrics, and fabrics with embedded electronics, complex knitting patterns, special stretching features, unique pattern structures, and multi-thread structures. The multi-dimensional knitting machine 900 includes a first-axis needle bed 902, a second-axis needle bed 908, and an Nth-axis needle bed (indicating there may be more than three needle beds). Each of these needle beds (e.g., needles 904, 910, and 918) is configured to use multiple different types of knitting patterns (e.g., plain weave, rib knit, double rib knit, French terry, wool knit, etc.) based on a programming sequence provided to the multi-dimensional knitting machine 900, and variations of these knits can be used to form a single continuous garment (e.g., a combination of plain weave and French terry, and / or a first variation of plain weave and a second variation of plain weave). In some embodiments, these variations of the knits can be implemented in a single continuous garment without creating seams (e.g., seamless wearable devices can be produced). In some embodiments, the knitting machine is also configured to layer fabrics to create multi-layered wearable structures (e.g., housing one or more electronic components). In some embodiments, each layer in a multi-layered wearable structure may be made of a different fabric, in one example produced using conductive yarns. For example, a multi-dimensional braided capacitive sensor may be produced using a multi-dimensional braiding machine 900, where the first and second layers use different yarns (e.g., coated conductive yarns and uncoated conductive yarns). Each of the multiple needle beds may include multiple fabric spools (e.g., fabric spool 904, fabric spool 912, and fabric spool 920). Each needle bed may use multiple types of fabric spools, allowing for the production of more complex woven structures (also known as garments). In some embodiments, the fabric spools may also include elastic yarns, allowing for the production of stretchable fabrics and / or fabrics with shape memory.

[0235] Each of the aforementioned needle beds may further include one or more non-woven inserts (e.g., non-woven insert 906, non-woven insert 914, and non-woven insert 922) configured to allow the insertion of a non-woven structure into the needle bed, such that the non-woven structure can be woven into the woven structure during the production of the woven structure (e.g., garment). For example, the non-woven structure may include flexible printed circuit boards, rigid circuit boards, wires, structural ribs, sensors (e.g., neuromuscular signal sensors, light sensors, PPG sensors, etc.), etc. In some embodiments, the multi-dimensional knitting machine may (e.g., according to a programmed sequence of knitting instructions provided to the machine) adjust the stitching pattern to accommodate these structures, in some embodiments meaning that these structures are woven into the fabric rather than sewn onto the woven fabric. This (e.g., by reducing protrusions that exert uneven pressure on the wearer's skin) allows for lighter, thinner, and more comfortable garments. In some embodiments, these multi-dimensional knitting machines may also knit the aforementioned woven structures along either or both of a vertical or horizontal axis, depending on the desired characteristics of the woven structure. Weaving along a horizontal axis means that garments will be produced from left to right (e.g., gloves will be produced starting at the little finger and then moving to the ring finger, middle finger, etc.). Vertical sewing means that garments will be produced from top to bottom (e.g., gloves will be produced starting at the top of the highest finger and moving down to the wrist of the glove). Figure 9 (As shown in 928). Regarding the glove example, a reverse manufacturing process is also considered (e.g., the thumb is woven first when knitting in the horizontal direction, and the wrist portion is woven first when knitting in the vertical direction). In some embodiments, the insert can feed the non-woven structure to the knitting machine, or in some other embodiments, the insert is fed by a knitting machine having a non-woven structure. In the latter case, the insert is not integrated into the garment and is discarded. In some embodiments, the insert is not fed at all, but is an integrated component of a multi-dimensional knitting machine that is activated based on a programmed knitting sequence, thereby allowing the non-woven component to be inserted into the knitted structure.

[0236] The multidimensional knitting machine 900 also includes a knitting logic module 924, which is user-programmable to allow users (which can be manufacturing entities that mass-produce wearable structures) to define knitting sequences to produce garments using any of the aforementioned materials, stitching patterns, knitting techniques, etc. As described above, the knitting logic module 924 allows for seamless combination of any of the aforementioned techniques, thereby allowing the creation of unique and complex knitted structures within a single knitting sequence (e.g., the user does not need to remove the knitted structure, then re-insert and reorient it to complete the knitting). The multidimensional knitting machine 900 also includes an insertion logic module 926, which works in conjunction with the knitting logic module 924 to allow the seamless insertion of non-woven components into the knitted structure as it is being knitted together. The insertion logic communicates with the knitting logic to allow adjustment of the knitted fabric based on the position of the inserted non-woven structure. In some embodiments, the user only needs to show where the non-woven structure will be inserted in their mock-up (e.g., at a user interface associated with a multidimensional knitting machine that allows the creation and editing of programmed knitting sequences), and the knitting logic module 924 and the insertion logic module 926 automatically work together to allow the generation of the knitted structure.

[0237] Figure 10 Alternative unfoldable mechanisms for securing smart glasses to a foldable charging case, according to some embodiments, are shown. (See references) Figures 1A to 3 Compared to the described deployable mechanism, the alternative deployable mechanism 1004 includes fewer parts. For example... Figure 10 As shown, a T-shaped rod 1000 is illustrated, which is used to engage a saddle 1006 to hold the smart glasses 1002. In some embodiments, the T-shaped rod 1000 is a continuous sheet of material. This simplified design facilitates manufacturing. Further details of this deployable mechanism will follow in the subsequent... Figures 11 to 12C The relevant sections will describe this.

[0238] Figure 11 The process of a deployable mechanism transitioning between a closed state, an open state, and an open state with smart glasses inserted, according to some embodiments, is illustrated. First pane 1100 shows the deployable mechanism 1102 in its undeployed state, which occurs when a foldable charging case (such as...) is in its undeployed state. Figure 1A and Figure 1B (As shown) when it is in its folded state and not wearing glasses.

[0239] Figure 11The second pane 1102 also shows the deployable mechanism 1102 in its deployed state but not yet holding the smart glasses. As shown, the saddle spring 1104 is configured to force the deployable mechanism 1102 into its deployed state when the foldable charging case is not folded.

[0240] Figure 11 Also shown in the third pane 1106 is the deployable mechanism 1103 in the deployed state, holding the smart glasses 1108 in place. The T-bar 1110 is configured to rotate independently of the saddle 1114 about the pivot point 1112 to provide force on the smart glasses 1108 (e.g., along the nose pad) when the smart glasses 1108 slides in and locks in place (e.g., coupled to spring pins 1116A and 1116B (not shown) via the charging contacts 1118A and 1118B of the smart glasses 1108).

[0241] In the third pane 1106, when the smart glasses 1108 act on the T-bar 1110, the T-bar 1110 moves away from the saddle 1114. When the smart glasses 1108 cease to act on the T-bar 1110, the T-bar 1110 returns to its initial position, achieved by a spring 1120 located within the saddle 1114. In other embodiments described below, the spring 1120 may be replaced by a magnet, a torsion spring, and / or a leaf spring. In some embodiments, the movement of the T-bar 1110 may be controlled by one or more of a spring bar, a coil spring, a leaf spring, and a magnet.

[0242] Figures 12A to 12C Three types of deployable mechanisms according to some embodiments are shown, which are used to control the movement of parts that hold smart glasses. While the components described herein are consistent with references... Figure 10 and Figure 11 The components described are used together, but these components also apply to the reference. Figures 1A to 1B and Figure 3 The part described.

[0243] Figure 12A A first deployable mechanism 1200 is shown, which is used to control the movement of the portion holding the smart glasses. Viewed from top to bottom... Figure 12AA T-bar 1202 for holding the smart glasses is shown. The T-bar 1202 is configured to partially hold the smart glasses, and its movement is primarily controlled by a magnet 1210. In some embodiments, the T-bar 1202 is manufactured using metal injection molding (MIM), and the T-bar 1202 may also include an optional derin overmolded portion surrounding an interface portion 1203 that contacts the nose pad of the smart glasses. A saddle 1204 is coupled to the T-bar 1202 such that the through-hole 1206 of the T-bar 1202 and the through-hole 1208 of the saddle 1204 are concentric. In some embodiments, the saddle 1204 is made of polycarbonate (PC).

[0244] Figure 12A A magnet 1210 is shown coupled to a magnet carrier 1212 positioned between a saddle 1204 and a saddle cover 1214. In some embodiments, the magnet carrier is made of stainless steel or other suitable material that does not deform under magnetic load. In some embodiments, the magnet carrier 1212 and the spring 1216 include corresponding through holes 1218 and 1220 concentric with the through hole 1206 of the T-bar 1202 and the through hole 1208 of the saddle 1204. In some embodiments, the saddle cover 1214 is made of the same material as the saddle 1204 (which may be made of PC).

[0245] Figure 12A The image also shows a saddle spring 1216, configured to force the saddle 1204, saddle cover 1214, magnet 1210, magnet carrier 1212, and T-bar 1202 upward about their respective through-positions. The saddle 1204, magnet carrier 1212, T-bar 1202, and saddle spring 1216 are rotatably mounted to a pin 1222, which is coupled to a bracket 1224, which is secured to a foldable charging case. In some embodiments, the saddle spring 1216 is one of a leaf spring, a torsion spring, or a coil spring. In some embodiments, the saddle spring 1216 is made of stainless steel. In some embodiments, the pin 1222 is made of stainless steel, and the bracket 1224 is made of MIM (Metal Ink).

[0246] Figure 12B A second deployable mechanism 1226 is shown, which is used to control the movement of the portion holding the smart glasses. Viewed from top to bottom... Figure 12BA glasses-holding T-bar 1228 is shown, configured to partially hold the smart glasses, and movement of the T-bar 1228 is primarily controlled by saddle springs 1242 and 1234. In some embodiments, the T-bar 1228 is made of MIM (optionally colored black) and may also include an optional overmolded portion surrounding an interface portion that contacts the nose pad of the smart glasses. In some embodiments, the overmolded portion may include POM plastic (optionally colored black). A saddle 1232 is coupled to the T-bar 1228 such that the through-hole 1233 of the T-bar 1228 and the through-hole 1236 of the saddle 1232 are concentric. In some embodiments, the saddle 1232 is made of polycarbonate (PC).

[0247] Figure 12B A spring 1234 (e.g., a torsion spring) is shown, coupled to a T-bar 1228 and forcing the T-bar 1228 downward to primarily maintain contact with the saddle 1232. The spring 1234 performs the same operation as the magnet described with reference to the first deployable mechanism 1200. In some embodiments, the spring 1234 is a torsion spring, a helical spring, or a leaf spring. In some embodiments, the spring 1234 is mounted to a pin 1237 via a through-hole 1239, which is concentric with the through-hole 1238 of the T-bar 1228 and the through-hole 1233 of the saddle 1232. In some embodiments, a saddle cover 1240 is coupled to the saddle 1232, and a rechargeable flexible printed circuit (FPC) 1241 is housed inside. Although the rechargeable FPC 1241 is only... Figure 12B As shown in the image, but Figure 12A The deployable mechanism also includes a charging FPC in a similar location. In some embodiments, the saddle cover 1240 is made of the same material as the saddle 1232 (which may be made of PC).

[0248] Figure 12B The diagram also shows a saddle spring 1242, configured to directly force the saddle 1232 and saddle cover 1240 upwards about their respective through-hole positions. The saddle spring 1242 further indirectly forces the T-bar 1228 upwards, but does not act directly on the T-bar. The saddle spring 1242 has a greater spring force than the spring 1234, thus allowing the saddle to be forced upwards to its open state, even though the spring 1234 acts on the saddle. The T-bar 1228 has a greater range of motion than the saddle 1232, which allows the spring... The T-bar 1228 has a greater range of motion than the saddle 1232 (e.g., the rotation angle of the T-bar 1228 around the pin 1237 is greater than that of the saddle 1232), therefore the T-bar 1228 can extend further into the extension region than the saddle 1232. In this extension region, when the T-bar is not in contact with the saddle 1232, the saddle spring 1242 no longer acts indirectly on the T-bar. However, in the extension region, the spring 1234 acts solely on the T-bar to force it downward. In some embodiments, the T-bar 1228 can extend up to 45 degrees further than the saddle 1232.

[0249] In some embodiments, the spring 1234 is rotatably mounted to the pin 1237, and optionally a bushing 1245 is included on the pin 1237. Due to spring force and packaging limitations, the bushing 1245 is used to accommodate springs of different sizes.

[0250] The saddle 1232, T-bar 1228, and saddle spring 1242 are rotatably mounted to pin 1237, which is coupled to bracket 1244, which is secured to the foldable charging case. In some embodiments, the saddle spring 1242 is a leaf spring, a torsion spring, or a coil spring. In some embodiments, the saddle spring 1242 is made of stainless steel. In some embodiments, pin 1236 is made of stainless steel, and bracket 1224 is made of MIM (Metal Ink). In some embodiments, spring 1234 is also rotatably mounted to pin 1236.

[0251] Figure 12C A third deployable mechanism 1246 is shown, which is used to control the movement of the portion holding the smart glasses. Viewed from top to bottom... Figure 12C A T-shaped rod 1248 is shown, configured to partially hold the smart glasses, and movement of the T-shaped rod 1248 is primarily controlled by a leaf spring 1250 integral with the T-shaped rod 1248. In some embodiments, the T-shaped rod 1248 is made of sheet metal and may also include an optional derin overmolding surrounding an interface portion that contacts the nose pad of the smart glasses. A saddle 1252 is coupled to the T-shaped rod 1248 such that the through-hole 1254 of the T-shaped rod 1248 and the through-hole 1256 of the saddle 1252 are concentric. In some embodiments, the saddle 1256 is made of polycarbonate (PC).

[0252] T-shaped rod 1248 surrounds saddle 1252, such that integrated leaf spring 1250 can use saddle 1252 as a fulcrum to return to its default position, i.e., T-shaped rod 1248 mainly remains in contact with saddle 1252 when not subjected to the insertion of smart glasses (e.g., the main surface of T-shaped rod is in contact with the main surface of saddle).

[0253] Figure 12CAlso shown is a saddle cover 1258 that covers a portion of the T-shaped bar during assembly. In some embodiments, the saddle cover 1258 is made of the same material as the saddle 1252 (which may be made of PC).

[0254] Figure 12C The image also shows a saddle spring 1260, configured to force the saddle 1252, saddle cover 1258, and T-bar 1248 upward about their respective through-positions. The saddle 1252, T-bar 1248, and saddle spring 1260 are rotatably mounted to a pin 1262, which is coupled to a bracket 1264, which is secured to a foldable charging case. In some embodiments, the saddle spring 1260 is a leaf spring, a torsion spring, or a coil spring. In some embodiments, the saddle spring 1260 is made of stainless steel. In some embodiments, the pin 1262 is made of stainless steel, and the bracket 1264 is made of MIM (Metal Ink).

[0255] Figure 13 This illustration shows how a foldable charging case, according to some embodiments, utilizes strategically placed magnets to allow the foldable charging case to "automatically" open when partially opened by a user. First pane 1300 shows a force 1302 present on the wing (side) 1304 of the foldable charging case 1306, which holds the wing 1304 in its folded position. In some embodiments, this force is maintained by the top portion 1305 when it is folded onto the wing 1304. When no force is applied to the wing 1304, the wing moves to a vertical position via a hinge, as shown in second pane 1311. In some embodiments, the top portion 1305 is held in place by another magnet 1307 and one or more corresponding magnets located in different areas to keep the foldable charging case folded and the wing 1304 in its folded position. The magnetic force between another magnet 1307 and one or more corresponding magnets is greater than the magnetic force of one or more magnets 1310 in the wing 1304 and magnet 1312 in the bottom portion 1308.

[0256] The second pane 1311 illustrates that once the foldable charging case begins to enter the open state, one or more magnets 1310 in the wings are attracted by magnets 1312 in the bottom portion 1308 to force the foldable charging case 1306 into a fully open position. In the open position, the wings 1304 are perpendicular to the bottom portion 1308. When the case is to be folded, the opposite interaction occurs, where a force is applied to the wings 1304 to push them back to be substantially parallel to the bottom portion 1308, and the portion 1305 is then configured to fold to secure it in place. In some embodiments, another side portion exists in the opposite position of the bottom portion and is configured to function in a similar but mirrored manner to the wings 1304. In some embodiments, these magnets are placed at the edge of the surface, but may also be placed in any suitable position to allow the case to self-assemble. In some embodiments, other components, including springs, may be used to induce self-assembly, which may optionally work in conjunction with the magnets.

[0257] Figure 14 Cross-sectional views 1400A and 1400B are shown of a wing 1402 that rotates about a bottom portion 1404 according to some embodiments. The transition between cross-sectional views 1400A and 1400B shows a fabric cover 1406 moving together with a hinged region 1408 and maintaining coverage of the hinged region 1408 throughout its range of motion.

[0258] Any data collection performed by the devices described herein and / or any device configured to perform the different embodiments described above with reference to any of the illustrations (hereinafter referred to as "devices") is conducted in a manner that complies with all applicable privacy regulations and with the user's consent. Users may choose to allow the devices to collect data, or to restrict or refuse data collection by the devices. Users can opt in or out of any data collection at any time. Furthermore, users may choose to request the deletion of any collected data.

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

[0260] The terminology used herein is for the purpose of describing particular embodiments only and is 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 the plural forms unless the context clearly indicates otherwise. It will also be understood that the term “and / or” as used herein refers to and includes any and all possible combinations of one or more of the associated listed items. It will also be understood that, as used in this specification, the terms “comprising” and / or “including” specify the presence of the stated features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0261] As used herein, the term "if" can be interpreted, depending on the context, as meaning "when" or "once" or "in response to determination" or "according to determination" or "in response to detection" when the stated prerequisite is true. Similarly, depending on the context, the phrases "if determination [the stated prerequisite is true]" or "if [the stated prerequisite is true]" or "when [the stated prerequisite is true]" can be interpreted as meaning "once determination" or "in response to determination" or "according to determination" or "once detection" or "in response to detection" when the stated prerequisite is true.

[0262] For illustrative purposes, the foregoing description has been illustrated 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. Many modifications and variations are possible in light of the above teachings. The embodiments were chosen and described in order to best explain the principles of operation and practical application, thereby enabling others skilled in the art to implement them.

Claims

1. A foldable charging case for smart glasses, the foldable charging case comprising: The foldable charging case has a foldable component configured to operate in at least two states, the at least two states including: Partially defining the reduced state of the first internal volume, and The unfolded state of a second internal volume that is larger than the first internal volume is partially defined, and the second internal volume is configured to accommodate smart glasses; A deployable mechanism configured to contact the nose bridge portion of smart glasses, and configured to operate in at least two states, the at least two states of the deployable mechanism including: The unfolded state that occurs when the foldable component of the foldable charging case is in the folded state, and The unfolded state is the state that occurs when the foldable component of the foldable charging case is in the undisturbed state, wherein the unfoldable mechanism is configured to contact the nose bridge portion of the smart glasses in the unfolded state.

2. The foldable charging case for smart glasses according to claim 1, wherein the foldable charging case comprises: Another foldable component is located on the opposite side of the foldable charging case relative to the foldable component, wherein the shape of the other foldable component is a mirror image of the foldable component.

3. The foldable charging case for smart glasses according to claim 1 or 2, wherein the foldable charging case comprises: A third foldable component is perpendicular to the foldable component, and the third foldable component is configured to cause the foldable component to enter the unfolded state when the third foldable component enters the unfolded state; preferably, the unfoldable mechanism is configured to enter the unfolded state in response to the third foldable component entering the unfolded state.

4. The foldable charging case for smart glasses according to any of the preceding claims, wherein, The deployable mechanism includes a spring, and the spring is compressed when the foldable component is in the folded state and uncompressed when the foldable component is in the unfolded state.

5. The foldable charging case for smart glasses according to any of the preceding claims, wherein, The deployable mechanism includes a retaining bracket configured to engage with the nose pad of the smart glasses to hold the smart glasses within the foldable charging case; preferably, the deployable mechanism includes a nose bridge interface portion including one or more charging contacts, and the nose bridge is configured to contact the smart glasses.

6. A foldable charging case for smart glasses according to any one of the preceding claims, wherein, The deployable mechanism is partially covered by a cover.

7. A foldable charging case for smart glasses according to any one of the preceding claims, wherein, The foldable charging case includes a battery and one or more electrical components configured to charge the smart glasses.

8. A foldable charging case for smart glasses according to any one of the preceding claims, wherein, The folded state has a rectangular cross-sectional shape, while the unfolded state has a triangular cross-sectional shape.

9. A foldable charging case for smart glasses according to any one of the preceding claims, wherein, The smart glasses mentioned are augmented reality glasses.

10. A foldable charging case for smart glasses according to any one of the preceding claims, wherein, The foldable charging case includes one or more magnets to maintain the shape of the folded state and the unclamped state.

11. A system comprising at least: (i) a foldable charging case and (ii) smart glasses, wherein the foldable charging case includes: The foldable charging case has a foldable component configured to operate in at least two states, the at least two states including: Partially defining the reduced state of the first internal volume, and The unfolded state of a second internal volume that is larger than the first internal volume is partially defined, and the second internal volume is configured to accommodate smart glasses; A deployable mechanism configured to contact the nose bridge portion of smart glasses, and configured to operate in at least two states, the at least two states of the deployable mechanism including: The unfolded state that occurs when the foldable component of the foldable charging case is in the folded state, and The unfolded state is the state that occurs when the foldable component of the foldable charging case is in the undisturbed state, wherein the unfoldable mechanism is configured to contact the nose bridge portion of the smart glasses in the unfolded state.

12. The system according to claim 11, wherein, The foldable charging case includes another foldable component located on the opposite side of the foldable component relative to the foldable component, wherein the other foldable component is a mirror image of the foldable component.

13. The system according to claim 11 or 12, wherein, The foldable charging case includes another foldable component perpendicular to the foldable component, and the other foldable component is configured to cause the foldable component to enter the unfolded state when the other foldable component enters the unfolded state.

14. The system according to any one of claims 11 to 13, wherein, The deployable mechanism includes a retaining bracket, which is configured to engage with the nose pad of the smart glasses to hold the smart glasses within the foldable charging case.

15. A method for charging smart glasses, the method comprising: The smart glasses are housed in a foldable charging case according to any one of claims 1 to 10; as well as In response to receiving the smart glasses at the unfoldable mechanism, charge is transferred from the foldable charging case to the smart glasses.

Images