# US 11,445,035 B2 · Graph knowledge base for modeling and processing stateful cloud-native applications > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,445,035 B2 - Document ID: US11445035B2 - Status: Granted - Kind: B2 - Application number: 17/157,491 - Filed: 2021-01-25 - Published: 2021-11-18 - Granted: 2022-09-13 - Earliest claimed: 2020-01-24 - Assignees: EnterpriseWeb LLC - Applicants: EnterpriseWeb LLC - Inventors: Dave M. Duggal; William J. Malyk - Web page: https://patentgrep.com/patent/US11445035B2 ## CPC - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04L 67/60: Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources (admission control or resource allocation H04L47/70) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Receive an order, the order indicating a network service model. Identify a context of the order based on metadata. Generate, using the network service model, a deployment plan, the deployment plan facilitating an instantiation of a contextually-motivated network service instance as a set of normalized lifecycle management (LCM) operations performed against at least one of a plurality of associated service entities. Deploy the deployment plan, wherein to deploy the deployment plan causes the system to bind each of the normalized LCM operations, based on the context of the order, to one or more respective micro-capabilities, each of the respective micro-capabilities having previously been onboarded to the system as one or more corresponding modeled objects capable of being declaratively composed, each of the corresponding modeled objects including a mapping of standard LCM operations to one or more existing micro-capabilities of the system, and manage execution of the one or more respective micro-capabilities and associated resources, associated storage, and associated network and service allocation and configuration, to instantiate the contextually-motivated network service instance, wherein to manage the execution of the one or more micro-capabilities causes the system to fulfill the order as a transaction providing guarantees, and applying any of compensations and rollback automatically. Trace the transaction based on the metadata, thereby simplifying test and debug operations and run-time observability. ## Claims ### Claim 1 A method for designing, deploying, and managing an application, comprising: providing a design environment comprising a catalog of objects, a rich type system, and a graph knowledge base describing an upper ontology that represents a higher-level abstraction, wherein the higher-level abstraction supports classification of generic data and function types for dynamic typing and prototypal inheritance; receiving in the design environment, a declarative composition of the application created using the rich type system; producing, based on the declarative composition, an object for storage in the catalog of objects; upon receipt of a request for the application, generating, using the graph knowledge base, the upper ontology, and the catalog of objects, context information to hydrate the request; executing at least one run-time function based on the hydrated request that accesses a service; distributing the at least one run-time function to the service; and as a response to the request, returning a result from the service. ### Claim 2 (depends on 1) The method of claim 1, wherein the graph knowledge base describes a domain specific language comprising concepts, types, and policies. ### Claim 3 (depends on 1) The method of claim 1, wherein each object in the catalog of objects further describes back-end service requirements for late-binding. ### Claim 4 (depends on 1) The method of claim 1, the distributing further comprising: writing the result to a transaction object associated with the application to provide a trace for auditing and debugging, wherein the transaction object provides for a closure over a set of operations during transaction processing. ### Claim 5 (depends on 1) The method of claim 1, the distributing further comprising: generating, based upon the graph knowledge base, a second run-time function that accesses a second service associated with the at least one object; and distributing the second run-time function in a parallel with the at least one run-time function. ### Claim 6 (depends on 1) The method of claim 1, wherein the graph knowledge base is extensible. ### Claim 7 (depends on 1) The method of claim 1, wherein the graph knowledge base includes industry-specific models for networking and life sciences. ### Claim 8 A system for designing, deploying, and managing an application, comprising: at least one processor; a memory storing executable instructions that when executed by the at least one processor causes the at least one processor to perform the steps of: provide a design environment comprising a catalog of objects, a rich type system, and a graph knowledge base describing an upper ontology that represents a higher-level abstraction, wherein the higher-level abstraction supports classification of generic data and function types for dynamic typing and prototypal inheritance; receive in the design environment a declarative composition of the application created using the rich type system; produce, based on the declarative composition, an object for storage in the catalog of objects; upon receipt of a request for the application, generate, using the graph knowledge base, the upper ontology, and the catalog of objects, context information to hydrate the request; execute at least one run-time function based on the hydrated request that accesses a service; distribute the at least one run-time function to the service; and as a response to the request, return a result from the service. ### Claim 9 (depends on 8) The system of claim 8, wherein the graph knowledge base describes a domain specific language comprising concepts, types, and policies. ### Claim 10 (depends on 8) The system of claim 8, wherein an object in the catalog of objects further describes back-end service requirements for late-binding. ### Claim 11 (depends on 8) The system of claim 8, wherein to distribute the at least one processor is further configured to: write the result to a transaction object associated with the application to provide a trace for auditing and debugging, wherein the transaction object provides for a closure over a set of operations during transaction processing. ### Claim 12 (depends on 8) The system of claim 8, the at least one processor further configured to: generate, based upon the graph knowledge base, a second run-time function that accesses a second service associated with the at least one object; and distribute the second run-time function in a parallel with the at least one run-time function. ### Claim 13 (depends on 8) The system of claim 8, wherein the graph knowledge base is extensible. ### Claim 14 (depends on 8) The system of claim 8, wherein the graph knowledge base includes industry-specific models for networking and life sciences. ### Claim 15 A non-transitory, tangible computer-readable device having instructions stored thereon that, when executed by at least one computing device, causes the at least one computing device to perform operations for designing, deploying, and managing an application, comprising: providing a design environment comprising a catalog of objects, a rich type system, and a graph knowledge base describing an upper ontology that represents a higher-level abstraction, wherein the higher-level abstraction supports classification of generic data and function types for dynamic typing and prototypal inheritance; receiving in the design environment, a declarative composition of the application created using the rich type system; upon receipt of a request for the application, generating, using the graph knowledge base, the upper ontology, and the catalog of objects, context information to hydrate the request; executing at least one run-time function based on the hydrated request that accesses a service; distributing the at least one run-time function to the service; and as a response to the request, returning a result from the service. ### Claim 16 (depends on 15) The non-transitory, tangible computer-readable device of claim 15, wherein the graph knowledge base describes a domain specific language comprising concepts, types, and policies. ### Claim 17 (depends on 15) The non-transitory, tangible computer-readable device of claim 15, wherein an object in the catalog of objects further describes back-end service requirements for late-binding. ### Claim 18 (depends on 15) The non-transitory, tangible computer-readable device of claim 15, the operations further comprising: writing the result to a transaction object associated with the application to provide a trace for auditing and debugging, wherein the transaction object provides for a closure over a set of operations during transaction processing. ### Claim 19 (depends on 15) The non-transitory, tangible computer-readable device of claim 15, the operations further comprising: generating, based upon the graph knowledge base, a second run-time function that accesses a second service associated with the at least one object; and distributing the second run-time function in a parallel with the at least one run-time function. ### Claim 20 (depends on 15) The non-transitory, tangible computer-readable device of claim 15, wherein the graph knowledge base is extensible.