Augmented reality eyeglass temple arm components, arrangements, and assemblies, and systems and methods of use

Abstract

An augmented reality (AR) glasses temple arm is disclosed. An example temple arm includes a curved temple arm housing configured to couple to the frame of the AR glasses. The curved temple arm housing has a head-shaped bend to conform to a portion of the user's head. The curved temple arm housing includes a set of electronic components coupled within the head-shaped bend of the curved temple arm housing, and an input device configured to control one or more electronic components positioned within the frame of the AR glasses. The set of electronic components includes a speaker, a front battery unit, and a rear battery unit. The speaker is positioned near the user's ear and between the front battery unit and the rear battery unit.

Description

Cross-reference to related applications

[0001] This application claims the benefit and priority of U.S. Provisional Patent Application No. 63 / 601,698, filed November 21, 2023; U.S. Provisional Patent Application No. 63 / 567,384, filed March 19, 2024; and U.S. Non-Provisional Patent Application No. 18 / 919,317, filed October 17, 2024. Technical Field

[0002] This application generally relates to temple arms for augmented reality glasses, including but not limited to techniques for forming temple arms for augmented reality glasses and for coupling electronic components within temple arms for augmented reality glasses. Background Technology

[0003] Existing augmented reality (AR) glasses house most of their electronic components within the frame and / or front display. This placement is challenging due to the compact form factor of these AR glasses units. Specifically, the physical space for electronic components (such as power supplies and other components) is limited. This placement further complicates weight, balance, and / or temperature control. For example, the weight of the AR glasses may be concentrated on the user's face, reducing comfort and / or increasing the likelihood of the glasses being knocked off or falling from the user's face. Furthermore, the frame of the AR glasses may experience high temperatures when all electronic components are active, potentially causing discomfort if worn for extended periods.

[0004] Therefore, it is necessary to solve one or more of the challenges mentioned above. A brief summary of the solutions to these problems is described below. Summary of the Invention

[0005] According to one aspect, a temple arm is provided, the temple arm including a curved temple arm housing and an input device, the curved temple arm housing being configured to be coupled to the frame of augmented reality (AR) glasses, the curved temple arm housing having a head-shaped curvature to conform to a portion of a user's head, wherein the curved temple arm housing includes: a set of electronic components coupled within the head-shaped curvature of the curved temple arm housing, the set of electronic components including a speaker, a front battery unit and a rear battery unit, wherein the speaker is positioned near the user's ear and between the front battery unit and the rear battery unit; the input device is configured to control one or more electronic components positioned within the frame of the AR glasses.

[0006] In one embodiment, the curved temple arm housing may further include a hinge seat located at the front end of the curved temple arm housing adjacent to the front battery unit, and the temple arm may further include a hinge assembly coupled to the curved temple arm housing via the hinge seat, wherein the hinge assembly is configured to couple the curved temple arm housing to the frame of the AR glasses, and the hinge assembly includes one or more channels for routing one or more wires to communicatively couple the set of electronic components to electronic components located within the frame of the AR glasses.

[0007] This set of electronic components can power the electronic devices within the frame of the glasses.

[0008] The hinge assembly may include a plurality of alignment ribs configured to align the hinge assembly with the hinge seat for coupling. The plurality of alignment ribs may define a predetermined gap for receiving adhesive.

[0009] The group of electronic components may also include a microphone positioned near the hinge assembly and the front battery cell.

[0010] The input device may be a power button located at the end of the curved temple arm housing, which is adjacent to the rear battery unit.

[0011] The input device may include a camera button located at the front end of the curved temple arm housing, which is adjacent to the front battery unit.

[0012] The input device may include a privacy slider positioned at the front end of the curved temple arm housing, which is adjacent to the front battery cell.

[0013] The curved temple arm housing may include multiple ribs that form a planar mounting surface for at least one of the group of electronic components.

[0014] The curved temple arm housing may include a plurality of alignment points, each of which is located at a different corner of the planar mounting surface. These alignment points may identify locations for coupling at least one of the group of electronic components to the curved temple arm housing.

[0015] The temple arm may also include one or more ear pads, wherein the one or more ear pads are configured to be adjacent to the speaker and coupled to the curved temple arm housing.

[0016] The set of electronic components may also include a printed circuit board (PCB) for transmitting data to and from the microphone and / or speaker. The PCB may be shaped to fit within the bend of the head shape of the curved temple arm housing.

[0017] The group of electronic components may also include one or more of the following: proximity sensor; temperature sensor; and / or inertial measurement unit (IMU).

[0018] According to another aspect, there is provided augmented reality glasses, which include: temple arms of the type described above; and an input device configured to control one or more electronic components positioned within the frame of the AR glasses.

[0019] According to another aspect, a manufacturing method is provided, the manufacturing method comprising: Provides a temple arm of the type described above; and a frame that couples the temple arm to the augmented reality (AR) glasses.

[0020] The systems and methods disclosed herein can provide one or more temple arms that house one or more electronic devices or components in a lightweight, small-shape element (e.g., eyeglasses or eyeglass temples). The temple arms may be water-resistant (or waterproof) and may provide structural support to protect one or more electronic devices from impacts (e.g., drops) and / or vibrations. The methods, systems, and devices described herein are configured to house one or more electronic components within the temple arms of a head-mounted device (e.g., augmented reality glasses). By placing the electronic components within the temple arms, the methods, systems, and devices described herein can evenly distribute the weight of the augmented reality glasses, preventing the weight from concentrating on a single part of the user's face (e.g., the nose and eyes). Furthermore, by evenly distributing the weight of the augmented reality glasses, the methods, systems, and devices described herein can allow the augmented reality glasses to be balanced, keeping them in place and providing greater comfort to the user when worn (e.g., preventing the augmented reality glasses from shifting or falling off the user's face when the user moves or when the user and / or the augmented reality glasses are unintentionally bumped or touched). Furthermore, the temple arms feature a curved temple arm housing, which enhances user comfort and allows for a more even distribution of components within the temple arm. The temple arms and their configuration will be discussed in detail below.

[0021] The methods, systems, and apparatus described herein can improve thermal control of augmented reality (AR) glasses by incorporating one or more electronic components within the temple arms. Specifically, the methods, systems, and apparatus described herein can distribute heat generated by the electronic components across the AR glasses (rather than concentrating it in a single location, such as the frame), which can enable higher thermal design power or better control over the temperature of the electronic components.

[0022] This article describes an example temple arm configured to couple with augmented reality glasses. The example temple arm includes a curved temple arm housing configured to couple to the frame of the augmented reality glasses. The curved temple arm housing has a head-shaped bend to hug a portion of the user's head. More specifically, the curved temple arm housing conforms to the user's head to increase the amount of surface area and pull the front frame towards the wearer's face. The curved temple arm housing includes a set of electronic components coupled within the head-shaped bend of the curved temple arm housing, including a speaker, a front battery unit (similar to power supply 170); Figures 1A to 3B The speaker is positioned near the user's ear and between the front and rear battery units, and the input device is configured to control one or more electronic components positioned within the frame of the augmented reality glasses.

[0023] The first example temple arm has been outlined above; now, the second example temple arm will be outlined.

[0024] Another example temple arm configured to couple with augmented reality glasses includes one or more batteries, a speaker, one or more sensors, an externally oriented temple arm housing, and a skin-oriented temple arm cover configured to couple with the externally oriented temple arm housing. The externally oriented temple arm housing includes: a head-shaped bend that conforms to (or encircles) a portion of the user's head when the temple arm is worn; a cavity opposite the externally oriented surface of the externally oriented temple arm housing; and one or more slots for receiving adhesive. The cavity is configured to hold one or more batteries, a speaker, and one or more sensors. The skin-oriented temple arm cover includes a corresponding head-shaped bend and one or more protrusions that conform to a portion of the user's head when the temple arm is worn. When the skin-oriented temple arm cover is coupled to the externally oriented temple arm housing, the skin-oriented temple arm cover (i) surrounds the cavity, and (ii) one or more protrusions engage one or more slots, forming a mechanical bond with the adhesive received within one or more slots. The grooves and protrusions are used to effectively increase the available adhesive surface area between the shell facing the external environment and the shell facing the skin, which is not possible with clamshell adhesive joints.

[0025] The second example temple arm has been outlined above; now, an example method for forming a temple arm will be outlined.

[0026] Another example of a temple arm configured to couple with augmented reality glasses includes: a curved temple arm housing having a head-shaped bend to conform to a portion of a user's head; multiple ribs; and a set of electronic components coupled within the head-shaped bend of the curved temple arm housing. The multiple ribs form flat surfaces for coupling one or more electronic components and include one or more identifiable markings for guiding the placement of one or more electronic components. The set of electronic components includes a speaker, a front battery unit, and a rear battery unit. The multiple ribs define areas for placing at least one front battery unit or rear battery unit, such that the position of the set of electronic components is predetermined.

[0027] The third example temple arm has been outlined above; now, example methods for forming temple arms will be outlined.

[0028] An example method of forming a temple arm includes providing a temple arm housing facing the external environment. The method includes coupling a set of electronic components within a cavity of the temple arm housing facing the external environment, and coupling a hinge assembly to one end of the temple arm housing facing the external environment. The method also includes applying an adhesive to a portion of the cavity of the temple arm housing facing the external environment, and attaching a temple arm housing cover facing the temporal region to the temple arm housing facing the external environment. The temple arm housing cover facing the temporal region and the temple arm housing facing the external environment encapsulate a portion of the hinge assembly and a set of electronic components.

[0029] 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.

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

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

[0032] Figures 1A to 1H A temple arm and one or more temple arm components according to some embodiments are shown.

[0033] Figure 2 A skin-facing temple cover is shown according to some embodiments.

[0034] Figure 3A and Figure 3B A cross-section of a temple arm according to some embodiments is shown.

[0035] Figure 4 A flowchart of a method for forming a mirror temple arm according to some embodiments is shown.

[0036] Figure 5A and Figure 5B An example artificial reality system according to some embodiments is shown.

[0037] Figures 6A to 6B An example wrist-worn wearable device according to some embodiments is shown.

[0038] Figures 7A to 7C An example head-mounted wearable device according to some embodiments is shown.

[0039] Figure 8A and Figure 8B An example handheld intermediate processing device according to some embodiments is shown.

[0040] 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

[0041] 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 only 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.

[0042] Embodiments of this disclosure may include various types of artificial reality systems or various embodiments of artificial reality systems, or a combination of various types of artificial reality systems or various embodiments of artificial reality systems. 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 make an air swipe gesture to cause a song-providing API to skip a song, such as one provided for playback 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 marked augmented reality environments, unmarked augmented reality environments, location-based augmented reality environments, and projection-based augmented reality environments); mixed reality; and other types of mixed reality environments.

[0043] Artificial reality content can include entirely generated content or generated content combined with captured (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 may also be associated with applications, products, accessories, services, or some combination thereof for, for example, creating content in artificial reality and / or otherwise using artificial reality (e.g., performing activities in artificial reality).

[0044] 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 the combined movement 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 made in open space in 3D space and does not contact a surface, object, or electronic device. More generally, the following surface contact gestures (contacts on surfaces, objects, user body parts, or electronic devices) can also be envisioned: in these surface contact gestures, contact (or the intention to contact) is detected at the surface (e.g., a single or double 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 (e.g., proximity sensors, time-of-flight sensors, sensors from 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)).

[0045] As described herein, temple arms are configured to be coupled to the frame of augmented reality glasses and to support the weight of the augmented reality glasses when worn by a user. Specifically, the temple arms rest on the user's ears and attach the augmented reality glasses to the user's head. The methods and apparatus described herein include descriptions of one or more components included in the temple arms and the formation of the temple arms. As described herein, the temple arms allow one or more electronic components to move from the frame of the augmented reality glasses to the temple arms. Furthermore, the temple arms are lightweight, water-resistant (or waterproof), and impact-resistant.

[0046] Figures 1A to 1H A temple arm and one or more temple arm components are shown according to some embodiments. Temple arm 100 ( Figure 1G and Figure 1HThe device is configured to be (mechanically) coupled to the frame of the augmented reality glasses. Specifically, the frame of the augmented reality glasses is configured to be coupled to two temple arms 100 (e.g., a first temple arm and a second temple arm opposite the first temple arm). The temple arms 100 and the frame of the augmented reality glasses include their respective electronic components (e.g., referred to below). Figures 7A to 7C (One or more electronic components described) are electrically coupled and / or communicationally coupled when the temple arm 100 and the frame of the augmented reality glasses are coupled. The first temple arm, the second temple arm, and the frame of the augmented reality glasses are generally referred to as the augmented reality glasses when they are coupled.

[0047] See below for reference Figures 1A to 1H Each temple arm 100 is formed by a temple arm housing 105 facing the external environment and a temple arm cover 190 facing the skin. The temple arm housing 105 facing the external environment may be a curved temple arm housing 110 having a head-shaped bend to (e.g., when the temple arm 100 is worn) conform to a portion of the user's head. The head-shaped bend of the curved temple arm conforms to the user's head to increase the amount of surface area and pull the front frame toward the wearer's face. The curved temple arm housing 110 (used synonymously with the temple arm housing 105 facing the external environment) is further configured to accommodate one or more components as described below. Differences (where present) between the temple arms 100 coupled to the frame of the augmented reality glasses are identified below.

[0048] Figure 1A A cavity 113 of a curved temple arm housing 110 is shown. The cavity 113 is opposite the externally facing surface of the curved temple arm housing 110. More specifically, the cavity 113 is a portion of the curved temple arm housing 110 that is not exposed to the external environment and does not contact the user's skin. The cavity 113 is configured to hold a set of electronic components, such as one or more power sources 170 (e.g., batteries, battery packs, or battery cells), one or more speakers 145, one or more microphones 150, and one or more sensors (e.g., inertial measurement unit (IMU) 153, proximity sensor 155, temperature sensor 151, etc.). Different temple arms 100 may have the same or different sets of electronic components. References below... Figures 1B to 1F The description includes different electronic components and / or different locations of electronic components within a set of electronic components. Cavity 113 may also include audio channel 121, deck mount 122, one or more pluralities of ribs 117, and one or more alignment points 127, each of which is discussed in detail below.

[0049] Audio channel 121 may be a speaker port (e.g., a direct port) adjacent to ear position 125 and located at the bottom of temple arm 100, which allows for speaker 145 ( Figure 1C The audio data generated is directly presented to the user. In some embodiments, an additional audio channel 119 is located on the side of the curved temple arm housing 110, allowing the audio data generated by the speaker 145 to be directly presented to the user. Figure 1C The representation of the audio data generated by the speaker 145 is presented on the exterior of the temple arm 100. Alternatively, in some embodiments, an additional audio channel is located on top of the curved temple arm housing 110 (not shown). Ear position 125 is the approximate location of the temple arm 100 where the user's ear supports the temple arm 100 when the augmented reality glasses are worn. Audio channel 121 allows the representation of the audio data generated by the speaker 145 to be presented on the exterior of the temple arm 100 and directed to the user's ear. In some embodiments, audio channel 121 and additional audio channel 119 are individually configured to be coupled to the temple arm 100 via an adhesive (e.g., pressure-sensitive adhesive or other glue) ring, as described in detail below.

[0050] One or more ribs 117 form a planar mounting surface for one or more electronic components in a group of electronic components. The planar mounting surface formed by one or more ribs 117 provides a substantially uniform flat surface for coupling electronic components to the curved temple arm housing 110. For example, a first plurality of ribs 117a forms a first planar mounting surface for coupling a first power supply 170a to the curved temple arm housing 110, a second plurality of ribs 117b forms a second planar mounting surface for coupling a second power supply 170b to the curved temple arm housing 110, and a third plurality of ribs 117c forms a third planar mounting surface for coupling additional circuitry (e.g., a rigid flex printed circuit assembly (RFPCA) and included components) to the curved temple arm housing 110. In some embodiments, RFPCA 160 ( Figure 1D The electronic components are coupled to one or more ribs 117, and other electronic components are coupled to the curved temple arm housing 110 via RFPCA 160. For example, as... Figure 1D and Figure 1EAs shown, RFPCA 160 is coupled to a first plurality of ribs 117a, a second plurality of ribs 117b, and a third plurality of ribs 117c, and a first power supply 170a and a second power supply 170b are coupled to RFPCA 160 (e.g., on top of RFPCA 160). In some embodiments, one or more ribs 117 form planar mounting surfaces for specific electronic components (e.g., power supply 170 and / or RFPCA 160) in a set of electronic components. One or more ribs 117 may form the same or different planar mounting surfaces. For example, planar mounting surfaces may have the same or different shapes, sizes, surface areas, etc. Similarly, one or more ribs 117 may be the same or different. For example, the ribs 117 may have the same or different rib spacing, rib height, rib orientation, rib thickness, etc. In some embodiments, the configuration of one or more ribs 117 (e.g., rib height, rib thickness, rib spacing, etc.) is based on the curvature of the curved temple arm housing 110, such that planar mounting surfaces can be formed within the cavity 113. In some embodiments, each of the plurality of ribs 117 has a predetermined size. For example, the plurality of ribs 117 may have a predetermined height (e.g., 0.6 mm (+ / - 0.02 mm)) and a predetermined width (0.8 mm (+ / - 0.02 mm)).

[0051] Multiple ribs 117 can be used to guide the placement of one or more electronic components from a group of electronic components. Specifically, the multiple ribs 117 can form a visible area on which at least one electronic component is placed. For example, the multiple ribs 117 can be positioned such that a power supply 170 is positioned at the rear and front of the curved temple arm housing 110. Similarly, the multiple ribs 117 can be positioned such that a speaker 145 is positioned between the power supplies 170, and the speaker is adjacent to the ear position 125. For example, see the following reference... Figure 1E The first power source 170a is positioned on a first plurality of ribs 117a at the rear of the curved temple arm housing 110, and the second power source 170b is positioned on a second plurality of ribs 117b at the front of the curved temple arm housing 110, with the first plurality of ribs 117a and the second plurality of ribs 117b at least spaced apart by the width of the speaker 145 (or the distance to the ear position 125). In some embodiments, the plurality of ribs 117 are positioned based on the size of the curved temple arm housing 110 and / or the configuration of the temple arm 100. Additionally, the plurality of ribs 117 allow for precise and consistent manufacturing of the temple arm 100 due to the limited space within the temple arm 100, the size of a set of electronic components, and / or the cooling requirements of that set of electronic components.

[0052] One or more alignment points 127 are associated with one or more of one or more ribs 117. In some embodiments, each alignment point 129 of the plurality of alignment points 127 is located at a different corner of the corresponding plurality of ribs 117 (or planar mounting surfaces). For example, a first plurality of alignment points 127a is associated with a first plurality of ribs 117a, and each alignment point 129a and 129b is located at a corresponding corner of the first plurality of ribs 117a; and a second plurality of alignment points 127b is associated with a second plurality of ribs 117b, and each alignment point 129c to 129f is located at a corresponding corner of the second plurality of ribs 117b. The plurality of alignment points 127 are used to identify locations for coupling at least one of a set of electronic components to the curved temple arm housing 110. In particular, the plurality of alignment points 127 serve as markers or identifiers used by a computer vision system to identify the location where at least one electronic component is placed. In other words, the computer vision system can detect one or more alignment points 127 and use these alignment points to guide the placement of at least one electronic component (e.g., power supply 170 (e.g., battery cell)). The multiple alignment points 127 are used to place and align the electronic component within 50 micrometers of a predetermined location. In some embodiments, a user (e.g., a manufacturer, repairman, etc.) can visually inspect the position of the alignment points to guide their placement of at least one electronic component.

[0053] While the above examples describe the use of multiple ribs 117 or multiple alignment points 127 to place at least one electronic component, combinations of multiple ribs 117 and multiple alignment points 127 can be used to guide the placement of a group of electronic components. Similarly, other portions of the curved temple arm housing 110 can be used alone or in combination with multiple ribs 117 and / or multiple alignment points 127 to guide the placement of a group of electronic components. For example, one or more slots 120 and / or one or more protruding inserts 115 can be used alone or in combination with multiple ribs 117 and / or multiple alignment points 127 to guide the placement of a group of electronic components.

[0054] The curved temple arm housing 110 includes one or more grooves 120 configured to receive adhesive 185. After receiving adhesive 185 in one or more grooves 120, one or more grooves 120 are further configured to receive one or more insert ribs 195 of the skin-facing temple arm cover 190. Figure 1F This allows adhesive 185 to bond one or more insert ribs 195 of the skin-facing temple cover 190 to one or more grooves 120. See below for reference. Figure 1F , Figure 3A and Figure 3BAs discussed, adhesive 185 is configured to secure the skin-facing temple cover 190 to the external environment-facing temple housing 105. Additionally, the adhesive, upon curing, is configured to form an airtight seal at the joint between the skin-facing temple cover 190 and the external environment-facing temple housing 105. In some embodiments, the curved temple housing 110 includes a predetermined number of slots 120 (e.g., at least one slot, at least four slots, at least seven slots, etc.). For example, as... Figure 1A As shown, the curved temple arm housing 110 includes at least six slots 120a to 120f.

[0055] The curved temple arm housing 110 includes one or more protruding inserts 115. One or more protruding inserts 115 are configured to receive one or more snap-fit ​​protrusions 197 (e.g., protrusions with hooks at one end) of the skin-facing temple arm cover 190. Figure 1F When the snap-fit ​​protrusion 197 is received by the protrusion insert 115, the snap-fit ​​protrusion 197 couples to a portion of the curved temple arm housing 110, thereby mechanically securing the skin-facing temple arm cover 190 to the external-facing temple arm housing 105. When the adhesive 185 cures, the snap-fit ​​protrusion 197 retains the skin-facing temple arm cover 190 coupled to the external-facing temple arm housing 105. The coupling of one or more snap-fit ​​protrusions 197 with one or more protrusion inserts 115 and / or the curved temple arm housing 110 will be referred to below. Figure 1F , Figure 3A and Figure 3B Detailed discussion. In some embodiments, the curved temple arm housing 110 includes a predetermined number of protruding inserts 115 (e.g., at least one protruding insert, at least three protruding inserts, etc.). For example, as... Figure 1A As shown, the curved temple arm housing 110 includes at least three protruding inserts 115a to 115c.

[0056] The curved temple arm housing 110 includes a power device mount 130. The power device mount 130 is configured to be coupled to one or more components based on the temple arm 100. Specifically, the power device mount 130 of the first temple arm may be configured to be coupled to one or more first components (e.g., power input devices 142, such as power buttons); Figure 1H The power equipment mount 130 of the second temple arm can be configured to be coupled with one or more second components (e.g., power input connector 144, such as a power charger connector). Figure 1HCoupling. In some embodiments, the first temple arm includes a power input device 142, and the second temple arm includes a power input connector 144. Alternatively, in some embodiments, the first temple arm includes a power input connector 144, and the second temple arm includes a power input device 142. The power input device 142 and / or the power input connector 144 are coupled to the end portion of the corresponding curved temple arm housing 110 (e.g., the end portion of the curved temple arm housing opposite to and / or adjacent to the rear power source (e.g., the first power source 170a)). Alternatively, in some embodiments, the power input connector 144 is coupled to the surface (e.g., the side surface) of the corresponding curved temple arm housing 110.

[0057] When the power input device 142 is coupled to the power device holder 130, the power input device 142 is partially exposed (e.g., via the temple arm housing 105 facing the external environment), allowing the user to provide user input via the temple arm housing 105 (e.g., on the side surface of the temple arm 100 opposite the surface that contacts the user's head). For example, the user can touch or actuate the power input device 142 on the outer surface of the temple arm 100 to power or wake the augmented reality glasses (e.g., switch from standby or sleep mode to active mode). In some embodiments, the power input device 142 may be a button, switch, slider, knob, capacitive touch surface, etc. The power input device 142 may include an actuator, spring, and / or button bracket. For example, the power input device 142 may be a power button that includes an actuator and a pressure spring abutting against the temple arm housing, such that when the user actuates the power button, the user receives mechanical feedback that the button has been pressed. In some embodiments, the pressure spring may be replaced with foam (configured to operate as a spring). In some embodiments, when a user actuates the power input device 142, the power input device 142 turns on the power supply to the two temple arms 100 and the frame and lenses of the augmented reality glasses.

[0058] When the power input connector 144 is coupled to the power device holder 130, the power input connector 144 is partially exposed, allowing power cables, power couplers, data connectors, and / or other connectors to be coupled to it. The power input connector 144 is configured to receive available power to power one or more electronic components of the temple arm 100, and, when coupled, to power the frame and / or another temple of the augmented reality glasses. Furthermore, the power input connector 144 can be configured to transmit data to and / or from the temple arm 100 (and / or other coupled devices, such as the frame of the augmented reality glasses, another temple arm, a laptop, tablet, smartphone, etc.). For example, the power input connector 144 may be a plurality of spring pins at least partially exposed to the external environment of the temple arm housing 105 or accessible via the external environment of the temple arm housing 105, these spring pins being configured to couple to a cable that transmits data and / or provides available power to the temple arm 100 and the frame and / or other temple arms of the augmented reality glasses (when coupled to the temple arm 100). Alternatively, the power input connector 144 may be a USB port (e.g., a USB-C port) at least partially exposed to the external environment of the temple arm housing 105 or accessible via the external environment of the temple arm housing 105, such that a USB cable can be coupled to the temple arm 100 to transmit data and / or provide available power to the temple arm 100 and the frame and / or other temple arms of the augmented reality glasses (when coupled to the temple arm 100). In some embodiments, the power input connector 144 is an electrical receptacle (e.g., a Type-C receptacle).

[0059] Each temple arm 100 is configured to be coupled to the frame of the augmented reality glasses via a hinge seat 135 and a hinge assembly 137. Specifically, a curved temple arm housing 110 receives and couples to the hinge seat 135, which is coupled to the hinge assembly 137, and the hinge assembly 137 is coupled to the frame of the augmented reality glasses. The curved temple arm housing 110 includes one or more alignment ribs 133 for receiving the hinge seat 135, and the hinge seat 135 may include a spherical surface for receiving the hinge assembly 137. One or more alignment ribs 133 are located at the front end of the curved temple arm housing 110 and are configured to guide the hinge seat 135 within a portion of the curved temple arm housing 110. Specifically, the hinge seat 135 is configured to slide into the curved temple arm housing 110 via one or more alignment ribs 133. One or more alignment ribs 133 align and hold the hinge seat 135 in a predetermined position (e.g., parallel to the curved temple arm housing 110). In some embodiments, the temple arm 100 may include additional mechanisms for adjustability (e.g., ball joints). In some embodiments, the interface between one or more alignment ribs 133 and the hinge seat 135 may include an adhesive (e.g., glue) to increase the stiffness of the temple arm (e.g., increasing the overall torsional stiffness of the temple arm by up to 5%).

[0060] The hinge base 135 and / or hinge assembly 137 may include one or more channels for routing one or more wires or one or more electrical connectors for communicatively coupling a set of electronic components of the curved temple arm housing 110 to electronic components within the frame and / or another temple arm of the AR glasses. For example, one or more channels may route one or more wires that communicatively couple one or more power supplies 170, one or more speakers 145, one or more sensors, etc., of the curved temple arm housing 110 to one or more components of the frame of the augmented reality glasses (e.g., display, projector, imaging device, and / or other components).

[0061] In some embodiments, the hinge seat 135 may be configured to receive an adhesive that bonds the hinge seat 135 to the curved temple arm housing 110. The hinge seat 135 and the adhesive can form an airtight seal between the curved temple arm housing 110, the hinge assembly 137, and the frame of the augmented reality glasses. In other words, the adhesive fills gaps to reduce and / or prevent liquids and / or dust from entering the temple arm 100, the hinge assembly 137, and / or the frame of the augmented reality glasses. In some embodiments, one or more alignment ribs 133 hold the hinge seat 135 in a predetermined position while the applied adhesive cures to create an airtight seal.

[0062] Hinge assembly 137 is coupled to hinge seat 135 and the frame of the augmented reality glasses. Hinge assembly 137 is configured to allow for various adjustments to the augmented reality glasses. Hinge assembly 137 allows adjustment of the augmented reality glasses along the x-axis, y-axis, and / or z-axis. For example, hinge assembly 137 can be used to adjust a first rotation or a first angle of the temple arm 100 relative to the frame of the augmented reality glasses, and / or a second rotation or a second angle of the temple arm 100 relative to the frame of the augmented reality glasses. Hinge assembly 137 allows the user to adjust the temple arm 100 such that the user's ear is supported by the temple arm 100 via ear position 125. In some embodiments, hinge assembly 137 is capable of adjusting the length of the temple arm 100. In some embodiments, hinge assembly 137 allows for adjustments associated with other mechanisms of the augmented reality glasses to accommodate different head sizes, nose bridge positions, and / or interpupillary distances of the user.

[0063] Figure 1B A curved temple arm housing 110 is shown, including an acoustic mesh 143. In some embodiments, wires or the acoustic mesh 143 are coupled to each of the audio channels 121 and additional audio channels 119. The acoustic mesh 143 is selected based on its properties of filtering external particles and / or contaminants. In some embodiments, the acoustic mesh 143 is a hydrophobic mesh configured to repel water, dust, and / or other contaminants. In some embodiments, the acoustic mesh is optional. In some embodiments, the acoustic mesh 143 is coupled to the curved temple arm housing 110 via a speaker adhesive 141 (e.g., a pressure-sensitive adhesive described below).

[0064] The speaker adhesive 141 may be a pressure-sensitive adhesive applied to a portion of the cavity 113. In some embodiments, the application of the speaker adhesive 141 is based on the size and / or shape of the speaker 145. For example, as Figure 1B As shown, speaker adhesive 141 is applied in a square outline (the square outline being the outer periphery of speaker 145). In some embodiments, speaker adhesive 141 is applied to the smallest portion of cavity 113 (e.g., the periphery of speaker 145 or speaker housing) to prevent interference with speaker 145 and / or avoid increasing the size (e.g., thickness) and / or weight of temple arm 100. In some embodiments, the curved temple arm housing 110 includes one or more mounting and securing devices 156 (e.g., bosses, studs, screw holes, anchor holes, etc.) for coupling speaker 145 or speaker housing thereto. See below for reference. Figure 1CAs discussed, the speaker 145 (or speaker housing) may be coupled to the curved temple arm housing 110 via speaker adhesive 141, fasteners (e.g., screws, anchors, etc.) or both. In some embodiments, the speaker adhesive 141 may be replaced by or used in combination with a liquid silicone rubber gasket to form an hermetically sealed seal.

[0065] Speaker adhesive 141 is applied to the ear position 125 ( Figure 1A The speaker 145 is positioned near the user's ear. In some embodiments, speaker adhesive 141 is placed between the first plurality of ribs 117a and the second plurality of ribs 117b, positioning the speaker 145 between two electronic components. For example, speaker adhesive 141 may be applied to cavity 113, positioning the speaker 145 between the first power supply 170a and the second power supply 170b. Although Figures 1A to 1H The illustrated temple arm 100 includes at least two power sources 170, but in some embodiments, the temple arm 100 may include one or more power sources. In some embodiments, speaker adhesive 141 is used to isolate the audio channel 121 from the additional audio channel 119 and further protect each speaker port from water, dust, or other external contaminants. Specifically, speaker adhesive 141 is configured to isolate the two speaker ports and prevent dust / water from entering the temple arm and / or speaker when water and / or dust enter via a membrane or mesh 143 (e.g., an adhesive ring around the additional audio channel 119 (e.g., the rear port) and another adhesive ring around the audio channel 121 (e.g., the direct port pointing downwards)).

[0066] The temple arm 100 may include an input device 140. The input device 140 may be as described below. Figure 1H The privacy slider 147 or the acquisition switch 148 shown and described. The input device 140 is positioned at the front end of the curved temple arm housing 110, adjacent to the hinge seat 135 and the hinge assembly 137. In some embodiments, the first temple arm includes the privacy slider 147, and the second temple arm includes the acquisition switch 148. Alternatively, in some embodiments, the second temple arm includes the privacy slider 147, and the first temple arm includes the acquisition switch 148. In some embodiments, the input device 140 is positioned at the bottom of the curved temple arm housing 110 (e.g., on a portion of the surface including the ear position 125). For example, as... Figure 1B As shown, the input device 140 is positioned at the bottom front end of the curved temple arm housing 110.

[0067] Input device 140 is configured to control one or more electronic components of the augmented reality glasses. For example, input device 140 may be a privacy slider 147, which, when actuated, is configured (e.g., mechanically or via one or more instructions provided to one or more processors) to disable or enable audio and / or image acquisition devices of the two temple arms and / or the frame of the augmented reality glasses. Alternatively, input device 140 may be a point-of-view (POV) camera acquisition switch 148, which, when actuated, initiates or terminates the operation of an imaging device communicatively coupled to the augmented reality glasses (e.g., acquiring still images, one or more images, video, etc.). In some embodiments, input device 140 provides auditory, visual, and / or tactile feedback to the user when actuated. For example, actuation of privacy slider 147 may include a tactile impact, an auditory "click," and / or the presentation of associated indicators (e.g., a strikethrough camera icon and / or microphone icon).

[0068] like Figure 1B As further shown, the hinge seat 135 and hinge assembly 137 are coupled to the curved temple arm housing 110. Specifically, the hinge seat 135 is inserted into the curved temple arm housing 110, and the hinge assembly 137 is coupled to the hinge seat 135 (e.g., a spherical or ball-shaped surface of the hinge assembly 137 is received via a corresponding spherical surface of the hinge seat 135). As described above, the hinge seat 135 and hinge assembly 137 form an hermetically sealed connection when coupled to the curved temple arm housing 110.

[0069] Go to Figure 1C A speaker 145 is coupled to a curved temple arm housing 110. Specifically, the speaker 145 is positioned within a middle portion of the curved temple arm housing 110, and the middle portion of the curved temple arm housing 110 is positioned near the user's ear (e.g., ear position 125). The speaker 145 includes a sound-generating element (e.g., a diaphragm) positioned such that the generated sound is directed to an audio channel 121. An additional audio channel 119, directed away from the user's ear, is configured to cancel audio leakage or audio that can be heard by others to enhance user privacy. In some embodiments, the sound-generating element has a predetermined area. For example, the predetermined area of ​​the sound-generating element may be 79 mm². The example area of ​​the sound-generating element is not limiting.

[0070] The speaker 145 may be coupled to a speaker housing (shown by pattern fill), which is secured to the curved temple arm housing 110 via speaker adhesive 141 and / or mounting fasteners 156 (e.g., cross-shaped pieces or pins). For example, the speaker housing may include corresponding mounting fasteners (e.g., fastener holes 159 coupled to or part of the speaker housing) for holding the speaker housing in a predetermined position within the curved temple arm housing 110. In some embodiments, the speaker 145 and the speaker housing are aligned within the curved temple arm housing 110 using one or more ribs 117 (e.g., between first ribs 117a and second ribs 117b) and / or an additional alignment rib 158 that controls rotation of the speaker housing within the temple arm housing.

[0071] In some embodiments, the speaker housing has predetermined dimensions such that the speaker housing and speaker 145 fit within the curved temple arm housing 110. For example, the dimensions of the speaker housing may be a predetermined width (e.g., 20 mm + / - 6 mm), a predetermined height (e.g., 12.6 mm + / - 6 mm), and a predetermined thickness (e.g., 4 mm + / - 6 mm). The above sample measurements are not limiting. The speaker 145 (and / or speaker housing) may take any size to fit within the temple arm 100. In some embodiments, the speaker 145 and speaker housing occupy the entire height of the curved temple arm housing 110.

[0072] The speaker housing may include a speaker cover that conceals the sound-generating elements (e.g., a diaphragm) of the speaker 145. Specifically, the speaker cover is coupled to the speaker 145 via the speaker housing and adjacent to a skin-facing temple arm cover 190. Figure 1F The speaker cover may include one or more guides for placing the RFPCA 160 or other components above the speaker housing. In some embodiments, the speaker 145 is configured to be coupled to one or more electronic components or one or more electronic parts (such as sensor platform 149 (discussed below)).

[0073] Sensor platform 149 is an RFPCA that includes one or more sensors or other electronic components. Sensor platform 149 may include one or more flexible printed circuit (FPC) regions, which include corresponding electronic components. In some embodiments, sensor platform 149 includes at least two sensor platform FPC regions (e.g., sensor platform FPC regions 149a and 149b); Figure 1FThe at least two sensor platform FPC regions are separated by at least a predetermined thickness of the speaker housing. This allows sensor platform 149 to isolate or separate one or more components from each other (e.g., to prevent or reduce interference) and / or create additional space for one or more components (e.g., RFPCA 160 and / or the rigid or semi-rigid portion 165 of RFPCA 160), as referenced below. Figure 1D As discussed, the sensor platform 149 includes a connection region 157 (e.g., an extended FPC region) configured to be coupled to a speaker 145. The connection region 157 couples one or more sensors or other components of the sensor platform 149 to the speaker 145, one or more power supplies 170, and / or other components of the augmented reality glasses. In some embodiments, the connection region 157 is a hardened or semi-rigid FPC having a predetermined shape or curvature, such that the connection region 157 is coupled to the outer periphery of the speaker 145 or the speaker housing. The sensor platform 149 may also include features for connecting the sensor platform 149 to an RFPCA 160 (…). Figure 1D A connector (not shown) is used for coupling. In some embodiments, the speaker 145 is part of the sensor platform 149. For example, the speaker 145 and the sensor platform 149 may form a single device (e.g., an audio output component).

[0074] Sensor platform 149 may include one or more sensors or other electronic components, such as IMU 153, proximity sensor 155, and temperature sensor 151. In some embodiments, sensor platform 149 may include a microphone (e.g., rear microphone 150). Sensor platform 149 may include more or fewer components than described above. For example, sensor platform 149 may include only temperature sensor 151 and microphone 150 (e.g., rear microphone 150a). In some embodiments, sensor platform 149 may include temperature sensor 151, microphone 150, and IMU 153 or proximity sensor 155. References below Figures 7A to 7C Describe one or more components of augmented reality glasses.

[0075] The sensor platform 149 is coupled to the curved temple arm housing 110 via a platform base 122. The platform base 122 may include one or more alignment features (e.g., protrusions) for aligning the sensor platform 149 onto the curved temple arm housing 110. The sensor platform 149 may be coupled to the curved temple arm housing 110 via an adhesive and / or one or more fasteners. For example, one or more alignment features may receive fasteners (e.g., screws, anchors, etc.) that couple the sensor platform 149 to the curved temple arm housing 110. In some embodiments, the alignment features may include an adhesive (e.g., epoxy, super glue, plastic glue, acrylic glue, threadlocker, etc.) to further reinforce the temple arm. In some embodiments, glue may be used within holes for receiving screws to further reinforce the temple arm. In some embodiments, glue may act as a liquid filler between one or more alignment ribs 133 and hinge base 135. The sensor platform 149 is positioned near the ear position 125 and / or speaker 145. In some embodiments, the sensor platform 149 is aligned within the curved temple arm housing 110 using one or more ribs 117 (e.g., between a first plurality of ribs 117a and a second plurality of ribs 117b). The curved temple arm housing 110 may include one or more perforations or openings for one or more components of the sensor platform 149. For example, one or more perforations allow the microphone 150 to acquire audio data (e.g., from the user or the external environment) and / or one or more sensors to detect external conditions.

[0076] In some embodiments, the temple arm 100 includes more than one microphone 150. For example, the temple arm 100 may include at least one rear microphone and one front microphone. In some embodiments, the front microphone 150c is positioned near the hinge base 135, hinge assembly 137, and input device 140 (e.g., between the hinge base 135 and a third plurality of ribs 117c). The front microphone 150c may be positioned as forward as possible (e.g., adjacent to the hinge base 135 and / or hinge assembly 137) to increase the available space within the curved temple arm housing 110 for one or more power supplies 170. Another front microphone 150b may be positioned between a second plurality of ribs 117b and a speaker 145. Additional rear microphones 150d and 150e may be positioned near the power supply housing 130 (e.g., the rear microphones adjacent to the first slot 120a and the second slot 120b).

[0077] exist Figure 1DIn this configuration, the RFPCA 160 is coupled to the curved temple arm housing 110. The RFPCA 160 is shaped to fit within the curved temple arm housing 110. In some embodiments, the RFPCA 160 includes one or more portions, such as a first RFPCA portion 160a, a primary rigid or semi-rigid portion 165, a second RFPCA portion 160b, and a rigid or semi-rigid rear portion 166. The RFPCA 160 is disposed on one or more ribs 117a to 117c and on the speaker 145 (e.g., on the speaker housing and speaker cover). For example, the first RFPCA 160a may be disposed on the speaker 145, the second plurality of ribs 117b, and the third plurality of ribs 117c; and the second RFPCA portion 160b may be disposed on the first plurality of ribs 117a. Additionally or alternatively, in some embodiments, the RFPCA 160 is disposed on or coupled to a portion of the curved temple arm housing 110 (e.g., on the surface of the cavity 113). For example, as Figure 1D As shown, a rigid or semi-rigid portion 165 of the RFPCA 160 is disposed between two FPC regions of the sensor platform 149 and directly coupled to the curved temple arm housing 110. The RFPCA 160 may be coupled to the curved temple arm housing 110 via an adhesive (e.g., pressure-sensitive adhesive) and / or one or more fasteners 172. For example, an adhesive may be applied to a plurality of ribs 117a to 117c to couple the first RFPCA portion 160a and the second RFPCA portion 160b to the curved temple arm housing 110, and the rigid or semi-rigid portion 165 of the RFPCA 160 may be coupled to the curved temple arm housing 110 via a first fastener 172a and a second fastener 172b.

[0078] RFPCA 160 may include reinforced rigid and / or semi-rigid portions. RFPCA 160 may have shape elements based on the shape, size, and available space of the curved temple arm housing 110, and the shape elements of one or more electronic components to be housed within the curved temple arm housing 110. For example, the first RFPCA portion 160a and the second RFPCA portion 160b may be parallel to the first plurality of ribs 117a and the second plurality of ribs 117b, and the third RFPCA portion 161a and the fourth RFPCA portion 161b may be perpendicular (or substantially perpendicular) to the second plurality of ribs 117b. In some embodiments, portions of RFPCA 160 are reinforced for one or more components (e.g., hinge seat 135, hinge assembly 137, input device 140), but are not entirely ridged or flexible. In some embodiments, the intermediate portion 162 of RFPCA 160 is a narrow segment extending over the top of the speaker 145 and / or speaker housing.

[0079] The RFPCA 160 couples the electronic components of the temple arm 100 to the electronic components of the augmented reality glasses. For example, the RFPCA 160 couples the electronic components of the augmented reality glasses to allow data to be transmitted to and from microphone 150, speaker 145, display, imaging device, sensor, and / or other components of the augmented reality glasses. The RFPCA 160 may include one or more connectors for coupling the temple arm 100 and one or more electronic components of the augmented reality glasses. For example, the rigid or semi-rigid rear portion 166 of the RFPCA 160 includes one or more connectors for coupling to a power supply circuit 163 (e.g., the power supply circuit includes circuitry for operating a power input device 142 and / or power input connector 144 mounted via a power device holder 130). The first RFPCA portion 160a may include one or more connectors for coupling with one or more wires or one or more electrical connectors routed via the hinge base 135 and / or hinge assembly 137. Similarly, the rigid or semi-rigid portion 165 of the RFPCA 160 may include one or more connectors for connecting the sensor platform 149, one or more power supplies 170, the speaker 145, and / or other electronic components to the RFPCA 160 and other electronic components of the augmented reality glasses.

[0080] The rigid or semi-rigid portion 165 of RFPCA 160 may include one or more processors (e.g., microcontroller units (MCUs) or as described below). Figure 7C Other processors 748 described herein, the one or more processors being used to control one or more electronic components of the temple arm 100 or to provide instructions to one or more electronic components of the temple arm 100, and to execute instructions (stored in memory (e.g., 750); Figure 7C This is for enabling one or more operations and / or functions of the augmented reality glasses to be performed, and / or for transmitting or sharing data between the electronic components of the augmented reality glasses. In some embodiments, the rigid or semi-rigid portion 165 of the RFPCA 160 includes an audio amplifier, charging circuitry (e.g., similar to power management integrated circuit 744); Figure 1C ) and / or other electronic components.

[0081] As described above, the power supply circuit 163 is configured to allow operation of the power input device 142 and / or power input connector 144 mounted via the power device socket 130. The power supply circuit 163 may be as described below. Figure 7CAs part of the described power system 742, the power supply circuit 163 should be understood to have at least some of the characteristics of the power system 742. For example, the power supply circuit 163 may resemble the charging input terminal 743. In some embodiments, the power supply circuit 163 is coupled to the curved temple arm housing 110 via one or more fasteners 172. For example, as Figure 1D As shown, the power supply circuit 163 is coupled to the curved temple arm housing 110 via a third fastener 172c, a fourth fastener 172d, and a fifth fastener 172e. In some embodiments, fewer than three fasteners are used (e.g., two fasteners or no fasteners). Alternatively, or additionally, in some embodiments, the power supply circuit 163 is coupled to the curved temple arm housing 110 via an adhesive, clip, or hook. In some embodiments, the power supply circuit 163 may include a power light-emitting diode (power LED 194); Figure 1H The power LEDs are visible through a portion of the temple arm housing facing the external environment.

[0082] The power LED 194 can be illuminated to notify the user of the status of the augmented reality glasses. For example, the power LED 194 can be illuminated to notify the user that the augmented reality glasses are fully charged, charging, active, low battery, etc. In some embodiments, the power LED 194 is illuminated to notify the user that the imaging device and / or microphone is active. Alternatively, or additionally, in some embodiments, the power LED 194 is illuminated to indicate a successful connection or ongoing connection with another device. For example, the power LED 194 can be illuminated to notify the user that the augmented reality glasses have successfully communicated or are in communication coupling with another device (e.g., wrist wearable device 600, handheld intermediate processing device 800, mobile device 550 (e.g., smartphone, tablet, etc.) and / or other electronic devices). In some embodiments, the power LED 194 is used to debug the power system 742 (e.g., when the power system 742 is not operating correctly or is not properly powered).

[0083] Figure 1E One or more power sources 170 coupled to the curved temple arm housing 110 are shown. In some embodiments, a first power source 170a is coupled to a second RFPCA portion 160b (above the first plurality of ribs 117a), and a second power source 170b is coupled to the first RFPCA portion 160a (above the second plurality of ribs 117b). The first power source 170a may be coupled to the rear of the curved temple arm housing 110 (e.g., adjacent to the power supply base 130), and the second power source 170b may be coupled to the front of the curved temple arm housing 110 (e.g., adjacent to the speaker 145), or vice versa. Although Figure 1EThe example shown illustrates two power sources 170, but in some embodiments, the temple arm 100 includes a single power source or more than two power sources.

[0084] In some embodiments, one or more power sources 170 are coupled via a battery FPC 173. The battery FPC 173 may include one or more portions that couple one or more power sources 170 together and / or to other electronic components of the temple arm 100. For example, a first battery FPC portion 173a may couple a first power source 170a (e.g., via a board-to-board connector) to a sensor platform 149, which couples the first power source 170a and a second power source 170b to the RFPCA 160 and other components of the augmented reality glasses. A second battery FPC portion 173b and a third battery FPC portion 173c (e.g., via a power connector 174) communicatively couple the first power source 170a and the second power source 170b. The second battery FPC portions 173b and the third battery FPC portions 173c are arranged within the curved temple arm housing 110 to increase the amount of usable space within the cavity 113. For example, the second battery FPC portion 173b may be positioned such that it is perpendicular or substantially perpendicular to the first battery FPC portion 173a and / or the first RFPCA portion 160a, and is arranged around the rigid or semi-rigid portion 165 of the sensor platform 149 and the RFPCA 160; the third battery FPC portion 173c may be a narrow segment extending on the top of the speaker 145 and / or the speaker housing. In some embodiments, each portion of the battery FPC 173 (e.g., 173a, 173b, and 173c) is configured to be individually coupled to the RFPCA 160.

[0085] In some embodiments, the temple arm 100 includes a support structure 167 coupled to a power input device 142 and / or a power input connector 144. Figure 1A In some embodiments, the support structure 167 is used in conjunction with one or more fasteners 172 to press the power circuit 163 (or RFPCA 160) into the curved temple arm housing 110 and / or to press an adhesive (e.g., pressure-sensitive adhesive) into the curved temple arm housing 110. For example, a third fastener 172c, a fourth fastener 172d, and a fifth fastener 172e can press the support structure 167 into the curved temple arm housing 110.

[0086] The temple arm 100 includes an ear pad 171 that can be coupled to the bottom surface of the curved temple arm housing 110 (e.g., adjacent to the audio channel 121 and the ear position 125). Figure 1AEar pads 171 may be coupled to the bottom surface of the curved temple arm housing 110 via adhesives and / or magnets (e.g., magnets within ear pads 171 configured to couple with opposing magnets in the curved temple arm housing 110). In some embodiments, a user may use ear pads 171 to adjust the position of the temple arm 100 and / or the frame of the augmented reality glasses on their ears and / or face. For example, if the user's ears are asymmetrical (e.g., one ear is higher or lower than the other) or the top of the user's ear is not aligned with the user's eyes (e.g., the ear is below the eyes), ear pads 171 may be used to fill the gap between the temple arm 100 and the user's ear to make the augmented reality glasses more comfortable for the user. In some embodiments, ear pads 171 provide additional support to reduce strain or stress on the user's ears when the augmented reality glasses are worn for extended periods. In some embodiments, ear pads 171 are formed of silicone, which provides greater comfort to the user compared to the material of the curved temple arm housing 110. Ear pads 171 can be removed and / or replaced with other ear pads 171 (e.g., ear pads of different sizes, thicknesses, materials, etc.). In some embodiments, ear pads 117 are manufactured in a factory and glued into the curved temple arm housing 110.

[0087] In some embodiments, the temple arm may include a spring finger or spring clip 169 configured to hold a microphone (e.g., front microphone 150c). Figure 1C Biased into the adhesive (e.g., pressure-sensitive adhesive, or a sandwich structure of pressure-sensitive adhesive / film / pressure-sensitive adhesive) and / or the curved temple arm housing 110 as an additional waterproof risk mitigation measure.

[0088] Figure 1F An exploded view of an example temple arm according to some embodiments is shown. The exploded view includes a curved temple arm housing 110, a speaker 145 (including speaker adhesive 141), a sensor platform 149 (including at least two sensor platform FPC regions 149a and 149b), a power input device 142, an RFPCA 160, a support structure 167, a first power supply 170a, a second power supply 170b, a battery FPC 173, a skin-facing temple arm cover 190, and an adhesive 185. The speaker 145, sensor platform 149, power input device 142, RFPCA 160, support structure 167, first power supply 170a, second power supply 170b, and battery FPC 173 are coupled to the curved temple arm housing 110, as referenced above. Figures 1A to 1E As described.

[0089] Adhesive 185 is disposed around the flange of the curved temple arm housing 110 and in one or more grooves 120 of the curved temple arm housing 110. Figure 1A The adhesive 185 covers the periphery of the curved temple arm housing 110 such that when the skin-facing temple arm cover 190 is coupled to the curved temple arm housing 110, the adhesive 185 forms an airtight seal. The adhesives may be the same or different. For example, in some embodiments, the adhesive 185 applied around the periphery of the curved temple arm housing 110 is a soft adhesive (e.g., a low-modulus sealant), while the adhesive 185 within one or more grooves 120 is a structural adhesive.

[0090] The following text is for reference only. Figure 3A and Figure 3B The application of adhesive 185 is discussed in detail.

[0091] A skin-facing temple cover 190 is configured to couple with a curved temple arm housing 110. The skin-facing temple cover 190 includes a bend corresponding to a head shape to conform to a portion of the user's head when the temple arm 100 is worn. Specifically, the skin-facing temple cover 190 is configured to contact the user's skin when the temple arm 100 is worn. The skin-facing temple cover 190 includes one or more insert ribs 195 and / or one or more snap-fit ​​protrusions 197. One or more insert ribs 195 are configured to insert into one or more slots 120 and couple the skin-facing temple cover 190 to the curved temple arm housing 110 when the adhesive 185 cures. One or more snap-fit ​​protrusions 197 are configured to insert into one or more protrusion inserts 115 and couple the skin-facing temple cover 190 to the curved temple arm housing 110 when the adhesive 185 cures. One or more insert ribs 195 provide additional surface area that reinforces the connection between the skin-facing temple cover 190 and the curved temple arm housing 110 during assembly. In some embodiments, one or more insert ribs 195 provide additional structure to the temple arm 100. Specifically, one or more insert ribs 195 engage one or more grooves 120 and form a mechanical bond with an adhesive 185 within one or more grooves 120. When the skin-facing temple cover 190 is coupled to the curved temple arm housing 110, the skin-facing temple cover 190 surrounds the cavity 113, forming a water-resistant or substantially waterproof seal. Reference below Figure 2 Additional information is provided regarding the skin-facing temple cover 190.

[0092] Figure 1GThe interior 198 of the temple arm 100 (e.g., the skin-facing portion of the temple arm) is shown. When a user wears augmented reality glasses, the interior 198 of the temple arm 100 directly contacts a portion of the user's head. As shown in the interior 198, the skin-facing temple arm cover 190 encloses the cavity 113 of the curved temple arm housing 110, preventing the electronic components within the curved temple arm housing 110 from being directly exposed to water, dust, and / or other external and / or environmental conditions. In some embodiments, the skin-facing temple arm cover 190 includes a first aperture 191 that allows light to be emitted from a power LED 194. In some embodiments, the curved temple arm housing 110 includes a hole or aperture covered with a membrane to allow the temple arm housing 105 facing the external environment to gradually dry as moisture penetrates.

[0093] Figure 1H The exterior 199 of the temple arm 100 (e.g., the portion of the temple arm facing the external environment) is shown. When the user wears the augmented reality glasses, the exterior 199 of the temple arm 100 is easily accessible to the user. Specifically, the user can touch the exterior 199 to provide one or more user inputs (e.g., actuate one or more input devices (such as power input device 142), provide one or more touch input commands (e.g., capacitive touch input commands), etc.). Furthermore, the exterior 199 is not obstructed, allowing sound generated by the speaker 145 and directed towards the user's ear to still be heard by the user while wearing the glasses and while the temple arm 100 is being interacted with.

[0094] A second aperture 193 is also shown on the exterior 199 of the temple arm 100. The second aperture 193 is adjacent to the sensor platform 149, allowing one or more electronic components on the sensor platform 149 to acquire data without being obstructed by the temple arm housing 105 facing the external environment. For example, a microphone 150 included on the sensor platform 149 can acquire audio data from the external environment. Additionally or alternatively, in some embodiments, the second aperture 193 is configured to allow air and / or heat to passively exit the temple arm 100.

[0095] The temple arm 100 may also include a privacy LED 146. The privacy LED 146 is positioned on the exterior 199 of the temple arm 100 such that it is visible to other persons (e.g., those looking at the user and / or in the user's direction). The privacy LED 146 may be illuminated based on user input at the input device 140. For example, actuation of the input device 140 may cause the privacy LED 146 to illuminate to notify other persons that the imaging device and / or microphone of the augmented reality glasses is active (e.g., on or currently acquiring data), inactive (e.g., off or currently not acquiring data), and / or disabled (e.g., the imaging device and / or microphone is unavailable or disconnected, making data acquisition impossible (e.g., even if a user instruction to acquire data is provided)).

[0096] As referenced above Figure 1B The input device 140 may be a privacy slider 147 or a data acquisition switch 148. The privacy slider 147 may be actuated in a horizontal direction (e.g., parallel to the longitudinal length of the temple arm 100 (e.g., the length from the hinge base 135 to the power device base 130)). When actuated, the privacy slider 147 disables and / or enables the imaging device and / or microphone of the augmented reality glasses. For example, when the privacy slider 147 is actuated to a first position, the imaging device and / or microphone of the augmented reality glasses may be mechanically disabled (e.g., temporarily removing the electrical coupling between the device and the remaining electronic components of the augmented reality glasses) and / or disabled via one or more instructions provided to one or more processors of the augmented reality glasses. When the privacy slider 147 is actuated to a second position, the imaging device and / or microphone of the augmented reality glasses may be mechanically enabled (e.g., electrically coupling the device and the remaining electronic components of the augmented reality glasses) and / or enabled via one or more instructions provided to one or more processors of the augmented reality glasses. The aforementioned positions are not limiting, and the privacy slider 147 can have more than two positions (e.g., a position to disable only the imaging device, a position to disable only the microphone, a position to mute the augmented reality glasses, etc.). The privacy slider 147 can be locked in each position, requiring the user to intentionally move the privacy slider 147 to a specific position.

[0097] The privacy slider 147 may include a switch arm coupled to a plunger configured to travel via a plunger guide. The plunger includes an O-ring that prevents or reduces the amount of water, dust, or other external contaminants entering the temple arm 100. When actuated, the privacy slider 147 actuates the switch arm, causing the plunger to be guided through the plunger guide, and the O-ring surrounding the plunger forms a seal between the plunger and the plunger guide to prevent the ingress of water, dust, or other external contaminants.

[0098] The acquisition switch 148 can be actuated in a vertical direction (e.g., perpendicular to the longitudinal length of the temple arm 100, such as the length from hinge base 135 to power equipment base 130)). The acquisition switch 148 can be configured as a POV camera acquisition switch 148, such that when actuated, the acquisition switch 148 acquires one or more images from the user's viewpoint. In some embodiments, the user can press and hold the acquisition switch 148 to acquire multiple images and / or video data. In some embodiments, actuation of the acquisition switch 148 may also activate the microphone 150 of the augmented reality glasses, thereby acquiring audio data associated with the image data. The acquisition switch 148 may include seals and springs to prevent or reduce the amount of water, dust, or other external contaminants entering the temple arm 100.

[0099] As referenced above Figure 1B The power device holder 130 can be coupled to a power input device 142 or a power input connector 144. The power input device 142 can be actuated to turn the augmented reality glasses on or off. The power input connector 144 can be configured to couple to an opposing connector configured to provide available power to the augmented reality glasses and / or transmit data to and / or from the augmented reality glasses. External 199 shows the power input connector 144 as two or more spring pins; however, as referenced above... Figure 1A In some embodiments, the power input connector 144 may be a USB port, a Thunderbolt port, a wireless connector (e.g., an inductive antenna, a capacitive antenna, etc.), or other types of connectors known in the art.

[0100] In some embodiments, the power device holder 130 includes a power LED 194. The power LED 194 can be illuminated to notify the user that the augmented reality glasses are fully charged, charging, active, or low in battery. As described above, refer to Figure 1D The power LED 194 can also be illuminated to notify the user of additional augmented reality glasses status updates. In some embodiments, the power LED 194 may be a ring of lights surrounding the power input device 142. Alternatively, in some embodiments, the power LED 194 may be a single light indicator.

[0101] As referenced above Figure 1A and Figure 1B In some embodiments, the privacy slider 147, the acquisition switch 148, the power input device 142, and the power input connector 144 can be placed on opposite temple arms. For example, in some embodiments, the privacy slider 147 and the power input device 142 can be on the right temple arm, and the acquisition switch 148 and the power input connector 144 can be on the left temple arm.

[0102] The above examples are non-limiting; different variations of electronic components may be included in the temple arms. See below for reference. Figures 7A to 7C Additional examples of electronic components included in augmented reality glasses are provided.

[0103] Figure 2 A skin-facing temple cover according to some embodiments is shown. Specifically, Figure 2 The inner surface 203 of the temple arm cover 190 facing the skin is shown, which is configured to interact with the curved temple arm housing 110. Figures 1A to 1H The cavity 113 is coupled to and surrounds the curved temple arm housing 110. The skin-facing temple arm cover 190 may be formed of carbon fiber or carbon fiber composite material and may include one or more insert ribs 195, one or more snap-fit ​​protrusions 197, one or more flange ribs 209a to 209c, and / or one or more spacers 207 (or supports). The skin-facing temple arm cover 190 is configured to have a predetermined thickness and a predetermined weight (e.g., a thickness of 0.35 mm and a weight of 1.26 g when including one or more insert ribs 195, one or more snap-fit ​​protrusions 197, one or more flange ribs 209a to 209c and / or one or more spacers 207). In some embodiments, the skin-facing temple arm cover 190 is 0.25 mm thick and weighs 0.95 g. In other embodiments, the skin-facing temple arm cover 190 may be formed of ultra-high molecular weight polyethylene, stamped sheet metal, injection-molded plastic, or other composite materials.

[0104] The number of insert ribs 195 equals the number of slots 120 (e.g., seven slots 120 correspond to seven insert ribs 195). One or more flange ribs 209 may be formed to accommodate one or more components (e.g., a periphery outlining the shape of the power source 170) within the curved temple arm housing 110. One or more spacers 207 are configured to maintain and / or control the height of the skin-facing temple arm cover 190 relative to the edge of the curved temple arm housing 110, as referenced below. Figure 3A and Figure 3B As described. In some embodiments, one or more spacers 207 are configured to control the thickness of the adhesive to (nominal) 0.20 mm + / - 0.10 mm.

[0105] One or more flange ribs 209a to 209c have predetermined measurements. For example, one or more flange ribs 209a to 209c may have a first predetermined measurement (e.g., height) and a second predetermined measurement (e.g., width). The first and second predetermined measurements can be selected such that one or more flange ribs 209a to 209c adapt to the outer edge (e.g., adhesive flange) of the curved temple arm housing 110. In some embodiments, the first predetermined measurement is 0.5 mm (+ / - 0.02 mm), the second predetermined measurement is 0.1 mm (+ / - 0.02 mm), and vice versa. The above example measurement results are non-limiting and represent different measurement results. In some embodiments, one or more flange ribs 209a to 209c include one or more introduction protrusions 211 configured to control the clearance around the edge periphery of the curved temple arm housing 110 (e.g., the distance between the wall (e.g., rib) of the skin-facing temple arm cover 190 and the wall of the curved temple arm housing 110). In some embodiments, one or more flange ribs 209a to 209c provide stiffness to the temple arm housing 105 facing the external environment during manufacturing and assembly.

[0106] Adhesive 185 is applied to the outer edge of the curved temple arm housing 110 (see below). Figure 3A and Figure 3B (Described as follows) and within one or more grooves 120a to 120f. One or more insert ribs 195 are configured to insert into one or more grooves 120a to 120f and are substantially immersed in adhesive 185. Similarly, one or more flange ribs 209a to 209c are configured to insert into the outer edge of the curved temple arm housing 110 and are substantially immersed in adhesive 185. One or more insert ribs 195, one or more flange ribs 209a-209c and adhesive 185 form an airtight seal upon curing when the skin-facing temple arm cover 190 is coupled to the curved temple arm housing 110. As described below, Figure 3A An example of an airtight seal is provided.

[0107] When the adhesive 185 cures, one or more snap-fit ​​protrusions 197 are configured to couple with a portion of the curved temple arm housing 110. The one or more snap-fit ​​protrusions 197 hold the skin-facing temple arm cover 190 coupled to the curved temple arm housing 110, allowing time for the adhesive 185 to cure. Specifically, the one or more snap-fit ​​protrusions 197 include hooks, latches, locks, grabs, and / or other similar fastening devices configured to couple with a portion of the curved temple arm housing 110 such that the skin-facing temple arm cover 190 does not unintentionally detach from the curved temple arm housing 110 when the adhesive 185 cures. The skin-facing temple arm cover 190 includes a predetermined number of snap-fit ​​protrusions 197. In some embodiments, the skin-facing temple cover 190 includes a first predetermined number of snap-fit ​​protrusions 197 at a first portion of the skin-facing temple cover 190 and a second predetermined number of snap-fit ​​protrusions 197 at a second portion of the skin-facing temple cover 190. For example, such as Figure 2 As shown, three snap-fit ​​protrusions 197a to 197c are provided at the rear 217 of the skin-facing temple arm cover 190 (e.g., they are inserted into one or more protrusion inserts 115 and coupled to the rear of the curved temple arm housing 110), and three snap-fit ​​protrusions 197d to 197f are provided at the front 215 of the skin-facing temple arm cover 190 (e.g., the front is coupled to the front end of the curved temple arm housing 110 (e.g., adjacent to the hinge seat 135)).

[0108] The skin-facing temple cover 190 is configured to partially slide into the curved temple housing 110 and be pushed downward to engage one or more snap-fit ​​protrusions 197 with the body of the curved temple housing 110. Specifically, the front portion 215 of the skin-facing temple cover 190 is configured to slide into the cover opening 192 ( Figure 1F In this configuration, a subset of the snap-fit ​​protrusions 197 (e.g., three snap-fit ​​protrusions 197d to 197f) can engage with the curved temple arm housing 110 when the front portion 215 of the skin-facing temple arm cover 190 is inserted. One or more insertion ribs 195, one or more snap-fit ​​protrusions 197, one or more flange ribs 209a to 209c, and / or other portions of the skin-facing temple arm cover 190 are positioned such that they will not puncture and / or damage one or more power sources 170 and / or other electronic components within the curved temple arm housing 110 when the skin-facing temple arm cover 190 is coupled to the curved temple arm housing 110.

[0109] Figure 3A and Figure 3B A cross-section of a temple arm according to some embodiments is shown. Figure 3AA first example cross-section 300 of the temple arm is shown. Figure 3B A second example cross-section 350 of the temple arm is shown.

[0110] Go to Figure 3A A first example cross-section 300 shows a skin-facing temple cover 190 coupled to an external-facing temple arm housing 105. The skin-facing temple cover 190 includes one or more insert ribs 195 substantially submerged in an adhesive 185 disposed on the external-facing temple arm housing 105. Specifically, the adhesive 185 is disposed on the edge (or flange 305) of the external-facing temple arm housing 105 and within one or more grooves 120 of the skin-facing temple cover 190, such that when the skin-facing temple cover 190 is coupled to the external-facing temple arm housing 105, one or more insert ribs 195 are submerged in the adhesive 185. In some embodiments, the adhesive 185 is received via a gap formed between the external-facing temple arm housing 105 and the skin-facing temple cover 190 (see below). Figure 3B (as shown and described).

[0111] When one or more insert ribs 195 are immersed in adhesive 185, the insert ribs 195 cause adhesive 185 to overflow (e.g., overflow from one or more grooves 120) and coat at least a portion of flange 305. In some embodiments, a portion of adhesive 185 overflows into the interior of the temple arm housing 105 facing the external environment (a small portion of adhesive overflows into a smaller gap adjacent to speaker 145), such that when adhesive 185 cures, a bond is formed on the vertical wall (e.g., between the temple arm housing 105 facing the external environment and the temple arm cover 190 facing the skin). Adhesive 185 within the grooves 120 increases the total surface area that can be coupled with one or more insert ribs 195 and increases the strength of the mechanical bond. Adhesive 185 disposed within one or more grooves 120 and on flange 305 forms an airtight seal upon curing (e.g., represented by edge adhesive 315 and adhesive 185 within the grooves 120).

[0112] An airtight seal is configured to provide water and / or dust resistance to the temple arm. In some embodiments, the airtight seal is configured to provide water and / or dust resistance to the temple arm. Furthermore, the adhesive 185 is configured to provide additional vibration and impact resistance to the temple arm. More specifically, the adhesive 185 is configured to absorb forces acting on the temple arm upon curing. In some embodiments, the adhesive 185 is a soft adhesive (e.g., a low-modulus sealant) to provide an airtight seal that prevents water ingress but does not crack or become too brittle. In some embodiments, the adhesive 185 within one or more grooves 120 is a structural adhesive.

[0113] The temple arm housing 105 facing the external environment includes one or more supports 310 configured to control or maintain a predetermined distance (t) between the skin-facing temple arm cover 190 and a corresponding portion of the temple arm housing 105 facing the external environment. For example, as Figure 3A As shown, one or more supports 310 separate the skin-facing temple arm cover 190 from the flange 305 of the external-facing temple arm housing 105 by a predetermined distance (t). In some embodiments, the predetermined distance (t) is 0.2 mm (+ / - 0.10 mm). The predetermined distance (t) is filled with adhesive 185 to form an airtight seal. Specifically, the adhesive 185 may have a thickness at the flange 305 equal to the predetermined distance (t), thereby forming an airtight seal around the periphery of the external-facing temple arm housing 105. The example predetermined distance (t) provided above is non-limiting, and different parameters may be selected based on the temple arm configuration.

[0114] One or more supports 310 may be configured to control or maintain different pitches (t) as required by a specific configuration. Specifically, one or more supports 310 may have a predetermined height (h). For example, the height (e.g., h) of one or more supports 310 may be selected to define a predetermined pitch (t). In some embodiments, the temple arm housing 105 facing the external environment includes a predetermined number of supports 310. For example, in some embodiments, the predetermined number of supports 310 is 15, 17, 19, etc.

[0115] Adhesive 185 is configured to cover a predetermined distance (d) of flange 305. The predetermined distance (d) is defined by one or more introduction protrusions 211 of one or more flange ribs 209a to 209c. Figure 2 The gap created. (See above for reference.) Figure 2 The aforementioned one or more protrusions 211 are configured to control the gap around the edge periphery of the curved temple arm housing 110. In some embodiments, the predetermined distance (d) is 0.5 mm (+ / - 0.02 mm). The example predetermined distance (d) provided above is non-limiting and different parameters can be selected based on the temple arm configuration.

[0116] Figure 3BThe diagram illustrates one or more snap-fit ​​protrusions 197 that couple the skin-facing temple arm cover 190 to the external environment-facing temple arm housing 105. A second example cross-section 350 of the temple arm also shows a power supply 170 positioned above an RFPCA 160 and an RFPCA 160 positioned above multiple ribs 117. The multiple ribs 117 allow plastic or metal components to be molded with uniform wall thickness and provide a means of mounting electronic components (e.g., (linear) batteries) within the curved body (e.g., a B-spline curve) of the temple arm. Alternatively, uneven wall thickness can create sink marks on the decorative surfaces (e.g., plastic surfaces) of the housing with a curved exterior.

[0117] As referenced above Figure 2 The described embodiment describes one or more snap-fit ​​protrusions 197 configured to couple the skin-facing temple arm cover 190 to the external-environment-facing temple arm housing 105 via an adhesive 185. For example, as shown in the second example cross-section 350, one or more snap-fit ​​protrusions 197 are coupled to a portion of the interior of the external-environment-facing temple arm housing 105. The skin-facing temple arm cover 190 can be coupled to the external-environment-facing temple arm housing 105 without the use of any tools (e.g., only downward pressure is required to snap it into place). In some embodiments, the adhesive 185 is applied prior to coupling the skin-facing temple arm cover 190 to the external-environment-facing temple arm housing 105. Alternatively, in some embodiments, the adhesive 185 is applied after coupling the skin-facing temple arm cover 190 to the external-environment-facing temple arm housing 105.

[0118] The skin-facing temple cover 190 is configured to form a space or gap around the external-facing temple housing 105. Specifically, the skin-facing temple cover 190 forms a decorative gap (g1), an adhesive application gap (g2), and a predetermined distance (t, e.g., the distance between the skin-facing temple cover 190 and a corresponding portion of the external-facing temple housing 105). The decorative gap (g1) can be a predetermined distance such that the adhesive is not visible. For example, the decorative gap (g1) can be 0.1 mm (+ / - 0.02 mm). In some embodiments, the decorative gap prevents interference between at least two parts when considering tolerances in the manufacture of the parts. The adhesive application gap (g2) can be a space that allows the adhesive 185 to flow. For example, the adhesive application gap (g2) can be 0.50 mm (+ / - 0.10 mm). The adhesive application gap (g2) can also have a height equal to the predetermined distance (t). The example measurements provided above are non-limiting and can be selected based on the temple configuration.

[0119] Figure 4A flowchart of a method for forming a temple arm according to some embodiments is shown. In some embodiments, various operations of the methods described herein are interchangeable and / or optional, and the corresponding operations of the methods are performed by any of the foregoing devices, systems, or combinations of devices and / or systems.

[0120] (A1) Figure 4 A flowchart of a method 400 for manufacturing a temple arm according to some embodiments is shown. Method 400 includes providing (410) a temple arm housing (similar to a curved temple arm housing 110) facing the external environment; Figures 1A to 3B Method 400 includes coupling (420) a set of electronic components within a cavity of a temple arm housing facing the external environment, and coupling (430) a hinge assembly to one end of the temple arm housing facing the external environment. Method 400 also includes applying (440) an adhesive to a portion of the cavity of the temple arm housing facing the external environment, and attaching a temple arm housing cover (similar to a skin-facing temple arm cover 190) to the temporal region. Figures 1A to 3B Attached (450) to the temple arm housing facing the external environment. The temple arm housing cover facing the temporal region and a portion of the temple encapsulation hinge assembly facing the external environment, and a set of electronic components (455). In some embodiments, performing different steps in a different order provides greater flexibility and / or other advantages. For example, steps 450 and / or 455 may be performed prior to step 430 to improve maintainability (e.g., the hinge may be coupled to a fully assembled and tested temple arm assembly, allowing replacement of a damaged hinge). (Refer to the above text) Figures 1A to 1H As described, the electronic components are housed within the temple arm housing 105 facing the external environment, and are encapsulated within the temple arm 100 by coupling the skin-facing temple arm cover 190 to the external environment-facing temple arm housing 105.

[0121] (A2) In some embodiments of A1, providing (410) an externally oriented temple arm housing includes forming an externally oriented temple arm housing, the forming including providing an inner mold formed of a water-soluble resin. The inner mold includes one or more undercuts defining a cavity of the temple arm housing. The forming also includes: forming a portion of the temple arm housing on the inner mold; dissolving the inner mold to form the externally oriented temple arm housing portion, the externally oriented temple arm housing portion including one or more grooves; and injection molding a temporal-oriented temple arm housing cover, the temporal-oriented temple arm housing cover including one or more fastening means for engaging with one or more grooves.

[0122] (B1) According to some embodiments, the temple arm includes a curved temple arm housing configured to be coupled to the frame of augmented reality (AR) glasses. The curved temple arm housing has a head-shaped bend to conform to a portion of the user's head. The curved temple arm housing includes a set of electronic components coupled within the head-shaped bend of the curved temple arm housing, the set of electronic components including a speaker, a front battery unit (similar to power supply 170); Figures 1A to 3B The speaker is positioned near the user's ear and between the front and rear battery units. Input devices are configured to control one or more electronic components located within the frame of the AR glasses. (See above for reference.) Figures 1A to 1H An example temple arm is shown and described.

[0123] (B2) In some embodiments of B1, the temple arm is formed according to either A1 or A2.

[0124] (B3) In some embodiments of any of B1 to B2, the speaker (or other audio output component) is a sealed module configured to prevent water from entering the temple arm (or reduce the ability of water to enter the temple arm). In some embodiments, the speaker is positioned within a middle portion of the curved temple arm housing; and the middle portion of the curved temple arm housing is positioned near the user's ear. In some embodiments, the speaker is fully tested before being integrated into the temple arm.

[0125] (B4) In some embodiments of any of B1 to B3, the curved temple arm housing further includes a hinge seat located at a front end of the curved temple arm housing adjacent to the front battery cell. The temple arm may also include a hinge assembly coupled to the curved temple arm housing via the hinge seat. The hinge assembly is configured to couple the curved temple arm housing to the frame of the AR glasses, and the hinge assembly includes one or more channels for routing one or more wires for communicatively coupling the set of electronic components to electronic components positioned within the frame of the AR glasses. Reference is made below. Figures 7A to 7C Additional information about AR glasses is provided.

[0126] (B5) In some embodiments of B4, the group of electronic components supplies power to electronic devices within the frame of the glasses.

[0127] (B6) In some embodiments of any of B4 to B5, the hinge assembly includes a plurality of alignment ribs configured to align the hinge assembly with the hinge seat for coupling; and an adhesive secures the plurality of alignment ribs of the hinge assembly to the hinge seat, thereby forming an airtight seal. In other words, the adhesive fills gaps to reduce / prevent liquid ingress into the temple arm. In some embodiments, the hinge assembly includes at least two ribs or alignment pins that allow the hinge to be coupled to the eyeglass frame in a predetermined position to produce the best possible seal. Furthermore, in some embodiments, the adhesive is coupled to the alignment pins to create a waterproof seal between the hinge and the eyeglass frame. In some embodiments, the adhesive is a soft adhesive (e.g., a low-modulus sealant) to provide an airtight seal against water ingress, but will not break when the temple arm is dropped or bent, or become too brittle when the temple arm is exposed to certain environmental conditions. References above Figure 1A and Figure 1B Additional information about the hinge assembly is provided.

[0128] In some embodiments, the eyeglasses are configured to be coupled to a first curved temple arm housing and a second curved temple arm housing, the first and second curved temple arm housings being coupled at opposite ends (or positions) of the eyeglass frame. In some embodiments, the second temple arm includes another set of electronic components communicatively coupled to electronics within the eyeglass frame. This other set of electronic components differs from the set of electronic components in the first and second temple arms. In some embodiments, the first and second temple arms share a plurality of identical electronic components and a plurality of different electronic components. In some embodiments, the first temple arm passes over the user's left ear, and the second temple arm passes over the user's right ear. (See above reference) Figures 1A to 1H Different examples of temple configurations are described. See also the following references. Figures 7A to 7C Describe the different configurations of head-mounted wearable devices.

[0129] (B7) In some embodiments of any of B1 to B6, the set of electronic devices further includes a first microphone positioned adjacent to the speaker (or adjacent to the rear battery cell) and a second microphone positioned adjacent to the hinge assembly and the front battery cell. Reference above Figures 1A to 1H Different example positions of the microphone and / or speaker within the temple arm are described. In some embodiments, the front microphone is pushed forward as far as possible to make room for the battery cell. In some embodiments, the distance between the microphones is optimized to improve beamforming (e.g., directionality) for sound acquisition.

[0130] (B8) In some embodiments of any of B1 to B7, the input device is a power button located at the end of a curved temple housing adjacent to the rear battery cell. For example, as referenced above... Figures 1A to 1HThe power input device 142 may be located at one end opposite the front end of the curved temple housing 110. The power button includes an actuator, button holder, or spring located on the surface of the temple housing, such that when the user actuates the power button, the user receives mechanical feedback that the button has been pressed. In some embodiments, the spring may be replaced with foam (configured to provide mechanical feedback or produce a similar result to a spring). In some embodiments, the power button is located on one side of the curved temple housing. In some embodiments, the power button is located at the rear of the left or right temple. In some embodiments, when the user actuates the power button, it activates power to both temples, as well as the frame and lenses of the eyeglasses.

[0131] (B9) In some embodiments of any of B1 through B8, the input device includes a camera button located at the front end of the curved temple arm housing. The front end of the curved temple arm housing is adjacent to the front battery cell. In some embodiments, the camera button is located at the bottom of the temple arm. In some embodiments, the camera button is located near the hinge assembly of the right temple arm and at the bottom of the right temple arm. Alternatively, in some embodiments, the camera button is located near the hinge assembly of the left temple arm and at the bottom of the right temple arm. The camera button includes an actuator located near the temple arm housing such that when a user actuates the camera button, the user receives mechanical feedback that the button has been pressed. In some embodiments, when a user presses the camera button, they can activate or deactivate the camera. (See above reference) Figures 1B to 1H An example of a camera button is provided.

[0132] (B10) In some embodiments of any of B1 through B9, the input device includes a privacy slider positioned at the front end of a curved temple arm housing. The front end of the curved temple arm housing is adjacent to the front battery cell. In some embodiments, the privacy slider assembly includes a switch arm coupled to a plunger coupled to a plunger guide. In some embodiments, the privacy slider assembly is located adjacent to a hinge assembly on the left temple arm and at the bottom of the left temple arm. Alternatively, in some embodiments, the privacy switch assembly is positioned on the right temple arm and at the bottom of the left temple arm. The privacy slider includes a switch arm coupled to a plunger coupled to a plunger guide. In some embodiments, the plunger further includes an O-ring such that when the user actuates the switch arm and the plunger is guided through the plunger guide, the O-ring around the plunger forms a seal between the plunger and the plunger guide, thereby preventing any liquid from entering. Reference above Figure 1H A privacy slider is described.

[0133] (B11) In some embodiments of any of B1 to B10, the curved temple arm housing includes a plurality of ribs forming planar mounting surfaces for at least one of a group of electronic components. In some embodiments, a first plurality of ribs forms a first planar mounting surface for coupling a front battery cell to the curved temple arm housing, and a second plurality of ribs forms a second planar mounting surface for coupling a rear battery cell to the curved temple arm housing. For example, as referenced above... Figures 1A to 1H The temple arm may include one or more ribs 117 that provide mounting surfaces for coupling an RFPCA 160, one or more power supplies 170, and / or other electronic components. In some embodiments, the placement of these ribs and the architecture of the curved temple arm housing are configured to accommodate battery expansion. In some embodiments, the one or more ribs 117 enhance the axial stiffness of the temple arm housing 105 facing the external environment, which facilitates assembly during manufacturing. As described above, in some embodiments, the front battery cell assembly is positioned near the hinge assembly, and the rear battery cell assembly is positioned near the end of the curved temple arm housing.

[0134] (B12) In some embodiments of B11, the curved temple arm housing includes a plurality of alignment points, each of which is located at a different corner of the planar mounting surface. The alignment points identify locations for coupling at least one of a set of electronic components to the curved temple arm housing. In some embodiments, the alignment points are used to align components (e.g., front battery cell, rear battery cell, etc.) within 50 micrometers of a desired location (e.g., within 50 micrometers of a predetermined location). In some embodiments, the alignment points serve as markers used by a computer vision system to place at least one electronic component. For example, the computer vision system can detect the alignment points and use them to guide the placement of at least one electronic component (e.g., a battery cell). Reference above Figures 1A to 1H Multiple alignment points 127 are described.

[0135] (B13) In some embodiments of any of B1 to B12, the temple arm further includes one or more ear pads. One or more ear pads are configured to couple adjacent to the speaker to the curved temple arm housing. For example, as referenced above... Figures 1A to 1HThe temple arms may include one or more ear pads 171. In some embodiments, the ear pads are magnetically coupled to the curved temple arms, allowing them to be easily attached to and removed from the temple arms. In some embodiments, the ear pads are adhesively coupled. In some embodiments, if the user's ears are asymmetrical (e.g., one ear is higher or lower than the other) or the top of the user's ear is not aligned with the user's eyes (e.g., the ear is below the eyes), the ear pads are used to fill the gap between the temple arms and the user's ears to make the user more comfortable wearing the glasses. In some embodiments, the ear pads are made of silicone. The ear pads can be adjusted and / or selected to improve the overall comfort of the user when wearing the temple arms and AR glasses.

[0136] (B14) In some embodiments of any of B1 to B13, a group of electronic components further includes a flexible printed circuit (FPC) or a rigid-flexible printed circuit (RFPC) for transmitting data to and from a microphone and / or speaker. The FPC or RFPC is shaped to fit within a curved portion of the head shape of the curved temple arm housing. The PCB may have a first surface configured to couple with a first plurality of ribs, a second surface perpendicular to the first surface configured to bypass the speaker, and a third surface configured to couple with a second plurality of ribs. In some embodiments, a large RFPCA connects all the electronics together in the temple arm. In some embodiments, one or more RFPCA segments are rigid, for example, a first rigid portion coupled to an MCU, charging circuitry, audio amplifier, Bluetooth device, etc. In some embodiments, a second portion of the RFPCA is rigid for a power button, LED, and connector. In some embodiments, portions of the RFPCA are rigid for certain components (e.g., hinges and switches), but are not entirely ridged or flexible. In some embodiments, the middle portion of the RFPCA is a narrow segment extending from the top of an audio output component (e.g., including a speaker). (See above reference) Figures 1A to 1H A sample configuration for RFPCA 160 is provided.

[0137] (B15) In some embodiments of any of B1 to B14, the group of electronic components further includes one or more of the following: a proximity sensor; a temperature sensor; and an inertial measurement unit (IMU). In some embodiments, the loudspeaker is part of a component (e.g., an audio output component) that includes the proximity sensor, temperature sensor, rear microphone, and inertial measurement unit (IMU). The audio output component may have predetermined dimensions, such as 20 mm × 12.6 mm × 4.6 mm (+ / - 2%). In some embodiments, the audio output component occupies the entire height of the curved temple arm housing. In some embodiments, the curved temple arm housing includes a plurality of holes or openings to accommodate sound from the loudspeaker and allow sound to enter the microphone. Reference above Figures 1A to 1H The described sensor platform 149 and other communication-coupled devices are examples of audio output components. See below for reference. Figures 7A to 7C Additional examples of sensors included in wearable devices for the temples and / or head are described.

[0138] (C1) According to some embodiments, the temple arm includes one or more batteries (e.g., power supply 170); Figures 1A to 1H The device comprises a speaker 145, one or more sensors, an externally oriented temple arm housing, and a skin-facing temple arm cover configured to couple with the externally oriented temple arm housing. The externally oriented temple arm housing includes: a head-shaped bend that conforms to a portion of a user's head when the temple arm is worn; a cavity opposite an externally oriented surface of the externally oriented temple arm housing; and one or more slots for receiving adhesive. The cavity is configured to hold one or more batteries, a speaker, and one or more sensors. The skin-facing temple arm cover includes: a corresponding head-shaped bend that conforms to a portion of a user's head when the temple arm is worn; and one or more protrusions (e.g., one or more insert ribs 195). When the skin-facing temple arm cover is coupled to the externally oriented temple arm housing, the skin-facing temple arm cover (i) surrounds the cavity, and (ii) one or more protrusions engage one or more slots, forming a mechanical bond with the adhesive received within one or more slots. Figures 1A to 3B An example is provided of coupling a skin-facing temple cover 190 to a curved temple housing 110.

[0139] (C2) In some embodiments of C1, the skin-facing temple cover further includes one or more snap-fit ​​protrusions configured to mechanically couple with the external-environment-facing temple housing such that the skin-facing temple cover remains coupled to the external-environment-facing temple housing when the adhesive cures. In some embodiments, the skin-facing temple cover includes three front snaps and three rear snaps. In some embodiments, the number of front snaps and / or rear snaps within the skin-facing temple can vary (e.g., more or less than three front snaps and / or more or less than three rear snaps). Each snap is configured to couple to an inner surface of the external-environment-facing temple housing. For example, as referenced above. Figures 1A to 2 As shown and described, one or more snap-fit ​​protrusions 197 of the skin-facing temple arm cover are received via one or more protrusion inserts 115 of the curved temple arm housing 110, and couple the skin-facing temple arm cover 190 to the curved temple arm housing 110. In some embodiments, one or more snap-fit ​​protrusions provide additional structure for the temple arm.

[0140] (C3) In some embodiments of any of C1 to C2, the external environment-facing temple arm housing includes one or more spacers (e.g., support 310) such that a predetermined gap is formed between the external environment-facing temple arm housing and the skin-facing temple arm cover when coupled to the external environment-facing temple arm housing. In some embodiments, the predetermined gap is configured to be 0.2 mm. This allows for an adhesive thickness of 0.2 mm between the edge of the cover and the housing. For example, as referenced above... Figure 3A and Figure 3B As shown and described, the support 310 is configured to control or maintain a predetermined distance (t) between the skin-facing temple arm cover 190 and a corresponding portion of the temple arm housing 105 facing the external environment. In some embodiments, the adhesive thickness is a nominal thickness of 0.2 mm.

[0141] (C3.5) In some embodiments of C3, a first set of spacers in one or more spacers is configured to control the visible decorative gap between the skin-facing temple cover and the external environment-facing temple housing, and a second set of spacers in one or more spacers defines a predetermined adhesive thickness.

[0142] (C4) In some embodiments of any of C1 to C3, the externally facing temple housing includes a flange configured to receive adhesive, and the skin-facing temple cover includes one or more corresponding flange structures. When the skin-facing temple cover is coupled to the externally facing temple housing, one or more corresponding flange structures of the skin-facing temple cover contact the flange of the externally facing temple housing and form a mechanical bond with the adhesive received at the flange. For example, as referenced above... Figure 2 The flange ribs 209a to 209c are configured to be received by the edge portion of the curved temple arm housing 110. The flange ribs 209a to 209c may have different dimensions. For example, the flange has a predetermined width to allow one or more flange ribs to be bonded together by adhesive.

[0143] (C5) In some embodiments of any of C1 to C4, the adhesive forms an airtight seal. Specifically, the adhesive forms a seal between the cap and the housing upon curing, preventing water from entering the housing.

[0144] (C5.5) In some embodiments of any of C1 to C5, a gasket is also included that forms an hermetically tight seal between the skin-facing temple cover and the external environment-facing temple housing (when coupled). In some embodiments, the gasket is an LRS (silicone) gasket.

[0145] (C6) In some embodiments of any of C1 to C5.5, the skin-facing temple cover is formed of carbon fiber.

[0146] (C7) In some embodiments of any of C1 to C6, the skin-facing temple cover does not contact one or more batteries, speakers, and one or more sensors. In some embodiments, one or more batteries, speakers, and one or more sensors are mounted to the inside of the skin-facing temple cover.

[0147] (C8) In some embodiments of any of C1 to C7, the temple arm is formed according to any of A1, A2 and B1 to B15.

[0148] (D1) According to some embodiments, the temple arm housing includes a curved temple arm housing having: a head-shaped bend that conforms to a portion of a user's head; a plurality of ribs; and a set of electronic components coupled within the head-shaped bend of the curved temple arm housing. The plurality of ribs form planar surfaces for coupling one or more electronic components and include one or more identifiable markings for guiding the placement of one or more electronic components. The set of electronic components includes a speaker, a front battery unit, and a rear battery unit. The plurality of ribs define areas for placing at least one front battery unit or a rear battery unit, such that the position of the set of electronic components is predetermined.

[0149] (D2) In some embodiments of D1, a pin is also included for guiding the speaker to be positioned near the user's ear and between the front and rear battery units. For example, the temple arm housing may include a cross-shaped mounting bracket (e.g., mounting bracket 156) for guiding the placement of the speaker.

[0150] (D3) In some embodiments of any of D1 to D2, one or more identifiable markers may be detected using computer vision, enabling the autonomous manufacturing system to detect and place a subset of electronic components. For example, as referenced above... Figures 1A to 1H The curved temple arm housing 110 may include a plurality of alignment points 127 for placing one or more electronic components.

[0151] (D4) In some embodiments of any of D1 to D3, the temple arm housing further includes a flexible printed circuit (FPC) or a rigid-flexible printed circuit (RFPC) configured to be coupled to a plurality of ribs, the FPC or RFPC being positioned between the group of electronic components. For example, as referenced above Figures 1A to 1H The curved temple arm housing 110 may include an RFPCA 160.

[0152] (D5) In some embodiments of any of D1 to D4, the temple arm is formed according to any of A1, A2, B1 to B15 and C1 to C8.

[0153] The devices described above, including systems, wrist-worn wearables, headset devices, and textile-based smart garments, 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 brevity, similar devices and components will be described below. Any differences between devices and components will be described in the corresponding sections below.

[0154] As described herein, a processor (e.g., a central processing unit (CPU), microcontroller unit (MCU), etc.) is an electronic component responsible for executing instructions and controlling the operation of electronic devices (e.g., a wrist-worn wearable device 600, a head-worn wearable device, a HIPD 800, a textile-based smart garment (not shown), or other computer systems). Various types of processors exist that can be used interchangeably or that may be particularly needed in 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 can be 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 in one or more electronic devices can be used in the various embodiments described herein.

[0155] 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 are 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.

[0156] 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 data 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 a boot loader); (iii) flash memory, disk storage devices, optical disc storage devices, or other non-volatile solid-state storage devices (e.g., USB drives, memory cards, and / or solid-state drives (SSDs)) which may be configured to store data in an electronic device; and (iv) cache memory configured to temporarily store frequently accessed data and instructions. As described herein, memory may include structured data (e.g., Structured Query Language (SQL) databases, MongoDB databases, GraphQL data, JSON data, etc.). 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, and documents; (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.

[0157] As described herein, the power system of an electronic device is configured to convert input power into a form that can be used to operate the device. The power system may include various components, including: (i) a power source, which may be an alternating current (AC) adapter power source or a direct current (DC) adapter power source; (ii) a charger input, which may be configured to use a wired and / or wireless connection (which may be part of a peripheral device interface, such as a Universal Serial Bus (USB), a micro USB interface, near-field magnetic coupling, magnetic induction and magnetic resonance charging, and / or radio frequency (RF) charging); (iii) a power management integrated circuit 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.

[0158] 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 Universal Serial Bus (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) a POGO pin, which may be a small spring-loaded pin configured to provide a charging interface; (v) a wireless charging interface; (vi) a GPS interface; (vii) a WiFi interface for providing connectivity between a device and a wireless network; and (viii) a sensor interface.

[0159] As described herein, a sensor is an electronic component (e.g., an electronic component located in and / or otherwise communicating electronically with an electronic device such as a wearable device): these electronic components are 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 in the vicinity of a part of the user's body (e.g., a sensor-skin interface) and / or other devices or objects; (vii) light sensors (e.g., time-of-flight sensors, infrared sensors, visible light sensors, etc.) and / or sensors for sensing data from the user or the user's environment. As described herein, biopotential signal sensing components are devices for measuring electrical activity within the body (e.g., biopotential signal sensors). Some types of bioelectric potential 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 eye muscles to detect eye movements and diagnose eye diseases.

[0160] 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 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.

[0161] 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).

[0162] 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.

[0163] 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).

[0164] Example AR System Figures 5A to 5B An example artificial reality system according to some embodiments is shown. Figure 5AThe first AR system 500a is shown, along with a first example user interaction using a wrist-worn wearable device 600, a head-worn wearable device (e.g., an AR device 700), and / or a handheld intermediary processing device (HIPD) 800. Figure 5B A second AR system 500b and a second example user interaction using a wrist-worn wearable device 600, an AR device 700, and / or a HIPD 800 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 be used with reference to the foregoing. Figures 1A to 4 The described temple arm is operated by a head-worn wearable device (such as AR device 700 and / or VR device 710).

[0165] The following text is for reference only. Figures 6A to 6B Describes a wrist-worn wearable device 600 and one or more of its components. See below for reference. Figure 7A Figure 7D illustrates a head-mounted wearable device and one or more of its components; and references are made below. Figures 8A to 8B Describe HIPD 800 and one or more of its components. The wrist wearable device 600, the head wearable device, and / or HIPD 800 can be communicatively coupled via a network 525 (e.g., cellular, near-field, Wi-Fi, personal area network, wireless LAN, etc.). Furthermore, the wrist wearable device 600, the head wearable device, and / or HIPD 800 can also be communicatively coupled via the network 525 (e.g., cellular, near-field, Wi-Fi, personal area network, wireless LAN, etc.) to one or more servers 530, computers 540 (e.g., laptops, computers, etc.), mobile devices 550 (e.g., smartphones, tablets, etc.), and / or other electronic devices.

[0166] Go to Figure 5A , Figure 5A The illustration shows a user 502 wearing a wrist-worn wearable device 600 and an AR device 700, with a HIPD 800 placed on their table. The wrist-worn wearable device 600, AR device 700, and HIPD 800 facilitate the user's interaction with the AR environment. Specifically, as shown in the first AR system 500a, the wrist-worn wearable device 600, AR device 700, and / or HIPD 800 enable the presentation of one or more avatars 504, digital representations of contacts 506, and virtual objects 508. As described below, the user 502 can interact with one or more avatars 504, digital representations of contacts 506, and virtual objects 508 via the wrist-worn wearable device 600, AR device 700, and / or HIPD 800.

[0167] User 502 may use any of the following to provide user input: wrist wearable device 600, AR device 700, and / or HIPD 800. For example, user 502 may perform one or more gestures detected by the following devices to provide user input: wrist wearable device 600 (e.g., using the reference below). Figures 6A to 6B The description includes one or more EMG sensors and / or IMUs) and / or AR devices 700 (e.g., using the references below). Figure 7A (To one or more image sensors or cameras depicted in Figure 7B). Alternatively or additionally, user 502 may provide user input via one or more touch surfaces of the wrist wearable device 600, AR device 700, and / or HIPD 800 and / or voice commands collected by the microphones of the wrist wearable device 600, AR device 700, and / or HIPD 800. In some embodiments, the wrist wearable device 600, AR device 700, and / or HIPD 800 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 502 may provide user input via one or more facial gestures and / or facial expressions. For example, the cameras of the wrist wearable device 600, AR device 700, and / or HIPD 800 may track the user 502's eyes to navigate the user interface.

[0168] The wrist-worn wearable device 600, AR device 700, and / or HIPD 800 can operate individually or in combination to allow user 502 to interact with the AR environment. In some embodiments, HIPD 800 is configured to operate as a central hub or control center for the wrist-worn wearable device 600, AR device 700, and / or another communication-coupled device. For example, user 502 can provide input to interact with the AR environment at any of the wrist-worn wearable device 600, AR device 700, and / or HIPD 800, and HIPD 800 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 600, AR device 700, and / or HIPD 800. 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 8A to 8BAs described, the HIPD 800 can perform backend tasks and provide runtime data corresponding to the performed backend tasks to the wrist-worn wearable device 600 and / or AR device 700, enabling the wrist-worn wearable device 600 and / or AR device 700 to perform frontend tasks. Thus, compared to the wrist-worn wearable device 600 and / or AR device 700, the HIPD 800, with its greater computing resources and larger thermal margin, performs computationally intensive tasks and reduces the computer resource utilization and / or power consumption of the wrist-worn wearable device 600 and / or AR device 700.

[0169] In the example shown in the first AR system 500a, HIPD 800 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 504 and contact's digital representation 506). Specifically, HIPD 800 performs backend tasks for processing and / or rendering image data (and other data) associated with the AR video call and provides the AR device 700 with runtime data associated with the performed backend tasks, causing the AR device 700 to perform frontend tasks for presenting the AR video call (e.g., presenting avatar 504 and contact's digital representation 506).

[0170] In some embodiments, the HIPD 800 may operate as a focus or anchor point for presenting information. This allows the user 502 to generally know where the information is presented. For example, as shown in the first AR system 500a, an avatar 504 and a digital representation 506 of a contact are presented above the HIPD 800. Specifically, the HIPD 800 and AR device 700 operate in conjunction to determine the location for presenting the avatar 504 and the digital representation 506 of the contact. In some embodiments, information may be presented within a predetermined distance from the HIPD 800 (e.g., within 5 meters). For example, as shown in the first AR system 500a, a virtual object 508 is presented on a table at a distance from the HIPD 800. Similar to the examples above, the HIPD 800 and AR device 700 may operate in conjunction to determine the location for presenting the virtual object 508. Alternatively, in some embodiments, the presentation of information is not constrained by the HIPD 800. More specifically, avatar 504, contact's digital representation 506, and virtual object 508 do not need to be displayed within the predetermined distance of the HIPD800.

[0171] The system coordinates user input provided at the wrist-worn wearable device 600, the AR device 700, and / or the HIPD 800, enabling the user to initiate, continue, and / or complete an operation using any device. For example, user 502 may provide user input to the AR device 700 to cause the AR device 700 to render a virtual object 508, and when the virtual object 508 is rendered by the AR device 700, user 502 may provide one or more gestures via the wrist-worn wearable device 600 to interact with and / or manipulate the virtual object 508.

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

[0173] In some embodiments, user 502 launches an application on a wrist-worn wearable device 600, AR device 700, and / or HIPD 800 via user input, which causes the application to launch on at least one device. For example, in a second AR system 500b, user 502 performs a gesture associated with a command to launch a messaging application (represented by the messaging user interface 512), wrist-worn wearable device 600 detects the gesture, and based on determining that user 502 is wearing AR device 700, causes AR device 700 to present the messaging user interface 512 of the messaging application. AR device 700 may present the messaging user interface 512 to user 502 through its display (e.g., as shown in user 502's field of view 510). In some embodiments, the application is launched and runs on a device (e.g., wrist-worn wearable device 600, AR device 700, and / or HIPD 800) 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 600 can detect user input to launch a messaging application, launch and run the messaging application, and provide runtime data to the AR device 700 and / or HIPD 800 to render 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 600 can detect gestures associated with launching the messaging application and enable the HIPD 800 to run the messaging application and coordinate its rendering.

[0174] Furthermore, user 502 can provide user input at the wrist wearable device 600, AR device 700, and / or HIPD 800 to continue and / or complete an operation initiated at another device. For example, after launching a messaging application via the wrist wearable device 600, and when the AR device 700 presents the messaging user interface 512, user 502 can provide input at HIPD 800 to prepare a response (e.g., indicated by a swipe gesture performed on HIPD 800). The gesture performed by user 502 on HIPD 800 can be provided and / or displayed on another device. For example, the swipe gesture performed by user 502 on HIPD 800 is displayed on the virtual keyboard of the messaging user interface 512 displayed by AR device 700.

[0175] In some embodiments, the wrist wearable device 600, AR device 700, HIPD 800, and / or other communication coupling devices may present one or more notifications to the user 502. The notification may be an indication of a new message, incoming call, application update, status update, etc. The user 502 may select the notification via the wrist wearable device 600, AR device 700, or HIPD 800, causing the application or action associated with the notification to be presented on at least one device. For example, the user 502 may receive a notification that a message has been received at the wrist wearable device 600, AR device 800, HIPD 800, and / or other communication coupling devices, and provide user input at the wrist wearable device 600, AR device 700, and / or HIPD 800 to view the notification, and the device detecting the user input may cause the application associated with the notification to be launched and / or presented at the wrist wearable device 600, AR device 700, and / or HIPD 800.

[0176] 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 700 can present game application data to user 502, and HIPD 800 can use a controller to provide input to the game. Similarly, user 502 can use wrist-worn wearable device 600 to activate the camera of AR device 700, and the user can use wrist-worn wearable device 600, AR device 700, and / or HIPD 800 to manipulate (e.g., zoom in or out, apply filters, etc.) image capture and acquire image data.

[0177] 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.

[0178] In some embodiments discussed below, example devices and systems including electronic devices and systems will be described. 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.

[0179] 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 two other electronic devices and / or subsets of components of one or more electronic devices, facilitating communication and / or data processing and / or data transmission between the respective electronic devices and / or electronic components.

[0180] Example wrist wearable devices Figure 6A and Figure 6B An example wrist-worn wearable device 600 according to some embodiments is shown. The wrist-worn wearable device 600 is referenced herein. Figure 5A and Figure 5B The examples of wearable devices described make it possible for a wrist-worn wearable device to be understood as having the characteristics of a wrist-worn wearable device 600. Figure 6A Multiple components of a wrist-worn wearable device 600 are shown. These components can be used individually or in combination, and include combinations containing other electronic devices and / or electronic components.

[0181] Figure 6A The wearable band 610 and the watch body 620 (or pouch) are shown to be coupled (as discussed below) to form a wrist wearable device 600. The wrist wearable device 600 can perform various functions and / or operations associated with browsing and selectively opening applications through a user interface.

[0182] As will be described in more detail below, the operations performed by the wrist-worn wearable device 600 may include: (i) presenting content to the user (e.g., displaying visual content via display 605); (ii) detecting (e.g., sensing) user input (e.g., sensing touches on peripheral buttons 623 and / or touches on the touchscreen of display 605, 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 613; sending and receiving messages (e.g., text, voice, video, etc.); image acquisition via one or more imaging devices or cameras 625; 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; sleep monitoring, etc.

[0183] The example functions described above can be performed independently in the watch body 620, independently in the wearable band 610, and / or via electronic communication between the watch body 620 and the wearable band 610. In some embodiments, multiple functions can be performed on the wrist wearable device 600 when an AR environment is presented (e.g., via one of the AR systems 500a to 500b). 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.

[0184] The wearable band 610 can be configured to be worn by a user such that the inner (or inner) surface of the wearable structure 611 of the wearable band 610 contacts the user's skin. When worn by the user, the sensor 613 contacts the user's skin. The sensor 613 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 613 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 613 is configured to track the localization and / or motion of the wearable band 610. One or more sensors 613 may include those defined above and / or those described below. Figure 6B Any sensor discussed.

[0185] One or more sensors 613 may be distributed on the inner and / or outer surfaces of the wearable band 610. In some embodiments, one or more sensors 613 are evenly spaced along the wearable band 610. Alternatively, in some embodiments, one or more sensors 613 are positioned at different points along the wearable band 610. Figure 6AAs shown, one or more sensors 613 may be the same or different. For example, in some embodiments, the shape of one or more sensors 613 may be defined as sheet-like (e.g., sensor 613a), elliptical, circular, square, oblong (e.g., sensor 613c), 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 613 are aligned to form a sensor pair (e.g., for sensing neuromuscular signals based on differential sensing within each respective sensor). For example, sensor 613b is aligned with an adjacent sensor to form sensor pair 614a, and sensor 613d is aligned with an adjacent sensor to form sensor pair 614b. In some embodiments, the wearable band 610 does not have sensor pairs. Alternatively, in some embodiments, the wearable band 610 has a predetermined number of sensor pairs (one pair, three pairs, four pairs, six pairs, sixteen pairs, etc.).

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

[0187] According to some embodiments, the wearable band 610 also includes an electrically grounding electrode and a shielding electrode. Similar to the sensor 613, the electrically grounding electrode and the shielding electrode may be distributed on the inner surface of the wearable band 610 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 616 or the inner surface of the wearable structure 611. The electrically grounding electrode and the shielding electrode may be formed as in the sensor 613, and / or use the same components as the sensor 613. In some embodiments, the wearable band 610 includes more than one electrically grounding electrode and more than one shielding electrode.

[0188] Sensor 613 may be formed as part of the wearable structure 611 of the wearable band 610. In some embodiments, sensor 613 is flush or substantially flush with the wearable structure 611 such that it does not extend beyond the surface of the wearable structure 611. Even when sensor 613 is flush with the wearable structure 611, sensor 613 is still configured to contact the user's skin (e.g., via a skin-contact surface). Alternatively, in some embodiments, sensor 613 extends beyond the wearable structure 611 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 613 is coupled to an actuator (not shown) configured to adjust the extension height of sensor 613 (e.g., distance from the surface of the wearable structure 611) such that sensor 613 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 the sensor 613 to improve the overall comfort of the wearable band 610 when worn, while still allowing the sensor 613 to contact the user's skin. In some embodiments, the sensor 613 is indistinguishable from the wearable structure 611 when worn by the user.

[0189] The wearable structure 611 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 611 is a textile or woven fabric. As described above, the sensor 613 may be formed as part of the wearable structure 611. For example, the sensor 613 may be molded into the wearable structure 611 or integrated into the woven fabric (e.g., the sensor 613 may be sewn into the fabric and mimic the flexibility of the fabric (e.g., the sensor 613 may be composed of a series of woven fabric strands)).

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

[0191] As described above, the wearable band 610 is configured to be worn by a user. Specifically, the wearable band 610 can be shaped or otherwise manipulated for wear by a user. For example, the wearable band 610 can be shaped to have a generally circular shape, such that the wearable band can be configured to be worn on the user's forearm or wrist. Alternatively, the wearable band 610 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 610 may include a holding mechanism 612 (e.g., buckles, hooks, and loop fasteners, etc.) for securing the wearable band 610 to the user's wrist or other body part. When the user wears the wearable band 610, the sensor 613 senses data from the user's skin (referred to as sensor data). Specifically, the sensor 613 of the wearable band 610 acquires (e.g., senses and records) neuromuscular signals.

[0192] 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 613 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 605 of the wrist-worn wearable device 600, 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 a virtual device 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 sub-muscular 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 specifies a mapping from gestures to commands).

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

[0194] In some embodiments, the wearable band 610 includes one or more tactile devices 646. Figure 6B 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 613 and / or haptic device 646 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)).

[0195] The wearable band 610 may also include a coupling mechanism 616 for detachably coupling a capsule (e.g., a computing unit) or a watch body 620 (via a coupling surface of the watch body 620) to the wearable band 610 (e.g., the bracket or shape of the coupling mechanism may correspond to the shape of the watch body 620 of the wrist wearable device 600). Specifically, the coupling mechanism 616 may be configured to receive a coupling surface of the watch body 620 near its bottom side (e.g., the side of the watch body 620 opposite the front side where the display 605 is located), allowing a user to push the watch body 620 downwards into the coupling mechanism 616 to attach the watch body 620 to the coupling mechanism 616. In some embodiments, the coupling mechanism 616 may be configured to receive a top side of the watch body 620 (e.g., the side near the front side of the watch body 620 where the display 605 is located), which is pushed upwards into a bracket rather than downwards into the coupling mechanism 616. In some embodiments, the coupling mechanism 616 is an integrated component of the wearable strap 610, such that the wearable strap 610 and the coupling mechanism 616 are a single integral structure. In some embodiments, the coupling mechanism 616 is a type of frame or shell, which allows the coupling surface of the watch body 620 to remain inside or on the coupling mechanism 616 of the wearable strap 610 (e.g., a bracket, tracker strap, support base, buckle, etc.).

[0196] The coupling mechanism 616 allows the watch body 620 to be detachably coupled to the wearable strap 610 via friction engagement, magnetic coupling, a rotation-based connector, a shear pin coupling, a retaining spring, 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 620 to and detach it from the wearable strap 610. For example, a user can twist, slide, rotate, push, pull, or rotate the watch body 620 relative to the wearable strap 610, or a combination of these actions, to attach the watch body 620 to and detach it from the wearable strap 610. Alternatively, as discussed below, in some embodiments, the watch body 620 can be detached from the wearable strap 610 by an actuated release mechanism 629.

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

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

[0199] Turning to the watch body 620, the watch body 620 may have a generally rectangular or circular shape. The watch body 620 is configured to be worn by a user on their wrist or another body part. More specifically, the size of the watch body 620 is configured for easy carrying by the user, attachment to a part of the user's clothing, and / or coupling to a wearable strap 610 (forming a wrist wearable device 600). As described above, the watch body 620 may have a shape corresponding to the coupling mechanism 616 of the wearable strap 610. In some embodiments, the watch body 620 includes a single release mechanism 629 or multiple release mechanisms (e.g., two release mechanisms 629 located on opposite sides of the watch body 620 (e.g., spring-loaded buttons)) for separating the watch body 620 and the wearable strap 610. The release mechanism 629 may include, but is not limited to, buttons, knobs, plungers, handles, levers, fasteners, buckles, dials, latches, or combinations thereof.

[0200] A user can actuate the release mechanism 629 by pushing, rotating, lifting, pressing, shifting, or performing other actions on it. Actuating the release mechanism 629 can release (e.g., detach) the watch body 620 from the coupling mechanism 616 of the wearable band 610, allowing the user to use the watch body 620 independently of the wearable band 610, and vice versa. For example, detaching the watch body 620 from the wearable band 610 allows the user to use the rear camera 625B to capture images. Although the release mechanism 629 is shown as being located at a corner of the watch body 620, it can be positioned anywhere on the watch body 620 that is convenient for user actuation. Furthermore, in some embodiments, the wearable band 610 may also include a corresponding release mechanism for detaching the watch body 620 from the coupling mechanism 616. In some embodiments, the release mechanism 629 is optional, and the watch body 620 can be detached from the coupling mechanism 616 as described above (e.g., by twisting, rotating, etc.).

[0201] The watch body 620 may include one or more peripheral buttons 623 and 627 for performing various operations at the watch body 620. For example, peripheral buttons 623 and 627 may be used to turn on or wake up the display 605 (e.g., switch from sleep to active state), unlock the watch body 620, 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 605 operates as a touchscreen and allows the user to provide one or more inputs for interacting with the watch body 620.

[0202] In some embodiments, the watch body 620 includes one or more sensors 621. The sensors 621 of the watch body 620 may be the same as or different from the sensors 613 of the wearable strap 610. The sensors 621 of the watch body 620 may be distributed on the inner and / or outer surfaces of the watch body 620. In some embodiments, the sensors 621 are configured to contact the user's skin when the user wears the watch body 620. For example, the sensors 621 may be placed on the underside of the watch body 620, and the coupling mechanism 616 may be a bracket with an opening that allows the underside of the watch body 620 to directly contact the user's skin. Alternatively, in some embodiments, the watch body 620 does not include sensors configured to contact the user's skin (e.g., sensors located inside and / or outside the watch body 620 configured to sense data about the watch body 620 and its surrounding environment). In some embodiments, the sensors 613 are configured to track the position and / or movement of the watch body 620.

[0203] The watch body 620 and the wearable band 610 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 620 and the wearable band 610 can share data sensed by sensors 613 and 621, as well as application and device-specific information (e.g., active and / or available applications, output devices (e.g., display, speaker, etc.), input devices (e.g., touchscreen, microphone, imaging sensor, etc.)).

[0204] In some embodiments, the watch body 620 may include, but is not limited to, a front camera 625A and / or a rear camera 625B, a sensor 621 (e.g., a biometric sensor, an IMU, 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 663). Figure 6B (e.g., touch sensors, sweat sensors, etc.). In some embodiments, the body 620 may include one or more tactile devices 676 configured to provide tactile feedback to the user (e.g., skin and / or kinesthetic sensations, etc.). Figure 6B (Vibration haptic actuator). Sensor 621 and / or haptic device 676 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).

[0205] As described above, the watch body 620 and wearable strap 610, when coupled, can form a wrist wearable device 600. When coupled, the watch body 620 and wearable strap 610 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 600. For example, depending on whether the watch body 620 includes a neuromuscular signal sensor, the wearable strap 610 may include alternative instructions for performing related instructions (e.g., providing sensed neuromuscular signal data to the watch body 620 via different electronic devices). Operation of the wrist wearable device 600 can be performed by the watch body 620 alone or in conjunction with the wearable strap 610 (e.g., via a corresponding processor and / or hardware component), or vice versa. In some embodiments, operation of the wrist wearable device 600, the watch body 620, and / or the wearable strap 610 can be combined with another communication coupling device (e.g., HIPD 800; Figures 8A to 8B It is executed by one or more processors and / or hardware components.

[0206] See below for reference Figure 6B As described in the block diagram, the wearable band 610 and / or the watch body 620 may each include independent resources required to perform independent functions. For example, the wearable band 610 and / or the watch body 620 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.

[0207] Figure 6B Block diagrams are shown of a computing system 630 corresponding to a wearable strap 610 and a computing system 660 corresponding to a watch body 620, according to some embodiments. According to some embodiments, the computing system of the wrist wearable device 600 includes a combination of components of the computing system 630 of the wearable strap and components of the computing system 660 of the watch body.

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

[0209] The computing system 660 of the table may include one or more processors 679, controllers 677, peripheral device interfaces 661, power systems 695, and memory (e.g., memory 680), each of which has been defined above and is described in more detail below.

[0210] The power system 695 may include a charging input 696, a power-management integrated circuit (PMIC) 697, and a battery 698, each of which has been defined above. In some embodiments, the watch body 620 and the wearable band 610 may have their own charging inputs (e.g., charging inputs 696 and 657), their own batteries (e.g., batteries 698 and 659), and may share power with each other (e.g., the watch body 620 may power and / or charge the wearable band 610, and vice versa). Although the watch body 620 and / or the wearable band 610 may include their own charging inputs, a single charging input can charge both devices when the two devices are coupled. The watch body 620 and the wearable band 610 may be charged using various technologies. In some embodiments, the watch body 620 and the wearable band 610 may be charged using a wired charging sub-component (e.g., a power cord). Alternatively or additionally, the watch body 620 and / or the wearable band 610 may be configured for wireless charging. For example, a portable charging device can be designed to mate with a portion of the watch body 620 and / or wearable band 610 and wirelessly deliver available power to the battery of the watch body 620 and / or wearable band 610. The watch body 620 and wearable band 610 can have independent power systems (e.g., power systems 695 and 656) to enable each to operate independently. The watch body 620 and wearable band 610 can also share power via their respective PMICs (e.g., PMICs 697 and 658) (e.g., one can charge the other), which can share power via power and ground conductors and / or via wireless charging antennas.

[0211] In some embodiments, the peripheral interface 661 may include one or more sensors 621, many of which are listed below and defined above. Sensor 621 may include one or more coupled sensors 662 for detecting when the watch body 620 is coupled to another electronic device (e.g., a wearable band 610). Sensor 621 may include imaging sensors 663 (one or more cameras 625 and / or individual imaging sensors 663 (e.g., thermal imaging sensors)). In some embodiments, sensor 621 includes one or more SpO2 sensors 664. In some embodiments, sensor 621 includes one or more biopotential signal sensors (e.g., EMG sensors 665 that may be located on the user-facing portion of the watch body 620 and / or the wearable band 610). In some embodiments, sensor 621 may include one or more capacitive sensors 666. In some embodiments, sensor 621 includes one or more heart rate sensors 667. In some embodiments, sensor 621 includes one or more IMUs 668. In some embodiments, one or more IMUs 668 may be configured to detect movement of the user's hand or other positions where the watch body 620 is placed or held.

[0212] In some embodiments, the peripheral device interface 661 includes a Near Field Communication (NFC) component 669, a Global Positioning System (GPS) component 670, a Long-Term Evolution (LTE) component 671, and / or Wi-Fi and / or Bluetooth communication (WiFi / BT) component 672. In some embodiments, the peripheral device interface 661 includes one or more buttons 673 (e.g., Figure 6A The peripheral buttons 623 and 627 in the interface cause an operation to be performed at the body 620 when selected by the user. In some embodiments, the peripheral interface 661 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.).

[0213] The watch body 620 may include at least one display 605 for displaying a visual representation (including user interface elements and / or three-dimensional virtual objects) of information or data to a user. The display may also include a touchscreen for inputting user input (e.g., touch gestures, swipe gestures, etc.). The watch body 620 may include at least one speaker 674 and at least one microphone 675 for providing audio signals to the user and receiving audio input from the user. The user can provide user input through the microphone 675 and can also receive audio output from the speaker 674 as part of a haptic event provided by the haptic controller 678. The watch body 620 may include at least one camera 625, including a front-facing camera 625A and a rear-facing camera 625B. The camera 625 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.

[0214] The computing system 660 of the watch body may include one or more tactile controllers 678 and associated components (e.g., tactile devices 676) for providing tactile events (e.g., vibrational sensations or audio outputs in response to events at the watch body 620) at the watch body 620. The tactile controllers 678 may communicate with one or more tactile devices 676, which may be, for example, electroacoustic devices including a speaker from one or more loudspeakers 674 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 tactile controllers 678 may provide tactile events that can be perceived by a user of the watch body 620. In some embodiments, one or more tactile controllers 678 may receive input signals from one of a plurality of applications 682.

[0215] In some embodiments, computing system 630 and / or computing system 660 may include memory 680, which may be controlled by a memory controller of one or more controllers 677 and / or one or more processors 679. In some embodiments, software components stored in memory 680 include one or more applications 682 configured to perform operations at table body 620. In some embodiments, one or more applications 682 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 680 include one or more communication interface modules 683 as described above. In some embodiments, software components stored in memory 680 include one or more graphics modules 684 for rendering, encoding, and / or decoding audio and / or video data; and one or more data management modules 685 for collecting, organizing, and / or providing access to data 687 stored in memory 680. In some embodiments, one or more applications 682 and / or one or more modules may work together to perform various tasks at table body 620.

[0216] In some embodiments, the software components stored in memory 680 may include one or more operating systems 681 (e.g., a Linux-based operating system, an Android operating system, etc.). Memory 680 may also include data 687. Data 687 may include data 688A, sensor data 689A, media content data 690, and application data 691.

[0217] It should be understood that the computing system 660 of the table body is an example of the computing system within the table body 620, and the table body 620 may have more or fewer components than those shown in the computing system 660 of the table body, combine two or more components, and / or have different configurations and / or arrangements of components. The various components shown in the computing system 660 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.

[0218] Turning to the computing system 630 of the wearable strap, one or more components may be included in the wearable strap 610. The computing system 630 of the wearable strap may include more or fewer components than those shown in the computing system 660 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 630 of the wearable strap are included in a single integrated circuit. Alternatively, in some embodiments, the components of the computing system 630 of the wearable strap are included in multiple communication-coupled integrated circuits. As described above, in some embodiments, the computing system 630 of the wearable strap is configured (e.g., via a wired or wireless connection) to be coupled to the computing system 660 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.

[0219] Similar to the computing system 660 of the watch body, the computing system 630 of the wearable band may include one or more processors 649, one or more controllers 647 (including one or more haptic controllers 648), peripheral device interfaces 631 (which may include one or more sensors 613 and other peripheral devices), power supply (e.g., power system 656), and memory (e.g., memory 650), which includes an operating system (e.g., operating system 651), data (e.g., data 654 including data data 688B, sensor data 689B, etc.), and one or more modules (e.g., communication interface module 652, data management module 653, etc.).

[0220] Based on the above definition, one or more sensors 613 may be similar to sensor 621 of computing system 660. For example, multiple sensors 613 may include one or more coupled sensors 632, one or more SpO2 sensors 634, one or more EMG sensors 635, one or more capacitive sensors 636, one or more heart rate sensors 637, and one or more IMUs 638.

[0221] The peripheral device interface 631 may also include other components similar to those included in the peripheral device interface 661 of the computing system 660, including an NFC component 639, a GPS component 640, an LTE component 641, a Wi-Fi and / or Bluetooth communication (WiFi / BT) component 642, and / or one or more tactile devices 676 as described above with reference to the peripheral device interface 661. In some embodiments, the peripheral device interface 631 includes one or more buttons 643, a display 633, a speaker 644, a microphone (MIC) 645, and a camera 655. In some embodiments, the peripheral device interface 631 includes one or more indicators, such as LEDs.

[0222] It should be understood that the computing system 630 of the wearable band is an example of the computing system within the wearable band 610, and the wearable band 610 may have more or fewer components than those shown in the computing system 630 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 630 of the wearable band may be implemented as one or a combination of hardware, software, and firmware including one or more signal processing integrated circuits and / or application-specific integrated circuits.

[0223] about Figure 6A The wrist wearable device 600 is an example of a coupled wearable strap 610 and a watch body 620; therefore, the wrist wearable device 600 will be understood to include the components shown and described for the computing system 630 for the wearable strap and the computing system 660 for the watch body. In some embodiments, the wrist wearable device 600 has a separate structure (e.g., a separate mechanical structure, a separate electrical structure) between the watch body 620 and the wearable strap 610. In other words, all the components shown in the computing system 630 for the wearable strap and the computing system 660 for the watch body can be accommodated or otherwise disposed in the combined watch device 600, or within the various components of the watch body 620, the wearable strap 610, and / or portions of the wearable strap (e.g., the coupling mechanism 616 of the wearable strap 610).

[0224] The above technology can be used with any device for sensing neuromuscular signals (including...). Figures 6A to 6B 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.

[0225] In some embodiments, the wrist wearable device 600 may be used in conjunction with head wearable devices (e.g., AR device 700 and VR device 710) and / or HIPD 800 described below, and the wrist wearable device 600 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). Having thus described exemplary wrist wearable devices, attention now turns to example head wearable devices, such as AR device 700 and VR device 710.

[0226] Example of a head-mounted wearable device Figures 7A to 7CAn 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 710 (e.g., an AR eye-wearing device or a smart eye-wearing device, such as smart glasses, smart monocles, smart contact lenses, etc.), a VR device 710 (e.g., a VR head-mounted viewer, a head-mounted display (HMD), etc.), or other eye-coupling devices. AR device 700 and VR device 710 are referenced herein. Figure 5A and Figure 5B The described examples of head-mounted wearable devices are such that the head-mounted wearable devices should be understood as having the characteristics of AR device 700 and / or VR device 710. AR device 700 and VR device 710 can perform various functions and / or operations associated with browsing and selectively opening applications through a user interface. AR device 700 and VR device 710 may include, according to... Figures 1A to 4 The temple arms of the mirror.

[0227] In some embodiments, AR systems (e.g., AR systems 500a and 500b); Figure 5A and Figure 5B ) including AR devices 700 (such as Figure 7A (as shown) and / or VR device 710 (such as Figure 7B-1 and Figure 7B-2 (As shown). In some embodiments, AR device 700 and VR device 710 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 7C For a more detailed description, the head-mounted wearable device may use a display projector (e.g., display projector components 707A and 707B) and / or a waveguide to project data representations to a user. Some embodiments of the head-mounted wearable device do not include a display.

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

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

[0230] Lenses 706-1 and 706-2 can be separate displays or display devices (e.g., waveguides for the projected representation). Lenses 706-1 and 706-2 can act together or independently to present an image or a series of images to a user. In some embodiments, lenses 706-1 and 706-2 can operate in conjunction with one or more display projector assemblies 707A and 707B to present image data to a user. Although AR device 700 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.

[0231] AR device 700 includes electronic components, many of which will be discussed below. Figure 7C To describe in more detail. Figure 7A The diagram shows some example electronic components, including sensors 723-1, 723-2, 723-3, 723-4, 723-5, and 723-6, which can be distributed along most of the frame 704 of the AR device 700. See below for reference. Figure 7C The AR device 700 also includes a left camera 739A and a right camera 739B located on different sides of the frame 704. Furthermore, the eye-wearing device includes one or more processors 748A and 748B (e.g., integrated microprocessors, such as ASICs) embedded in a portion of the frame 704.

[0232] Figure 7B-1 and Figure 7B-2 An example visual description of a VR device 710 (e.g., a head-mounted display (HMD) 712, also referred to herein as an artificial reality head-mounted viewer, head-wearable device, VR head-mounted viewer, etc.) is shown. The HMD 712 includes a front body 714 and a frame 716 (e.g., a strip or band) shaped to fit around a user's head. In some embodiments, the front body 714 and / or frame 716 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 748A-1), IMUs, tracking transmitters or detectors, sensors, etc.). In some embodiments, the HMD 712 includes an output audio transducer (e.g., audio transducer 718-1, such as...) Figure 7B-2 As shown. In some embodiments, as Figure 7B-2 As shown, one or more components, such as one or more output audio converters 718 and a frame 716 (e.g., a portion or all of the frame 716 and / or the output audio converters 718), can be configured to attach and detach (e.g., detachably attach) to the HMD 712. In some embodiments, coupling the detachable component to the HMD 712 enables the detachable component to communicate electronically with the HMD 712. The VR device 710 includes electronic components, many of which will be discussed below. Figure 7C To describe in more detail.

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

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

[0235] Alternatively or additionally, in some embodiments, head-worn wearable devices such as VR device 710 and / or AR device 700 include or are communicatively coupled to another external device (e.g., a pairing device), such as a HIPD 8 (hereinafter referred to as...). Figures 8A to 8B (Discussion) and / or optional neckband. An optional neckband can be coupled to the head-wearable device via one or more connectors (e.g., wired or wireless connectors). The head-wearable device and neckband can operate independently without any wired or wireless connection between them. In some embodiments, components of the head-wearable device and components of the neckband can be located on one or more additional peripheral devices, 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.

[0236] In some cases, pairing an external device, such as a mid-processing device (e.g., HIPD 800, optional neckband, and / or wearable accessory device), with a head-worn device (e.g., AR device 700 and / or VR device 710) 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 800) 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, allowing them to more fully integrate the artificial environment into their daily activities, compared to users tolerating wearing a heavier eye-mounted device alone.

[0237] 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, positioning, 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).

[0238] 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 800 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 800) can perform all inertial and spatial calculations from the IMU located on the head-mounted wearable device. See below for reference. Figure 8A and Figure 8B Additional examples of processing performed by communication-coupled devices such as the HIPD 800 are provided.

[0239] Artificial reality systems can include various types of visual feedback mechanisms. For example, the display device in AR device 700 and / or VR device 710 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 a 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 700 and / or VR device 710 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. The display device 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, some artificial reality systems can substantially replace one or more of the user's sensory perceptions of the real world with virtual experiences, rather than blending artificial reality with real reality.

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

[0241] In some embodiments, AR device 700 and / or VR device 710 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 (e.g., wrist-worn device 600, HIPD 800, etc.)) and / or other devices described herein.

[0242] Figure 7C A computing system 720 and an optional housing 790 are shown, each illustrating components that can be included in a head-mounted wearable device (e.g., AR device 700 and / or VR device 710). In some embodiments, the optional housing 790 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 790 may include additional components that extend and / or enhance the functionality of the head-mounted wearable device.

[0243] In some embodiments, the computing system 720 and / or optional housing 790 may include one or more peripheral interfaces 722A and 722B, one or more power systems 742A and 742B (including a charging input 743, a PMIC 744, and a battery 745), one or more controllers 746A and 746B (including one or more haptic controllers 747), one or more processors 748A and 748B (as defined above, including any of the examples provided), and memories 750A and 750B, all of which can communicate electronically with each other. For example, one or more processors 748A and / or 748B may be configured to execute instructions stored in memories 750A and / or 750B, which may cause controllers in one or more controllers 746A and / or 746B to perform operations at one or more peripherals of the peripheral interfaces 722A and / or 722B. In some embodiments, each of the described operations may occur based on power supplied by power systems 742A and / or 742B.

[0244] In some embodiments, the peripheral device interface 722A may include one or more devices configured as part of the computing system 720, many of which have already been described above. Figure 6Aand Figure 6B The wrist-worn wearable device shown is defined and / or described. For example, the peripheral device interface may include one or more sensors 723A. Some example sensors include: one or more coupled sensors 724, one or more acoustic sensors 725, one or more imaging sensors 726, one or more EMG sensors 727, one or more capacitive sensors 728, and / or one or more IMUs 729. In some embodiments, sensor 723A may also include a depth sensor 767, a light sensor 768, and / or any other type of sensor defined above or described with respect to any other embodiments discussed herein.

[0245] In some embodiments, the peripheral device interface may include one or more additional peripheral devices, including one or more NFC devices 730, one or more GPS devices 731, one or more LTE devices 732, one or more WiFi and / or Bluetooth (WiFi / BT) devices 733, one or more buttons 734 (e.g., including slide-able or otherwise adjustable buttons), one or more displays 735A, one or more speakers 736A, one or more microphones 737A, one or more cameras 738A (e.g., including first cameras 739-1 to nth cameras 739-n similar to left camera 739A and / or right camera 739B), one or more haptic devices 740, and / or any other type of peripheral device as defined above or described with respect to any other embodiments discussed herein.

[0246] Head-mounted wearable devices can include various types of visual feedback mechanisms (e.g., presentation devices). For example, the display device in AR device 700 and / or VR device 710 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 735A can be coupled to each of the lenses 706-1 and 706-2 of AR device 700. The displays 735A coupled to each of the lenses 706-1 and 706-2 can operate together or independently to present an image or a series of images to the user. In some embodiments, AR device 700 and / or VR device 710 include a single display 735A (e.g., a near-eye display) or more than two displays 735A.

[0247] In some embodiments, a first set of one or more displays 735A may be used to present an augmented reality environment, and a second set of one or more display devices 735A may be used to present a virtual reality environment. In some embodiments, one or more waveguides may be used in conjunction with presenting artificial reality content to a user of AR device 700 and / or VR device 710 (e.g., as a means of delivering light from a display projector assembly and / or one or more displays 735A to the user's eyes). In some embodiments, one or more waveguides may be wholly or partially integrated into AR device 700 and / or VR device 710. 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 700 and / or VR device 710 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 735A.

[0248] 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 corresponding 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 that is located in the same location as a physical object 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.

[0249] The head-mounted wearable device may include one or more external displays 735A for presenting information to a user. For example, the external display 735A 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 735A may be used to communicate with other elements. For example, a user of the head-mounted wearable device may cause the external display 735A to display a Do Not Disturb notification. The user may also use the external display 735A to share any information acquired by one or more components of the peripheral device interface 722A and / or (e.g., during the operation and / or execution of one or more applications) generated by the head-mounted wearable device.

[0250] The memory 750A may include instructions and / or data executable by one or more processors 748A (and / or processor 748B of housing 790) and / or a memory controller 746A (and / or controller 746B of housing 790). The memory 750A may include one or more operating systems 751, one or more applications 752, one or more communication interface modules 753A, one or more graphics modules 754A, one or more AR processing modules 755A, and / or any other type of module or component defined above or described with respect to any other embodiments discussed herein.

[0251] The data 760 stored in memory 750A can be used in conjunction with one or more of the applications and / or programs discussed above. Data 760 may include data 761, sensor data 762, media content data 763, AR application data 764, and / or any other types of data defined above or described with respect to any other embodiments discussed herein.

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

[0253] 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 748A and controllers 746A 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. Offloading 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 800) are coupled to the head-worn device via one or more connectors. The 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.

[0254] Head-mounted wearable devices can include various types of computer vision components and subsystems. For example, AR device 700 and / or VR device 710 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 7B-1 and Figure 7B-2 A VR device 710 with cameras 739A to 739D 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.

[0255] The optional housing 790 may include components similar to those described above with respect to the computing system 720. For example, the optional housing 790 may include a corresponding peripheral interface 722B, which includes more or fewer components than those described above with respect to peripheral interface 722A. As mentioned above, the components of the optional housing 790 can be used to enhance and / or expand the functionality of the head-mounted wearable device. For example, the optional housing 790 may include corresponding sensors 723B, speakers 736B, displays 735B, microphones 737B, cameras 738B, and / or other components for acquiring and / or presenting data. Similarly, the optional housing 790 may include one or more processors 748B, controllers 746B, and / or memory 750B (including corresponding communication interface modules 753B; one or more graphics modules 754B; one or more AR processing modules 755B, etc.), and the one or more processors, controllers, and / or memory may be used individually and / or in combination with the components of the computing system 720.

[0256] The above text is in Figures 7A to 7C The techniques described herein can be used with various head-mounted wearable devices. In some embodiments, a head-mounted device (e.g., AR device 700 and / or VR device 710) can be used in conjunction with one or more wearable devices, such as wrist-mounted wearable device 600 (or a component thereof). Having thus described examples of head-mounted wearable devices, attention now turns to example handheld middleware devices such as the HIPD 800.

[0257] Example handheld intermediate processing device Figure 8A and Figure 8B An example handheld intermediate processing device (HIPD) 800 according to some embodiments is shown. HIPD 800 is the subject of this document. Figure 5A and Figure 5B The HIPD 800 is an instance of an intermediate device described herein, and therefore should be understood as having the characteristics described with respect to any intermediate device as defined above or elsewhere in this document, and vice versa. The HIPD 800 can perform various functions and / or operations associated with browsing and selectively opening applications through a user interface.

[0258] Figure 8A A top view 805 and a side view 825 of the HIPD 800 are shown. The HIPD 800 is configured to communicatively couple to one or more wearable devices (or other electronic devices) associated with a user. For example, the HIPD 800 is configured to communicatively couple to a user's wrist-worn wearable device 600 (or components thereof, such as the watch body 620 and wearable strap 610), an AR device 700, and / or a VR device 710. The HIPD 800 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 the HIPD 800 can successfully communicatively couple with an electronic device such as a wearable device (e.g., 10 meters)).

[0259] The HIPD 800 can perform various functions independently and / or in conjunction with one or more wearable devices (e.g., wrist wearable device 600, AR device 700, VR device 710, etc.) to perform various functions. The HIPD 800 is configured to enhance and / or improve the functionality of communication-coupled devices such as wearable devices. The HIPD 800 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 800 may include, but are not limited to, task offloading and / or handover; hot offloading and / or handover; 6 degrees of freedom (6DoF) raycasting and / or gaming (e.g., using imaging devices or cameras 814A and 814B, 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 822A and 822B); sensing user input (e.g., sensing touch on multi-touch input surface 802); 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 800 and / or in communication between the HIPD 800 and another wearable device described herein. In some embodiments, the functions of the HIPD 800 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 800 described herein can be used with any type of suitable AR environment.

[0260] When the HIPD 800 is communicatively coupled to wearable devices and / or other electronic devices, the HIPD 800 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 800 for execution. The HIPD 800 executes one or more operations of the wearable device and / or other electronic device and provides data corresponding to the completed operations to the wearable device and / or other electronic device. For example, a user can initiate a video stream using an AR device 700, and backend tasks associated with executing the video stream (e.g., video rendering) can be offloaded to the HIPD 800, which executes the backend tasks and provides the corresponding data to the AR device 700 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 700). In this way, the HIPD 800, 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.

[0261] The HIPD 800 includes a multi-touch input surface 802 located on a first side (e.g., the front surface), configured to detect one or more user inputs. Specifically, the multi-touch input surface 802 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 802 is configured to detect capacitive touch input and / or force (and / or pressure) touch input. The multi-touch input surface 802 includes a first touch input surface 804 defined by surface recesses and a second touch input surface 806 defined by substantially flat portions. The first touch input surface 804 may be positioned adjacent to the second touch input surface 806. In some embodiments, the first touch input surface 804 and the second touch input surface 806 may have different sizes, shapes, and / or cover different portions of the multi-touch input surface 802. For example, the first touch input surface 804 may be substantially circular, while the second touch input surface 806 may be substantially rectangular. In some embodiments, a surface recess on the multi-touch input surface 802 is configured to guide the user in manipulating the HIPD 800. Specifically, the surface recess is configured such that the user holds the HIPD 800 vertically when holding it with one hand (e.g., such that the imaging device or cameras 814A and 814B being used are pointed towards the ceiling or sky). Furthermore, the surface recess is configured such that the user's thumb rests within the first touch input surface 804.

[0262] In some embodiments, different touch input surfaces include multiple touch input areas. For example, a second touch input surface 806 includes at least a first touch input area 808 located within the second touch input area 806 and a third touch input area 810 located within the first touch input area 808. 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 808 causes the HIPD 800 to execute a first command, while user input detected in the second touch input area 806 causes the HIPD 800 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 808 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 806 can be configured to detect capacitive touch input.

[0263] HIPD 800 includes one or more sensors 851 for sensing data used in performing one or more operations and / or functions. For example, HIPD 800 may include an IMU used in conjunction with a camera 814 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 851 included in HIPD 800 include light sensors, magnetometers, depth sensors, pressure sensors, and force sensors. See below for reference. Figure 8B Additional examples of sensor 851 are provided.

[0264] The HIPD 800 may include one or more light indicators 812 to 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 812 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 804. The light indicator may emit light in different colors and / or patterns to provide the user with one or more notifications and / or information about the device. For example, a light indicator located around the first touch input surface 804 may flash when the user receives a notification (e.g., a message), turn red when the HIPD 800 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.

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

[0266] Side view 825 of the HIPD 800 shows a sensor group 820 and a camera 814B. The sensor group 820 includes one or more cameras 822A and 822B, a depth projector 824, an ambient light sensor 828, and a depth receiver 830. In some embodiments, the sensor group 820 includes a light indicator 826. The light indicator 826 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 820 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 820 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 800 described herein can be constructed and / or positioned using different sensor group 820 configurations.

[0267] In some embodiments, HIPD 800 includes one or more tactile devices 871 configured to provide tactile feedback (e.g., kinesthetic sensation). Figure 8B (e.g., a vibration haptic actuator). Sensor 851 and / or haptic device 871 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)).

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

[0269] As described above, HIPD 800 can distribute and / or provide instructions for performing one or more tasks at HIPD 800 and / or the communication coupling device. For example, HIPD 800 can identify one or more back-end tasks to be performed by HIPD 800 and one or more front-end tasks to be performed by the communication coupling device. Although HIPD 800 is configured to offload and / or hand over tasks to the communication coupling device, HIPD 800 can (e.g., via one or more processors, such as a central processing unit (CPU) 877); Figure 8B The HIPD 800 performs both backend and frontend tasks. It can be used to perform enhanced calling (e.g., receiving and / or sending 3D or 2.5D real-time volumetric calls, real-time digital human avatar calls, and / or avatar calls), discreet messaging, 6DoF portrait / landscape gaming, AR / VR object manipulation, AR / VR content display (e.g., content presented via a virtual display), and / or other AR / VR interactions. The HIPD 800 can perform these operations alone or in conjunction with wearable devices (or other communication-coupled electronic devices).

[0270] Figure 8B A block diagram of a computing system (also referred to as a computer system) 840 of a HIPD 800 according to some embodiments is shown. The HIPD 800 described in detail above may include one or more components shown in the HIPD computing system 840. The HIPD 800 is to be understood as including the components of the HIPD computing system 840 shown and described below. In some embodiments, all or most of the components of the HIPD computing system 840 are included in a single integrated circuit. Alternatively, in some embodiments, the components of the HIPD computing system 840 are included in multiple communication-coupled integrated circuits.

[0271] The HIPD computing system 840 may include a processor (e.g., CPU 877, GPU, and / or CPU with integrated graphics), a controller 875, a peripheral interface 850 including one or more sensors 851 and other peripherals, a power supply (e.g., power system 895), and memory (e.g., memory 878) including an operating system (e.g., operating system 879), data (e.g., data 888), one or more applications (e.g., application 880), and one or more modules (e.g., communication interface module 881, graphics module 882, task and processing management module 883, interoperability module 884, AR processing module 885, data management module 886, etc.). The HIPD computing system 840 also includes a power system 895, which includes a charging input / output terminal 896, a PMIC 897, and a battery 898, all of which are defined above.

[0272] In some embodiments, the peripheral device interface 850 may include one or more sensors 851. Sensor 851 may include those referenced above. Figure 6B The sensor described is similar to other sensors. For example, sensor 851 may include an imaging sensor 854, (optionally) an EMG sensor 856, an IMU 858, and a capacitive sensor 860. In some embodiments, sensor 851 may include one or more pressure sensors 852 for sensing pressure data, an altimeter 853 for sensing the altitude of HIPD 800, a magnetometer 855 for sensing magnetic fields, a depth sensor 857 (or time-of-flight sensor) for determining the difference between the camera and an image object, a position sensor 859 (e.g., a flexible position sensor) for sensing relative displacement or positional changes of a portion of HIPD 800, a force sensor 861 for sensing forces applied to a portion of HIPD 800, and a light sensor 862 (e.g., an ambient light sensor) for detecting the amount of illumination. Sensor 851 may include Figure 8B One or more sensors not shown in the diagram.

[0273] References above Figure 6B Similar peripheral devices are described, and peripheral device interface 850 may also include NFC component 863, GPS component 864, LTE component 865, Wi-Fi and / or Bluetooth communication (WiFi / BT) component 866, speaker 869, haptic device 871, and microphone 873. (See above reference) Figure 8A The HIPD 800 may optionally include a display 868 and / or one or more buttons 867. The peripheral interface 850 may also include one or more cameras 870, a touch surface 872, and / or one or more light emitters 874. (See above reference) Figure 8AThe described multi-touch input surface 802 is an example of touch surface 872. The emitter 874 can be one or more LEDs, lasers, etc., and the emitter 874 can be used to project or present information to the user. For example, the emitter 874 may include the information referenced above. Figure 8A The light indicators 812 and 826 are described. Camera 870 (e.g., as described above) Figure 8A The cameras 814A, 814B, and 822 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 870 may be used for SLAM; 6DoF raycasting, gaming, object manipulation, and / or other rendering; face recognition and facial expression recognition, etc.

[0274] Similar to the reference above Figure 6B The computing system 660 of the described watch body and the computing system 630 of the wearable strap, the computing system 840 of the HIPD may include one or more haptic controllers 876 and associated components (e.g., haptic devices 871) for providing haptic events at the HIPD 800.

[0275] Memory 878 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 memory 878 by other components of HIPD 800 (e.g., one or more processors and peripheral interface 850) may be controlled by the memory controller of controller 875.

[0276] In some embodiments, the software components stored in the memory 878 include one or more operating systems 879, one or more applications 880, one or more communication interface modules 881, one or more graphics modules 882, and one or more data management modules 885, which are similar to those described above. Figure 6B The software component described.

[0277] In some embodiments, software components stored in memory 878 include a task and processing management module 883 for identifying one or more front-end and back-end tasks associated with an operation performed by a user, executing one or more front-end and / or back-end tasks, and / or providing instructions to one or more communication-coupled devices that cause the execution of one or more front-end and / or back-end tasks. In some embodiments, the task and processing management module 883 uses data 888 (e.g., device data 890) 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 devices. For example, the task and processing management module 883 may cause the execution of one or more back-end tasks (operations performed at the communication-coupled AR device 700) at HIPD 800 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 700.

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

[0279] The memory 878 may also include data 887, which includes structured data. In some embodiments, data 887 may include data 889, device data 889 (including device data of one or more devices communicatively coupled to the HIPD 800, such as device type, hardware, software, configuration, etc.), sensor data 891, media content data 892, and application data 893.

[0280] It should be understood that the computing system 840 of the HIPD is an example of a computing system within the HIPD 800, and the HIPD 800 may have more or fewer components than those shown in the computing system 840 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 840 of the HIPD are implemented in hardware, software, firmware, or combinations thereof, including one or more signal processing and / or application-specific integrated circuits.

[0281] The above text is in Figures 8A to 8BThe technology described herein can be used with any device used as a human-machine interface controller. In some embodiments, the HIPD 800 can be used in conjunction with one or more wearable devices such as head-mounted wearable devices (e.g., AR device 700 and VR device 710) and / or wrist-mounted wearable devices 600 (or components thereof).

[0282] 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.

[0283] 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.

[0284] 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.

[0285] 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.

[0286] For purposes of explanation, the foregoing description has been illustrated with reference to specific embodiments. However, the illustrative arguments above are 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 operating principles and practical applications to others skilled in the art.

Claims

1. A temple arm for eyeglasses, the temple arm comprising: A curved temple arm housing configured to be coupled to the frame of augmented reality (AR) glasses, the curved temple arm housing having a head-shaped bend to conform to a portion of a user's head, wherein the curved temple arm housing includes: A set of electronic components coupled within the head-shaped bend of the curved temple housing, the set of electronic components including a speaker, a front battery unit, and a rear battery unit, wherein the speaker is positioned near the user's ear and between the front battery unit and the rear battery unit; and An input device configured to control one or more electronic components positioned within the frame of the AR glasses.

2. The temple arm of claim 1, wherein, The curved temple arm housing also includes a hinge seat located at the front end of the curved temple arm housing, the front end of the curved temple arm housing being adjacent to the front battery unit, and the temple arm also includes: A hinge assembly, coupled to the curved temple arm housing via the hinge seat, wherein: The hinge assembly is configured to couple the curved temple arm housing to the frame of the AR glasses, and The hinge assembly includes one or more channels for routing one or more wires to communicatively couple the set of electronic components to electronic components positioned within the frame of the AR glasses.

3. The temple arm of claim 2, wherein, The set of electronic components powers the electronic devices within the frame of the glasses.

4. The temple arm according to claim 2 or 3, wherein: The hinge assembly includes a plurality of alignment ribs configured to align the coupling of the hinge assembly with the hinge seat; and The plurality of alignment ribs define predetermined gaps for receiving the adhesive.

5. The ear leg arm of any preceding claim, wherein, The set of electronic devices also includes a microphone positioned near the hinge assembly and the front battery cell.

6. The ear leg arm of any preceding claim, wherein, The input device is a power button located at the end of the curved temple arm housing, which is adjacent to the rear battery unit.

7. The temple arm according to any of the preceding claims, wherein, The input device includes a camera button located at the front end of the curved temple arm housing, which is adjacent to the front battery unit.

8. The temple arm according to any of the preceding claims, wherein, The input device includes a privacy slider positioned at the front end of the curved temple arm housing, the front end of the curved temple arm housing being adjacent to the front battery cell.

9. The temple arm according to any of the preceding claims, wherein, The curved temple arm housing includes multiple ribs that form a planar mounting surface for at least one of the set of electronic components.

10. The temple arm according to claim 9, wherein, The curved temple arm housing includes a plurality of alignment points, each of which is located at a different corner of the planar mounting surface, wherein the plurality of alignment points indicate a position for coupling at least one of the set of electronic components to the curved temple arm housing.

11. The temple arm according to any of the preceding claims, wherein the temple arm further comprises: One or more ear pads, wherein the one or more ear pads are configured to be coupled adjacent to the speaker to the curved temple arm housing.

12. The temple arm according to any of the preceding claims, wherein, The set of electronic components also includes: A printed circuit board (PCB) for transmitting data to and from a microphone and / or speaker, wherein the PCB is shaped to fit within a curved portion of the head shape of the curved temple arm housing.

13. The temple arm according to any of the preceding claims, wherein, The set of electronic components also includes one or more of the following: Proximity sensor; Temperature sensor; and / or Inertial Measurement Unit (IMU).

14. An augmented reality glasses, said augmented reality glasses comprising: The temple arm according to any of the preceding claims; as well as An input device configured to control one or more electronic components positioned within the frame of the AR glasses.

15. A manufacturing method, the manufacturing method comprising: Provide a temple arm according to any one of claims 1 to 13; as well as The temple arms are coupled to the frame of the augmented reality (AR) glasses.

Images