Patent Grant
11611691
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.
The present invention relates to photographing and particularly to lightning of a scene when the time of taking a picture of the scene.
When it is desired to provide additional light to a scene to be photographed, a flash device may be used to provide the additional light to the scene. The camera used for taking the photography may be arranged to provide a sync signal to the flash device when the photographer takes a picture to activate the flash device.
An object of the invention is to improve control in lightning a scene at the time of taking a picture of the scene.
This object has been achieved by means of a computer-implemented method for coordinating taking of a picture using a camera and initiation of a flash pulse of at least one flash device.
In accordance with this method, taking of pictures with a camera is coordinated with obtaining of a flash pulse with one or a plurality of flash devices. The coordination may be made such that the camera takes the picture at the same point in time or near the same point in time as the respective flash pulse is emitted. Alternatively, the coordination may be made such that there is a predetermined relation between taking the picture and the obtaining of the flash pulse of the respective flash device.
The method comprises the steps of obtaining a time base for a processor element of the first device; estimating a time base for a processor element of each at least one remote device in relation to the time base of the processor element of the first device; scheduling a timing for initiation of the flash pulse of the respective at least one flash device and/or a timing for initiation of taking a picture using the camera in the time base of the first device so that the coordination with the timing for taking the picture is obtained; and obtaining at the respective remote device of the system the scheduled timing of initiation of the remote device in the time base of that device.
Thereby, the timing of initiation of flash pulses from each of one or a plurality of flash devices and the taking of pictures using the camera may be coordinated. The coordination of the timing of initiation of flash pulses from each of one or a plurality of flash devices and the taking of pictures using the camera may involve determining timings for taking the picture and timings for initiating a flash pulse from the respective flash device.
With the coordination as defined above the timing of the flash pulses in relation to the taking of the images may be coordinated so that the flash pulses take place at a desired timing in relation to the taking of the picture. Further, when a plurality of flash devices are used, they may be coordinated to flash at a desired timing in relation to each other and in relation to the taking of a picture.
Characteristically the time base of the first device and the at least one flash device are different. Thus, a clock of a processor element of the first device has characteristically a different timing than a clock of the respective remote device. This instantaneous difference between the readings of the clock of the first device and the respective remote device is called their skew or clock skew. Thus, there is characteristically a skew between the time base of the first device and the at least one flash device. Thus, the skew may be taken into account when coordinating timing of initiation of flash pulses from each of one or a plurality of flash devices and the taking of pictures using the camera.
Further, the time bases may drift in relation to each other with time. Therefore, the estimation of the time base for a processor element of each at least one remote device in relation to the time base of the processor element of the first device may be performed continuously or repeatedly.
The present disclosure further relates to a control system 200 for coordinating taking of a picture using a camera and initiation of a flash pulse of at least one flash device. The control system is arranged to control operation of a first device having a processor element operating in a first time base and at least one remote device having a processor element operating in a respective second time base. The control system comprises a time base estimating element arranged to estimate a relation between the first and the respective second time bases. The control system comprises further a scheduler element arranged to schedule in the time base of the first device a timing for initiation of the flash pulse of the respective at least one flash device and/or a timing for initiation of taking a picture using the camera so that the coordination with the timing for taking the picture is obtained. The control system comprises further a communication interface arranged to transmit to the respective remote device the scheduled timing of that remote device.
The present disclosure further relates to a camera device arranged to coordinate taking of a picture using said camera device and initiation of a flash pulse of at least one remote flash device. The camera device has a processor element operating in a first time base, wherein the at least one remote flash device has a processor element operating in a respective second time base. The camera device comprises at least a part of a time base estimating element arranged to estimate a relation between the first and the respective second time bases, a scheduler element arranged to schedule in the first time base a timing for initiation of the flash pulse of the respective at least one remote flash device so that coordination with the timing for taking the picture is obtained, and a communication interface arranged to transmit to the respective remote flash device the scheduled timing of that remote flash device.
The camera device may be a camera phone or tablet which may be arranged to communicate with the at least one remote flash device via a Bluetooth interface.
The present disclosure further relates to a flash device arranged to coordinate initiation of a flash pulse of the flash device with taking of a picture using a remote camera device, said flash device having a processor element operating in a first time base, wherein the remote camera device having a processor element operating in a second time base. The flash device comprises at least a part of a time base estimating element arranged to estimate a relation between the first and the respective second time bases, a scheduler element arranged to schedule in the time base of the flash device a timing for taking a picture using the camera device so that the coordination with the initiation of the flash pulse is obtained, and a communication interface arranged to transmit to the camera device the scheduled timing of that remote camera device.
The present disclosure further relates to a computer program product for performing the method for coordinating taking of a picture using a camera and initiation of a flash pulse of at least one flash device as disclosed herein.
In
In
In
Each device of the system 100a, 100b has a control element (not shown) for controlling that device. The control element is associated to an internal clock 104a, 104b, 104c, 104d, 104e of that device. The internal clock 104a, 104b, 104c, 104d, 104e forms a time for that device. Control by means of the control element of the respective device is performed in the time base of that device.
The control system 200 comprises a scheduler element 210 and a time base estimating element 211. The control system 200 further comprises communication interface(s) 212 for communication between different devices of the system.
The control system 200 may further comprise a user interface 213 for user requests. The user interface comprises a function for user request to take a picture. The user interface may therefore for example comprise a pushbutton of a camera. When the camera is implemented in a wireless device such as a camera phone or tablet, the “pushbutton” is then implemented in the user interface of the wireless device.
The scheduler element 210 is arranged to, upon request, scheduling a timing for initiation of the flash pulse of the respective at least one flash device and/or a timing for taking a picture using the camera in the time base of the first device so that the coordination with the timing for taking the picture is obtained and obtaining the scheduled timings of initiation of the respective device in the time base of that device.
The request is characteristically obtained via the “camera pushbutton” of the user interface 213.
The scheduled timing(s) are fed from the scheduler element 210 to the devices of the system 100a, 100b. The scheduled timing(s) for those devices, which are remote devices, are fed to the communication interface 212 for transmission of the scheduled timings to the respective remote device. Any scheduled timing associated to a flashlight or picture taking device in which the scheduler element is implemented is also communicated to that flashlight or picture taking function.
The scheduled timing(s) fed to the communication interface 212 is/are transmitted to the remote device to which the particular timing is associated.
The time base estimating element 211 is arranged to obtaining a time base for a processor element of the own device 101 and estimating a time base for each at least one remote device 102 relative to the obtained time base of the own device 101. Generally, the estimation of time base comprises transmitting at least one request for time information relating to said at least one remote device, obtaining a timing of the transmission of the request for time information based on the obtained time reference, receiving a response from each said at least one remote device comprising the requested time information in a time base of that remote device, and determining the estimate of the time base for each at least one remote device based on the obtained timing of the transmission of the request for time information and the time information comprised in the response from respective remote device. Examples of how the time bases may be estimated will be discussed more in detail below.
The first device 101 may be a camera phone or tablet. The first device may be a flash device.
The at least one remote device 102 may comprise at least one remote flash device. The at least one remote device may comprise the camera phone or tablet.
The control system 200 comprises a time base estimating element 211 arranged to estimate a relation between the first and the respective second time bases. The control system comprises further a scheduler element 210 arranged to schedule in the time base of the first device a timing for initiation of the flash pulse of the respective at least one flash device and/or a timing for initiation of taking a picture using the camera so that the coordination with the timing for taking the picture is obtained. Communication between the first device and the at least one remote device is performed over a communication interface (not shown). The communication interface may be a wireless interface such as a Bluetooth interface.
In the example of
In response to receipt of the transmission request TR, the remote device is arranged to provide the requested time information in the time base of that remote device. The time base estimating element is at the remote device further arranged to form a response (R) comprising the requested time information and to transmit the formed response to the first device. The response comprises characteristically also the identity uniquely identifying the request. Thereby, pairing of the request with its corresponding response is facilitated.
A time base determining pat 214 of the time base estimating element is arranged to determine the estimate of the second time base of the processing element of each at least one remote device in relation to the time base of the processor element of the first device based on the obtained timing of the transmission of the request for time information and the time information comprised in the response (R) from the respective remote device.
The scheduler element 210 is arranged to feed to the communication interface for further communication to the respective remote device the scheduled timing for the respective remote device in the second time base.
In the example of
In response to receipt of the transmission request TR, the remote device is arranged to obtain the requested time information in the time base of that remote device.
The time base determining part 214 of the time base estimating element is in this example arranged at the respective remote device 102. The time base determining part is arranged to determine the estimate of the time base of the processing element of its remote device in relation to the time base of the processor element of the first device based on the obtained timing of the transmission of the request for time information and the obtained requested time information.
The scheduler element 210 is arranged to feed to the communication interface for further communication to the respective remote device the scheduled timing for the respective remote device in the first time base. The respective remote device may then convert the scheduled timing to a timing in the time base of that remote device.
In
The method is adapted for a system including a first device and at least one remote device. The method comprises the steps of obtaining S1 a time base for a processor element of the first device.
The method further comprises a step of estimating S2 a time base for a processor element of each at least one remote device in relation to the time base of the processor element of the first device.
The communication between the first device and at least one remote device may be performed over a wireless channel with predetermined communication timings, so called connect events. The estimation S2 of a time base for each at least one remote device is performed also based on the predetermined communication timings. Further, the time bases may drift in relation to each other with time. Therefore, the estimation S2 of the time base for a processor element of each at least one remote device in relation to the time base of the processor element of the first device may be performed continuously or repeatedly. The method further comprises a step of scheduling S3 a timing for initiation of the flash pulse of the respective at least one flash device and/or a timing for taking a picture using the camera in the time base of the first device so that the coordination with the timing for taking the picture is obtained. The scheduling may be performed at least in part in the first device. The scheduling may be performed at least in part in a control device in communication with the first device. The scheduling characteristically takes place when the user indicates that he/she wishes to take a picture via a user interface at the first device or control device associated thereto. The indication may in another example be obtained by means of an indication via a user interface of one of the remote device(s). The scheduling may take account to any delays within the respective devices to initiate taking of the picture and/or initiating the flash light. The scheduling may also or instead take into account timings of connect events for communication between the first device and the respective remote device. The timings for connect events may be provided in the step of estimating S2 the time base for the respective remote device; this is further illustrated in relation to
A timing relating to scheduling of the first device may be obtained. The timing relating to scheduling of the first device is then fed to control hardware/software for control of the first device.
The method further comprises a step of obtaining S4 at the respective remote device of the system the scheduled timing of initiation of the remote device in the time base of that device. The scheduled timing is communicated from the first device to the respective remote device.
In
The obtained response (R1, R2, R3) for each said remote device may be transmitted to the first device. The determination S24 of the estimate of the time base for each at least one remote device is then performed at the first device. Scheduled timings are then transmitted to the respective remote device in the time base of that remote device.
The at least one request (TR1, TR2, TR3) may comprise the obtained timing (TTR1, TTR2, TTR3) of the transmission of the request. The determination (S24) of the estimate of the time base of the remote device in relation to the time base of the first device may then be performed at the remote device based on the obtained timing (TTR1, TTR2, TTR3) of the transmission of the request and the obtained response (R1, R2, R3). The scheduled timings may then be transmitted to the respective remote device in the time base of the first device.
The communication between the first device and at least one remote device may be performed over a wireless channel with predetermined communication timings, so called connect events. Communication may be performed according to a Bluetooth protocol.
The predetermined communication timings may be unknown. The estimation of a time base for each at least one remote device may then be performed also based on the predetermined communication timings.
However, the predetermined communication timings may be unknown. A plurality of requests (TR1, TR2, TR3) for timing information may then be transmitted S21. The determination S24 of the estimate of the time base for each at least one remote device may then comprise determining a timing relation between the timing (TTR1, TTR2, TTR3) of the transmission of each request and the communication timings based on the information in the respective obtained response.
The timing of the transmittal of a next request for timing information may be selected based on the determined timing relation between the timing (TTR1, TTR2, TTR3) of the transmission of the preceding request(s) and the communication timings so as to narrow a time window within which the communication event occurs. It may be that time information relating to directly preceding request(s) are not available. Then, earlier requests may be used in the selection.
The determining S24 of the estimate of the time base may comprise determining a time interval within which the time base lies based on a time window within which it has been determined that the communication event occurs. The requests for timing information may be repeatedly transmitted until the time interval within which the time base lies is within predetermined boundaries.
In
In the illustrated example a time interval TI between connect events, i.e. timings when the first device communicates with the remote device is known. The example is illustrated in relation to an example wherein the connect time interval TI is 100; this connect time interval is only set for illustrative purposes. The connect time interval TI may for example be given in microseconds.
In the illustrated example, the first device transmits a request for time information at a timing TTR1=50. In the illustrated example, this request for time information is denoted TR1. The request for time information is communicated to the remote device during a next connect event CE1. The timing TCE1 of the next connect event CE1 is not known. However, as the time interval is known, it is known that the next connect event C1 will occur within the connect timing interval TI, i.e. within 100 microseconds.
In response to receipt of the request for time information, the remote device forms a response R1 to the request for time information. The response R1 comprises time information indicating the time of an internal clock of the remote device. In the illustrated example, the response comprises the time 1200. The time is for example given in microseconds.
Then, a difference between the time of the first device and the remote device may be estimated. The estimated time difference may be given as a time interval.
An upper limit for the time difference interval may be determined based on a time difference between the timing T1 of the transmission of the request and the timing information in the response. Thus, in the illustrate example, an upper limit for the time difference interval is 1200-50=1150 [μs].
Further, as the upper limit has been determined and the connect time interval TI between connect events in this example is known, this may be used for determined a lower limit for the time difference interval, i.e. the lower time limit is 1150−100=1050 [μs]. Thus, the estimation of the difference between the time of the first device and the remote device may be given as a time interval Δ1ϵ[1050, 1150], i.e. Δ1=1100±50. However, note that an upper limit can always be estimated, even though the time interval is not known.
The information provided above relating to transmission of the transmission request TR, the formation of the associated response R1 and the time interval T1 may also be used to provide an estimate relating to the timing of the connect events in the time base of the first device. Thus, the timing of the connect event C1 in the time base of the first device may be estimated as
TCE1_First device≈″1200−Δ≈1200−(1100±50)≈100±50.
Accordingly, the next connect event CE2 in the time based of the first device may be estimated to take place at TCE2_First device≈200±50.
The so estimated time difference interval Δ1 may not be satisfactory small. Therefore, the above-described process is repeated one or a plurality of times until the time difference interval is within acceptable boundaries.
Accordingly, in accordance with the illustrated example, the first device transmits a second request for time information. In the illustrated example, the second request for time information is transmitted at a timing TTR2=180. In the illustrated example, this request for time information is denoted TR2. The time for transmitting the second request for time information may obtained arbitrary or selected. If selected, the time may be selected based on the connect time interval. In the illustrated example, the timing of the transmitting of the second request for time information is selected to be incremented in relation to the first request TR1 for time information with a time larger than the connect time interval TI. Thus, the second request for time information is selected to try to get a bit closer to the timing of the connect event than the first request for time information. It may be that time information relating to directly preceding request(s) are not available. Then, earlier requests may be used in the selection.
The request for time information is communicated to the remote device during a next connect event CE2.
In response to receipt of the second request for time information, the remote device forms a response R2 to the second request TR2 for time information. The response R2 comprises as described above time information indicating the time of an internal clock of the remote device. In the illustrated example, the response comprises the time 1300 [μs].
Then, the estimation of the time difference between the time of the first device and the remote device may be updated.
As the time information included in the second response R2 differs with an amount corresponding to the connect time interval TI between connect events, in this case 100 [μs], it can be concluded that the response was received in a connect event directly following the first connect event.
The upper limit for the time difference interval may be updated based on a time difference between the timing TTR2 of the transmission of the request TR2 and the timing information of the formed response R2.
Thus, in the illustrate example, an upper limit for the time difference is 1300−180=1120 [μs].
At this stage, no information has been obtained for updating the lower time limit.
Thus, the time difference between the time of the first device and the remote device has now been updated.
Thus, the estimation of the difference between the time of the first device and the remote device has been updated. The time difference may be given as a time difference interval Δ2ϵ[1050, 1120], i.e. Δ2=1085±35.
Further, the timing TCE2 of the connect event C2 in the time base of the first device may be estimated as
TCE2_First device≈1300−Δ2≈215±35.
Accordingly, the next connect event CE3 in the time based of the first device may be estimated to take place at TCE3_First device≈315±35.
The so determined time difference interval may not be satisfactory small. Therefore, the above-described process may be repeated again to obtain satisfactory accuracy.
Accordingly, in accordance with the illustrated example, the first device transmits a third request TR3 for time information. In the illustrated example, the third request TR3 for time information is transmitted at a timing TTR3=310. In the illustrated example, the timing TTR3 of the transmission of the third request TR3 for time information is obtained arbitrary or selected. If selected, the timing TTR3 of the transmission of the third request TR3 may be incremented in relation to the second request for time information TR2 with a time larger that the connect time interval TI. Thus, the third request for time information is then selected to try to get a bit closer to the timing of the connect event than the second request for time information. It may be that time information relating to directly preceding request(s) are not available. Then, earlier requests may be used in the selection.
The request TR3 for time information is communicated to the remote device during a connect event CE4.
In response to receipt of the third request for time information TR3, the remote device forms a response to the third request for time information TR3. The response comprises as described above time information indicating the time of an internal clock of the remote device. In the illustrated example, the response comprises the time 1500 [μs].
Then, the estimation of the time difference between the time of the first device and the remote device may be updated.
As the time information included in the third response differs with an amount corresponding to two connect time intervals TIs between connect events, in this case 200 [μs], it can be concluded that the response was not formed in a connect event CE3 directly following the second connect event but in a thereafter following connect event CE4. This means that the third request TR3 was transmitted at a timing after the third connect event CE3 or at least so close to the timing of the connect event CE3 that the third request TR3 could not be included in the third connect event CE3.
The lower value for the time difference interval may be updated based on a time difference between the timing T3 of the transmission of the request and the timing information of the of received response R3. The lower limit for the time difference may be updated by determining that the request was transmitted after the timing 1500−310=1190 [μs] in the time base of the remote device and that the lower limit for the time difference then may be updated as the difference between the timing of the third connect event CE in the time base of the remote device and the timing of the transmission of the third request TR3 in the time base of the first device.
In practice, the lower limit for the time limit may be calculated as follows. The time difference between the timing TTR3 of the transmission of the request TR3 and the timing information of the formed response R3 is determined as 1500−310=1190. This time difference larger than the previously estimated upper limit, and thus it may be determined that the third request TR3 was transmitted at a timing after the third connect event CE3 or at least so close to the timing of the connect event CE3 that the third request TR3 could not be included in the third connect event CE3
Thus, in the illustrate example, a lower limit for the time difference is 1500−100−310=1090 [μs].
Thus, the estimation of the difference between the time of the first device and the remote device has been updated. The time difference may be given as a time difference interval Δ3ϵ[1090, 1120], i.e. Δ3=1105±15.
At this stage, no information has been obtained for updating the upper time limit.
Thus, the time difference between the time of the first device and the remote device has now been updated. In this example, the time difference interval has been updated to be Δ3ϵ[1090, 1120].
Further, the timing TCE4 of the connect event C4 in the time base of the first device may be estimated as
TCE4_First device≈395±15.
Accordingly, a next connect event CE5 in the time based of the first device may be estimated to take place at TCE5_First device≈495±15.
The so determined time difference interval may not be satisfactory small. Therefore, the above-described process may be repeated again using timings of transmissions of the requests TRn in order to further narrow the time interval 4.
In
In line with the example of
In line with the example of
In accordance with this example, a plurality of transmission requests TR1, TR2, TR3 are transmitted at different, predetermined timings in relation to each connect event. Thereby, the time needed for obtaining a time difference between the first device and the respective remote device may be shortened in relation to the example of
The first and second transmission requests TR1, TR2 for time information are communicated to the remote device during a next connect event CE1. However, the third transmission request is not communication at that connect event. The third transmission request is awaiting the thereafter following connect event CE2.
In response to receipt of the first and second transmission requests TR1, TR2 for time information, the remote device forms a response R1, R2 to the respective first and second requests TR1, TR2 for time information. The responses R1, R2 to the respective first and second transmission requests TR1, TR2 comprises time information indicating the time of an internal clock of the remote device. Thus, the response comprises in an example two time indications indicating the same timing. In the illustrated example, the responses comprise the time 1200. The time is for example given in microseconds. The response does not comprise a third time indication as the third transmission request TR3 has not yet been communicated.
Thus, after the first connect event CE1 of this example, the same information is obtained as after a plurality of connect events in
Then, a difference between the time of the first device and the remote device may be estimated. The estimated time difference may be given as a time interval.
The time difference between the time of the first device and the remote device may then be determined to be Δϵ[1090, 1120] based on the connect time interval information TI, the timings of the transmission requests (TTR1=50, TTR2=180, TTR3=310) and the information that the first and second responses were received at 1200 in the time base of the remote device in an equivalent manner as described in relation to
The example illustrated in relation to
In the herein illustrated examples, some algorithm for selection of timings for transmissions of the transmission requests TR may be used for narrowing the time interval Δ. The selection may be based on previous responses to transmission requests. It may be that responses relating to directly preceding request(s) are not available. Then, earlier requests may be used in the selection.
Further, in the herein illustrated examples, communication of the request, formation of the response and communication of the response, when applicable take place within the same connect events. However, this is only an example. For example, the communication of the request and the formation of the response may be arranged to take place in one connect event and the communication of the response, when applicable, takes place in a following connect event. In another example, the communication of the request takes place in one connect event and the communication of the response, when applicable, takes place in a following connect event. The teaching as described herein is applicable to all situations, as long as the scheme for communication and formation of responses is known. Should there be occurrences data falls outside the determined scheme for communication and formation of responses, those data should be ignored.
Further, in the herein illustrated examples, it is assumed that the communication of the transmission request of the first device, the reception of the transmission request at the remote device, the processing of the transmission request at the remote device, the transmission of the response from the remote device and the receipt of the response at the first device is performed momentarily. In order to further improve the estimation of the time difference between the first device and the remote device, any delays in this scheme may be taken into account when estimating the time difference between the first device and the remote device.
Further, the transmission requests may comprise an identity uniquely identifying the request. Transmitted responses then characteristically also comprise the identity uniquely identifying the one or plurality of requests to which the response is associated. Thereby, pairing of the request with its corresponding response is facilitated. When the requests are uniquely identified, this allows for example for discarding retransmissions when estimating the time difference between the first device and the remote device. Precision in the estimation may thereby be improved.
Further, in practice, the clocks of the first device and the remote device will characteristically drift in relation to each other. Therefore, estimation of the time difference between the first device and the remote devices may be performed repeatedly. Thus, the estimation time difference between the first device and the respective remote device may take place continuously or at predetermined time intervals.
| Number | Date | Country | Kind |
|---|---|---|---|
| 1851073-5 | Sep 2018 | SE | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/SE2019/050829 | 9/4/2019 | WO |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2020/055305 | 3/19/2020 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 4373793 | Taniguchi et al. | Feb 1983 | A |
| 5452048 | Edgar | Sep 1995 | A |
| 6178296 | Kojima | Jan 2001 | B1 |
| 6404987 | Fukui | Jun 2002 | B1 |
| 7420613 | Lee | Sep 2008 | B2 |
| 7583297 | Yamada | Sep 2009 | B2 |
| 7697062 | Wernersson | Apr 2010 | B2 |
| 7756354 | Washisu | Jul 2010 | B2 |
| 7783188 | Clark | Aug 2010 | B2 |
| 7986853 | Washisu | Jul 2011 | B2 |
| 8854536 | Ogasawara | Oct 2014 | B2 |
| 8964062 | Neglur | Feb 2015 | B1 |
| 9001226 | Ng et al. | Apr 2015 | B1 |
| 9531961 | Rivard et al. | Dec 2016 | B2 |
| 9819849 | Rivard et al. | Nov 2017 | B1 |
| 9912928 | Rivard et al. | Mar 2018 | B2 |
| 9917995 | Falk | Mar 2018 | B2 |
| 9998721 | Rivard et al. | Jun 2018 | B2 |
| 10044941 | Falk | Aug 2018 | B2 |
| 10110870 | Rivard et al. | Oct 2018 | B2 |
| 10129514 | Rivard et al. | Nov 2018 | B2 |
| 10200663 | Saito et al. | Feb 2019 | B2 |
| 10375315 | Falk | Aug 2019 | B2 |
| 10375369 | Rivard et al. | Aug 2019 | B2 |
| 10455130 | Falk | Oct 2019 | B2 |
| 10469714 | Rivard et al. | Nov 2019 | B2 |
| 10477077 | Rivard et al. | Nov 2019 | B2 |
| 10742892 | Le et al. | Aug 2020 | B1 |
| 10904505 | Rivard et al. | Jan 2021 | B2 |
| 20040239767 | Stavely et al. | Dec 2004 | A1 |
| 20070025270 | Sylvain | Feb 2007 | A1 |
| 20070025720 | Raskar et al. | Feb 2007 | A1 |
| 20080298793 | Clark | Dec 2008 | A1 |
| 20090129634 | De Waele | May 2009 | A1 |
| 20090135262 | Ogasawara | May 2009 | A1 |
| 20090160970 | Fredlund et al. | Jun 2009 | A1 |
| 20090196595 | Okubo | Aug 2009 | A1 |
| 20100008658 | King | Jan 2010 | A1 |
| 20100026853 | Mokhnatyuk | Feb 2010 | A1 |
| 20100124041 | Druchinin | May 2010 | A1 |
| 20100124412 | King | May 2010 | A1 |
| 20100202767 | Shirakawa | Aug 2010 | A1 |
| 20100290771 | Clark | Nov 2010 | A1 |
| 20110123185 | Clark | May 2011 | A1 |
| 20110157408 | Steinberg et al. | Jun 2011 | A1 |
| 20110188845 | Hanayama et al. | Aug 2011 | A1 |
| 20120033959 | King | Feb 2012 | A1 |
| 20120044380 | Imai | Feb 2012 | A1 |
| 20120045193 | King | Feb 2012 | A1 |
| 20120127334 | Imai | May 2012 | A1 |
| 20120140088 | Clark | Jun 2012 | A1 |
| 20120177352 | Pillman et al. | Jul 2012 | A1 |
| 20120321287 | King et al. | Dec 2012 | A1 |
| 20130069559 | Li et al. | Mar 2013 | A1 |
| 20130128101 | Midorikawa | May 2013 | A1 |
| 20130300894 | Imai et al. | Nov 2013 | A1 |
| 20140016026 | Wolfe et al. | Jan 2014 | A1 |
| 20140347554 | Shirakawa | Nov 2014 | A1 |
| 20150116586 | Mahowald | Apr 2015 | A1 |
| 20150262024 | Braithwaite et al. | Sep 2015 | A1 |
| 20160021292 | Zhang | Jan 2016 | A1 |
| 20160198078 | Falk | Jul 2016 | A1 |
| 20160232672 | Rezaiifar | Aug 2016 | A1 |
| 20160248960 | Falk | Aug 2016 | A1 |
| 20170332131 | Opsenica et al. | Nov 2017 | A1 |
| 20170374265 | Finlow-Bates | Dec 2017 | A1 |
| 20180343374 | Tamura | Nov 2018 | A1 |
| 20180359411 | Kohstall et al. | Dec 2018 | A1 |
| 20190037018 | Scurrell | Jan 2019 | A1 |
| 20190124252 | Suzuki | Apr 2019 | A1 |
| 20200059575 | Rivard et al. | Feb 2020 | A1 |
| 20200267299 | Le et al. | Aug 2020 | A1 |
| 20210274142 | Rivard et al. | Sep 2021 | A1 |
| 20220053121 | Falk et al. | Feb 2022 | A1 |
| 20220150407 | Stenbacka | May 2022 | A1 |
| Number | Date | Country |
|---|---|---|
| 2967455 | Nov 2017 | CA |
| 1509130 | Jun 2004 | CN |
| 1574899 | Feb 2005 | CN |
| 1645914 | Jul 2005 | CN |
| 1704835 | Dec 2005 | CN |
| 101048796 | Oct 2007 | CN |
| 201083935 | Jul 2008 | CN |
| 101536493 | Sep 2009 | CN |
| 102143320 | Aug 2011 | CN |
| 201936103 | Aug 2011 | CN |
| 102447834 | May 2012 | CN |
| 102879977 | Jan 2013 | CN |
| 103076708 | May 2013 | CN |
| 103297684 | Sep 2013 | CN |
| 203407048 | Jan 2014 | CN |
| 105556384 | May 2016 | CN |
| 105579901 | May 2016 | CN |
| 105635599 | Jun 2016 | CN |
| 105657281 | Jun 2016 | CN |
| 106027912 | Oct 2016 | CN |
| 106210550 | Dec 2016 | CN |
| 106576155 | Apr 2017 | CN |
| 107079193 | Aug 2017 | CN |
| 107209940 | Sep 2017 | CN |
| 107395997 | Nov 2017 | CN |
| 107534738 | Jan 2018 | CN |
| 108012134 | May 2018 | CN |
| 109644224 | Apr 2019 | CN |
| 113454530 | Sep 2021 | CN |
| 1278373 | Jan 2003 | EP |
| 3047333 | Jul 2016 | EP |
| 3047334 | Jul 2016 | EP |
| 2154341 | Sep 1985 | GB |
| 2477406 | Aug 2011 | GB |
| S 63-276039 | Nov 1988 | JP |
| 2004-029184 | Jan 2004 | JP |
| 2017-121029 | Jul 2017 | JP |
| 200900830 | Jan 2009 | TW |
| WO 2015038047 | Mar 2015 | WO |
| WO 2015038061 | Mar 2015 | WO |
| WO 2015047150 | Apr 2015 | WO |
| WO 2017030777 | Feb 2017 | WO |
| WO 2017134933 | Aug 2017 | WO |
| WO 2017134933 | Oct 2017 | WO |
| WO 2018005765 | Jan 2018 | WO |
| WO 2018017625 | Jan 2018 | WO |
| WO 2019022243 | Jan 2019 | WO |
| Entry |
|---|
| Extended European Search Report for European Patent Application No. 19858764.4, dated May 10, 2022, in 10 pages. |
| International Search Report and Written Opinion of the International Searching Authority for International Application No. PCT/SE2019/050829, dated Nov. 18, 2019, in 19 pages. |
| International Search Report for International Application No. PCT/SE2014/051072, dated Jan. 9, 2015, in 5 pages. |
| International Written Opinion for International Application No. PCT/SE2014/051072, dated Jan. 9, 2015, in 5 pages. |
| International Preliminary Reporton Patentability for International Application No. PCT/SE2014/051072, dated Sep. 8, 2015, in 6 pages. |
| Extended European Search Report in Patent Application No. 14844738.6, dated May 2, 2017, in 10 pages. |
| International Search Report for International Application No. PCT/SE2014/050224, dated Nov. 14, 2014, in 5 pages. |
| International Written Opinion for International Application No. PCT/SE2014/050224, dated Nov. 14, 2014, in 5 pages. |
| International Preliminary Report on Patentability for International Application No. PCT/SE2014/050224, dated Aug. 14, 2015, in 12 pages. |
| Extended European Search Report in Patent Application No. 14844826.9, dated Apr. 13, 2017, in 8 pages. |
| International Search Report for International Application No. PCT/SE2014/050225, dated May 27, 2014, in 5 pages. |
| International Written Opinion for International Application No. PCT/SE2014/050225, dated May 27, 2014, in 5 pages. |
| International Preliminary Report on Patentability for International Application No. PCT/SE2014/050225, dated Sep. 8, 2015, in 6 pages. |
| International Search Report and Written Opinion of the International Searching Authority for International Application No. PCT/SE2019/050850, dated Nov. 26, 2019, in 17 pages. |
| International Search Report and Written Opinion of the International Searching Authority for International Application No. PCT/SE2020/050070, dated Aug. 4, 2020, in 12 pages. |
| Swedish Search Report for Swedish Patent Application No. 1950126-1, dated Aug. 7, 2019, in 12 pages. |
| Extended European Search Report for European Patent Application No. 19861059.4, dated Apr. 28, 2022, in 8 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20220053120 A1 | Feb 2022 | US |
