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 .
Information Disclosure Statement
The information disclosure statement (IDS) submission is in compliance with the provisions of 37 CFR 1.97. Accordingly, the information disclosure statement is being considered by the examiner.
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP §§ 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-20 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1, 3-16 and 18-22 of copending Application No. 18342825, in view of OSWAL (US 20240028605 A1). This is a provisional nonstatutory double patenting rejection.
Instant Application
Application No. 18342825
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
obtain one or more rendering workloads from a client; and
obtain one or more rendering workloads from a client; and
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, wherein the plurality of computing platforms comprises at least one client computing platform and at least one cloud computing platform, and
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
wherein the automatically managing execution of the one or more rendering workloads further comprises utilizing one or more estimations to determine an execution plan for the one or more rendering workloads prior to execution.
perform, prior to execution of the one or more rendering workloads, a compliance evaluation operation corresponding to at least one compliance attribute associated with execution of the one or more rendering workloads;
Claim 4. … compute the one or more estimations using at least one of a coarse estimation stage and a fine estimation stage based on one or more of a rendering application type, a resource scoring metric, and one or more specifications associated with the one or more rendering workloads.
send, to the client, a set of one or more candidate execution plans responsive to the compliance evaluation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms;
Claim 6. The apparatus of claim 1, wherein the execution plan comprises a plurality of execution levels based on an attribute computed for the one or more estimations.
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
Claim 14. The apparatus of claim 1, wherein the at least one processing device, when automatically managing execution of the one or more rendering workloads is further configured to: apply one or more security protocols in accordance with the execution of the one or more rendering workloads.
Claims 1, 3-16 and 18-22 of copending Application No. 18342825 do not disclose receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans. However, in the same field of endeavor, OSWAL (US 20240028605 A1) discloses receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans ([0039] “After selecting an optimal execution plan for a query, coordinator node 150 obtains and executes the execution plan, in an embodiment.”). It would have been obvious to one of ordinary skill in the art before the effective filing date of the invention to have modified the Claims 1, 3-16 and 18-22 of copending Application No. 18342825 with the feature of receive from the client an indication of a selection of at least one execution plan from the set of one or more candidate execution plans. Doing so could allow the optimal plan to be selected and executed, as taught by OSWAL.
Claims 1-20 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of copending Application No. 18926613. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-20 of instant application are anticipated by claims 1-20 of copending Application No. 18926613. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented.
Claims 1-20 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of copending Application No. 18926583. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-20 of instant application are anticipated by claims 1-20 of copending Application No. 18926583. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented.
Claims 1-20 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of copending Application No. 18926598. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-20 of instant application are anticipated by claims 1-20 of copending Application No. 18926598. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented.
Instant Application
Application No. 18926613
Application No. 18926583
Application No. 18926598
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
obtain one or more rendering workloads from a client; and
obtain one or more rendering workloads from a client; and
obtain one or more rendering workloads from a client; and
obtain one or more rendering workloads from a client; and
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
perform, prior to execution of the one or more rendering workloads, a compliance evaluation operation corresponding to at least one compliance attribute associated with execution of the one or more rendering workloads;
perform, prior to execution of the one or more rendering workloads, an estimation operation corresponding to at least one execution attribute associated with the one or more rendering workloads;
perform, prior to execution of the one or more rendering workloads, an estimation operation corresponding to at least one execution attribute associated with the one or more rendering workloads, wherein the estimation operation evaluates a resource utilization associated with at least one adjustment to a resolution of at least a portion of at least one of the one or more rendering workloads;
perform, prior to execution of the one or more rendering workloads, an estimation operation corresponding to at least one execution attribute associated with the one or more rendering workloads, wherein the estimation operation evaluates a resource utilization associated with embedding at least one digital watermark in at least a portion of one or more of the rendering workloads;
send, to the client, a set of one or more candidate execution plans responsive to the compliance evaluation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms;
send, to the client, a set of one or more candidate execution plans responsive to the estimation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms, wherein at least one of the one or more candidate execution plans is generated based at least in part on one or more execution criteria for the one or more rendering workloads, wherein at least one value of one or more of the execution criteria is generated by at least one language model based at least in part on at least one input from the client;
send, to the client, a set of one or more candidate execution plans responsive to the estimation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms;
send, to the client, a set of one or more candidate execution plans responsive to the estimation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms;
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
Features in claims 2-20 are taught by or rendered obvious by claims 2-20 of Application No. 18926613, claims 2-20 of Application No. 18926583, and claims 2-20 of Application No. 18926598.
Claims 1-20 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of copending Application No. 18926944. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-20 of instant application are anticipated by claims 1-20 of copending Application No. 18926944. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented.
Claims 1-20 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of copending Application No. 18926660. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-20 of instant application are anticipated by claims 1-20 of copending Application No. 18926660. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented.
Claims 1-20 are provisionally rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of copending Application No. 18915683. Although the claims at issue are not identical, they are not patentably distinct from each other because claims 1-20 of instant application are anticipated by claims 1-20 of copending Application No. 18915683. This is a provisional nonstatutory double patenting rejection because the patentably indistinct claims have not in fact been patented.
Instant Application
Application No. 18926944
Application No. 18926660
Application No. 18915683
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
1. An apparatus comprising: at least one processing device comprising a processor coupled to a memory, the at least one processing device, when executing program code, is configured to:
obtain one or more rendering workloads from a client; and
obtain one or more rendering workloads from a client; and
obtain one or more rendering workloads from a client; and
obtain one or more rendering workloads from a client; and
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
automatically manage execution of the one or more rendering workloads in accordance with at least a subset of resources of a plurality of computing platforms, the plurality of computing platforms comprising at least one client computing platform and at least one cloud computing platform;
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
wherein, when automatically managing execution of the one or more rendering workloads, the at least one processing device is further configured to:
perform, prior to execution of the one or more rendering workloads, a compliance evaluation operation corresponding to at least one compliance attribute associated with execution of the one or more rendering workloads;
perform, prior to execution of the one or more rendering workloads, an estimation operation corresponding to at least one execution attribute associated with the one or more rendering workloads, wherein the estimation operation evaluates a resource utilization associated with at least one adjustment to a resolution of one or more identified regions of at least one of the one or more rendering workloads;
perform, prior to execution of the one or more rendering workloads, a security evaluation operation corresponding to at least one security attribute associated with execution of the one or more rendering workloads;
perform, prior to execution of the one or more rendering workloads, an estimation operation corresponding to at least one execution attribute associated with the one or more rendering workloads, wherein the estimation operation comprises at least one machine learning algorithm;
send, to the client, a set of one or more candidate execution plans responsive to the compliance evaluation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms;
send, to the client, a set of one or more candidate execution plans responsive to the estimation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms;
send, to the client, a set of one or more candidate execution plans responsive to the security evaluation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms;
send, to the client, a set of one or more candidate execution plans responsive to the estimation operation, wherein each candidate execution plan corresponds to a different subset of resources of the plurality of computing platforms;
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
receive, from the client, an indication of a selection of at least one execution plan from the set of one or more candidate execution plans; and
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
cause the at least one selected execution plan to be implemented to enable execution of the one or more rendering workloads.
Features in claims 2-20 are taught by or rendered obvious by claims 2-20 of Application No. 18926944, claims 2-20 of Application No. 18926660, and claims 2-20 of Application No. 18915683.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure:
Cheng (US 9727608 B2) – this reference discloses techniques for generating statistical views in a database system. In one embodiment, a request is received to execute a database workload. One or more constraints pertaining to executing the database workload is retrieved. The database workload is evaluated to generate multiple statistical view candidates. The statistical view candidates are refined based on the one or more constraints. One or more statistical views are then generated based on the refined statistical view candidates.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to CHONG WU whose telephone number is (571)270-5207. The examiner can normally be reached MON-FRI: 9AM-5PM EST.
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, Xiao Wu can be reached at 571-272-7761. 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.
/CHONG WU/Primary Examiner, Art Unit 2613
Prosecution Insights