This disclosure relates to scanning lidar systems for creating a depth map of a field of regard.
Lidar is a technology that can be used to measure distances to remote targets. Typically, a lidar system includes a light source and a detector. The light source emits light pulses toward a target which then scatters the light. Some of the scattered light is received back at the detector. The system determines the distance to the target based on one or more characteristics associated with the returned light pulses. For example, the system may determine the distance to the target based on the time of flight of a returned light pulse.
In some embodiments, a lidar system comprises: a light source configured to emit a pulse of light; a scanner configured to: scan a field of view of the light source in a forward-scanning direction across a plurality of pixels located downrange from the lidar system, wherein the plurality of pixels comprises a first pixel and a second pixel, wherein the second pixel is located adjacent to the first pixel along the forward-scanning direction; direct the pulse of light toward the second pixel; and scan a field of view of a first detector of the lidar system, wherein: the first-detector field of view is scanned in the forward-scanning direction across the plurality of pixels; and the first-detector field of view is offset from the light-source field of view in a direction opposite the forward-scanning direction, wherein, when the pulse is emitted: the first-detector field of view at least partially overlaps the first pixel; and the light-source field of view at least partially overlaps the second pixel; and the first detector, wherein the first detector is configured to detect a portion of the pulse of light scattered by a target located at least partially within the second pixel.
In some embodiments, a method comprises: emitting, by a light source of a lidar system, a pulse of light; scanning a field of view of the light source in a forward-scanning direction across a plurality of pixels located downrange from the lidar system, wherein the plurality of pixels comprises a first pixel and a second pixel, wherein the second pixel is located adjacent to the first pixel along the forward-scanning direction; directing the pulse of light toward the second pixel; scanning a field of view of a first detector of the lidar system, wherein: the first-detector field of view is scanned in the forward-scanning direction across the plurality of pixels; and the first-detector field of view is offset from the light-source field of view in a direction opposite the forward-scanning direction, wherein, when the pulse is emitted: the first-detector field of view at least partially overlaps the first pixel; and the light-source field of view at least partially overlaps the second pixel; and detecting a portion of the pulse of light scattered by a target located at least partially within the second pixel.
Lidar systems can be used to determine the distance to a downrange target. By scanning the lidar system across a field of regard, the system can be used to map the distance to a number of points within the field of regard. Each of these points can be referred to as a pixel. It is often desirable that the depth-mapped points within the field of regard be as closely spaced as possible in order to achieve a high resolution depth map of the field of regard. In addition, it is often desirable that the scan time required to create the depth map be as short as possible. For example, it may be desirable to repeatedly complete depth maps of the field of regard at frame rates fast enough to support a depth map video (e.g., 30 frames per second). This disclosure describes a lidar system 100 which is capable of achieving relatively high resolution depth maps at video frame rates.
After reflecting from the scanner 118, the pulse of light is incident upon a holographic element, pixelator, diffractive element, or similar device 120. The holographic element or pixelator 120 splits the pulse of light into two pulses which now travel along separate angularly-separated paths 140, 141. The two pulses of light propagate downrange from the lidar system 100 toward a target 122. In
In some embodiments, the angular separation θ imparted by the holographic element or pixelator 120 is such that the distance between the two light pulses at the maximum range of the lidar system corresponds to the width of multiple pixels. For example, the holographic element or pixelator can be designed such that the separation between the two light pulses at the maximum range corresponds to an odd number of pixels greater than or equal to three pixels (e.g., 3, 5, 7, 9, etc.). (The significance of this particular spacing is described below.) In
The light pulses scatter from the target 122 and a portion of each pulse propagates back toward the lidar system along reciprocal paths 140, 141. Each return light pulse is reflected by the scanner 118, which has since rotated slightly from its position when the pulses were transmitted, toward the quarter wave plate 116. After passing through the quarter wave plate 116, the return light pulses are reflected by the beam splitter 114 toward a mirror 124. (Although
The detectors 130a, 130b create electrical signals which are indicative of the return light pulses. The electrical signals are fed to a processor 132 which then determines the distance to the target 122 based on, for example, the time of flight of the light pulses. This process is repeated as the scanner 118 traverses the field of regard in order to create a depth map of the scene. The processor 132 can also be used to control the timing of light pulses from the light source 110 and other functions of the lidar system 100.
The lidar system 100 is designed such that each detector 130a, 130b is aligned with a downrange pixel that is respectively offset from one of the downrange pixels with which the light source 110 is aligned (the light source 110 is aligned with two downrange pixels simultaneously because of the pixelator 120). For example, in some embodiments, the detectors 130a, 130b are aimed at the two pixels directly adjacent (in the direction opposite the scanning direction) to the respective downrange pixels with which the light source is aligned.
With reference to
In
A comparison of
As shown in
As just discussed above with respect to
In some embodiments, a lidar system 100 may include a light source 110, a scanner 118, and a detector (e.g., detector 130a). The scanner 118 may be configured to scan a field of view of the light source 110 in a scanning direction across multiple pixels (e.g., pixels #1-#3 illustrated in
In some embodiments, a pixel may represent or may correspond to a field of view of the light source 110. As the light-source beam propagates away from the light source 110, the diameter of the beam (as well as the size of a corresponding pixel) may increase according to the beam divergence. As an example, if the light source 110 has a divergence of 1 milliradian (mrad), then at a distance of 100 m from the light source 110, the light-source beam may have a size or diameter of approximately 10 cm, and a corresponding pixel may also have a corresponding size or diameter of approximately 10 cm. At a distance of 200 m from the light source 110, the light-source beam and the corresponding pixel may each have a diameter of approximately 20 cm.
In some embodiments, the light source 110 may emit a pulse of light at a time t1, and the scanner 118 may direct the pulse of light toward pixel #2 (e.g., when the pulse is emitted, the light-source field of view may partially, substantially, or completely overlap pixel #2). The scanner 118 may also be configured to scan a field of view of detector 130a across the pixels in the same scanning direction as the light-source field of view is scanned. In some embodiments, the detector 130a field of view may be offset from the light-source field of view in a direction opposite the scanning direction (e.g., the field of view of detector 130a lags behind the light-source field of view). The offset between the detector and light-source fields of view may be such that, at time t1 when the pulse is emitted, the field of view of detector 130a at least partially overlaps pixel #1, and the light-source field of view at least partially overlaps pixel #2 (e.g., the field of view of detector 130a lags behind the light-source field of view by approximately one pixel). As an example, at time t1, the field of view of detector 130a may overlap substantially all (e.g., greater than or equal to 80%) of pixel #1 (e.g., as illustrated in
In some embodiments, detector 130a may be configured to detect a portion of the pulse of light which is scattered by a target located at least partially within pixel #2. The portion of the pulse of light may be detected at any suitable time after t1 when the pulse is emitted (e.g., detector 130a may detect the portion of the pulse at a time t2, where t2>t1). In some embodiments, lidar system 100 may include a processor 132 which determines a distance from the lidar system 100 to the target based at least in part on a time of flight of the pulse of light, where the time of flight is (t2-t1). If lidar system 100 measures a time of flight of Δt (e.g., Δt, which equals t2-t1, represents the round-trip time for light to travel from the lidar system 100 to a target and back to the lidar system 100), then the distance D from the target to the lidar system 100 may be expressed as D=c·Δt/2, where c is the speed of light (approximately 3.0×108 m/s). As an example, if a time of flight is measured to be Δt=300 ns, then the distance from the target 122 to the lidar system 100 is approximately D=45.0 m.
If the distance from the lidar system 100 to the target 122 corresponds to a maximum range of the lidar system 100, then a round-trip time corresponding to the maximum range of the lidar system is approximately (t2-t1), and at time t2 (when the detector detects the scattered portion of the emitted pulse) the field of view of detector 130a overlaps substantially all (e.g., greater than or equal to 80%) of pixel #2. The maximum range of lidar system 100 may be any suitable distance, such as for example, 100 m, 200 m, 500 m, or 1 km. As an example, if the maximum range is 200 m, then the time of flight corresponding to the maximum range is approximately 2·(200 m)/c≅1.33 μs. In some embodiments, if the target is a close-range target located within 20% of the maximum range of the lidar system 100, then at time t2 (when the detector detects the scattered portion of the emitted pulse) the detector field of view may overlap less than or equal to 20% of pixel #2. In some embodiments, if the target is a midrange target located between 20% and 80% of the maximum range of the lidar system 100, then at time t2 the detector field of view may overlap between 20% and 80% of pixel #2. In some embodiments, if the target is located a distance greater than or equal to 80% of the maximum range of the lidar system 100, then at time t2 the detector field of view may overlap greater than or equal to 80% of pixel #2.
In some embodiments, the field of view of detector 130a and the light-source field of view may have approximately the same scanning speed. As an example, the detector field of view and the light-source field of view may each scan a width of one pixel in a time that is approximately equal to the round-trip time corresponding to the maximum range of the lidar system 100. In some embodiments, the detector field of view being offset from the light-source field of view in the direction opposite the scanning direction may result in the detector field of view being aligned with pixel #2 at a time t3, where t3 is greater than t1, t3 is greater than or equal to t2, and (t3-t1) corresponds to the round-trip time for the maximum range of the lidar system 100. As an example, the light source may emit a pulse of light toward pixel #2 at time t1, and a corresponding return signal from pixel #2 may be received at a subsequent time t2. The detector field of view may be aligned with pixel #2 at time t3, where time t3 occurs after time t1 (e.g., time t3>t1), and the time (t3-t1) corresponds to the round-trip time for the maximum range of the lidar system 100. If the return signal from pixel #2 includes scattered light from a target located at the maximum range, then t3 may be approximately equal to t2 (e.g., the light is received at approximately the same time as the detector field of view is aligned with pixel #2). Otherwise, if the return signal from pixel #2 originates from a target located closer than the maximum range, then t3 is greater than t2 (e.g., the light is received at time t2 before the detector field of view is substantially aligned with pixel #2 at time t3).
In some embodiments, after emitting a pulse of light at a time t1, the light source 110 may be configured to emit another pulse of light at a time t4. The subsequent pulse of light may be emitted at a time when the detector field of view is aligned with pixel #2 or at a subsequent time. The detector field of view may be aligned with pixel #2 at a time t3, where (t3-t1) corresponds to the round-trip time for the maximum range of the lidar system 100, and the light source 110 may emit the subsequent pulse of light at time t4, where t4 is greater than or equal to t3. Additionally, the pixels may include pixel #3 located adjacent to pixel #2 along the scanning direction, and at time t4 when the pulse is emitted, the field of view of the light source 110 may be aligned to direct the pulse toward pixel #3.
In some embodiments, a lidar system 100 may perform a series of forward and reverse scans. As an example, a forward scan may include the detector FOV being scanned horizontally from left to right, and a reverse scan may include the detector being scanned from right to left, or vice versa. As another example, a forward scan may include the detector FOV being scanned vertically (e.g., scanning upward or downward), and a reverse scan may include the detector FOV being scanned in the opposite direction. As another example, a forward scan may include the detector FOV begin scanned along any suitable direction (e.g., along a 45-degree angle), and a reverse scan may include the detector FOV being scanned along a substantially opposite direction.
As illustrated in
In some embodiments, a lidar system 100 may be configured so that the detector FOV is larger than the light-source FOV, and the detector and light-source FOVs are substantially coincident or overlapped. The light source 110 may emit a pulse of light toward pixel #1 (e.g., when the pulse is emitted, the light-source FOV may partially, substantially, or completely overlap pixel #1). The FOV of a detector may be larger than the light-source FOV, and when the pulse of light is emitted toward pixel #1, the detector FOV may contain and may be approximately centered on pixel #1. As illustrated in
In
In some embodiments, during a forward scan, the light source 110 may emit a pulse of light, and the scanner 118 may direct the pulse of light toward pixel #1. When the pulse is emitted, the FOVs of detector 130g and 130h may each overlap less than or equal to 20% of pixel #1. The scanner 118 may scan the FOVs of detector 130g and 130h along the forward-scanning direction (e.g., left to right in
In some embodiments, during a reverse scan, the light source 110 may emit another pulse of light, and the scanner 118 may direct the pulse of light toward pixel #2. When the pulse is emitted, the FOVs of detector 130g and 130h may each overlap less than or equal to 20% of pixel #2. The scanner 118 may scan the FOVs of detector 130g and 130h along the reverse-scanning direction (e.g., right to left in
In some embodiments, a detector array 128 may include two detectors (e.g., a first detector and a second detector), where the first detector is used to detect scattered light during a forward scan, and the second detector is used to detect scattered light during a reverse scan. The lidar system 100 may include an optical element configured to direct scattered light to the first detector during the forward scan and to direct scattered light to the second detector during the reverse scan. As an example, the scanner 118 may be used to apply a first amount of fixed deflection or angular offset during a forward scan so that scattered light from an emitted pulse is directed to the first detector. Similarly, the scanner 118 may apply a second amount of deflection or angular offset during a reverse scan so that scattered light is directed to the second detector. As another example, the lidar system 100 may include an additional deflection mirror or a deflecting element (e.g., a wedged optic) that has two deflection states for directing scattered light to the first or second detector during a forward or reverse scan, respectively. In some embodiments, a lidar system may include one detector configured to detect scattered light during both forward and reverse scans. The lidar system 100 may include an optical element that provides two states for the orientation of the detector FOV. During a forward scan, the detector FOV may be oriented so that it lags the light source FOV and detects scattered light from emitted pulses, and during a reverse scan, the detector FOV may be oriented so that it also lags the light source FOV.
In some embodiments, a lidar system 100 may include a light source 110, a splitter 120, a scanner 118, and a detector array 128. The light source 110 may emit pulses of light, and the splitter 120 may split each emitted pulse of light into two or more pulses of angularly separated light. The pulses may be separated by any suitable angle Θ, such as for example, 1 mrad, 2 mrad, 5 mrad, 10 mrad, 20 mrad, or 50 mrad. The scanner 118 may scan pulses of light, which are emitted by the light source 110 and split by the splitter 120, along a scanning direction across pixels located downrange from the lidar system 100. The detector array 128 may include two or more detectors. As an example, the splitter 120 may split an emitted pulse into two pulses of angularly separated light (e.g., a first pulse and a second pulse), and the detector array 128 may include a first detector 130a and a second detector 130b. The first and second detectors may be separated by a detector-separation distance along a direction corresponding to the scanning direction of the light pulses. The first detector may be configured to detect scattered light from the first pulse of light, and the second detector may be configured to detect scattered light from the second pulse of light. In some embodiments, the lidar system 100 may also include a processor configured to determine one or more distances to one or more targets based at least in part on a time of flight of the first pulse of light or a time of flight of the second pulse of light.
In some embodiments, the splitter 120 may include a holographic optical element, a diffractive optical element, a polarizing beam splitter, a non-polarizing beam splitter, or a beam splitter with a metallic or dielectric coating. As an example, the splitter 120 may include a beam splitter that is manufactured using a holographic process, or the splitter 120 may include a diffractive beam splitter. As another example, the splitter 120 may include a holographic element or a diffractive element that divides an input beam into two or more output beams. In some embodiments, the splitter 120 may be positioned after the scanner 118 so that the splitter 120 receives the emitted pulses of light from the scanner 118. As illustrated in
In some embodiments, the splitter 120 may be configured to split a pulse of light substantially equally into two pulses. As an example, the splitter 120 may receive one pulse of light and split it into a first pulse and a second pulse, where the first and second pulses each have approximately one-half of the energy or peak power of the received pulse of light. In some embodiments, the splitter 120 may be configured to split a pulse of light into three pulses of angularly separated light (e.g., a first pulse, a second pulse, and a third pulse). Additionally, the detector array may include three detectors (e.g., a first detector, a second detector, and a third detector), where each detector is configured to receive and detect light from one of the respective pulses of light (e.g., the first detector detects light from the first pulse). In some embodiments, the angularly separated pulses of light from the splitter 120 may be split along a direction corresponding to the scanning direction. As an example, if the scanning direction is substantially horizontal, the angularly separated pulses of light may also be split along the same horizontal direction.
In some embodiments, the light source 110 may emit a pulse of light at a time t1, and the splitter 120 may split the pulse into two pulses (e.g., a first pulse and a second pulse). The scanner 118 may scan a first light-source field of view associated with the first pulse and a second light-source field of view associated with the second pulse along the scanning direction and across the pixels located downrange from the lidar system 100. The pixels may include pixel #1, pixel #2, pixel #3, pixel #4, and pixel #5 positioned in order along the scanning direction (e.g., the first or second light-source field of view may scan across the pixels and encounter the pixels in the following order: pixel #1, pixel #2, pixel #3, pixel #4, and pixel #5). In some embodiments, the scanner 118 may direct the first pulse of light toward pixel #2 and the second pulse of light toward pixel #5. Additionally, the scanner 118 may scan a field of view of the first detector and a field of view of the second detector along the scanning direction across the pixels. The first-detector field of view may be offset from the first light-source field of view in a direction opposite the scanning direction, where, at time t1, the first-detector field of view at least partially overlaps the first pixel, and the first light-source field of view at least partially overlaps the second pixel. Similarly, the second detector field of view may be offset from the second light-source field of view in a direction opposite the scanning direction, where, at time t1, the second detector field of view at least partially overlaps the fourth pixel, and the second light-source field of view at least partially overlaps the fifth pixel.
In some embodiments, the separation distance between the first and second pulses of light at the maximum range of the lidar system 100 may correspond to the separation distance between detectors 130a and 130b. As an example, when the first and second pulses of light are incident on a target located at the maximum range of the lidar system 100, the first and second pulses of light may be separated by a distance that corresponds to the detector-separation distance. When the first and second pulses of light are emitted, their fields of view may overlap pixels #2 and #5, respectively. When the first and second pulses of light return to the lidar system 100 after scattering from the target, the first-detector field of view may overlap pixel #2, and the second detector field of view may overlap pixel #5. In some embodiments, the separation distance between the first and second pulses of light at the maximum range of the lidar system 100 may correspond to an odd number of pixels greater than or equal to three pixels. As an example, at the maximum range, the first and second pulses of light may be separated by a distance corresponding to three pixels so that when the first pulse is directed at pixel #2, the second pulse is directed at pixel #5. In some embodiments, the detector-separation distance may correspond to an odd number of pixels greater than or equal to three pixels. As an example, the detector-separation distance may correspond to three pixels so that when the first detector receives light from pixel #2, the second detector receives light from pixel #5.
In some embodiments, the scanner 118 may be configured to scan additional pulses of light, which are emitted by the light source 110 and split by the splitter 120, along a reverse-scanning direction corresponding to the direction opposite the forward-scanning direction. The light source 110 may emit an additional pulse of light while the scanner 118 is scanning in the reverse-scanning direction. As discussed herein, scans of the reverse-scanning direction may be displaced with respect to the forward-scanning direction. In
A lidar system 100 as described or illustrated herein may also include various elements described or illustrated in U.S. Provisional Patent Application No. 62/243,633, filed 19 Oct. 2015 and entitled “Lidar System with Improved Signal-to-Noise Ratio in the Presence of Solar Background Noise” or U.S. Provisional Patent Application No. 62/261,214, filed 30 Nov. 2015 and entitled “Lidar System with a Distributed Laser and a Plurality of Sensor Heads,” each of which is incorporated herein by reference.
Embodiments have been described in connection with the accompanying drawings. However, it should be understood that the figures are not drawn to scale. Distances, angles, etc. are merely illustrative and do not necessarily bear an exact relationship to actual dimensions and layout of the devices illustrated. In addition, the foregoing embodiments have been described at a level of detail to allow one of ordinary skill in the art to make and use the devices, systems, etc. described herein. A wide variety of variation is possible. Components, elements, and/or steps may be altered, added, removed, or rearranged. While certain embodiments have been explicitly described, other embodiments will become apparent to those of ordinary skill in the art based on this disclosure.
The systems and methods described herein can advantageously be implemented, at least in part, using computer software, hardware, firmware, or any combination of software, hardware, and firmware. Software modules can comprise computer executable code for performing the functions described herein. In some embodiments, computer-executable code is executed by one or more general purpose computers. However, a skilled artisan will appreciate, in light of this disclosure, that any module that can be implemented using software to be executed on a general purpose computer can also be implemented using a different combination of hardware, software, or firmware. For example, such a module can be implemented completely in hardware using a combination of integrated circuits. Alternatively or additionally, such a module can be implemented completely or partially using specialized computers designed to perform the particular functions described herein rather than by general purpose computers. In addition, where methods are described that are, or could be, at least in part carried out by computer software, it should be understood that such methods can be provided on computer-readable media (e.g., optical disks such as CDs or DVDs, hard disk drives, flash memories, diskettes, or the like) that, when read by a computer or other processing device, cause it to carry out the method.
While certain embodiments have been explicitly described, other embodiments will become apparent to those of ordinary skill in the art based on this disclosure. Therefore, the scope of the invention is intended to be defined by reference to the claims and not simply with regard to the explicitly described embodiments.
Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57. For example, this application is a continuation of U.S. patent application Ser. No. 15/342,595, filed Nov. 3, 2016, and entitled “LIDAR SYSTEM WITH IMPROVED SCANNING SPEED FOR HIGH-RESOLUTION DEPTH MAPPING,” which claims priority to U.S. Provisional Patent Application No. 62/251,672, filed Nov. 5, 2015, and entitled “LIDAR SYSTEM WITH IMPROVED SCANNING SPEED FOR HIGH-RESOLUTION DEPTH MAPPING,” the entirety of each of which is hereby incorporated by reference herein.
Number | Name | Date | Kind |
---|---|---|---|
5006721 | Cameron et al. | Apr 1991 | A |
5198657 | Trost et al. | Mar 1993 | A |
5696778 | MacPherson | Dec 1997 | A |
5867305 | Waarts et al. | Feb 1999 | A |
5872621 | Wilkerson et al. | Feb 1999 | A |
5892575 | Marino | Apr 1999 | A |
6449384 | Laumeyer et al. | Sep 2002 | B2 |
6710324 | Hipp | Mar 2004 | B2 |
6723975 | Saccomanno | Apr 2004 | B2 |
6747747 | Hipp | Jun 2004 | B2 |
6759649 | Hipp | Jul 2004 | B2 |
7092548 | Laumeyer et al. | Aug 2006 | B2 |
7209221 | Breed et al. | Apr 2007 | B2 |
7345271 | Boehlau et al. | Mar 2008 | B2 |
7443903 | Leonardo et al. | Oct 2008 | B2 |
7532311 | Henderson et al. | May 2009 | B2 |
7570793 | Lages et al. | Aug 2009 | B2 |
7583364 | Mayor et al. | Sep 2009 | B1 |
7649920 | Welford | Jan 2010 | B2 |
7652752 | Fetzer et al. | Jan 2010 | B2 |
7872794 | Minelly et al. | Jan 2011 | B1 |
7902570 | Itzler et al. | Mar 2011 | B2 |
7945408 | Dimsdale et al. | May 2011 | B2 |
7969558 | Hall | Jun 2011 | B2 |
7995796 | Retterath et al. | Aug 2011 | B2 |
8059263 | Haberer et al. | Nov 2011 | B2 |
8072663 | O'Neill et al. | Dec 2011 | B2 |
8081301 | Stann et al. | Dec 2011 | B2 |
8138849 | West et al. | Mar 2012 | B2 |
8279420 | Ludwig et al. | Oct 2012 | B2 |
8280623 | Trepagnier et al. | Oct 2012 | B2 |
8346480 | Trepagnier et al. | Jan 2013 | B2 |
8364334 | Au et al. | Jan 2013 | B2 |
8452561 | Dimsdale et al. | May 2013 | B2 |
8541744 | Liu | Sep 2013 | B1 |
8548014 | Fermann et al. | Oct 2013 | B2 |
8625080 | Heizman et al. | Jan 2014 | B2 |
8675181 | Hall | Mar 2014 | B2 |
8723955 | Klehn et al. | May 2014 | B2 |
8767190 | Hall | Jul 2014 | B2 |
8796605 | Mordarski et al. | Aug 2014 | B2 |
8804787 | Coleman et al. | Aug 2014 | B1 |
8817096 | Ni et al. | Aug 2014 | B1 |
8836922 | Pennecot et al. | Sep 2014 | B1 |
8880296 | Breed | Nov 2014 | B2 |
8896818 | Walsh et al. | Nov 2014 | B2 |
8934509 | Savage-Leuchs et al. | Jan 2015 | B2 |
9000347 | Woodward et al. | Apr 2015 | B2 |
9041136 | Chia | May 2015 | B2 |
9048370 | Urmson et al. | Jun 2015 | B1 |
9063549 | Pennecot et al. | Jun 2015 | B1 |
9069060 | Zbrozek et al. | Jun 2015 | B1 |
9074878 | Steffey et al. | Jul 2015 | B2 |
9086273 | Gruver et al. | Jul 2015 | B1 |
9086481 | Dowdall et al. | Jul 2015 | B1 |
9091754 | d'Aligny | Jul 2015 | B2 |
9103669 | Giacotto et al. | Aug 2015 | B2 |
9121703 | Droz et al. | Sep 2015 | B1 |
9160140 | Gusev et al. | Oct 2015 | B2 |
9170333 | Mheen et al. | Oct 2015 | B2 |
9199641 | Ferguson et al. | Dec 2015 | B2 |
9213085 | Kanter | Dec 2015 | B2 |
9239260 | Bayha et al. | Jan 2016 | B2 |
9246041 | Clausen et al. | Jan 2016 | B1 |
9285464 | Pennecot et al. | Mar 2016 | B2 |
9285477 | Smith et al. | Mar 2016 | B1 |
9297901 | Bayha et al. | Mar 2016 | B2 |
9299731 | Lenius et al. | Mar 2016 | B1 |
9304154 | Droz et al. | Apr 2016 | B1 |
9304203 | Droz et al. | Apr 2016 | B1 |
9304316 | Weiss et al. | Apr 2016 | B2 |
9310471 | Sayyah et al. | Apr 2016 | B2 |
9335255 | Retterath et al. | May 2016 | B2 |
9360554 | Retterath et al. | Jun 2016 | B2 |
9368933 | Nijjar et al. | Jun 2016 | B1 |
9383201 | Jachman et al. | Jul 2016 | B2 |
9383445 | Lu et al. | Jul 2016 | B2 |
9383753 | Templeton et al. | Jul 2016 | B1 |
20020041435 | Krummrich | Apr 2002 | A1 |
20020060784 | Pack et al. | May 2002 | A1 |
20030043058 | Jamieson et al. | Mar 2003 | A1 |
20050214690 | Verheijden et al. | Sep 2005 | A1 |
20060227316 | Gatt | Oct 2006 | A1 |
20060231771 | Lee et al. | Oct 2006 | A1 |
20060290920 | Kämpchen et al. | Dec 2006 | A1 |
20070040121 | Kalayeh | Feb 2007 | A1 |
20070182949 | Niclass | Aug 2007 | A1 |
20070247612 | Pack et al. | Oct 2007 | A1 |
20080027591 | Lenser et al. | Jan 2008 | A1 |
20080074640 | Walsh et al. | Mar 2008 | A1 |
20080181266 | Deladurantaye et al. | Jul 2008 | A1 |
20080309913 | Fallon | Dec 2008 | A1 |
20090122295 | Eaton | May 2009 | A1 |
20090262760 | Krupkin et al. | Oct 2009 | A1 |
20090273770 | Bauhahn et al. | Nov 2009 | A1 |
20100034221 | Dragic | Feb 2010 | A1 |
20100091263 | Kumagai et al. | Apr 2010 | A1 |
20100128744 | Deladurantaye et al. | May 2010 | A1 |
20110085149 | Nathan | Apr 2011 | A1 |
20110122012 | Van Zeijl et al. | May 2011 | A1 |
20120038903 | Weimer et al. | Feb 2012 | A1 |
20120168605 | Milanovic | Jul 2012 | A1 |
20120206712 | Chang et al. | Aug 2012 | A1 |
20120227263 | Leclair et al. | Sep 2012 | A1 |
20120268105 | Mann et al. | Oct 2012 | A1 |
20130010820 | Curtis | Jan 2013 | A1 |
20130033742 | Rogers et al. | Feb 2013 | A1 |
20130282208 | Mendez-Rodriguez et al. | Oct 2013 | A1 |
20140111805 | Albert et al. | Apr 2014 | A1 |
20140146303 | Mitchell et al. | May 2014 | A1 |
20140168631 | Haslim et al. | Jun 2014 | A1 |
20140176933 | Haslim et al. | Jun 2014 | A1 |
20140211194 | Pacala et al. | Jul 2014 | A1 |
20140268098 | Schwartz | Sep 2014 | A1 |
20140268311 | Zhu | Sep 2014 | A1 |
20140293263 | Justice et al. | Oct 2014 | A1 |
20140293266 | Hsu et al. | Oct 2014 | A1 |
20140330479 | Dolgov | Nov 2014 | A1 |
20140376001 | Swanson | Dec 2014 | A1 |
20150109605 | Major, Jr. et al. | Apr 2015 | A1 |
20150131080 | Retterath et al. | May 2015 | A1 |
20150177368 | Bayha et al. | Jun 2015 | A1 |
20150185244 | Inoue et al. | Jul 2015 | A1 |
20150185313 | Zhu | Jul 2015 | A1 |
20150192676 | Kotelnikov et al. | Jul 2015 | A1 |
20150192677 | Yu et al. | Jul 2015 | A1 |
20150204978 | Hammes et al. | Jul 2015 | A1 |
20150214690 | Savage-Leuchs et al. | Jul 2015 | A1 |
20150219765 | Mead et al. | Aug 2015 | A1 |
20150301182 | Geiger et al. | Oct 2015 | A1 |
20150316415 | Islam | Nov 2015 | A1 |
20150323654 | Jachmann et al. | Nov 2015 | A1 |
20150378023 | Royo et al. | Dec 2015 | A1 |
20150378241 | Eldada | Dec 2015 | A1 |
20160025842 | Anderson et al. | Jan 2016 | A1 |
20160041266 | Smits | Feb 2016 | A1 |
20160047896 | Dussan | Feb 2016 | A1 |
20160047901 | Pacala et al. | Feb 2016 | A1 |
20160049765 | Eldada | Feb 2016 | A1 |
20160146939 | Shpunt et al. | May 2016 | A1 |
20160146940 | Koehler | May 2016 | A1 |
20160161600 | Eldada et al. | Jun 2016 | A1 |
20160245919 | Kalscheur et al. | Aug 2016 | A1 |
20170131387 | Campbell et al. | May 2017 | A1 |
20170131388 | Campbell et al. | May 2017 | A1 |
Number | Date | Country |
---|---|---|
WO 2017079483 | May 2017 | WO |
WO 2017095817 | Aug 2017 | WO |
Entry |
---|
Search Report and Written Opinion dated Apr. 4, 2017 in PCT Application No. PCT/US2016/064020. |
Search Report and Written Opinion dated Feb. 1, 2017 in corresponding PCT Application No. PCT/US16/60397, 9 pgs. |
Office Action dated Jul. 13, 2017 in U.S. Appl. No. 15/470,718, 17 pgs. |
Office Action dated Aug. 14, 2017 in U.S. Appl. No. 15/470,708, 15 pgs. |
Number | Date | Country | |
---|---|---|---|
62251672 | Nov 2015 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 15342595 | Nov 2016 | US |
Child | 15479167 | US |