EYE TRACKING SYSTEMS AND METHODS FOR NEAR-EYE-DISPLAY (NED) DEVICES

BACKGROUND

Near-Eye-Display (NED) systems superimpose computer-generated images (“CG images”) over a user's view of a real-world environment. For example, a NED system may generate composite views to enable a user to visually perceive a CG image superimposed over a physical object that exists within the real-world environment. In some instances, a user's experience is highly dependent on the NED system accurately tracking the user's eye movements. For example, in some instances the NED system may track an interpupillary distance (IPD) of the user. One reason for tracking IPD is so that CG images can be rendered at a suitable separation within the user's field of view. Additionally, or alternatively, the NED system may track a depth at which the user is focusing within the real-world environment. One reason for tracking the user's focal depth (e.g., accommodation plane) is because the user may experience motion sickness or vertigo if CG images are rendered at a depth that is different (i.e., closer to/farther from the user) than that which the user is focusing.

Some conventional eye tracking systems illuminate the user's eyes with near infrared light and then track the user's eye movements by observing reflective patterns that are formed from the near infrared light. For example, upon being illuminated with near infrared light, the eyes may form one or more first Purkinje reflections (e.g., “glints”) that are distributed around the iris. Conventional eye tracking systems track eye movements (e.g., the user's gaze direction) by analyzing the location(s) of these Purkinje reflections with respect to the center of the pupil.

It is with respect to these and other considerations that the disclosure made herein is presented.

SUMMARY

Technologies described herein provide eye tracking systems and methods for Near-Eye-Display (NED) devices. Generally described, an exemplary eye tracking system for a NED device includes sensors (e.g., CMOS sensors) that are directed toward a user's eyes. The sensors are angularly offset from the user's eyes in a manner that causes circular features (e.g., irises and/or pupils) of the user's eyes to appear elliptical within sensor planes that correspond to the individual sensors. For example, it can be appreciated that both an iris and a pupil of an eye will appear circular when the eye is looked at straight on (i.e., perpendicular to an optical axis of the eye's lens). It can further be appreciated that a circular object will appear to be elliptical when observed from an angle that is angularly offset from (e.g., not normal to) a plane on which the circular object resides. The eye tracking systems and methods disclosed herein exploit these principles to track movements of the user's eyes with a higher degree of accuracy than conventional eye tracking systems.

Various embodiments disclosed herein track the user's interpupillary distance (IPD) in real time while the NED device is operating—rather than merely determining the user's IPD at predetermined intervals as conventional eye tracking systems do. Additionally, or alternatively, various embodiments disclosed herein track the user's visual axes—rather than merely tracking the user's optical axis and/or line of sight as conventional eye tracking systems do. Then, by determining a vergence in space between the visual axes for each of the user's two eyes, such embodiments calculate the depth in space at which the user is focused with a significantly higher degree of accuracy than conventional eye tracking systems. Accordingly, the disclosed eye tracking systems and methods represents a substantial advance toward preventing a user of a NED device from experiencing motion sickness or vertigo due to CG images being generated in front of or behind the user's accommodation plane (e.g., focal plane).

In an exemplary embodiment, an eye tracking system includes one or more sensors that generate eye tracking data associated with one or more substantially circular features of one or both of a user's eyes. Exemplary such “substantially” circular features include pupils and irises which are generally very close to circular and, therefore, may be modeled as perfect circles for purposes of the calculations described herein. The individual sensors have corresponding sensor planes that are angularly skewed with respect to the planes on which the circular features reside (e.g., an Iris-Pupil Plane). Based on the eye tracking data, the eye tracking system determines ellipse parameters for ellipses that result from these sensor planes being angularly skewed from the Iris-Pupil Planes. In some embodiments, the eye tracking system may track only one of the user's eyes. In other embodiments, the eye tracking system may track both of the user's eyes. In embodiments that track both eyes, the eye tracking system may determine ellipse parameters that define: (i) first ellipses that correspond to projections of an iris and/or pupil of a right eye onto a first sensor plane; and (ii) second ellipses that correspond to projections of an iris and/or pupil of a left eye onto a second sensor plane. The projections of each of the iris(es) and/or pupil(s) onto the corresponding sensor plane(s) may in some embodiments pass through a predetermined point such as, for example, an entrance pupil of each corresponding sensor.

Based on the ellipse parameters, the eye tracking system may then generate propagation data that defines three-dimensional (3D) propagations of the ellipses. The 3D propagation data may define a series of lines (e.g., rays) that extend from individual ellipses that are detected on the sensor plane. For example, individual lines of the series of lines may begin on the sensor plane at individual points along a perimeter of a detected ellipse. The individual lines may all commonly propagate from the sensor plane through a predetermined point toward the user's eyes. In some implementations, the predetermined point through which all lines of a particular 3D propagation pass is an entrance pupil of a corresponding sensor. Since all of the lines of these 3D propagations extend from the ellipse through the predetermined point, the 3D propagations may be graphically represented as an elliptic cone that extends from the predetermined point toward the eye.

The eye tracking system may utilize the propagation data to determine pupil orientation parameters that define various characteristics of the user's eye(s). Exemplary pupil orientation parameters may define optical axes for one or both of the user's eyes (e.g., an axis of an eye lens), visual axes for one or both of the user's eyes (e.g. axes that extend from the fovea through the lens and into the real-world environment), rotational angles of the user's eyes (e.g. an angle of rotation between a semi-axis of an ellipse and a horizontal axes of the sensor), Iris-Pupil Planes of the user's eyes (e.g. a plane on which the pupil resides), center points for the user's eyes (e.g., a point at which the optical axis (or alternatively the visual axis) intersects the Iris-Pupil plane). Additionally, or alternatively, the pupil orientation parameters may define various other characteristics of the user's eyes.

As described in detail below, the eye tracking system may utilize the pupil orientation parameters to continually determine of a current (e.g., real time) IPD for a user, i.e. while the NED device is operating. For example, the eye tracking system may dynamically track the center points for each of the user's two eyes and continually calculate and re-calculate the user's interpupillary distance in near real time. Additionally, or alternatively, the eye tracking system may utilize the pupil orientation parameters to determine a vergence of two visual axes (which are different than the optical axis) of the user. For example, the eye tracking system may dynamically track the visual axis of each of the user's two eyes and continually calculate a location in space at which the distance between these two visual axes is the smallest. In various implementations, the visual axes are determined based on visual axis offset data that indicates at least an angular relationship between the optical axis and the visual axis. As described in detail below, this visual axis offset data may be specifically custom to a particular user and may be determined through a user-specific calibration process. It can be appreciated that although vergence is generally understood as the “point” at which the user's two visual axis intersect, in a practical sense these axes rarely mathematically intersect but rather simply become the closest at the user's accommodation plane. Thus, as described herein the vergence of the visual axes may be determined by calculating a point in space at which the separation between the two visual axes is the least (i.e., wherever the two axes become closest together).

In some embodiments, the pupil orientation parameters may be determined by analyzing the propagation data with respect to an ocular rotation model to calculate an orientation of the Iris-pupil plane for an eye, a distance from a predetermined point of the sensor to a center of an entrance pupil of the eye, and/or a radius of the pupil of the eye. The ocular rotation model may be usable to model rotation of a circular feature of an eye around that eye's center of rotation. For example, the ocular rotation model may be (or be based on) an equation that defines coordinates for a circle of a particular radius as that circle is rotated around the center of an eye. It can be appreciated that a circle of a specific radius will mathematically match the “elliptical” 3D propagations only at a single plane. Therefore, utilizing various error minimization algorithms to analyze the propagation data with respect to the ocular rotation model may yield the Iris-Pupil plane's specific location in space and the circular pupil's specific location and rotation thereon. Although some specific error minimization algorithms are described herein, such descriptions are provided for exemplary purposes only and other error minimization algorithms may also be used.

It should be appreciated that any reference to “first,” “second,” etc. items and/or abstract concepts within the Summary and/or Detailed Description is not intended to and should not be construed to necessarily correspond to any reference of “first,” “second,” etc. elements of the claims. In particular, within the Summary and/or Detailed Description, items and/or abstract concepts such as, for example, three-dimensional (3D) propagations and/or circular features of eyes and/or sensor entrance pupils may be distinguished by numerical designations without such designations corresponding to the claims or even other paragraphs of the Summary and/or Detailed Description. For example, any designation of a “first 3D propagation” and “second 3D propagation” of the eye tracking system within any specific paragraph of this the Summary and/or Detailed Description is used solely to distinguish two different 3D propagations of the eye tracking system within that specific paragraph—not any other paragraph and particularly not the claims.

These and various other features will be apparent from a reading of the following Detailed Description and a review of the associated drawings. This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended that this Summary be used to limit the scope of the claimed subject matter. Furthermore, the claimed subject matter is not limited to implementations that solve any or all disadvantages noted in any part of this disclosure.

DRAWINGS

The Detailed Description is described with reference to the accompanying figures. In the figures, the left-most digit(s) of a reference number identifies the figure in which the reference number first appears. The same reference numbers in different figures indicate similar or identical items. References made to individual items of a plurality of items can use a reference number with another number included within a parenthetical (and/or a letter without a parenthetical) to refer to each individual item. Generic references to the items may use the specific reference number without the sequence of letters.

FIG. 1 illustrates an exemplary hardware layout for a Near-Eye-Display (NED) device that is configured to implement the methods described herein.

FIG. 2 illustrates a pair of three-dimensional (3D) propagations that extend from ellipses that result from circular features of user's eyes being projected into the sensors.

FIG. 3 illustrates in an exemplary ellipse that is being projected onto a sensor plane within a sensor that is angularly skewed with respect to the Iris-Pupil plane (not shown in FIG. 3) so that circular features on the Iris-Pupil plane appear elliptical on the sensor plane.

FIG. 4 illustrates a side view of a 3D propagation of the ellipse of FIG. 3 from the sensor plane through a predetermined point and toward the Iris-Pupil plane.

FIG. 5A illustrates exemplary eye tracking data in the form of pixel data that is generated by the sensors and that is usable to implement the techniques described herein.

FIG. 5B illustrates exemplary eye tracking data in the form of pixel data that has changed in relation to FIG. 5A due to the user's focus shifting to the left.

FIG. 6 illustrates exemplary positions of a user's fovea in relation to the optical axes of the user's left and right eyes.

FIG. 7 illustrates exemplary positions of a user's right fovea and left fovea in relation to the optical axes of the user's right eye and left eye, respectively.

FIG. 8 illustrates a side view of a user's eye showing how the offset position of the user's fovea in relation to the optical axis results in the visual axis diverging from the optical axis.

FIG. 9 illustrates an exemplary environment in which a user may perform vergence movements of the eyes to shift a vergence of the two visual axes (e.g., a focal point) from a first accommodation plane to a second accommodation plane.

FIG. 10 illustrates an exemplary anatomical eye model that defines geometrical relationships between various portions of an eye.

FIG. 11 illustrates a pair of visual axes that are determinable based on visual axis offset data defining a spatial relationship between the individual visual axes and corresponding optical axes.

FIG. 12 illustrates an exemplary environment in which a plurality of virtual stimuli can be sequentially generated at a predetermined accommodation plane for performance of a user-specific calibration process.

FIG. 13 is a flow diagram of a process 1300 to generate propagation data that defines three-dimensional (3D) propagations from ellipses detected at a sensor plane to determine pupil orientation parameters.

DETAILED DESCRIPTION

The following Detailed Description describes technologies for implementing eye tracking systems and methods for Near-Eye-Display (NED) devices. Generally described, an exemplary eye tracking system for a NED device includes sensors that are directed toward and angularly offset from a user's eyes in a manner that causes circular features (e.g., irises and/or pupils) of the user's eyes to appear elliptical within sensor planes of the individual sensors. For example, it can be appreciated that an iris and/or pupil of an eye will appear circular when the eye is looked at straight on (i.e., perpendicular to an optical axis of the eye's lens) but elliptical when observed from an angular offset. The eye tracking systems and methods disclosed herein exploit these principles to track movements of the user's eyes with a higher degree of accuracy than conventional eye tracking systems.

As described in more detail below, various embodiments track the user's visual axes—rather than merely tracking the user's optical axis and/or line of sight as conventional eye tracking systems do. It will be appreciated from the following discussion that determining a vergence in space between the visual axes for each of the user's two eyes provides substantially more actual calculations of the depth in space at which the user is focused than is currently achievable by conventional eye tracking systems. The disclosed eye tracking systems and methods therefore represent a substantial advance toward preventing a user of a NED device from experiencing motion sickness or vertigo due to CG images being generated in front of or behind the user's current (e.g., real time) accommodation plane (e.g., focal plane).

Aspects of the techniques described herein are primarily described in the context of the sensors being cameras that contain one or more lenses that define an entrance pupil that is disposed in front of an image-sensor (e.g., a CMOS sensor). In such embodiments, the image sensor may generate eye tracking data in the form of pixel data that defines images of the user's eyes. While the disclosed techniques are not necessarily limited to using cameras, an appreciation of various aspects of the invention is best gained through a discussion of example in such a context. However, any type of sensor that is suitable for observing a shape and/or orientation of the iris and/or pupil of the user's eye shall be considered variations of the techniques described herein. For example, it will be appreciated that various forms of lenses sensors may also be suitable for implementing the techniques described herein.

Turning now to FIG. 1, illustrated is an exemplary hardware layout for a Near-Eye-Display (NED) device 100 that is configured to implement the methods described herein. In the exemplary hardware layout the NED device 100 includes a pair of sensors 102 that are each directed toward a corresponding eye 104 of a user. More specifically, the illustrated NED device 100 includes a first sensor 102(1) that is angularly offset from and directed toward a right eye 104(R) and also a second sensor 102(1) that is angularly offset from and directed toward a left eye 104(L). The right eye 104(R) includes a corresponding pupil 106(R) and a corresponding iris 108(R). The left eye 104(L) includes a corresponding pupil 106(L) and a corresponding iris 108(L). The sensors 102 can be in any suitable form such as, for example, a non-contact sensor configured to use optical-based tracking (e.g. video camera based and/or some other specially designed optical-sensor-based eye tracking technique) to monitor the one or more physical characteristics of the user's eyes. Exemplary physical characteristics include, but are not limited to, pupil size, a rate of change of pupil size, gaze direction, and/or a rate of change to a gaze direction.

FIG. 1 is illustrated from a perspective that is directly in front of the optical axes of the eyes 104 so that the pupils 106 and irises 108 appear perfectly circular. It will be appreciated by one skilled in the art that in humans (and many other vertebrates for that matter) the pupils 106 and irises 108 of the eyes 104 are almost perfect circles. Therefore, in various calculations described below, the pupils 106 and/or irises 108 are mathematically modeled as and/or presumed to be perfectly circular in shape. From the perspective of the individual sensors 102, however, the pupils 106 and irises 108 of the eyes 104 appear to be elliptical as described herein. This is because the sensors 102 are angularly offset from the eyes 104 in the sense that the optical axis of each individual sensor 102 is not parallel to the optical axis of the eye 104 it is tracking. The position of the sensors 102 shown in FIG. 1 is for illustrative purposes only. It will be appreciated that the techniques described herein can be performed with the sensors 102 being located in a variety of positions with respect to the eyes. As a specific but nonlimiting example, the sensors could be embedded within a lens or other substrate directly in front of the eyes.

In the illustrated embodiment, the NED device 100 further includes a controller 110 that is configured to implement the various operations of the methods described herein. The controller 110 may be communicatively coupled to the sensors 102 to receive eye tracking data that is generated by the sensors 102 in association with the circular features of the eyes. The controller 110 may further be communicatively coupled to other componentry of the NED display device 100. The controller 110 includes one or more logic devices and one or more computer memory devices storing instructions executable by the logic device(s) to deploy functionalities described herein with relation to the NED device 100. The controller 116 can comprise one or more processing units 112, one or more computer-readable media 114 for storing an operating system 116 and data such as, for example, eye tracking data, visual axis offset data, application data, etc. The computer-readable media 114 may further include an eye tracking engine 116 configured to receive the eye tracking data from the sensor 102 and, based thereon, determine one or more physical characteristics of the user's eyes using the methods and techniques described herein. The components of the NED device 100 are operatively connected, for example, via a bus 120, which can include one or more of a system bus, a data bus, an address bus, a PCI bus, a Mini-PCI bus, and any variety of local, peripheral, and/or independent buses.

The processing unit(s) 112, can represent, for example, a CPU-type processing unit, a GPU-type processing unit, a field-programmable gate array (FPGA), another class of digital signal processor (DSP), or other hardware logic components that may, in some instances, be driven by a CPU. For example, and without limitation, illustrative types of hardware logic components that can be used include Application-Specific Integrated Circuits (ASICs), Application-Specific Standard Products (ASSPs), System-on-a-Chip Systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

As used herein, computer-readable media, such as computer-readable media 114, can store instructions executable by the processing unit(s). Computer-readable media can also store instructions executable by external processing units such as by an external CPU, an external GPU, and/or executable by an external accelerator, such as an FPGA type accelerator, a DSP type accelerator, or any other internal or external accelerator. In various examples, at least one CPU, GPU, and/or accelerator is incorporated in a computing device, while in some examples one or more of a CPU, GPU, and/or accelerator is external to a computing device.

Computer-readable media can include computer storage media and/or communication media. Computer storage media can include one or more of volatile memory, nonvolatile memory, and/or other persistent and/or auxiliary computer storage media, removable and non-removable computer storage media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules, or other data. Thus, computer storage media includes tangible and/or physical forms of media included in a device and/or hardware component that is part of a device or external to a device, including but not limited to random access memory (RAM), static random-access memory (SRAM), dynamic random-access memory (DRAM), phase change memory (PCM), read-only memory (ROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, rotating media, optical cards or other optical storage media, magnetic storage, magnetic cards or other magnetic storage devices or media, solid-state memory devices, storage arrays, network attached storage, storage area networks, hosted computer storage or any other storage memory, storage device, and/or storage medium that can be used to store and maintain information for access by a computing device.

In contrast to computer storage media, communication media can embody computer-readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave, or other transmission mechanism. As defined herein, computer storage media does not include communication media. That is, computer storage media does not include communications media consisting solely of a modulated data signal, a carrier wave, or a propagated signal, per se.

The NED device 100 may further include various other components, for example speakers, microphones, accelerometers, gyroscopes, magnetometers, temperature sensors, touch sensors, biometric sensors, other image sensors, energy-storage components (e.g. battery), a communication facility, a GPS receiver, etc.

Turning now to FIG. 2, illustrated is a pair of three-dimensional (3D) propagations 202 that extend from ellipses 204 that result from circular features (e.g., pupils 106 and/or irises 108) of user's eyes 104 being projected into the sensors 102. As illustrated, a first 3D propagation 202(1) extends from a first ellipse 204(1), which is detected at the first sensor 102(1), through a first point P1. As further illustrated, a second 3D propagation 202(2) extends from a second ellipse 204(2), which is detected at the second sensor 102(2), through a second point P2. Each of the 3D propagations 202 extend toward a corresponding Iris-Pupil plane 206 that is angularly offset with respect to the sensors 102. The angularly offset nature of the Iris-Pupil planes 206 results in the pupils 106 and irises 108 appearing elliptical from the perspectives of the sensors 102.

As illustrated, each of the individual 3D propagations 202 may include a series of lines that extend from a perimeter of a corresponding individual ellipse 204 through a corresponding predetermined point and, ultimately, to the perimeter of a circular feature (e.g., pupil 106 or iris 108) that resides within a corresponding Iris-Pupil plane 206. The predetermined points (e.g., P1 and P2) may correspond to specific points in space that are measurable in relation to corresponding sensors 102. For example, the first predetermined point P1 may correspond to a center of an entrance pupil of the first sensor 102(1) whereas the second predetermined point P2 may correspond to a center of an entrance pupil of the second sensor 102(2). Thus, it can be appreciated that P1 may correspond to a point in space at which light rays cross prior to forming an image within the first sensor 102(1) and that P2 may correspond to a point in space at which light rays cross prior to forming an image within the second sensor 102(2).

As described in more detail below, these 3D propagations 202 may be used to determine pupil orientation parameters that define various characteristics of the user's pupil(s) 106. For example, it can be appreciated that the 3D propagations 202 can be mathematically modeled as elliptical cones. This is because individual ones of the 3D propagations 202 originate at a corresponding ellipse 204 and pass through a singular point. It can further be appreciated that a cross-section of an elliptical cone will be circular in shape if that cross-section is taken at a specific orientation. Thus, by using the mathematical assumption that the pupils 106 and irises 108 are circular in shape, the 3D propagations 202 may enable a determination of the specific orientation of the Iris-Pupil planes 206. Additionally, as described in more detail below, performing various error minimization techniques of the 3D propagations with respect to an ocular rotation model may further enable a determination of the center points of the pupils 106. It can be appreciated that once the location in space of the center point of a pupil 106 and an orientation of an Iris-Pupil plane 206 is known for a particular eye, the optical axis (illustrated as dashed lines for each eye) for that particular eye is also known.

Turning now to FIG. 3, illustrated in an exemplary ellipse 204 that is projected from a circular feature of an eye 104 (e.g., an Iris 108) onto a sensor plane 302 of a sensor 102. The sensor plane 302 may correspond to a substantially planar surface within the sensor 102 that is angularly skewed with respect to a corresponding Iris-Pupil plane 206 (not shown in FIG. 3) so that circular features on the Iris-Pupil plane appear elliptical on the sensor plane 302. In some embodiments, the sensors 102 may be image sensors such as, for example, complementary metal oxide semiconductor (CMOS) sensors and/or charge-coupled device (CCD) sensors. In such embodiments, the sensors 102 may generate eye tracking data in the form of pixel data that defines images of the eyes. These images may be formed based on ambient light surrounding the user. Thus, in contrast to conventional eye tracking systems that rely on illuminating the eye(s) with near infrared light to cause first Purkinje reflections (e.g., “glints”) that are distributed around the iris, the techniques disclosed herein do not require active emission of near infrared light toward the user's eyes. The numerous benefits of the techniques disclosed herein include providing a system that can track the user's eyes using ambient light rather than having to expend battery resources to generate near infrared light. Moreover, the disclosed techniques provide a system that is highly sensitive and accurate in the detection of eye movements (e.g., the systems are sensitive enough to even accurately track saccadic eye movements).

Semi-axes for the “elliptically shaped” iris 108 and/or pupil 106 are uniquely oriented within the sensor plane 302 for any particular subtended angle of the sensor 102 and rotation of the eye being tracked. The size of the semi axes of the elliptically shaped iris 108 and pupil 106 depend on the original size of each and any magnification caused by optical components (e.g., lenses, etc.) of the sensor 102. In FIG. 3, the semi-major axis of the elliptically shaped iris 108 is labelled p_ip^Mand the semi-minor axis of the elliptically shaped iris 108 is labelled p_ip^m. The sensor plane 302 is illustrated with a sensor coordinate system centered thereon. The sensor coordinate system includes a vertical y-Axis and a horizontal x-Axis. Additionally, as illustrated, the elliptically shaped iris 108 is rotated an angle a with respect to the horizontal x-Axis. Therefore, within the sensor plane 302, an ellipse 204 that is centered at (x_ip^d, y_ip^d) with semi-major axis p_ip^Mand semi-minor axis p_ip^mand that is also rotated an angle α with respect to the horizontal x-Axis is given by Equation 1 shown below:

E
_ip(i, j)≡{x_ip^d+p_im^Mcos[φ(i, j)]cos(α)−p_ip^msin[φ(i, j)]sin(α), y_ip^d+p_ip^Mcos[φ(i, j)]sin(α)−p_ip^msin[φ(i, j)]cos(α)} (1)

Turning now to FIG. 4, illustrated is a side view of a 3D propagation 202 of the ellipse 204 of FIG. 3 from the sensor plane 302 through a predetermined point. In the illustrated embodiment, the predetermined point is labeled {right arrow over (r)}_oand is defined as the center of the entrance pupil for the sensor 102. To improve the clarity of the illustration, only two individual 3D rays of the 3D propagation 202 are shown. Each individual ray extends from a point on the sensor plane 302 that falls along the perimeter of the ellipse 204 through the point {right arrow over (r)}_oand, ultimately, to a point on the Iris-Pupil plane 206 that falls along the perimeter of the pupil 106 or iris 108. In plain terms, the 3D propagation 202 represents the reverse of the projections of the pupil 106 or iris 108 through the point {right arrow over (r)}_oand to the sensor plane 302. Thus, in three dimensional terms the rays that start from the sensor plane 302 and pass through point {right arrow over (r)}^o(e.g., the center of the entrance pupil of the sensor 102) and then travel some additional distance to reach the circular perimeter of the pupil 106 or iris 108 at the Iris-Pupil plane 206 is given by Equation 2 shown below:

{right arrow over (r)}
_ip
^d(i, j)={right arrow over (r)}_o+[√{square root over (p_ip²+d_ipo)}+√{square root over (|D_cip(i, j)|²+f²)}]{circumflex over (T)}_oip(j, j) (2)

where, {right arrow over (r)}_ois a point at which all of the rays of a particular image cross prior to forming an image on the sensor plane 302, d_ipois the distance from the point {right arrow over (r)}^oto the center of the iris/pupil {right arrow over (r)}_ip⁰(as labeled in FIG. 4), D_cipis the radial distance between the center of the sensor 102 and the ellipse points E_ip, f is the focal length of the sensor 102, and {circumflex over (T)}^oip(i, j) is the vector going from the points in the ellipse 204 to the point {right arrow over (r)}^o.

In some embodiments, the systems described herein may determine one or more of an orientation Rot(ϕ, Θ) of the Iris-Pupil plane 206, a radius p_ipof the pupil 106 or iris 108 (e.g., whichever circular feature is being observed to perform eye tracking), and the distance d_ipofrom the point {right arrow over (r)}^oto the center {right arrow over (r)}_ip⁰of the iris/pupil by analyzing the 3D propagations 202 with respect to an ocular rotation model. The ocular rotation model may be usable to model rotation of a circular feature of an eye around that eye's center of rotation {right arrow over (r)}_c. For example, an ocular rotation model may define coordinates of a circle with a center {right arrow over (r)}_ip⁰(i, j) and a radius p_ipand that is rotated around the eye's center of rotation {right arrow over (r)}^can elevation angle Θ and azimuth angle as given by Equation 3 shown below:

{right arrow over (r)}
_ip
^r
=Rot(ϕ, Θ)·({right arrow over (r)}_ip⁰+{right arrow over (r)}_ip^c(i, j)−{right arrow over (r)}_c) (3)

where the position of the center of the circle is given by {right arrow over (r)}_ip⁰={{right arrow over (x)}_ip⁰, {right arrow over (y)}_ip⁰, {right arrow over (z)}_ip⁰}, and the oarametrized coordinates of the circle are defined as {right arrow over (r)}_ip^c(i, j)={p_ipcos φ, p_ipsin φ, 0}. In various embodiments, the center of the iris/pupil circle and the center of rotation of the eye {right arrow over (r)}_care defined from one or more anatomical eye models such as, for example, the Gullstrand model, the Arizona model, the Liou-Brennan model, and/or the Navarro model. Moreover, as described in more detail below, a user-specific calibration may be performed to complete global minimization of the various parameters used in Equation 3 to customize the ocular rotation model to a specific user.

As a specific but non-limiting example, the orientation Rot(ϕ, Θ) of the Iris-Pupil plane 206, the radius p_ipof the pupil 106 or iris 108, and the distance d_ipofrom the point {right arrow over (r)}_oto the center {right arrow over (r)}_ip⁰of the iris/pupil are determined by minimizing the error between the 3D propagations 202 of the points detected (e.g in the sensor plane 302) {right arrow over (r)}_ip^dthrough the vector {circumflex over (T)}_cip(i, j), and a circle of radius p_iprotated around the eye center {right arrow over (r)}^c. An exemplary such error minimization technique is given by Equation 4 shown below:

$\begin{matrix} Err (p_{ip}, d_{ipo}, Rot (φ, Θ)) = argmin \sum_{i, j} { {\vec{r}}_{ip}^{d} (i, j) - {\vec{r}}_{ip} (i, j) }^{2} & (4) \end{matrix}$

It will be appreciated that upon determining the orientation Rot(ϕ, Θ) of the Iris-Pupil plane 206 and the distance d_ipofrom the point {right arrow over (r)}_oto the center {right arrow over (r)}_ip⁰of the iris/pupil, the systems disclosed herein can then determine where an optical axis for a tracked eye begins and in which direction it propagates with respect to the sensor 102. Additionally, in embodiments that include two sensors 102 which are separated by a known distance, upon determining the location of the center {right arrow over (r)}_ip⁰of the pupil for both eyes in relation to the sensors 102, the systems disclosed herein can dynamically determine an interpupillary distance (IPD) for the user (as shown in FIG. 2).

Turning now to FIG. 5A, exemplary eye tracking data is shown in the form of pixel data 502 that is generated by the sensors 102 and that is usable to implement the techniques described herein. As illustrated in FIG. 5A, a NED device 100 includes a first sensor 102(1) that is angularly offset from and directed toward a user's right eye 104(R) and a second sensor 102(2) that is angularly offset from and directed toward a user's left eye 104(L). As the user's eyes move around to look at and/or track various objects within the user's field-of-view (FOV), the sensors 102 continually capture images of the pupils 106 and/or irises 108 of the user's eyes.

Similar to FIG. 1, FIG. 5A is illustrated from a particular perspective that is directly in front of the user's while the user's is looking straight forward. Thus, the optical axis of each of the eyes 104 is normal to the page and the pupils 106 and irises 108 are illustrated to be perfect circles. Since each of the sensors 102 is angularly offset from the optical axis of the particular eye that it is imaging, the pixel data 502 corresponding to each eye defines the pupils 106 and irises 108 as ellipses. As described above, these ellipses correspond to projections of the pupils 106 and irises 108 onto the corresponding sensor planes 302. Moreover, depending on the optical characteristics of the sensors 102 and/or lenses thereof, these projections may be defined by a series of rays that all pass through a common point such as the center of the entrance pupil of the sensor 102.

As described above, the ellipses that are formed by the projections of the pupils 106 and/or irises 108 onto the corresponding sensor plane 302 have unique orientations and semi-axes for any particular subtended angle of the sensor 102 and rotation of the eye being tracked. As illustrated in FIG. 5A, each of the right eye pixel data 502(1) and the left eye pixel data 502(2) define an image of a corresponding elliptically shaped iris 108. Each elliptically shaped iris 108 has a semi-major axis that is labelled p_ip^Mand a semi-minor axis that is labelled p_ip^m. The sensor planes 302 are each illustrated with a corresponding sensor coordinate system centered thereon. Each sensor coordinate system includes a vertical y-Axis and a horizontal x-Axis. Additionally, as illustrated, each elliptically shaped iris 108 is aligned with (e.g., centered on and not rotated with respect to) a corresponding sensor coordinate system. Thus, within each of the sensor planes 302(1) and 302(2), the perimeters of the right elliptically shaped iris 108(R) and the left elliptically shaped iris 108(L) define a first ellipse 204(1) and a second ellipse 204(2), respectively. Each of the ellipses 204 are centered at ({right arrow over (x)}_ip^d, {right arrow over (y)}_ip^d) with semi-major axis p_ip^Mand semi-minor axis p_ip^mand is not rotated respect to the horizontal x-Axis of their corresponding sensor plane 302.

Turning now to FIG. 5B, exemplary eye tracking data is shown in the form of pixel data 502 that has changed in relation to FIG. 5A due to the user's focus shifting to the left. As illustrated, the first ellipse 204(1) that corresponds to the projection of the user's right eye 104(R) has shifted and rotated in relation to the first sensor plane 302(1). Additionally, the semi-minor axis p_ip^mof the first ellipse 204(1) has lengthened since the right eye's optical axis is directed more towards the sensor 102(1) in FIG. 5B (e.g., after the user looks left) that it was in FIG. 5A. As further illustrated, the second ellipse 204(2) that corresponds to the projection of the user's left eye 104(L) has shifted and rotated in relation to the second sensor plane 302(2). Additionally, the semi-minor axis p_ip^mof the second ellipse 204(2) has shortened since the lefteye's optical axis is directed more away from the second sensor 102(2) in FIG. 5B (e.g., after the user looks left) that it was in FIG. 5A.

In various embodiments, the eye tracking data for the user's two eyes may be used to continually and dynamically determine the current (e.g., real time) interpupillary distance (IPD) of the user. In particular, the eye tracking data may be analyzed to determine ellipse parameters that define the ellipses 204 for each eye within the corresponding sensor plane 302. Then, using the techniques described above with respect to equations 1 through 4, the center points {right arrow over (r)}_ip⁰for each eye may be determined with respect to the corresponding sensor 102. Since the sensors 102 are mechanically fixed at known locations and angles with respect to each other, the determined center points {right arrow over (r)}_ip⁰for the right eye 104(R) with respect to the first sensor 102(1) and the left eye 104(L) with respect to the second sensor 102(2) together yield the IPD at particular time at which the pixel data was captured. Thus, as shown in FIG. 5A, an IPD can be initially determined in association with pixel data that is captured at a first time T₁. Then, as shown in FIG. 5B after the user has looked to the left, an updated IPD can be determined can be determined in association with other pixel data that is captured at a second time T₂.

Turning now to FIG. 6, illustrated is the exemplary NED device 100 with various geometrical features labeled thereon that are relevant to a specific technique for calculating the interpupillary distance (IPD). It can be appreciated that Equation 2 as described above can be modified to specifically place the center of the pupil {right arrow over (r)}_ip^d(center) in space for both the left and right eyes. Specifically, Equation 2 can be modified into Equation 2.1 as shown below:

{right arrow over (r)}
_ip
^d(center)={right arrow over (r)}_o+[d_ipo+√{square root over (D_cip(center)²+f²)}]{circumflex over (T)}_oip(center) (2.1)

Then, once the center of the pupil for each of the right eye 104(R) and the left eye 104(L) have been placed in space, the IPD can be obtained as the norm of the subtraction of the projected pupillary axis for the left eye and the right eye—as given by Equation 5 below:

Interpupilary Distance (IPD)=∥{right arrow over (r)}_ip^d(left, center)−{right arrow over (r)}_ip^d(right, center)∥ (5)

Turning now to FIG. 7, illustrated are exemplary positions of a user's right fovea 702(R) and left fovea 702(L) in relation to the optical axes of the user's right eye 104(R) and left eye 104(L), respectively. As can be seen from FIG. 7, the position of the fovea for each eye is eccentric (e.g., not centrally placed) regarding the optical axis of the corresponding eye. Generally speaking, the right fovea 702(R) tends to be positioned in the second quadrant for the right eye 104(R) whereas the left fovea 702(L) tends to be positioned in the first quadrant for the left eye 104(L). This is consistent with the illustrated positions of the fovea in FIG. 7. The fovea 702 is the specific region of the retina at which visual acuity is highest due to the user's retinal cones being particularly concentrated in this area. For this reason, the center of the user's field of vision for each eye is focused at the fovea for that eye. The result is that the user's visual axis passes through the center of the fovea 702 so that light from whatever object the user is currently focused on passes through the pupil and lens of the eye before ultimately striking the fovea 702.

Turning now to FIG. 8, illustrated is a side view of a user's eye 104 showing how the offset position of the user's fovea in relation to the optical axis results in the visual axis diverging from the optical axis. As illustrated, the fovea position being above the optical axis at the back of the user's eye results in the visual axis pointing down slightly. It should also be appreciated from the combination of FIGS. 7 and 8 that the visual axes of the user's eyes will also tent to be pointed inward slightly.

As shown in FIG. 8, a line of sight of the user extends from the center of the entrance pupil {right arrow over (r)}_ip⁰and intersects the visual axis at a singular intersection point. Accordingly, when the user is focused on an object at a particular accommodation plane, determining the user's line of sight may be adequate to determine where the user is focused. However, since the visual axis will be most closely directed at whatever object the user is focused on regardless of the depth at which the user is focused, conventional eye tracking methods that merely track the user's line of sight are inadequate for determining where the user is focused for all accommodation planes. By dynamically tracking the user's visual axis, the eye tracking systems disclosed herein are able to determine a vergence in space at which the user is currently focused independent of what accommodation plane that vergence falls on.

In some instances, convention eye tracking systems estimate the user's line of sight by observing the Purkinje reflections with the addition of head tracking information. Unfortunately, even an accurate estimation of the user's line of sight may be insufficient to accurately determine the depth at which the user is focusing within the real-world environment. This is because the user's line of sight and the user's visual axis (which actually propagates to the user's fovea) only converge at a single depth plane. Although the visual axis is illustrated as a straight and continuous line in FIG. 8, it will be appreciated by one skilled in the art that the actual optical path of the visual axis is more aptly described as a line connecting the fixation point (at which the user is focused) to the first and second nodal points (not shown in FIG. 8) and the user's Fovea.

Turning now to FIG. 9 to demonstrate the foregoing point, illustrated is an exemplary environment 900 in which a user may perform vergence movements of the eyes to shift a vergence of the two visual axes (e.g., a focal point) from a first accommodation plane to a second accommodation plane. It will be appreciated that vergence movements are closely connected to accommodation of the eye. Under normal conditions, changing the focus of the eyes to look at objects at different distances will automatically cause vergence and accommodation. This is sometimes referred to as the accommodation-convergence reflex. Generally speaking, a vergence movement comprises the simultaneous movement of a binocular system (e.g., the user's two eyes) in opposite directions to perform a depth operation. When the user performs a vergence movement to change a focus from a distant object to a relatively closer object, the eyes rotate toward each other (i.e., the eyes perform a convergence movement). When the user performs a vergence movement to change a focus from a close object to a relatively more distant object, the eyes rotate toward away from each other (i.e., the eyes perform a divergence movement).

The left side of FIG. 9 shows the focus of the user on a house at “Accommodation Plane 1” that is relatively farther from the user than “Accommodation Plane 2.” Thus, on the right side of FIG. 9 the visual axes each reach a common vergence point that resides on the house whereas a vergence of the lines of sight (which conventional systems track) does not actually represent where the user is focused. The left side of FIG. 9 shows the focus of the user on a tree that is at an Accommodation Plane 2 that is relatively closer to the user. Thus, on the left side of FIG. 9 the visual axes each reach a common vergence point that resides on the tree whereas a vergence of the lines of sight again does not actually represent where the user is focused.

In some embodiments, visual axis offset data is used to continuously track the visual axis of the user's eyes 104. For example, it can be appreciated that by deploying various techniques as described above, the eye tracking systems described herein may continually determine the optical axis and the orientation Rot(ϕ, Θ) of the Iris-Pupil plane 206. Exemplary visual axis offset data defines a spatial relationship between the optical axis of the eye and/or the orientation Rot(ϕ, Θ) of the Iris-Pupil plane 206 of the eye 104. Thus, upon determining the optical axis and/or the orientation Rot(ϕ, Θ) for a particular eye, the eye tracking systems described herein may utilize the visual axis offset data to calculate the visual axis.

Turning now to FIG. 10 to demonstrate the foregoing point, illustrated is an exemplary anatomical eye model 1000 that defines geometrical relationships between various portions of an eye 104. As illustrated, the anatomical eye model 1000 defines: a horizontal dimension Di from the center of the eye 104 (i.e., the point labeled “C”) to the fovea (i.e., the point labeled “O”); a horizontal dimension D₂from the center of the eye 104 (i.e., the point labeled “C”) to the front surface of the cornea; a horizontal dimension D₃from the front surface of the cornea to a rear surface of the lens of the eye 104 (i.e., the point labeled “N”); a horizontal dimension D₄from the front surface of the cornea to a front surface of the lens of the eye 104 (i.e., the point labeled “P′”); and a vertical dimension D₅from the center of the eye 104 (i.e., the point labeled “C”) to the fovea (i.e., the point labeled “O”). In various implementations, these or other dimensions may be used to define the visual axis offset data. The values for the relevant dimensions may be taken from any variety of suitable models that include, but are not limited to, the Gullstrand model, the Arizona model, the Liou-Brennan model, and/or the Navarro model.

As illustrated in FIG. 10, the visual angle custom-character _N′ line may be represented as a vector that extends from the fovea at point “O” to the point labeled “N′” that represents the rear surface of the lens of the eye 104. The visual angle _n′ line subtends an angle k from the optical axis and can be defined based on Equation 6 below:

$\begin{matrix} N^{'} = \frac{{\vec{r}}_{N^{'}} - {\vec{r}}_{O}}{\langle {\vec{r}}_{N^{'}} - {\vec{r}}_{O} \rangle} = \frac{{\vec{R}}_{N^{'} O}}{\langle {\vec{R}}_{N^{'} O} \rangle} & (6) \end{matrix}$

where {right arrow over (r)}_N′ is the image nodal position and {right arrow over (r)}₀is the central position of the fovea 702. In general, literature has reported that the angle k ranges between 4 and 8 degrees.

It can be appreciated that by applying the definition of nodal points to the exemplary anatomical eye model 1000, there is a conservation of the angles regarding the optical axis. For this reason, the line that starts from the object nodal point “N” can be described by Equation 7 given below:

{right arrow over (VA)}
_N
={right arrow over (r)}
_N
D
_SN
custom-character
_N′ (7)

where {right arrow over (r)}_Nis the object nodal point and D_SNis the distance between object nodal point “N” and the stimulus (e.g., object) upon which the user is focused.

Based on the foregoing, it can be appreciated that the rotation calculated from the minimization technique described in relation to Equation 4 as applied over {right arrow over (VA)}_Nregarding to the center {right arrow over (r)}_Cof the eye 104 must be equal to the vector joining the stimulus and the target as given by Equation 8 below:

Rot(ϕ, Θ) ({right arrow over (R)}_SC+∥{right arrow over (R)}_SN∥ custom-character _N′)={right arrow over (R)}_SC (8)

It can be appreciated that the various nodal points that are illustrated in FIG. 10 and described throughout this document will change in relative position as the user focuses on object at different accommodation planes. For example, in focusing on objects at different depths, the lenses of the eyes are of course caused to change shape. As these shape changes occur the rear surface of the lens may shift between the nodal point labeled “N” and the nodal point labeled “N′” whereas the front surface of the lens may shift between the nodal point labeled “P” and the nodal point labeled “P′.” Notable, these changes in the shape of the lens and positions of the nodal points that are triggered by accommodation changes have an insignificant impact on the orientation and placement of the visual axis within the eye. For this reason, in various embodiments the visual axis offset data may define relationships between the optical axis of the eye in a manner that is independent of the current accommodation plane upon which the user is focused.

To illustrate the foregoing, FIG. 11 illustrates a pair of visual axes that are determinable based on visual axis offset data defining a spatial relationship between the individual visual axes and corresponding optical axes. As illustrated in FIG. 10, upon determining the optical axis and the orientation Rot(ϕ, Θ) of the Iris-Pupil plane 206 for each eye 104, the eye tracking systems described herein can then calculate the visual axes for each eye. These calculations may be done continuously based on visual axis offset data that defines a spatial relationship between the optical axis of the eye and/or the orientation Rot(ϕ, Θ) of the Iris-Pupil plane 206 of the eye 104.

In some embodiments, upon calculating the pair of visual axes for a particular moment in time, the eye tracking system may then determine the vergence of the visual axes in space. The two visual axes will rarely actually converge in space perfectly. This is because although generally modeled as such, the human body does not behave perfectly symmetrically. Rather, there are slight variations in where the two eyes will actually be pointed in a real-life scenario. As such, in various embodiments, the vergence is calculated by performing minimization techniques with respect to both of the two visual axes. Stated plainly, based on the assumption that the two visual axes will be closest to actually converging at or very near the point in space that the user is actually focusing, the techniques described herein may determine the vergence point to be the point in space at which the visual axes are closest together.

Turning now to FIG. 12, illustrated is an exemplary environment 1200 in which a plurality of virtual stimuli 1202 can be sequentially generated at a predetermined accommodation plane for performance of a user-specific calibration process. As illustrated, the plurality of virtual stimuli 1202 may be uniformly spaced in a predetermined grid shaped pattern at a predetermined accommodation plane. The predetermined accommodation plane may be spaced a predetermined distance in front of the NED device 100 (not shown in FIG. 12). As a specific but non-limiting example, the predetermined accommodation plane may be spaced a distance of two meters in front of the user. It should be appreciated that as the stimuli are virtual in nature, the virtual stimuli may be generated at the accommodation plane of two meters by a display element (e.g. a waveguide display) that is located at a much closer distance to the user's eyes than two meters. For example, modern NED devices are capable of rendering images at a plurality of accommodation depths all from a transparent display that is positioned between fifteen and thirty-five millimeters from the user's eyes.

To perform the user-specific calibration process, individual ones of the virtual stimuli 1202 are sequentially rendered (e.g., one at a time) to cause the eyes of the subject to rotate so that the visual axes converge at the currently rendered virtual stimuli. Then, the discrepancy between the orientations Rot(ϕ, Θ) of the Iris-Pupil plane 206 as the user's focus changes between the individual stimuli can be exploited to determine the optimum visual axis for that specific user. Stated plainly, the visual axis offset data can be customized for the specific user.

During performance of the user-specific calibration process, the orientation Rot(ϕ, Θ) of the Iris-Pupil plane 206 while the user is focused on each individual one of the virtual stimuli 1202. Then, various error minimization techniques can be deployed to determine what the optimum visual axis is for the user. As a specific example of such an error minimization technique is given by Equation 9 as shown below:

$\begin{matrix} Err (N^{'}) = \sum_{i = 1}^{m} \sum_{j = 1}^{n} { Rot (φ, Θ, i, j) ({\vec{R}}_{SC} (i, j) +  R_{SN}  N^{'}) - {\vec{R}}_{SC} (i, j) }^{2} & (9) \end{matrix}$

This type of minimization technique has the advantage that it is convex and that the visual axis can be calculated analytically. Furthermore, while the coordinates of the stimulus are known {right arrow over (r)}_S, the values of the center of rotation of the eye {right arrow over (r)}_Cand the object nodal point {right arrow over (r)}_Ncan be either introduced following anatomical models like Gullstrand, Arizona, Liou-Brennan or Navarro among others, or otherwise, a global minimization can be performed for custom values.

Turning now to FIG. 13, a flow diagram is illustrated of a process 1300 to generate propagation data that defines three-dimensional (3D) propagations from ellipses detected at a sensor plane to determine pupil orientation parameters. The process 1300 is illustrated as a collection of blocks in a logical flow graph, which represent a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the blocks represent computer-executable instructions that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform or implement particular functions. The order in which operations are described is not intended to be construed as a limitation, and any number of the described blocks can be combined in any order and/or in parallel to implement the process. Other processes described throughout this disclosure shall be interpreted accordingly.

At block 1301, an eye tracking system receives eye tracking data from at least one sensor that is directed toward at least one eye. As described herein, the at least one sensor can be a camera that includes at least one lens through which light passes prior to striking an image sensor (e.g., a CMOS sensor or any other suitable type of image sensor). The eye tracking data may be in the form of pixel data that defines an image of circular feature(s) of the at least one eye. In an exemplary embodiment, the eye tracking data includes images of both a right eye and a left eye of a user of a NED device. Moreover, as described above, the images may include elliptical representations of the circular features of the eyes due to a sensor plane in each of the sensors being angularly offset from an Iris-Pupil plane of the respective eye that each sensor is tracking. In various implementations, the eye tracking system may select between tracking the pupil vs the iris depending on physical characteristics of the user. For example, if the user has very dark irises, there may be very little contrast between the user's pupils and the user's irises. The result of this lack of contrast may be that tracking the user's pupil is impractical. In such a case, the eye tracking system may use the user's iris to perform the eye tracking since there will be greater contrast between the user's iris and the sclera (commonly referred to as the “white of the eye”) of the user's eyes than between the user's “dark” iris and the user's dark pupil.

At block 1303, the eye tracking system may determine ellipse parameters for first ellipses that correspond to projections of a circular feature of a first eye (e.g., a right eye) onto a first sensor plane and also for second ellipses that correspond to projections of a circular feature of a second eye (e.g., a left eye) onto a second sensor plane. For example, the system may determine, for each of the first ellipse and the second ellipse, a center-point for the ellipse, a semi-major axis of the ellipse, a semi-minor axis of the ellipse, and an angular rotation of the ellipse with respect to a sensor plane.

At block 1305, the eye tracking system may generate propagation data that defines first 3D propagations of the first ellipse back toward the first eye and second 3D propagations of the second ellipse back toward the second eye. In various embodiments, each of the 3D propagations may comprise a series of lines that all begin at a point along the perimeter of an ellipse that is detected on a sensor plane and then propagation through a predetermined point back toward the eye of a user. It should be appreciated that the 3D propagations described herein may be generally understood as mathematical representations of rays of light rather than actual projections of light that are emitted from the eye tracking system toward the user. Notable, a major benefit of the eye tracking systems and techniques disclosed herein is that light need not be emitted for implementations—rather the eye tracking data can be generated based exclusively on ambient light.

At block 1307, the eye tracking system may utilize the propagation data to determine pupil orientation parameters that define various characteristics of the user's eye(s). Exemplary pupil orientation parameters may define optical axes for one or both of the user's eyes (e.g., an axis of an eye lens), visual axes for one or both of the user's eyes (e.g. axes that extend from the fovea through the lens and into the real-world environment), rotational angles of the user's eyes (e.g. an angle of rotation between a semi-axis of an ellipse and a horizontal axes of the sensor), Iris-Pupil Planes of the user's eyes (e.g. a plane on which the pupil resides), center points for the user's eyes (e.g., a point at which the optical axis (or alternatively the visual axis) intersects the Iris-Pupil plane). Additionally, or alternatively, the pupil orientation parameters may define various other characteristics of the user's eyes.

As described above, in various embodiments the eye tracking system may utilize the pupil orientation parameters and visual axis offset data to determine visual axes that correspond to each of the eyes of the user. Then, the eye tracking system may perform various minimization techniques to determine a vergence between the two visual axes. The determined vergence then represents a focal point within the real-world environment at which the user is currently focused. The vergence may be determined by calculating the point in space at which the two visual axes come the closest to actually converging in pure mathematical terms since in a practical sense the calculated visual axes for a user will rarely (if ever) actually converge.

EXAMPLE CLAUSES

Example Clause A, an eye tracking system for a Near-Eye-Display (NED) device, comprising: at least one sensor configured to generate eye tracking data associated with a first circular feature of a first eye of a user and a second circular feature of a second eye of the user; one or more processors; and at least one computer storage medium having computer executable instructions stored thereon which are executable by the one or more processors to: receive the eye tracking data from the at least one sensor; determine, based at least on the eye tracking data, ellipse parameters that define: first ellipses that correspond to projections of the first circular feature of the first eye onto a first sensor plane, and second ellipses that correspond to projections of the second circular feature of the second eye onto a second sensor plane; generate, based at least on the ellipse parameters, propagation data that defines: first three-dimensional (3D) propagations of the first ellipses through a first predetermined point, and second 3D propagations of the second ellipses through a second predetermined point; and determine, based at least on the propagation data, pupil orientation parameters that define a first center point of the first circular feature and a second center point of the second circular feature.

Example Clause B, the eye tracking system of Example Clause A, wherein the computer executable instructions are further executable by the one or more processors to determine, based at least on the propagation data, a first axis of the first eye and a second axis of the second eye.

Example Clause C, the eye tracking system of any of Example Clauses A through B, wherein the first axis is a first visual axis of the first eye that is angularly offset from a first optical axis of the first eye, and wherein the second axis is a second visual axis of the second eye that is angularly offset from a second optical axis of the second eye.

Example Clause D, the eye tracking system of any of Example Clauses A through C, wherein the computer executable instructions are further executable by the one or more processors to determine a vergence by calculating a point along a first visual axis that corresponds to a minimum distance from a second visual axis.

Example Clause E, the eye tracking system of any of Example Clauses A through D, wherein the computer executable instructions are further executable by the one or more processors to: determine an interpupillary distance of the user based at least on the pupil orientation parameters that define the first center point of the first circular feature and the second center point of the second circular feature.

Example Clause F, the eye tracking system of any of Example Clauses A through E, wherein determining the pupil orientation parameters includes performing error minimization of the first 3D propagations and the second 3D propagations with respect to at least one ocular rotation model to determine orientations of a first iris-pupil plane of the first eye and a second iris-pupil plane of the second eye.

Example Clause G, the eye tracking system of any of Example Clauses A through F, wherein the first circular feature is at least one of a first pupil of the first eye or a first iris of the first eye, and wherein the second circular feature is at least one of a second pupil of the second eye or a second iris of the second eye.

Example Clause H, the eye tracking system of any of Example Clauses A through G, wherein the at least one sensor includes at least a first image sensor that is directed toward the first eye and a second image sensor that is directed toward the second eye.

Example Clause I, the eye tracking system of any of Example Clauses A through H, wherein the first predetermined point corresponds to a first entrance pupil of a first sensor, and wherein the second predetermined point corresponds to a second entrance pupil of a second sensor.

Example Clause J, a computer-implemented method, comprising: receiving, from at least one sensor, eye tracking data associated with a first circular feature of a first eye of a user and a second circular feature of a second eye of the user; determining, based at least on the eye tracking data, ellipse parameters that define first ellipses that correspond to projections of the first circular feature onto a first sensor plane and second ellipses that correspond to projections of the second circular feature onto a second sensor plane; generating, based at least on the ellipse parameters, propagation data that defines first three-dimensional (3D) propagations of the first ellipses through a first predetermined point and second 3D propagations of the second ellipses through a second predetermined point; and determining, based at least on the propagation data, pupil orientation parameters that define at least: a first center point of the first circular feature, and a second center point of the second circular feature.

Example Clause K, the computer-implemented method of Example Clause J, wherein the determining the pupil orientation parameters includes determine, based at least on the propagation data, a first axis of the first eye and a second axis of the second eye.

Example Clause L, the computer-implemented method of any one of Example Clauses J through K, further comprising: performing minimization of the propagation data with respect to an ocular rotation model to determine: a first orientation of a first Iris-Pupil plane of the first eye, and a second orientation of a second Iris-Pupil plane of the second eye.

Example Clause M, the computer-implemented method of any one of Example Clauses J through L, further comprising: determining, based at least on the propagation data, a first visual axis of the first eye and a second visual axis of the second eye; and determining a vergence of the first visual axis and the second visual axis, wherein the vergence corresponds to a minimum distance between the first visual axis and the second visual axis.

Example Clause N, the computer-implemented method of any one of Example Clauses J through M, further comprising: causing a display to sequentially render a plurality of virtual stimuli objects within a field of view of the user; determining, based at least on the eye tracking data, a plurality of sets of ellipse parameters that correspond to the plurality of virtual stimuli objects, wherein individual sets of ellipse parameters correspond to individual virtual stimuli objects; and determining visual axis offset data that indicates at least one of based at least on the plurality of sets of ellipse parameters.

Example Clause O, the computer-implemented method of any one of Example Clauses J through N, wherein the at least one sensor includes at least a first image sensor that is directed toward the first eye and a second image sensor that is directed toward the second eye.

Example Clause P, a Near-Eye-Display (NED) system, comprising: a sensor configured to generate eye tracking data associated with at least one substantially circular feature of an eye of a user, wherein the at least one substantially circular feature includes at least one of an iris or a pupil; a controller that is communicatively coupled to the sensor, wherein the controller is configured to perform operations that include: receiving the eye tracking data from the sensor; determining, based at least on the eye tracking data, ellipse parameters defining ellipses that correspond to projections of the at least one substantially circular feature of the eye onto a sensor plane that corresponds to the sensor; generating, based at least on the ellipse parameters, propagation data defining three-dimensional (3D) propagations of the ellipses from the sensor plane through a predetermined point; and determining an ocular rotation model to model rotation of the at least one substantially circular feature about a center of rotation of the eye of the user; and analyzing the propagation data with respect to the ocular rotation model to determine pupil orientation parameters that define characteristics of the eye.

Example Clause Q, the NED system of Example Clause P, wherein the analyzing the propagation data with respect to the ocular rotation model to determine the optical axis includes minimizing an error between the 3D propagations and the ocular rotation model to determine at least: an orientation of a pupil plane of the eye, and a distance to the pupil plane from at least one of the sensor plane or the predetermined point.

Example Clause R, the NED system of any one of Example Clauses P through Q, wherein the operations that the controller is configured to perform further include determining a visual axis of the eye based at least on visual axis offset data that indicates at least an angular relationship between the optical axis and the visual axis.

Example Clause S, the NED system of any one of Example Clauses P through R, wherein the pupil orientation parameters define at least one of an optical axis of the eye, or a visual axis of the eye.

Example Clause T, the NED system of any one of Example Clauses P through S, wherein the predetermined point is an entrance pupil that corresponds to the sensor.

CONCLUSION

In closing, although the various techniques have been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended representations is not necessarily limited to the specific features or acts described. Rather, the specific features and acts are disclosed as example forms of implementing the claimed subject matter.

EYE TRACKING SYSTEMS AND METHODS FOR NEAR-EYE-DISPLAY (NED) DEVICES

Information

Publication Number

Date Filed

Date Published

Inventors

Original Assignees

CPC

International Classifications

Abstract

Description

Claims