26. In the example depicted in FIG. 1, the server computing system 24 is an edge server of a large network via which the service provider 26 provides services, such as video services, data services, and/or the like, to thousands and/or millions of customers. The HMDD 12 may communicate with the server computing system 24 via one or more intermediate devices, such as a wireless gateway router (not shown), that are coupled to the network 22 via a communications medium (e.g., coaxial cable, fiber, etc.). In some examples, the HMDD 12 may be connected to a local area network (LAN) implemented by the wireless gateway router that is different than the network 22 to which the server computing system 24 is connected. In some examples, the HMDD 12 may communicate with the server computing system 24 via intermediate telecommunications equipment, such as 4G telecommunications equipment, 5G telecommunications equipment, satellite communications equipment, and/or the like.

The server computing system 24 may include a processor device 28 and a memory 30, such as any of the processor device(s) and/or memory device(s) described herein. For examples, the processor device 28 may include any computing or electronic device capable of executing software instructions to implement the functionality described herein, and the memory 30 may be or otherwise include any device(s) capable of storing data, including, but not limited to, volatile memory (random access memory, etc.), non-volatile memory, storage device(s) (e.g., hard drive(s), solid state drive(s), etc.).

As noted above, the HMDD 12 may be worn, for instance, on a head of the user 14 and may be operable to provide VR functionality and/or AR functionality to the user 14. In particular, the HMDD 12 may include a display device 32. The display device 32 may include an active display, such as a Liquid Crystal on Silicon (LCOS) display, a Light-Emitting Diode (LED) display, an Organic Light-Emitting Diode (OLED) display, a Liquid Crystal Display (LCD), an Active Matrix Organic Light-Emitting Diode (AMOLED) display, a flexible display, a 3D display, a Plasma Display Panel (PDP), a Cathode Ray Tube (CRT) display, and/or the like, on which imagery is presented. It should be understood that any suitable display device 32 may be used without deviating from the scope of the present disclosure.

The HMDD 12 may further include one or more sensors 34. For instance, in some examples, the HMDD 12 may include an inertial measurement unit sensor (IMU) 36. The IMU 36 may be operable to generate data (e.g., roll data, yaw data, pitch data, etc.), and the processor device 16 may use the data generated by the IMU 36 to determine in which direction the HMDD 12 is oriented and, thus, what real-word objects are within a field of view (FOV) of the HMDD 12. The HMDD 12 may further include one or more biometric sensors 38, such as any suitable biometric sensor operable to obtain biometric data associated with the user 14. The HMDD 12 may further include one or more depth sensors 40 (e.g., depth cameras). The depth sensors 40 may generate depth data, and the processor device 16 may use the depth data to generate a spatial map of the physical space surrounding the user 14. The HMDD 12 may further include one or more optical sensors 42 (e.g., one or more built-in interior cameras) operable to track the eyes of the user 14 when the user 14 is wearing the HMDD 12.

The HMDD 12 may further include one or more XR applications 44, such as any suitable application that allows the HMDD 12 to implement and provide (to the user 14) a computer-generated digital environment, such as an XR environment (e.g., AR environment, VR environment, MR environment, etc.). As described herein, the computer-generated digital environment (e.g., AR environment, VR environment, etc.) provided by the HMDD 12 to the user 14 includes scenes, objects, etc. that appear to be real which, in turn, makes the user 14 feel as if they are immersed in their surroundings. For instance, the one or more XR applications 44 may be related to, by way of non-limiting example, gaming, social media, medicine, vehicles, military and space applications, and/or the like. In some examples, the server computing system 24 may also include the one or more XR applications 44.

The HMDD 12 may further include one or more XR platforms 46, such as any suitable AR platform, VR platform, MR platform, and/or the like, that hosts and/or provides the XR applications 44 to the HMDD 12 (and, in some examples, to the server computing system 24). In some examples, the server computing system 24 may also include the one or more XR platforms 46.

The HMDD 12 may further include an input device 48 that is operable to receive an input (e.g., feedback) from the user 14 (e.g., via a user-selectable control). The input device 48 may be used by the user 14 to provide an input (e.g., a voice input, a touch input, a gesture input, a click via a mouse or a remote controller, etc.) to the HMDD 12 to execute any of the processes described herein. By way of non-limiting example, the input device 48 may include one or more of a keyboard (e.g., a physical keyboard, virtual keyboard, etc.), a mouse, a joystick, a button, a switch, an electronic pen or stylus, a gesture recognition sensor (e.g., to recognize gestures of a user including movements of a body part), an input sound device or voice recognition sensor (e.g., a microphone to receive a voice command), a track ball, a remote controller, a portable (e.g., a cellular or smart) phone, a dial, a digital crown, and/or the like. The input device 48 may be integrated with the HMDD 12 and/or may be communicatively coupled to the HMDD 12. For example, the user 14 may hold a remote controller having buttons, switches, a keyboard, etc., to provide a user input for executing a function of the HMDD 12, where the user input may be transmitted from the remote controller to the HMDD 12 in a wired and/or a wireless manner. The input device 48 may also be embodied by a touch-sensitive display device having, for instance, a touchscreen capability. It should be understood that any suitable input device 48 may be used without deviating from the scope of the present disclosure. In some examples, the user 14 may adjust an immersion level associated with the HMDD 12 via the input device 48. For instance, the HMDD 12 may be configured in a plurality of immersion levels, such as a VR immersion level (e.g., the user 14 immersed in a VR environment), an MR immersion level (e.g., the user 14 immersed in an MR environment), an AR immersion level (e.g., the user 14 immersed in an AR environment), and/or the like.

The HMDD 12 may further include an output device 50 that is operable to provide an output to the user 14. The output device 50 may be any suitable output device and may be operable to provide various indications, alerts, notifications, etc. to the user 14 and/or other entities in the physical surroundings of the user 14. By way of non-limiting example, the output device 50 may be one or more of an audio device (e.g., speakers), a haptic device operable to provide haptic feedback to the user 14, a light source (e.g., one or more LEDs) operable to provide visual feedback to the user 14, and/or the like. In some examples, the output device 50 may be an outward-facing display device, such as a display device facing in a similar direction as the FOV associated with the HMDD 12. It should be understood that any suitable output device 50 may be used without deviating from the scope of the present disclosure.

The HMDD 12 may further include one or more cameras 52. The one or more cameras 52 may include any suitable imaging sensor, such as, by way of non-limiting example, a complementary metal-oxide-semiconductor (CMOS), a charge-coupled device (CCD), and/or the like. In some examples, the one or more cameras 52 may be externally mounted on the HMDD 12 and may be oriented at different angles with respect to one another (e.g., a forward direction, a rearward direction, an oblique direction, etc.) so that images from the different directions can be captured by the one or more cameras 52. The one or more cameras 52 may be any suitable image-capture device operable to capture, detect, and/or recognize a behavior, figure, expression, status, etc. of the user 14 and/or the physical environment of the user 14.

The HMDD 12 may further include a communications interface 54, such as any suitable communications interface for communicating (via the network 22) with one or more computing devices, such as the server computing system 24, one or more client computing devices 56 (e.g., mobile phone, tablet device, laptop, desktop, etc.).

The HMDD 12 may further include a first adjustable lens 58-1 and a second adjustable lens 58-2 (collectively, “adjustable lens(es) 58”) proximate the display device 32. The adjustable lenses 58 may be integral with and/or insertable to the HMDD 12. The adjustable lenses 58 may be between the user 14 and the display device 32 along an optical path of the eyes of the user 14 (e.g., having an optical path directed towards the user 14). As will be discussed in greater detail below, the adjustable lenses 58 may include a first active medium 60-1 (e.g., first adjustable lens 58-1) and a second active medium 60-2 (e.g., second adjustable lens 58-2) (collectively, active medium(s) 60). In some examples, the adjustable lenses 58 may be electro-optical lenses that include an active liquid crystal medium (e.g., active medium 60) which, when an external stimulus (e.g., electrical stimuli) is applied thereto (e.g., by processor device(s) 16), adjusts (e.g., changes) one or more optical characteristics (e.g., refractive index, lens curvature, etc.) of the adjustable lenses 58. In some examples, the adjustable lenses 58 may be opto-mechanical lenses that include an active fluid medium within a flexible membrane (e.g., active medium 60) which, when an external stimulus (e.g., mechanical stimuli) is applied thereto (e.g., by processor device(s) 16), adjusts (e.g., changes) one or more optical characteristics (e.g., refractive index, lens curvature, etc.) of the adjustable lenses 58.

The HMDD 12 may further include a power source 62, such as, by way of non-limiting example, any suitable internal and/or external battery. It should be understood that, although depicted as a battery in Figure 1, the HMDD 12 may include any suitable power source 62 without deviating from the scope of the present disclosure. The power source 62 and, hence, the HMDD 12 may be activated in response to detecting a power-on trigger. For instance, in some examples, the HMDD 12 may include an input device (e.g., input device 48) that, when, activated, provides a power-on trigger to the HMDD 12 and, in response, initiates a boot process of the HMDD 12. In some examples, the HMDD 12 may include one or more sensors (e.g., sensor(s) 34) that provide a power-on trigger to the HMDD 12 in response to, by way of non-limiting example, detecting a gesture of the user 14, detecting a change in position (e.g., via IMU 36) of the HMDD 12, and/or the like. It should be understood that, as used herein, a “power-on trigger” refers to any trigger event that initiates a boot process in the HMDD 12, such as when the HMDD 12 turns on, changes from an “idle” state to a ”normal” operating state, changes from a “low-power” operating state to a “normal” operating state, and/or the like.

The HMDD 12 may perform any suitable boot process that initializes and configures the HMDD 12 and its internal components such that the HMDD 12 is operable to provide AR and/or VR services to the user 14. For instance, in some examples, the HMDD 12 may perform an internal self-check to ensure the various components described herein are functioning properly. In some examples, the HMDD 12 may obtain (e.g., from memory 18, server computing system 24, etc.) and load firmware file(s), operating system(s), and/or the like. In some examples, the HMDD 12 may initialize and configure the display device 32. In some examples, the HMDD 12 may establish a connection link with the one or more client computing devices 56. In some examples, the HMDD 12 may load (e.g., from memory 18) and/or synchronize with (e.g., from server computing system 24) the one or more XR applications 44, the one or more XR platforms 46, and/or the like.

In some examples, the HMDD 12 may perform one or more user authentication processes to determine and/or confirm an identify of the user 14. For instance, the HMDD 12 (e.g., via the one or more sensors 34, the one or more cameras 52, etc.) may obtain biometric authentication data 64 associated with the user 14, such as, by way of non-limiting example, eye tracking data, facial recognition data, one or more images of the user 14, and/or the like. The HMDD 12 may determine and, if applicable, confirm an identity of the user 14 based on the biometric authentication data 64. It should be understood that the biometric authentication data 64 may include any data from which the identity of the user 14 may be determined, confirmed, and/or the like.

In some examples, the HMDD 12 may obtain a user profile 66 associated with the user 14. In some examples, the HMDD 12 may obtain the user profile 66 from the memory 18. In some examples, the server computing system 24 may store the user profiles associated with each user serviced by the service provider 26. In such examples, the HMDD 12 may obtain the user profile 66 from the server computing system 24 via the network 22. The user profile 66 may identify and include preferences of the user 14, system parameters 68 associated with the HMDD 12, operational data and preferences associated with one or more mobile applications, and/or the like. For instance, the HMDD 12 may be configured based on the system parameters 68 of the user profile 66.

In some examples, the HMDD 12 may dynamically and intelligently determine and configure a vision setting 70 for the adjustable lenses 58, such as a first vision setting 70-1 for the first adjustable lens 58-1 and a second vision setting 70-2 for the second adjustable lens 58-2. More particularly, the HMDD 12 may determine a visual acuity metric 72 for the user 14. The visual acuity metric 72 may characterize and/or otherwise be associated with a quality and/or a clarity of a vision of the user 14. The HMDD 12 may adjust and/or configure one or more optical characteristics 74 (e.g., refractive index, lens curvature, etc.) of the adjustable lenses 58 (e.g., first optical characteristic 74-1 of the first adjustable lens 58-1, second optical characteristic 74-2 of the second adjustable lens 58-2) based on the visual acuity metric 72 associated with the user 14.

By way of non-limiting example, the HMDD 12 may provide a user-selectable control to the user 14. In some examples, the HMDD 12 may provide the user-selectable control to the user 14 via the display device 32 as an interactive user interface (UI) element (e.g., slider) having a range 76 of different vision settings 78. By way of non-limiting example, the range 76 of different vision settings 78 may include a farsightedness vision setting 78-1 corresponding to a configuration of the adjustable lenses 58 operable to compensate for hyperopia refractive error (e.g., farsightedness), a plurality of intermediate vision settings 78-2 (e.g., at least one of which corresponding to a configuration of the adjustable lenses 58 operable to compensate for no refractive error), and a nearsightedness vision setting 78-3 corresponding to a configuration of the adjustable lenses operable to compensate for myopia refractive error (e.g., nearsightedness). The user 14 may select one of the different vision settings 78 as a selected vision setting via the input device 48, and the HMDD 12 may receive user input data 80 from the input device 48 characterizing the selected vision setting of the range 76 of different vision setting 78. The HMDD 12 may determine the visual acuity metric 72 associated with the user 14 based on the user input data 80 characterizing the selected vision setting.

In some examples, the HMDD 12 may provide a first user-selectable control to the user 14 via the display device 32. The first user-selectable control may include a range of different vision settings for the first adjustable lens 58-1, such as the range 76 described above. The HMDD 12 may also provide a second user-selectable control to the user 14 via the display device 32. The second user-selectable control may include a range of different vision setting for the second adjustable lens 58-2, such as the range 76 described above. The user 14 may individually select a vision setting for each of the first adjustable lens 58-1 and the second adjustable lens 58-2 in a similar manner as described above. The HMDD 12 may receive first user input data 80-1 (e.g., characterizing a selected vision setting for the first adjustable lens 58-1) and second user input data 80-2 (e.g., characterizing a selected vision setting for the second adjustable lens 58-2). The HMDD 12 may determine the visual acuity metric 72 associated with the user 14 based on the first user input data 80-1 and the second user input data 80-2. The HMDD 12 may adjust a first optical characteristic 74-1 (e.g., refractive index, lens curvature, etc.) of the first adjustable lens 58-1 based on the first user input data 80-1 (e.g., characterizing a selected vision setting for the first adjustable lens 58-1); the HMDD 12 may adjust a second optical characteristic 74-2 (e.g., refractive index, lens curvature, etc.) of the second adjustable lens 58-2 based on the second user input data 80-2 (e.g., characterizing a selected vision setting for the second adjustable lens 58-2).

As another non-limiting example, the HMDD 12 (e.g., via the one or more sensors 34) may obtain biometric data 82 associated with the user 14. In some examples, the biometric data 82 may characterize a refractive error of the user 14. For instance, in some examples, the HMDD 12 may include a refractometer 84 in an optical path associated with the user 14 (e.g., having an optical path directed towards the user 14). The refractometer 84 may obtain biometric data 82 characterizing the refractive error of the user 14. In such examples, the HMDD 12 may determine the visual acuity metric 72 associated with the user 14 based on the biometric data 82 obtained by the refractometer 84.

As described herein, the HMDD 12 may adjust and/or configure the one or more optical characteristics 74 (e.g., refractive index, lens curvature, etc.) of the adjustable lenses 58 (e.g., first adjustable lens 74-1 and second adjustable lens 74-2) by applying external stimuli (e.g., electrical stimuli, mechanical stimuli, etc.) to an active medium 60 of the adjustable lenses 58. As an illustrative example, the adjustable lenses 58 may be electro-optical lenses having an active medium 60 that includes liquid crystals. In such examples, the HMDD 12 may provide (e.g., via a controller (not shown), processor device 16, etc.) electrical stimuli to the active medium 60 to adjust the refractive index and/or the lens curvature of the adjustable lenses 58.

As another illustrative example, the adjustable lenses 58 may be opto-mechanical lenses having an active medium 60 that includes a fluid (e.g., fluid silicon, liquid silicone, etc.) within a flexible membrane. In such examples, the HMDD 12 may provide (e.g., via a controller (not shown), processor device 16, etc.) mechanical stimuli to the active medium 60 to adjust the refractive index and/or the lens curvature of the adjustable lenses 58. For instance, in some examples, a controller (e.g., processor device 16) of the HMDD 12 may be coupled to a motor (not shown), which may be operable to provide pressure (e.g., a mechanical stimuli) to the active medium 60 which, in turn, adjusts the refractive index and/or lens curvature of the adjustable lenses 58.

In some examples, the HMDD 12 may fine-tune the vision setting 70 for the adjustable lenses 58. For instance, subsequent to adjusting the optical characteristics 74 of the adjustable lenses 58, the HMDD 12 may receive user feedback data 86. The user feedback data 86 may be provided by the user 14 and received by the HMDD 12 in any suitable manner, such as in a similar manner as described above with reference to the user input data 80. The user feedback data 86 may characterize a tuned vision setting 88 for the adjustable lenses 58. The user 14 may have an increased vision quality and/or vision clarity with the tuned vision setting 88 relative to the vision setting 70. The HMDD 12 may tune (e.g., adjust) the optical characteristic 74 of the adjustable lenses 58 based on the tuned vision setting 88.

Each of the features of the HMDD 12 described above may be operatively connected to one another via a system bus (not shown). Likewise, each of the features of the server computing system 24 described above may be operatively connected to one another via a system bus (not shown). For instance, the system bus (not shown) of the HMDD 12 and/or the system bus (not shown) of the server computing system 24 may be any of several types of bus structures that may further interconnect to a memory bus (with or without a memory controller), a peripheral bus, and/or a local bus using any of a variety of commercially available bus architectures.

The HMDD 12 and server computing system 24 of FIG. 1 and the constituent elements thereof may encompass any one of known digital logic elements, semiconductor circuits, processing cores, and/or memory structures, among other elements, or combinations thereof. Examples described herein are not restricted to any particular arrangement of elements, and it is to be understood that some embodiments of the HMDD 12 may include more or fewer elements than illustrated in FIG. 1. For example, the processor device 16 (of the HMDD 12) and/or the processor device 28 (of the server computing system 24) may further include one or more functional units, instruction caches, unified caches, memory controllers, interconnect buses, and/or additional memory devices, caches, and/or controller circuits, which are omitted from FIG. 1 for the sake of clarity.

FIGS. 2A-2D are a sequence diagrams illustrating messages communicated between and actions taken by certain components illustrated in FIG. 1 to perform dynamic and adaptive vision correction in a head-mounted display device (HMDD) according to one implementation of the present disclosure. FIGS. 2A-2D will be discussed in conjunction with FIG. 1.

Referring to FIG. 2A, the user 14 provides a power-on trigger to the HMDD 12 by, for example, providing a user in put to the input device 48 (FIG. 2A, step 100). In response, the HMDD 12 (e.g., via processor device 16) initiates a boot process (FIG. 2A, step 102). The HMDD 12 (e.g., processor device 16) obtains sensor data (e.g., biometric data 80) from the sensors 34 (e.g., biometric sensor(s) 38, optical sensor(s) 42) (FIG. 2A, step 104). Based on the sensor data, the HMDD 12 (e.g., processor device 16) determines whether the user 14 is wearing the HMDD 12 (FIG. 2A, step 106).

In response to determining the user 14 is wearing the HMDD 12 (FIG. 2A, step 108), the HMDD 12 (e.g., processor device 16) obtains biometric authentication data 64 associated with the user 14 from the sensors 34 (FIG. 2A, step 110). The HMDD 12 (e.g., processor device 16) determines the identity of the user 14 based on the biometric authentication data 64 (FIG. 2A, step 112). In response to (and confirming) the identity of the user 14, the HMDD 12 (e.g., processor device 16) obtains the user profile 66 associated with the user 14 (FIG. 2A, step 114). In some examples, the user profile 66 may be stored in and retrieved from the memory 18. In some examples, the user profile 66 may be stored in and obtained from the client computing device(s) 56. In some examples, the user profile 66 may be stored in and retrieved from the server computing system 24.

The HMDD 12 (e.g., processor device 16) configures its internal components (e.g., display device(s) 32, sensor(s) 34, XR application(s) 44, XR platform(s) 46, input device(s) 48, output device(s) 50, camera(s) 52, communications interface(s) 54, etc.) based on the system parameters 68 of the user profile 66 (FIG. 2A, step 116). The HMDD 12 (e.g., processor device 16) enables and/or configures the adjustable lenses 58 in a neutral configuration (e.g., operable to compensate for no refractive error in the user 14), such as in one of the plurality of intermediate vision settings 78-2 (FIG. 2A, step 118).

Subsequent to determining the user 14 is wearing the HMDD 12, the HMDD 12 (e.g., processor device 16) determines a visual acuity metric 72 associated with the user 14 (FIG. 2A, step 120). In some examples, the HMDD 12 (e.g., processor device 16) may determine a visual acuity metric 72 for each eye of the user 14 (e.g., visual acuity metric 72-1, visual acuity metric 72-2).

A first non-limiting example and a second non-limiting example of the HMDD 12 determining the visual acuity metric 72 for the user is depicted in FIGS. 2B and 2C, respectively.

As one illustrative example, referring now to FIG. 2B, the HMDD 12 (e.g., via display device 32) provides a user-selectable control (e.g., interactive user interface (UI) slider) to the user 14 that includes the range of different vision settings 78 for the adjustable lenses 58 (FIG. 2B, step 122). The HMDD 12 (e.g., via input device(s) 48) receives user input data 80 associated with the user-selectable control (e.g., associated with a user selection by the user 14) that characterizes a selected vision setting (e.g., vision setting 70) of the range of different vision settings 78 (FIG. 2B, step 124). The HMDD 12 (e.g., processor device 16) determines the visual acuity metric 72 associated with the user 14 based on the user input data 80 (FIG. 2B, step 126).

As another illustrative examples, referring now to