# US 2022/0286352 A1 · Managing Pre-Provisioning and Post-Provisioning of Resources Using Bitemporal Analysis > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2022/0286352 A1 - Document ID: US20220286352A1 - Status: Published application - Kind: A1 - Application number: 17/516,329 - Filed: 2021-11-01 - Published: 2022-09-08 - Earliest claimed: 2021-03-05 - Assignees: Capital One Services, LLC - Applicants: Capital One Services, LLC - Inventors: Brian Lee WONG; Virendra K. ABELAK; Steven LOTT; Philip Austin KEDY - Web page: https://patentgrep.com/patent/US20220286352A1 ## CPC - G06Q 20/389: {Keeping log of transactions for guaranteeing non-repudiation of a transaction} - G06F 16/215: Improving data quality; Data cleansing, e.g. de-duplication, removing invalid entries or correcting typographical errors - G06F 16/219: {Managing data history or versioning (querying versioned data G06F16/2474; querying temporal data G06F16/2477)} - G06F 16/2308: {Concurrency control (transaction processing G06F9/466)} - G06F 16/2358: {Change logging, detection, and notification (replication G06F16/27)} - G06F 16/2365: {Ensuring data consistency and integrity} - G06F 16/2379: {Updates performed during online database operations; commit processing} - G06F 16/2477: {Temporal data queries} - G06F 16/9024: {Graphs; Linked lists (G06F16/9027 takes precedence)} - G06Q 20/08: Payment architectures - G06Q 20/382: {insuring higher security of transaction} - H04L 9/3297: {involving time stamps, e.g. generation of time stamps} - H04L 9/50: {using hash chains, e.g. blockchains or hash trees} - H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play - H04L 41/0816: the condition being an adaptation, e.g. in response to network events - H04L 41/0856: {by backing up or archiving configuration information} - H04L 41/0866: Checking the configuration - H04L 63/123: {received data contents, e.g. message integrity} - H04L 67/34: {involving the movement of software or configuration parameters (network booting or remote initial program loading [RIPL] G06F9/4416)} - H04L 69/02: {Protocol performance} - H04L 69/08: Protocols for interworking; Protocol conversion - G06Q 40/00: Finance; Insurance; Tax strategies; Processing of corporate or income taxes - H04L 41/0894: Policy-based network configuration management - H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)} - 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 - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract Embodiments disclosed are directed to ensuring resource compliance within a cloud-based environment. The embodiments include steps for performing both pre-provisioning and post-provisioning checks of resources, such as network protocols, prior to and after their deployment within the cloud-based environment. These steps include using bitemporal analysis to determine the impact of deploying resources within the environment through the use of multiple execution timelines where the impact of deploying a resource may be evaluated on an alternative timeline that does not change the current resource scope of the cloud-based environment. The analysis may further include tracking the impact of the resource after it has been deployed to ensure resource compliance. ## Claims ### Claim 1 A computer-implemented method for improving protocol compliance in a cloud network that includes an immutable database by performing a pre-provisioning check of a new protocol and a post-provisioning check of a current protocol, the method comprising: maintaining, in the immutable database, a state of the cloud network on a current execution timeline, wherein the current execution timeline is a time-ordered data series of a history of transactions, wherein the state of the cloud network includes the history of transactions associated with a user financial account, wherein the history of transactions includes transactions previously processed by the cloud network up to a current date; performing the pre-provisioning check of the new protocol by: receiving provisioning information associated with provisioning the new protocol in the cloud network; generating an alternate transaction based on the provisioning information; and determining whether to provision the new protocol based on an evaluation of the alternate transaction; and performing a post-provisioning check of the current protocol by: receiving a modification to the current protocol; generating a second alternate transaction based on the modification to the current protocol; and determining whether to provisioning the modification to the current protocol based on a second evaluation of the second alternate transaction. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein performing the post-provisioning check further comprises: receiving second provisioning information associated with provisioning the modification to the current protocol in the cloud network; and generating a second alternate execution timeline based on the second provisioning information, wherein the second alternate execution timeline includes the second alternate transaction, wherein the second alternate execution timeline is separate from the current execution timeline and the alternate execution timeline. ### Claim 3 (depends on 2) The computer-implemented method of claim 2, further comprising: performing the second evaluation of the second alternate transaction, wherein the second evaluation indicates that the second alternate transaction is compliant or non-compliant with the cloud network; and determining whether to provision the modification to the current protocol based on the second evaluation. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, wherein performing the pre-provisioning check of the new protocol further comprises: generating an alternate execution timeline based on the provisioning information and the current execution timeline, wherein the alternate execution timeline includes the alternate transaction, and wherein the alternate transaction is generated based on the transactions previously processed by the cloud network up to the current date; and performing the evaluation of the an alternate transaction, wherein the evaluation of the alternate transaction indicates that the an alternate transaction is compliant or non-compliant with the cloud network. ### Claim 5 (depends on 4) The computer-implemented method of claim 4, further comprising: responsive to the evaluation of the alternate transaction indicating that the new protocol is compliant with the cloud network, performing a first action of provisioning the new protocol in the cloud network; and responsive to the evaluation of the alternate transaction indicating that the new protocol is non-compliant with the cloud network, performing a second action of preventing the provisioning of the new protocol in the cloud network. ### Claim 6 (depends on 5) The computer-implemented method of claim 5, further comprising: discarding the alternate execution timeline subsequent to performing the first action or performing the second action. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, wherein generating the alternate execution timeline further comprises: populating the alternate execution timeline with an alternate history of transactions using the history of transactions, wherein the alternate history of transactions mirrors the history of transactions. ### Claim 8 (depends on 7) The computer-implemented method of claim 7, wherein the alternate execution timeline comprises an execution space for testing the new protocol using the alternate history of transactions, wherein testing the new protocol results in an alternate change to the cloud network. ### Claim 9 (depends on 8) The computer-implemented method of claim 8, wherein the evaluation is based on determining whether the alternate change is permitted by a plurality of protocol rules associated with enforcement of policies in the cloud network. ### Claim 10 (depends on 8) The computer-implemented method of claim 8, wherein the alternate change is represented as a new transaction in the alternate history of transactions. ### Claim 11 (depends on 1) The computer-implemented method of claim 1, wherein the current execution timeline and the alternate execution timeline are generated by a bitemporal ledger in the immutable database. ### Claim 12 (depends on 1) The computer-implemented method of claim 1, wherein the history of transactions is stored in a temporal sequence on the current execution timeline, wherein the cloud network processes financial transactions associated with the user financial account, wherein the history of transactions includes a plurality of financial transactions, and wherein the temporal sequence specifies the history of transactions in order of a transaction date of each of the plurality of financial transactions. ### Claim 13 A compliance system for a cloud network, the compliance system comprising: an immutable database; a processor configured to: maintain, in the immutable database, a state of the cloud network on a current execution timeline, wherein the state of the cloud network includes a history of transactions associated with a user financial account, wherein the history of transactions includes transactions previously processed by the cloud network up to a current date; and perform the pre-provisioning check of a new protocol by: receive provisioning information associated with provisioning the new protocol in the cloud network; generate an alternate transaction based on the provisioning information; and determine whether to provision the new protocol based on an evaluation of the alternate transaction; perform a post-provisioning check of a current protocol by: receive a modification to the current protocol; generate a second alternate transaction based on the modification to the current protocol; and determine whether to provisioning the modification to the current protocol based on a second evaluation of the second alternate transaction. ### Claim 14 (depends on 13) The compliance system of claim 13, wherein performing the post-provisioning check further comprises: receiving second provisioning information associated with provisioning the modification to the current protocol in the cloud network; and generating a second alternate execution timeline based on the second provisioning information, wherein the second alternate execution timeline includes the second alternate transaction, wherein the second alternate execution timeline is separate from the current execution timeline and the alternate execution timeline. ### Claim 15 (depends on 14) The compliance system of claim 14, the processor further configured to: perform the second evaluation of the second alternate transaction, wherein the second evaluation indicates that the second alternate transaction is compliant or non-compliant with the cloud network; and determine whether to provision the modification to the current protocol based on the second evaluation. ### Claim 16 (depends on 13) The compliance system of claim 13, wherein performing the pre-provisioning check of the new protocol further comprises: generate an alternate execution timeline based on the provisioning information and the current execution timeline, wherein the alternate execution timeline includes the alternate transaction, and wherein the alternate transaction is generated based on the transactions previously processed by the cloud network up to the current date; and perform the evaluation of the an alternate transaction, wherein the evaluation indicates that the an alternate transaction is compliant or non-compliant with the cloud network. ### Claim 17 (depends on 16) The compliance system of claim 16, wherein the processor is further configured to: responsive to the evaluation indicating that the new protocol is compliant with the cloud network, perform a first action of provisioning the new protocol in the cloud network; and responsive to the evaluation indicating that the new protocol is non-compliant with the cloud network, perform a second action of preventing the provisioning of the new protocol in the cloud network. ### Claim 18 (depends on 17) The compliance system of claim 17, wherein the processor is further configured to: discard the alternate execution timeline subsequent to performing the first action or performing the second action. ### Claim 19 (depends on 13) The compliance system of claim 13, wherein in generating the alternate execution timeline, the processor is further configure to: populate the alternate execution timeline with an alternate history of transactions using the history of transactions, wherein the alternate history of transactions mirrors the history of transactions. ### Claim 20 A non-transitory computer-readable medium storing instructions, the instructions, when executed by a processor in a compliance system of a cloud network, cause the processor to perform operations comprising: maintaining, in an immutable database of the compliance system, a state of the cloud network on a current execution timeline, wherein the state of the cloud network includes a history of transactions associated with a user financial account, wherein the history of transactions includes transactions previously processed by the cloud network up to a current date; and performing the pre-provisioning check of a new protocol by: receiving provisioning information associated with provisioning the new protocol in the cloud network; generating an alternate transaction based on the provisioning information; and determining whether to provision the new protocol based on an evaluation of the alternate transaction; performing a post-provisioning check of a current protocol by: receiving a modification to the current protocol; generating a second alternate transaction based on the modification to the current protocol; and determining whether to provisioning the modification to the current protocol based on a second evaluation of the second alternate transaction.