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 .
Claims 1, 6, 7, 16, and 18 are amended; claims 2-5, 17, 19, and 20 are cancelled. Claims 1, 6-16, and 18 are pending.
The text of those sections of Title 35, U.S. Code not included in this action can be found in a prior Office action.
Response to Arguments
Applicant's arguments filed 06/29/2026 have been considered but they are not fully persuasive.
Regarding claims 1-7 and 16-20 rejected under 35 U.S.C. 101 as being directed to an abstract idea without significantly more, Applicant’s arguments have been fully considered and are persuasive. The rejection has been withdrawn.
Regarding claims 1-20 rejected under 35 U.S.C. 112(b) as being indefinite, Examiner acknowledges the amendments to claims 1 and 4 in overcoming their respective rejections. The rejections have been withdrawn.
Regarding claim 9 rejected under 35 U.S.C. 112(b) as being indefinite, Applicant has not amended claim 9 and the amendments do not address this specific rejection. The rejection is maintained.
Regarding claims 1-20 rejected under 35 U.S.C. 102(a)(1) as being anticipated by Abdul-Jawad et al. (U.S. Pat. 10,775,976), Applicant asserts that the prior art does not disclose “performing, at the ingest processor, advanced data processing to process the machine data, prior to indexing or storing the data, based on an advanced data processing pipeline executed on the ingest processor, wherein the advanced data processing pipeline uses advanced data processing content in a search language format to perform the advanced data processing, including a masking task, a noise reduction task, a filtering task, or a metricization task, that is different from the basic data processing performed at the forwarder” as recited in amended claim 1.
Applicant's arguments fail to comply with 37 CFR 1.111(b) because they amount to a general allegation that the claims define a patentable invention without specifically pointing out how the language of the claims patentably distinguishes them from the references.
Examiner submits that the prior art reference teaches the limitation above, as detailed in the rejection below. Accordingly, the rejection is maintained.
Claim Rejections - 35 USC § 112
Claim 9 is 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 9 recites “the advanced data processing content included in a technology add-on having basic data processing content”. There is insufficient antecedent basis for this limitation in the claims, as while the claims previously recite “advanced data processing content”, the claims do not previously recite that the advanced data processing content is “included in a technology add-on having basic data processing content”.
Claim Rejections - 35 USC § 102
Claims 1, 6-16, and 18 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Abdul-Jawad et al. (U.S. Pat. 10,775,976), hereinafter Abdul-Jawad.
Regarding claim 1, Abdul-Jawad disclosed a computer-implemented method, comprising: obtaining machine data at an ingest processor from a forwarder that performs basic data processing of the machine data (intake system/streaming data processor, i.e., ingest processor, receiving, i.e., obtaining, data, col. 14, lines 64-65, col. 19, lines 35-38; receiving raw machine data, col. 15, lines 7-8; forwarder transmitting data to streaming data processor, col. 19, lines 26-37; forwarder tagging data, i.e., basic data processing, col. 20, lines 2-6), wherein the ingest processor performs machine data processing in a cloud computing service (processing data, col. 14, line 30-31, 64-66; cloud-based service, col. 17, line 41) and provides the processed machine data to another component for subsequent indexing or storage (making processed data available to downstream systems/components, e.g., indexing system, col. 18, lines 20-25, col. 19, lines 26-41; storing processed data, col. 14, lines 30-38); performing, at the ingest processor, advanced data processing to process the machine data, prior to indexing or storing the data, based on an advanced data processing pipeline executed on the ingest processor (intake system performing processing, i.e., advanced data processing, on data, col. 14, lines 65-66, col. 18, line 22, col. 19, lines 26-28; intake system including forwarder, col. 19, line 28-29; forwarder comprising pipelines, i.e., advanced data processing pipeline, col. 20, lines 11-13), wherein the advanced data processing pipeline uses advanced data processing content in a search language format to perform the advanced data processing, including a masking task, a noise reductions task, a filtering task, or a metricization task, that is different from the basic data processing performed at the forwarder (utilizing rules/model, i.e., advanced data processing content, to process data, col. 15, lines 14-15, col. 18, lines 31-33, col. 19, lines 35-38; processing pipeline using search language, i.e., search language format, col. 123, lines 12-34; streaming data processors processing messages to determine which topics to place messages, i.e., filtering task, col. 24, lines 27-31); and providing the processed machine data to an indexer or data store of the cloud computing service for performing subsequent searching, analysis, and/or data visualization (making processed data available to downstream systems/components, e.g., indexing system, col. 18, lines 20-25, col. 19, lines 26-41; storing processed data, col. 14, lines 30-38; providing querying, i.e., searching, dashboards, i.e., analysis, and visualizations, col. 127, lines 31-34).
Regarding claim 6, Abdul-Jawad disclosed the method wherein the machine data obtained at the ingest processor comprises raw machine data (receiving raw machine data, col. 15, lines 7-8).
Regarding claim 7, Abdul-Jawad disclosed the method wherein the ingest processor is remote from an on-premises environment hosting a data source at which the machine data is generated (data intake and query system implemented in remote distributed computing system, col. 17, lines 38-46).
Regarding claim 8, Abdul-Jawad disclosed the method further comprising updating the advanced data processing pipeline based on the advanced data processing content (updating rules, i.e., advanced data processing content, applied by streaming data processors, col. 58, lines 41-49).
Regarding claim 9, Abdul-Jawad disclosed the method further comprising generating, via user input, the advanced data processing pipeline using the advanced data processing content included in a technology add-on having basic data processing content (users, i.e., user input, creating, i.e., generating, processing pipelines, col. 138, lines 43-50; utilizing rules/model, i.e., advanced data processing content, to process data, col. 15, lines 14-15, col. 18, lines 31-33, col. 19, lines 35-38).
Regarding claim 10, Abdul-Jawad disclosed the method further comprising generating, via user input, the advanced data processing pipeline using one or more processing functions included in a repository of processing functions (users, i.e., user input, creating, i.e., generating, processing pipelines, col. 138, lines 43-50; user specifying processing functions for processing pipeline, col. 141, lines 53-54).
Regarding claim 11, Abdul-Jawad disclosed the method wherein the advanced data processing content is integrated with the advanced data processing pipeline based on a discovery of the advanced data processing content in response to a user input and a selection of the advanced data processing content, or a technology add-on associated therewith (user creating and automatically discovering/generating rules, col. 112, lines 25-45).
Regarding claim 12, Abdul-Jawad disclosed the method further comprising performing, at the ingest processor, basic data processing to process the data based on a basic data processing pipeline executed on the ingest processor, wherein the basic data processing pipeline uses basic data processing content to perform the basic data processing (streaming data processor processing data according to rules, basic data processing content, col. 19, lines 35-38).
Regarding claim 13, Abdul-Jawad disclosed the method further comprising performing, at the ingest processor, basic data processing to process the data based on a basic data processing pipeline executed on the ingest processor (streaming data processor processing data according to rules, basic data processing content, col. 19, lines 35-38), wherein the basic data processing content is in a search language format converted from a properties and/or transformations configuration format included in a technology add-on (converting format of data, col. 56, lines 61-63; implementing search language, col. 109, lines 18-27).
Regarding claim 14, Abdul-Jawad disclosed the method wherein the advanced data processing content is installed on the ingest processor (rules maintained, i.e., installed, at the streaming data processor, col. 56, lines 48-49).
Regarding claim 15, Abdul-Jawad disclosed the method further comprising: generating the advanced data processing pipeline by referencing the advanced data processing content in the advanced data processing pipeline (creating data processing pipelines, col. 138, lines 42-45); and deploying the advanced data processing pipeline on the ingest processor (deploying data processing pipeline, col. 140, lines 33-36).
Regarding claim 16, Abdul-Jawad disclosed a computing device, comprising: a processor (processor, col. 159, line 42); and a non-transitory computer-readable medium having instructions stored thereon (non-transitory computer-readable storage medium containing instructions, col. 159, lines 39-47) that, when executed by the processor, cause the processor to perform operations including: obtaining machine data at an ingest processor from a forwarder that performs basic data processing of the machine data (intake system/streaming data processor, i.e., ingest processor, receiving, i.e., obtaining, data, col. 14, lines 64-65, col. 19, lines 35-38; receiving raw machine data, col. 15, lines 7-8; forwarder transmitting data to streaming data processor, col. 19, lines 26-37; forwarder tagging data, i.e., basic data processing, col. 20, lines 2-6), wherein the ingest processor performs machine data processing in a cloud computing service (processing data, col. 14, line 30-31, 64-66; cloud-based service, col. 17, line 41) and provides the processed machine data to another component for subsequent indexing or storage (making processed data available to downstream systems/components, e.g., indexing system, col. 18, lines 20-25, col. 19, lines 26-41; storing processed data, col. 14, lines 30-38); performing, at the ingest processor, advanced data processing to process the machine data, prior to indexing or storing the data, based on an advanced data processing pipeline executed on the ingest processor (intake system performing processing, i.e., advanced data processing, on data, col. 14, lines 65-66, col. 18, line 22, col. 19, lines 26-28; intake system including forwarder, col. 19, line 28-29; forwarder comprising pipelines, i.e., advanced data processing pipeline, col. 20, lines 11-13), wherein the advanced data processing pipeline uses advanced data processing content in a search language format to perform the advanced data processing, including a masking task, a noise reduction task, a filtering task, or a metricization task, that is different from the basic data processing performed at the forwarder (utilizing rules/model, i.e., advanced data processing content, to process data, col. 15, lines 14-15, col. 18, lines 31-33, col. 19, lines 35-38; processing pipeline using search language, i.e., search language format, col. 123, lines 12-34; streaming data processors processing messages to determine which topics to place messages, i.e., filtering task, col. 24, lines 27-31); and providing the processed machine data to an indexer or data store of the cloud computing service for performing subsequent searching, analysis, and/or data visualization (making processed data available to downstream systems/components, e.g., indexing system, col. 18, lines 20-25, col. 19, lines 26-41; storing processed data, col. 14, lines 30-38; providing querying, i.e., searching, dashboards, i.e., analysis, and visualizations, col. 127, lines 31-34).
Regarding claim 18, Abdul-Jawad disclosed a non-transitory computer-readable medium having stored instructions thereon (non-transitory computer-readable storage medium containing instructions, col. 159, lines 39-47) that, when executed by one or more processors, cause the one or more processors to perform operations including: obtaining machine data at an ingest processor from a forwarder that performs basic data processing of the machine data (intake system/streaming data processor, i.e., ingest processor, receiving, i.e., obtaining, data, col. 14, lines 64-65, col. 19, lines 35-38; receiving raw machine data, col. 15, lines 7-8; forwarder transmitting data to streaming data processor, col. 19, lines 26-37; forwarder tagging data, i.e., basic data processing, col. 20, lines 2-6), wherein the ingest processor performs machine data processing in a cloud computing service (processing data, col. 14, line 30-31, 64-66; cloud-based service, col. 17, line 41) and provides the processed machine data to another component for subsequent indexing or storage (making processed data available to downstream systems/components, e.g., indexing system, col. 18, lines 20-25, col. 19, lines 26-41; storing processed data, col. 14, lines 30-38); performing, at the ingest processor, advanced data processing to process the machine data, prior to indexing or storing the data, based on an advanced data processing pipeline executed on the ingest processor (intake system performing processing, i.e., advanced data processing, on data, col. 14, lines 65-66, col. 18, line 22, col. 19, lines 26-28; intake system including forwarder, col. 19, line 28-29; forwarder comprising pipelines, i.e., advanced data processing pipeline, col. 20, lines 11-13), wherein the advanced data processing pipeline uses advanced data processing content in a search language format to perform the advanced data processing, including a masking task, a noise reduction task, a filtering task, or a metricization task, that is different from the basic data processing performed at the forwarder (utilizing rules/model, i.e., advanced data processing content, to process data, col. 15, lines 14-15, col. 18, lines 31-33, col. 19, lines 35-38; processing pipeline using search language, i.e., search language format, col. 123, lines 12-34; streaming data processors processing messages to determine which topics to place messages, i.e., filtering task, col. 24, lines 27-31); and providing the processed machine data to an indexer or data store of the cloud computing service for performing subsequent searching, analysis, and/or data visualization (making processed data available to downstream systems/components, e.g., indexing system, col. 18, lines 20-25, col. 19, lines 26-41; storing processed data, col. 14, lines 30-38; providing querying, i.e., searching, dashboards, i.e., analysis, and visualizations, col. 127, lines 31-34).
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 JOSEPH R MANIWANG whose telephone number is (571)270-7257. The examiner can normally be reached 8:30AM - 4:30PM.
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, Wing F Chan can be reached at (571) 272-7493. 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.
/JOSEPH R MANIWANG/Primary Examiner, Art Unit 2453
Prosecution Insights