Note: Descriptions are shown in the official language in which they were submitted.
APPARATUS, SYSTEM AND METHOD OF DETERMINING A PUPILLARY
DISTANCE
CROSS REFERENCE
[001] This Application claims the benefit of and priority from US Provisional
Patent
Application No. 62/159,490 entitled "APPARATUS, SYSTEM AND METHOD OF
DETERMINING A PUPILLARY DISTANCE", filed May 11, 2015.
TECHNICAL FIELD
[002] Embodiments described herein generally relate to determining a pupillary
distance.
BACKGROUND
[003] A pupillary distance (PD) between pupils of a user may be measured,
e.g., in
addition to the refractive prescription for eyeglasses, e.g., mono-focal or
multi-focal
eyeglasses.
[004] Optical centers of eyeglasses may be configured to coincide with a line
of sight of
the user, for example, to provide clear and convenient vision.
[005] Multi-Focal (MF) spectacles, which may have a narrow distant vision
zone, may
require higher accuracy in the PD measurement than mono-focal spectacles.
[006] The PD may be stated as two unequal numbers of distances from a frame
center,
e.g., a center of a nose of the user, for example, if symmetry in the PD is
not always a
constitution, e.g., in strabismus cases.
[007] Discrepancy in the pupillary distance may lead, for example, to double
vision,
headaches, and/or other unwanted effects.
[008] A degree of a possible error in the pupillary distance may depend on
the power of
the lens, e.g., an Rx of spectacles. For example, for a low power of the lens,
larger errors in
the pupillary distance may not affect a vision of the user.
[009] An error tolerance of the pupillary distance may not be symmetric. In
one example,
1
Date Recue/Date Received 2022-09-20
CA 02985315 2017-11-07
WO 2016/181308
PCT/IB2016/052671
if a measured PD of a user is less than an actual PD of the user, e.g., a
negative error, the user
may be able to compensate for the negative error, for example, by a slight
accommodation of
the eyes, which may lead to eye convergence that may reduce the actual PD of
the user. In
another example, a measured PD of a user, which is larger than an actual PD of
the user, e.g.,
a positive error, may result in some degree of double vision and/or other
inconveniences.
2
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
BRIEF DESCRIPTION OF THE DRAWINGS
[0010] For simplicity and clarity of illustration, elements shown in the
figures have not
necessarily been drawn to scale. For example, the dimensions of some of the
elements may
be exaggerated relative to other elements for clarity of presentation.
Furthermore, reference
numerals may be repeated among the figures to indicate corresponding or
analogous
elements. The figures are listed below.
[0011] Fig. 1 is a schematic block diagram illustration of a system, in
accordance with some
demonstrative embodiments.
[0012] Fig. 2 is a schematic illustration of a lens and a sensor of a camera,
in accordance
with some demonstrative embodiments.
[0013] Fig. 3 is a schematic illustration of an imaging diagram for capturing
an image of an
object, in accordance with some demonstrative embodiments.
[0014] Fig. 4 is a schematic illustration of an imaging diagram for capturing
an image of a
tilted object, in accordance with some demonstrative embodiments.
[0015] Fig. 5 is a schematic illustration of an imaging diagram for capturing
an object by a
tilted camera, in accordance with some demonstrative embodiments.
[0016] Fig. 6 is a schematic illustration of a horizontal section of a right
eye of a user, in
accordance with some demonstrative embodiments.
[0017] Fig. 7 is a schematic illustration of a pupillary distance between two
eyes of a user
looking towards a camera, in accordance with some demonstrative embodiments.
[0018] Figs. 8A-8F are schematic illustrations of histograms corresponding to
a plurality of
Monte Carlo simulations, in accordance with some demonstrative embodiments.
[0019] Fig. 9 is a schematic flow-chart illustration of a method of
determining a pupillary
distance (PD) of a user, in accordance with some demonstrative embodiments.
[0020] Fig. 10 is a schematic flow-chart illustration of a method of
determining a PD of a
user, in accordance with some demonstrative embodiments.
[0021] Fig. 11 is a schematic illustration of a product, in accordance with
some
demonstrative embodiments.
DETAILED DESCRIPTION
3
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[0022] In the following detailed description, numerous specific details are
set forth in order
to provide a thorough understanding of some embodiments. However, it will be
understood
by persons of ordinary skill in the art that some embodiments may be practiced
without these
specific details. In other instances, well-known methods, procedures,
components, units
and/or circuits have not been described in detail so as not to obscure the
discussion.
[0023] Some portions of the following detailed description are presented in
terms of
algorithms and symbolic representations of operations on data bits or binary
digital signals
within a computer memory. These algorithmic descriptions and representations
may be the
techniques used by those skilled in the data processing arts to convey the
substance of their
work to others skilled in the art.
[0024] An algorithm is here, and generally, considered to be a self-consistent
sequence of
acts or operations leading to a desired result. These include physical
manipulations of
physical quantities. Usually, though not necessarily, these quantities take
the form of
electrical or magnetic signals capable of being stored, transferred, combined,
compared, and
otherwise manipulated. It has proven convenient at times, principally for
reasons of common
usage, to refer to these signals as bits, values, elements, symbols,
characters, terms, numbers
or the like. It should be understood, however, that all of these and similar
terms are to be
associated with the appropriate physical quantities and are merely convenient
labels applied
to these quantities.
[0025] Discussions herein utilizing terms such as, for example, "processing",
"computing",
"calculating", "determining", "establishing", "analyzing", "checking", or the
like, may refer
to operation(s) and/or process(es) of a computer, a computing platform, a
computing system,
or other electronic computing device, that manipulate and/or transform data
represented as
physical (e.g., electronic) quantities within the computer's registers and/or
memories into
other data similarly represented as physical quantities within the computer's
registers and/or
memories or other information storage medium that may store instructions to
perform
operations and/or processes.
[0026] The terms "plurality" and "a plurality", as used herein, include, for
example,
"multiple" or "two or more". For example, "a plurality of items" includes two
or more items.
[0027] References to "one embodiment", "an embodiment", "demonstrative
embodiment",
"various embodiments" etc., indicate that the embodiment(s) so described may
include a
particular feature, structure, or characteristic, but not every embodiment
necessarily includes
4
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
the particular feature, structure, or characteristic. Further, repeated use of
the phrase "in one
embodiment" does not necessarily refer to the same embodiment, although it
may.
[0028] As used herein, unless otherwise specified the use of the ordinal
adjectives "first",
"second", "third" etc., to describe a common object, merely indicate that
different instances
of like objects are being referred to, and are not intended to imply that the
objects so
described must be in a given sequence, either temporally, spatially, in
ranking, or in any other
manner.
[0029] Some embodiments, for example, may take the form of an entirely
hardware
embodiment, an entirely software embodiment, or an embodiment including both
hardware
and software elements. Some embodiments may be implemented in software, which
includes
but is not limited to firmware, resident software, microcode, or the like.
[0030] Furthermore, some embodiments may take the form of a computer program
product
accessible from a computer-usable or computer-readable medium providing
program code for
use by or in connection with a computer or any instruction execution system.
For example, a
computer-usable or computer-readable medium may be or may include any
apparatus that
can contain, store, communicate, propagate, or transport the program for use
by or in
connection with the instruction execution system, apparatus, or device.
[0031] In some demonstrative embodiments, the medium may be an electronic,
magnetic,
optical, electromagnetic, infrared, or semiconductor system (or apparatus or
device) or a
propagation medium. Some demonstrative examples of a computer-readable medium
may
include a semiconductor or solid state memory, magnetic tape, a removable
computer
diskette, a random access memory (RAM), a read-only memory (ROM), a FLASH
memory,
a rigid magnetic disk, and an optical disk. Some demonstrative examples of
optical disks
include compact disk ¨ read only memory (CD-ROM), compact disk ¨ read/write
(CD-R/W),
.. and DVD.
[0032] In some demonstrative embodiments, a data processing system suitable
for storing
and/or executing program code may include at least one processor coupled
directly or
indirectly to memory elements, for example, through a system bus. The memory
elements
may include, for example, local memory employed during actual execution of the
program
code, bulk storage, and cache memories which may provide temporary storage of
at least
some program code in order to reduce the number of times code must be
retrieved from bulk
storage during execution.
5
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[0033] In some demonstrative embodiments, input/output or I/O devices
(including but not
limited to keyboards, displays, pointing devices, etc.) may be coupled to the
system either
directly or through intervening I/0 controllers. In some demonstrative
embodiments, network
adapters may be coupled to the system to enable the data processing system to
become
coupled to other data processing systems or remote printers or storage
devices, for example,
through intervening private or public networks. In some demonstrative
embodiments,
modems, cable modems and Ethernet cards are demonstrative examples of types of
network
adapters. Other suitable components may be used.
[0034] Some embodiments may include one or more wired or wireless links, may
utilize
one or more components of wireless communication, may utilize one or more
methods or
protocols of wireless communication, or the like. Some embodiments may utilize
wired
communication and/or wireless communication.
[0035] Some embodiments may be used in conjunction with various devices and
systems,
for example, a mobile phone, a Smartphone, a mobile computer, a laptop
computer, a
notebook computer, a tablet computer, a handheld computer, a handheld device,
a Personal
Digital Assistant (PDA) device, a handheld PDA device, a mobile or portable
device, a non-
mobile or non-portable device, a cellular telephone, a wireless telephone, a
device having one
or more internal antennas and/or external antennas, a wireless handheld
device, or the like.
[0036] Reference is now made to Fig. 1, which schematically illustrates a
block diagram of a
system 100, in accordance with some demonstrative embodiments.
[0037] As shown in Fig. 1, in some demonstrative embodiments system 100 may
include a
device 102.
[0038] In some demonstrative embodiments, device 102 may be implemented using
suitable
hardware components and/or software components, for example, processors,
controllers,
memory units, storage units, input units, output units, communication units,
operating
systems, applications, or the like.
[0039] In some demonstrative embodiments, device 102 may include, for example,
a
computing device, a mobile phone, a Smartphone, a Cellular phone, a notebook,
a mobile
computer, a laptop computer, a notebook computer, a tablet computer, a
handheld computer,
a handheld device, a PDA device, a handheld PDA device, a wireless
communication device,
a PDA device which incorporates a wireless communication device, or the like.
[0040] In some demonstrative embodiments, device 102 may include, for example,
one or
6
CA 02985315 2017-11-07
WO 2016/181308
PCT/IB2016/052671
more of a processor 191, an input unit 192, an output unit 193, a memory unit
194, and/or a
storage unit 195. Device 102 may optionally include other suitable hardware
components
and/or software components. In some demonstrative embodiments, some or all of
the
components of one or more of device 102 may be enclosed in a common housing or
packaging, and may be interconnected or operably associated using one or more
wired or
wireless links. In other embodiments, components of one or more of device 102
may be
distributed among multiple or separate devices.
[0041] In some demonstrative embodiments, processor 191 may include, for
example, a
Central Processing Unit (CPU), a Digital Signal Processor (DSP), one or more
processor
cores, a single-core processor, a dual-core processor, a multiple-core
processor, a
microprocessor, a host processor, a controller, a plurality of processors or
controllers, a chip,
a microchip, one or more circuits, circuitry, a logic unit, an Integrated
Circuit (IC), an
Application-Specific IC (ASIC), or any other suitable multi-purpose or
specific processor or
controller. Processor 191 may execute instructions, for example, of an
Operating System
(OS) of device 102 and/or of one or more suitable applications.
[0042] In some demonstrative embodiments, input unit 192 may include, for
example, a
keyboard, a keypad, a mouse, a touch-screen, a touch-pad, a track-ball, a
stylus, a
microphone, or other suitable pointing device or input device. Output unit 193
may include,
for example, a monitor, a screen, a touch-screen, a flat panel display, a
Light Emitting Diode
(LED) display unit, a Liquid Crystal Display (LCD) display unit, a plasma
display unit, one
or more audio speakers or earphones, or other suitable output devices.
[0043] In some demonstrative embodiments, memory unit 194 includes, for
example, a
Random Access Memory (RAM), a Read Only Memory (ROM), a Dynamic RAM (DRAM),
a Synchronous DRAM (SD-RAM), a flash memory, a volatile memory, a non-volatile
memory, a cache memory, a buffer, a short term memory unit, a long term memory
unit, or
other suitable memory units. Storage unit 195 may include, for example, a hard
disk drive, a
floppy disk drive, a Compact Disk (CD) drive, a CD-ROM drive, a DVD drive, or
other
suitable removable or non-removable storage units. Memory unit 194 and/or
storage unit 195,
for example, may store data processed by device 102.
[0044] In some demonstrative embodiments, device 102 may be configured to
communicate
with one or more other devices via a wireless and/or wired network 103.
[0045] In some demonstrative embodiments, network 103 may include a wired
network, a
7
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
local area network (LAN), a wireless LAN (WLAN) network, a radio network, a
cellular
network, a Wireless Fidelity (WiFi) network, an IR network, a Bluetooth (BT)
network, and
the like.
[0046] In some demonstrative embodiments, device 102 may allow one or more
users to
interact with one or more processes, applications and/or modules of device
102, e.g., as
described herein.
[0047] In some demonstrative embodiments, device 102 may be configured to
perform
and/or to execute one or more operations, modules, processes, procedures and
/or the like.
[0048] In some demonstrative embodiments, device 102 may be configured to
determine a
pupillary distance (PD) of a user of device 102, e.g., as described below.
[0049] In some demonstrative embodiments, the pupillary distance may include a
near
pupillary distance or a far pupillary distance.
[0050] In some demonstrative embodiments, system 100 may include at least one
service,
module, controller, and/or application 160 configured to determine the
pupillary distance
(PD) of the user of device 102, e.g., as described below.
[0051] In some demonstrative embodiments, application 160 may include, or may
be
implemented as, software, a software module, an application, a program, a
subroutine,
instructions, an instruction set, computing code, words, values, symbols, and
the like.
[0052] In some demonstrative embodiments, application 160 may include a local
application
to be executed by device 102. For example, memory unit 194 and/or storage unit
195 may
store instructions resulting in application 160, and/or processor 191 may be
configured to
execute the instructions resulting in application 160, e.g., as described
below.
[0053] In other embodiments, application 160 may include a remote application
to be
executed by any suitable computing system, e.g., a server 170.
[0054] In some demonstrative embodiments, server 170 may include at least a
remote server,
a web-based server, a cloud server, and/or any other server.
[0055] In some demonstrative embodiments, the server 170 may include a
suitable memory
and/or storage unit 174 having stored thereon instructions resulting in
application 160, and a
suitable processor 171 to execute the instructions, e.g., as descried below.
[0056] In some demonstrative embodiments, application 160 may include a
combination of a
remote application and a local application.
8
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[0057] In one example, application 160 may be downloaded and/or received by
the user of
device 102 from another computing system, e.g., server 170, such that
application 160 may
be executed locally by users of device 102. For example, the instructions may
be received
and stored, e.g., temporarily, in a memory or any suitable short-term memory
or buffer of
device 102, e.g., prior to being executed by processor 191 of device 102.
[0058] In another example, application 160 may include a front-end to be
executed locally by
device 102, and a backend to be executed by server 170. For example, one or
more first
operations of determining the pupillary distance of the user may be performed
locally, for
example, by device 102, and/or one or more second operations of deteimining
the pupillary
distance may be performed remotely, for example, by server 170, e.g., as
described below.
[0059] In other embodiments, application 160 may include any other suitable
computing
arrangement and/or scheme.
[0060] In some demonstrative embodiments, system 100 may include an interface
110 to
interface between a user of device 102 and one or more elements of system 100,
e.g.,
application 160.
[0061] In some demonstrative embodiments, interface 110 may be implemented
using any
suitable hardware components and/or software components, for example,
processors,
controllers, memory units, storage units, input units, output units,
communication units,
operating systems, and/or applications.
[0062] In some embodiments, interface 110 may be implemented as part of any
suitable
module, system, device, or component of system 100.
[0063] In other embodiments, interface 110 may be implemented as a separate
element of
system 100.
[0064] In some demonstrative embodiments, interface 110 may be implemented as
part of
device 102. For example, interface 110 may be associated with and/or included
as part of
device 102.
[0065] In one example, interface 110 may be implemented, for example, as
middleware,
and/or as part of any suitable application of device 102. For example,
interface 110 may be
implemented as part of application 160 and/or as part of an OS of device 102.
9
CA 02985315 2017-11-07
WO 2016/181308
PCT/IB2016/052671
[0066] In some demonstrative embodiments, interface 160 may be implemented as
part of
server 170. For example, interface 110 may be associated with and/or included
as part of
server 170.
[0067] In one example, interface 110 may include, or may be part of a Web-
based
application, a web-site, a web-page, a plug-in, an ActiveX control, a rich
content component
(e.g., a Flash or Shockwave component), or the like.
[0068] In some demonstrative embodiments, interface 110 may be associated with
and/or
may include, for example, a gateway (GW) 112 and/or an application programming
interface
(API) 114, for example, to communicate information and/or communications
between
elements of system 100 and/or to one or more other, e.g., internal or
external, parties, users,
applications and/or systems.
[0069] In some embodiments, interface 110 may include any suitable Graphic-
User-Interface
(GUI) 116 and/or any other suitable interface.
[0070] In some demonstrative embodiments, application 160 may be configured to
determine
the pupillary distance of the user based on a captured image of the user,
e.g., as described
below.
[0071] In some demonstrative embodiments, the captured image may be captured
by the
user, and may include the eyes of the user, e.g., as described below.
[0072] In one example, extracting a precise PD measurement from a two
dimensional (2D)
captured image, may include measuring, evaluating and/or analyzing one or more
parameters
to determine a three dimensional (3D) environment, for example, to determine
the PD. For
example, the 3D environment may reflect a camera located at a distance from a
face of the
user, and a location of each pupil of the user while looking at the camera,
which may be in an
offset from the center of the pupil, e.g., an offset of up to 1 millimeter.
The location of the
pupil may coincide with the line of sight of the user, e.g., at a visual axis.
[0073] In some demonstrative embodiments, device 102 may include an image
capturing
device, e.g., a camera 118 or any other device, configured to capture the
image.
[0074] In some demonstrative embodiments, device 102 may include a light
source 122
configured to illuminate the user, for example, when the image is captured.
[0075] In some demonstrative embodiments, light source 122 may include a
flash, a LED
light, or any other source of light.
CA 02985315 2017-11-07
WO 2016/181308
PCT/IB2016/052671
[0076] In some demonstrative embodiments, application 160 may be configured to
receive
the captured image of the user, e.g., from the camera 118.
[0077] In some demonstrative embodiments, the captured image may include first
and
second reflections of a light of the light source 122.
[0078] In some demonstrative embodiments, the first reflection may include a
reflection of
the light from a first pupil of the user, e.g., a first Purldnje image from
the first pupil, and the
second reflection may include a reflection of the light from a second pupil of
the user, e.g., a
first Purkinje image from the second pupil).
[0079] In some demonstrative embodiments, application 160 may be configured to
determine
.. the pupillary distance of the user, for example, based on locations of the
first and second
reflections in the captured image, and an estimated distance between device
102 and the
pupils of the user, e.g., when the image is captured.
[0080] In some demonstrative embodiments, application 160 may be configured to
determine
the pupillary distance of the user, for example, based on a number of pixels
between the first
and second reflections, and a pixel to millimeter (mm) ratio of the pixels,
e.g., as described
below.
[0081] In some demonstrative embodiments, application 160 may be configured to
determine
the pupillary distance of the user, for example, based on one or more
attributes of camera
118, e.g., as described below.
[0082] In some demonstrative embodiments, application 160 may be configured to
determine
the pupillary distance of the user, for example, based on an eye radius
parameter, and a
distance between camera 118 and a plane including the pupils of the user,
e.g., as described
below.
[0083] In some demonstrative embodiments, application 160 may be configured to
determine
the pupillary distance of the user, for example, based on orientation
information with respect
to an orientation of device 102, for example, if device 102 is tilted, e.g.,
as described below.
[0084] In some demonstrative embodiments, application 160 may receive the
captured image
including the first and second reflections from the first and second pupils of
the user.
[0085] In one example, application 160 may be configured to determine the PD
locally, for
example, if application 160 is locally implemented by device 102. According to
this example,
camera 118 may be configured to capture the image, and application 160 may be
configured
11
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
to receive the captured image, e.g., from camera 118, to determine the
estimated distance
between device 102 and the pupils of the user, and to determine the pupillary
distance of the
user, e.g., as described below.
[0086] In another example, application 160 may be configured to determine the
PD remotely,
for example, if application 160 is implemented by server 170, or if the back-
end of
application 160 is implemented by server 170, e.g., while the front-end of
application 160 is
implemented by device 102. According to this example, camera 118 may be
configured to
capture the image; the front-end of application 160 may be configured to
receive the captured
image, and to determine the estimated distance between device 102 and the
pupils of the user;
and server 170 and/or the back-end of application 160 may be configured to
determine the
pupillary distance of the user, e.g., based on information received from the
front-end of
application 160.
[0087] In one example, device 102 and/or the front-end of application 160 may
be configured
to send the captured image and the estimated distance to server 170, e.g., via
network 103;
and/or server 170 and/or the back-end of application 160 may be configured to
receive the
captured image and/or the estimated distance, and to determine the pupillary
distance of the
user, for example, based on the captured image and the estimated distance
received from
device 102.
[0088] In some demonstrative embodiments, the captured image may include an
object on a
face of the user ("the reference object").
[0089] In one example, the PD may be extracted from a single image of a person
looking at
the flash of the camera 118, for example, while the camera 118 captures the
image, and the
person is holding an object of a known size close to a feature of the face of
the person.
[0090] In some demonstrative embodiments, application 160 may be configured to
determine
an estimated distance between camera 118 and the reference object, for
example, based on
one or more dimensions of the object on the face of the user, e.g., as
described below.
[0091] In some demonstrative embodiments, application 160 may be configured to
determine
the estimated distance between camera 118 and the reference object, for
example, based on
acceleration information indicating an acceleration of device 102, e.g., as
described below.
[0092] In some demonstrative embodiments, application 160 may be configured to
determine
the estimated distance between camera 118 and the reference object, for
example, based on
12
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
the object on the face of the user and one or more attributes of the camera
118, e.g., as
described below.
[0093] In some demonstrative embodiments, the one or more attributes of camera
118 may
include an Effective Focal Length (EFL) of a lens of the camera 118, a
horizontal Field of
View (FOV) of a sensor of the camera 118, a vertical field of view of the
sensor of camera
118, a resolution of the sensor, a distance ("a sensor pitch") between two
adjacent pixels of
the sensor, ancUor any other additional or alternative attributes of camera
118.
[0094] Reference is made to Fig. 2, which schematically illustrates a lens 210
and a sensor
220 of a camera, in accordance with some demonstrative embodiments. For
example, camera
118 (Fig. 1) may include lens 210 and sensor 220.
[0095] In some demonstrative embodiments, as shown in Fig. 2, the lens 210 may
have an
EFL 222, which may be given and/or calibrated, e.g., by device 102 (Fig. 1),
located at a
distance equal to the lens EFL from the sensor 220.
[0096] In some demonstrative embodiments, a viewing horizontal angle, denoted
och, may be
determined based on the horizontal size of the sensor 220, and the EFL 222 of
the lens 210.
[0097] In some demonstrative embodiments, a viewing vertical angle may be
determined, for
example, based on the vertical size of the sensor 220.
[0098] In some demonstrative embodiments, as shown in Fig. 2, a sensor
horizontal pitch
224, denoted pitch;,, may be defined as a distance between the centers of each
two adjacent
pixels.
[0099] In some demonstrative embodiments, the sensor pitch 224 may be
determined, for
example, based on the horizontal length of the sensor and the total number of
horizontal
pixels of the senor.
[00100] In some demonstrative embodiments, the sensor pitch 224 may be
determined, for
example, based on the EFL 222, the viewing horizontal angle an, and/or the
viewing vertical
angle, e.g., as follows:
2*ef/*tan
sensor horizontal length 2 )
pitch, =
total horizontal pixels pixelsõ
(1)
13
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[001011 Referring back to Fig. 1, in some demonstrative embodiments,
application 160 may
be configured to determine the estimated distance between camera 118 and the
reference
object, for example, based on the one or more attributes of camera 118, e.g.,
the viewing
horizontal angle oth, EFL 222 (Fig. 2), and/or the sensor pitch 224 (Fig. 2),
e.g., as described
below.
[00102] In some demonstrative embodiments, application 160 may be configured
to
determine the estimated distance between camera 118 and the reference object,
for example,
based on the one or more attributes of camera 118, and the one or more
dimensions of the
reference object, e.g., as described below.
[00103] In some demonstrative embodiments, the reference object may include an
object
having one or more known dimensions, e.g., which may be measured and/or given.
For
example, the reference object may include a credit card, a banknote, and/or
the like.
[00104] In some demonstrative embodiments, the reference object may include a
facial
object or element having one or more known dimensions, e.g., which may be
measured
and/or given. For example, the reference object may include an iris, an eye
radius parameter,
and/or the like.
[00105] In some demonstrative embodiments, camera 118 may be configured to
capture the
image including the reference object.
[00106] In some demonstrative embodiments, application 160 may be configured
to
determine the estimated distance between camera 118 and the reference object,
for example,
based on the imaged dimensions of the object in the captured image, the real
dimensions of
the object, and the camera attributes, e.g., as described below.
[00107] Reference is made to Fig. 3, which schematically illustrates an
imaging diagram 300
for capturing an image of an object 302, in accordance with some demonstrative
embodiments.
[00108] In some demonstrative embodiments, as shown in Fig. 3, an image 312 of
object 302
may be captured via a lens 310 of a camera. For example, camera 118 (Fig. 1)
may include
lens 310.
[00109] In some demonstrative embodiments, as shown in Fig. 3, object 302 may
have a
height, denoted h, which may be known and/or given.
14
CA 02985315 2017-11-07
WO 2016/181308 PCT/1B2016/052671
[001101 In some demonstrative embodiments, as shown in Fig. 3, image 312 of
the object
302, e.g., when captured via lens 310, may have an imaged height, denoted h'.
[00111] In some demonstrative embodiments, a distance, denoted u, between lens
310 and
the object 302 may be determined, for example, based on the EFL of lens 310,
which may be
known and/or given, the height h, and/or the imaged height h', e.g., as
described below.
[00112] In some demonstrative embodiments, the following Equation may be
given, for
example, based on triangles similarity in imaging scheme 300, e.g., as
follows:
h _ v efl
¨
h tt u
(2)
wherein v is approximately the EFL of lens 310.
[00113] In some demonstrative embodiments, the imaged height h' of image 312
may be
based on a number of pixels, denoted h'_pixels_estimated, occupied by image
312, and a
sensor pitch, denoted pitch, of lens 310, e.g., as follows:
h' = pitch * h' _ pixels _estimated
(3)
[00114] In some demonstrative embodiments, the distance u may be determined,
for
example, based on Equation 2 and Equation 3, e.g., as follows:
ell* h ell
, ¨
pitch h _pixels _estimated
(4)
[00115] In some demonstrative embodiments, as shown in Fig. 3, object 302 may
be vertical,
e.g., with no tilt.
[00116] In some demonstrative embodiments, an object to be captured by the
camera may be
tilted, e.g., as described below with reference to Fig. 4.
[00117] Reference is made to Fig. 4, which schematically illustrates an
imaging diagram 400
for capturing an image of a tilted object 402, in accordance with some
demonstrative
embodiments.
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[001181 In some demonstrative embodiments, as shown in Fig. 4, an image 412 of
tilted
object 402 may be captured via a lens 410 of a camera. For example, camera 118
(Fig. 1)
may include lens 410.
[00119] In some demonstrative embodiments, as shown in Fig. 4, object 402 may
have a
height, denoted h, which may be known and/or given.
[00120] In some demonstrative embodiments, as shown in Fig. 4, an image 412 of
the object
402, e.g., when captured via lens 410, may have an imaged height, denoted h'.
[00121] In some demonstrative embodiments, as shown in Fig. 4, the imaged
height h' of the
image 412 may reflect a projection of object 402 onto a plane 407 at a tilt
angle, denoted O.
[00122] In some demonstrative embodiments, as shown in Fig. 4, the projection
of height h
may result in an error and/or a reduction, denoted Ah, of the height h of
object 402, which
may reduce the imaged height h' of the image 412.
[00123] In some demonstrative embodiments, the error Ali in the object size h
may be
determined, e.g., as follows:
Ah = h * ¨cos(0))
(5)
[00124] In one example, for an assumed error Ah, which may result, for
example, from a tilt
angle of 100 (degrees), a relative error of the height may be of
approximately, e.g., +1.5%
(percent).
[00125] In some demonstrative embodiments, the relative error may affect the
estimated
distance, for example, by the same percentage.
[00126] Referring back to Fig. 1, in some demonstrative embodiments,
application 160 may
be configured to determine the estimated distance between camera 118 and the
object, for
example, based on a 3D Cartesian coordinate of the object, e.g., as described
below.
[00127] In some demonstrative embodiments, device 102 may include a 3D sensor
124
configured to determine the 3D Cartesian coordinate of the object.
[00128] In some demonstrative embodiments, 3D sensor 124 may be configured to
map the
object to a set of points, e.g., 3 points, denoted yi,
zd, e.g., in a 3 dimension Cartesian
coordinate.
16
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00129] In one example, the set of points may include a projected structure,
including a
distance dependent structure, a distance from defocus structure, a stereo ¨
based triangulation
structure, and/or the like.
[00130] In some demonstrative embodiments, a distance, denoted d, between the
object and
camera 118 may be determined, e.g., as follows:
d x0)2 +(y, ¨ yo)2+(z, ¨z0)
(6)
wherein { xo, yo, zo) denotes the camera location, e.g., in the same Cartesian
coordinate
system as the object, and k denotes a discrete point on the object, which was
captured by the
3D sensor 124.
[00131] In some demonstrative embodiments, application 160 may be configured
to estimate
the distance from the camera to the object, for example, based on information
from the 3D
sensor 124.
[00132] In some demonstrative embodiments, 3D sensor 124 may be configured to
provide
information describing each pixel in an image or each group of pixels in the
image as a
function of distance from the camera, or as a function of absolute dimension,
e.g., in meters,
inches or any other size units.
[00133] In one example, the function of distance may enable application 160 to
determine
the distance between the object and camera 118.
[00134] In another example, the function of absolute dimension may enable to
determine a
distance to an object, for example, based on Equation 4. In one example,
application 160 may
determine the object size h, for example, based on the information from 3D
sensor 124, for
example, by an estimation of how many pixels the imaged height of the object
acquired in the
image.
[00135] In some demonstrative embodiments, application 160 may be configured
to
determine the distance between the camera 118 and the eye of the user, e.g.,
even without
using the object, for example, by using acceleration information corresponding
to the
acceleration of device 102, e.g., as described below.
[00136] In some demonstrative embodiments, application 160 may be configured
to
determine the estimated distance between the camera 118 and the eyes of the
user, for
17
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
example, based on the acceleration information indicating the acceleration of
device 102,
e.g., as described below.
[00137] In some demonstrative embodiments, device 102 may include an
accelerometer 126
to provide to application 160 the acceleration information of device 102.
[00138] In some demonstrative embodiments, accelerometer 126 may be configured
to
provide the acceleration information at a given time, for example, for each
axis, e.g., of the
Cartesian coordinate system.
[00139] In some demonstrative embodiments, application 160 may be configured
to
determine the distance between the camera 118 and the eyes of the user, for
example, based
on satisfaction of a set of two conditions, e.g., as described below.
[00140] In some demonstrative embodiments, application 160 may determine the
distance
between the camera 118 and the eyes of the user, for example, after performing
an
initialization procedure, which may include setting an initial distance,
denoted xo, between
the eye of the user and the camera 118, when holding device 102 close to the
eye of the user.
[00141] In some demonstrative embodiments, application 160 may cause device
102 to
instruct the user to begin the measurement for the distance between the camera
118 and the
eyes of the user, for example, after the initialization procedure, by
instructing the user to
move the device 102 away from the eyes.
[00142] In some demonstrative embodiments, application 160 may receive from
accelerometer 126 the acceleration infoimation of device 102, e.g., in one or
more, e.g., all,
axes of the Cartesian coordinate system, for example, according to the
movement of device
102.
[00143] In some demonstrative embodiments, application 160 may determine an x-
axis
distance on the X-axis, denoted x(t'), at a given time, for example, based on
acceleration
information on the X-axis, denoted a(t), at the given time, e.g., as follows:
X(1) a.,(011ble)ft v.(e)ott 0.(041: -v LI 4; Md. if 4.0)41 ff
11.0* x`$
0 0
(7)
18
CA 02985315 2017-11-07
WO 2016/181308 PCT/1B2016/052671
[00144] In some demonstrative embodiments, application 160 may determine the x-
axis
distance x(t'), for example, based on a velocity, denoted v( (t'), of device
102 at the given
time, e.g., as follows:
rt. õ
v ,x(' j 0 ax( )dt
(8)
[00145] In some demonstrative embodiments, application 160 may determine a Y-
axis
distance on the Y-axis, denoted y(t'), for example, based on acceleration,
denoted a(t), of
device 102 on the Y-axis, e.g., in a similar manner to determining the
distance x(t').
[00146] In some demonstrative embodiments, application 160 may determine a Z-
axis
distance on the Z-axis, denoted z(r), for example, based on acceleration,
denoted (40, of
device 102 on the Z-axis, e.g., in a similar manner to determining the
distance x(t').
[00147] In some demonstrative embodiments, application 160 may determine the
estimated
distance, denoted r(t' ), of the camera 118 from the eye, for example, based
on the X-axis
distance, the Y-axis distance, and the Z-axis distance, e.g., as follows:
(9)
[00148] In some demonstrative embodiments, an accuracy of the estimated
distance r(e)
may be increased, for example, by using more than one measurement to estimate
the distance,
e.g., as described below.
[00149] In some demonstrative embodiments, application 160 may be configured
to use the
acceleration information in combination with information from other distance
metering
sensors, for example, to increase the metering range, reliability, accuracy
and/or sensitivity.
[00150] In some demonstrative embodiments, application 160 may be configured
to increase
an accuracy of the distance estimation by accelerometer 126, for example, by
integrating one
or more images captured by camera 118, for example, in addition to the
acceleration
information.
[00151] In some demonstrative embodiments, application 160 may be configured
to control,
cause, trigger, and/or instruct camera 118 to capture one or more images, for
example, during
the movement of device 102, e.g., after the initialization procedure.
19
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00152] In some demonstrative embodiments, application 160 may be configured
to use
information from the captured images, for example, to increase the accuracy of
the estimated
distance, e.g., based on the acceleration information.
[00153] In some demonstrative embodiments, application 160 may use the
information from
the captured images, for example, when the captured images include an object,
which has
known dimensions, e.g., as described above.
[00154] In some demonstrative embodiments, application 160 may be configured
to
determine a distance between a pair of images of the captured images, for
example, based on
a change in magnification of the object.
[00155] In some demonstrative embodiments, an error of the accelerometer
information may
not be accumulated throughout the movement of device 102, for example, if the
distance
between the pair of images is used to evaluate the acceleration information.
[00156] In one example, the initialization procedure may be performed at a
time, denoted to,
followed by N camera acquisitions at times, denoted tri, ez e3, t'4...t'N),
and at distances,
denoted fr-'7, r'z r'4...r'N}, determined from the accelerometer
information sensor data,
and the related sizes, denoted {I/ h'2, h'3, h'4...h'N}, of the object at the
captured images.
[00157] In some demonstrative embodiments, an optimization for the distance
measurements
related to the accelerometer information may be performed to reduce the error
of the
accelerator information, for example, when all the captured correspond to the
same size h of
the object.
[00158] In some demonstrative embodiments, an equation to optimize the minimum
error
may be defined, e.g., as follows:
( 2 \
efi Ii
min vN
1929 39 4 /V
'411=1 }pitch 1)11,h; hõ1_, pixels _estimated
- I
(10)
[00159] In some demonstrative embodiments, application 160 may be configured
to
determine a distance between a plane of the pupils of the user ("the pupils
plane") and the
camera 118, for example, to determine the pupillary distance of the user.
[00160] In some demonstrative embodiments, application 160 may determine the
distance
between the pupils plane and camera 118, for example, after determining the
distance from
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
the camera 118 to the object, for example, using 3D sensor 124, accelerometer
126, and/or
the captured images including the object, e.g., as described above.
[00161] In some demonstrative embodiments, calculating the distance between
the pupils
plane and camera 118 may enable determining a magnification at the pupils
plane, which
may enable to calculate the absolute distance between the pupils.
[00162] In some demonstrative embodiments, calculating the distance between
the pupils
plane and camera 118 may enable determining an angle at which the eyes were
looking to the
camera, for example, to accommodate for the eye convergence when looking to
camera 118.
[00163] In some demonstrative embodiments, assuming that camera 118
accommodates for
distortion aberration created from a flat sensor and non-optimal lens, the
magnification across
a plane perpendicular to the sensor, or the lens apex, of camera 118, may be
uniform, and
pincushion and barrel distortions may be minimal.
[00164] In some demonstrative embodiments, a
magnification, denoted
Mobject( camera_object_distnace), may define a conversion between an estimated
number of
pixels, denoted hobi `_pixels_estimated, of a captured dimension, denoted
h'obj, of the object at
the captured image at a plain perpendicular to the sensor of camera 118, and
an absolute
dimension of the object, denoted hobj, at a plain including the object.
[00165] In some demonstrative embodiments, determining the magnification may
enable
determining a pixel to millimeter ratio, which may enable calculating the PD
from the
captured image, for example, by calculating a number of pixels, e.g., as
descried below.
[00166] In one example, it may be assumed that camera 118 may be tilted, and
one or more
features in the captured image may be at different distances from the camera
118. According
to this example, each set of pixels in the captured image may represent a
different
magnification.
[00167] In some demonstrative embodiments, the magnification may be based on
the
distance between camera 118 and the object, e.g., as follows:
e
M objõi(camera _object _distance)¨ _______________
fl
camera _object _distance camera _object _distance
(11)
21
CA 02985315 2017-11-07
WO 2016/181308 PCT/1B2016/052671
[00168] In some demonstrative embodiments, the absolute dimension, e.g.,
height hobj, of the
object may be determined based on the magnification and the imaged dimension,
e.g., the
imaged height, h' obi, e.g., as followed:
hob, ¨ 12bj * 111 nbject(camera _object _dis tan ce)=
= b, ¨pixels _estimated * pitch* M objecr(camera _object
_distance)
(12)
[00169] In some demonstrative embodiments, the object may not be positioned on
the plane
of the pupils. For example, the object may be positioned on a forehead of the
user.
[00170] In some demonstrative embodiments, application 160 may be configured
to
determine a change of magnification between an object plane, which includes
the object, and
the pupils plane, while considering the tilt of the acquiring camera 118.
[00171] In some demonstrative embodiments, application 160 may determine the
distance
between a plane of the pupils of the user and the camera 118, for example,
based on an axial
offset between the object and the pupils along an axis perpendicular to a
plane including the
object, for example, the object plane, e.g., as described below.
[00172] In some demonstrative embodiments, application 160 may be configured
to
determine the axial offset between the object and the pupils along the axis
perpendicular to
the plane including the object, e.g., as described below.
[00173] In some demonstrative embodiments, calculating the axial offset may
enable
determining the magnification change between the object plane and the pupils
plane.
[00174] In some demonstrative embodiments, application 160 may be configured
to
determine the change of magnification, while considering a tilt of camera 118.
[00175] In one example, camera 118 may not be vertical to the ground, for
example, when
capturing the image including the object.
[00176] In some demonstrative embodiments, application 160 may be configured
to
determine the distance between the pupils plane and the object plane, for
example, based on
the axial offset and the tilt of camera 180, e.g., as described below.
[00177] In some demonstrative embodiments, device 102 may include an
orientation
estimator 128, configured to determine an orientation of device 102, and/or an
orientation of
one or more elements of device 102, e.g., camera 118.
22
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[001781 In some demonstrative embodiments, application 160 may be configured
to receive,
e.g., from orientation estimator 128, orientation information indicating an
orientation of
device 102, for example, when the image is captured.
[00179] In some demonstrative embodiments, application 160 may be configured
to
determine the pupillary distance of the user, for example, based on the
orientation
information.
[00180] In some demonstrative embodiments, the orientation information may
indicate an
orientation of camera 118.
[00181] In some demonstrative embodiments, the orientation information may
indicate the
tilt angle of camera 118.
[00182] In one example, application 160 may be configured to determine the
tilt angle of
camera 118, e.g., when the image is captured, for example, based on the
orientation of
camera 118 and/or the orientation of device 102.
[00183] In some demonstrative embodiments, application 160 may be configured
to
determine the pupillary distance of the user, for example, based on the
orientation
information and the axial offset between the object and the pupils along an
axis perpendicular
to a plane including the object, e.g., as described below.
[00184] Reference is made to Fig. 5, which schematically illustrates a
capturing diagram 500
for capturing of an object 502 by a tilted camera 518, in accordance with some
demonstrative
embodiments. For example, camera 518 may perform the functionality of camera
118 (Fig.
1).
[00185] In some demonstrative embodiments, as shown in Fig. 5, camera 518 may
be tilted
at a tilt angle, denoted 0, e.g., with respect to the horizon.
[00186] In some demonstrative embodiments, as shown in Fig. 5, camera 518 may
be at a
distance, denoted camera_obj_distance, from object 502.
[00187] In some demonstrative embodiments, as shown in Fig. 5, object 502 may
be located
at a horizontal offset, denoted, horizontal_offset, and a vertical offset,
denoted ver_offset,
from the eyes 506 of the user.
[00188] In some demonstrative embodiments, as shown in Fig. 5, eyes 530 may be
included
in a plane 527, denoted eyes_plane, e.g., the pupils plane, which is
perpendicular to the
sensor of camera 118.
23
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[001891 In some demonstrative embodiments, as shown in Fig. 5, object 502 may
be
included in a plane 529, denoted object_plane, which is perpendicular to the
sensor of camera
118.
[00190] In some demonstrative embodiments, as shown in Fig. 5, there may be an
axial
offset, denoted axis_offset, on an axis perpendicular to the plane 527 and the
plane 529.
[00191] In some demonstrative embodiments, as shown in Fig. 5, the axial
offset, may define
a distance between the plane 527 and the plane 529.
[00192] In some demonstrative embodiments, as shown in Fig. 5, there may be a
vertical
projected offset, denoted projected_ver_offset, between the centers of eyes
530 and object
502, when the centers of eyes 530 and object 502 are projected onto the plane
529 and/or the
plane 527.
[00193] In some demonstrative embodiments, it may be assumed that the
magnification of
the captured image is uniform across planes perpendicular to the camera
sensor, e.g., the
plane 527 and/or the plane 529.
[00194] In some demonstrative embodiments, the axial offset may be determined
based on
the vertical projected offset, the horizontal offset, and the tilt angle,
e.g., as follows:
axis _offset = horizontal_ offset ¨ projected _ver _distance* sin(0)
cos(0)
(13)
[00195] In some demonstrative embodiments, the vertical projected offset may
be
determined, for example, by analyzing a vertical displacement of the eyes 530
from the
object 502 on the projected plane, e.g., the plane 529, for example, by
estimating a number of
pixels between the centers of camera 518 and eyes 530 at the captured image.
[00196] In some demonstrative embodiments, the horizontal offset may be given,
calculated
and/or may be predefined, e.g., approximately 30 millimeter (mm).
[00197] In some demonstrative embodiments, a magnification, denoted Meyes, at
the pupils
plane, e.g., plane 527, may be based on the distance from camera 518 to the
pupils plane.
[00198] In some demonstrative embodiments, the distance from camera 518 to the
pupils
plane may be based on a sum of the distance from the object to the camera 118,
and the axial
offset, e.g., as may be determined according to Equation 13.
24
CA 02985315 2017-11-07
WO 2016/181308 PCT/IB2016/052671
[00199] In some demonstrative embodiments, a distance, denoted u, between the
camera and
the pupils plane may be defined based on a sum of the distance from the object
to the camera
118, and the axial offset, e.g., as follows:
u = camera _ object _ dis tan ce + axis _offset
(14)
[00200] In some demonstrative embodiments, a magnification, denoted Mõõ(u), at
the
distance u may be determined e.g., as follows:
efl
M eyes(14)
camera _object _distance+ axis _offset
(15)
[00201] Referring back to Fig. 1, in some demonstrative embodiments,
application 160 may
be configured to identify a location on the pupil, through which the user
looks into camera
118, e.g., when capturing the image.
[00202] In some demonstrative embodiments, application 160 may be configured
to identify
the location on the pupil, through which the user looks into camera 118, for
example, based
on the reflection of light from the eye in the captured image, e.g., as
described below.
[00203] In some demonstrative embodiments, application 160 may be configured
to identify
the location on the pupil, through which the user looks into camera 118, e.g.,
based on a first
Purkinje image.
[00204] Reference is made to Fig. 6, which schematically illustrates a
horizontal section of a
.. right eye 600 of a user, in accordance with some demonstrative embodiments.
[00205] In some demonstrative embodiments, as shown in Fig. 6, the horizontal
section of
the right eye 600, may depict a difference between a visual axis 602 and an
optical axis 604
of the right eye 600.
[00206] In some demonstrative embodiments, a location 606 in which the visual
axis 602
crosses the pupil may be used to measure the PD, for example, since the eye
600 would rotate
to view the most sharp image, e.g., of camera 118, that is imaged at the Fovea
610.
[00207] In some demonstrative embodiments, the Fovea 610, may be located about
5 degrees
temporally, e.g., towards the ear, for example, when looking from above, to
the optical axis
604. Therefore, the line of sight, in which the eye is rotated to look at the
object, may not
CA 02985315 2017-11-07
WO 2016/181308 PCT/1B2016/052671
coincide with the optical axis 604, which connects the line between the cornea
apex and the
center of the pupil. Accordingly, the location 606 may not be the center of
the pupil.
[00208] In some demonstrative embodiments, application 160 (Fig. 1) may be
configured to
identify location 606, for example, based on a reflection of the light source
122 on eye 600 at
the captured image.
[00209] In one example, location 606 may be identified, for example, by
looking for the first
reflection, e.g., the first Purkinje image, which is the reflection of light
source 122, imaged by
the most outer reflecting cornea surface. The eye may be rotated to view the
light source 122,
and the reflecting cornea surface may be perpendicular to the light source
122. Therefore, the
first reflection may be along the visual axis 602. Accordingly, location 606
may be
determined based on the first reelection in the captured image.
[00210] In some demonstrative embodiments, application 160 (Fig. 1) may
determine the
PD, for example, based on location 606 of the right eye 600 and a location of
the second
reflection in the left eye, e.g., instead of using the center of the pupil or
an arbitrary location
in the pupil.
[00211] Referring back to Fig. 1, in some demonstrative embodiments,
application 160 may
be configured to determine a number of pixels, denoted
heyes'_pixels_estimated, between the
first and second reelections in the captured image, e.g., location 606 (Fig.
6) of the right eye
600 (Fig. 6), and the location of the second reflection of the left eye.
[00212] In some demonstrative embodiments, application 160 may be configured
to calculate
a PD, denoted PDconvergence, for converging eyes, for example, when the eyes
are looking
towards camera 118.
[00213] In some demonstrative embodiments, application 160 may calculate the
PD for
converging eyes, for example, based on the sensor pitch, and the magnification
at the pupils
plane and the number of pixels, e.g., as follows:
PD converg heye' s _pixels _estimated* pitch I M eyes(U)
yõ pixels _estimated* pitch* (camera _object _distance + axis _offset)
efl
(16)
[00214] In some demonstrative embodiments, application 160 may be configured
to calculate
the PD, for example, when the eyes are looking towards infinity ("infinity
eyes").
26
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[002151 In some demonstrative embodiments, application 160 may be configured
to calculate
a correction between the pupillary distance for converging eyes and the
pupillary distance for
infinity eyes, e.g., as described below.
[00216] Reference is made to Fig. 7, which schematically illustrates a PD
between two eyes
720 of a user looking towards a camera 718, in accordance with some
demonstrative
embodiments.
[00217] In some demonstrative embodiments, as shown in Fig. 7, camera 718 may
be located
at a distance, denoted camera_eye_distance, from the eyes 720.
[00218] In some demonstrative embodiments, as shown in Fig. 7, each eye 720 is
rotated at
an angle cg e.g., towards the nose, to look at the camera 718.
[00219] In some demonstrative embodiments, as shown in Fig. 7, a location 706
of a visual
axis 708 crossing the pupil may be displaced transversely at an accommodation
distance,
denoted towards a location 709, e.g., towards the ears, for example, when eyes
720 look
toward infinity.
[00220] In some demonstrative embodiments, the accommodation distance t may
be, for
example, the result of eyes 730 rotating at a radius, denoted R, at the angle
co, to the location
709, e.g., to look towards infinity.
[00221] In some demonstrative embodiments, assuming that the centers of
rotation of eyes
720 are equal, the radiuses R of the eyes may be equal to a predefined value,
e.g., of about
13.5mm.
[00222] In some demonstrative embodiments, locations 709 may be considered,
for
example, when determining the pupillary distance, e.g., for distance
spectacles.
[00223] In some demonstrative embodiments, as shown in Fig. 7, the pupillary
distance for
converging eyes, denoted PD(), may be defined, for example, when eyes 720 are
converged
to look toward a flash of camera 718, for example, if camera 718 is located at
a e, which is
not an infinity distance, e.g., the distance camera_eye_distance.
[00224] In some demonstrative embodiments, the angle co may be expressed as
follows:
PD convergence/
= tan-1 2
camera _eye _distance
27
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
(17)
[00225] In some demonstrative embodiments, the pupillary distance for infinity
eyes,
denoted PDinfinity, e.g., when eyes 720 are looking to infinity, may be
determined, for
example, based on the sum of the pupillary distance PDconvergence for
converging eyes and
the accommodation distance t for the two eyes 720, e.g., as follows:
PD=PDconvergence+ 2r = PDconvergence + 2R sin(co)
(18)
[00226] In some demonstrative embodimentsõ the pupillary distance PDinfinity
may be
determined, for example, by combining Equation 17 and Equation 18, e.g., as
follows:
PDinfinity PDconversence[l + _______
camera eye distance)
(19)
[00227] In some demonstrative embodiments, a negative feedback may reduce an
accumulated error. For example, in a case when a calculated horizontal offset
horizontal_offset is longer than a real horizontal offset, e.g., between the
eye and the object,
the distance camera_eye_distance may be longer, e.g., resulting with a higher
PD in the eyes
plane. However, the accommodation for conversion, e.g., the distance T, from
higher
distance, e.g., may reduce angle co, which may result in a lower addition to
the pupillary
distance, which may reduce the accumulated error.
[00228] Reference is made to Figs. 8A-8F, which schematically illustrate
histograms of
Monte Carlo simulations, in accordance with some demonstrative embodiments.
[00229] In some demonstrative embodiments, the simulations considered
variations in a
distance between the camera to the object, e.g., between 300mm and 900mm, an
error in
camera to object distance estimation, e.g., between -5mm and 15mm, and a
horizontal offset
error between the pupils and the object, e.g., between -15mm and 5mm.
[00230] In some demonstrative embodiments, Fig. 8A shows a histogram of Monte
Carlo
simulations to evaluate the accumulated errors generated from a camera error
to known size
object estimation, for example, when the camera is placed at multiple
distances.
28
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00231] In some demonstrative embodiments, Fig. 8B shows a histogram of Monte
Carlo
simulations to evaluate the accumulated errors generated from an error to the
camera to a
known size object estimation.
[00232] In some demonstrative embodiments, Fig. 8C shows a histogram of Monte
Carlo
simulations to evaluate the error of a horizontal offset between the pupils
and the object.
[00233] In some demonstrative embodiments, Fig. 8D shows a histogram of Monte
Carlo
simulations to depict a variation of the nominal PD.
[00234] In some demonstrative embodiments, Fig. 8E shows the result of an
accumulated
error of the horizontal axis presented as a histogram.
[00235] In some demonstrative embodimentsõ the horizontal axis of Fig. 8E
defines the
accumulated error, and the vertical axis defines the amount of trials that
resulted with that
amount of errors, e.g., when the number of simulations is N=1000.
[00236] In some demonstrative embodiments, Fig. 8F depicts a histogram showing
that the
total error in the measured PD is within the range [-1,+1] mm for at least 95%
of the cases.
[00237] Reference is made to Fig. 9, which schematically illustrates a method
of determining
a PD of a user, in accordance with some demonstrative embodiments. For
example, one or
operations of the method of Fig. 9 may be performed by a mobile device, device
102 (Fig. 1),
a server, e.g., server 170 (Fig. 1), and/or an application, e.g., application
160 (Fig. 1).
[00238] As indicated at block 902, the method may include capturing an image
of eyes of a
user looking at the flash of a camera, and receiving information relating to
an orientation of
the camera, the sensor pitch of the camera, and the EFL of the lens of the
camera. For
example, application 160 (Fig. 1) may receive the captured image including the
first and
second reflections from camera 118 (Fig. 1), and may receive the orientation
information, the
sensor pitch, and the EFL of camera 118 (Fig. 1), e.g., as described above.
[00239] As indicated at block 904, the method may include estimating a
distance from the
camera to an object on the face of the user. For example, application 160
(Fig. 1) may
estimate the distance between camera 118 and the reference object, for
example, using
information from the 3D sensor 124 (Fig. 1), the acceleration information from
accelerometer
128 (Fig. 1), and/or based on dimensions of the object, e.g., as described
above.
[00240] As indicated at block 906, the method may include calculating an axial
offset
between an object plane including the object and a pupils-plane including the
pupils of the
29
CA 02985315 2017-11-07
WO 2016/181308
PCT/IB2016/052671
user, for example, based on the camera orientation. For example, application
160 (Fig. 1)
may determine the axial offset between the object plane and the pupils plane,
for example,
based on the orientation information from orientation estimator 128 (fig. 1),
e.g., as described
above.
.. [00241] As indicated at block 908, the method may include determining a
magnification at
the pupils-plane, based on the axial distance and the measured distance from
the camera to
the object, for example, using the EFL and the sensor pitch. For example,
application 160
(Fig. 1) may determine the magnification at the pupils-plane, for example,
based on the axial
offset and the distance from camera 118 (Fig. 1) to the object, e.g., as
described above.
[00242] As indicated at block 910, the method may include identifying first
and second
reflections of the flash on the eyes of the user, and measuring the distance,
e.g., in pixels,
between the first reflection and the second reflection. For example,
application 160 (Fig. 1)
may estimate the distance, e.g., in pixels, between the first reflection and
the second
reflection, e.g., as described above.
[00243] As indicated at block 912, the method may include converting the
distance in pixels
into distance units, for example, according to the magnification at the pupils
plane. For
example, application 160 (Fig. 1) may estimate the distance between the first
reflection and
the second reflection, e.g., as described above.
[00244] As indicated at block 914, the method may include accommodating the
measured
distance for eye convergence, for example, by calculating where the first and
second
reflections would have been imaged for eyes looking to infinity, and setting
the inter
pupillary distance for far distance spectacles based on the accommodation. For
example,
application 160 (Fig. 1) may determine the pupillary distance PDinfinity, for
example, based
on the distance T, e.g., as described above.
[00245] In some demonstrative embodiments, the method may optionally include
calculating
where the first and second reflections would have been imaged for an eye
rotation to a near
distance, for example, a predefined distance of 45 centimeter, and setting the
near pupillary
distance for near vision.
[00246] In some demonstrative embodiments, a method of determining a PD of a
user may
include, for example, only some of the operations of Fig. 9, for example,
while not including
one or more other operations of the method of Fig. 9.
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00247] In some demonstrative embodiments, a method of determining a PD may be
performed, for example, even without performing one or more, e.g., all, of the
operations
described above with respect to blocks 906 and/or 908, for example, if a
distance between the
camera and the pupils is known, or determined.
[00248] In some demonstrative embodiments, the distance between the camera and
the
pupils may be determined, for example, based on a size of a facial future of
the face of the
user.
[00249] In one example, the method of determining a PD may include calibrating
and/or
measuring a size of the facial feature, e.g., an Iris diameter; capturing an
image of the face
using the flash of the camera; and determining the distance from the camera to
the pupils, for
example, based on the facial feature.
[00250] In some demonstrative embodiments, calibrating and/or measuring the
facial feature
may be, for example, by capturing in an image including the facial object and
a reference
object, e.g., a credit card, which may be placed on the face of the user.
[00251] For example, a user may cover one eye of the user with the reference
object, e.g., the
credit card, for example, to enable a calibration of a diameter of an iris of
the other eye.
[00252] Reference is made to Fig. 10, which schematically illustrates a method
of
determining a PD of a user, in accordance with some demonstrative embodiments.
For
example, one or operations of the method of Fig. 10 may be performed by a
mobile device,
device 102 (Fig. 1), a server, e.g., server 170 (Fig. 1), and/or an
application, application 160
(Fig. 1)
[00253] As indicated at block 1002, the method may include receiving a
captured image
including first and second reflections of light of a light source, the first
reflection including a
reflection of the light from a first pupil of the user. For example,
application 160 (Fig. 1) may
.. receive the captured image including the first and second reflections,
e.g., as described above.
[00254] As indicated at block 1004, the method may include determining the
pupillary
distance based on locations of the first and second reflections in the
captured image and an
estimated distance between a camera used to capture the image and the pupils
of the user,
when the image is captured. For example, application 160 (Fig. 1) may
determine the
pupillary distance of the user, for example, based on locations of the first
and second
reflections in the captured image and an estimated distance between device 102
(Fig. 1) and
the pupils of the user, when the image is captured, e.g., as described above.
31
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00255] Reference is made to Fig. 11, which schematically illustrates a
product of
manufacture 1000, in accordance with some demonstrative embodiments. Product
1100 may
include one or more tangible computer-readable non-transitory storage media
1102, which
may include computer-executable instructions, e.g., implemented by logic 1104,
operable to,
when executed by at least one computer processor, enable the at least one
computer processor
to implement one or more operations at device 102 (Fig. 1), server 170 (Fig.
1), and/or
application 160 (Fig. 1), and/or to perform, trigger and/or implement one or
more operations,
communications and/or functionalities according to Figs. 1-10, and/or one or
more operations
described herein. The phrase "non-transitory machine-readable medium" is
directed to
include all computer-readable media, with the sole exception being a
transitory propagating
signal.
[00256] In some demonstrative embodiments, product 1100 and/or machine-
readable storage
medium 1102 may include one or more types of computer-readable storage media
capable of
storing data, including volatile memory, non-volatile memory, removable or non-
removable
memory, erasable or non-erasable memory, writeable or re-writeable memory, and
the like.
For example, machine-readable storage medium 1102 may include, RAM, DRAM,
Double-
Data-Rate DRAM (DDR-DRAM), SDRAM, static RAM (SRAM), ROM, programmable
ROM (PROM), erasable programmable ROM (EPROM), electrically erasable
programmable
ROM (EEPROM), Compact Disk ROM (CD-ROM), Compact Disk Recordable (CD-R),
Compact Disk Rewriteable (CD-RW), flash memory (e.g., NOR or NAND flash
memory),
content addressable memory (CAM), polymer memory, phase-change memory,
ferroelectric
memory, silicon-oxide-nitride-oxide-silicon (SONOS) memory, a disk, a floppy
disk, a hard
drive, an optical disk, a magnetic disk, a card, a magnetic card, an optical
card, a tape, a
cassette, and the like. The computer-readable storage media may include any
suitable media
involved with downloading or transferring a computer program from a remote
computer to a
requesting computer carried by data signals embodied in a carrier wave or
other propagation
medium through a communication link, e.g., a modem, radio or network
connection.
[00257] In some demonstrative embodiments, logic 1104 may include
instructions, data,
and/or code, which, if executed by a machine, may cause the machine to perform
a method,
process and/or operations as described herein. The machine may include, for
example, any
suitable processing platform, computing platform, computing device, processing
device,
computing system, processing system, computer, processor, or the like, and may
be
implemented using any suitable combination of hardware, software, firmware,
and the like.
32
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00258] In some demonstrative embodiments, logic 1104 may include, or may be
implemented as, software, a software module, an application, a program, a
subroutine,
instructions, an instruction set, computing code, words, values, symbols, and
the like. The
instructions may include any suitable type of code, such as source code,
compiled code,
interpreted code, executable code, static code, dynamic code, and the like.
The instructions
may be implemented according to a predefined computer language, manner or
syntax, for
instructing a processor to perform a certain function. The instructions may be
implemented
using any suitable high-level, low-level, object-oriented, visual, compiled
and/or interpreted
programming language, such as C, C++, Java, BASIC, Matlab, Pascal, Visual
BASIC,
.. assembly language, machine code, and the like.
EXAMPLES
[00259] The following examples pertain to further embodiments.
[00260] Example 1 includes a product comprising one or more tangible computer-
readable
non-transitory storage media comprising computer-executable instructions
operable to, when
executed by at least one computer processor, enable the at least one computer
processor to
implement operations of measuring a pupillary distance between pupils of a
user, the
operations comprising receiving a captured image comprising first and second
reflections of a
light of a light source, the first reflection comprising a reflection of the
light from a first pupil
of the user, and the second reflection comprising a reflection of the light
from a second pupil
of the user; and determining the pupillary distance based on locations of the
first and second
reflections in the captured image and an estimated distance between an image
capturing
device and pupils of the user, when the image is captured.
[00261] Example 2 includes the subject matter of Example 1, and optionally,
wherein the
captured image comprises an object on a face of the user, the estimated
distance is based on
one or more dimensions of the object.
[00262] Example 3 includes the subject matter of Example 2, and optionally,
wherein the
operations comprise determining art axial offset between the object and the
pupils along an
axis perpendicular to a plane including the object, and determining the
pupillary distance
based on the axial offset.
[00263] Example 4 includes the subject matter of Example 2 or 3, and
optionally, wherein
the estimated distance is based on a three dimensional (3D) Cartesian
coordinate of a feature
of the face.
33
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00264] Example 5 includes the subject matter of any one of Examples 1-4, and
optionally,
wherein the estimated distance is based on acceleration information indicating
an acceleration
of the image capturing device.
[00265] Example 6 includes the subject matter of any one of Examples 1-5, and
optionally,
wherein the operations comprise determining the pupillary distance based on a
number of
pixels between the first and second reflections, and a pixel to millimeter
(mm) ratio of the
pixels.
[00266] Example 7 includes the subject matter of any one of Examples 1-6, and
optionally,
wherein the operations comprise receiving orientation information indicating
an orientation
of the image capturing device when the image is captured, and determining the
pupillary
distance based on the orientation information.
[00267] Example 8 includes the subject matter of Example 7, and optionally,
wherein the
orientation information indicates a tilt angle of the image capturing device.
[00268] Example 9 includes the subject matter of any one of Examples 1-8, and
optionally,
wherein the operations comprise determining the pupillary distance based on
one or more
attributes of the image capturing device.
[00269] Example 10 includes the subject matter of Example 9, and optionally,
wherein the
one or more attributes comprise at least one attribute selected from the group
consisting of an
Effective Focal Length (EFL) of a lens of the image capturing device, a
horizontal field of
view of a sensor of the image capturing device, a vertical field of view of
the sensor, a
resolution of the sensor, and a distance between two adjacent pixels of the
sensor.
[00270] Example 11 includes the subject matter of any one of Examples 1-10,
and
optionally, wherein the operations comprise determining the pupillary distance
based on an
eye radius parameter and a distance between the image capturing device and a
plane
comprising the pupils.
[00271] Example 12 includes the subject matter of any one of Examples 1-11,
and
optionally, wherein the pupillary distance comprises a near pupillary distance
or a far
pupillary distance.
[00272] Example 13 includes a mobile device configured to measure a pupillary
distance
between pupils of a user, the mobile device comprising a camera to capture an
image
comprising first and second reflections of a light of a light source, the
first reflection
34
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
comprising a reflection of the light from a first pupil of the user, and the
second reflection
comprising a reflection of the light from a second pupil of the user; and a
pupillary distance
calculator to receive the captured image, and to determine the pupillary
distance based on
locations of the first and second reelections in the captured image and an
estimated distance
between the mobile device and the pupils, when the image is captured.
[00273] Example 14 includes the subject matter of Example 13, and optionally,
wherein the
captured image comprises an object on a face of the user, the estimated
distance is based on
one or more dimensions of the object.
[00274] Example 15 includes the subject matter of Example 14, and optionally,
wherein the
mobile device is configured to determine an axial offset between the object
and the pupils
along an axis perpendicular to a plane including the object, and to determine
the pupillary
distance based on the axial offset.
[00275] Example 16 includes the subject matter of Example 14 or 15, and
optionally,
wherein the estimated distance is based on a three dimensional (3D) Cartesian
coordinate of a
feature of the face.
[00276] Example 17 includes the subject matter of any one of Examples 13-16,
and
optionally, wherein the estimated distance is based on acceleration
information indicating an
acceleration of the image capturing device.
[00277] Example 18 includes the subject matter of any one of Examples 13-17,
and
optionally, wherein the mobile device is configured to determine the pupillary
distance based
on a number of pixels between the first and second reflections, and a pixel to
millimeter
(mm) ratio of the pixels.
[00278] Example 19 includes the subject matter of any one of Examples 13-18,
and
optionally, wherein the mobile device is configured to receive orientation
information
.. indicating an orientation of the image capturing device when the image is
captured, and to
determine the pupillary distance based on the orientation information.
[00279] Example 20 includes the subject matter of Example 19, and optionally,
wherein the
orientation information indicates a tilt angle of the image capturing device.
[00280] Example 21 includes the subject matter of any one of Examples 13-20,
and
optionally, wherein the mobile device is configured to determine the pupillary
distance based
on one or more attributes of the image capturing device.
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00281] Example 22 includes the subject matter of Example 21, and optionally,
wherein the
one or more attributes comprise at least one attribute selected from the group
consisting of an
Effective Focal Length (EFL) of a lens of the image capturing device, a
horizontal field of
view of a sensor of the image capturing device, a vertical field of view of
the sensor, a
resolution of the sensor, and a distance between two adjacent pixels of the
sensor.
[00282] Example 23 includes the subject matter of any one of Examples 13-22,
and
optionally, wherein the operations comprise determining the pupillary distance
based on an
eye radius parameter and a distance between the image capturing device and a
plane
comprising the pupils.
[00283] Example 24 includes the subject matter of any one of Examples 13-23,
and
optionally, wherein the pupillary distance comprises a near pupillary distance
or a far
pupillary distance.
[00284] Example 25 includes a method of measuring a pupillary distance between
pupils of a
user, the method comprising receiving a captured image comprising first and
second
reflections of a light of a light source, the first reflection comprising a
reflection of the light
from a first pupil of the user, and the second reflection comprising a
reflection of the light
from a second pupil of the user; and determining the pupillary distance based
on locations of
the first and second reflections in the captured image and an estimated
distance between an
image capturing device and pupils of the user, when the image is captured.
[00285] Example 26 includes the subject matter of Example 25, and optionally,
wherein the
captured image comprises an object on a face of the user, the estimated
distance is based on
one or more dimensions of the object.
[00286] Example 27 includes the subject matter of Example 26, and optionally,
comprising
determining an axial offset between the object and the pupils along an axis
perpendicular to a
plane including the object, and determining the pupillary distance based on
the axial offset.
[00287] Example 28 includes the subject matter of Example 26 or 27, and
optionally,
wherein the estimated distance is based on a three dimensional (3D) Cartesian
coordinate of a
feature of the face.
[00288] Example 29 includes the subject matter of any one of Examples 25-28,
and
optionally, wherein the estimated distance is based on acceleration
information indicating an
acceleration of the image capturing device.
36
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00289] Example 30 includes the subject matter of any one of Examples 25-29,
and
optionally, comprising determining the pupillary distance based on a number of
pixels
between the first and second reflections, and a pixel to millimeter (mm) ratio
of the pixels.
[00290] Example 31 includes the subject matter of any one of Examples 25-30,
and
optionally, comprising receiving orientation information indicating an
orientation of the
image capturing device when the image is captured, and determining the
pupillary distance
based on the orientation information.
[00291] Example 32 includes the subject matter of Example 31, and optionally,
wherein the
orientation information indicates a tilt angle of the image capturing device.
[00292] Example 33 includes the subject matter of any one of Examples 25-32,
and
optionally, comprising determining the pupillary distance based on one or more
attributes of
the image capturing device.
[00293] Example 34 includes the subject matter of Example 33, and optionally,
wherein the
one or more attributes comprise at least one attribute selected from the group
consisting of an
Effective Focal Length (EFL) of a lens of the image capturing device, a
horizontal field of
view of a sensor of the image capturing device, a vertical field of view of
the sensor, a
resolution of the sensor, and a distance between two adjacent pixels of the
sensor.
[00294] Example 35 includes the subject matter of any one of Examples 25-34,
and
optionally, comprising determining the pupillary distance based on an eye
radius parameter
and a distance between the image capturing device and a plane comprising the
pupils.
[00295] Example 36 includes the subject matter of any one of Examples 25-35,
and
optionally, wherein the pupillary distance comprises a near pupillary distance
or a far
pupillary distance.
[00296] Example 37 includes an apparatus to measure a pupillary distance
between pupils of
a user, the apparatus comprising means for receiving a captured image
comprising first and
second reflections of a light of a light source, the first reflection
comprising a reflection of the
light from a first pupil of the user, and the second reflection comprising a
reflection of the
light from a second pupil of the user; and means for determining the pupillary
distance based
on locations of the first and second reflections in the captured image and an
estimated
distance between an image capturing device and pupils of the user, when the
image is
captured.
37
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00297] Example 38 includes the subject matter of Example 37, and optionally,
wherein the
captured image comprises an object on a face of the user, the estimated
distance is based on
one or more dimensions of the object.
[00298] Example 39 includes the subject matter of Example 38, and optionally,
comprising
.. means for determining an axial offset between the object and the pupils
along an axis
perpendicular to a plane including the object, and determining the pupillary
distance based on
the axial offset.
[00299] Example 40 includes the subject matter of Example 38 or 39, and
optionally,
wherein the estimated distance is based on a three dimensional (3D) Cartesian
coordinate of a
feature of the face.
[00300] Example 41 includes the subject matter of any one of Examples 37-40,
and
optionally, wherein the estimated distance is based on acceleration
information indicating an
acceleration of the image capturing device.
[00301] Example 42 includes the subject matter of any one of Examples 37-41,
and
optionally, comprising means for determining the pupillary distance based on a
number of
pixels between the first and second reflections, and a pixel to millimeter
(mm) ratio of the
pixels.
[00302] Example 43 includes the subject matter of any one of Examples 37-42,
and
optionally, comprising means for receiving orientation information indicating
an orientation
of the image capturing device when the image is captured, and determining the
pupillary
distance based on the orientation information.
[00303] Example 44 includes the subject matter of Example 43, and optionally,
wherein the
orientation information indicates a tilt angle of the image capturing device.
[00304] Example 45 includes the subject matter of any one of Examples 37-44,
and
.. optionally, comprising means for determining the pupillary distance based
on one or more
attributes of the image capturing device.
[00305] Example 46 includes the subject matter of Example 45, and optionally,
wherein the
one or more attributes comprise at least one attribute selected from the group
consisting of an
Effective Focal Length (EFL) of a lens of the image capturing device, a
horizontal field of
view of a sensor of the image capturing device, a vertical field of view of
the sensor, a
resolution of the sensor, and a distance between two adjacent pixels of the
sensor.
38
CA 02985315 2017-11-07
WO 2016/181308
PCT/1B2016/052671
[00306] Example 47 includes the subject matter of any one of Examples 37-46,
and
optionally, comprising means for determining the pupillary distance based on
an eye radius
parameter and a distance between the image capturing device and a plane
comprising the
pupils.
.. [00307] Example 48 includes the subject matter of any one of Examples 37-
47, and
optionally, wherein the pupillary distance comprises a near pupillary distance
or a far
pupillary distance.
[00308] Functions, operations, components and/or features described herein
with reference to
one or more embodiments, may be combined with, or may be utilized in
combination with,
one or more other functions, operations, components and/or features described
herein with
reference to one or more other embodiments, or vice versa.
[00309] While certain features have been illustrated and described herein,
many
modifications, substitutions, changes, and equivalents may occur to those
skilled in the art. It
is, therefore, to be understood that the appended claims are intended to cover
all such
modifications and changes as fall within the true spirit of the disclosure.
39
