Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Arguments
Applicant’s arguments with respect to claims 1, 11, and 19 have been considered. As stated in the interview conducted on 2/17/2026, and in the interview summary filed 2/19/2026, the rejections of these claims are withdrawn due to the examiner’s error in the analysis of the prior art reference, not because of applicant’s arguments.
Claim Rejections - 35 USC § 103
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 1, 3, 7, 8, 11, 13, 16, 17, 19, and 20 are rejected under 35 U.S.C. 103 as being unpatentable over Helsloot (US 20210033711 A1), in view of Wang (US 20230194684 A1), further in view of Dussan (US 20170242109 A1).
Regarding Claim 1: Helsloot discloses a lidar device (Fig. 1, LIDAR scanning system 100; Fig. 2, LIDAR scanning system 200) comprising:
channels ([0035] “Different groups of pixels can be fired at by activating its corresponding light source”; a light source which has corresponding groups of pixels makes a channel);
a controller (Fig. 2, system controller 23), wherein the controller is configured to:
cause one or more of the light emitters in the array of channels to emit light pulses ([0057] “the laser sources of the illumination unit 10 are triggered by the system controller 23”),
determine, based on a reflection pulse detected by a first light detector of a first channel in the array of channels, that a high reflectivity surface is present in a surrounding environment (Fig. 3A and 3B showing glare artifact 300; Fig. 4, APD(n) corresponds to a signal that was reflected by retroreflector 40 and represents the actual location of the retroreflector) and a distance between the lidar device and the high-reflectivity surface (Fig. 4, the distance can be determined from the time of flight, which is recorded as ToF1 on the graph along the time axis; [0072] due to crosstalk and the high intensity return from the retroreflector, “This may lead to a false reading by the neighboring pixels that an object is present at the same time-of-flight distance that corresponds to the electrical pulse generated by pixel APD(n)”);
determine, based on: (i) a position of the first light detector (Fig. 4, pixel APD(n); [0071] “a light source of illumination unit 10 fires a laser beam that is reflected by a retro-reflector 40 and is incident on a single pixel APD(n) of the photodetector array 15. This pixel APD(n) may be referred to as a retro-reflector pixel”); (ii) positions of other light detectors within the array of channels ([0071] “Those pixels adjacent to the retro-reflector pixel that experience crosstalk may be referred to as crosstalk pixels or simply neighboring pixels”), and (iii) the distance between the lidar device and the high reflectivity surface, which of the other light detectors within the array of channels are susceptible to crosstalk from the first channel ([0085] “By combining two or more crosstalk indicators and recording the transmission angle, pixel number, and distance, a probability of identifying a crosstalk pixel is increased”);
identify one or more detected pulses that represent crosstalk from the first channel, wherein the one or more detected pulses that represent crosstalk are associated with the light detectors susceptible to crosstalk and are identified based on the distance between the lidar device and the high-reflectivity surface ([0082] “A decrease in amplitude across multiple neighboring pixels with increasing distance from the retro-reflector pixel may be an indicator of vertical crosstalk”; and [0088] “If untargeted pixels produce an output signal (i.e., an electrical pulse), the system controller 23 is configured to record the transmission angle corresponding to the rotation angle of the MEMS mirror 12, the pixel number of the untargeted pixel that generates the signal, and the TOF (i.e., the distance)”; [0072] “the highly reflective object causes leakage in the electrical domain into neighboring pixels APD(n−1), APD(n−2), APD(n+1), and APD(n+2). This effect may also be seen from low reflective objects located at a close range to the photodetector array 15”, identifying that the neighboring pixels APD(n±1) and APD(n±2) are identified as crosstalk pixels); and
prevent the one or more detected pulses that represent crosstalk from the first channel from being included in a dataset usable to generate a point cloud ([0085] “a probability of identifying a crosstalk pixel is increased and steps can be taken by a DSP to mitigate the identified crosstalk event and possibly remove glare artefacts from the point cloud”).
Helsloot further discloses a first set of light detectors [that represent] the light detectors within the array of channels that are within a first distance of the first light detector based on a map of locations of the light detectors within the array of channels ([0072] and Fig. 4, the target pixel is APD(n), and the neighboring pixels are labeled APD(n±3), APD(n±2), and APD(n±1), based on their location relative to the target pixel. In the illustration of Fig. 4, the first set of light detectors within a first distance are APD(n±2), and APD(n±1), which experience vertical crosstalk). Helsloot also implicitly discloses that when the first range of distance values includes shorter distances than the second range of distance values, the first distance [corresponding to the distance from the first light detector within the array of channels] is longer than the second distance ([0072] low reflective objects at a close range to photodetector array may lead to crosstalk also; See Figs. 4 and 5). If a low reflective object is able to cause crosstalk when it is close to the photodetector array, then a highly reflective object would cause more crosstalk and the crosstalk would affect more pixels when the retro-reflective object is closer, compared to a situation when the retroreflective object is farther.
Helsloot does not expressly teach: an array of channels, wherein each channel comprises a light detector and a corresponding light emitter; having a list of which of the other light detectors within the array of channels are susceptible to crosstalk from the first channel.
However, Wang an array of channels (Fig. 3, with array of channels 302a through 302h, which each have a transmitter to emit an optical signal and a detector to receive a signal. Here, channel 302a is the “active” channel, but this is merely an example. It is understood that any one of the channels is capable of being an “active” channel).
It would have been obvious to a person having ordinary skill in the art before the effective filing date to modify the LDIAR device disclosed by Helsloot, such that the transmitters and receivers are arranged into an array of channels where each transmitter has its corresponding receiver, as taught by Wang. This would be a different design option and “Known work in one field of endeavor may prompt variations of it for use in either the same field or a different one based on design incentives or other market forces if the variations are predictable to one of ordinary skill in the art.” See MPEP 2141.III KSR Rationale (F).
However, this combination does not expressly teach the limitation of storing information about pixels relative to each other in a list form.
Dussan teaches a detector array (Fig. 6A, detector array 600 with sensors 602) where the pixels that are expected to receive a signal are stored in a list ([0050] based on the location of the targeted range point in the field of view, a subset of pixels in the detector are selected, where a specific targeted pixel is selected as well as the surrounding pixels that are expected to receive light also; Fig. 6B, step 622), and that the subset of pixels can change depending on information from the scene (Fig. 12, step 1204 and 1206, where the list of eligible pixels can be adjusted based on sensed light or environmental scene).
It would have been obvious to a person having ordinary skill in the art before the effective filing date of the claimed invention to further modify the device taught by Helsloot and Wang, such that the subsets of pixels that are expected to receive crosstalk in the device disclosed by Helsloot, are stored in a list form as taught by Dussan. Using a list to store information about which subset of pixels would be expected to receive a signal based on the actual targeted detector pixel and environmental conditions would be applying a known technique for storing information to a known lidar device to yield predictable results (MPEP 2141.III KSR Rationale D).
Regarding Claim 3: Helsloot, in view of Wang and Dussan, teaches the lidar device of claim 1. Helsloot further discloses wherein the controller is further configured to cause a first light emitter of the first channel to emit a series of light pulses according to a predefined firing sequence ([0075] “the laser may follow a sequential firing pattern such that only a portion of the vertical regions of the field of view is illuminated at a given time. This can be done by only triggering a portion of the light sources at a time, leaving other light sources deactivated. Thus, for each laser beam transmission there exists a group of targeted pixels and non-targeted pixels”), and wherein the one or more detected pulses that represent crosstalk are identified based on the predefined firing sequence ([0087] “reading out and monitoring untargeted pixels, and flagging TOF hits based on common artefact properties derived from the untargeted pixels”).
Regarding Claim 7: Helsloot, in view of Wang and Dussan, teaches the lidar device of claim 1. Helsloot further discloses wherein the controller is further configured to generate the point cloud using detected pulses detected by the light detectors ([0065] “[0065] The system controller 23 includes signal processing circuitry that receives the raw digital data as well as serial data of a differential time between start and ToF hit digital signals generated by an ADC, and uses the received data to calculate time-of-flight information for each field position within the field of view, to generate object data (e.g., point cloud data), and to generate a 3D point cloud”; Figs. 3B and 5, which show the point cloud).
Regarding Claim 8: Helsloot, in view of Wang and Dussan, teaches the lidar device of claim 1. Helsloot further discloses wherein the high-reflectivity surface comprises a surface of a retroreflective object ([0071] “a light source of illumination unit 10 fires a laser beam that is reflected by a retro-reflector 40”; [0068] “FIG. 3B shows an example of a point cloud of a 1D scanning LIDAR system with the retro-reflector glare artefact 300”).
Regarding Claim 11: Claim 11 is essentially the method version of system claim 1, and is therefore rejected for the same reasons.
Regarding Claim 13: Claim 13 is essentially the method version of system claim 3, and is therefore rejected for the same reasons.
Regarding Claim 16: Claim 16 is essentially the method version of system claim 7, and is therefore rejected for the same reasons.
Regarding Claim 17: Claim 17 is essentially the method version of system claim 8, and is therefore rejected for the same reasons.
Regarding Claim 19: Helsloot discloses a system (Fig. 2, LIDAR scanning system 200) comprising:
a computing device configured to generate a point cloud from a dataset usable to generate the point cloud (Fig. 7, point cloud processing circuit 80; [0117] “the crosstalk processing circuit 70 transmits ToF data and possibly crosstalk information to a point cloud processing circuit 80 that is configured to generate point cloud data based thereon and output a point cloud”); and
a lidar device (Fig. 2, transmitter unit 21 and receiver unit 22) comprising:
channels ([0035] “Different groups of pixels can be fired at by activating its corresponding light source”; a light source which has corresponding groups of pixels makes a channel) and
a controller (Fig. 2, system controller 23), wherein the controller is configured to:
cause one or more of the light emitters in the array of channels to emit light pulses ([0057] “the laser sources of the illumination unit 10 are triggered by the system controller 23”),
determine, based on a reflection pulse detected by a first light detector of a first channel in the array of channels, that a high reflectivity surface is present in a surrounding environment (Fig. 3A and 3B showing glare artifact 300; Fig. 4, APD(n) corresponds to a signal that was reflected by retroreflector 40 and represents the actual location of the retroreflector) and a distance between the lidar device and the high-reflectivity surface (Fig. 4, the distance can be determined from the time of flight, which is recorded as ToF1 on the graph along the time axis; [0072] due to crosstalk and the high intensity return from the retroreflector, “This may lead to a false reading by the neighboring pixels that an object is present at the same time-of-flight distance that corresponds to the electrical pulse generated by pixel APD(n)”);
determine, based on: (i) a position of the first light detector (Fig. 4, pixel APD(n); [0071] “a light source of illumination unit 10 fires a laser beam that is reflected by a retro-reflector 40 and is incident on a single pixel APD(n) of the photodetector array 15. This pixel APD(n) may be referred to as a retro-reflector pixel”); (ii) positions of other light detectors within the array of channels ([0071] “Those pixels adjacent to the retro-reflector pixel that experience crosstalk may be referred to as crosstalk pixels or simply neighboring pixels”), and (iii) the distance between the lidar device and the high reflectivity surface, which of the other light detectors within the array of channels are susceptible to crosstalk from the first channel ([0085] “By combining two or more crosstalk indicators and recording the transmission angle, pixel number, and distance, a probability of identifying a crosstalk pixel is increased”);
identify one or more detected pulses that represent crosstalk from the first channel, wherein the one or more detected pulses that represent crosstalk are associated with the light detectors susceptible to crosstalk and are identified based on the distance between the lidar device and the high-reflectivity surface ([0082] “A decrease in amplitude across multiple neighboring pixels with increasing distance from the retro-reflector pixel may be an indicator of vertical crosstalk”; and [0088] “If untargeted pixels produce an output signal (i.e., an electrical pulse), the system controller 23 is configured to record the transmission angle corresponding to the rotation angle of the MEMS mirror 12, the pixel number of the untargeted pixel that generates the signal, and the TOF (i.e., the distance)”; [0072] “the highly reflective object causes leakage in the electrical domain into neighboring pixels APD(n−1), APD(n−2), APD(n+1), and APD(n+2). This effect may also be seen from low reflective objects located at a close range to the photodetector array 15”, identifying that the neighboring pixels APD(n±1) and APD(n±2) are identified as crosstalk pixels); and
prevent the one or more detected pulses that represent crosstalk from the first channel from being included in a dataset usable to generate a point cloud ([0085] “a probability of identifying a crosstalk pixel is increased and steps can be taken by a DSP to mitigate the identified crosstalk event and possibly remove glare artefacts from the point cloud”); and
transmit to the computing device, the dataset usable to generate the point cloud (Fig. 7 and [0116]: “The crosstalk processing circuit 70 receives the detected TOF hits from the targeted scene processing circuit 61 and the artefact box parameters from the non-targeted scene processing circuit 62” and [0117]: “Based on the results of the probability thresholding step, the crosstalk processing circuit 70 transmits ToF data and possibly crosstalk information to a point cloud processing circuit 80”).
Helsloot further discloses a first set of light detectors [that represent] the light detectors within the array of channels that are within a first distance of the first light detector based on a map of locations of the light detectors within the array of channels ([0072] and Fig. 4, the target pixel is APD(n), and the neighboring pixels are labeled APD(n±3), APD(n±2), and APD(n±1), based on their location relative to the target pixel. In the illustration of Fig. 4, the first set of light detectors within a first distance are APD(n±2), and APD(n±1), which experience vertical crosstalk). Helsloot also implicitly discloses that when the first range of distance values includes shorter distances than the second range of distance values, the first distance [corresponding to the distance from the first light detector within the array of channels] is longer than the second distance ([0072] low reflective objects at a close range to photodetector array may lead to crosstalk also; See Figs. 4 and 5). If a low reflective object is able to cause crosstalk when it is close to the photodetector array, then a highly reflective object would cause more crosstalk and the crosstalk would affect more pixels when the retro-reflective object is closer, compared to a situation when the retroreflective object is farther.
Helsloot does not expressly teach: an array of channels, wherein each channel comprises a light detector and a corresponding light emitter; having a list of which of the other light detectors within the array of channels are susceptible to crosstalk from the first channel.
However, Wang an array of channels (Fig. 3, with array of channels 302a through 302h, which each have a transmitter to emit an optical signal and a detector to receive a signal. Here, channel 302a is the “active” channel, but this is merely an example. It is understood that any one of the channels is capable of being an “active” channel).
It would have been obvious to a person having ordinary skill in the art before the effective filing date to modify the LDIAR device disclosed by Helsloot, such that the transmitters and receivers are arranged into an array of channels where each transmitter has its corresponding receiver, as taught by Wang. This would be a different design option and “Known work in one field of endeavor may prompt variations of it for use in either the same field or a different one based on design incentives or other market forces if the variations are predictable to one of ordinary skill in the art.” See MPEP 2141.III KSR Rationale (F).
However, this combination does not expressly teach the limitation of storing information about pixels relative to each other in a list form.
Dussan teaches a detector array (Fig. 6A, detector array 600 with sensors 602) where the pixels that are expected to receive a signal are stored in a list ([0050] based on the location of the targeted range point in the field of view, a subset of pixels in the detector are selected, where a specific targeted pixel is selected as well as the surrounding pixels that are expected to receive light also; Fig. 6B, step 622), and that the subset of pixels can change depending on information from the scene (Fig. 12, step 1204 and 1206, where the list of eligible pixels can be adjusted based on sensed light or environmental scene).
It would have been obvious to a person having ordinary skill in the art before the effective filing date of the claimed invention to further modify the device taught by Helsloot and Wang, such that the subsets of pixels that are expected to receive crosstalk in the device disclosed by Helsloot, are stored in a list form as taught by Dussan. Using a list to store information about which subset of pixels would be expected to receive a signal based on the actual targeted detector pixel and environmental conditions would be applying a known technique for storing information to a known lidar device to yield predictable results (MPEP 2141.III KSR Rationale D).
Regarding Claim 20: Helsloot, in view of Wang and Dussan, teaches the system of claim 19. Helsloot further teaches wherein transmitting, to the computing device, the dataset usable to generate the point cloud, comprises transmitting a datastream to the computing device, and wherein preventing the one or more detected pulses that represent crosstalk from the first channel from being included in the dataset usable to generate the point cloud comprises removing the one or more detected pulses from the datastream ([0098] “The system controller 23 may compare each probability score to a predefined probability threshold, and discard any TOF hits with a probability score less than the predefined probability threshold. For example, a predefined probability threshold of 50% would result in any TOF hit having a probability score less than 50% be discarded and not reported (output) to the system controller 23.” The probability threshold discussed in this paragraph represents the likelihood that the detected TOF hit is valid, depending on distance, amplitude, and how many hits the pixel has, for example, as described in [0097]).
Claims 2 and 12 are rejected under 35 U.S.C. 103 as being unpatentable over Helsloot (US 20210033711 A1), in view of Wang (US 20230194684 A1), further in view of Dussan (US 20170242109 A1), and further in view of Ulrich (US 20200096637 A1).
Regarding Claim 2: Helsloot, in view of Wang and Dussan, teaches the lidar device of claim 1. In this combination, Helsloot further discloses that there is a plurality of combinations of: (i) distances between the lidar device and the high-reflectivity surface and (ii) light detectors detecting reflection pulses that correspond to a high-reflectivity surface ([0071] based on distance to the retro-reflector, there may be two or more retro-reflector pixels/target pixels APD(n) which correspond to an actual location of the retro-reflector. This means that for far distances, more pixels in the array will receive detections that correspond to the same object due to the effect of divergence; Fig. 4, the target pixel is APD(n), and the neighboring pixels are labeled APD(n±3), APD(n±2), and APD(n±1), based on their location relative to the target pixel. In the illustration of Fig. 4, the first set of light detectors within a first distance are APD(n±2), and APD(n±1), which experience vertical crosstalk).
In this combination, Dussan teaches that the light detectors expected to receive reflected light are stored in a list ([0050] based on the location of the targeted range point in the field of view, a subset of pixels in the detector are selected, where a specific targeted pixel is selected as well as the surrounding pixels that are expected to receive light also).
However, Helsloot, in view of Wang and Dussan, do not teach wherein determining which of the other light detectors within the array of channels are susceptible to crosstalk comprises accessing a lookup table.
However, Ulrich teaches the use of a lookup table to store information about an incident light beam on an array of pixels in paragraph [0073]: “The function
Φ
r
→
describes a phase delay of the incident light spot, which may be caused, for example, by phase crosstalk/signal crosstalk between the pixels. Since this is not necessarily isotropic, it may be necessary to model
Φ
r
→
as a two-dimensional function (e.g., a 2D spline or a 2D lookup table).”
It would have been obvious to a person having ordinary skill in the art before the effective filing date to modify the lidar system taught by Helsloot, Wang, and Dussan, such that the list of which pixels are expected to detect a signal are stored in a lookup table, as taught by Ulrich. Storing subsets of pixels in a lookup table is simply another way for storing and organizing information. This modification would be motivated by the fact that Dussan teaches that the list of pixels to be included in a specific subset “can be any data structure 1202 that includes data of which pixels 602 are eligible to be selected for inclusion in the subset 1130” (Dussan, [0077]), and a lookup table is just another data structure. This suggestion made by Dussan would have led one of ordinary skill to incorporate the use of a lookup table for storing information to arrive at the claimed invention. See MPEP 2141.III G.
Regarding Claim 12: Claim 12 is essentially the method version of system claim 2 and is therefore rejected for the same reasons.
Claims 4, 5, 14, and 15 are rejected under 35 U.S.C. 103 as being unpatentable over Helsloot (US 20210033711 A1), in view of Wang (US 20230194684 A1), further in view of Dussan (US 20170242109 A1), and further in view of Zhu (US 20230358866 A1).
Regarding Claim 4: Helsloot, in view of Wang and Dusan, teaches the lidar device of claim 3. Helsloot further discloses wherein the controller is configured to buffer, within the memory, a series of detected pulses for each light detector susceptible to crosstalk (Fig. 7, DSP line processing 50 and [0112] “The DSP line processing circuit 50 also includes a multiplexer configured to receive targeted pixel information and selectively output detected pulse information to either the targeted scene processing circuit 61 or to the non-targeted scene processing circuit 62 based on the received targeted pixel information”), and the memory has sufficient storage so as to store a number of detected pulses in the series of detected pulses for each light detector susceptible to crosstalk ([0023] “multiple TOF hit times are stored and the counter counts until the end of predefined measurement period, which is defined by a maximum distance to be observed”; Fig. 6, it is seen that for APD(n-2), not only is TOF1 stored, but TOF2 is also stored. According to paragraph [0093], TOF2 corresponds to an object at a further distance and TOF1 is indicative of crosstalk because the detectors show signs of vertical crosstalk and APD(n-2) has a secondary signal).
However, they do not expressly teach: wherein the series of light pulses emitted according to the predefined firing sequence comprises a first predefined number of emission pulses, and when the number of detected pulses is equal to the first predefined number.
Zhu teaches a lidar system where the series of light pulses emitted according to the predefined firing sequence comprises a first predefined number of emission pulses (Fig. 2, where multi-pulse sequences 201, 203, 205, 207, and 209 all have predefined numbers of pulses); wherein the controller comprises a memory, wherein the controller is further configured to buffer within the memory, a series of detected pulses ([0062] “The temporal profile of the measurement signals may be stored in a memory unit and used for identifying legitimate sequence of light pulses”); and wherein the memory has sufficient storage so as to store a number of detected pulses in the series of detected pulses for each light detector when the number of detected pulses is equal to the first predefined number ([0062] “The return signals corresponding to the multi-pulse sequence are shown as signals 303. In some cases, one or more factors (e.g., amplitude, number of pulses) of the temporal profile may be stored and used for determining a legitimate sequence of light pulses. For example, amplitudes, number of pulses in a sequence and the like may be used to determine a match”).
It would have been obvious to a person having ordinary skill in the art before the effective filing date of the claimed invention to further modify the system taught by Helsloot, Wang, and Dussan, such that there is a predefined number of pulses in the firing sequence and to further configure the memory such that it has sufficient storage to store that same predefined number of pulses, as taught by Zhu. This modification would be beneficial because encoding measurement signals with distinguishable temporal profiles, such as a certain number of pulses, avoids crosstalk. This enables the system to take concurrent measurements while avoiding crosstalk because different channels are encoded with different coding schemes (Zhu, [0030]).
Regarding Claim 5: Helsloot, in view of Wang, Dussan, and Zhu, teaches the lidar device of claim 4. Helsloot further discloses wherein preventing the one or more detected pulses that represent crosstalk from the first channel from being included in the dataset usable to generate a point cloud comprises removing, from the memory, those detected pulses buffered within the memory that represent crosstalk ([0098] “The system controller 23 may compare each probability score to a predefined probability threshold, and discard any TOF hits with a probability score less than the predefined probability threshold. For example, a predefined probability threshold of 50% would result in any TOF hit having a probability score less than 50% be discarded and not reported (output) to the system controller 23.” Fig. 7 shows that the targeted pixel information is buffered in the DSP Line processing 50, and according to paragraph [0098], if the measurement is determined to be crosstalk, it will not be outputted).
Regarding Claim 14: Claim 14 is essentially the method version of system claim 4 and is therefore rejected for the same reasons.
Regarding Claim 15: Claim 15 is essentially the method version of system claim 5 and is therefore rejected for the same reasons.
Claim 6 is rejected under 35 U.S.C. 103 as being unpatentable over Helsloot (US 20210033711 A1), in view of Wang (US 20230194684 A1), further in view of Dussan (US 20170242109 A1), further in view of Zhu (US 20230358866 A1), and further in view of Uehara (US 20190391270 A1). Helsloot, as modified in view of Wang, Dussan, and Zhu, teaches the lidar device of claim 4. Helsloot further discloses wherein the controller comprises a FPGA ([0056] The controller may be a FPGA that generates the control signals) communicatively coupled to the memory ([0119] “The implementation can be performed using a digital storage medium, for example a floppy disk, a DVD, a Blue-Ray, a CD, a ROM, a PROM, an EPROM, an EEPROM or a FLASH memory, having electronically readable control signals stored thereon, which cooperate (or are capable of cooperating) with a programmable computer system such that the respective method is performed”; Fig. 7, the controller 23 communicates the processing systems 50, 61, and 62 which store and process information on the detections).
Helsloot, Wang, Dussan, and Zhu, all fail to expressly teach: the memory comprises a RAM.
However, Uehara teaches the use of a memory, which is a RAM, to store information, and which is communicatively coupled to the controller which instructs the lidar device to perform various functions ([0033] “the reflectivity system 170 includes a memory 210 that stores a scanning module 220 and an output module 230. The memory 210 is a random-access memory (RAM)”).
It would have been obvious to a person having ordinary skill in the art before the effective filing date of the claimed invention to further modify the lidar device taught by Helsloot, Wang, Dussan, and Zhu, by using RAM as the memory as taught by Uehara, instead of the memory employed by Helsloot, which could be a ROM, for example. This would be a simple substitution for one type of memory for another type of memory and would yield predictable results (See MPEP 2141.III KSR Rationale B).
Claims 9 and 18 are rejected under 35 U.S.C. 103 as being unpatentable over Helsloot (US 20210033711 A1), in view of Wang (US 20230194684 A1), further in view of Dussan (US 20170242109 A1), further in view of Zhu2 (US 10983197 B1).
Regarding Claim 9: Helsloot, in view of Wang and Dussan, teaches the lidar device of claim 1. Helsloot further discloses wherein which of the light detectors within the array of channels are susceptible to crosstalk from the first channel is further based on an emission vector associated with a first emitter of the channel ([0085] “By combining two or more crosstalk indicators and recording the transmission angle, pixel number, and distance, a probability of identifying a crosstalk pixel is increased”; [0107] “the system controller 23 also tracks which pixel column is targeted and which pixel column(s) is not targeted based on the transmission angle of the MEMS mirror 12”).
Helsloot does not expressly teach that it is a pitch angle and a yaw angle that is used.
However, Zhu2 teaches this limitation in Col. 12 line 54 through Col. 13 line 4: “each VCSEL may have an angle (e.g., pitch angle, yaw angle, etc) with respect to the horizontal or vertical direction” and “The dimension and configuration of the emitter array 207 and the emitting optical system 203, 205, and receiving optical system 213 are designed such that the emitter and return paths can be predicted, which means that the yaw and pitch of the lasers and their respective angles are taken into account into the prediction of the return path.”
It would have been obvious to a person having ordinary skill in the art before the effective filing date of the claimed invention to further modify the system taught by Helsloot, Wang, and Dussan, such that the yaw and pitch angles of the emitted light are both taken into account in predicting the return path of the light as taught by Zhu2. The pitch and yaw angles are two angles that can be used to describe the “transmission angle” disclosed by Helsloot. Because lidar systems are used in the real world where there are only three dimensions, there are only three angles (pitch, yaw, and roll) that can be used to describe a vector, and choosing to use the pitch and yaw angles to define a “transmission angle” would be “obvious to try” with the reasonable expectation of success (See MPEP 2141.III KSR Rationale E).
Regarding Claim 18: Claim 18 is essentially the method version of system claim 9 and is therefore rejected for the same reasons.
Claim 10 is rejected under 35 U.S.C. 103 as being unpatentable over Helsloot (US 20210033711 A1), in view of Wang (US 20230194684 A1), further in view of Dussan (US 20170242109 A1), further in view of Uehara (US 20190391270 A1). Helsloot, in view of Wang and Dussan, teaches the lidar device of claim 1. However, they do not expressly teach wherein that the high-reflectivity surface is present in the surrounding environment comprises comparing an intensity of the reflection pulse detected by the first light detector to a threshold intensity.
Uehara teaches this limitation in paragraph [0035]: “The scanning module 220 can analyze the first point cloud 250 to detect the presence of obscuring objects that have a relatively high reflectivity (e.g., above a threshold for saturating a detector).”
It would have been obvious to a person having ordinary skill in the art before the effective filing date of the claimed invention to further modify the lidar device taught by Helsloot, Wang, and Uehara, such that a threshold intensity is used to identify crosstalk, as taught by Uehara. This would be beneficial because objects that have a high reflectivity can obscure and blind the LIDAR device from perceiving other objects, especially when the detector is oversaturated (Uehara, [0035]).
Conclusion
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to ISABELLE LIN BOEGHOLM whose telephone number is (571)270-0570. The examiner can normally be reached Monday-Thursday 7:30am-5pm, Fridays 8am-12pm.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Yuqing Xiao can be reached at (571) 270-3603. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/ISABELLE LIN BOEGHOLM/Examiner, Art Unit 3645
/YUQING XIAO/Supervisory Patent Examiner, Art Unit 3645