Snap Patent | Multi-purpose cameras for simultaneous capture and cv on wearable ar devices
Patent: Multi-purpose cameras for simultaneous capture and cv on wearable ar devices
Patent PDF: 20240323516
Publication Number: 20240323516
Publication Date: 2024-09-26
Assignee: Snap Inc
Abstract
Eyewear having an image signal processor (ISP) dynamically operable in a camera pipeline for augmented reality (AR) and computer vision (CV) systems. Multi-purpose cameras are used for simultaneous image capture and CV on wearable AR devices. The cameras are coupled to a frame and configured to generate images, wherein the cameras and the ISP operate in a first AR mode and capture images having a first resolution suitable for use in AR, and are configured to operate in a second CV mode to provide the images having a second resolution suitable for use in CV. The first resolution in the AR mode is higher than the second resolution in the CV mode, and the cameras and the ISP consume less power in the second CV mode than the first AR mode. The cameras and the ISP save significant system power by operating in the low power mode CV mode.
Claims
What is claimed is:
1.
2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a Continuation of U.S. patent application Ser. No. 17/460,244 filed on Aug. 29, 2021, which claims priority to U.S. Provisional Application Ser. No. 63/085,215 filed on Sep. 30, 2020, and to U.S. Provisional Application Ser. No. 63/113,336 filed on Nov. 13, 2020, the contents of which are incorporated fully herein by reference.
TECHNICAL FIELD
The present subject matter relates to an eyewear device, e.g., smart glasses.
BACKGROUND
Portable eyewear devices, such as smart glasses, headwear, and headgear available today integrate cameras and see-through displays. Power consumption is a function of processing various features of the eyewear device.
BRIEF DESCRIPTION OF THE DRAWINGS
The drawing figures depict one or more implementations, by way of example only, not by way of limitations. In the figures, like reference numerals refer to the same or similar elements.
FIG. 1A is a side view of an example hardware configuration of an eyewear device, which shows a right optical assembly with an image display, and field of view adjustments are applied to a user interface presented on the image display based on detected head or eye movement by a user;
FIG. 1B is a top cross-sectional view of a temple of the eyewear device of FIG. 1A depicting a visible light camera, a head movement tracker for tracking the head movement of the user of the eyewear device, and a circuit board;
FIG. 2A is a rear view of an example hardware configuration of an eyewear device, which includes an eye scanner on a frame, for use in a system for identifying a user of the eyewear device;
FIG. 2B is a rear view of an example hardware configuration of another eyewear device, which includes an eye scanner on a temple, for use in a system for identifying a user of the eyewear device;
FIGS. 2C and 2D are rear views of example hardware configurations of the eyewear device, including two different types of image displays.
FIG. 3 shows a rear perspective view of the eyewear device of FIG. 2A depicting an infrared emitter, an infrared camera, a frame front, a frame back, and a circuit board;
FIG. 4 is a cross-sectional view taken through the infrared emitter and the frame of the eyewear device of FIG. 3;
FIG. 5 illustrates detecting eye gaze direction;
FIG. 6 illustrates detecting eye position;
FIG. 7 depicts an example of visible light captured by the left visible light camera as a left raw image and visible light captured by the right visible light camera as a right raw image;
FIG. 8 illustrates a high-level functional block diagram including example electronic components disposed in eyewear;
FIG. 9 illustrates the camera image processor power consumption for various pixel rates;
FIG. 10 illustrates per-rail power measurements for various pixel rates;
FIG. 11 illustrates a camera pipeline reading out higher resolution data into the ISP;
FIG. 12 illustrates a camera pipeline according to this disclosure that saves power by doing the image downscaling in the cameras themselves;
FIG. 13 illustrates the image quality and color degradations where the left capture is after auto-white balance (AWB), and the right capture completely disables the AWB;
FIG. 14 illustrates an off-the-shelf 3A camera (auto-exposure, auto-white balance, auto-focus) that consumes a lot of power in the form of CPU utilization;
FIG. 15 illustrates an external low power spectral ambient-light sensor (ALS) used to provide basic color temperature information to ISP;
FIG. 16 illustrates the external ALS employed to provide basic brightness information, and basic image properties that can be computed efficiently (e.g. average pixel intensity), to provide a low power auto exposure solution;
FIG. 17 illustrates a general purpose input/output (GPIO) between the two cameras to synchronize the vsyncs control signals;
FIG. 18 illustrates the image frames generated from each of the cameras are matched by the ISP, and put into a single buffer before further algorithmic processing;
FIG. 19A and FIG. 19B illustrate a dynamic mono/stereo camera pipeline, where in FIG. 19B one of the cameras 114A or 114B is dynamically turned off by ISP, and then powered up again, the stereo synchronization (shared vsyncs) is also re-enabled;
FIG. 20 illustrates non-linear power consumption increases, where power consumption vs DDR load increases significantly under heavy load.
FIG. 21 illustrates the image data from the last stage in the ISP input into a shared buffer;
FIG. 22 illustrates a method of image processing according to this disclosure; and
FIG. 23 illustrates a method of operating the cameras in a camera pipeline.
DETAILED DESCRIPTION
This disclosure includes eyewear having an image signal processor (ISP) dynamically operable in a camera pipeline for augmented reality (AR) and computer vision (CV) systems. Multi-purpose cameras are used for simultaneous image capture and CV on wearable AR devices. The cameras are coupled to a frame and configured to generate images, wherein the cameras and the ISP are configured to operate in a first AR mode and capture images having a first resolution suitable for use in AR, and are configured to operate in a second CV mode to provide the images having a second resolution suitable for use in CV. The first resolution in the AR mode is higher than the second resolution in the CV mode, and the cameras and the ISP consume less power in the second CV mode than the first AR mode. The cameras and the ISP save significant system power by operating in the low power mode CV mode.
Additional objects, advantages and novel features of the examples will be set forth in part in the description which follows, and in part will become apparent to those skilled in the art upon examination of the following and the accompanying drawings or may be learned by production or operation of the examples. The objects and advantages of the present subject matter may be realized and attained by means of the methodologies, instrumentalities and combinations particularly pointed out in the appended claims.
In the following detailed description, numerous specific details are set forth by way of examples in order to provide a thorough understanding of the relevant teachings. However, it should be apparent to those skilled in the art that the present teachings may be practiced without such details. In other instances, well known methods, procedures, components, and circuitry have been described at a relatively high-level, without detail, in order to avoid unnecessarily obscuring aspects of the present teachings.
The term “coupled” as used herein refers to any logical, optical, physical or electrical connection, link or the like by which signals or light produced or supplied by one system element are imparted to another coupled element. Unless described otherwise, coupled elements or devices are not necessarily directly connected to one another and may be separated by intermediate components, elements or communication media that may modify, manipulate or carry the light or signals.
The orientations of the eyewear device, associated components and any complete devices incorporating an eye scanner and camera such as shown in any of the drawings, are given by way of example only, for illustration and discussion purposes. In operation for a particular variable optical processing application, the eyewear device may be oriented in any other direction suitable to the particular application of the eyewear device, for example up, down, sideways, or any other orientation. Also, to the extent used herein, any directional term, such as front, rear, inwards, outwards, towards, left, right, lateral, longitudinal, up, down, upper, lower, top, bottom and side, are used by way of example only, and are not limiting as to direction or orientation of any optic or component of an optic constructed as otherwise described herein.
Reference now is made in detail to the examples illustrated in the accompanying drawings and discussed below.
FIG. 1A is a side view of an example hardware configuration of an eyewear device 100, which includes a right optical assembly 180B with an image display 180D (FIG. 2A). Eyewear device 100 includes multiple visible light cameras 114A-B (FIG. 7) that form a stereo camera, of which the right visible light camera 114B is located on a right temple 110B.
The left and right visible light cameras 114A-B have an image sensor that is sensitive to the visible light range wavelength. Each of the visible light cameras 114A-B have a different frontward facing angle of coverage, for example, visible light camera 114B has the depicted angle of coverage 111B. The angle of coverage is an angle range which the image sensor of the visible light camera 114A-B picks up electromagnetic radiation and generates images. Examples of such visible lights camera 114A-B include a high-resolution complementary metal-oxide-semiconductor (CMOS) image sensor and a video graphic array (VGA) camera, such as 640p (e.g., 640×480 pixels for a total of 0.3 megapixels), 720p, or 1080p. Image sensor data from the visible light cameras 114A-B are captured along with geolocation data, digitized by an image processor, and stored in a memory.
To provide stereoscopic vision, visible light cameras 114A-B may be coupled to an image processor (element 912 of FIG. 9) for digital processing along with a timestamp in which the image of the scene is captured. Image processor 912 includes circuitry to receive signals from the visible light camera 114A-B and process those signals from the visible light cameras 114A-B into a format suitable for storage in the memory (element 934 of FIG. 9). The timestamp can be added by the image processor 912 or other processor, which controls operation of the visible light cameras 114A-B. Visible light cameras 114A-B allow the stereo camera to simulate human binocular vision. Stereo cameras provide the ability to reproduce three-dimensional images (element 715 of FIG. 7) based on two captured images (elements 758A-B of FIG. 7) from the visible light cameras 114A-B, respectively, having the same timestamp. Such three-dimensional images 715 allow for an immersive life-like experience, e.g., for virtual reality or video gaming. For stereoscopic vision, the pair of images 758A-B are generated at a given moment in time-one image for each of the left and right visible light cameras 114A-B. When the pair of generated images 758A-B from the frontward facing angles of coverage 111A-B of the left and right visible light cameras 114A-B are stitched together (e.g., by the image processor 912), depth perception is provided by the optical assembly 180A-B.
In an example, a user interface field of view adjustment system includes the eyewear device 100. The eyewear device 100 includes a frame 105, a right temple 110B extending from a right lateral side 170B of the frame 105, and a see-through image display 180D (FIGS. 2A-B) comprising optical assembly 180B to present a graphical user interface to a user. The eyewear device 100 includes the left visible light camera 114A connected to the frame 105 or the left temple 110A to capture a first image of the scene. Eyewear device 100 further includes the right visible light camera 114B connected to the frame 105 or the right temple 110B to capture (e.g., simultaneously with the left visible light camera 114A) a second image of the scene which partially overlaps the first image. Although not shown in FIGS. 1A-B, the user interface field of view adjustment system further includes the processor 932 coupled to the eyewear device 100 and connected to the visible light cameras 114A-B, the memory 934 accessible to the processor 932, and programming in the memory 934, for example in the eyewear device 100 itself or another part of the user interface field of view adjustment system.
Although not shown in FIG. 1A, the eyewear device 100 also includes a head movement tracker (element 109 of FIG. 1B) or an eye movement tracker (element 213 of FIGS. 2A-B). Eyewear device 100 further includes the see-through image displays 180C-D of optical assembly 180A-B for presenting a sequence of displayed images, and an image display driver (element 942 of FIG. 9) coupled to the see-through image displays 180C-D of optical assembly 180A-B to control the image displays 180C-D of optical assembly 180A-B to present the sequence of displayed images 715, which are described in further detail below. Eyewear device 100 further includes the memory 934 and the processor 932 having access to the image display driver 942 and the memory 934. Eyewear device 100 further includes programming (element 934 of FIG. 9) in the memory. Execution of the programming by the processor 932 configures the eyewear device 100 to perform functions, including functions to present, via the see-through image displays 180C-D, an initial displayed image of the sequence of displayed images, the initial displayed image having an initial field of view corresponding to an initial head direction or an initial eye gaze direction (element 230 of FIG. 5).
Execution of the programming by the processor 932 further configures the eyewear device 100 to detect movement of a user of the eyewear device by: (i) tracking, via the head movement tracker (element 109 of FIG. 1B), a head movement of a head of the user, or (ii) tracking, via an eye movement tracker (element 213 of FIGS. 2A-B, FIG. 5), an eye movement of an eye of the user of the eyewear device 100. Execution of the programming by the processor 932 further configures the eyewear device 100 to determine a field of view adjustment to the initial field of view of the initial displayed image based on the detected movement of the user. The field of view adjustment includes a successive field of view corresponding to a successive head direction or a successive eye direction. Execution of the programming by the processor 932 further configures the eyewear device 100 to generate a successive displayed image of the sequence of displayed images based on the field of view adjustment. Execution of the programming by the processor 932 further configures the eyewear device 100 to present, via the see-through image displays 180C-D of the optical assembly 180A-B, the successive displayed images.
FIG. 1B is a top cross-sectional view of the temple of the eyewear device 100 of FIG. 1A depicting the right visible light camera 114B, a head movement tracker 109, and a circuit board. Construction and placement of the left visible light camera 114A is substantially similar to the right visible light camera 114B, except the connections and coupling are on the left lateral side 170A. As shown, the eyewear device 100 includes the right visible light camera 114B and a circuit board, which may be a flexible printed circuit board (PCB) 140. The right hinge 126B connects the right temple 110B to a right temple 125B of the eyewear device 100. In some examples, components of the right visible light camera 114B, the flexible PCB 140, or other electrical connectors or contacts may be located on the right temple 125B or the right hinge 126B.
As shown, eyewear device 100 has a head movement tracker 109, which includes, for example, an inertial measurement unit (IMU). An inertial measurement unit is an electronic device that measures and reports a body's specific force, angular rate, and sometimes the magnetic field surrounding the body, using a combination of accelerometers and gyroscopes, sometimes also magnetometers. The inertial measurement unit works by detecting linear acceleration using one or more accelerometers and rotational rate using one or more gyroscopes. Typical configurations of inertial measurement units contain one accelerometer, gyro, and magnetometer per axis for each of the three axes: horizontal axis for left-right movement (X), vertical axis (Y) for top-bottom movement, and depth or distance axis for up-down movement (Z). The accelerometer detects the gravity vector. The magnetometer defines the rotation in the magnetic field (e.g., facing south, north, etc.) like a compass which generates a heading reference. The three accelerometers detect acceleration along the horizontal, vertical, and depth axis defined above, which can be defined relative to the ground, the eyewear device 100, or the user wearing the eyewear device 100.
Eyewear device 100 detects movement of the user of the eyewear device 100 by tracking, via the head movement tracker 109, the head movement of the head of the user. The head movement includes a variation of head direction on a horizontal axis, a vertical axis, or a combination thereof from the initial head direction during presentation of the initial displayed image on the image display. In one example, tracking, via the head movement tracker 109, the head movement of the head of the user includes measuring, via the inertial measurement unit 109, the initial head direction on the horizontal axis (e.g., X axis), the vertical axis (e.g., Y axis). or the combination thereof (e.g., transverse or diagonal movement). Tracking, via the head movement tracker 109, the head movement of the head of the user further includes measuring, via the inertial measurement unit 109, a successive head direction on the horizontal axis, the vertical axis, or the combination thereof during presentation of the initial displayed image.
Tracking, via the head movement tracker 109, the head movement of the head of the user further includes determining the variation of head direction based on both the initial head direction and the successive head direction. Detecting movement of the user of the eyewear device 100 further includes in response to tracking, via the head movement tracker 109, the head movement of the head of the user, determining that the variation of head direction exceeds a deviation angle threshold on the horizontal axis, the vertical axis, or the combination thereof. The deviation angle threshold is between about 3° to 10°. As used herein, the term “about” when referring to an angle means±10% from the stated amount.
Variation along the horizontal axis slides three-dimensional objects, such as characters, Bitmojis, application icons, etc. in and out of the field of view by, for example, hiding, unhiding, or otherwise adjusting visibility of the three-dimensional object. Variation along the vertical axis, for example, when the user looks upwards, in one example, displays weather information, time of day, date, calendar appointments, etc. In another example, when the user looks downwards on the vertical axis, the eyewear device 100 may power down.
The right temple 110B includes temple body 211 and a temple cap, with the temple cap omitted in the cross-section of FIG. 1B. Disposed inside the right temple 110B are various interconnected circuit boards, such as PCBs or flexible PCBs, that include controller circuits for right visible light camera 114B, microphone(s) 130, speaker(s) 132, low-power wireless circuitry (e.g., for wireless short-range network communication via Bluetooth™), high-speed wireless circuitry (e.g., for wireless local area network communication via WiFi).
The right visible light camera 114B is coupled to or disposed on the flexible PCB 140 and covered by a visible light camera cover lens, which is aimed through opening(s) formed in the right temple 110B. In some examples, the frame 105 connected to the right temple 110B includes the opening(s) for the visible light camera cover lens. The frame 105 includes a front-facing side configured to face outwards away from the eye of the user. The opening for the visible light camera cover lens is formed on and through the front-facing side. In the example, the right visible light camera 114B has an outwards facing angle of coverage 111B with a line of sight or perspective of the right eye of the user of the eyewear device 100. The visible light camera cover lens can also be adhered to an outwards facing surface of the right temple 110B in which an opening is formed with an outwards facing angle of coverage, but in a different outwards direction. The coupling can also be indirect via intervening components.
Left (first) visible light camera 114A is connected to the left see-through image display 180C of left optical assembly 180A to generate a first background scene of a first successive displayed image. The right (second) visible light camera 114B is connected to the right see-through image display 180D of right optical assembly 180B to generate a second background scene of a second successive displayed image. The first background scene and the second background scene partially overlap to present a three-dimensional observable area of the successive displayed image.
Flexible PCB 140 is disposed inside the right temple 110B and is coupled to one or more other components housed in the right temple 110B. Although shown as being formed on the circuit boards of the right temple 110B, the right visible light camera 114B can be formed on the circuit boards of the left temple 110A, the temples 125A-B, or frame 105.
FIG. 2A is a rear view of an example hardware configuration of an eyewear device 100, which includes an eye scanner 213 on a frame 105, for use in a system for determining an eye position and gaze direction of a wearer/user of the eyewear device 100. As shown in FIG. 2A, the eyewear device 100 is in a form configured for wearing by a user, which are eyeglasses in the example of FIG. 2A. The eyewear device 100 can take other forms and may incorporate other types of frameworks, for example, a headgear, a headset, or a helmet.
In the eyeglasses example, eyewear device 100 includes the frame 105 which includes the left rim 107A connected to the right rim 107B via the bridge 106 adapted for a nose of the user. The left and right rims 107A-B include respective apertures 175A-B which hold the respective optical element 180A-B, such as a lens and the see-through displays 180C-D. As used herein, the term lens is meant to cover transparent or translucent pieces of glass or plastic having curved and flat surfaces that cause light to converge/diverge or that cause little or no convergence/divergence.
Although shown as having two optical elements 180A-B, the eyewear device 100 can include other arrangements, such as a single optical element depending on the application or intended user of the eyewear device 100. As further shown, eyewear device 100 includes the left temple 110A adjacent the left lateral side 170A of the frame 105 and the right temple 110B adjacent the right lateral side 170B of the frame 105. The temples 110A-B may be integrated into the frame 105 on the respective sides 170A-B (as illustrated) or implemented as separate components attached to the frame 105 on the respective sides 170A-B. Alternatively, the temples 110A-B may be integrated into temples (not shown) attached to the frame 105.
In the example of FIG. 2A, the eye scanner 213 includes an infrared emitter 115 and an infrared camera 120. Visible light cameras typically include a blue light filter to block infrared light detection, in an example, the infrared camera 120 is a visible light camera, such as a low-resolution video graphic array (VGA) camera (e.g., 640×480 pixels for a total of 0.3 megapixels), with the blue filter removed. The infrared emitter 115 and the infrared camera 120 are co-located on the frame 105, for example, both are shown as connected to the upper portion of the left rim 107A. The frame 105 or one or more of the left and right temples 110A-B include a circuit board (not shown) that includes the infrared emitter 115 and the infrared camera 120. The infrared emitter 115 and the infrared camera 120 can be connected to the circuit board by soldering, for example.
Other arrangements of the infrared emitter 115 and infrared camera 120 can be implemented, including arrangements in which the infrared emitter 115 and infrared camera 120 are both on the right rim 107B, or in different locations on the frame 105, for example, the infrared emitter 115 is on the left rim 107A and the infrared camera 120 is on the right rim 107B. In another example, the infrared emitter 115 is on the frame 105 and the infrared camera 120 is on one of the temples 110A-B, or vice versa. The infrared emitter 115 can be connected essentially anywhere on the frame 105, left temple 110A, or right temple 110B to emit a pattern of infrared light. Similarly, the infrared camera 120 can be connected essentially anywhere on the frame 105, left temple 110A, or right temple 110B to capture at least one reflection variation in the emitted pattern of infrared light.
The infrared emitter 115 and infrared camera 120 are arranged to face inwards towards an eye of the user with a partial or full field of view of the eye in order to identify the respective eye position and gaze direction. For example, the infrared emitter 115 and infrared camera 120 are positioned directly in front of the eye, in the upper part of the frame 105 or in the temples 110A-B at either ends of the frame 105.
FIG. 2B is a rear view of an example hardware configuration of another eyewear device 200. In this example configuration, the eyewear device 200 is depicted as including an eye scanner 213 on a right temple 210B. As shown, an infrared emitter 215 and an infrared camera 220 are co-located on the right temple 210B. It should be understood that the eye scanner 213 or one or more components of the eye scanner 213 can be located on the left temple 210A and other locations of the eyewear device 200, for example, the frame 105. The infrared emitter 215 and infrared camera 220 are like that of FIG. 2A, but the eye scanner 213 can be varied to be sensitive to different light wavelengths as described previously in FIG. 2A.
Similar to FIG. 2A, the eyewear device 200 includes a frame 105 which includes a left rim 107A which is connected to a right rim 107B via a bridge 106; and the left and right rims 107A-B include respective apertures which hold the respective optical elements 180A-B comprising the see-through display 180C-D.
FIGS. 2C-D are rear views of example hardware configurations of the eyewear device 100, including two different types of see-through image displays 180C-D. In one example, these see-through image displays 180C-D of optical assembly 180A-B include an integrated image display. As shown in FIG. 2C, the optical assemblies 180A-B includes a suitable display matrix 180C-D of any suitable type, such as a liquid crystal display (LCD), an organic light-emitting diode (OLED) display, a waveguide display, or any other such display. The optical assembly 180A-B also includes an optical layer or layers 176, which can include lenses, optical coatings, prisms, mirrors, waveguides, optical strips, and other optical components in any combination. The optical layers 176A-N can include a prism having a suitable size and configuration and including a first surface for receiving light from display matrix and a second surface for emitting light to the eye of the user. The prism of the optical layers 176A-N extends over all or at least a portion of the respective apertures 175A-B formed in the left and right rims 107A-B to permit the user to see the second surface of the prism when the eye of the user is viewing through the corresponding left and right rims 107A-B. The first surface of the prism of the optical layers 176A-N faces upwardly from the frame 105 and the display matrix overlies the prism so that photons and light emitted by the display matrix impinge the first surface. The prism is sized and shaped so that the light is refracted within the prism and is directed towards the eye of the user by the second surface of the prism of the optical layers 176A-N. In this regard, the second surface of the prism of the optical layers 176A-N can be convex to direct the light towards the center of the eye. The prism can optionally be sized and shaped to magnify the image projected by the see-through image displays 180C-D, and the light travels through the prism so that the image viewed from the second surface is larger in one or more dimensions than the image emitted from the see-through image displays 180C-D.
In another example, the see-through image displays 180C-D of optical assembly 180A-B include a projection image display as shown in FIG. 2D. The optical assembly 180A-B includes a laser projector 150, which is a three-color laser projector using a scanning mirror or galvanometer. During operation, an optical source such as a laser projector 150 is disposed in or on one of the temples 125A-B of the eyewear device 100. Optical assembly 180A-B includes one or more optical strips 155A-N spaced apart across the width of the lens of the optical assembly 180A-B or across a depth of the lens between the front surface and the rear surface of the lens.
As the photons projected by the laser projector 150 travel across the lens of the optical assembly 180A-B, the photons encounter the optical strips 155A-N. When a particular photon encounters a particular optical strip, the photon is either redirected towards the user's eye, or it passes to the next optical strip. A combination of modulation of laser projector 150, and modulation of optical strips, may control specific photons or beams of light. In an example, a processor controls optical strips 155A-N by initiating mechanical, acoustic, or electromagnetic signals. Although shown as having two optical assemblies 180A-B, the eyewear device 100 can include other arrangements, such as a single or three optical assemblies, or the optical assembly 180A-B may have arranged different arrangement depending on the application or intended user of the eyewear device 100.
As further shown in FIGS. 2C-D, eyewear device 100 includes a left temple 110A adjacent the left lateral side 170A of the frame 105 and a right temple 110B adjacent the right lateral side 170B of the frame 105. The temples 110A-B may be integrated into the frame 105 on the respective lateral sides 170A-B (as illustrated) or implemented as separate components attached to the frame 105 on the respective sides 170A-B. Alternatively, the temples 110A-B may be integrated into temples 125A-B attached to the frame 105.
In one example, the see-through image displays include the first see-through image display 180C and the second see-through image display 180D. Eyewear device 100 includes first and second apertures 175A-B which hold the respective first and second optical assembly 180A-B. The first optical assembly 180A includes the first see-through image display 180C (e.g., a display matrix of FIG. 2C or optical strips 155A-N′ and a projector 150A). The second optical assembly 180B includes the second see-through image display 180D e.g., a display matrix of FIG. 2C or optical strips 155A-N″ and a projector 150B). The successive field of view of the successive displayed image includes an angle of view between about 15° to 30, and more specifically 24°, measured horizontally, vertically, or diagonally. The successive displayed image having the successive field of view represents a combined three-dimensional observable area visible through stitching together of two displayed images presented on the first and second image displays.
As used herein, “an angle of view” describes the angular extent of the field of view associated with the displayed images presented on each of the left and right image displays 180C-D of optical assembly 180A-B. The “angle of coverage” describes the angle range that a lens of visible light cameras 114A-B or infrared camera 220 can image. Typically, the image circle produced by a lens is large enough to cover the film or sensor completely, possibly including some vignetting (i.e., a reduction of an image's brightness or saturation toward the periphery compared to the image center). If the angle of coverage of the lens does not fill the sensor, the image circle will be visible, typically with strong vignetting toward the edge, and the effective angle of view will be limited to the angle of coverage. The “field of view” is intended to describe the field of observable area which the user of the eyewear device 100 can see through his or her eyes via the displayed images presented on the left and right image displays 180C-D of the optical assembly 180A-B. Image display 180C of optical assembly 180A-B can have a field of view with an angle of coverage between 15° to 30°, for example 24°, and have a resolution of 480×480 pixels.
FIG. 3 shows a rear perspective view of the eyewear device of FIG. 2A. The eyewear device 100 includes an infrared emitter 215, infrared camera 220, a frame front 330, a frame back 335, and a circuit board 340. It can be seen in FIG. 3 that the upper portion of the left rim of the frame of the eyewear device 100 includes the frame front 330 and the frame back 335. An opening for the infrared emitter 215 is formed on the frame back 335.
As shown in the encircled cross-section 4 in the upper middle portion of the left rim of the frame, a circuit board, which is a flexible PCB 340, is sandwiched between the frame front 330 and the frame back 335. Also shown in further detail is the attachment of the left temple 110A to the left temple 325A via the left hinge 126A. In some examples, components of the eye movement tracker 213 (FIGS. 2A-B), including the infrared emitter 215, the flexible PCB 340, or other electrical connectors or contacts may be located on the left temple 325A or the left hinge 126A.
FIG. 4 is a cross-sectional view through the infrared emitter 215 and the frame corresponding to the encircled cross-section 4 of the eyewear device of FIG. 3. Multiple layers of the eyewear device 100 are illustrated in the cross-section of FIG. 4, as shown the frame includes the frame front 330 and the frame back 335. The flexible PCB 340 is disposed on the frame front 330 and connected to the frame back 335. The infrared emitter 215 is disposed on the flexible PCB 340 and covered by an infrared emitter cover lens 445. For example, the infrared emitter 215 is reflowed to the back of the flexible PCB 340. Reflowing attaches the infrared emitter 215 to contact pad(s) formed on the back of the flexible PCB 340 by subjecting the flexible PCB 340 to controlled heat which melts a solder paste to connect the two components. In one example, reflowing is used to surface mount the infrared emitter 215 on the flexible PCB 340 and electrically connect the two components. However, it should be understood that through-holes can be used to connect leads from the infrared emitter 215 to the flexible PCB 340 via interconnects, for example.
The frame back 335 includes an infrared emitter opening 450 for the infrared emitter cover lens 445. The infrared emitter opening 450 is formed on a rear-facing side of the frame back 335 that is configured to face inwards towards the eye of the user. In the example, the flexible PCB 340 can be connected to the frame front 330 via the flexible PCB adhesive 460. The infrared emitter cover lens 445 can be connected to the frame back 335 via infrared emitter cover lens adhesive 455. The coupling can also be indirect via intervening components.
In an example, the processor 932 utilizes eye tracker 213 to determine an eye gaze direction 230 of a wearer's eye 234 as shown in FIG. 5, and an eye position 236 of the wearer's eye 234 within an eyebox as shown in FIG. 6. The eye tracker 213 is a scanner which uses infrared light illumination (e.g., near-infrared, short-wavelength infrared, mid-wavelength infrared, long-wavelength infrared, or far infrared) to captured image of reflection variations of infrared light from the eye 234 to determine the gaze direction 230 of a pupil 232 of the eye 234, and also the eye position 236 with respect to the see-through display 180D.
FIG. 7 depicts an example of capturing visible light with cameras. Visible light is captured by the left visible light camera 114A with a left visible light camera field of view 111A as a left raw image 758A. Visible light is captured by the right visible light camera 114B with a right visible light camera field of view 111B as a right raw image 758B having an overlapping field of view 713 with the left visible light camera 114A. Based on processing of the left raw image 758A and the right raw image 758B, a three-dimensional depth map 715 of a three-dimensional scene, referred to hereafter as an image, is generated by processor 932.
FIG. 8 depicts a high-level functional block diagram including example electronic components disposed in eyewear 100/200 (e.g., heat sensor 940), including algorithm 2200 and 2300 operable by image processor 912.
Memory 934 includes instructions for execution by image processor 912 and high-speed processor 932 to implement functionality of eyewear 100/200. Memory 934 also includes instructions for execution by image processor 912 and high-speed processor 932 for ultra-low power for a camera pipeline for computer vision (CV) in augmented reality (AR) systems. The camera pipeline is a set of components used between an image source, such as a camera, and an image renderer, such as a display, for performing intermediate digital image processing. Processor 912 and processor 932 receive power from an eyewear battery (not shown) and execute the instructions stored in memory 934, or integrated with the processor 912 and 932 on-chip, to perform functionality of eyewear device 100/200, and communicating with external devices via wireless connections.
A user interface adjustment system 900 includes a wearable device, which is the eyewear device 100/200 with an eye movement tracker 213 (e.g., shown as infrared emitter 215 and infrared camera 220 in FIG. 2B). User interface adjustments system 900 also includes a mobile device 990 and a server system 998 connected via various networks. Mobile device 990 may be a smartphone, tablet, laptop computer, access point, or any other such device capable of connecting with eyewear device 100 using both a low-power wireless connection 925 and a high-speed wireless connection 937. Mobile device 990 is connected to server system 998 and network 995. The network 995 may include any combination of wired and wireless connections.
Eyewear device 100/200 includes at least two visible light cameras 114A-B (one associated with the left lateral side 170A and one associated with the right lateral side 170B). Eyewear device 100/200 further includes two see-through image displays 180C-D of the optical assembly 180A-B (one associated with the left lateral side 170A and one associated with the right lateral side 170B). The image displays 180C-D are optional in this disclosure. Eyewear device 100/200 also includes image display driver 942, image processor 912, low-power circuitry 920, and high-speed circuitry 930. The components shown in FIG. 8 for the eyewear device 100/200 are located on one or more circuit boards, for example a PCB or flexible PCB, in the temples. Alternatively, or additionally, the depicted components can be located in the temples, frames, hinges, or bridge of the eyewear device 100/200. Left and right visible light cameras 114A-B can include digital camera elements such as a complementary metal-oxide-semiconductor (CMOS) image sensor, charge coupled device, a lens, or any other respective visible or light capturing elements that may be used to capture data, including images of scenes with unknown objects.
An eye movement tracking programming implements the user interface field of view adjustment instructions, including, to cause the eyewear device 100/200 to track, via the eye movement tracker 213, the eye movement of the eye of the user of the eyewear device 100/200. Other implemented instructions (functions) cause the eyewear device 100/200 to determine, a field of view adjustment to the initial field of view of an initial displayed image based on the detected eye movement of the user corresponding to a successive eye direction. Further implemented instructions generate a successive displayed image of the sequence of displayed images based on the field of view adjustment. The successive displayed image is produced as visible output to the user via the user interface. This visible output appears on the see-through image displays 180C-D of optical assembly 180A-B, which is driven by image display driver 942 to present the sequence of displayed images, including the initial displayed image with the initial field of view and the successive displayed image with the successive field of view.
As shown in FIG. 8, high-speed circuitry 930 includes high-speed processor 932, memory 934, and high-speed wireless circuitry 936. In the example, the image display driver 942 is coupled to the high-speed circuitry 930 and operated by the high-speed processor 932 in order to drive the left and right image displays 180C-D of the optical assembly 180A-B. High-speed processor 932 may be any processor capable of managing high-speed communications and operation of any general computing system needed for eyewear device 100/200. High-speed processor 932 includes processing resources needed for managing high-speed data transfers on to a wireless local area network (WLAN) using high-speed wireless circuitry 936 and to server system 998. In certain examples, the high-speed processor 932 executes an operating system such as a LINUX operating system or other such operating system of the eyewear device 100/200 and the operating system is stored in memory 934 for execution. In addition to any other responsibilities, the high-speed processor 932 executing a software architecture for the eyewear device 100/200 is used to manage data transfers with high-speed wireless circuitry 936. In certain examples, high-speed wireless circuitry 936 is configured to implement Institute of Electrical and Electronic Engineers (IEEE) 802.11 communication standards, also referred to herein as Wi-Fi. In other examples, other high-speed communications standards may be implemented by high-speed wireless circuitry 936.
Low-power wireless circuitry 924 and the high-speed wireless circuitry 936 of the eyewear device 100 can include short range transceivers (Bluetooth™) and wireless wide, local, or wide area network transceivers (e.g., cellular or WiFi). Mobile device 990, including the transceivers communicating via the low-power wireless connection 925 and high-speed wireless connection 937, may be implemented using details of the architecture of the eyewear device 100/200, as can other elements of network 995.
Memory 934 includes any storage device capable of storing various data and applications, including, among other things, color maps, camera data generated by the left and right visible light cameras 114A-B and the image processor 912, as well as images generated for display by the image display driver 942 on the see-through image displays 180C-D of the optical assembly 180A-B. While memory 934 is shown as integrated with high-speed circuitry 930, in other examples, memory 934 may be an independent standalone element of the eyewear device 100/200. In certain such examples, electrical routing lines may provide a connection through a chip that includes the high-speed processor 932 from the image processor 912 or low-power processor 922 to the memory 934. In other examples, the high-speed processor 932 may manage addressing of memory 934 such that the low-power processor 922 will boot the high-speed processor 932 any time that a read or write operation involving memory 934 is needed.
Server system 998 may be one or more computing devices as part of a service or network computing system, for example, that include a processor, a memory, and network communication interface to communicate over the network 995 with the eyewear device 100/200 via high-speed wireless circuitry 936, either directly via high-speed wireless connection 937, or via the mobile device 990. Eyewear device 100/200 is connected with a host computer. In one example, the eyewear device 100/200 wirelessly communicates with the network 995 directly, without using the mobile device 990, such as using a cellular network or WiFi, In another example, the eyewear device 100/200 is paired with the mobile device 990 via the high-speed wireless connection 937 and connected to the server system 998 via the network 995.
Output components of the eyewear device 100/200 include visual components, such as the left and right image displays 180C-D of optical assembly 180A-B as described in FIGS. 2C-D (e.g., a display such as a liquid crystal display (LCD), a plasma display panel (PDP), a light emitting diode (LED) display, a projector, or a waveguide). The image displays 180C-D of the optical assembly 180A-B are driven by the image display driver 942. The output components of the eyewear device 100/200 further include acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor), other signal generators, and so forth. The input components of the eyewear device 100/200, the mobile device 990, and server system 998, may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point-based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instruments), tactile input components (e.g., a physical button, a touch screen that provides location and force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like.
Eyewear device 100/200 may optionally include additional peripheral device elements. Such peripheral device elements may include biometric sensors, additional sensors, or display elements integrated with eyewear device 100/200. For example, peripheral device elements may include any I/O components including output components, motion components, position components, or any other such elements described herein.
For example, the biometric components of the user interface field of view adjustment 900 include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components include acceleration sensor components (e.g., accelerometer), gravitation sensor components, rotation sensor components (e.g., gyroscope), and so forth. The position components include location sensor components to generate location coordinates (e.g., a Global Positioning System (GPS) receiver component), WiFi or Bluetooth™ transceivers to generate positioning system coordinates, altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like. Such positioning system coordinates can also be received over wireless connections 925 and 937 from the mobile device 990 via the low-power wireless circuitry 924 or high-speed wireless circuitry 936.
According to some examples, an “application” or “applications” are program(s) that execute functions defined in the programs. Various programming languages can be employed to create one or more of the applications, structured in a variety of manners, such as object-oriented programming languages (e.g., Objective-C, Java, or C++) or procedural programming languages (e.g., C or assembly language). In a specific example, a third party application (e.g., an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform) may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or another mobile operating systems. In this example, the third-party application can invoke API calls provided by the operating system to facilitate functionality described herein.
Low Power Multi-Purpose Camera Pipeline in AR Systems
Power consumption and thermal runtime are challenges in eyewear devices 100/200. This disclosure improves the steady state power consumption of the eyewear 100/200 to ensure the “lens viewing” mode of camera operation can run for as long as possible (ideally not thermally constrained). This is achieved by aggressively improving the camera pipeline, by selectively sacrificing the image quality of the cameras 114A and 114B in some instances, to achieve very low power in instances where the camera images can have a lower resolution and are only used by the CV algorithms, such as when the user won't actually see the images—the camera images are just used for tracking to provide augmented reality experiences. When the user of eyewear device 100/200 wishes to capture an AR experience, the image processor 912, in collaboration with the high-speed processor 932, dynamically switches out of this power optimized mode, into a higher-powered capture configuration which is more optimized for high image quality (IQ) than for power consumption and is in a high-power mode.
To achieve this ultra-low power, referred to as a CV-optimized mode, a number of power optimizations are combined.
Scaled Sensor Mode
Power consumption of the camera pipeline increases with the resolution of the image data, as shown in FIG. 9 illustrating the camera image processor 912, also referred to herein as image signal processor (ISP), power consumption for various pixel rates. FIG. 10 illustrates per-rail power measurements for various pixel rates.
Most CV algorithms only require low resolution images, (typically video graphics array (VGA)-640×480 pixels). However, capture cameras including cameras 114A and 114B typically support much higher resolution images (e.g. 20 megapixel). As illustrated in FIG. 11, a typical camera pipeline 1100 reads out this higher resolution data into the ISP, which ISP downscales the image to whatever resolution is needed.
FIG. 12 illustrates a camera pipeline 1200 according to this disclosure that saves power by doing the image downscaling in the cameras 114A/114B themselves, and greatly reduces the amount of data needed to transfer a camera image over mobile industry processor interface (MIPI) lines from the cameras to the ISP 912, which may be a system on a chip (SOC), where the CV algorithms are running. The image front end (IFE) is the first stage of the ISP 912 that does debayering and minimal IQ tuning. The downscaling function of the ISP 912 is more sophisticated than that of the cameras (yielding better image quality), but CV algorithms are typically more robust to noise so the power savings are worth the tradeoff. When a user wants to capture a video/photo, the camera mode is dynamically switched to the higher resolutions and the CV algorithms run with minimal interruption, but the images they receive are now downscaled in the ISP 912.
Low Power AWB For Tracking Use Cases
In an example as illustrated in FIG. 14, the Qualcomm® off-the-shelf 3A camera (auto-exposure, auto-white balance, auto-focus) consumes a lot of power in the form of CPU utilization. Typically, a good 3A camera is essential for good image quality. As illustrated in FIG. 14, for a typical 3A architecture, statistics from the image are used to configure auto white balance color channel gains. If the 3A camera is completely disabled, the image quality and color degradations preclude the ability to show this to a user, as shown in FIG. 13, where the left capture is after auto-white balance (AWB), and the right capture completely disables the AWB.
However, the CV algorithms can be exploited because the CV algorithms are robust to noise and slight color non-uniformities, and sacrifice image quality for power savings. As illustrated in FIG. 15, an external low power spectral ambient-light sensor (ALS) 1500 is used to provide basic color temperature information to ISP 912, and which indicates when the white balance gains is good enough for the ISP 912. By using the ALS 1500, the costly operation of extracting additional features from the image data itself can be avoided. When the user wishes to capture an AR experience, the high-power, more IQ-optimized auto white balance solution is dynamically enabled.
Low Power AE For Tracking Use Cases
Similar to the low-power auto white balance, the power-hungry, IQ-optimized (Image Quality optimized), proprietary auto exposure (AE) solution is avoided if it is not necessary. The external ALS is employed to provide basic brightness information, and basic image properties that can be computed efficiently (e.g. average pixel intensity), to provide a low power auto exposure solution, as shown in FIG. 16. Again, the high-power, IQ-optimized auto exposure is enabled when the user requests a capture (photo or video recording).
Dynamic Mono to Synchronized Stereo Camera Pipeline
The cameras 114A/114B themselves consume a tremendous amount of power (relative to other components in the system). By turning off one of the cameras when it is not needed, the runtime of the augmented reality experiences is significantly increased. It is important to not turn off the cameras without the tracking algorithms being informed. It is also important that the primary camera stream is not interrupted when turning off the secondary camera, or the trackers will begin to drift, diverge, or both.
Background-Frame Stitching/Synchronization
The computer vision algorithms require stitched, synchronized images from each of the cameras 114A and 114B. Synchronized refers to the fact that both of the cameras 114A and 114B start exposure at approximately the same time. This is achieved in hardware via a general purpose input/output (GPIO) between the two cameras to synchronize the vsyncs control signals as shown in FIG. 17. This is done by sharing a pin driven by the primary camera to synchronize the vsyncs control signals.
Additionally, the image frames generated from each of the cameras 114A and 114B are matched by the ISP 912, and are put into a single buffer before further algorithmic processing as shown in FIG. 18.
Referring to FIG. 19A and FIG. 19B, there is illustrated a dynamic mono/stereo camera pipeline at 1900. As shown in FIG. 19B, when one of the cameras 114A or 114B is dynamically turned off by ISP 912, and then powered up again, the stereo synchronization (shared vsyncs) is also re-enabled.
Zero-Copy Frame Stitching
Copying high-resolution, high-frame rate image data is a very costly operation from a power perspective. It often involves scaling up the frequencies/voltages of the ISP 912 CPU/DDR (central processing unit/double data read) rails, resulting in non-linear ISP power consumption increases as illustrated in FIG. 20, where ISP 912 power consumption vs DDR load increases significantly under heavy load. To mitigate this, the ISP 912 has a dynamic operable topology to dynamically operate such that the image data from the last stage in the ISP 912 is input into a shared buffer 2100 as shown in FIG. 21. The ISP 912 has a camera pipeline topology having a first upper portion configured to operate and process the images in the first mode, and a second lower portion configured to operate and process the images in the second mode. This ISP topology saves a significant amount of ISP 912 power from the unnecessary CPU/DDR operations during the image capture AR mode, referred to as a high IQ resolution mode, while still providing stitched, synchronized image data to the downstream CV algorithms.
FIG. 22 is a flowchart 2200 illustrating one example algorithm 2200 of operating the ISP 912 and a camera pipeline. Although shown as occurring serially, the blocks of FIG. 22 may be reordered or parallelized depending on the implementation.
At block 2202, the user of eyewear 100/200 determines whether to use the cameras 114A and 114B to capture images in the high power high IQ resolution mode, such as to provide an AR experience, referred to as the AR mode, or in an ultra-low power CV mode to capture lower quality images, such as VGA images. These camera images are shown as images 758A and 758B in FIG. 7. The ISP 912 responds to the user's selection by controlling the camera pipeline, such as pipeline 1900 shown in FIGS. 19A and 19B.
At block 2204, the ISP 912 instructs the cameras 114A and 114B to capture high IQ images in high resolution at a high camera power level if the user selects the high-resolution mode such as for an AR experience. If the user selects the ultra-low power CV mode, the ISP 912 instructs the cameras 114A and 114B to capture lower quality images, such as VGA images.
At block 2206, when the ultra-low power CV mode is selected, the cameras 114A and 114B provide the lower quality images 758A and 758B to the ISP 912. The cameras 114A and 114B save significant power by doing image downscaling in the cameras 114A/114B themselves to provide lower quality images, such as VGA quality. This also greatly reduces the amount of data needed to transfer the camera images over mobile industry processor interface (MIPI) lines from the cameras to the ISP 912, which may be a system on a chip (SOC), where the CV algorithms are running.
At block 2208, the ISP 912 operates in the CV mode. The IFE is the first stage of the ISP 912 that does debayering and minimal IQ tuning. The downscaling function of the ISP 912 is more sophisticated than that of the cameras (yielding better image quality), but CV algorithms are typically more robust to noise so the power savings are worth the tradeoff. On camera can be turned off in the CV mode such as shown in FIG. 19B to save power. As shown in FIG. 19B, when one of the cameras 114A or 114B is dynamically turned off by ISP 912, and then powered up again, the stereo synchronization (shared vsyncs) is also re-enabled. As illustrated in FIG. 15, an external low power spectral ambient-light sensor (ALS) 1500 is used to provide basic color temperature information to ISP 912, and which indicates when the white balance gains is good enough for the ISP 912. By using the ALS 1500, the costly operation of extracting additional features from the image data itself can be avoided. When the user wishes to capture an AR experience, the high-power, more IQ-optimized auto white balance solution is dynamically enabled.
At block 2210, when the user wants to capture a video/photo, the camera mode is dynamically switched to the higher resolutions and the CV algorithms run with minimal interruption, but the images the CB algorithms receive are now downscaled in the ISP 912.
FIG. 23 is a flowchart 2300 illustrating an example algorithm 2300 of operating the ISP 912 and a camera pipeline in the dynamic ISP topology, such as pipeline 1900 shown in FIG. 19A and FIG. 19B. This algorithm 2300 utilizes multi-purpose cameras 114A and 114B for simultaneous capture and CV on wearable AR eyewear device 100/200, referred to as the ISP 912 operating in a high IQ mode and a low IQ mode, respectively. The ISP topology/camera configuration simultaneously supports the data requirements for both capture and CV with only two RGB cameras.
Although shown as occurring serially, the blocks of FIG. 23 may be reordered or parallelized depending on the implementation.
At block 2302, the ISP 912 of the camera pipeline determines if the user has selected the eyewear 100/200 to operate in the high IQ mode/high power AR Mode, or in the ultra-low power CV mode/low IQ mode. The ISP 912 controls the capture mode of the cameras 114A and 114B to control the power the cameras consume in each mode.
At block 2304, the ISP 912 instructs the cameras 114A and 114B to capture high IQ images in high resolution (high IQ mode) at a high camera power level if the user selects the high-resolution AR mode such as for an AR experience. If the user selects the ultra-low power CV mode, the ISP 912 instructs the cameras 114A and 114B to capture lower quality images, such as VGA images. These camera images are shown as images 758A and 758B in FIG. 7.
At block 2306, the ISP 912 responds to the user's selection by controlling the camera pipeline, such as pipeline 1900 shown in FIGS. 19A and 19B. When the ultra-low power CV mode is selected, the cameras 114A and 114B automatically provide the lower quality images 758A and 758B to the ISP 912. The cameras 114A and 114B save significant power by doing image downscaling of the captured images in the cameras 114A/114B themselves to provide lower quality images, such as VGA quality. This also greatly reduces the amount of data needed to transfer the camera images over mobile industry processor interface (MIPI) lines from the cameras to the ISP 912, which may be a system on a chip (SOC), where the CV algorithms are running.
At block 2308, when the high power AR mode is selected such that the user captures high quality images and video, the cameras 114A and 114B automatically provide the higher IQ images 758A and 758B to the ISP 912. The cameras 114A and 114B operate as a significant higher power than in the CV mode.
It will be understood that the terms and expressions used herein have the ordinary meaning as is accorded to such terms and expressions with respect to their corresponding respective areas of inquiry and study except where specific meanings have otherwise been set forth herein. Relational terms such as first and second and the like may be used solely to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between such entities or actions. The terms “comprises,” “comprising,” “includes,” “including,” or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises or includes a list of elements or steps does not include only those elements or steps but may include other elements or steps not expressly listed or inherent to such process, method, article, or apparatus. An element preceded by “a” or “an” does not, without further constraints, preclude the existence of additional identical elements in the process, method, article, or apparatus that comprises the element.
Unless otherwise stated, any and all measurements, values, ratings, positions, magnitudes, sizes, and other specifications that are set forth in this specification, including in the claims that follow, are approximate, not exact. Such amounts are intended to have a reasonable range that is consistent with the functions to which they relate and with what is customary in the art to which they pertain. For example, unless expressly stated otherwise, a parameter value or the like may vary by as much as +10% from the stated amount.
In addition, in the foregoing Detailed Description, it can be seen that various features are grouped together in various examples for the purpose of streamlining the disclosure. This method of disclosure is not to be interpreted as reflecting an intention that the claimed examples require more features than are expressly recited in each claim. Rather, as the following claims reflect, the subject matter to be protected lies in less than all features of any single disclosed example. Thus, the following claims are hereby incorporated into the Detailed Description, with each claim standing on its own as a separately claimed subject matter.
While the foregoing has described what are considered to be the best mode and other examples, it is understood that various modifications may be made therein and that the subject matter disclosed herein may be implemented in various forms and examples, and that they may be applied in numerous applications, only some of which have been described herein. It is intended by the following claims to claim any and all modifications and variations that fall within the true scope of the present concepts.
