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
The objections to the drawings and specification are withdrawn in view of the amendment filed on 10/19/2026.
The objections to the specification is withdrawn in view of the amendment filed on 10/19/2026.
Applicant’s arguments in view of the claim amendments filed on 10/19/2026, with respect to the 35 U.S.C. §112(a) rejections have been fully considered and are persuasive. The 35 U.S.C. §112(a) rejections have been withdrawn.
Applicant’s arguments in view of the claim amendments filed on 10/19/2026, with respect to the 35 U.S.C. §112(b) rejections have been fully considered and are persuasive. The 35 U.S.C. §112(b) rejections have been withdrawn.
Applicant’s arguments in view of the claim amendments filed on 10/19/2026, with respect to the prior art rejection have been fully considered and are persuasive. The 35 U.S.C. §103 rejections have been withdrawn.
Claim Objections
Claim 13 is objected to because of the following informality: "a natural-language scene description that identifying objects" should read "a natural-language scene description that identifies objects". Appropriate correction is required.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 11 and 13-19 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claim 11 recites "performing, by the one or more processors, edge processing on the multimedia input to generate key input", together with "reducing a volume of frame data transmitted to the metadata extraction engine" (step (ii)) and "as the key input for transmission to the metadata extraction engine" (step (v)). By antecedent, "the one or more processors" are the "one or more processors of a metadata extraction engine" recited in the receiving step (very first limitation of the claim). The same step, however, describes its output as data transmitted to that engine. The claim therefore has two plausible constructions: (1) the engine's own processors perform the edge processing, and "transmission" means an internal hand-off between modules of the engine; or (2) edge processing is performed at the user device (the "edge") and the key input is sent over a network to the server-based engine. The specification supports both readings. It states that the system "performs edge processing to extract key input, via a server-based metadata extraction (MEX) engine" (pg. 13), and it also describes edge processing as a stage that precedes transmission of the key inputs (pg. 16-17; Fig. 1). The two constructions differ in who practices the claim: under (2), a server that receives raw multimedia and performs the cropping, scene segmentation and key-frame selection itself would not perform the claimed method, whereas under (1) it would. Because the claim does not inform a PHOSITA with reasonable certainty which construction is intended, claim 11 is indefinite. See MPEP § 2173.02 (In re Packard; Nautilus).
For purposes of examination, the edge processing of claim 11 is interpreted under BRI as performed by any processor, whether on the user device or in the metadata extraction engine. "[T]ransmission to the metadata extraction engine" is interpreted as any transfer of the key input to the feature-extraction stage of the engine, including an internal transfer between modules of the same engine.
Claim 11 recites "multimedia input comprising at least one of video data, audio data, still image data, or textual data" and then "applies a trained machine learning model to each frame and audio segment of the multimedia input to compute a numeric quality score, and storing ... only those frames and audio segments having a quality score at or above a predefined fidelity threshold". The conjunctive "each frame and audio segment" can plausibly be read in two ways. It may require that the multimedia input contain both frames and audio segments, so that video without audio, or a still image alone, falls outside the claim even though the claim says "at least one of". Or it may require the model to be applied only to whichever frames and audio segments happen to be present. The specification does not resolve the conflict. It describes the Fidelity Qualifier as filtering "low-fidelity video, still images, and audio" (g. 16, Fig. 2-1) without saying that both kinds of data must be present. Because the claim's own definition of the input is inconsistent with the conjunctive requirement of step (i), a PHOSITA cannot determine with reasonable certainty whether audio data is a required part of the input. Claim 11 is therefore indefinite. See MPEP § 2173.02.
For purposes of examination, claim 11 is interpreted under BRI to require multimedia input that includes at least frame-based visual data (video or still images). The fidelity qualification process is interpreted as applied to the frames, and to audio segments when audio data is present.
Claim 13 recites "the large language model (LLM) analysis generates a natural-language scene description". Claim 11, from which claim 13 depends, already recites that the same LLM analysis "generates a natural-language scene description." Claim 13 introduces the description a second time with an indefinite article. Double inclusion is not improper per se, but here it creates a real ambiguity. It is unclear whether claim 13 further limits the description of claim 11 or requires a second, separately generated description. It is therefore also unclear which description is meant by "the natural-language scene description" that the cross-validation step receives and compares in clause (a). Because the two constructions differ in scope (one description versus two), claim 13 is indefinite. See MPEP § 2173.05(o) (the facts of each case determine whether multiple inclusion of an element gives rise to indefiniteness); MPEP § 2173.02.
For purposes of examination, "a natural-language scene description" in claim 13 is interpreted under BRI as further limiting the same scene description generated by the LLM analysis of claim 11.
Claim 13 recites "a YOLO-class object detection model". Adding "-class" to the otherwise definite name "YOLO" (You Only Look Once) extends the expression to an undefined set of models. MPEP § 2173.05(b)(III)(E) explains that "[t]he addition of the word 'type' to an otherwise definite expression ... extends the scope of the expression so as to render it indefinite" (citing Ex parte Copenhaver), and that "ZSM-5-type aluminosilicate zeolites" was held indefinite because it was unclear what "type" was intended to convey. The suffix "-class" works the same way. The claim does not say whether the "class" is limited to YOLO models or extends to other single-stage detectors (e.g., SSD, RetinaNet), anchor-free detectors, or any real-time detector that shares some YOLO characteristic. As filed, the specification used "YOLO-class" only once, at pg. 7, in a passage that repeats the claim language without definition. Elsewhere it names only "You Only Look Once (YOLO)" models (pg. 18). The amendment to the specification filed 10/19/2026 strikes "YOLO-" from the pg. 7 passage, so the amended specification gives no guidance at all on what the claimed "class" covers. Claim 13 is therefore indefinite.
For purposes of examination, "a YOLO-class object detection model" is interpreted under BRI as any You Only Look Once (YOLO) object detection model, i.e., a single-pass convolutional detector that predicts bounding boxes and class labels in one forward pass.
Claim 15 recites "by identifying the specific information fields that caused the sufficiency condition to fail". The only possible antecedent for "the specific information fields" is "subtask-objective information fields" in alternative (ii), the completeness metric. Amended claim 15 requires at least one criterion "selected from" alternatives (i), (ii) or (iii), so it covers embodiments in which only the confidence score of (i) or only the uncertainty metric of (iii) is evaluated. In those embodiments no information fields are recited, so there is no antecedent basis for "the specific information fields". It is also unclear how the narrower subtask objective is "algorithmically derived ... by identifying" fields when the sufficiency condition fails because of a cross-source agreement score or a sampling variance rather than unpopulated fields. The scope of the sub-agent generation step therefore cannot be determined with reasonable certainty.
For purposes of examination, "the specific information fields that caused the sufficiency condition to fail" is interpreted under BRI as any portion of the research agent's subtask objective (for example, unpopulated subtask-objective information fields, or the data items for which agreement or certainty was insufficient) associated with the evaluation criterion that failed its threshold. This is consistent with the specification's description of sub-agents spawned to resolve "inconsistencies, omissions, or cross-modal conflicts" (spec. at pg. 3).
Claim 17 recites "inferred preferences from the session". Claim 17 recites "inferred preferences from the session" but introduces no "session" that "the session" can refer to. The only sessions recited are "a prior configuration session" and "prior interaction sessions". It cannot be determined whether "the session" means the prior configuration session, one of the prior interaction sessions, or the current session in which the user request is decomposed and the structured metadata is transmitted, which claims 11 and 17 never recite.
For purposes of examination, "the session" is interpreted under BRI as the current interaction session in which the user request of claim 11 is processed and the structured metadata is transmitted.
Claims 14, 16, 18 and 19 are rejected because they depend, directly or indirectly, from rejected claim 11 (and, for claim 16, from rejected claim 15) and inherit the indefiniteness identified above. They present no independent ground of indefiniteness beyond their base claims.
Appropriate correction is required.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). 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 ALAN CHEN whose telephone number is (571)272-4143. The examiner can normally be reached M-F 10-7.
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, Kamran Afshar can be reached at (571) 272-7796. 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.
/ALAN CHEN/Primary Examiner, Art Unit 2125