This relates generally to a portable charging case that is configured to charge a pair of smart glasses (e.g., head-worn augmented-reality glasses) when they are secured into the portable charging case, including components configured ensure the pair of smart glasses remain in contact with charging contacts of the portable charging case.
Traditional smart glasses need to be charged often due to their compact nature and high-power requirements. These constraints pose issues for users who wish to use the smart glasses in a public setting (i.e., not at home), as it becomes inconvenient to worry about looking for a power outlet in an unfamiliar location and then being tethered to that charging location for a significant period of time. Even if the device could be charged using a mobile battery charging bank, ensuring charging continues while the pair of glasses are moving can be problematic, as charging connections can become unconnected.
As such, there is a need to address one or more of the above-identified challenges. A brief summary of solutions to the issues noted above are described below.
The example portable charging cases described herein address the issues noted above, including being able to charge a pair of smart glasses while out and ensuring that uninterrupted charging takes place while the pair of smart glasses are being charged within the portable charging case. Uninterrupted charging is ensured by one or more components described herein configured to hold the smart glasses in a position such that the charging contacts of the portable charging case remain in contact irrespective of orientation. In addition having a charging case that includes a battery that is configured to charge a battery of a pair of smart glasses is convenient, as the user can go longer between needing to plug the portable charging case into a power source.
One example of a portable charging case (e.g., portable charging case described in reference in any of
In another example embodiment, a portable charging case for smart glasses comprises a cavity configured to house a pair of smart glasses. The portable charging case also comprises a lid configured to enclose the cavity, and a clasp that attaches the lid to another portion of the portable charging case. The portable charging case also comprises a light integrated into a portion of the clasp that is attached the other portion of the portable charging case, and the light ring is configured to provide (i) a charging status information of the portable charging case, and (ii) a charging status information for a pair of smart glasses inserted into the cavity. Charging status information can indicate whether the case is charged, case is charging, glasses are charged, glasses are charging, or a combination of charging statuses. For example,
The features and advantages described in the specification are not necessarily all inclusive and, in particular, certain additional features and advantages will be apparent to one of ordinary skill in the art in view of the drawings, specification, and claims. Moreover, it should be noted that the language used in the specification has been principally selected for readability and instructional purposes.
Having summarized the above example aspects, a brief description of the drawings will now be presented.
For a better understanding of the various described embodiments, reference should be made to the Detailed Description below, in conjunction with the following drawings in which like reference numerals refer to corresponding parts throughout the figures.
In accordance with common practice, the various features illustrated in the drawings may not be drawn to scale. Accordingly, the dimensions of the various features may be arbitrarily expanded or reduced for clarity. In addition, some of the drawings may not depict all of the components of a given system, method, or device. Finally, like reference numerals may be used to denote like features throughout the specification and figures.
Numerous details are described herein to provide a thorough understanding of the example embodiments illustrated in the accompanying drawings. However, some embodiments may be practiced without many of the specific details, and the scope of the claims is only limited by those features and aspects specifically recited in the claims. Furthermore, well-known processes, components, and materials have not necessarily been described in exhaustive detail so as to avoid obscuring pertinent aspects of the embodiments described herein.
Embodiments of this disclosure can include or be implemented in conjunction with various types or embodiments of artificial-reality systems. Artificial-reality (AR), as described herein, is any superimposed functionality and or sensory-detectable presentation provided by an artificial-reality system within a user's physical surroundings. Such artificial-realities can include and/or represent virtual reality (VR), augmented reality, mixed artificial-reality (MAR), or some combination and/or variation one of these. For example, a user can perform a swiping in-air hand gesture to cause a song to be skipped by a song-providing API providing playback at, for example, a home speaker. An AR environment, as described herein, includes, but is not limited to, VR environments (including non-immersive, semi-immersive, and fully immersive VR environments); augmented-reality environments (including marker-based augmented-reality environments, markerless augmented-reality environments, location-based augmented-reality environments, and projection-based augmented-reality environments); hybrid reality; and other types of mixed-reality environments.
Artificial-reality content can include completely generated content or generated content combined with captured (e.g., real-world) content. The artificial-reality content can include video, audio, haptic events, or some combination thereof, any of which can be presented in a single channel or in multiple channels (such as stereo video that produces a three-dimensional effect to a viewer). Additionally, in some embodiments, artificial reality can also be associated with applications, products, accessories, services, or some combination thereof, which are used, for example, to create content in an artificial reality and/or are otherwise used in (e.g., to perform activities in) an artificial reality.
A hand gesture, as described herein, can include an in-air gesture, a surface-contact gesture, and or other gestures that can be detected and determined based on movements of a single hand (e.g., a one-handed gesture performed with a user's hand that is detected by one or more sensors of a wearable device (e.g., electromyography (EMG) and/or inertial measurement units (IMU) s of a wrist-wearable device) and/or detected via image data captured by an imaging device of a wearable device (e.g., a camera of a head-wearable device)) or a combination of the user's hands. In-air means, in some embodiments, that the user hand does not contact a surface, object, or portion of an electronic device (e.g., a head-wearable device or other communicatively coupled device, such as the wrist-wearable device), in other words the gesture is performed in open air in 3D space and without contacting a surface, an object, or an electronic device. Surface-contact gestures (contacts at a surface, object, body part of the user, or electronic device) more generally are also contemplated in which a contact (or an intention to contact) is detected at a surface (e.g., a single or double finger tap on a table, on a user's hand or another finger, on the user's leg, a couch, a steering wheel, etc.). The different hand gestures disclosed herein can be detected using image data and/or sensor data (e.g., neuromuscular signals sensed by one or more biopotential sensors (e.g., EMG sensors) or other types of data from other sensors, such as proximity sensors, time-of-flight (ToF) sensors, sensors of an inertial measurement unit, etc.) detected by a wearable device worn by the user and/or other electronic devices in the user's possession (e.g., smartphones, laptops, imaging devices, intermediary devices, and/or other devices described herein).
As described herein, a portable charging case that is configured to protect and charge a pair of smart glasses, similar to those described above, will be discussed in detail.
A first step 110 of the sequence is shown, where the smart glasses 102 are just starting to be inserted into the portable charging case 104. As shown in the first step 110, glasses retention bracket 108 has a cylindrical shape, and the cylindrical shape is configured such that it can move along the nose pads 112A and 112B of the smart glasses.
In order for the retention bracket 108 to move along the nose pads 112A and 112B, the glasses retention bracket 108 is coupled to a glasses retention portion 106 that is at least partially configured to bend. For example, the glasses retention portion 106 is a leaf spring 114 that is coupled at one end 116 to the charging case (or intermediary component 117 that is coupled to the charging case), and the other end 118 is coupled to the glasses retention bracket 108. In some embodiments, the glasses retention portion 106 has a shape that follows a contour of an interior surface 120 of the charging case.
A second step 122 of the sequence is shown, where the smart glasses 102 are partially inserted into the portable charging case 104. As shown in second step 122, the nose pads 112A and 112B moving along the retention bracket 108 and ultimately causing the glasses retention portion 106 (e.g., a leaf spring 114) to deflect (e.g., bend).
Third step 124 illustrates that the smart glasses 102 are fully inserted into the portable charging case 104. As shown in third step 124, the nose pads 112A and 112B are no longer pushing against the glasses retention bracket 108 and the glasses retention portion 106 (e.g., the leaf spring 114) ends up returning to its resting state. In some embodiments, the resting state includes at least some preload on the leaf spring to ensure a predefined resistance force is maintained. Once the smart glasses 102 are fully inserted, a charging pad on the smart glasses 102 make contact with case-charging contacts 126A and 126B which can be spring loaded charging contacts that are configured to charge the smart glasses 102. The glasses retention bracket 108, in conjunction with spring loaded contacts and the retention bracket 108, the portable charging case 104 can continuously charge the smart glasses 102 in any orientation. The nose pads have a shape such that when fully inserted, the glasses retention bracket is in contact with the nose pads and the glasses portion is in its undeflected state.
The devices described above are further detailed below, including systems, wrist-wearable devices, headset devices, and smart textile-based garments. Specific operations described above may occur as a result of specific hardware, such hardware is described in further detail below. The devices described below are not limiting and features on these devices can be removed or additional features can be added to these devices. The different devices can include one or more analogous hardware components. For brevity, analogous devices and components are described below. Any differences in the devices and components are described below in their respective sections.
As described herein, a processor (e.g., a central processing unit (CPU) or microcontroller unit (MCU)), is an electronic component that is responsible for executing instructions and controlling the operation of an electronic device (e.g., a wrist-wearable device 603, a head-wearable device, an HIPD 607, a smart textile-based garment, or other computer system). There are various types of processors that may be used interchangeably or specifically required by embodiments described herein. For example, a processor may be (i) a general processor designed to perform a wide range 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 three-dimensional modeling); (iv) a field-programmable gate array (FPGA) that can be programmed and reconfigured after manufacturing and/or customized to perform specific tasks, such as signal processing, cryptography, and machine learning; (v) a digital signal processor (DSP) designed to perform mathematical operations on signals such as audio, video, and radio waves. One of skill in the art will understand that one or more processors of one or more electronic devices may be used in various embodiments described herein.
As described herein, controllers are electronic components that manage and coordinate the operation of other components within an electronic device (e.g., controlling inputs, processing data, and/or generating outputs). Examples of controllers can include (i) microcontrollers, including small, low-power controllers that are commonly used in embedded systems and Internet of Things (IoT) devices; (ii) programmable logic controllers (PLCs) that may be configured to be used in industrial automation systems to control and monitor manufacturing processes; (iii) system-on-a-chip (SoC) controllers that integrate multiple components such as processors, memory, I/O interfaces, and other peripherals into a single chip; and/or DSPs. As described herein, a graphics module is a component or software module that is designed to handle graphical operations and/or processes, and can include a hardware module and/or a software module.
As described herein, memory refers to electronic components in a computer or electronic device that store data and instructions for the processor to access and manipulate. The devices described herein can include volatile and non-volatile memory. Examples of memory can include (i) random access memory (RAM), such as DRAM, SRAM, DDR RAM or other random access solid state memory devices, configured to store data and instructions temporarily; (ii) read-only memory (ROM) configured to store data and instructions permanently (e.g., one or more portions of system firmware and/or boot loaders); (iii) flash memory, magnetic disk storage devices, optical disk storage devices, other non-volatile solid state storage devices, which can be configured to store data in electronic devices (e.g., universal serial bus (USB) drives, memory cards, and/or solid-state drives (SSDs)); and (iv) cache memory configured to temporarily store frequently accessed data and instructions. Memory, as described herein, can include structured data (e.g., SQL databases, MongoDB databases, GraphQL data, or JSON data). Other examples of memory can include: (i) profile data, including user account data, user settings, and/or other user data stored by the user; (ii) sensor data detected and/or otherwise obtained by one or more sensors; (iii) media content data including stored image data, audio data, documents, and the like; (iv) application data, which can include data collected and/or otherwise obtained and stored during use of an application; and/or any other types of data described herein.
As described herein, a power system of an electronic device is configured to convert incoming electrical power into a form that can be used to operate the device. A power system can include various components, including (i) a power source, which can be an alternating current (AC) adapter or a direct current (DC) adapter power supply; (ii) a charger input that can be configured to use a wired and/or wireless connection (which may be part of a peripheral interface, such as a USB, micro-USB interface, near-field magnetic coupling, magnetic inductive 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 safe limits (e.g., regulating voltage, controlling current flow, 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.
As described herein, peripheral interfaces are electronic components (e.g., of electronic devices) that allow electronic devices to communicate with other devices or peripherals and can provide a means for input and output of data and signals. Examples of peripheral interfaces can include (i) USB and/or micro-USB interfaces configured for connecting devices to an electronic device; (ii) Bluetooth interfaces configured to allow devices to communicate with each other, including Bluetooth low energy (BLE); (iii) near-field communication (NFC) interfaces configured to be short-range wireless interfaces for operations such as access control; (iv) POGO pins, which may be small, spring-loaded pins configured to provide a charging interface; (v) wireless charging interfaces; (vi) global-position system (GPS) interfaces; (vii) Wi-Fi interfaces for providing a connection between a device and a wireless network; and (viii) sensor interfaces.
As described herein, sensors are electronic components (e.g., in and/or otherwise in electronic communication with electronic devices, such as wearable devices) configured to detect physical and environmental changes and generate electrical signals. Examples of sensors can include (i) imaging sensors for collecting imaging data (e.g., including one or more cameras disposed on a respective electronic device); (ii) biopotential-signal sensors; (iii) inertial measurement unit (e.g., IMUs) for detecting, for example, angular rate, force, magnetic field, and/or changes in acceleration; (iv) heart rate sensors for measuring a user's heart rate; (v) SpO2 sensors for measuring blood oxygen saturation and/or other biometric data of a user; (vi) capacitive sensors for detecting changes in potential at a portion of a user's body (e.g., a sensor-skin interface) and/or the proximity of other devices or objects; and (vii) light sensors (e.g., ToF sensors, infrared light sensors, or visible light sensors), and/or sensors for sensing data from the user or the user's environment. As described herein biopotential-signal-sensing components are devices used to measure electrical activity within the body (e.g., biopotential-signal sensors). Some types of biopotential-signal sensors include: (i) electroencephalography (EEG) sensors configured to measure electrical activity in the brain to diagnose neurological disorders; (ii) electrocardiogramar EKG) sensors configured to measure electrical activity of the heart to diagnose heart problems; (iii) electromyography (EMG) sensors configured to measure the electrical activity of muscles and diagnose neuromuscular disorders; (iv) electrooculography (EOG) sensors configured to measure the electrical activity of eye muscles to detect eye movement and diagnose eye disorders.
As described herein, an application stored in memory of an electronic device (e.g., software) includes instructions stored in the memory. Examples of such applications include (i) games; (ii) word processors; (iii) messaging applications; (iv) media-streaming applications; (v) financial applications; (vi) calendars; (vii) clocks; (viii) web browsers; (ix) social media applications, (x) camera applications, (xi) web-based applications; (xii) health applications; (xiii) artificial-reality (AR) applications, and/or any other applications that can be stored in memory. The applications can operate in conjunction with data and/or one or more components of a device or communicatively coupled devices to perform one or more operations and/or functions.
As described herein, communication interface modules can include hardware and/or software capable of data communications using any of a variety of custom or standard wireless protocols (e.g., IEEE 802.15.4, Wi-Fi, ZigBee, 6LoWPAN, Thread, Z-Wave, Bluetooth Smart, ISA100.11a, WirelessHART, or MiWi), custom or standard wired protocols (e.g., Ethernet or HomePlug), and/or any other suitable communication protocol, including communication protocols not yet developed as of the filing date of this document. A communication interface is a mechanism that enables different systems or devices to exchange information and data with each other, including hardware, software, or a combination of both hardware and software. For example, a communication interface can refer to a physical connector and/or port on a device that enables communication with other devices (e.g., USB, Ethernet, HDMI, or Bluetooth). In some embodiments, a communication interface can refer to a software layer that enables different software programs to communicate with each other (e.g., application programming interfaces (APIs) and protocols such as HTTP and TCP/IP).
As described herein, a graphics module is a component or software module that is designed to handle graphical operations and/or processes, and can include a hardware module and/or a software module.
As described herein, non-transitory computer-readable storage media are physical devices or storage medium that can be used to store electronic data in a non-transitory form (e.g., such that the data is stored permanently until it is intentionally deleted or modified).
The user 602 can use any of the wrist-wearable device 603, the AR device 700, and/or the HIPD 607 to provide user inputs. For example, the user 602 can perform one or more hand gestures that are detected by the wrist-wearable device 603 (e.g., using one or more EMG sensors and/or IMUs) and/or AR device 700 (e.g., using one or more image sensors or cameras, described below in reference to
The wrist-wearable device 603, the AR device 700, and/or the HIPD 607 can operate alone or in conjunction to allow the user 602 to interact with the AR environment. In some embodiments, the HIPD 607 is configured to operate as a central hub or control center for the wrist-wearable device 603, the AR device 700, and/or another communicatively coupled device. For example, the user 602 can provide an input to interact with the AR environment at any of the wrist-wearable device 603, the AR device 700, and/or the HIPD 607, and the HIPD 607 can identify one or more back-end and front-end tasks to cause the performance of the requested interaction and distribute instructions to cause the performance of the one or more back-end and front-end tasks at the wrist-wearable device 603, the AR device 700, and/or the HIPD 607. In some embodiments, a back-end task is a background-processing task that is not perceptible by the user (e.g., rendering content, decompression, or compression), and a front-end task is a user-facing task that is perceptible to the user (e.g., presenting information to the user or providing feedback to the user). The HIPD 607 can perform the back-end tasks and provide the wrist-wearable device 603 and/or the AR device 700 operational data corresponding to the performed back-end tasks such that the wrist-wearable device 603 and/or the AR device 700 can perform the front-end tasks. In this way, the HIPD 607, which has more computational resources and greater thermal headroom than the wrist-wearable device 603 and/or the AR device 700, performs computationally intensive tasks and reduces the computer resource utilization and/or power usage of the wrist-wearable device 603 and/or the AR device 700.
In the example shown by the first AR system 600a, the HIPD 607 identifies one or more back-end tasks and front-end tasks associated with a user request to initiate an AR video call with one or more other users (represented by the avatar 604 and the digital representation of the contact 606) and distributes instructions to cause the performance of the one or more back-end tasks and front-end tasks. In particular, the HIPD 607 performs back-end tasks for processing and/or rendering image data (and other data) associated with the AR video call and provides operational data associated with the performed back-end tasks to the AR device 700 such that the AR device 700 performs front-end tasks for presenting the AR video call (e.g., presenting the avatar 604 and the digital representation of the contact 606).
In some embodiments, the HIPD 607 can operate as a focal or anchor point for causing the presentation of information. This allows the user 602 to be generally aware of where information is presented. For example, as shown in the first AR system 600a, the avatar 604 and the digital representation of the contact 606 are presented above the HIPD 607. In particular, the HIPD 607 and the AR device 700 operate in conjunction to determine a location for presenting the avatar 604 and the digital representation of the contact 606. In some embodiments, information can be presented within a predetermined distance from the HIPD 607 (e.g., within five meters). For example, as shown in the first AR system 600a, virtual object 608 is presented on the desk some distance from the HIPD 607. Similar to the above example, the HIPD 607 and the AR device 700 can operate in conjunction to determine a location for presenting the virtual object 608. Alternatively, in some embodiments, presentation of information is not bound by the HIPD 607. More specifically, the avatar 604, the digital representation of the contact 606, and the virtual object 608 do not have to be presented within a predetermined distance of the HIPD 607.
User inputs provided at the wrist-wearable device 603, the AR device 700, and/or the HIPD 607 are coordinated such that the user can use any device to initiate, continue, and/or complete an operation. For example, the user 602 can provide a user input to the AR device 700 to cause the AR device 700 to present the virtual object 608 and, while the virtual object 608 is presented by the AR device 700, the user 602 can provide one or more hand gestures via the wrist-wearable device 603 to interact and/or manipulate the virtual object 608.
In some embodiments, the user 602 initiates, via a user input, an application on the wrist-wearable device 603, the AR device 700, and/or the HIPD 607 that causes the application to initiate on at least one device. For example, in the second AR system 600b, the user 602 performs a hand gesture associated with a command for initiating a messaging application (represented by messaging user interface 612), the wrist-wearable device 603 detects the hand gesture, and, based on a determination that the user 602 is wearing AR device 700, causes the AR device 700 to present a messaging user interface 612 of the messaging application. The AR device 700 can present the messaging user interface 612 to the user 602 via its display (e.g., as shown by user 602's field of view 610). In some embodiments, the application is initiated and can be run on the device (e.g., the wrist-wearable device 603, the AR device 700, and/or the HIPD 607) that detects the user input to initiate the application, and the device provides another device operational data to cause the presentation of the messaging application. For example, the wrist-wearable device 603 can detect the user input to initiate a messaging application, initiate and run the messaging application, and provide operational data to the AR device 700 and/or the HIPD 607 to cause presentation of the messaging application. Alternatively, the application can be initiated and run at a device other than the device that detected the user input. For example, the wrist-wearable device 603 can detect the hand gesture associated with initiating the messaging application and cause the HIPD 607 to run the messaging application and coordinate the presentation of the messaging application.
Further, the user 602 can provide a user input provided at the wrist-wearable device 603, the AR device 700, and/or the HIPD 607 to continue and/or complete an operation initiated at another device. For example, after initiating the messaging application via the wrist-wearable device 603 and while the AR device 700 presents the messaging user interface 612, the user 602 can provide an input at the HIPD 607 to prepare a response (e.g., shown by the swipe gesture performed on the HIPD 607). The user 602's gestures performed on the HIPD 607 can be provided and/or displayed on another device. For example, the user 602's swipe gestures performed on the HIPD 607 are displayed on a virtual keyboard of the messaging user interface 612 displayed by the AR device 700.
In some embodiments, the wrist-wearable device 603, the AR device 700, the HIPD 607, and/or other communicatively coupled devices can present one or more notifications to the user 602. The notification can be an indication of a new message, an incoming call, an application update, a status update, etc. The user 602 can select the notification via the wrist-wearable device 603, the AR device 700, or the HIPD 607 and cause presentation of an application or operation associated with the notification on at least one device. For example, the user 602 can receive a notification that a message was received at the wrist-wearable device 603, the AR device 700, the HIPD 607, and/or other communicatively coupled device and provide a user input at the wrist-wearable device 603, the AR device 700, and/or the HIPD 607 to review the notification, and the device detecting the user input can cause an application associated with the notification to be initiated and/or presented at the wrist-wearable device 603, the AR device 700, and/or the HIPD 607.
While the above example describes coordinated inputs used to interact with a messaging application, the skilled artisan will appreciate upon reading the descriptions that user inputs 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, the AR device 700 can present to the user 602 game application data and the HIPD 607 can use a controller to provide inputs to the game. Similarly, the user 602 can use the wrist-wearable device 603 to initiate a camera of the AR device 700, and the user can use the wrist-wearable device 603, the AR device 700, and/or the HIPD 607 to manipulate the image capture (e.g., zoom in or out or apply filters) and capture image data.
Having discussed example AR systems, devices for interacting with such AR systems, and other computing systems more generally, devices and components will now be discussed in greater detail below. Some definitions of devices and components that can be included in some or all of the example devices discussed below are defined here for ease of reference. A skilled artisan will appreciate that certain types of the components described below may be more suitable for a particular set of devices and less suitable for a different set of devices. But subsequent references to the components defined here should be considered to be encompassed by the definitions provided.
In some embodiments discussed below, example devices and systems, including electronic devices and systems, will be discussed. Such example devices and systems are not intended to be limiting, and one of skill in the art will understand that alternative devices and systems to the example devices and systems described herein may be used to perform the operations and construct the systems and devices that are described herein.
As described herein, an electronic device is a device that uses electrical energy to perform a specific function. It can be any physical object that contains electronic components such as transistors, resistors, capacitors, diodes, and integrated circuits. Examples of electronic devices include smartphones, laptops, digital cameras, televisions, gaming consoles, and music players, as well as the example electronic devices discussed herein. As described herein, an intermediary electronic device is a device that sits between two other electronic devices and/or a subset of components of one or more electronic devices, which facilitates communication, and/or data processing, and/or data transfer between the respective electronic devices and/or electronic components.
In some embodiments, an AR system (e.g.,
The AR device 700 includes mechanical glasses components, including a frame 704 configured to hold one or more lenses (e.g., one or both lenses 706-1 and 706-2). One of ordinary skill in the art will appreciate that the AR device 700 can include additional mechanical components, such as hinges configured to allow portions of the frame 704 of the AR device 700 to be folded and unfolded, a bridge configured to span the gap between the lenses 706-1 and 706-2 and rest on the user's nose, nose pads configured to rest on the bridge of the nose and provide support for the AR device 700, earpieces configured to rest on the user's ears and provide additional support for the AR device 700, temple arms 705 configured to extend from the hinges to the earpieces of the AR device 700, and the like. One of ordinary skill in the art will further appreciate that some examples of the AR device 700 can include none of the mechanical components described herein. For example, smart contact lenses configured to present AR to users may not include any components of the AR device 700.
The lenses 706-1 and 706-2 can be individual displays or display devices (e.g., a waveguide for projected representations). The lenses 706-1 and 706-2 may act together or independently to present an image or series of images to a user. In some embodiments, the 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. While the AR device 700 includes two displays, embodiments of this disclosure may be implemented in AR devices with a single near-eye display (NED) or more than two NEDs.
The AR device 700 includes electronic components, many of which will be described in more detail below with respect to
The VR device 710 can include a housing 790 storing one or more components of the VR device 710 and/or additional components of the VR device 710. The housing 790 can be a modular electronic device configured to couple with the VR device 710 (or an AR device 700) and supplement and/or extend the capabilities of the VR device 710 (or an AR device 700). For example, the housing 790 can include additional sensors, cameras, power sources, and processors (e.g., processor 748A-2). to improve and/or increase the functionality of the VR device 710. Examples of the different components included in the housing 790 are described below in reference to
Alternatively, or in addition, in some embodiments, the head-wearable device, such as the VR device 710 and/or the AR device 700, includes, or is communicatively coupled to, another external device (e.g., a paired device), such as an HIPD 607 and/or an optional neckband. The optional neckband can couple to the head-wearable device via one or more connectors (e.g., wired or wireless connectors). The head-wearable device and the neckband can operate independently without any wired or wireless connection between them. In some embodiments, the components of the head-wearable device and the neckband are located on one or more additional peripheral devices paired with the head-wearable device, the neckband, or some combination thereof. Furthermore, the neckband is intended to represent any suitable type or form of paired device. Thus, the following discussion of neckbands may also apply to various other paired devices, such as smartwatches, smartphones, wrist bands, other wearable devices, hand-held controllers, tablet computers, or laptop computers.
In some situations, pairing external devices, such as an intermediary processing device (e.g., an HIPD device 607, an optional neckband, and/or a wearable accessory device) with the head-wearable devices (e.g., an AR device 700 and/or a VR device 710) enables the head-wearable devices to achieve a similar form factor of a pair of glasses while still providing sufficient battery and computational power for expanded capabilities. Some, or all, of the battery power, computational resources, and/or additional features of the head-wearable devices can be provided by a paired device or shared between a paired device and the head-wearable devices, thus reducing the weight, heat profile, and form factor of the head-wearable device overall while allowing the head-wearable device to retain its desired functionality. For example, the intermediary processing device (e.g., the HIPD 607) can allow components that would otherwise be included in a head-wearable device to be included in the intermediary processing device (and/or a wearable device or accessory device), thereby shifting a weight load from the user's head and neck to one or more other portions of the user's body. In some embodiments, the intermediary processing device has a larger surface area over which to diffuse and disperse heat to the ambient environment. Thus, the intermediary processing device can allow for greater battery and computational capacity than might otherwise have been possible on the head-wearable devices, standing alone. Because weight carried in the intermediary processing device can be less invasive to a user than weight carried in the head-wearable devices, a user may tolerate wearing a lighter eyewear device and carrying or wearing the paired device for greater lengths of time than the user would tolerate wearing a heavier eyewear device standing alone, thereby enabling an AR environment to be incorporated more fully into a user's day-to-day activities.
In some embodiments, the intermediary processing device is communicatively coupled with the head-wearable device and/or to other devices. The other devices may provide certain functions (e.g., tracking, localizing, depth mapping, processing, and/or storage) to the head-wearable device. In some embodiments, the intermediary processing device includes a controller and a power source. In some embodiments, sensors of the intermediary processing device are configured to sense additional data that can be shared with the head-wearable devices in an electronic format (analog or digital).
The controller of the intermediary processing device processes information generated by the sensors on the intermediary processing device and/or the head-wearable devices. The intermediary processing device, such as an HIPD 607, can process information generated by one or more of its sensors and/or information provided by other communicatively coupled devices. For example, a head-wearable device can include an IMU, and the intermediary processing device (a neckband and/or an HIPD 607) can compute all inertial and spatial calculations from the IMUs located on the head-wearable device. Additional examples of processing performed by a communicatively coupled device, such as the HIPD 607.
AR systems may include a variety of types of visual feedback mechanisms. For example, display devices in the AR devices 700 and/or the VR devices 710 may 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 screen. AR systems may include a single display screen for both eyes or may provide a display screen for each eye, which may allow for additional flexibility for varifocal adjustments or for correcting a refractive error associated with the user's vision. Some AR systems also include optical subsystems having one or more lenses (e.g., conventional concave or convex lenses, Fresnel lenses, or adjustable liquid lenses) through which a user may view a display screen. In addition to or instead of using display screens, some AR systems include one or more projection systems. For example, display devices in the AR device 700 and/or the VR device 710 may include micro-LED projectors that project light (e.g., using a waveguide) into display devices, such as clear combiner lenses that allow ambient light to pass through. The display devices may refract the projected light toward a user's pupil and may enable a user to simultaneously view both AR content and the real world. AR systems may also be configured with any other suitable type or form of image projection system. As noted, some AR systems may, instead of blending an artificial reality with actual reality, substantially replace one or more of a user's sensory perceptions of the real world with a virtual experience.
While the example head-wearable devices are respectively described herein as the AR device 700 and the VR device 710, either or both of the example head-wearable devices described herein can be configured to present fully immersive VR scenes presented in substantially all of a user's field of view, additionally or alternatively to, subtler augmented-reality scenes that are presented within a portion, less than all, of the user's field of view.
In some embodiments, the AR device 700 and/or the VR device 710 can include haptic feedback systems. The haptic feedback systems may provide various types of cutaneous feedback, including vibration, force, traction, shear, texture, and/or temperature. The haptic feedback systems may also provide various types of kinesthetic feedback, such as motion and compliance. The haptic feedback can be implemented using motors, piezoelectric actuators, fluidic systems, and/or a variety of other types of feedback mechanisms. The haptic feedback systems may be implemented independently of other AR devices, within other AR devices, and/or in conjunction with other AR devices (e.g., wrist-wearable devices that may be incorporated into headwear, gloves, body suits, handheld controllers, environmental devices (e.g., chairs or floormats), and/or any other type of device or system, such as a wrist-wearable device 603, an HIPD 607, smart textile-based garment), and/or other devices described herein.
In some embodiments, the computing system 720 and/or the optional housing 790 can include one or more peripheral interfaces 722A and 722B, one or more power systems 742A and 742B (including charger input 743, PMIC 744, and 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 memory 750A and 750B, which can all be in electronic communication with each other. For example, the one or more processors 748A and/or 748B can be configured to execute instructions stored in the memory 750A and/or 750B, which can cause a controller of the one or more controllers 746A and/or 746B to cause operations to be performed at one or more peripheral devices of the peripherals interfaces 722A and/or 722B. In some embodiments, each operation described can occur based on electrical power provided by the power system 742A and/or 742B.
In some embodiments, the peripherals interface 722A can include one or more devices configured to be part of the computing system 720, many of which have been defined above. For example, the peripherals interface can include one or more sensors 723A. Some example sensors include one or more coupling 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, the sensors 723A further include depth sensors 767, light sensors 768, and/or any other types of sensors defined above or described with respect to any other embodiments discussed herein.
In some embodiments, the peripherals interface can 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 Wi-Fi and/or Bluetooth devices 733, one or more buttons 734 (e.g., including buttons that are slidable or otherwise adjustable), one or more displays 735A, one or more speakers 736A, one or more microphones 737A, one or more cameras 738A (e.g., including the first camera 739-1 through nth camera 739-n, which are analogous to the left camera 739A and/or the right camera 739B), one or more haptic devices 740, and/or any other types of peripheral devices defined above or described with respect to any other embodiments discussed herein.
The head-wearable devices can include a variety of types of visual feedback mechanisms (e.g., presentation devices). For example, display devices in the AR device 700 and/or the 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 types of display screens. The head-wearable devices can include a single display screen (e.g., configured to be seen by both eyes) and/or can provide separate display screens for each eye, which can allow for additional flexibility for varifocal adjustments and/or for correcting a refractive error associated with the user's vision. Some embodiments of the head-wearable devices also include optical subsystems having one or more lenses (e.g., conventional concave or convex lenses, Fresnel lenses, or adjustable liquid lenses) through which a user can view a display screen. For example, respective displays 735A can be coupled to each of the lenses 706-1 and 706-2 of the AR device 700. The displays 735A coupled to each of the lenses 706-1 and 706-2 can act together or independently to present an image or series of images to a user. In some embodiments, the AR device 700 and/or the VR device 710 includes a single display 735A (e.g., a near-eye display) or more than two displays 735A.
In some embodiments, a first set of one or more displays 735A can be used to present an augmented-reality environment, and a second set of one or more display devices 735A can be used to present a VR environment. In some embodiments, one or more waveguides are used in conjunction with presenting AR content to the user of the AR device 700 and/or the 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 are fully or partially integrated into the AR device 700 and/or the VR device 710. Additionally, or alternatively, to display screens, some AR systems include one or more projection systems. For example, display devices in the AR device 700 and/or the VR device 710 can include micro-LED projectors that project light (e.g., using a waveguide) into display devices, such as clear combiner lenses that allow ambient light to pass through. The display devices can refract the projected light toward a user's pupil and can enable a user to simultaneously view both AR content and the real world. The head-wearable devices can also be configured with any other suitable type or form of image projection system. In some embodiments, one or more waveguides are provided, additionally or alternatively, to the one or more display(s) 735A.
In some embodiments of the head-wearable devices, ambient light and/or a real-world live view (e.g., a live feed of the surrounding environment that a user would normally sec) can be passed through a display element of a respective head-wearable device presenting aspects of the AR system. In some embodiments, ambient light and/or the real-world live view can be passed through a portion, less than all, of an AR environment presented within a user's field of view (e.g., a portion of the AR environment co-located with a physical object in the user's real-world environment that is within a designated boundary (e.g., a guardian boundary) configured to be used by the user while they are interacting with the AR environment). For example, a visual user interface element (e.g., a notification user interface element) can be presented at the head-wearable devices, and an amount of ambient light and/or the real-world live view (e.g., 15%-50% of the ambient light and/or the real-world live view) can be passed through the user interface element, such that the user can distinguish at least a portion of the physical environment over which the user interface element is being displayed.
The head-wearable devices can include one or more external displays 735A for presenting information to users. For example, an external display 735A can be used to show a current battery level, network activity (e.g., connected, disconnected), current activity (e.g., playing a game, in a call, in a meeting, or watching a movie), and/or other relevant information. In some embodiments, the external displays 735A can be used to communicate with others. For example, a user of the head-wearable device can cause the external displays 735A to present a “do not disturb” notification. The external displays 735A can also be used by the user to share any information captured by the one or more components of the peripherals interface 722A and/or generated by the head-wearable device (e.g., during operation and/or performance of one or more applications).
The memory 750A can include instructions and/or data executable by one or more processors 748A (and/or processors 748B of the housing 790) and/or a memory controller of the one or more controllers 746A (and/or controller 746B of the housing 790). The memory 750A can 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 types of modules or components defined above or described with respect to any other embodiments discussed herein.
The data 760 stored in memory 750A can be used in conjunction with one or more of the applications and/or programs discussed above. The data 760 can include profile 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.
In some embodiments, the controller 746A of the head-wearable devices processes information generated by the sensors 723A on the head-wearable devices and/or another component of the head-wearable devices and/or communicatively coupled with the head-wearable devices (e.g., components of the housing 790, such as components of peripherals interface 722B). For example, the controller 746A can process information from the acoustic sensors 725 and/or image sensors 726. For each detected sound, the controller 746A can perform a direction of arrival (DOA) estimation to estimate a direction from which the detected sound arrived at a head-wearable device. As one or more of the acoustic sensors 725 detect sounds, the controller 746A can populate an audio data set with the information (e.g., represented by sensor data 762).
In some embodiments, a physical electronic connector can convey information between the head-wearable devices and another electronic device, and/or between one or more processors 748A of the head-wearable devices and the controller 746A. The information can be in the form of optical data, electrical data, wireless data, or any other transmittable data form. Moving the processing of information generated by the head-wearable devices to an intermediary processing device can reduce weight and heat in the eyewear device, making it more comfortable and safer for a user. In some embodiments, an optional accessory device (e.g., an electronic neckband or an HIPD 607) is coupled to the head-wearable devices via one or more connectors. The connectors can be wired or wireless connectors and can include electrical and/or non-electrical (e.g., structural) components. In some embodiments, the head-wearable devices and the accessory device can operate independently without any wired or wireless connection between them.
The head-wearable devices can include various types of computer vision components and subsystems. For example, the AR device 700 and/or the VR device 710 can include one or more optical sensors such as two-dimensional (2D) or three-dimensional (3D) cameras, ToF depth sensors, single-beam or sweeping laser rangefinders, 3D LiDAR sensors, and/or any other suitable type or form of optical sensor. A head-wearable device can process data from one or more of these sensors to identify a location of a user and/or aspects of the user's real-world physical surroundings, including the locations of real-world objects within the real-world physical surroundings. In some embodiments, the methods described herein are used to map the real world, to provide a user with context about real-world surroundings, and/or to generate interactable virtual objects (which can be replicas or digital twins of real-world objects that can be interacted with an AR environment), among a variety of other functions. For example,
The optional housing 790 can include analogous components to those describe above with respect to the computing system 720. For example, the optional housing 790 can include a respective peripherals interface 722B, including more or fewer components to those described above with respect to the peripherals interface 722A. As described above, the components of the optional housing 790 can be used to augment and/or expand on the functionality of the head-wearable devices. For example, the optional housing 790 can include respective sensors 723B, speakers 736B, displays 735B, microphones 737B, cameras 738B, and/or other components to capture and/or present data. Similarly, the optional housing 790 can include one or more processors 748B, controllers 746B, and/or memory 750B (including respective communication interface modules 753B, one or more graphics modules 754B, one or more AR processing modules 755B) that can be used individually and/or in conjunction with the components of the computing system 720.
The techniques described above in
Any data collection performed by the devices described herein and/or any devices configured to perform or cause the performance of the different embodiments described above in reference to any of the Figures, hereinafter the “devices,” is done with user consent and in a manner that is consistent with all applicable privacy laws. Users are given options to allow the devices to collect data, as well as the option to limit or deny collection of data by the devices. A user is able to opt in or opt out of any data collection at any time. Further, users are given the option to request the removal of any collected data.
It will be understood that, although the terms “first,” “second,” etc., may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another.
The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the claims. As used in the description of the embodiments and the appended claims, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It will be further understood that the terms “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.
As used herein, the term “if” can be construed to mean “when” or “upon” or “in response to determining” or “in accordance with a determination” or “in response to detecting,” that a stated condition precedent is true, depending on the context. Similarly, the phrase “if it is determined [that a stated condition precedent is true]” or “if [a stated condition precedent is true]” or “when [a stated condition precedent is true]” can be construed to mean “upon determining” or “in response to determining” or “in accordance with a determination” or “upon detecting” or “in response to detecting” that the stated condition precedent is true, depending on the context.
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the claims to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain principles of operation and practical applications, to thereby enable others skilled in the art.
This claims benefit of, and the priority to, U.S. Provisional Application Ser. No. 63/591,088, entitled “Charging Case with Retention Mechanism for Retaining and Facilitating Charging of Smart Glasses Via Nose Bridge of Smart Glasses” filed Oct. 17, 2023, the disclosure of which is incorporated in its entirety by this reference.
Number | Date | Country | |
---|---|---|---|
63591088 | Oct 2023 | US |