# US 11,907,944 B2 · Managing pre-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 11,907,944 B2 - Document ID: US11907944B2 - Status: Granted - Kind: B2 - Application number: 17/516,340 - Filed: 2021-11-01 - Published: 2022-09-08 - Granted: 2024-02-20 - 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/US11907944B2 ## 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 pre-provisioning checks of resources, such as network protocols, prior to 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. ## Claims ### Claim 1 A computer-implemented method for improving protocol compliance in a cloud network by performing a pre-provisioning check on a new protocol, the method comprising: storing a current execution timeline of the cloud network, wherein the current execution timeline includes a current resource scope of the cloud network; receiving, at a compliance system associated with the cloud network, a request to provision a new protocol in the cloud network; and prior to provisioning the new protocol in the cloud network, initiating, by the compliance system, a pre-provisioning evaluation of the new protocol, wherein initiating the pre-provisioning evaluation comprises: duplicating the current resource scope to an alternate resource scope in an alternate execution timeline; providing provisioning data associated with the new protocol, wherein the provisioning data comprises information to provision the new protocol in the cloud network; running the new protocol on the alternate resource scope in the alternate execution timeline; and collecting a result of running the new protocol on the alternate resource scope. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, wherein the result indicates an alternate impact on the current resource scope of the cloud network. ### Claim 3 (depends on 2) The computer-implemented method of claim 2, further comprising: responsive to the alternate impact indicating that the new protocol is compliant with the cloud network, applying the new protocol to the current execution timeline of the cloud network; and responsive to the alternate impact indicating that the new protocol is non-compliant with the cloud network, preventing application of the new protocol to the current execution timeline of the cloud network. ### Claim 4 (depends on 3) The computer-implemented method of claim 3, wherein when the alternate impact identifies at least one resource that violates the current resource scope of the cloud network, the alternate impact indicates that the new protocol is non-compliant with the cloud network. ### Claim 5 (depends on 3) The computer-implemented method of claim 3, further comprising: responsive to the alternate impact indicating that the new protocol is non-compliant with the cloud network, returning a failure message indicating that the new protocol was prevented from being applied to the current execution timeline. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, further comprising: receiving a query for the current execution timeline of the cloud network; and returning, responsive to the query, the current resource scope, wherein the current resource scope indicates a plurality of policies that are provisioned in compliance with the cloud network. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, wherein the request is a hook call from a pre-provisioning interface, wherein the pre-provisioning interface is implemented separately from the compliance system. ### Claim 8 A compliance system for a cloud network, the compliance system comprising: a memory; a processor configured to: store a current execution timeline of the cloud network, wherein the current execution timeline includes a current resource scope of the cloud network; receive, at the compliance system associated with the cloud network, a request to provision a new protocol in the cloud network; and prior to provisioning the new protocol in the cloud network, initiate, by the compliance system, a pre-provisioning evaluation of the new protocol, wherein to initiate the pre-provisioning evaluation, the processor is further configured to: duplicate the current resource scope to an alternate resource scope in an alternate execution timeline; provide provisioning data associated with the new protocol, wherein the provisioning data comprises information to provision the new protocol in the cloud network; run the new protocol on a hypothetical resource scope in a hypothetical execution timeline; and collect a result of running the new protocol on the hypothetical resource scope. ### Claim 9 (depends on 8) The system of claim 8, wherein the result indicates a hypothetical impact on the current resource scope of the cloud network. ### Claim 10 (depends on 9) The system of claim 9, the processor is further configured to: responsive to the hypothetical impact indicating that the new protocol is compliant with the cloud network, apply the new protocol to the current execution timeline of the cloud network; and responsive to the hypothetical impact indicating that the new protocol is non-compliant with the cloud network, prevent application of the new protocol to the current execution timeline of the cloud network. ### Claim 11 (depends on 10) The system of claim 10, wherein when the hypothetical impact identifies at least one resource that violates the current resource scope of the cloud network, the hypothetical impact indicates that the new protocol is non-compliant with the cloud network. ### Claim 12 (depends on 10) The system of claim 10, the processor is further configured to: responsive to the hypothetical impact indicating that the new protocol is non-compliant with the cloud network, return a failure message indicating that the new protocol was prevented from being applied to the current execution timeline. ### Claim 13 (depends on 8) The system of claim 8, the processor is further configured to: receive a query for the current execution timeline of the cloud network; and return, responsive to the query, the current resource scope, wherein the current resource scope indicates a plurality of policies that are provisioned in compliance with the cloud network. ### Claim 14 (depends on 8) The system of claim 8, wherein the request is a hook call from a pre-provisioning interface, wherein the pre-provisioning interface is implemented separately from the compliance system. ### Claim 15 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: storing a current execution timeline of the cloud network, wherein the current execution timeline includes a current resource scope of the cloud network; receiving, at the compliance system associated with the cloud network, a request to provision a new protocol in the cloud network, wherein the compliance system comprises a maintenance module, a collection module, and an evaluation module; prior to provisioning the new protocol in the cloud network, initiating, by the maintenance module, a pre-provisioning evaluation of the new protocol, wherein initiating the pre-provisioning evaluation comprises: duplicating the current resource scope to a hypothetical resource scope in a hypothetical execution timeline; providing provisioning data associated with the new protocol, wherein the provisioning data comprises information to provision the new protocol in the cloud network; running the new protocol on the hypothetical resource scope in the hypothetical execution timeline; and collecting a result of running the new protocol on the hypothetical resource scope. ### Claim 16 (depends on 15) The non-transitory computer-readable medium of claim 15, wherein the result indicates a hypothetical impact on the current resource scope of the cloud network. ### Claim 17 (depends on 16) The non-transitory computer-readable medium of claim 16, the operations further comprising: responsive to the hypothetical impact indicating that the new protocol is compliant with the cloud network, applying the new protocol to the current execution timeline of the cloud network; and responsive to the hypothetical impact indicating that the new protocol is non-compliant with the cloud network, preventing application of the new protocol to the current execution timeline of the cloud network. ### Claim 18 (depends on 17) The non-transitory computer-readable medium of claim 17, wherein when the hypothetical impact identifies at least one resource that violates the current resource scope of the cloud network, the hypothetical impact indicates that the new protocol is non-compliant with the cloud network. ### Claim 19 (depends on 17) The non-transitory computer-readable medium of claim 17, the operations further comprising: responsive to the hypothetical impact indicating that the new protocol is non-compliant with the cloud network, returning a failure message indicating that the new protocol was prevented from being applied to the current execution timeline. ### Claim 20 (depends on 15) The non-transitory computer-readable medium of claim 15, the operations further comprising: receiving a query for the current execution timeline of the cloud network; and returning, responsive to the query, the current resource scope, wherein the current resource scope indicates a plurality of policies that are provisioned in compliance with the cloud network.