Patent Grant
10341194
This disclosure relates generally to cloud based computing environments in which a user is able to specify a desired infrastructure using a programming language configured to interface with an cloud environment operating system (OS). The computing environments can be configured to simultaneously support multiple users, wherein each user being able to operate against one or more cloud based environments. Once the computing infrastructure has been specified, the cloud environment operating system can build the desired infrastructure in the specified cloud service, optimize the infrastructure based on conditions encountered in the cloud computing environment, and enforce desired infrastructure specifications in real-time.
Cloud computing allows individuals, businesses, and other organizations to implement and run large and complex computing environments without having to invest in the physical hardware (such as a server or local computer) necessary to maintain such environments. Rather than having to keep and maintain physical machines that perform the tasks associated with the desired computing environment, an end-user can instead “outsource” the computing to a computing “cloud” that can implement the desired computing environment in a remote location. The cloud can consist of a network of remote servers hosted on the internet that are shared by numerous end-users to implement each of their desired computing needs. Simplifying the process to build, optimize, and maintain computing environments on the cloud can lead to a positive end-user experience. Allowing a user to develop a robust computing infrastructure on the cloud, while seamlessly optimizing and maintain it, can minimize frustrations associated with corrupted infrastructure that can occur during the course of operating a computing environment on the cloud.
This disclosure relates to a cloud environment operating system that accepts a user-defined computing environment infrastructure specification, produces and optimizes the software modules necessary to build the infrastructure, and continuously works to maintain the infrastructure according to the user's specification during operation of the computing environment on the cloud. By continuously maintaining the specified infrastructure during operation, the cloud environment operating system can minimize infrastructure corruption that can occur over time.
A cloud computing system (“cloud”) is a large distributed computer that is shared by multiple clients and is used to virtualize computing environments thereby liberating end-users from the burdens of having to build and maintain physical information technology infrastructure at a local site.
The cloud 106, as previously discussed, is one or more distributed generalized computers that provide the computing resources to a user to allow them to implement their desired computing environment. Commercial cloud computing services such as Amazon™ web services, Microsoft Azure™, Google Cloud Platform™, are examples of distributed computer networks (clouds) available to users (for a fee) that allow them to build and host applications and websites, store and analyze data, among other uses. Clouds are scalable, meaning that the computing resources of the cloud can be increased or decreased based on the real-time needs of a particular user. In one example, a cloud 104 can be utilized to implement a website run by a user 102. The cloud 106 can maintain and operate a web-server based on the specifications defined by the user 102. As web-traffic to the website increases, the cloud can increase the computing resources dedicated to the website to match the surge in traffic. When web traffic is sparse, the cloud 106 can decrease the computing resources dedicated to the website to match the decrease in traffic. Cloud service providers can implement computing environments in “user accounts,” maintained and operated by the cloud service provider. Thus the computing environment of a first user can be implemented in a first user account, while the computing environment of a second user can be implemented in a second account. In some embodiments, a single user can maintain separate accounts for separate computing environments that they wish to implement and maintain. A Cloud Service Provider offers the infrastructure services that allow users to implement infrastructure “environments” in their CSP user accounts through those infrastructure services. For example, the VPC AWS Service allows one to create, modify, and delete a VPC.
An cloud environment operating system (OS) 104 can help to facilitate the interaction between a user 102 and a cloud computing environment 106. A conventional operating system manages the resources and services of a single computer. In contrast, an cloud environment operating system manages the resources and services of a cloud.
An cloud environment operating system can automate the creation and operation of one or more cloud infrastructures and can create and destroy computing instances on one or more cloud service providers. While the example of
An cloud environment operating system 104 can interface with a user 102 by allowing the user to specify a desired computing infrastructure in a simplified and concise manner. In one example, a user 102 can specify a computing environment using a programming language designed to interface with the cloud environment operating system 104.
At step 202 a user can provide a declaration of the infrastructure to be built on the cloud service provider. As an example, the user, using a pre-defined programming language, can specify the components within the infrastructure, the specifications of each component, and the types of communication that each component within the infrastructure has with each other.
In one example, at step 202, a user can provide a declaration of the infrastructure to be built on the cloud service provider utilizing a domain-specific programming language configured to allow a user to express infrastructure elements and relationships concisely in a text-based format. In additional examples, the domain-specific language can allow for comments to be expressed in-line with other content, thus allowing for the understanding and maintenance of content over time. Additionally, the domain specific-language can include pre-defined concepts (i.e., service types) that can enable the user of the cloud environment operating system to reference or use the concepts without having to define them themselves. Additionally, the domain specific language can allow for a user to define their own types, functions, and modules if desired. In some examples, the domain-specific language can include pre-defined libraries that can encompass definitions of cloud infrastructure elements, which can allow for code reuse, and thus reduce overall development effort. Finally, in one or more of the examples described above, the domain-specific language described above can be run through a compile, so as to identify problems in the user's specification of the cloud computing environment. This can lead to shorter feedback cycles, that can potentially be reduce costs by ascertaining problems with a cloud computing environment specification before consuming or instantiating a cloud-based service to develop computing infrastructure.
Referring back to
At step 204, the user's declarations generated at step 202 can be compiled. The compiler can include multiple libraries that provide meaning to the declarations that the user generated at step 202. For instance the libraries can include information about the cloud environment operating systemcloud environment operating system that is to be accessed, the cloud service on which the infrastructure is to be build (i.e., Google, Amazon, Microsoft) and information about the different components that can be created using the programming language.
Finally, at step 206, the compiled program code can be sent to the cloud environment operating system 104 for further processing. In some examples, the code compiled at step 204 and transmitted at step 206 is not a complete program ready to be executed by the cloud 106, but rather can be a code that contains numerous omissions to be later filled in by the cloud environment operating system 104. These “omissions” can be later be parsed by the cloud environment operating system and resolved based on the cloud service provider that is to be used in implementing the computing infrastructure. The compiled program code generated at step 204 can contain a terse, machine-friendly, but less user-friendly syntax. In this way, the programming language used in the example of
The syntax used by the programming language can be generic. In other words the syntax does not have to be tailored to work with any particular cloud service provider such as Amazon, Google, etc. Instead, a user can specify generic infrastructure and the cloud environment operating system as further discussed below can implement the generic declaration into a series of instructions that are understood by the cloud service provider being utilized. In some embodiments, the cloud environment operating system can determine which cloud service provider to implement the infrastructure on based on the specification of the infrastructure provided by the user. Referring back to
A user can also declare the infrastructure in a syntax that is germane to the cloud service provider that is ultimately be utilized. For instance, if a user knows that they want to utilize Microsoft's Azure platform, the user can generate declarations of the communication path between A and C in a syntax that is specific to the Azure cloud platform.
In addition to creating infrastructure for a cloud, the user can also save previously created infrastructures as libraries within the coding platform. In one example, if a user in the past created a database server infrastructure, they can save that infrastructure as a library. Then in the future, if the user wishes to create a computing environment that utilizes a database server, rather than create a new database server, the user can simply call upon the library in which the database server infrastructure is already stored and utilize it in the computing environment that is currently being created. In this way, the user can define re-usable infrastructure that can be applied to the creation of future infrastructure on a cloud based computing platform.
At step 404 the composition generated by the user can be sent to a handler. The handler can capture and version the composition and determine if the composition drafted by the user is a new build (i.e., generating a new computer infrastructure from scratch) or an update to a previously existing infrastructure already running on the cloud. Once the handler receives the composition and makes the determinations described above, it can then trigger the build process by sending the composition to a planning stage.
At step 406, the composition can be passed from the handler stage to planner stage wherein the composition generated by the user is run through a series of modules (described in further detail below) that convert it into a series of instructions to be sent to a builder that will ultimately build the infrastructure in the cloud. The planner stage in addition to interpreting the language of the composition can also perform operations on the composition to determine whether or not there are any errors or structural faults with the composition as written by the user.
The planner 406 can transmit the instructions created from the composition to a builder. The builder at step 408 can take the instructions and build, update, or destroy the infrastructure specified by the user in the specified cloud.
At step 410, the cloud can run the infrastructure specified by the builder in step 408. As the cloud is running the specified infrastructure, should any errors occur in the operation of the infrastructure, the cloud can notify a watcher algorithm at step 412 which can then trigger a rebuild at the handler step 404 of the components of the infrastructure that have generated the error.
Block 502 can represent the user process that occurs before operation of the cloud environment operating system as described above with respect to
Block 504 can represent a lobby server. Lobby server 504 can receive low level code (otherwise known as a command line interface) from one or more users and performs a “pitch and catch process” that receives code from one or more users and unpacks it (i.e., distill the parts of the code that will interface with the cloud environment operating system) and stores any data (at storage unit 508) that is needed to compile the code and routes the information that comes from the user to the appropriate modules within the cloud environment operating system. In addition, the lobby server 504 can identify all of the processes associated with a particular user's command line interface and apply process “tags” to those processes. The process tags can allow the cloud environment operating system to track where in the system the processes are currently being executed. This feature can allow for simplicity in scheduling management as will be discussed further below.
The lobby server 504 can also handle external data requests. If a request is made to the cloud environment operating system for certain forms of data about the run-time environment of the cloud environment operating system, the lobby server 504 is able to receive the request, execute it, and send the acquired data to the appropriate stake holder.
Once the code received from the user has been processed by the lobby server 504, the processed code can then be sent to process manager 506. The process manager 506 can manage a process table 510 which lists each and every process to be run by the cloud environment operating system. In other words, one set of instructions to build a particular infrastructure by a particular user can be handled as a process. Another set of instructions to build infrastructure by another user can be handled as a separate process. The process manager 506 can manage each separate user's tasks as a processes within the system by assigning it a process ID and tracking the process ID through the system. Each user's individual tasks to be executed by the cloud environment operating system can be managed as separate entities. In this way, the process manager 506 can enable the cloud environment operating system to operate as a “multi-tenant” system as opposed to a single-user system. In other words, multiple users can implement multiple computing environments via single instance of a cloud environment operating system. The cloud environment operating system can handle requests for infrastructure from multiple users simultaneously rather than being dedicated to a single user or single machine.
In addition to the functions described above, the process manager 506 can also perform status checks on the implementation of the infrastructure in the cloud. In pre-determined time intervals, the process manager 506 can initiate a process whereby a signal is sent to the query manager 522 to determine the status of the infrastructure in the cloud. The query manager 522 can determine the status of the user's infrastructure and send commands to the interpreter manager 512 to take action (described further below) if it is determined from the query manager that the user's infrastructure specification does not match infrastructure present on the cloud.
Once the process manger identifies the process to be executed on the cloud environment operating system and stores the processes on process table 510, it can then send those processes to the Interpreter Manager 512 to be converted into a set of instructions that can ultimately be executed by the cloud.
The interpreter manager 512 can be responsible for converting the user's command line interface language (i.e., high level declaration) into a series of specific instructions that can be executed by the cloud environment operating system. The interpreter manager 512 can achieve this by employing a series of planning modules 514 that accept, in some examples, resource tables at its input and generates resource tables in which any omissions in the syntax provided by the user are filled in. The interpreter manager 512 can review a resource table sent by the user and send it to the series of planning modules 514 based on what infrastructure needs have been declared by the user. The planning modules 514 alter the user's resource table and return it to the interpreter manager 512. This process may be repeated with other planning modules until the final correct version of the resource table is complete. The interpreter manager 512 then converts the resource table into a machine instruction file which can be referred to as a low level declaration of the computer infrastructure to be built on the cloud. The low level declaration is then sent to the builder/driver 516 (discussed in detail below).
Each planning module 602 can accept at its input the code received by the user 600 expressed a resource table, and can return a resource table that is more specific and complete filling in any omissions in the resource table that were present when it was inputted. In one example, the code from the user is input into a first planning module 602 that returns a resource table that is then inputted into a second module. The output of the second module is then inputted into a third module, etc., etc.
The use of modules to convert a user's command line interface language into instructions for a cloud can also allow for ease in defining new types of infrastructure previously not available on the cloud environment operating system. In one example, if a load balancer was not an infrastructure type supported by the cloud environment operating system, a user could simply create a library in the programming language on the user side that supports the declaration of a load balancer. In order for the cloud environment operating system to support the “new” load balancer, a new module could be created that provides the logic for handling load balancer infrastructure types. In this way, the modular nature of the interpreter manager 512 allows for ease in adding new infrastructure types.
Returning to
The order in which the code is processed through the modules 602 can vary. For instance in one example, the code can be processed sequentially through each module in a pre-defined order. In another example, the code can be processed in an order that depends on dependencies between the modules 602. For instance, one module may depend on the result of another module before it can process the code. In this instance, the module that is dependent on the result of another module can wait until completion of the module it is dependent on to finish before beginning its' processing.
After the code provided by the user is processed through the modules 602, it can finally be sent to a final module 604 for final processing. Final module 604 can be responsible for finalizing the resource table to be prepared for conversion into a series of instructions that can be understood by the cloud. Ultimately the pipeline of modules 602 and 604 create a low level code that is free from the abstractions and omissions previously present at the higher level language provided by the user. Finally, module 604 can also determine whether all of the abstractions and omissions have been resolved by the modules 602. If it is determined that not all omissions and abstractions have been resolved, final module 604 can run the resource tables back through the modules and repeat the process until each and every resource table has been completed.
In addition to a language interpretation function, in which the modules 602 interpret language from a user into a lower level language to be executed by the cloud, each module can also perform one or more run-time operations. As an example, the modules can run a de-bugging operation. When a high level declaration is received from a user, a dry run through the modules can be performed in which the code is run through module-by-module to ensure that there are no errors in the code such as those caused by typos or other operator error. If an error is found, the interpreter manager 512 can notify the user of the error.
In contrast, a cloud environment operating system without this capability would instead parse the code from the user and pass a series of instructions to the cloud. Once the cloud begins to implement the series of instructions, it may then encounter an error and ultimately not generate the desired infrastructure. The user may not become aware of the error until much later in the process which can waste time and resources. Instead the cloud environment operating system, through the interpreter manager 512, can detect these errors earlier in the process chain such that they can be corrected further upstream in the process.
Another example of a run-time operation performed by the modules is that each module is able to communicate to resources external to the cloud environment operating system in order to resolve omissions and abstractions from the user's code. For instance in one example, if the user level code requires the most update-to-date version of a component of the infrastructure, the modules 602 can communicate with an external configuration management system to provide that up-to-date component.
The planning modules 514 discussed above can adjust a user's infrastructure in response to conditions of the infrastructure after it has already been implemented on the cloud. As discussed above, process manager 506, after a pre-defined time period, can query the status of the infrastructure via a query manager 522. The status of the infrastructure can then be sent by the process manager to interpreter manager 512. Interpreter manager 512, via the planning modules 514, can compare the specification of the infrastructure as specified by the user with the current status of the infrastructure. If a difference is found between the specification of the infrastructure by the user and its current state on the cloud, the planning modules 514 can generate code to correct the infrastructure on the cloud so that it conforms to what the user specified.
At step S704 the interpreter manager 512 can generate a completed resource table based on the specified infrastructure to be built by the user. As will be discussed further below, the completed resource table can be sent to a Builder/Driver 516 to be converted into a series of instructions that will be executed by the cloud.
At step S706, the interpreter builder 512 can receive a status of the infrastructure already built from query manager 522. As discussed above, query manager 522 can be prompted by the process manager 506 in pre-determined time intervals to return a status of the infrastructure.
At step S708 the interpreter manager 512 can compare the current status of the infrastructure on the cloud as provided by the query manager 522 with the declaration of the infrastructure provided by the user at S702. If there are no differences between the declared infrastructure and the current status of the infrastructure, the process can return to step S706 to await the next status update from the query manager 522.
If however, there is a difference between the current status of the infrastructure, the planning modules 514 of interpreter manager 512 can be employed to generate resource table updates that can be passed to the cloud via builder/driver 516 so as to ensure that the infrastructure on the cloud is conformed to the original declaration of the infrastructure by the user.
Once the infrastructure on the cloud has been modified according the user's declaration, the process can return to the step S706 to await the next status update from the query manager 522.
In this way, not only does the cloud environment operating system build a desired infrastructure on a cloud, it also continually checks the infrastructure to ensure that there has not been any configuration drift or corruption over time that would bring the infrastructure out of specification with what the user initially declared the structure to be. This feature can provide an improvement over conventional cloud operation systems that implement a user's infrastructure but do not monitor that infrastructure for configuration drift or corruption over time.
Returning to
In another example, lobby server 504, process manager 506, storage 508, process table 510, interpreter manager 512, planner modules 514, builder driver 516, and query manager 522 can be implemented within a cloud computing environment in which case, rather than interfacing with a cloud 518, the system interfaces with a computing environment located within the cloud or another cloud service provider external to the cloud computing environment in which the above mentioned components reside (see further discussion below). In some embodiments, a cloud computing environment can include a separate account created in a cloud service provider by the cloud computing environment to implement a user-specified computing environment.
In addition to monitoring the implementation of the declared infrastructure on the cloud, the system described in
The foregoing description, for purpose of explanation, has been described with reference to specific embodiments. However, the illustrative discussions above are not intended to be exhaustive or to limit the invention to the precise forms disclosed. Many modifications and variations are possible in view of the above teachings. The embodiments were chosen and described in order to best explain the principles of the techniques and their practical applications. Others skilled in the art are thereby enabled to best utilize the techniques and various embodiments with various modifications as are suited to the particular use contemplated.
As discussed above, in some examples, the cloud environment operating system can be implemented within a cloud service provider environment.
As previously discussed, the cloud environment operating system 808, can refer to the components described above that can be used to automate the creation and operation of one or more cloud computing infrastructures and can create and destroy computing instances on one or more cloud service providers based on a user provided specification of computing infrastructure. Also as previously discussed, the cloud environment operating system 808 can be deployed within a cloud service provider.
As an example, in
In another example, a single user can use a single deployment of the cloud environment operating system on their cloud service provider account to manage multiple cloud computing environments.
In the example of
In the example of
While the user accesses the cloud environment operating system within a single cloud service provider, the user may not be limited to specifying cloud infrastructure for the single cloud service provider, and instead can specify cloud computing environments that can be implemented in multiple cloud service providers.
In the example of
In the example of
A single deployment of a cloud environment operating system within a cloud service provider can also be utilized by multiple users to create multiple computing environments.
In another scenario, rather than having multiple users share a common deployed cloud computing system, the multiple users can operate parallel computing environments using multiple cloud environment operating systems deployed in multiple cloud service provider accounts.
In the example of
In parallel to the operations of user 1260, an additional user 1262 can create domain specific language files 1218 that via CLI 1220 can create cloud computing environments via cloud environment operating system 1238. Cloud environment operating system 1238 can be deployed on a second cloud service provider 1226 and can be used to create computing environments 1234 and 1236 on a second user account 1232 located within cloud service provider 1226. Additionally, cloud environment operating system 1238 can be used to create cloud computing environment 1224 on a second user account 1222 located within cloud service provider 1206.
As the examples of
Although the disclosure and examples have been fully described with reference to the accompanying figures, it is to be noted that various changes and modifications will become apparent to those skilled in the art. Such changes and modifications are to be understood as being included within the scope of the disclosure and examples as defined by the claims.
This application claims priority to U.S. Provisional Patent Application No. 62/237,432, filed Oct. 5, 2015, which is incorporated herein by reference in its entirety.
| Number | Name | Date | Kind |
|---|---|---|---|
| 5680547 | Chang | Oct 1997 | A |
| 6199203 | Saboff | Mar 2001 | B1 |
| 6272499 | Wooten | Aug 2001 | B1 |
| 6501995 | Kinney et al. | Dec 2002 | B1 |
| 7188163 | Srinivasan et al. | Mar 2007 | B2 |
| 7275213 | Katano | Sep 2007 | B2 |
| 7284274 | Walls et al. | Oct 2007 | B1 |
| 7350207 | Fisher | Mar 2008 | B2 |
| 7486678 | Devanagondi et al. | Feb 2009 | B1 |
| 7533377 | Appavoo et al. | May 2009 | B2 |
| 7571120 | Fellenstein et al. | Aug 2009 | B2 |
| 7735078 | Vaidya | Jun 2010 | B1 |
| 7739155 | Fellenstein et al. | Jun 2010 | B2 |
| 8032846 | Balasubramanian | Oct 2011 | B1 |
| 8218539 | Dai | Jul 2012 | B2 |
| 8615584 | Dawson et al. | Dec 2013 | B2 |
| 8676621 | Helfrich et al. | Mar 2014 | B1 |
| 8745746 | Jain | Jun 2014 | B1 |
| 8755522 | Stella et al. | Jun 2014 | B2 |
| 8819836 | Stella et al. | Aug 2014 | B2 |
| 9003372 | Stella et al. | Apr 2015 | B2 |
| 9003525 | Stella et al. | Apr 2015 | B2 |
| 9014373 | Stella et al. | Apr 2015 | B2 |
| 9385866 | Stella et al. | Jul 2016 | B2 |
| 9461823 | Stella et al. | Oct 2016 | B2 |
| 9508095 | Stella et al. | Nov 2016 | B2 |
| 9800465 | Steinder | Oct 2017 | B2 |
| 9847878 | Stella et al. | Dec 2017 | B2 |
| 20020154781 | Sowa et al. | Oct 2002 | A1 |
| 20020178375 | Whittaker et al. | Nov 2002 | A1 |
| 20020188935 | Hertling et al. | Dec 2002 | A1 |
| 20030115123 | Lang | Jun 2003 | A1 |
| 20030147369 | Singh et al. | Aug 2003 | A1 |
| 20030156718 | Candelore et al. | Aug 2003 | A1 |
| 20040210769 | Radatti et al. | Oct 2004 | A1 |
| 20040255290 | Bates et al. | Dec 2004 | A1 |
| 20050022023 | Chincheck et al. | Jan 2005 | A1 |
| 20060165232 | Burazerovic et al. | Jul 2006 | A1 |
| 20060282897 | Sima et al. | Dec 2006 | A1 |
| 20070016961 | Vogler et al. | Jan 2007 | A1 |
| 20070033420 | Sherwani et al. | Feb 2007 | A1 |
| 20070091926 | Apostolopoulos et al. | Apr 2007 | A1 |
| 20070100905 | Masters et al. | May 2007 | A1 |
| 20070136455 | Lee et al. | Jun 2007 | A1 |
| 20070162541 | Dhawan et al. | Jul 2007 | A1 |
| 20070242620 | Zhai | Oct 2007 | A1 |
| 20070250582 | Sidhu et al. | Oct 2007 | A1 |
| 20080022374 | Brown et al. | Jan 2008 | A1 |
| 20080092235 | Comlekoglu | Apr 2008 | A1 |
| 20080095149 | Dai | Apr 2008 | A1 |
| 20080134177 | Fitzgerald et al. | Jun 2008 | A1 |
| 20080229300 | O'Brien | Sep 2008 | A1 |
| 20080263658 | Michael et al. | Oct 2008 | A1 |
| 20090076628 | Smith et al. | Mar 2009 | A1 |
| 20090125897 | Matlin et al. | May 2009 | A1 |
| 20090254900 | Nakamura | Oct 2009 | A1 |
| 20090319773 | Frenkel et al. | Dec 2009 | A1 |
| 20100050172 | Ferris | Feb 2010 | A1 |
| 20100083240 | Siman | Apr 2010 | A1 |
| 20100145864 | Boesjes | Jun 2010 | A1 |
| 20100195663 | Sharma et al. | Aug 2010 | A1 |
| 20100262950 | Garland | Oct 2010 | A1 |
| 20100325622 | Morton | Dec 2010 | A1 |
| 20100332262 | Horvitz et al. | Dec 2010 | A1 |
| 20110064081 | Lee et al. | Mar 2011 | A1 |
| 20110119104 | Levine et al. | May 2011 | A1 |
| 20110138050 | Dawson et al. | Jun 2011 | A1 |
| 20110138051 | Dawson et al. | Jun 2011 | A1 |
| 20110154313 | Nolterieke et al. | Jun 2011 | A1 |
| 20110209131 | Hohenstein et al. | Aug 2011 | A1 |
| 20110231899 | Pulier et al. | Sep 2011 | A1 |
| 20110258701 | Cruz et al. | Oct 2011 | A1 |
| 20110296391 | Gass et al. | Dec 2011 | A1 |
| 20110321028 | Evans et al. | Dec 2011 | A1 |
| 20120016721 | Weinman | Jan 2012 | A1 |
| 20120054345 | Sahu et al. | Mar 2012 | A1 |
| 20120066672 | Smith et al. | Mar 2012 | A1 |
| 20120079472 | Lenger | Mar 2012 | A1 |
| 20120131139 | Siripurapu et al. | May 2012 | A1 |
| 20120166582 | Binder | Jun 2012 | A1 |
| 20120185913 | Martinez et al. | Jul 2012 | A1 |
| 20120192253 | Betsch et al. | Jul 2012 | A1 |
| 20120243533 | Leong | Sep 2012 | A1 |
| 20120271874 | Nugent | Oct 2012 | A1 |
| 20120290460 | Curry, Jr. et al. | Nov 2012 | A1 |
| 20120317416 | Shetty et al. | Dec 2012 | A1 |
| 20130031028 | Martin | Jan 2013 | A1 |
| 20130081007 | Charters et al. | Mar 2013 | A1 |
| 20130138812 | Assuncao | May 2013 | A1 |
| 20130205020 | Broda et al. | Aug 2013 | A1 |
| 20130346227 | Jain et al. | Dec 2013 | A1 |
| 20140033308 | Sawyer et al. | Jan 2014 | A1 |
| 20140040885 | Donahue | Feb 2014 | A1 |
| 20140047546 | Sidagni | Feb 2014 | A1 |
| 20140052979 | Stella et al. | Feb 2014 | A1 |
| 20140053273 | Stella et al. | Feb 2014 | A1 |
| 20140053274 | Stella et al. | Feb 2014 | A1 |
| 20140067496 | Buswell | Mar 2014 | A1 |
| 20140067772 | Sabbouh et al. | Mar 2014 | A1 |
| 20140229221 | Shih et al. | Aug 2014 | A1 |
| 20140241380 | Bennett et al. | Aug 2014 | A1 |
| 20140278808 | Iyoob et al. | Sep 2014 | A1 |
| 20140380043 | Stella et al. | Dec 2014 | A1 |
| 20140380487 | Stella et al. | Dec 2014 | A1 |
| 20150067323 | Salowey et al. | Mar 2015 | A1 |
| 20150106620 | Cabrera et al. | Apr 2015 | A1 |
| 20150213270 | Stella et al. | Jul 2015 | A1 |
| 20150213271 | Stella et al. | Jul 2015 | A1 |
| 20150381580 | Graham, III et al. | Dec 2015 | A1 |
| 20160142427 | de los Reyes et al. | May 2016 | A1 |
| 20180019985 | Schoof et al. | Jan 2018 | A1 |
| 20180020008 | Schoof et al. | Jan 2018 | A1 |
| 20180034847 | Stella et al. | Feb 2018 | A1 |
| Number | Date | Country |
|---|---|---|
| 2 439 687 | Apr 2012 | EP |
| 2499193 | Aug 2013 | GB |
| WO-02023867 | Mar 2002 | WO |
| WO-2008087640 | Jul 2008 | WO |
| WO 2014088541 | Jun 2014 | WO |
| Entry |
|---|
| Stella et al., U.S. Office Action dated Dec. 6, 2013, directed to U.S. Appl. No. 13/969,158; 15 pages. |
| Stella et al., Notice of Allowance, dated May 23, 2014, directed to U.S. Appl. No. 13/969,158; 20 pages. |
| Stella et al., U.S. Office Action dated Nov. 3, 2014, directed to U.S. Appl. No. 14/467,933; 14 pages. |
| Stella et al., U.S. Office Action dated Jul. 31, 2015, directed to U.S. Appl. No. 14/679,831; 13 pages. |
| Stella et al., U.S. Office Action dated Feb. 9, 2016, directed to U.S. Appl. No. 14/679,831; 12 pages. |
| Stella et al., U.S. Office Action dated Jan. 2, 2014, directed to U.S. Appl. No. 13/969,181; 17 pages. |
| Stella et al., U.S. Office Action dated May 9, 2014, directed to U.S. Appl. No. 13/969,181; 19 pages. |
| Stella et al., U.S. Notice of Allowance dated Feb. 3, 2015, directed to U.S. Appl. No. 13/969,181; 10 pages. |
| Stella et al., U.S. Office Action dated Sep. 15, 2015, directed to U.S. Appl. No. 14/679,811; 17 pages. |
| Stella et al., U.S. Office Action dated Nov. 27, 2013, directed to U.S. Appl. No. 13/969,216; 21 pages. |
| Stella et al., Notice of Allowance, dated Mar. 18, 2014, directed to U.S. Appl. No. 13/969,216; 17 pages. |
| Stella et al., Notice of Allowability, dated May 21, 2014, directed to U.S. Appl. No. 13/969,216; 9 pages. |
| Stella et al., U.S. Office Action dated Oct. 30, 2014, directed to U.S. Appl. No. 14/305,500; 22 pages. |
| Stella et al., U.S. Notice of Allowance dated Feb. 23, 2015, directed to U.S. Appl. No. 14/305,500; 9 pages. |
| Stella et al., U.S. Office Action dated Jul. 9, 2015, directed to U.S. Appl. No. 14/691,436; 23 pages. |
| Stella et al., U.S. Office Action dated Mar. 2, 2016, directed to U.S. Appl. No. 14/691,436; 23 pages. |
| Stella et al., U.S. Office Action dated Sep. 22, 2016, directed to U.S. Appl. No. 14/691,436; 20 pages. |
| Stella et al., U.S. Office Action dated May 2, 2017, directed to U.S. Appl. No. 14/691,436; 16 pages. |
| Stella, J. et al., U.S. Office Action dated Oct. 9, 2014, directed to U.S. Appl. No. 14/302,220; 20 pages. |
| Stella, J. et al., U.S. Office Action dated Feb. 23, 2015, directed to U.S. Appl. No. 14/302,220; 22 pages. |
| International Search Report and Written Opinion dated Apr. 28, 2014, directed to International Application No. PCT/US2013/055449; 25 pages. |
| International Search Report and Written Opinion dated Aug. 25, 2015, directed to International Application No. PCT/US2015/034109; 20 pages. |
| Invitation to Pay Additional fees dated Sep. 11, 2017, directed to International Application No. PCT/US2017/042654; 2 pages. |
| International Search Report and Written Opinion dated Nov. 17, 2017, directed to International Application No. PCT/US2017/042654; 14 pages. |
| International Search Report and Written Opinion dated Oct. 10, 2017, directed to International Application No. PCT/US2017/042665; 10 pages. |
| International Search Report and Written Opinion dated Sep. 27, 2017, directed to International Application No. PCT/US2017/044199; 15 pages. |
| Office Action dated Nov. 25, 2016, directed to CN Application No. 201380049976.1; 7 pages. |
| Partial Supplementary Search Report dated Mar. 3, 2016, directed to EP Application No. 13831764.9; 9 pages. |
| Extended Search Report and Written Opinion dated Jul. 8, 2016, directed to EP Application No. 13831764.9; 13 pages. |
| Extended Search Report dated Oct. 9, 2017, directed to EP Application No. 15806113.5; 13 pages. |
| Office Action dated Oct. 27, 2017, directed to JP Application No. 2015-527673; 14 pages. |
| (2012) “Cybersecurity Startup Luminal Gets $3.82M in Series A Funding,” located at PrivateEquity.com. 1 page. |
| Microsoft “Windows Update Explained: How the Software Update Service Works and Why it Matters to You,” Published Sep. 2008; 12 pages. |
| McLellan, Lizzy, (Apr. 23, 2014) “Cybersecurity's new frontier: Frederick-based Luminal developing new security software,” The Daily Record (Baltimore, MD); 2 pages. |
| Summary of Luminal.com, located at <https://web.archive.org/web/20140401000000*/http://luminal.com> visited on Sep. 25, 2014. 3 pages. |
| Parelkar et al., “Authenticated Encryption in Hardware,” A Thesis Submitted to the Graduate Faculty of George Mason University, 2005, pp. 1-128. |
| Tanenbaum et al., (Dec. 1981) “Network Protocols,” Computing Surveys 13(4): 453-489. |
| U.S. Appl. No. 62/363,803, filed Jul. 18, 2016; 56 pages. |
| International Search Report and Written Opinion dated Dec. 8, 2016, directed to International Application No. PCT/US2016/055372; 9 pages. |
| Number | Date | Country | |
|---|---|---|---|
| 20170099191 A1 | Apr 2017 | US |
| Number | Date | Country | |
|---|---|---|---|
| 62237432 | Oct 2015 | US |
