DETAILED ACTION
This application has been examined. Claims 1-5,7-12,14-19 are pending. Claims 6,13,20 are cancelled.
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 .
Making Final
Applicant's arguments filed 4/28/2026 have been fully considered but they are moot in view of the new grounds for rejection.
The claim amendments regarding -- ‘a second cloud service by the cloud service provider’ -- clearly change the literal scope of the independent and dependent claims and/or the range of equivalents for such claims. The said amendments alter the scope of the claims but do not overcome the disclosure by the prior art as shown below.
The Examiner is presenting new grounds for rejection as necessitated by the claim amendments and is thus making this action FINAL.
Response to Arguments
Applicant's arguments filed 4/28/2026 have been fully considered but they are moot in view of the new grounds for rejection.
Kulkarni disclosed (re. Claim 1) wherein the first set of functions is provided as a first cloud service by a cloud service provider (Kulkarni-Paragraph 177, data intake and query system 108 can be…cloud-based service)
While Kulkarni substantially disclosed the claimed invention Kulkarni does not disclose (re. Claim 1) a second cloud service by the cloud service provider.
Ead Figure 7,Paragraph 168 disclosed a first cloud services provider (e.g., OCI) 710 and a second cloud environment provided by a second cloud services provider 720 (e.g., AWS). The first cloud environment 710 includes a multi-cloud infrastructure that provisions for capabilities to deliver services of the first cloud environment to users of other cloud environments (e.g., the second cloud environment 720).
Ead disclosed (re. Claim 1) a second cloud service by the cloud service provider.(Ead-Figure 7,Paragraph 168,a first cloud services provider (e.g., OCI) 710 and a second cloud environment provided by a second cloud services provider 720 (e.g., AWS). The first cloud environment 710 includes a multi-cloud infrastructure that provisions for capabilities to deliver services of the first cloud environment to users of other cloud environments (e.g., the second cloud environment 720).)
Kulkarni and Ead are analogous art because they present concepts and practices regarding cloud monitoring services. Before the time of the effective filing date of the claimed invention it would have been obvious to combine Ead into Kulkarni. The motivation for the said combination would have been to enable a user experience as close as possible to that of the native cloud environments of the users (e.g., the second cloud environment 720), while providing simple integration between the cloud environments.(Ead-Paragraph 169)
Kulkarni-Ead disclosed (re. Claim 1) wherein the second set of functions is provided as a second cloud service by the cloud service provider, (Ead-Figure 7,Paragraph 168,a first cloud services provider (e.g., OCI) 710 and a second cloud environment provided by a second cloud services provider 720 (e.g., AWS). The first cloud environment 710 includes a multi-cloud infrastructure that provisions for capabilities to deliver services of the first cloud environment to users of other cloud environments (e.g., the second cloud environment 720).) wherein the first cloud service and the second cloud service are services that can be subscribed to by one or more customers of the cloud service provider.(Kulkarni-Paragraph 177, a user may pay a subscription or other fee to use such a service. Each subscribing user of the cloud-based service)
Priority
The effective date of the claims described in this application is November 8, 2024.
Claim Rejections - 35 USC § 103
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.
Claim(s) 1-5,7-12,14-19 is/are rejected under 35 U.S.C. 103 as being unpatentable over Kulkarni (USPGPUB 2023/0385288) further in view of Ead (USPGPUB 2024/0129285)
Regarding Claim 1
Kulkarni Figure 35, Paragraph 135 disclosed wherein the data intake and query system receives machine data from any type and number of sources (e.g., one or more system logs, streams of network packet data, sensor data, application program data, error logs, stack traces, system performance data, etc.). The system parses the machine data to produce events each having a portion of machine data associated with a timestamp. The system stores the events in a data store. The system enables users to run queries against the stored events to, for example, retrieve events that meet criteria specified in a query, such as criteria indicating certain keywords or having specific values in defined fields.
Kulkarni disclosed (re. Claim 1) a method comprising: receiving, at a first system, a request from a user for a particular metric computed by a second system; (Kulkarni-Figure 35,Paragraph 164, execute queries on the data in response to requests received from the client devices 204.)
generating, by the first system, a request requesting the particular metric and associated data, (Kulkarni-Paragraph 135, enables users to run queries against the stored events to, for example, retrieve events that meet criteria specified in a query, such as criteria indicating certain keywords or having specific values in defined fields,Paragraph 747, performance metrics can include: (1) CPU-related performance metrics; (2) disk-related performance metrics; (3) memory-related performance metrics; (4) network-related performance metrics) the request further including information identifying the user, (Kulkarni-Paragraph 269, search manager 514 that has parsed a query to identify the following filter criteria that is used to identify the data to be processed: time range: past hour, partition: _sales, tenant: ABC, Inc.) wherein the request is generated in a format that is understandable by the second system; (Kulkarni-Paragraph 139, system facilitates use of a “common information model” (CIM) across the disparate data sources, Paragraph 205, transformation may include modifying data within the message, such as altering a format in which the data is conveyed)
communicating, by the first system, the request to the second system; (Kulkarni-Paragraph 289, search manager 514 can ping or set up a communication link between it and the search nodes 506 assigned to execute the query.)
responsive to the communicating, receiving, by the first system and from the second system, the requested particular metric and the associated data; (Kulkarni-Paragraph 135,the data intake and query system receives machine data from any type and number of sources (e.g., one or more system logs, streams of network packet data, sensor data, application program data, error logs, stack traces, system performance data )
transforming, by the first system, the particular metric and the associated data to a format that is consumable by a dashboard generation system of the first system; (Kulkarni-Paragraph 365, generation of a message may include converting a format of the data into a format suitable for publishing on the intake ingestion buffer 306.)
generating, by the dashboard generation system of the first system, a dashboard for displaying the particular metric and the associated data; and causing, by the first system, the generated dashboard to be displayed on a display device.(Kulkarni-Figure 33D,Paragraph 46, user interface displaying both log data and performance data)
Kulkarni disclosed (re. Claim 1) wherein the first set of functions is provided as a first cloud service by a cloud service provider (Kulkarni-Paragraph 177, data intake and query system 108 can be…cloud-based service)
While Kulkarni substantially disclosed the claimed invention Kulkarni does not disclose (re. Claim 1) a second cloud service by the cloud service provider.
Ead Figure 7,Paragraph 168 disclosed a first cloud services provider (e.g., OCI) 710 and a second cloud environment provided by a second cloud services provider 720 (e.g., AWS). The first cloud environment 710 includes a multi-cloud infrastructure that provisions for capabilities to deliver services of the first cloud environment to users of other cloud environments (e.g., the second cloud environment 720).
Ead disclosed (re. Claim 1) a second cloud service by the cloud service provider.(Ead-Figure 7,Paragraph 168,a first cloud services provider (e.g., OCI) 710 and a second cloud environment provided by a second cloud services provider 720 (e.g., AWS). The first cloud environment 710 includes a multi-cloud infrastructure that provisions for capabilities to deliver services of the first cloud environment to users of other cloud environments (e.g., the second cloud environment 720).)
Kulkarni and Ead are analogous art because they present concepts and practices regarding cloud monitoring services. Before the time of the effective filing date of the claimed invention it would have been obvious to combine Ead into Kulkarni. The motivation for the said combination would have been to enable a user experience as close as possible to that of the native cloud environments of the users (e.g., the second cloud environment 720), while providing simple integration between the cloud environments.(Ead-Paragraph 169)
Kulkarni-Ead disclosed (re. Claim 1) wherein the second set of functions is provided as a second cloud service by the cloud service provider, (Ead-Figure 7,Paragraph 168,a first cloud services provider (e.g., OCI) 710 and a second cloud environment provided by a second cloud services provider 720 (e.g., AWS). The first cloud environment 710 includes a multi-cloud infrastructure that provisions for capabilities to deliver services of the first cloud environment to users of other cloud environments (e.g., the second cloud environment 720).) wherein the first cloud service and the second cloud service are services that can be subscribed to by one or more customers of the cloud service provider.(Kulkarni-Paragraph 177, a user may pay a subscription or other fee to use such a service. Each subscribing user of the cloud-based service)
Regarding Claim 8
Claim 8 (re. device) recites substantially similar limitations as Claim 1. Claim 8 is rejected on the same basis as Claim 1.
Regarding Claim 15
Claim 15 (re. non-transitory computer-readable medium) recites substantially similar limitations as Claim 1. Claim 15 is rejected on the same basis as Claim 1.
Regarding Claim 2,9,16
Kulkarni-Ead disclosed (re. Claim 2,9,16) establishing a communication channel between the first system and the second system; and wherein the communicating comprises communicating the request via the communication channel.(Kulkarni-Paragraph 289, search manager 514 can ping or set up a communication link between it and the search nodes 506 assigned to execute the query.)
Regarding Claim 3,10,17
Kulkarni-Ead disclosed (re. Claim 3,10,17) wherein receiving the particular metric and the associated data by the first system and from the second system comprises: streaming, by the second system, the particular metric and the associated data to the first system via the communication channel.(Kulkarni-Paragraph 555, intake system 210 may receive a data stream from a log file generated by an application server, from a stream of network data from a network device)
Regarding Claim 4,11,18
Kulkarni-Ead disclosed (re. Claim 4,11,18) wherein the associated data comprises a metric type (Kulkarni-Paragraph 747, performance metrics can include: (1) CPU-related performance metrics; (2) disk-related performance metrics; (3) memory-related performance metrics; (4) network-related performance metrics) , a metric name, a metric source, and a metric time.(Kulkarni-Paragraph 675, Search screen 2400 includes a search bar 2402 that accepts user input in the form of a search string. It also includes a time range picker 2412 that enables the user to specify a time range for the search.)
Regarding Claim 5,12,19
Kulkarni-Ead disclosed (re. Claim 5,12,19) wherein the first system performs a first set of functions comprising: receiving a plurality of logs from a monitored system, the plurality of logs comprising one or more of application logs data, system logs data, security logs data, network logs data, audit logs data, and database logs data; (Kulkarni-Paragraph 135, data intake and query system receives machine data from any type and number of sources (e.g., one or more system logs, streams of network packet data, sensor data, application program data, error logs, stack traces, system performance data)
wherein the second system performs a second set of functions comprising: receiving observability data for the monitored system, the observability data comprising measurements of the monitored system; (Kulkarni-Paragraph 135, enables users to run queries against the stored events to, for example, retrieve events that meet criteria specified in a query, such as criteria indicating certain keywords or having specific values in defined fields,Paragraph 747, performance metrics can include: (1) CPU-related performance metrics; (2) disk-related performance metrics; (3) memory-related performance metrics; (4) network-related performance metrics) and generating a set of one or more metrics based on the received observability data, the set of one or more metrics comprising the particular metric.(Kulkarni-Paragraph 745, operational visibility into granular performance metrics )
Regarding Claim 7,14
Kulkarni-Ead disclosed (re. Claim 7,14) storing, at the first system, an access token generated upon successful single sign on of the user into the second system via the first system; and wherein communicating the request from the first system to the second system comprises communicating the access token from the first system to the second system.(Ead-Paragraph 177, Each request includes a token associated with the account of the user in the second cloud infrastructure. The proxy module extracts the token and validates the token in conjunction with access control module 723B (i.e., the identity provider system of the second cloud environment). Upon successful validation, the proxy module 712A may check roles (i.e., set of privileges) associated with the user.)
Conclusion
Examiner’s Note: In the case of amending the claimed invention, Applicant is respectfully requested to indicate the portion(s) of the specification which dictate(s) the structure relied on for proper interpretation and also to verify and ascertain the metes and bounds of the claimed invention.
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 GREG C BENGZON whose telephone number is (571)272-3944. The examiner can normally be reached on Monday - Friday 8 AM - 4:30 PM.
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, John Follansbee can be reached on (571) 272-3964. 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.
/GREG C BENGZON/ Primary Examiner, Art Unit 2444
Prosecution Insights