Systems, methods, and apparatuses for implementing an SQL query and filter mechanism for blockchain stored data using distributed ledger technology (DLT)
Gespeichert in:
| Titel: | Systems, methods, and apparatuses for implementing an SQL query and filter mechanism for blockchain stored data using distributed ledger technology (DLT) |
|---|---|
| Patent Number: | 11803,537 |
| Publikationsdatum: | October 31, 2023 |
| Appl. No: | 16/777141 |
| Application Filed: | January 30, 2020 |
| Abstract: | Systems, methods, and apparatuses for implementing an SQL query and filter mechanism for blockchain stored data using Distributed Ledger Technology (DLT) in conjunction with a cloud based computing environment include operating a blockchain interface to the blockchain on behalf of a plurality of tenants of the host organization, in which each one of the plurality of tenants operate as a participating node with access to the blockchain. The system receives input for adding a plurality of authorized network participants to a declared application, updates a blockchain asset on the blockchain containing metadata for the declared application, deploys an executable install package to each of the plurality of authorized network participants for the declared application, retrieves the metadata for the declared application from the blockchain, and displays GUIs specific to the declared application which are auto generated by the executable install package based on the retrieved metadata. |
| Inventors: | Salesforce.com, Inc. (San Francisco, CA, US) |
| Assignees: | Salesforce, Inc. (San Francisco, CA, US) |
| Claim: | 1. A method performed by a system of a host organization having at least a processor and a memory therein to execute instructions, wherein the method comprises: operating a blockchain interface to a blockchain on behalf of a plurality of tenants of the host organization, wherein each one of the plurality of tenants operate as a participating node with access to the blockchain, and wherein the operating the blockchain interface on behalf of a plurality of tenants of the host organization comprises, for each tenant: receiving consent from a participating node of the tenant; and creating, based on the receiving the consent, a sidechain associated with the participating node, wherein the sidechain is formed from a fork block of the blockchain and further comprises one or more sidechain blocks, and wherein the participating node has access to the one or more sidechain blocks; receiving an SQL formatted query specifying data records stored within the blockchain; retrieving, based on the SQL formatted query, metadata from the blockchain describing a data structure for the stored records including relationships between entities within the stored records; creating RDBMS tables based on the metadata retrieved from the blockchain; building a temporary view for the stored records within a database of the host organization and formatting the temporary view in an RDBMS format based on the retrieved metadata; applying the SQL formatted query to the RDBMS tables to identify one or more block numbers associated with the blockchain; retrieving payload data from the blocks of the blockchain associated with the block numbers, wherein the payload data comprises the stored records in a native blockchain format; populating the stored records retrieved from the blockchain into the temporary view by populating the payload data into the RDBMS tables; and applying the received SQL formatted query against the RDBMS tables populated with the payload data within the temporary view in the database system of the host organization. |
| Claim: | 2. The method of claim 1 , further comprising: recording all transactions against the blockchain affecting the stored records; and replaying all transactions recorded against the temporary view to synchronize the temporary view with the blockchain when the blockchain is inaccessible. |
| Claim: | 3. The method of claim 2 , further comprising: writing the synchronized temporary view to a new blockchain to migrate the data from the first blockchain to the new blockchain. |
| Claim: | 4. The method of claim 2 , further comprising: writing the synchronized temporary view back to the blockchain to restore the stored records onto the blockchain after a catastrophic failure and data loss for the blockchain. |
| Claim: | 5. The method of claim 1 , wherein the RDBMS tables are contained within an Apex translation engine, and wherein the method further comprises: receiving the SQL formatted query at the Apex translation engine; and parsing the SQL formatted query at the Apex translation engine to identify one or more asset identifiers, wherein the asset identifiers are associated with the block numbers. |
| Claim: | 6. The method of claim 5 , further comprising: transmitting the parsed SQL query terms and the one or more asset identifiers through an Apex block translator to convert the SQL formatted query into a native blockchain protocol for payload data retrieval from the blockchain. |
| Claim: | 7. The method of claim 1 , wherein the payload data is provided to an Apex block translator to populate the RDBMS tables. |
| Claim: | 8. The method of claim 1 : wherein the payload data is retrieved from the blockchain in a hashed or serialized data format. |
| Claim: | 9. The method of claim 1 , wherein retrieving the payload data comprises retrieving the blocks of the blockchain associated with the block numbers. |
| Claim: | 10. The system of claim 1 , wherein the system is further configurable to perform operations including: recording all transactions against the blockchain affecting the stored records; replaying all transactions recorded against the temporary view to synchronize the temporary view with the blockchain when the blockchain is inaccessible; and writing the synchronized temporary view to a new blockchain to migrate the data from the first blockchain to the new blockchain or writing the synchronized temporary view back to the blockchain to restore the stored records onto the blockchain after a catastrophic failure and data loss for the blockchain. |
| Claim: | 11. The system of claim 1 : wherein the payload data is retrieved from the blockchain in a hashed or serialized data format. |
| Claim: | 12. A non-transitory computer-readable storage media having instructions stored thereupon that, when executed by a processor of a system at a host organization, the instructions cause the system to perform operations including: operating a blockchain interface to a blockchain on behalf of a plurality of tenants of the host organization, wherein each one of the plurality of tenants operate as a participating node with access to the blockchain, and wherein the operating the blockchain interface on behalf of a plurality of tenants of the host organization comprises, for each tenant: receiving consent from a participating node of the tenant; and creating, based on the receiving the consent, a sidechain associated with the participating node, wherein the sidechain is formed from a fork block of the blockchain and further comprises one or more sidechain blocks, and wherein the participating node has access to the one or more sidechain blocks; receiving an SQL formatted query specifying data records stored within the blockchain; retrieving, based on the SQL formatted query, metadata from the blockchain describing a data structure for the stored records including relationships between entities within the stored records; creating RDBMS tables based on the metadata retrieved from the blockchain; building a temporary view for the stored records within a database of the host organization and formatting the temporary view in an RDBMS format based on the retrieved metadata; applying the SQL formatted query to the RDBMS tables to identify one or more block numbers associated with the blockchain; retrieving payload data from the blocks of the blockchain associated with the block numbers, wherein the payload data comprises the stored records in a native blockchain format; populating the stored records retrieved from the blockchain into the temporary view by populating the payload data into the RDBMS tables; and applying the received SQL formatted query against the RDBMS tables populated with the payload data within the temporary view in the database system of the host organization. |
| Claim: | 13. The non-transitory computer-readable storage media of claim 12 , wherein the instructions, when executed by the processor, cause the system to perform operations further comprising: recording all transactions against the blockchain affecting the stored records; and replaying all transactions recorded against the temporary view to synchronize the temporary view with the blockchain when the blockchain is inaccessible. |
| Claim: | 14. The non-transitory computer-readable storage media of claim 13 , wherein the instructions, when executed by the processor, cause the system to perform operations further comprising: writing the synchronized temporary view to a new blockchain to migrate the data from the first blockchain to the new blockchain; or writing the synchronized temporary view back to the blockchain to restore the stored records onto the blockchain after a catastrophic failure and data loss for the blockchain. |
| Claim: | 15. The non-transitory computer-readable storage media of claim 12 , wherein the RDBMS tables are contained within an Apex translation engine, and wherein the operations further comprise: receiving the SQL formatted query at the Apex translation engine; and parsing the SQL formatted query at the Apex translation engine to identify one or more asset identifiers, wherein the asset identifiers are associated with the block numbers; and transmitting the parsed SQL query terms and the one or more asset identifiers through an Apex block translator to convert the SQL formatted query into a native blockchain protocol for payload data retrieval from the blockchain. |
| Claim: | 16. The non-transitory computer-readable storage media of claim 12 , wherein the payload data is provided to an Apex block translator to populate the RDBMS tables. |
| Claim: | 17. The non-transitory computer-readable storage media of claim 12 : wherein the payload data is retrieved from the blockchain in a hashed or serialized data format. |
| Claim: | 18. The non-transitory computer-readable storage media of claim 12 , wherein retrieving the payload data comprises retrieving the blocks of the blockchain associated with the block numbers. |
| Claim: | 19. A system to execute at a host organization, wherein the system comprises: a memory configured to store non-transitory instructions; a processor configured to execute the non-transitory instructions to cause the system to carry out operations including: operating a blockchain interface to a blockchain on behalf of a plurality of tenants of the host organization, wherein each one of the plurality of tenants operate as a participating node with access to the blockchain, and wherein the operating the blockchain interface on behalf of a plurality of tenants of the host organization comprises, for each tenant: receiving consent from a participating node of the tenant; and creating, based on the receiving the consent, a sidechain associated with the participating node, wherein the sidechain is formed from a fork block of the blockchain and further comprises one or more sidechain blocks, and wherein the participating node has access to the one or more sidechain blocks; receiving an SQL formatted query specifying data records stored within the blockchain; retrieving, based on the SQL formatted query, metadata from the blockchain describing a data structure for the stored records including relationships between entities within the stored records; creating RDBMS tables based on the metadata retrieved from the blockchain; building a temporary view for the stored records within a database of the host organization and formatting the temporary view in an RDBMS format based on the retrieved metadata; applying the SQL formatted query to the RDBMS tables to identify one or more block numbers associated with the blockchain; retrieving payload data from the blocks of the blockchain associated with the block numbers, wherein the payload data comprises the stored records in a native blockchain format; populating the stored records retrieved from the blockchain into the temporary view by populating the payload data into the RDBMS tables; and applying the received SQL formatted query against the RDBMS tables populated with the payload data within the temporary view in the database system of the host organization. |
| Claim: | 20. The system of claim 19 , wherein the operations further comprise: recording all transactions against the blockchain affecting the stored records; and replaying all transactions recorded against the temporary view to synchronize the temporary view with the blockchain when the blockchain is inaccessible. |
| Patent References Cited: | 5634053 May 1997 Noble et al. 6333929 December 2001 Drottar et al. 7587348 September 2009 Liao et al. 7730478 June 2010 Weissman 8095463 January 2012 Hartmaier 9027094 May 2015 Balazs et al. 9390154 July 2016 Baird, III 9529923 December 2016 Baird, III 9569700 February 2017 Santos et al. 9646029 May 2017 Baird, III 9690822 June 2017 Roy-Faderman 9978067 May 2018 Sadaghiani et al. 10042636 August 2018 Srivastava et al. 10311230 June 2019 Jagadeesan et al. 10373129 August 2019 James et al. 10425399 September 2019 Kravitz et al. 10482466 November 2019 Walters et al. 10505726 December 2019 Andon et al. 10521196 December 2019 Wang et al. 10521780 December 2019 Hopkins, III et al. 10541821 January 2020 Toll et al. 10701054 June 2020 Padmanabhan et al. 10728283 July 2020 Dobrek et al. 10762506 September 2020 Cash et al. 10885567 January 2021 Bhattacherjee et al. 10929866 February 2021 Qi et al. 11038771 June 2021 Padmanabhan 11184394 November 2021 Dobrek et al. 11244313 February 2022 Padmanabhan et al. 20050102159 May 2005 Mondshine 20060118611 June 2006 Michelsen et al. 20060259361 November 2006 Barhydt et al. 20080066165 March 2008 Rosenoer 20090037949 February 2009 Birch 20110265069 October 2011 Fee 20110276892 November 2011 Jensen-Horne 20110289140 November 2011 Pletter et al. 20130041934 February 2013 Annamalaisami et al. 20130226682 August 2013 Grossman 20130346173 December 2013 Chandoor 20140039990 February 2014 Georgi 20140278894 September 2014 Toumayan et al. 20140279857 September 2014 Bharadwaj 20150026061 January 2015 Siegel et al. 20160027229 January 2016 Spanos et al. 20160042383 February 2016 Joshi et al. 20160092872 March 2016 Prakash et al. 20160148251 May 2016 Thomas et al. 20160337400 November 2016 Gupta 20160350860 December 2016 Dintenfass et al. 20160358267 December 2016 Arjomand et al. 20160364743 December 2016 St. Lawrence et al. 20170005804 January 2017 Zinder 20170046698 February 2017 Haldenby et al. 20170085545 March 2017 Lohe et al. 20170103167 April 2017 Shah 20170132625 May 2017 Kennedy 20170132630 May 2017 Castinado et al. 20170140145 May 2017 Shah 20170200157 July 2017 Bergeon et al. 20170206603 July 2017 Al-Masoud 20170236215 August 2017 Eisen et al. 20170289111 October 2017 Voell et al. 20170295021 October 2017 Gutiérrez et al. 20170295023 October 2017 Madhavan et al. 20170300627 October 2017 Giordano et al. 20170300872 October 2017 Brown et al. 20170300876 October 2017 Musiala, Jr. et al. 20170337534 November 2017 Goeringer 20170344988 November 2017 Cusden et al. 20170353309 December 2017 Gray 20170364549 December 2017 Abalos 20170372300 December 2017 Dunlevy et al. 20180005186 January 2018 Hunn 20180006831 January 2018 Toll et al. 20180019879 January 2018 Kravitz et al. 20180026505 January 2018 Galmiche et al. 20180039667 February 2018 Pierce 20180041345 February 2018 Maim 20180082256 March 2018 Tummuru et al. 20180088928 March 2018 Smith et al. 20180123779 May 2018 Zhang 20180139186 May 2018 Castagna 20180144042 May 2018 Sheng et al. 20180158162 June 2018 Ramasamy 20180165416 June 2018 Saxena et al. 20180189100 July 2018 Nemoto et al. 20180191503 July 2018 Alwar et al. 20180204213 July 2018 Zappier et al. 20180218176 August 2018 Voorhees et al. 20180225611 August 2018 Daniel et al. 20180232644 August 2018 Acharya et al. 20180232659 August 2018 Ranatunga et al. 20180239897 August 2018 Ventura 20180247191 August 2018 Katz et al. 20180253661 September 2018 Strauss 20180260212 September 2018 Wisnovsky 20180262505 September 2018 Ligatti 20180268401 September 2018 Ortiz et al. 20180268506 September 2018 Wodetzki et al. 20180276553 September 2018 Redkar et al. 20180276626 September 2018 Laiben 20180307990 October 2018 Chawla et al. 20180323963 November 2018 Stollman 20180365686 December 2018 Kondo 20180367528 December 2018 Schwarz et al. 20190012249 January 2019 Mercuri et al. 20190012595 January 2019 Beser et al. 20190019090 January 2019 Chacko et al. 20190028276 January 2019 Pierce et al. 20190034404 January 2019 Anderson et al. 20190035018 January 2019 Nolan et al. 20190042619 February 2019 Baird, III 20190050855 February 2019 Martino et al. 20190052454 February 2019 Wright et al. 20190058709 February 2019 Kempf et al. 20190081796 March 2019 Chow et al. 20190086988 March 2019 He et al. 20190087598 March 2019 Adkins et al. 20190087892 March 2019 Pinski et al. 20190102409 April 2019 Shi et al. 20190102423 April 2019 Little et al. 20190108543 April 2019 Chan et al. 20190109702 April 2019 Maggu et al. 20190109713 April 2019 Clark 20190122186 April 2019 Kano et al. 20190147532 May 2019 Singh et al. 20190149325 May 2019 Garagiola et al. 20190149334 May 2019 Velden 20190158270 May 2019 Berti 20190164156 May 2019 Lindemann 20190164220 May 2019 Raj et al. 20190172282 June 2019 Patel 20190182047 June 2019 Andreina et al. 20190188706 June 2019 McCurtis 20190215149 July 2019 Ramasamy et al. 20190228006 July 2019 Tormasov et al. 20190236559 August 2019 Padmanabhan 20190236562 August 2019 Padmanabhan 20190236598 August 2019 Padmanabhan 20190236606 August 2019 Padmanabhan et al. 20190238316 August 2019 Padmanabhan 20190238525 August 2019 Padmanabhan et al. 20190268147 August 2019 Baird, III 20190287026 September 2019 Calmon et al. 20190287116 September 2019 Karantzis 20190295114 September 2019 Pavletic et al. 20190303121 October 2019 Padmanabhan 20190303445 October 2019 Padmanabhan 20190303579 October 2019 Reddy et al. 20190306235 October 2019 Veale et al. 20190334716 October 2019 Kocsis et al. 20190361917 November 2019 Tran 20190370634 December 2019 Moreno et al. 20190370866 December 2019 Lawbaugh et al. 20190377806 December 2019 Padmanabhan et al. 20190385160 December 2019 Safak et al. 20190386834 December 2019 Furukawa 20200019923 January 2020 Santhar et al. 20200027005 January 2020 Harrison et al. 20200027090 January 2020 Braundmeier 20200042939 February 2020 Padmanabhan 20200050613 February 2020 Gauvreau, Jr. 20200057860 February 2020 Patil et al. 20200074477 March 2020 Lamba et al. 20200074515 March 2020 Ghatage et al. 20200076574 March 2020 Austin et al. 20200089672 March 2020 Velisetti et al. 20200089895 March 2020 Gollogly 20200104636 April 2020 Halevi et al. 20200118011 April 2020 Kaiser et al. 20200133955 April 2020 Padmanabhan et al. 20200134656 April 2020 Padmanabhan 20200143267 May 2020 Gidney 20200169546 May 2020 Padmanabhan 20200186338 June 2020 Andon et al. 20200234386 July 2020 Blackman et al. 20200250174 August 2020 Padmanabhan et al. 20200250176 August 2020 Padmanabhan 20200250177 August 2020 Padmanabhan 20200250295 August 2020 Padmanabhan 20200250683 August 2020 Padmanabhan et al. 20200250747 August 2020 Padmanabhan 20200252205 August 2020 Padmanabhan 20200252404 August 2020 Padmanabhan 20200252406 August 2020 Padmanabhan et al. 20200336475 October 2020 Padmanabhan et al. 20200344132 October 2020 Padmanabhan 20200357084 November 2020 Hunn et al. 20210152535 May 2021 Padmanabhan et al. 20210152536 May 2021 Padmanabhan et al. 20210182423 June 2021 Padmanabhan 20210226774 July 2021 Padmanabhan 20210243193 August 2021 Padmanabhan 20220006705 January 2022 Padmanabhan 108021986 May 2018 109173261 January 2019 2019800219289 September 2020 197071681 August 2020 2020541893 July 2020 2016161073 October 2016 2018007827 January 2018 2018007828 January 2018 2018194707 October 2018 2018230581 December 2018 2019152750 August 2019 |
| Other References: | Final Office Action for U.S. Appl. No. 15/885,803 dated Nov. 17, 2021, 28 pages. cited by applicant Final Office Action for U.S. Appl. No. 15/885,811, dated Feb. 3, 2022, 38 pages. cited by applicant Final Office Action for U.S. Appl. No. 15/932,092 dated Sep. 27, 2021, 25 pages. cited by applicant Final Office Action for U.S. Appl. No. 15/932,099 dated Nov. 1, 2021, 35 pages. cited by applicant Mandal, S., “A Framework for Modular Norm Extraction, Modeling, and Reasoning,” [Doctoral dissertation, University of Nebraska], 2017, 151 pages, ProQuest Dissertations Publishing. cited by applicant Non-final Office Action for U.S. Appl. No. 16/399,920, dated Feb. 17, 2022, 66 pages. cited by applicant Non-final Office Action for U.S. Appl. No. 16/777,409 dated Oct. 4, 2021, 42 pages. cited by applicant Non-final Office Action for U.S. Appl. No. 16/917,506, dated Oct. 4, 2021, 44 pages. cited by applicant Norta, A. et al., “Self-Aware Agent Supported Contract Management on Blockchains for Legal Accountability,” 2017, 37 pages. cited by applicant Notice of Allowance for U.S. Appl. No. 16/177,300, dated Oct. 6, 2021, 14 pages. cited by applicant Notice of Allowance for U.S. Appl. No. 16/264,653 dated Sep. 29, 2021, 17 pages. cited by applicant Notice of Allowance for U.S. Appl. No. 16/683,932 dated Dec. 3, 2021, 9 pages. cited by applicant Office Action for U.S. Appl. No. 15/885,811 dated Aug. 4, 2021, 26 pages. cited by applicant Office Action for U.S. Appl. No. 16/177,305 dated Sep. 16, 2021, 42 pages. cited by applicant Office Action for U.S. Appl. No. 16/264,645 dated Oct. 27, 2021, 46 pages. cited by applicant Office Action for U.S. Appl. No. 16/399,913, dated Dec. 24, 2021, 51 pages. cited by applicant “BigchainDB 2.0 the Blockchain Database,” Berlin Germany dated May 2018, 14 pages. cited by applicant “Deloitte IoT Powered by Blockchain”, dated May 2017, 20 pages. cited by applicant “How Creating Digital Twins in Blockchain Will Protect Brands?”, dated Nov. 15, 2018, 4 pages. cited by applicant “How Smart Certificates of Authenticity Improve Asset Management”, Jan. 17, 2019, 4 pages. cited by applicant “Nasdaq, Using Blockchain Track Assets Proof Ownership”, dated Nov. 30, 2016, 30 pages. cited by applicant Azaria, A., et al “MedRec: Using Blockchain for Medical Data Access and Permission Management,” 2016 2nd Int'l Conference on Open and Big Data, IEEE, (Aug. 22, 2016), pp. 25-30. cited by applicant Final Office Action for U.S. Appl. No. 15/885,803, dated Jul. 20, 2020, 29 pages. cited by applicant Final Office Action for U.S. Appl. No. 15/885,811, dated Aug. 5, 2020, 45 pages. cited by applicant Final Office Action for U.S. Appl. No. 15/932,092 dated Jun. 22, 2020, 42 pages. cited by applicant Final Office Action for U.S. Appl. No. 15/932,099 dated Jun. 1, 2020, 26 pages. cited by applicant Genestier, P., et al, “Blockchain for Consent Management in the eHealth Environment: A Nugget for Privacy and Security Challenges,” Journal of the Int'l Society for Telemedicine and eHealth, (Jan. 1, 2017), 4 pages. cited by applicant International Search Report and Written Opinion for Application No. PCT/US2019/036103, dated Aug. 1, 2019, 12 pages. cited by applicant International Search Report and Written Opinion for Application No. PCT/US2020/01561B dated May 11, 2020, 13 pages. cited by applicant International Search Report and Written Opinion for International Patent Application No. PCT/US2019/016199, dated Apr. 2, 2019, 12 pages. cited by applicant McConaghy et al., “BigchainDB: A Scalable Blockchain Database (Draft)” dated Jun. 8, 2016, 64 Pages. cited by applicant Notice of Allowance for U.S. Appl. No. 15/932,100 dated Feb. 20, 2020, 5 pages. cited by applicant Notice of Allowance for U.S. Appl. No. 15/940,646, dated Oct. 31, 2019, 8 pages. cited by applicant Notice of allowance for U.S. Appl. No. 16/264,653 dated Nov. 23, 2020, 16 pages. cited by applicant Office Action for U.S. Appl. No. 15/885,803 dated Jan. 8, 2020, 47 pages. cited by applicant Office Action for U.S. Appl. No. 15/885,811 dated Jan. 17, 2020, 40 pages. cited by applicant Office Action for U.S. Appl. No. 15/932,092 dated Jan. 22, 2020, 36 pages. cited by applicant Office Action for U.S. Appl. No. 15/932,099, dated Oct. 3, 2019, 26 pages. cited by applicant Office Action for U.S. Appl. No. 15/932,100, dated Nov. 8, 2019, 9 pages. cited by applicant Office Action for U.S. Appl. No. 15/940,646, dated Apr. 29, 2019, 7 pages. cited by applicant Office Action for U.S. Appl. No. 16/177,305 dated Jul. 23, 2020, 41 pages. cited by applicant Office Action for U.S. Appl. No. 16/264,657, dated Sep. 18, 2020, 33 pages. cited by applicant Office Action for U.S. Appl. No. 16/683,945 dated Sep. 14, 2020, 26 Pages. cited by applicant Office Action for EP Application No. 19707168.1 dated Sep. 24, 2020, 3 pages. cited by applicant Ojha, “Chaincode for Go Developers, Part 1: Writing Blockchain Chaincode in Go for Hyperledger Fabric v0.6,” 2017, 15 pages. cited by applicant Peterson, K., et al, “A Blockchain-Based Approach to Health Information Exchange Networks,” (Aug. 8, 2016), Retrieved from the Internet: URL: http://kddlab.zjgsu.edu.cn:7200/research/blockchain/huyiyang-reference/A%20Blockchain-Based%20Approach%20to%20Health%20Information%20Exchange.pdf, Retrieved on Mar. 21, 2019), 10 pages. cited by applicant Salesforce, “Force.com Apex Code Developer's Guide,” version 34.0, 2015, 1000 pages. cited by applicant Sandgaard, J., et al, “MedChain White Paper V1.1” (Oct. 1, 2017), Retrieved from the Internet: URL:https://www.medchain.global/doc/Medchain%20Whitepaper%20v1.1.pdf, Retrieved on Mar. 21, 2019, 54 pages. cited by applicant Using Sawtooth with Docker: Configuring the List of Transaction Families, Apr. 6, 2018, 13 pages. cited by applicant Wikipedia, “Federate database system,” Jun. 8, 2016, https://en.wikipedia.org/w/index.php/?title=Federated%20database%20system&oldid=808166410, 6 pages. cited by applicant Wikipedia, “Solidity,” Feb. 2, 2017, https://web.archive.org/web/2017020202304/https://en.wikipeida.org/wiki/Solidity (Year: 2017), 3 pages. cited by applicant Zyskind, G., et al, “Decentralizing Privacy: Using Blockchain to Protect Personal Data,” 2015 IEEE Security and Privacy Workshops (May 1, 2015), 5 pages. cited by applicant U.S. Appl. No. 17/153,872, filed Jan. 20, 2021, Prithvi Krishnan Padmanabhan. cited by applicant U.S. Appl. No. 17/163,547, filed Jan. 31, 2021, Prithvi Krishnan Padmanabhan. cited by applicant U.S. Appl. No. 17/348,286, filed Jun. 15, 2021, Prithvi Krishnan Padmanabhan. cited by applicant U.S. Appl. No. 62/840,074, filed Apr. 29, 2019, Prithvi Krishnan Padmanabhan. cited by applicant Bendor-Samuel, P. (2017) Blockchain-enabled “smart-contracts” solve problems in administering IT ecosystem services, CIO, 3 pages. cited by applicant Final Office Action for U.S. Appl. No. 15/932,099 dated Jun. 1, 2020, 27 pages. cited by applicant Final Office Action for U.S. Appl. No. 16/177,305 dated Feb. 2, 2021, 47 pages. cited by applicant Final Office Action for U.S. Appl. No. 16/264,657 dated May 17, 2021, 36 pages. cited by applicant Non-final Office Action for U.S. Appl. No. 16/177,305 dated Jul. 23, 2020, 52 pages. cited by applicant Normans Media Ltd., Smart Contracts: Blockchain-based contracts that don't require lawyers. 2016, 4 pages. cited by applicant Notice of Allowance for U.S. Appl. No. 16/264,653 dated Jun. 7, 2021, 21 pages. cited by applicant Notice of Allowance for U.S. Appl. No. 16/683,945, dated Feb. 10, 2021, 14 pages. cited by applicant Office Action for U.S. Appl. No. 15/885,803, dated Apr. 14, 2021, 31 pages. cited by applicant Office Action for U.S. Appl. No. 15/932,092 Mar. 17, 2021, 23 pages. cited by applicant Office Action for U.S. Appl. No. 16/177,300 dated Jun. 16, 2021, 80 pages. cited by applicant Office Action for U.S. Appl. No. 16/683,945, dated Sep. 14, 2020, 18 pages. cited by applicant Shukla, A., et al., “Smart Contracts for Multiagent Plan Execution in Untrusted Cyber-physical Systems,” 2018 IEEE 25th International Conference on High Performance Computing Workshops (HiPCW), 10 pages. cited by applicant |
| Assistant Examiner: | Ohba, Mellissa M. |
| Primary Examiner: | Ng, Amy |
| Attorney, Agent or Firm: | Polygon IP, LLP |
| Dokumentencode: | edspgr.11803537 |
| Datenbank: | USPTO Patent Grants |
| Abstract: | Systems, methods, and apparatuses for implementing an SQL query and filter mechanism for blockchain stored data using Distributed Ledger Technology (DLT) in conjunction with a cloud based computing environment include operating a blockchain interface to the blockchain on behalf of a plurality of tenants of the host organization, in which each one of the plurality of tenants operate as a participating node with access to the blockchain. The system receives input for adding a plurality of authorized network participants to a declared application, updates a blockchain asset on the blockchain containing metadata for the declared application, deploys an executable install package to each of the plurality of authorized network participants for the declared application, retrieves the metadata for the declared application from the blockchain, and displays GUIs specific to the declared application which are auto generated by the executable install package based on the retrieved metadata. |
|---|