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 .
This is in response to Application filed 11/04/24. Claims 1 – 20 have been examined and are pending.
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 – 20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Hykes et al. US 20240078101 A1.
Regarding claim 1, 22 and 23, Hykes et al. anticipates a computer system / computer-implemented method / non-transitory computer-readable storage media storing one or more comprising:
a script automation processor (See Abstract, identical language, Note: Similar inventive entity different priority dates and not listed as continuing or co-pending application or parent case in App folder/contents and continuance information wrapper) and
a virtual compute instance and a virtual storage instance associated with one or more non-transitory computer-readable storage media storing one or more first sequences of instructions defining an API implementation of an API, a graph server, and one or more programming language runtime interpreters, and which, when executed using the virtual compute instance, cause the virtual compute instance to execute (See Abstract, identical language, Note: Similar inventive entity different priority dates and not listed as continuing or co-pending application or parent case and App folder).
obtaining access to a user pipeline automation script comprising one or more second sequences of instructions specifying one or more API calls to the API (See Abstract);
executing the script automation processor (See Abstract);
creating and storing one or more modules in one or more programming languages
from the user pipeline automation script, the one or more modules extending the API, wherein one or more of the modules are re-usable (See Abstract);
creating and storing one or more programmatic containers in memory of the script automation processor, the containers corresponding to the one or more modules;
creating and storing a directed acyclic graph (DAG) in the memory of the script
automation processor, the DAG comprising nodes and edges corresponding to dependencies of the containers interpreting each of the one or more modules using a particular programming
language runtime interpreter among the one or more programming language runtime
interpreters; and installing the one or more modules in association with the API implementation (See Abstract).
Regarding claim 2, the computer system of claim 1, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
generating a command line interface (CLI);
receiving, via the CLI, an initiation command configured to create a first module; and creating and storing the first module (See Abstract, identical language, Note: Similar inventive entity different priority dates and not listed as continuing or co-pending application or parent case and App folder).
Regarding claim 3, the computer system of claim 2, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a function calling command configured to execute a function associated with the first module; and executing the function associated with the first module in a programmatic container of the
one or more programmatic containers (See Abstract).
Regarding claim 4, the computer system of claim 2, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a modification command configured to modify the first module;
modifying the first module; and receiving, via the CLI, a synchronization command configured to reload the first module (See Abstract).
Regarding claim 5, the computer system of claim 2, a function associated with the first module being configured to take and return data objects associated with a plurality of types [0062].
Regarding claim 6, the computer system of claim 2, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
receiving, via the CLI, a module calling command configured to add a dependency of a
second module to the first module; executing the first module; and during the execution of the first module, calling and executing the second module [0027].
Regarding claim 7, the computer system of claim 2, wherein the first module is stored in two or more repositories, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a function calling command specifying a first repository of the two or more repositories [0141]; consuming the first module from the first repository; and executing the first module [0027].
Regarding claim 8, the computer system of claim 2, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute: receiving, via the CLI, a module publishing command specifying a repository to publish the first module; and
publishing the first module in the repository [0071 – 0074, shows writing to storage, also refer to virtual storage in 0027].
Regarding claim 9, the computer system of claim 2, wherein a first function is associated with the first module, wherein the first function is configured to return custom objects defining one or more second functions [0147].
Regarding claim 10, the computer system of claim 9, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
receiving, via the CLI, a function calling command configured to execute the first function; executing the first function; and during the execution of the first function, calling and executing the one or more second functions [0027].
Regarding claim 11, the computer system of claim 1, wherein at least a first function is associated with a first module of the one or more modules, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
executing the first function; and instantiating and returning one or more services from the first function [0025].
Regarding claim 12, the computer system of claim 11, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
creating and storing one or more programmatic service containers in memory of the script automation processor, the service containers corresponding to the one or more services [0025 – 0027].
Regarding claim 13, the computer system of claim 12, wherein each of the service containers comprises a service hostname configured for querying the corresponding service container [0027].
Regarding claim 14, the computer system of claim 12, wherein each of the service containers comprises one or more ports configured to expose the corresponding service to a host [0027].
Regarding claim 15, the computer system of claim 14, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
receiving, via one or more of the ports, a request to use the first service from a client on
the host; and executing the first service [0046 – 0047].
Regarding claim 16, the computer system of claim 12, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
binding a first service of the services executing in a first service container of the service
container to a client container; and automatically starting the first service when the client container executes [0027].
Regarding claim 17, the computer system of claim 12, wherein a first service of the services executes on a host, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
binding a first container of the containers to the first service; executing the user pipeline automation script to automatically build, test, or deploy a user application in a cloud computing service; and during the executing of the user pipeline automation script, querying the first service by the first container [0027].
Regarding claim 18, the computer system of claim 12, the script automation processor further comprising the first sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute creating and storing, in the DAG, nodes corresponding the services and edges corresponding to bindings associated with the services [0027].
Regarding claim 19, the computer system of claim 1, the script automation processor further comprising two or more programming language runtime interpreters, wherein each programming language runtime interpreter among the two or more programming language runtime interpreters is programmed to interpret a different programming language used in each of the one or more modules [0027].
Regarding claim 20, the computer system of claim 1, wherein the script automation processor further comprises the second sequences of instructions which, when executed using the virtual compute instance, cause the virtual compute instance to execute:
executing the user pipeline automation script to automatically build, test, or deploy a user application in a cloud computing service; and during the executing, based on the user pipeline automation script, invoking one or more of the one or more modules as part of automatically building, testing, or deploying the user application in the cloud computing service [0027].
Regarding claim 21, the computer system of claim 1, wherein the user pipeline automation script further comprises at least one reference to a software development kit (SDK), and wherein the script automation processor comprises an SDK interface responsive to function invocations via the at least one reference [0027].
Correspondence Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Chuck Kendall whose telephone number is 571-272-3698. The examiner can normally be reached on 10:00 am - 6:30pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Hyung Sough can be reached on 571-272-6799. 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 [0060 – 0080].
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).
/CHUCK O KENDALL/
Primary Examiner, Art Unit 2192
Prosecution Insights