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 .
In response to the restriction requirement, Applicant elected claims 1, 5-6, 12, and 16-20 for further examination. As a result, claims 2-4, 7-11, 13-15 are withdrawn from further prosecution.
Applicant’s Election with traverse is acknowledged. The traversal is on the ground that the searches would be co-extensive and would not unduly burden the examiner. This is not found persuasive because burden is not only based upon searches being co-extensive. Examination and analysis for determination of patentability creates burden.
Claim Rejections - 35 USC § 102
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.
Claim(s) 1, 5-6, 12, and 16-20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Jewell et al. (US 9122602).
Jewell et al. discloses a method comprising:
obtaining a first set of conditions associated with a system, the first set of conditions
corresponding to one or more system components included in the system (FIG. 5: The list of components in the “Component” column. Abstract: Possible root causes (conditions) for anomalies experienced by the system components);
obtaining a mapping between one or more individual conditions of the first set of
conditions and one or more system classes corresponding to one or more system level effects
caused by the first set of conditions (column 4, lines 20-31: The root cause detection server can load and rank anomaly records (classes) to determine (map) which anomalies are the most likely root cause of the anomaly experienced by the monitored system component);
obtaining collapsing instructions, the collapsing instructions including a structure of
collapsing and one or more of the system components or one or more of the system classes of
interest (FIG. 5: User selects the condition set (root causes) in the Filter drop-down to collapse the unsalted conditions (root causes));
generating a second set of conditions, the second set of conditions organizing the first set of conditions according to the structure of collapsing; identifying a subset of conditions from the second set of conditions, the subset of conditions corresponding to one or more of the system components or one or more of the system classes included in the collapsing instructions (FIG. 5: Only the subset of root causes (“Top 5 possible root causes”) selected by the user appears, all others are collapsed/hide);
generating a visualization within a graphical user interface (GUI) including at least the
subset of conditions; and causing presentation of the visualization within the GUI to allow a user to interact with the visualization within the GUI (FIG. 5 shows the graphical user interface (GUI) to let a user to select the subset of root causes (conditions)).
Regarding to claims 5-6, 16-17: wherein the collapsing instructions are determined based at least on example structures determined based at least on hierarchy of the one or more system components included in the particular system, wherein the example structures are modified by a user (FIG. 5 shows the collapsing/filtering instruction from a user based on the rank of anomaly records mapped to the possible root cause).
Regarding to claim 18: wherein the one or more system classes are determined based at least on the one or more system components included in the system, the one or more system classes indicating how individual system components affect the system via failure (column 4, lines 20-31: Anomaly records (classes) determine (map) which anomalies are the most likely root cause of the anomaly experienced by the monitored system component).
Regarding to claim 19: wherein the system is comprised in at least one of: a control system for an autonomous or semi-autonomous machine; a perception system for an autonomous or semi-autonomous machine; a system for performing simulation operations; a system for performing digital twin operations; a system for performing light transport simulation; a system for performing collaborative content creation for 3D assets; a system for performing deep learning operations; a system for presenting at least one of augmented reality content, virtual reality content, or mixed reality content; a system for hosting one or more real-time streaming applications; a system implemented using an edge device; a system implemented using a robot; a system for performing conversational AI operations; a system implementing one or more large language models (LLMs); a system for generating synthetic data; a system incorporating one or more virtual machines (VMs); a system implemented at least partially in a data center; or a system implemented at least partially using cloud computing resources (The use of the prior art system such as one disclosed by Jewell et al. in a system as claimed is considered as an intended use that does not carry patentable weight).
CONTACT INFORMATION
Any inquiry concerning this communication or earlier communications from the examiner should be directed to LAM S NGUYEN whose telephone number is (571)272-2151.
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, DOUGLAS RODRIGUEZ, can be reached on 571-431-0716. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/LAM S NGUYEN/ Primary Examiner, Art Unit 2853
Prosecution Insights