DETAILED ACTION
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 filed January 16, 2025 have been fully considered but they are not persuasive. Applicant argues that particular limitations that have been added to the independent claims by the instant amendment are not taught by Bellaish. Some of the limitations that have been added were recited in original claim 8, which has been cancelled. Original claim 8 was rejected as being anticipated by Bellaish. Applicant argues specifically that the following limitation are not taught or suggested by Bellaish:
a processing device configured to (i) generate a confidence value associated with the installation accuracy determined for each of the installed components, (ii) if the confidence value is within a confidence value threshold range for a respective installed component, identify the respective installed component as being improperly installed, the confidence value threshold range being selected based on a type of defect identified for each of the installed components, and (iii) generating a marker in an image to identify the installed component having the confidence value within the confidence value threshold range as an improperly installed component.
The examiner disagrees. With reference to limitation (i), as indicated in the nonfinal Office Action, paras. [0122]-[0125] of Bellaish disclose using an inference model to determine quality indications for installations of different types of concrete components based on images of the concrete components. The quality indications are confidence values relating to the installation accuracy, as discussed in, for example, para. [0099], which defines construction errors to include “concrete of low quality”. The different concrete components include, for example, walls, ceilings and stairs, as discussed in para. [0124]. Therefore, Bellaish teaches limitation (i).
With reference to limitation (ii), Bellaish discloses that the threshold values or ranges are selected for the respective type of concrete component and that if the quality indication is within a threshold range for the respective concrete component, the component is identified as improperly installed. As indicated above, para. [0099] defines low quality concrete as a construction error and para. [0125] discusses selecting thresholds for the respective concrete component types. Para. [0133] discusses comparing the quality indication values to the respective thresholds. Para. [0127] discloses that the threshold value for the different types of component can be based on a construction plan that identifies “minimal quality indication requirements” for the concrete components. The comparison of the quality indication value with the respective threshold value or range, the installation is deemed to be improper or in error.
Bellaish discloses that the quality indication threshold range is selected based on the type of defects that can occur in the components. Para. [0123] discusses training the inference model to determine the quality indication values for the concrete objects based on images of the objects that are in the ordinary condition and based on images of the objects having known defects (“segregation of the concrete, discoloration of the concrete, scaling of the concrete, crazing of the concrete, cracking of the concrete, curling of the concrete, etc.”). Since the purpose of identifying the quality indication values is so that they can be compared to threshold ranges that are selected to identify such defects, the threshold ranges are necessarily selected based at least in part on the types of defects to be identified in the different components. Therefore, Bellaish teaches limitation (ii).
With reference to limitation (iii), Fig. 18, para. [0253] of Bellaish discloses overlaying the image containing the construction error with a visual indication of the construction error (“wherein the overlay may include a visual indication of the construction error and the visual indication may be based on the type of the construction error”. Para. [0259] of Bellaish discloses that the overlaid visual indication is a marker such as “an arrow pointing on the location, with a polygon around the location”. Therefore, Bellaish teaches limitation (iii).
Applicant also argues that “[a]lthough Bellaish briefly discusses using different threshold values for the quality of installation, Bellaish fails to distinguish between high and low risk installations to customize the threshold values.” Applicant argues further that “[t]he subject application states that the threshold range for the confidence value can be different for high and low risk installations, and the selection of the confidence value threshold range recited in claim 1 provides a customization to ensure accuracy in identifying improper installations and a means for additional oversight in high risk installations.”
First of all, the independent claims do not recite any language pertaining to customizing the threshold values to take into account high and low risk installations. Although the claims are interpreted in light of the specification, limitations from the specification are not read into the claims. See In re Van Geuns, 988 F.2d 1181, 26 USPQ2d 1057 (Fed. Cir. 1993).
Secondly, the threshold values in Bellaish are based at least in part on risk because they are designed to be compared to the quality indication values, which are based at least in part on the risk associated with the particular installed concrete component. For example, the quality indication value can indicate “cracking of the concrete” (para. [0123]), which can lead to failure of, for example, a staircase. As indicated above, the threshold range is selected based on the type of component, as indicated in para. [0124]: “for example using one set of threshold values for walls, a second set of threshold values for ceilings, a third set of threshold values for stairs, and so forth.” Therefore, the threshold is based at least in part on risk associated with the component.
Furthermore, Bellaish discloses that a degree of severity of a construction error is assigned based on a result of the comparison of the error with a threshold value (para. [0273]), which means that the threshold values or ranges that are used are selected based at least on part on the risk associated with the error or defect. The BRI for the terms “low risk” and “high risk”, based on para. [0043] of the present specification, is that it means the risk that the defect has on building envelope performance, such as missing fasteners, which are considered low risk defects, compared to missing window flashing, which are considered low risk defects. Bellaish discloses determining the levels of severity of identified defects and assigning different severity levels to the defects based on the comparison of the errors with the respective threshold values or ranges (para. [0026]). A defect assigned a higher severity level would correspond to a high-risk improper installation whereas a defect assigned a lower severity would correspond to a low-risk improper installation. Therefore, Bellaish teaches this limitation.
Claim Interpretation
The claims in this application are given their broadest reasonable interpretation (BRI) using the plain meaning of the claim language in light of the specification as it would be understood by one of ordinary skill in the art. The BRI of a claim element (also commonly referred to as a claim limitation) is limited by the description in the specification.
In the following, some of the terms in the claims have been given BRIs in light of the specification. These BRIs are used for purposes of searching for prior art and examining the claims, but cannot be incorporated into the claims. Should Applicant believe that different interpretations are appropriate, Applicant should point to the portions of the specification that clearly support a different interpretation.
Claim Objections
Claims 5 and 24 are objected to because of the following informalities:
In claim 5, line 3, “the
In claim 24, line 3, “markets” should be changed to –markers--.
Appropriate correction is required.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-3, 5-6, 9-13, 15-16, 18-21 and 23 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by U.S. Publ. Appl. No. 2020/0151833 of Bellaish et al. (hereinafter referred to as “Bellaish”).
Regarding claim 1, Bellaish discloses a system for determining construction installation accuracy (Fig. 11, para. [0186] disclose detecting “an object installed incorrectly”), the system comprising:
a database configured to electronically store data, the data including an
installation detection model trained based on historical construction installation data (the BRI for historical construction data, based on para. 0041] of the present disclosure, is that it means data of accurate or inaccurate construction installations used to trans a model; para. [0123] of Bellaish discloses training an object detection machine learning model using images of construction installments that are labeled with quality indications that indicate a degree of correctness of the construction installation depicted in the image; regarding the recited database and the installation detection model, Fig. 6, memory 600, para. [0091] discusses the database of Bellaish and para. [0111] of Bellaish discusses the installation detection model: “[i]n some embodiments, analyzing image data, for example by Step 720, Step 730, Step 930, Step 1120, Step 1320, Step 1520, Step 1530, etc., may comprise analyzing the image data and/or the preprocessed image data using one or more rules, functions, procedures, artificial neural networks, object detection algorithms, face detection algorithms, visual event detection algorithms, action detection algorithms, motion detection algorithms, background subtraction algorithms, inference models, and so forth. Some examples of such inference models may include: an inference model preprogrammed manually; a classification model; a regression model; a result of training algorithms, such as machine learning algorithms and/or deep learning algorithms, on training examples, where the training examples may include examples of data instances, and in some cases, a data instance may be labeled with a corresponding desired label and/or result; and so forth”); and
a processing device in communication with the database (paras. [0084]-[0091], Fig. 5, computational node 500 includes memory unit 210 that can be part of the database memory 600), the processing device configured to:
receive as input an image associated with a construction installation (para. [0104], Fig. 7, step 710, apparatus 200 with image sensor 260);
electronically detect one or more components installed in the construction installation depicted in the image (para. [0112]: “[i]n some embodiments, analyzing the image data to identify a region depicting an object of an object type and made of concrete (Step 720) may comprise analyzing image data (such as image data captured from a construction site using at least one image sensor and obtained by Step 710) and/or preprocessed image data to identify a region of the image data depicting at least part of an object, wherein the object is of an object type and made, at least partly, of concrete. In one example, multiple regions may be identified, depicting multiple such objects of a single object type and made, at least partly, of concrete”);
execute the installation detection model to determine an installation accuracy of the installed one or more components (para. [0111] cited above discloses one or more installation detection models/algorithms that are executed to detect objects; para. [0186] discloses analyzing the captured images of the construction site in step 1120 of Fig. 11 to “identify an object installed incorrectly”; para. [0099] defines low quality concrete as a construction error);
generate a confidence value associated with the installation accuracy determined for each of the one or more installed components (paras. [0122]-[0125] of Bellaish disclose using an inference model to generate quality indication values for installations of different types of concrete components (e.g., walls, ceilings, stairs, etc.) based on images of the concrete components; the quality indication values constitute confidence values associated with installation accuracy; for example, para. [0099] defines construction errors to include, for example, “concrete of low quality”, which would be indicated by the quality indication value generated by the inference model);
if the confidence value is within a confidence value threshold range for a respective one or more installed components, identify the respective installed one or more installed components as being improperly installed, wherein the confidence value threshold range is selected based on a type of defect identified for each of the one or more installed components (Bellaish discloses that the threshold values or ranges are selected for the respective type of concrete component and that if the quality indication is within a quality value threshold range for the respective concrete component, the component is identified as improperly installed. Para. [0125] discusses selecting thresholds for the respective concrete component types. Para. [0133] discusses comparing the quality indication values to the respective thresholds. Para. [0127] discloses that the threshold value for the different types of component can be based on a construction plan that identifies “minimal quality indication requirements” for the concrete components. The comparison of the quality indication value with the respective threshold value or a range delineated by the threshold, the installation is deemed to be improper or in error. Para. [0123] discusses training the inference model to determine the quality indication values for the concrete objects based on images of the objects that are in the ordinary condition and based on images of the objects having known defects (“segregation of the concrete, discoloration of the concrete, scaling of the concrete, crazing of the concrete, cracking of the concrete, curling of the concrete, etc.”). Since the purpose of identifying the quality indication values is so that they can be compared to threshold ranges that are selected to identify such defects, the threshold ranges are selected based on the type of defect to be identified in the different components); and
generate a marker in the image to identify the one or more installed components having the confidence value within the confidence value threshold range as an improperly installed component (the BRI for “marker”, based on para. [0045] of the present disclosure, is that it means any designation on the image identifying a region or item in the image, such as, for example, a bounding box, circle, oval, arrow, or the like; Fig. 18, para. [0253] of Bellaish discloses overlaying the image containing the construction error with a visual indication of the construction error, “wherein the overlay may include a visual indication of the construction error, and the visual indication may be based on the type of the construction error”; para. [0259] discloses that the visual indication marker may include “an arrow pointing on the location, with a polygon around the location”).
Regarding claim 2, Bellaish discloses that the installation detection model is trained based on at least one of manufacturer or industry construction standards (para. [0261] discloses that the detected construction error can be an incorrect rating of the installed object, such as an incorrect fire rating, soundproofing rating, etc.; such ratings are governed by manufacturer and/or industry standards; see also para. [0127] discussing determining whether construction site installations meet industry standards).
Regarding claim 3, Bellaish discloses that the system comprises a user electronic device in communication with the processing device, the user electronic device capable of electronically transmitting the image as the input to the processing device via a communication interface, wherein the processing device is configured to transmit an updated image to the user electronic device via the communication interface, the updated image including the marker generated in the image to identify the improperly installed component (para. [0072] discloses capturing the images of the construction site via one or more image sensors 260 of a user device and transmitting the images via one or more communications modules 230 to other computerized devices such as communication node 500, which constitutes the processing device; para. [0103] discloses that the image sensor 260 can be, for example, a various types of wearable image sensors worn by a person at the construction site; Fig. 18, para. [0253] of Bellaish discloses overlaying the image containing the construction error with a visual indication of the construction error, “wherein the overlay may include a visual indication of the construction error, and the visual indication may be based on the type of the construction error”; para. [0259] discloses that the visual indication marker may include “an arrow pointing on the location, with a polygon around the location”; para. [0080] discloses transmitting visual information to the user via user electronic visual output devices; as indicated above, Fig. 18, para. [0253] discloses overlaying the image containing the construction error with a visual indication of the construction error; the image overlayed with the visual indication of the construction error constitutes the updated image that is transmitted to the user electronic device).
Regarding claim 5, Bellaish discloses that the processing device (computational node 500) is configured to transmit to the user electronic device instructions on how to correctly install the one or more components (para. [0263] discloses transmitting to the user the image with the overlaid visual indication indicating that the object is installed at an incorrect orientation along with a visual indication of the correct orientation of the installed object based on the desired orientation in a construction plan; this constitutes transmitting instructions to the user on how to correctly install the component).
Regarding claim 6, Bellaish discloses that the one or more components installed in the construction installation depicted in the image are of different types of installations, the processing device is configured to detect, identify and classify each type of the different types of installations (paras. [0259]-[0267] disclose that the one or more components are different types of installations, e.g., the object installed at an incorrect location at the construction site (para. [0259]), an object of an incorrect type installed at the construction site (para. [0260]), an object of an incorrect rating installed at construction site (para. [0261]), an incorrect quantity of an element installed at the construction site (para. [0262]), an incorrect orientation of an object at the construction site (para. [0263]), an object of incorrect dimensions installed at the construction site (para. [0264]), an object missing from the construction site (para. [0265]), an object installed in the construction site that is unnecessary according to a construction plan (para. [0266]), an incorrect performance order of actions, e.g., a performance of a first action in the construction site before a performance of a second action (para. [0267]), an incorrect spacing between objects installed in the construction site (para. [0268]); paras. [0259]-[0267] disclose that the type of error is detected, identified and classified as, for example, an incorrect location of installment, an incorrect type of object installed, an object of an incorrect rating installed, etc.).
Regarding claim 9, Bellaish discloses if the confidence value is equal to or greater than a bottom threshold value of the confidence value threshold range, the processing device is configured to transmit an updated image to a user electronic device via a communication interface, the updated image including the identified improperly installed component (para. [0132] discloses that the quality indication is compared to at least a bottom threshold (para. [0127], the minimal quality indication value for the component indicated by the construction plan) of the quality indication value threshold range, and in response to the result of the comparison, transmitting an updated image overlaid with a visual indication presenting information to the user based on the quality indication; para. [0080] discloses transmitting visual information such as the updated image with the overlay to the user via user electronic visual output devices; paras. [0063]-[0064] disclose various communication interfaces for transmitting information from the user to the system and vice versa).
Regarding claim 10, Bellaish discloses wherein if the confidence value is less than the bottom threshold value, the processing device is configured to transmit an updated image to a reviewer electronic device via a communication interface to request confirmation of the identification of the improperly installed component, and wherein validation of the updated image by the reviewer trains the installation detection model and improves performance of the installation detection model (para. [0132] discloses determining whether a quality indication is or is not greater than the bottom threshold value and causing an action to be taken based on the comparison, where the action can be presenting the result of the comparison to a user; paras. [0127] and [0135] disclose that the threshold may be set to a minimal quality indication requirement specified in the construction plan, in which case a determination that the quality indication is less than the threshold would indicate that the installation does not meet specifications and therefore constitutes an improperly installed component; para. [0132] discloses that the indications provided to the user can be “provided as a: visual output, audio output, tactile output, any combination of the above, and so forth. In some examples, the amount of indications provided to the user, the events triggering the indications provided to the user, the content of the indications provided to the user, the nature of the indications provided to the user, etc., may be configurable. The indications provided to the user may be provided: by the apparatus detecting the events, through another apparatus (such as a mobile device associated with the user, mobile phone 111, tablet 112, and personal computer 113, etc.), and so forth”; paras. [0218]-[0219] disclose that when the confidence with which an object at the construction site is detected and recognized is low, the image data and associated progress records are presented to the user with a query asking the user to identify the object by inputting information to a user interface; when the user answers the query, step 1340 of Fig. 13 receives the feedback; para. [0123] discloses using training examples, which can include these images and the corresponding user feedback, to train the installation detection model to improve the performance of the model).
Regarding claim 11, the rejection of claim 1 applies mutatis mutandis to claim 11.
Regarding claims 12 and 13, the rejections of claims 3 and 5 apply mutatis mutandis to claims 12 and 13.
Regarding claim 15, the rejection of claim 2 applies mutatis mutandis to claim 15.
Regarding claim 16, the rejection of claim 6 applies mutatis mutandis to claim 16.
Regarding claim 18, the rejection of claim 9 applies mutatis mutandis to claim 18.
Regarding claim 19, the rejection of claim 10 applies mutatis mutandis to claim 19.
Regarding claim 20, to the extent that claims 1 and 20 recite the same limitations, the rejection of claim 1 applies mutatis mutandis to claim 20. The only limitation that is recited in claim 20 that are not also recited in claim 1 is the non-transitory computer-readable medium storing instructions for performing the operations recited in claims 1 and 20. Bellaish discloses a non-transitory computer-readable medium storing instructions for performing those operations (para. [0027]).
Regarding claim 21, Bellaish discloses that the type of defect identified for the installed component is a high risk installation or a low risk installation (the BRI for the terms “low risk” and “high risk”, based on para. [0043] of the present specification, is that it means the risk that the defect has on building envelope performance, such as missing fasteners compared to missing window flashing. Bellaish discloses determining the levels of severity of identified defects and assigning different severities to the defect based on the comparison of the error with a threshold (para. [0026]). A defect assigned a higher severity would correspond to a high-risk installation whereas a defect assigned a lower severity would correspond to a low-risk installation).
Regarding claim 23, to the extent that claim 22 recites limitations concerning the marker that are recited in claims 1 and 3, the rejections of claims 1 and 3 apply mutatis mutandis to claim 22. Bellaish discloses that the processing device generates multiple initial markers as elements improperly installed and associated with the improperly installed component (paras. [0253]-[0272] discuss multiple markers overlaid on the image to identify multiple types of construction errors, such as, for example, an installed object having incorrect dimensions, an installed object having an incorrect rating, an installed object being in an incorrect location on the construction site, an installed door or window being open on the construction site, etc.).
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
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.
The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows:
1. Determining the scope and contents of the prior art.
2. Ascertaining the differences between the prior art and the claims at issue.
3. Resolving the level of ordinary skill in the pertinent art.
4. Considering objective evidence present in the application indicating obviousness or nonobviousness.
This application currently names joint inventors. In considering patentability of the claims the examiner presumes that the subject matter of the various claims was commonly owned as of the effective filing date of the claimed invention(s) absent any evidence to the contrary. Applicant is advised of the obligation under 37 CFR 1.56 to point out the inventor and effective filing dates of each claim that was not commonly owned as of the effective filing date of the later invention in order for the examiner to consider the applicability of 35 U.S.C. 102(b)(2)(C) for any potential 35 U.S.C. 102(a)(2) prior art against the later invention.
Claim 22 is rejected under 35 U.S.C. 103 as being unpatentable over Bellaish.
As indicated above, Bellaish discloses that the threshold ranges are different for different types of concrete component installations and that the thresholds are selected based on the construction plan. Bellaish also discloses that some types of construction errors are more severe than others and that the threshold range for each type of component installation is compared to the detected construction error associated with the component to determine the severity of the error. As indicated above in the rejection of claim 21, the term “risk” in the present disclosure is equivalent in meaning the term “severity” in Bellaish. Therefore, the threshold ranges that are used in Bellaish for improper installations of high severity are necessarily different from the threshold ranges that are used for improper installations of low severity.
Bellaish does not explicitly disclose that if the type of defect is a high risk installation defect, the quality indication value threshold range has a bottom threshold value that is smaller than the bottom threshold value for the low risk installation defect. However, it would be obvious to one of ordinary skill in the art before the effective filing date of the present disclosure to try different threshold ranges for component defects of different severity levels and choose one in which the quality indication value threshold range for a high risk installation has a bottom threshold value that is smaller than the bottom threshold value for the low risk installation since there are finite number of predictable ranges that can be used with a reasonable expectation of success. (See KSR International Co. v. Teleflex Inc., 550 U.S. 398, 82 USPQ2d 1385 (2007), in which the Supreme Court held that "obvious to try" was a valid rationale for an obviousness finding, for example, when there is a "design need" or "market demand" and there are a "finite number" of solutions).
Claim 24 is rejected under 35 U.S.C. 103 as being unpatentable over Bellaish in view of Chinese Patent Publication CN 112819747 A to Li (hereinafter referred to as “Li”).
Bellaish does not explicitly disclose that if an overlap of two or more of the initial markers is greater than a predetermined threshold value, the processing device merges the two or more of the initial markers to generate the marker. Li, in the same field of endeavor, discloses that if an overlap of two markers that mark lung nodule areas is greater than a predetermined threshold value (e.g., 60%), the processing device merges the two markers (page 8, last paragraph: “When multiple doctors are marking the same CT sequence or the area marked by the same doctor overlaps, calculate the overlap of the coordinates of the overlap area (the ratio of the coordinates of the overlap area to the coordinates of the marked area of each lung nodule), If the repetition is greater than the set threshold (60%), the two lung nodules will be merged into the same lung nodule for processing, otherwise, if the repetition is less than the set threshold, they will be processed separately”).
It would have been obvious to one of ordinary skill in the art, before the effective filing date of the present disclosure, to modify the system and method of Bellaish based on the teachings of Li to merge markers if they overlap by greater than a predetermined threshold amount as taught by Li. One of ordinary skill in the art would have been motivated to make the modification to prevent the final images from appearing cluttered or confusing due to multiple markers designating the same defect. The modification could have been made by one of ordinary skill in the art before the effective filing date of the present disclosure with a reasonable expectation of success because making the modification merely involves combining prior art elements according to known methods to yield predictable results (modifying the software executed by the system of Bellaish to determine the amount of overlap between markers and merge markers that have a large overlap).
Claim 25 is rejected under 35 U.S.C. 103 as being unpatentable over Bellaish in view of U.S. Publ. Appl. No. 2025/0174354 A1 to Kavusi (hereinafter referred to as “Kavusi”).
Bellaish does not explicitly disclose that the processing device automatically rejects the image if the image has insufficient quality to detect the one or more components and generates a notification requesting input of an additional image having sufficient quality to detect the one or more components. Kavusi, in the same field of endeavor, discloses a diagnostic platform (Fig. 6, 602) that automatically rejects an image if the image has insufficient quality to detect the one or more components (structures of the human eye) and generates a notification requesting input of an additional image having sufficient quality to detect the one or more components (if the platform 602 performing the quality check 702 determines that the image is of insufficient quality for diagnosis, the platform causes a notification to be sent to a recipient that prompts the recipient to generate another image (paras. [0065]-[0066]).
It would have been obvious to one of ordinary skill in the art, before the effective filing date of the present disclosure, to modify the system and method of Bellaish based on the teachings of Kavusi to determine whether the image captured by the user device is of sufficient quality to analyze for improper installations, and if so, to send a request to the user to capture another image of the construction site. One of ordinary skill in the art would have been motivated to make the modification to improve the accuracy of the defect detection algorithm and to reduce computational overhead associated with performing the analysis on images of poor quality that may lead to erroneous results. The modification could have been made by one of ordinary skill in the art before the effective filing date of the present disclosure with a reasonable expectation of success because making the modification merely involves combining prior art elements according to known methods to yield predictable results (modifying the software executed by the system of Bellaish to check image quality before performing the analysis and send a message to the user to capture another image if the image is of poor quality).
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 DANIEL J SANTOS whose telephone number is (571)272-2867. The examiner can normally be reached M-F 9-5.
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, Matt Bella can be reached at (571)272-7778. 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.
/DANIEL J SANTOS/Examiner, Art Unit 2667
/MATTHEW C BELLA/Supervisory Patent Examiner, Art Unit 2667