throbber
Application No.: 17/316,760
`
`Docket No.: 083710-3336
`
`I.
`
`Introduction
`
`REMARKS
`
`In response to the pending Office Action, Applicants respectfully traverse the rejection of
`
`the claims under 35 U.S.C. § 112, second paragraph, and under 35 U.S.C. § 102 for the reasons set
`
`forth below. In addition, new claims 15-18 have been added. Support for the new claims can be
`
`found, for example, in paragraphs [0227]-[0232] of the specification. No new matter has been
`
`added.
`
`
`
`IL. The Rejection Of The Claims Under 35 U.S.C.§112, Second Paragraph
`
`Claims 1-14 were rejected under 35 U.S.C. § 112, second paragraph, and the pending
`
`rejection asserts that there is not proper antecedent support for the term “the data” in claim 1 or
`
`claim 13. However, both claims | and 13 recite the phrase “the signal processing circuit generates
`
`data”. For example, claim | recites: the signal processing circuit generates data indicating a state
`
`of the target based on a temporal changein thefirst image data and a temporal changein the
`
`
`second image data and outputs the data. As such, Applicants respectfully submit that claim 1
`
`provides a proper antecedent basis for the term “the data”.
`
`Similar to claim 1, claim 13 recites: generating data indicating a state ofthe target based on
`
`a temporal changein thefirst image data and a temporal changein the second image data and
`
`
`outputting the data. As such, claim 13 also provides a proper antecedent basis for the term “the
`
`data”.
`
`In view ofthe foregoing, it is respectfully submitted that both claim 1 and claim 13 provide
`
`a proper antecedentbasis for all elements recited therein, and therefore the rejection should be
`
`withdrawn.
`
`

`

`Application No.: 17/316,760
`
`Docket No.: 083710-3336
`
`
`
`Ill. The Rejection Of The Claims Under 35 U.S.C.§102
`
`Claims 1-3, 9 and 12-14 were rejected under 35 U.S.C. § 102 as being anticipated by USP
`
`Pub. No. 2017/0289568 to Fujii. For at least the following reasons, it is respectfully submitted that
`
`all pending claims are patentable over Fujii.
`
`Claim 1 recites in-part:
`
`a light source that emits a light pulse radiated onto a target part including a head of a
`
`target;
`
`an image sensorthat receives a reflected light pulse which is caused as the light pulse
`is radiated onto the target part, and that outputs first image data indicating appearance of a
`face of the target and second image data according to distribution of an amountoflight of at
`least one of componentsofthe reflected light pulse;
`
`a control circuit that controls the light source and the image sensor; and
`the signal processing circuit generates data indicating a state of the target based on
`a temporal changein the first image data and a temporal change in the second image data
`and outputs the data.
`
`Thus, in accordance with claim 1, the image sensor outputsfirst image data indicating
`
`
`appearance ofa face of the target, and the signal processing circuit generates data indicating a
`
`state of the target based on a temporal changein thefirst image data and a temporal change in the
`
`second image data and outputs the data. Nowhere does Fuji disclose or suggest the foregoing
`
`highlighted elements of claim 1.
`
`More specifically, nowhere does Fujii disclose or suggest generating any image data
`
`indicating the appearance of the face of the target(first data). As such,it is also clear that Fujii
`
`fails to disclose or suggest generating data indicating the state of the target based on a temporal
`
`changein thefirst data. Indeed, the specification of Fujii does not even mention the term “face,”
`
`muchless suggest generating image data indicating the appearance of the face of the target. Thus,
`
`

`

`Application No.: 17/316,760
`
`Docket No.: 083710-3336
`
`for at least these reasons, it is clear that Fujii does not disclose or suggest the foregoing elements of
`
`claim 1.
`
`Turning to claim 13, claim 13 recites in-part:
`
`
`causing the image sensorto outputfirst image data indicating appearance ofa face
`of the target;
`
`
`generating data indicating a state of the target based on a temporal change in the
`first image data and a temporal change in the second image data and outputting the data.
`
`Asclaim 13 recites elements corresponding the elements of claim 1 discussed above, it is
`
`respectfully submitted that claim 13 is also patentable over Fujii for the same reasonsas claim 1.
`
`Finally, as claim 14 recites the same elements as claim 13 noted above, claim 14 is also
`
`patentable over Fujii for the same reasonsas claims 1 and 13.
`
`IV.
`
`Dependent Claims
`
`UnderFederal Circuit guidelines, a dependent claim is nonobviousif the independent claim
`
`upon whichit dependsis allowable becauseall the limitations of the independent claim are
`
`contained in the dependent claims, Hartness InternationalInc. v. Simplimatic Engineering Co., 819
`
`F.2d at 1100, 1108 (Fed. Cir. 1987). Accordingly, as the pending independentclaimsare patentable
`
`for at least the reasonsset forth above, it is respectfully submitted that all claims dependent thereon
`
`are also patentable.
`
`V.
`
`Summary
`
`Having fully respondedto all matters raised in the Office Action, Applicants submit thatall
`
`claims are in condition for allowance, an indication for which is respectfully solicited. If there are
`
`9
`
`

`

`Application No.: 17/316,760
`
`Docket No.: 083710-3336
`
`any outstanding issues that might be resolved by an interview or an Examiner’s amendment, the
`
`Examineris requested to call Applicants’ attorney at the telephone number shownbelow.
`
`Respectfully submitted,
`
`RIMON,P.C.
`
`/Michael E. Fogarty/
`
`MichaelE. Fogarty
`Registration No. 36,139
`
`8300 Greensboro Dr., Suite 500
`McLean, VA, 22102
`Phone/Fax: (571) 765-7716
`Date: December 21, 2023
`
`Please recognize our Customer No. 53080
`as our correspondence address.
`
`10
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket