US 12,273,463 B2
Technologies for blockchain-based data transparency and authentication
Archana Sekar, Chennai (IN); Javier Villalobos, Menlo Park, CA (US); and Yochai Konig, San Francisco, CA (US)
Assigned to Genesys Cloud Services, Inc., Menlo Park, CA (US)
Filed by Genesys Cloud Services, Inc., Menlo Park, CA (US)
Filed on Aug. 18, 2023, as Appl. No. 18/452,446.
Application 18/452,446 is a continuation of application No. 17/029,846, filed on Sep. 23, 2020, granted, now 11,757,651.
Prior Publication US 2023/0396446 A1, Dec. 7, 2023
Int. Cl. H04L 9/14 (2006.01); H04L 9/08 (2006.01); H04L 9/32 (2006.01); H04L 9/00 (2022.01)
CPC H04L 9/3247 (2013.01) [H04L 9/0825 (2013.01); H04L 9/0861 (2013.01); H04L 9/14 (2013.01); H04L 9/50 (2022.05)] 17 Claims
OG exemplary drawing
 
1. A system for conducting a data transaction between a first contact center system and a second contact center system using a permissioned blockchain infrastructure that includes one or more nodes, wherein each of the first contact center system and the second contact center system comprises at least one respective node of the one or more nodes of the permissioned blockchain infrastructure, the system comprising:
at least one processor; and
at least one memory comprising a plurality of instructions stored thereon that, in response to execution by the at least one processor, causes the system to:
receive at the first contact center system a request for data from an end user;
determine, via the first contact center system, that the second contact center system possesses the data requested by the end user in response to a determination that the first contact center system does not possess the data requested by the end user;
transmit the request for data from the first contact center system to the second contact center system in response to the determination that the second contact center system possesses the data requested by the end user;
provide the data requested by the end user from the second contact center system to the first contact center system by (i) generating a block representing the data transaction in the permissioned blockchain infrastructure; (ii) publishing the block to the one or more nodes in the permissioned blockchain infrastructure; (iii) validating the data transaction at the one or more nodes in the permissioned blockchain infrastructure; (iv) adding the block to a blockchain based on a consensus reached among the one or more nodes in the permissioned blockchain infrastructure; (v) updating the one or more nodes in the permissioned blockchain infrastructure with the block; and (vi) labeling the data transaction as successful; and
transmit, via the first contact center system, the data requested by the end user and received from the second contact center system via the permissioned blockchain infrastructure to the end user;
wherein the block includes self-executing computer-executable code of a smart contract which is configured to monitor one or more conditions associated with the blockchain.