Systems and methods for rapid booting and deploying of an enterprise system in a cloud environment

Patent metadata

Field	Value
Publication number	US-11522772-B2
Application number	US-202117240682-A
Country	US
Kind code	B2
Filing date	Apr 26, 2021
Priority date	Jan 18, 2019
Publication date	Dec 6, 2022
Grant date	Dec 6, 2022

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.

First claim

What is claimed is:

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 provide:
one or more first containers hosting at least one application, the application comprising at least one enterprise function and a platform layer with one or more extensions, the platform layer comprising a plurality of construct sets, wherein at least one of the plurality of the construct sets includes one or more data structures defining a set of variables and functions to provide one or more custom application features;
one or more second containers hosting at least one microservice configured to activate the at least one enterprise function; and
at least one application programming interface (API) between the at least one microservice and at least one client; and
one or more virtual data stores accessible by the one or more first containers, the one or more virtual data stores comprising data from at least one backup file,
wherein the at least one backup file is decrypted before being parsed into a format associated with the one or more first containers and subsequently re-encrypted into a format associated with the one or more first containers.

2. The system of claim 1 , wherein the at least one processor is further configured to validate the integrity of the at least one backup file.

3. The system of claim 2 , wherein validating the integrity of the at least one backup file is based on a hash of the at least one backup file.

4. The system of claim 2 , wherein validating the integrity of the at least one backup file is based on one or more tags associated with the at least one backup file.

5. The system of claim 1 , wherein the at least one backup file is re-encrypted using a different schema from a first schema used to encrypt the at least one backup file.

6. The system of claim 1 , wherein the at least one client comprises a secondary enterprise system.

7. The system of claim 6 , wherein the client is configured to send an input to the microservice to activate one or more of the at least one enterprise functions.

8. The system of claim 7 , wherein the secondary enterprise system comprises an input device and the client is configured to send the input to the microservice in response to user input from the input device.

9. The system of claim 6 , wherein the at least one client comprises credential-based authentication.

10. The system of claim 1 , wherein each container of the one or more first containers hosts only one application.

11. The system of claim 1 , wherein each container of the one or more second containers hosts only one microservice.

12. The system of claim 1 , wherein the enterprise system comprises a banking core.

13. The system of claim 1 , wherein the platform layer comprises a plurality of construct sets.

14. The system of claim 13 , wherein the plurality of construct sets comprises a product definition construct set, an arrangement management construct set, and a transaction processing construct set.

15. The system of claim 14 , wherein the plurality of construct sets further comprises at least one of a pricing definition construct set or an account processing construct set.

16. 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 provide:
one or more first containers hosting at least one application, the application comprising at least one enterprise function and a platform layer with one or more extensions, the platform layer comprising a plurality of construct sets, wherein at least one of the plurality of the construct sets includes one or more data structures defining a set of variables and functions to provide one or more custom application features;
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;
one or more virtual data stores accessible by the one or more first containers, the one or more virtual data stores comprising data from at least one backup file; and
at least one gateway configured to manage access to the at least one API, wherein:
the at least one application provides at least one peripheral processing function;
the at least one microservice is configured to process input from and output to at least one peripheral system and in communication with the at least one application; and
the at least one processor is further configured to:
decrypt the at least one backup file before parsing the at least one backup file into a format associated with the enterprise system and subsequently re-encrypting the at least one backup file into a format associated with the enterprise system, and
provide at least one communication channel with the at least one peripheral system, the at least one communication channel configured to receive input from the at least one peripheral system and to transmit output from the at least one microservice to the at least one peripheral system.

17. The system of claim 16 , wherein the at least one application comprises an automated clearing house (ACH) incoming file application, an ACH outgoing file application, an ACH incoming return application, or an ACH outgoing return application.

18. The system of claim 16 , wherein the at least one application comprises an automated teller machine (ATM) withdrawal application, or an ATM deposit application.

19. The system of claim 16 , wherein the at least one microservice comprises a batch scheduler for substitute check incoming files or a batch scheduler for substitute check outgoing files.

20. A method for deploying an enterprise system in a cloud environment, comprising:
providing one or more first containers hosting at least one application, the application comprising at least one enterprise function and a platform layer with one or more extensions, the platform layer comprising a plurality of construct sets, wherein at least one of the plurality of the construct sets includes one or more data structures defining a set of variables and functions to provide one or more custom application features;
providing one or more second containers hosting at least one microservice configured to activate the at least one enterprise function;
providing at least one application programming interface (API) between the at least one microservice and at least one client; and
providing one or more virtual data stores accessible by the one or more first containers, the one or more virtual data stores comprising data from at least one backup file;
decrypting the at least one backup file;
parsing the at least one backup file into a format associated with the one or more first containers; and
re-encrypting the at least one backup file into a format associated with the one or more first containers.

21. The system of claim 15 , wherein the one or more custom application features include any one or more of: product definition, arrangement management, transaction processing, pricing definition, or account processing.

Assignees

• Fidelity Information Services Llc

Inventors

• Meyer Scott
• Sindhu Fiaz
• Novielli Giacomo
• Madhav Miriyala

Classifications

• G06F9/45558

  Hypervisor-specific management and integration aspects · CPC title

• H04L67/34

  involving the movement of software or configuration parameters  (network booting or remote initial program loading [RIPL] G06F9/4416) · CPC title

• H04L41/5029

  Service quality level-based billing, e.g. dependent on measured service level customer is charged more or less · CPC title

• G06F2009/45562

  Creating, deleting, cloning virtual machine instances · CPC title

• G06F9/44526

  Plug-ins; Add-ons · CPC title