# US 11,121,944 B2 · Systems and methods for rapid booting and deploying of an enterprise system in a cloud environment > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 11,121,944 B2 - Document ID: US11121944B2 - Status: Granted - Kind: B2 - Application number: 16/837,809 - Filed: 2020-04-01 - Published: 2020-08-06 - Granted: 2021-09-14 - Earliest claimed: 2019-01-18 - Assignees: Fidelity Information Services, LLC - Applicants: Fidelity Information Services, LLC - Inventors: Scott Meyer; Fiaz Sindhu; Giacomo Novielli; Miriyala Venu Madhav - Web page: https://patentgrep.com/patent/US11121944B2 ## CPC - H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components - G06F 9/4416: {Network booting; Remote initial program loading [RIPL]} - G06F 9/44526: {Plug-ins; Add-ons} - G06F 9/45533: {Hypervisors; Virtual machine monitors} - G06F 9/45558: {Hypervisor-specific management and integration aspects} - G06Q 40/02: Banking, e.g. interest calculation or account maintenance (credit or loans G06Q40/03) - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - H04L 41/0886: {Fully automatic configuration} - H04L 41/0889: {Techniques to speed-up the configuration process} - H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements - H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities - H04L 41/5029: {Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less} - H04L 63/0428: {wherein the data content is protected, e.g. by encrypting or encapsulating the payload} - H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)} - H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46) - H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS] - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - G06F 2009/45562: {Creating, deleting, cloning virtual machine instances} - G06F 2009/4557: {Distribution of virtual machine instances; Migration and load balancing} - G06F 2009/45587: {Isolation or security of virtual machine instances} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - G06Q: INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR ## Abstract The present disclosure relates to systems and methods for deploying enterprise systems in cloud environments. In one implementation, a system for deploying an enterprise system in a cloud environment may include at least one processor configured to provide: one or more first containers hosting at least one application with at least one enterprise function; one or more second containers hosting at least one microservice configured to activate the at least one enterprise function; at least one application programming interface (API) between the at least one microservice and at least one client; and at least one gateway configured to manage access to the at least one API. ## Claims ### Claim 1 A system for deploying an enterprise system in a cloud environment, comprising: at least one memory storing instructions; and at least one processor configured to execute the instructions to perform operations comprising: receiving an enterprise back-up file for an enterprise system in response to a disconnect event from a peripheral system; requesting cloud services for the enterprise system, including at least one data store, at least one application container, and at least one service container; initiating at least one application in the at least one application container; initiating at least one microservice in the at least one service container; connecting the at least one microservice and the at least one application via an application programming interface (API); integrating the at least one microservice with the peripheral system to allow the at least one microservice to send and receive data from the peripheral system; and enabling a gateway to manage access to the API to allow users access the integrated microservice. ### Claim 2 (depends on 1) The system of claim 1, wherein receiving an enterprise back-up file comprises: receiving at least one first back-up file in a first format; and generating the enterprise back-up file in a second format that is compatible with the enterprise system by parsing the at least one first back-up file. ### Claim 3 (depends on 2) The system of claim 2, wherein the first format is a file format defined by Part 360 of Federal Deposit Insurance Corporation Rules and Regulations. ### Claim 4 (depends on 2) The system of claim 2, wherein receiving the enterprise back-up file further comprises: determining that the at least one first back-up file is encrypted; retrieving an encryption key for the at least one first back-up file; and decrypting the at least one first back-up file. ### Claim 5 (depends on 4) The system of claim 4, wherein receiving the enterprise back-up file further comprises: validating the decrypted at least one first back-up file based on a hash associated with the at least one back-up file. ### Claim 6 (depends on 1) The system of claim 1, wherein the at least one data store is one or more of: an Amazon S3 bucket, an Amazon elastic block store (EBS) volume, a structured query language (SQL) databases, and a NoSQL database. ### Claim 7 (depends on 1) The system of claim 1, wherein the at least one application container is one or more of: a Kubernetes pod, a FreeBSD jail, and a Docker container. ### Claim 8 (depends on 1) The system of claim 1, wherein the at least one service container is one or more of: a Kubernetes pod, a FreeBSD jail, and a Docker container. ### Claim 9 (depends on 1) The system of claim 1, the operations further comprising: duplicating the at least one initiated application across multiple application containers. ### Claim 10 (depends on 1) The system of claim 1, wherein connecting the at least one microservice and the at least one application comprises: utilizing a helm chart to boot the at least one microservice and connect the at least one microservice to the at least one platform application. ### Claim 11 (depends on 1) The system of claim 1, further comprising: storing the enterprise back-up file in the at least one data store. ### Claim 12 (depends on 11) The system of claim 11, wherein storing the enterprise back-up file in the at least one data store further comprises: transferring at least part of the enterprise back-up file to the at least one microservice; and encrypting the enterprise back-up file for storage. ### Claim 13 (depends on 1) The system of claim 1, wherein integrating the at least one microservice with the peripheral system comprises: opening a secure channel for the at least one microservice to connect to the peripheral system. ### Claim 14 (depends on 13) The system of claim 13, wherein opening a secure channel for the at least one microservice to connect to the peripheral system comprises: re-routing the peripheral system to an address of the secure channel. ### Claim 15 (depends on 1) The system of claim 1, wherein the disconnect event is a failure of a cloud system. ### Claim 16 (depends on 1) The system of claim 1, wherein the disconnect event is a system upgrade. ### Claim 17 (depends on 1) The system of claim 1, wherein the disconnect event is deploying a new enterprise system from existing data. ### Claim 18 (depends on 1) The system of claim 1, wherein the peripheral system is one of: a point-of-sale system, a transaction processing system, an external bank system, or a government bank system. ### Claim 19 A computer implemented method for deploying an enterprise system in a cloud environment, comprising: receiving an enterprise back-up file for an enterprise system in response to a disconnect event from a peripheral system; requesting cloud services for the enterprise system, including at least one data store, at least one application container, and at least one service container; initiating at least one application in the at least one application container; initiating at least one microservice in the at least one service container; connecting the at least one microservice and the at least one application via an application programming interface (API); integrating the at least one microservice with the peripheral system to allow the at least one microservice to send and receive data from the peripheral system; and enabling a gateway to manage access to the API to allow users access the integrated microservice. ### Claim 20 A non-transitory computer-readable medium that stores instructions that, when executed by at least one processor, cause the at least one processor to perform a method comprising: receiving an enterprise back-up file for an enterprise system in response to a disconnect event from a peripheral system; requesting cloud services for the enterprise system, including at least one data store, at least one application container, and at least one service container; initiating at least one application in the at least one application container; initiating at least one microservice in the at least one service container; connecting the at least one microservice and the at least one application via an application programming interface (API); integrating the at least one microservice with the peripheral system to allow the at least one microservice to send and receive data from the peripheral system; and enabling a gateway to manage access to the API to allow users access the integrated microservice.