IP Library › Granted Patent US 12,542,650
Granted Patent B2
US 12,542,650 · App. 18/376,138 · Granted Feb 3, 2026

Artificial intelligence (AI) based cloud architecture segmentation leveraging homomorphic encryption

Inventors: Saurabh Garg (Faridabad, IN); Bhagat Allugubelly (Hyderabad, IN); Maneesh Sethia (Telangana, IN)
Assignee: Bank of America Corporation
H04L9/008G06F21/602
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,542,650
App. No.
18/376,138
Filed
Oct 3, 2023
Granted
Feb 3, 2026
Kind
B2
Examiner
LI, MENG
Art Unit
2437
USPC
713/189
Abstract

A computing platform may train, using smart contract and file type information, a homomorphic encryption model, which may configure the homomorphic encryption model to identify, for a given input file, a corresponding smart contract defining a corresponding set of parameters, included in the given input file, for display. The computing platform may receive an unencrypted file, and may identify, by inputting the unencrypted file into the homomorphic encryption model, a smart contract defining one or more parameters for display. The computing platform may encrypt, using homomorphic encryption, the unencrypted file to produce an encrypted file, and may store the encrypted file. The computing platform may receive, via an application programming interface (API) at a user device, a request to access the encrypted file. The computing platform may send, based on the smart contract and for display at the user device via the API, the parameters for display.

Claims (58)

1 . A computing platform comprising:

at least one processor;

a communication interface communicatively coupled to the at least one processor; and

memory storing computer-readable instructions that, when executed by the at least one processor, cause the computing platform to:

train, using smart contract and file type information, a homomorphic encryption model, wherein training the homomorphic encryption model configures the homomorphic encryption model, by establishing stored correlations between the file type information and the smart contracts, to identify, based on a given file type for a given input file, a corresponding smart contract defining a corresponding set of parameters, included in the given input file, for display, wherein the homomorphic encryption model comprises one of a supervised learning model or an unsupervised learning model, and wherein the homomorphic encryption model is further trained using historical system performance information, and wherein training the homomorphic encryption model using the historical system performance information configures the homomorphic encryption model to output, for the given input file, one or more corresponding processing resources of the computing platform at which to perform homomorphic encryption of an encrypted file;

receive an unencrypted file;

identify, by inputting the unencrypted file into the homomorphic encryption model, a smart contract defining one or more parameters for display, wherein the homomorphic encryption model identifies the smart contract by:

comparing a file type of the unencrypted file to the file type information used to train the homomorphic encryption model, and

identifying, based on the stored correlations between the file type information and the smart contracts, the smart contract corresponding to the file type;

encrypt, using homomorphic encryption, the unencrypted file to produce the encrypted file;

store the encrypted file;

receive, via an application programming interface (API) at a user device, a request to access the encrypted file and authentication credentials; and

send, based on the smart contract, based on validation of the authentication credentials, and for display at the user device via the API, the parameters for display.

2 . The computing platform of claim 1 , wherein the homomorphic encryption model comprises an artificial intelligence (AI) model.

3 . The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, further cause the computing platform to:

identify, by inputting the unencrypted file and current system performance information into the homomorphic encryption model, one or more processing resources of the computing platform at which to perform the homomorphic encryption of the encrypted file.

4 . The computing platform of claim 3 , wherein the current system performance information comprises system latency, available memory, available processing resources, and system load.

5 . The computing platform of claim 1 , wherein the smart contract defines the one or more parameters for display and one or more parameters to remain concealed.

6 . The computing platform of claim 1 , wherein the smart contract defines different parameters for display for different users.

7 . The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, further cause the computing platform to:

generate a file token representing the unencrypted file; and

store, using a distributed ledger, the file token.

8 . The computing platform of claim 7 , wherein the file token comprises one of a non-fungible token (NFT) or a crypto token.

9 . The computing platform of claim 1 , wherein sending the parameters for display comprises sending the parameters without decrypting the encrypted file.

10 . The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, further cause the computing platform to:

update, based on the identified smart contract, the homomorphic encryption model.

11 . The computing platform of claim 1 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, further cause the computing platform to:

identify, based on the authentication credentials, a user identity, wherein sending the parameters for display comprises sending, based on the user identity, a subset of the parameters for display.

12 . A method comprising:

at a computing platform comprising at least one processor, a communication interface, and memory:

training, using smart contract and file type information, a homomorphic encryption model, by establishing stored correlations between the file type information and the smart contracts, wherein training the homomorphic encryption model configures the homomorphic encryption model to identify, based on a given file type for a given input file, a corresponding smart contract defining a corresponding set of parameters, included in the given input file, for display, wherein the homomorphic encryption model comprises one of a supervised learning model or an unsupervised learning model, and wherein the homomorphic encryption model is further trained using historical system performance information, and wherein training the homomorphic encryption model using the historical system performance information configures the homomorphic encryption model to output, for the given input file, one or more corresponding processing resources of the computing platform at which to perform homomorphic encryption of an encrypted file;

receiving an unencrypted file;

identifying, by inputting the unencrypted file into the homomorphic encryption model, a smart contract defining one or more parameters for display, wherein the homomorphic encryption model identifies the smart contract by:

comparing a file type of the unencrypted file to the file type information used to train the homomorphic encryption model, and

identifying, based on the stored correlations between the file type information and the smart contracts, the smart contract corresponding to the file type;

encrypting, using homomorphic encryption, the unencrypted file to produce the encrypted file;

storing the encrypted file;

receiving, via an application programming interface (API) at a user device, a request to access the encrypted file; and

sending, based on the smart contract and for display at the user device via the API, the parameters for display.

13 . The method of claim 12 , wherein the homomorphic encryption model comprises an artificial intelligence (AI) model.

14 . The method of claim 12 , further comprising:

identifying, by inputting the unencrypted file and current system performance information into the homomorphic encryption model, one or more processing resources of the computing platform at which to perform the homomorphic encryption of the encrypted file.

15 . The method of claim 14 , wherein the current system performance information comprises system latency, available memory, available processing resources, and system load.

16 . The method of claim 12 , wherein the smart contract defines the one or more parameters for display and one or more parameters to remain concealed.

17 . The method of claim 12 , wherein the smart contract defines different parameters for display for different users.

18 . One or more non-transitory computer-readable media storing instructions that, when executed by a computing platform comprising at least one processor, a communication interface, and memory, cause the computing platform to:

train, using smart contract and file type information, a homomorphic encryption model, wherein training the homomorphic encryption model configures the homomorphic encryption model, by establishing stored correlations between the file type information and the smart contracts, to identify, based on a given file type for a given input file, a corresponding smart contract defining a corresponding set of parameters, included in the given input file, for display, wherein the homomorphic encryption model comprises one of a supervised learning model or an unsupervised learning model, and wherein the homomorphic encryption model is further trained using historical system performance information, and wherein training the homomorphic encryption model using the historical system performance information configures the homomorphic encryption model to output, for the given input file, one or more corresponding processing resources of the computing platform at which to perform homomorphic encryption of an encrypted file;

receive an unencrypted file;

identify, by inputting the unencrypted file into the homomorphic encryption model, a smart contract defining one or more parameters for display, wherein the homomorphic encryption model identifies the smart contract by:

comparing a file type of the unencrypted file to the file type information used to train the homomorphic encryption model, and

identifying, based on the stored correlations between the file type information and the smart contracts, the smart contract corresponding to the file type;

encrypt, using homomorphic encryption, the unencrypted file to produce the encrypted file;

store the encrypted file;

receive, via an application programming interface (API) at a user device, a request to access the encrypted file; and

send, based on the smart contract and for display at the user device via the API, the parameters for display.

19 . The one or more non-transitory computer-readable media of claim 18 , wherein the homomorphic encryption model comprises an artificial intelligence (AI) model.

20 . The one or more non-transitory computer-readable media of claim 18 , wherein the memory stores additional computer-readable instructions that, when executed by the at least one processor, further cause the computing platform to:

identify, by inputting the unencrypted file and current system performance information into the homomorphic encryption model, one or more processing resources of the computing platform at which to perform the homomorphic encryption of the encrypted file.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 3, 2023
From: GARG, SAURABH; ALLUGUBELLY, BHAGAT; SETHIA, MANEESH
To: BANK OF AMERICA CORPORATION
Reel/Frame 065107/0962 →
Continuity (1)
Related Publication 20250112758A1 · Apr 3, 2025
References Cited (51)
US 8630422B2 · Gentry · 2014 [cited by applicant]
US 9716590B2 · Gentry · 2017 [cited by applicant]
US 10546141B2 · Miguel et al. · 2020 [cited by applicant]
US 11374736B2 · Gao · 2022 [cited by applicant]
US 11777707B2 · Ghosh et al. · 2023 [cited by applicant]
US 11777729B2 · Williams et al. · 2023 [cited by applicant]
US 11790459B1 · Strauss · 2023 [cited by examiner]
US 12309182B1 · McAleer · 2025 [cited by examiner]
US 20200019864A1 · Gu · 2020 [cited by examiner]
US 20200151356A1 · Rohloff et al. · 2020 [cited by applicant]
US 20200225655A1 · Cella · 2020 [cited by examiner]
US 20200250663A1 · Abad · 2020 [cited by examiner]
US 20200322323A1 · Corning · 2020 [cited by examiner]
US 20210099287A1 · Keselman et al. · 2021 [cited by applicant]
US 20210117408A1 · Figueredo de Santana · 2021 [cited by examiner]
US 20210366586A1 · Ryan · 2021 [cited by examiner]
US 20210390599A1 · Tardiou · 2021 [cited by examiner]
US 20210398017A1 · Garg · 2021 [cited by examiner]
US 20220366494A1 · Cella · 2022 [cited by examiner]
US 20220398341A1 · Diaz-Mitoma · 2022 [cited by examiner]
US 20230006809A1 · Shpurov et al. · 2023 [cited by applicant]
US 20230113896A1 · Milazzo · 2023 [cited by examiner]
US 20230185919A1 · Bond · 2023 [cited by applicant]
US 20230188316A1 · Springer, IV et al. · 2023 [cited by applicant]
US 20230188317A1 · Choi et al. · 2023 [cited by applicant]
US 20230188320A1 · Park et al. · 2023 [cited by applicant]
US 20230188321A1 · Jing · 2023 [cited by examiner]
US 20230188322A1 · Bajpeyi et al. · 2023 [cited by applicant]
US 20230198740A1 · Kachare et al. · 2023 [cited by applicant]
US 20230208610A1 · Shaul et al. · 2023 [cited by applicant]
US 20230208638A1 · Manevich · 2023 [cited by examiner]
US 20230216655A1 · Liao et al. · 2023 [cited by applicant]
US 20230216656A1 · Liao et al. · 2023 [cited by applicant]
US 20230216657A1 · Aharoni et al. · 2023 [cited by applicant]
US 20230246807A1 · Lee et al. · 2023 [cited by applicant]
US 20230254125A1 · No et al. · 2023 [cited by applicant]
US 20230269067A1 · Son et al. · 2023 [cited by applicant]
US 20230269069A1 · No et al. · 2023 [cited by applicant]
US 20230291541A1 · Gupta et al. · 2023 [cited by applicant]
US 20230297649A1 · Drucker et al. · 2023 [cited by applicant]
US 20230306237A1 · Greenberg et al. · 2023 [cited by applicant]
US 20230396453A1 · Jain · 2023 [cited by examiner]
US 20240070306A1 · Jurat · 2024 [cited by examiner]
US 20240106846A1 · Kapoor · 2024 [cited by examiner]
US 20240144381A1 · Martine · 2024 [cited by examiner]
US 20240273535A1 · Fang · 2024 [cited by examiner]
US 20240370861A1 · Benvenuti · 2024 [cited by examiner]
US 20240370865A1 · Bernardi · 2024 [cited by examiner]
US 20250112758A1 · Garg · 2025 [cited by examiner]
CN 107181584B · 2020 [cited by applicant]
CN 108462575B · 2020 [cited by applicant]