WO2020061226A1 - Field-based peer permissions in a blockchain network - Google Patents

Field-based peer permissions in a blockchain network Download PDF

Info

Publication number
WO2020061226A1
WO2020061226A1 PCT/US2019/051783 US2019051783W WO2020061226A1 WO 2020061226 A1 WO2020061226 A1 WO 2020061226A1 US 2019051783 W US2019051783 W US 2019051783W WO 2020061226 A1 WO2020061226 A1 WO 2020061226A1
Authority
WO
WIPO (PCT)
Prior art keywords
peer
exchange
tenant
permission
field
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2019/051783
Other languages
English (en)
French (fr)
Inventor
Prithvi Krishnan Padmanabhan
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Salesforce Inc
Original Assignee
Salesforce com Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Salesforce com Inc filed Critical Salesforce com Inc
Priority to JP2021515119A priority Critical patent/JP7268140B2/ja
Priority to AU2019345041A priority patent/AU2019345041A1/en
Priority to CN201980076006.8A priority patent/CN113168622B/zh
Priority to EP19782823.9A priority patent/EP3853794A1/en
Publication of WO2020061226A1 publication Critical patent/WO2020061226A1/en
Anticipated expiration legal-status Critical
Priority to AU2023216803A priority patent/AU2023216803A1/en
Priority to AU2025248682A priority patent/AU2025248682A1/en
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/10—File systems; File servers
    • G06F16/18—File system types
    • G06F16/182—Distributed file systems
    • G06F16/1834—Distributed file systems implemented based on peer-to-peer networks, e.g. gnutella
    • G06F16/1837—Management specially adapted to peer-to-peer storage networks
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/901—Indexing; Data structures therefor; Storage structures
    • G06F16/9024—Graphs; Linked lists
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3821—Electronic credentials
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • H04L63/123—Applying verification of the received information received data contents, e.g. message integrity
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/006—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols involving public key infrastructure [PKI] trust models
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0618—Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/06—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols the encryption apparatus using shift registers or memories for block-wise or stream coding, e.g. DES systems or RC4; Hash functions; Pseudorandom sequence generators
    • H04L9/0643—Hash functions, e.g. MD5, SHA, HMAC or f9 MAC
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
    • H04L9/3236—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions
    • H04L9/3239—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials using cryptographic hash functions involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
    • H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees

Definitions

  • One or more implementations relate to the field of data management; and more specifically, to assigning and enforcing peer-based permissions to fields of data stored in a peer- to-peer blockchain network.
  • a blockchain is a continuously expanding list of records/blocks that are linked and secured using cryptography.
  • every block in a blockchain may include a cryptographic hash of the immediately preceding block, a timestamp for the current block, and transaction data (e.g., the addition/modification of information associated with a peer in a blockchain network).
  • transaction data e.g., the addition/modification of information associated with a peer in a blockchain network.
  • the blockchain may be shared and managed through a peer-to- peer network via a system of verifying/validating new blocks to be added to the chain such that a block in a blockchain cannot be altered without alteration of all subsequent blocks, which requires network consensus.
  • This architecture allows for security of information stored within blocks through the use of cryptography; sharing/distribution of information through the use of peer-to-peer networks; trust through the use of consensus of block addition; and immutability of information stored within blocks through the use of cryptography, chaining/linking of blocks, and peer distribution (e.g., each peer in the blockchain network may maintain a ledger of all verified/validated transactions in the network).
  • a multi-tenant cloud architecture In contrast to a blockchain architecture, a multi-tenant cloud architecture relies on centralization of information in a common database or other data structure.
  • cloud- based architectures provide many benefits in comparison to blockchain architectures, including the ability to remove many management functions from tenants and instead focus these functions on a centralized system, these architectures do not provide the same level of security, trust, and immutability of information during inter-tenant communications of data.
  • blockchain architectures provide many benefits, including those described above, these architectures do not allow for secrecy between peers or enforcement of other access
  • each piece of information in a block of a peer-ledger is visible to all peers in a blockchain network and each peer has the same permissions/privileges in the blockchain network.
  • Figure 1 shows a block diagram illustrating a computing environment, including a multi-tenant server, according to one example implementation.
  • Figure 2 shows a method for the multi-tenant server to manage data in a peer-to-peer blockchain network, according to one example implementation.
  • Figure 3A shows the computing environment, including a set of separate blockchain services per tenant system, according to one example implementation.
  • Figure 3B shows the computing environment, including a set of shared blockchain services, according to another example implementation.
  • Figure 4 shows physical objects corresponding to a set of tenant systems, according to one example implementation.
  • Figure 5 shows an exchange object, including a set of mappings between exchange fields and fields of physical objects, according to one example implementation.
  • Figure 6 shows security objects for each of the tenant systems, according to one example implementation.
  • Figure 7 shows an example of a shadow object corresponding to a tenant system, according to one example implementation.
  • Figure 8 shows an example of a transaction object, according to one example implementation.
  • Figure 9 shows an example of a blockchain, including a set of entries/blocks, according to one example implementation.
  • Figure 10A shows an electronic device according to one example implementation.
  • Figure 10B shows a block diagram of an environment where the computing environment and the server may be implemented according to one example implementation.
  • FIG. 1 is a block diagram illustrating a computing environment 100, according to one example implementation.
  • the computing environment 100 includes tenant systems 102i- 1023, a multi -tenant server 104, and a set of communications networks 106.
  • the tenant systems 102i-102 3 may be part of a peer-to-peer blockchain network 108 and the multi -tenant server 104 provides a cloud environment to manage data and transactions of the tenant systems 102i-102 3 in the peer-to-peer blockchain network 108 via a transaction queue 104A, tenant level objects 104B, network level objects 104C, and blockchain services 104D, including a security service 112.
  • the blockchain services 104D may generate mapping data that maps fields of physical objects of tenant systems 102 to exchange fields, which are used for processing transactions in the peer-to- peer blockchain network 108. Additionally, the blockchain services 104D may generate public and private keys for each tenant system 102 in the blockchain network 108 and assign/enforce permissions/privileges in relation to exchange fields using these keys. Namely, exchange fields may be encrypted using private and/or public keys of tenant systems 102 that are permitted to access these fields and separate sets of keys may be provided to corresponding tenant systems 102 for different permission/privilege levels.
  • a transaction generator 1 lOi of the tenant system 102i may generate a request to (1) add/insert a new record to/into a physical object associated with the tenant system 102i or (2) modify/update an existing record of the physical object associated with the tenant system 102i.
  • the physical object may include a set of fields for each record and is stored in a portion/partition of the tenant level objects 104B of the multi -tenant server 104 associated with the tenant system 102i such that the physical object is only accessible to the tenant system 102i (e.g., the tenant system 1022 and the tenant system l02 3 are not permitted to read or write to the physical object of the tenant system 102i).
  • the request may cause the addition of a record in a shadow object in the portion/partition of the tenant level objects 104B associated with the tenant system 102i.
  • the shadow object represents uncommitted data to the physical object (i.e., data for which a consensus amongst the peers/tenants in the peer-to-peer blockchain network 108 has not yet been achieved).
  • the shadow object may be used by the transaction queue 104 A for generating a transaction object, which will be distributed/made available to the other tenant systems 1022 and l02 3 for receiving consensus for the proposed addition/modification to the physical object of the tenant system l02i.
  • the set of fields of the transaction object is a subset of the fields of the physical object and the set of fields of the transaction object are defined by an exchange object, which is included in the network level objects 104C.
  • the exchange object may include a set of exchange fields, which will be included in the transaction object, and each exchange field of the exchange object may be mapped to a field in the physical objects of the tenant systems 102i-1023.
  • a physical object of the tenant system 102i may include fields A-D
  • a physical object of the tenant system 1022 may include fields E-H
  • a physical object of the tenant system 1023 may include fields I-K.
  • a first exchange field of the exchange object of the peer-to-peer blockchain network 108 may be mapped to the field B of the tenant system 102i, the field F of the tenant system l02 2 , and the field I of the tenant system 1023.
  • a second exchange field of the exchange object of the peer-to-peer blockchain network 108 may be mapped to the field C of the tenant system 102i, the field E of the tenant system 1022. and the field J of the tenant system 1023.
  • the corresponding transaction object when a proposal for adding/modifying a record for the physical object of the tenant system 102i is received, the corresponding transaction object includes the first exchange field with a value from field B of the proposed physical/shadow object and the second exchange field with a value from field C of the proposed physical/shadow object.
  • the exchange object provides a uniform transaction object via mapping metadata for verification/validation purposes in the peer-to-peer blockchain network 108 while allowing the tenant system 102i to only reveal particular portions of information to other tenants/peers in the peer-to-peer blockchain network 108 (e.g., sensitive information/fields in physical objects may not be included in transaction objects which are distributed amongst tenant systems 102i-1023 in the peer-to-peer blockchain network 108 and later included in distributed ledgers).
  • the multi-tenant server 104 may perform many of the functions of the peer-to-peer blockchain network 108 on behalf of the tenant systems 102i-1023.
  • the multi -tenant server 104 may include a virtual space/organization for each of the tenant systems 102i-1023.
  • Each virtual space/organization may include data and
  • each virtual space/organization may include tenant level objects 104B corresponding to respective tenants/tenant systems 102i-1023 and separate instantiations of or access to blockchain services 104D.
  • the virtual space/organization for each tenant system 102I-1023 may perform one or more blockchain functions/operations on behalf of the corresponding tenant system 102i-1023.
  • the multi -tenant server 104 may generate a shadow object record in the virtual space/organization of the tenant system 102i within the multi-tenant server 104.
  • a transaction queue 104A may generate a transaction object corresponding to the record in the shadow object using the exchange object of the peer-to-peer blockchain network 108, such that the transaction object includes exchange fields with data from the shadow object, and a set of cryptographic keys of the tenant system 102i such that the transaction object may be distributed or otherwise be made available to virtual
  • the security service 112 of the blockchain services 104D may encrypt each exchange field of a transaction object based on permission/privilege levels of each tenant system 102. For example, the security service 112 may determine that the tenant system 102i has read, update, and insert permissions/privileges for first and second exchange fields. In contrast, the tenant system 1022 may only have read permission for the first exchange field and read and update permissions for the second exchange field. Lastly, the tenant system l02 3 may have no permissions/privi privileges in relation to the first exchange field and read, update, and insert privileges for the second exchange field.
  • the security service 112 may generate a first set of keys for the tenant system 102i, a second set of keys for the tenant system 1022, and a third set of keys for the tenant system l02 3 based on the private and public keys of the tenant system 102i-102 3 and the assigned permission/privilege levels.
  • the first set of keys allow the tenant system 102i to read, update, and insert data in relation to the first and second exchange fields;
  • the second set of keys allow the tenant system l02 2 to read the first exchange field and read and update the second exchange field;
  • the third set of keys allow the tenant system l02 3 to read, update, and insert data in relation to the second exchange field.
  • the security service 112 of the multi -tenant server 104 provides permission/privilege level control of data in the blockchain network 108.
  • the virtual spaces/organizations of the other tenant systems 1022 and l02 3 may thereafter analyze the transaction object to determine whether validation/verification is appropriate.
  • the transaction queue 104A may wait for validation/verification from the virtual spaces/organizations of the tenant systems 1022 and l02 3 such that consensus for the proposed alteration to the physical object of the tenant system 102i is achieved.
  • a virtual space/organization of a leader tenant system 102i-102 3 may (1) add a record or modify a record (as appropriate) in a corresponding physical object and (2) add a corresponding entry /block to a distributed ledger of the leader tenant system 102i-102 3 .
  • the virtual space/organization of a leader tenant system 102i-102 3 may transmit a request to the virtual spaces/organizations of the other/remaining tenant systems 102i- l02 3 to commit the change to their physical objects (based on a mapping defined in the exchange object) and/or add a corresponding entry /block to a ledger of these tenant systems 102I-1023.
  • the cloud environment provided by the multi -tenant server 104 e.g., the virtual spaces/organizations provided by the multi -tenant server 104
  • the security service 112 encrypts exchange fields such that permissions/privileges (e.g., read, update, and insert permissions/privileges) may be enforced per peer/tenant system 102 and per exchange field.
  • the computing environment 100 of Figure 1 may include more elements than those shown in Figure 1. Accordingly, the computing environment 100 of Figure 1 is purely for illustrative purposes.
  • the tenant systems 102i-1023 and the multi -tenant server 104 may be connected through a set of one or more communication networks 106.
  • the set of one or more communication networks 106 may be, for example, a local area network (LAN), a wide area network (WAN), a global area network (GAN), such as the Internet, or a combination of such networks.
  • LAN local area network
  • WAN wide area network
  • GAN global area network
  • the tenant systems 102I-1023 and the multi -tenant server 104 may maintain a direct connection to each other via a wired or wireless medium.
  • Each of the tenant systems 102i-1023 may be a computing system that may be operated by one or more users.
  • each of the tenant systems 102i-1023 may be a personal computer (PC), a workstation, a laptop computer, a tablet computer, a mobile phone, a smartphone, a personal digital assistant (PDA), or the like.
  • the tenant systems 102i-1023 may communicate with the multi-tenant server 104 to modify/add/store and retrieve data.
  • the tenant systems 102i-1023 may each include a screen/display (e.g., a liquid crystal (LCD) display) for presenting an interface (e.g., a graphical user interface (GUI)) to a user, including an interface presented in a web page.
  • a screen/display e.g., a liquid crystal (LCD) display
  • GUI graphical user interface
  • each of the tenant systems 102i-1023 may include a corresponding transaction generator 1 IOi-I I O3 for receiving inputs from a user to alter a physical object associated with the tenant system 102i-1023 (e.g., addition of a new record in the physical object or modification of an existing record in the physical object) and triggering the process of obtaining consensus (e.g., verification/validation) from the other tenant systems 102i-1023 in the peer-to-peer blockchain network 108 for the alteration.
  • a corresponding transaction generator 1 IOi-I I O3 for receiving inputs from a user to alter a physical object associated with the tenant system 102i-1023 (e.g., addition of a new record in the physical object or modification of an existing record in the physical object) and triggering the process of obtaining consensus (e.g., verification/validation) from the other tenant systems 102i-1023 in the peer-to-peer blockchain network 108 for the alteration.
  • the tenant systems 102i-1023 may each be associated with one or more
  • users of the tenant system 102i may be customers of a first organization/tenant and a user of the tenant system 1023 may be a customer of a second organization/tenant.
  • Organizations/tenants may be any firm, corporation, institution, association, or society that has contracted with an administrator of the multi -tenant server 104 to provide users access to data stored therein via the tenant systems 102i-102 3 .
  • the multi -tenant server 104 may be any computing device that provides users access to resources via the tenant systems 102i-102 3 and the communication network(s) 106.
  • the multi-tenant server 104 may provide users of the tenant systems 102i-102 3 access to data in one or more physical objects and/or one or more corresponding distributed peer ledgers that describe changes to the physical objects.
  • a physical object of the tenant system 102i may correspond to a medical lab report.
  • the records in the physical object may include a lab report identifier field, a patient name field, a lab network identifier field, a lab test identifier field, a patient identifier field, and a social security number field.
  • the multi -tenant server 104 uses the transaction queue 104A, the tenant level objects 104B, the network level objects 104C, and the blockchain services 104D to attempt to make these alterations in the peer-to-peer blockchain network 108 (e.g., alterations reflected in physical objects and distributed ledgers associated with the tenant systems 102i-102 3 ).
  • the multi -tenant server 104 may include various elements of hardware and software of a multi-tenant system.
  • the term“multi-tenant system” refers to those systems in which various elements of hardware and software may be shared by one or more tenants.
  • the multi -tenant server 104 may simultaneously process requests for a great number of tenants, and a given database table may store records for a potentially much greater number of tenants.
  • the multi -tenant server 104 may include an application platform including a framework (e.g., services and metadata) that allows applications to execute, such as the hardware or software infrastructure of the system.
  • the multi-tenant server 104 includes separate virtual spaces/organizations (sometimes referred to as portions or partitions) for data/objects as well as services of each tenant system 102i-102 3 .
  • each tenant system 102i-102 3 may be assigned a separate virtual space/organization.
  • Each virtual space/organization is a logical partition within the multi-tenant server 104 and includes separate tenant level objects 104B that are only accessible to that tenant system 102i-102 3 and are inaccessible to other tenant systems 102i-102 3 (e.g., tenant systems 102i-102 3 cannot read and/or write tenant level objects 104B of another tenant system 102i-102 3 ) in addition to services used by the multi -tenant server 104 on behalf of the corresponding tenant system 102i- 1023 (e.g., blockchain services 104D).
  • tenant level objects 104B that are only accessible to that tenant system 102i-102 3 and are inaccessible to other tenant systems 102i-102 3 (e.g., tenant systems 102i-102 3 cannot read and/or write tenant level objects 104B of another tenant system 102i-102 3 ) in addition to services used by the multi -tenant server 104 on behalf of the corresponding tenant system 102i- 1023 (e.g., blockchain services 104D).
  • the peer-to-peer blockchain network 108 may include the tenant systems 102i-102 3 , which each represent tenants/peers.
  • the peer-to-peer blockchain network 108 shown in Figure 1 is a representation of peers/tenants within the blockchain network 108.
  • the peer-to-peer blockchain network 108 may be viewed as a distributed network that is controlled by the multi -tenant server 104 with inputs/requests from the tenant systems 102i-102 3 .
  • the multi -tenant server 104 may perform various functions/operations on behalf of the tenant systems 102i-102 3 .
  • the multi -tenant server 104 may perform blockchain functions/operations on behalf on the tenant systems 102i-102 3 using the blockchain services 104D.
  • the blockchain functions/operations may be performed in separate virtual spaces/organizations associated with respective tenant systems 102I-102 3 .
  • the peer-to-peer blockchain network 108 may include more or fewer tenants/peers.
  • the peer-to-peer blockchain network 108 may include two, four, five, or more tenants/peers with corresponding tenant systems 102. Accordingly, the use of three tenants/peers is for illustrative purposes.
  • the multi -tenant server 104 to manage data in the peer-to- peer blockchain network 108.
  • the multi -tenant cloud environment provided by the multi -tenant server 104 may be used for managing permissions/privileges of tenant systems 102I-1023 for data in the peer-to-peer blockchain network 108.
  • the method 200 will be described in relation to the example computing environment 100 shown in Figure 1, the example computing environment 300A shown in Figure 3A, and/or the example computing environment 300B shown in Figure 3B. However, in other words, in other words
  • the method 200 may operate in other environments, including different implementations of the multi -tenant server 104.
  • the method 200 may commence at operation 202 with the membership service 302A of the blockchain services 104D determining and/or adding a set of tenants (sometimes referred to as peers) to the peer-to-peer blockchain network 108.
  • the peer-to-peer blockchain network 108 is identified in the network object 304A and the tenants for the peer-to-peer blockchain network 108 are identified in the peers object 304B (e.g., tenants represented by identifiers of the tenant system 102i-l 023).
  • the membership service 302A may determine a set of tenants in the peer-to-peer blockchain network 108 by examining the peers object 304B at operation 202.
  • adding a tenant/tenant system 102i-1023 to the peer-to-peer blockchain network 108 may require consensus through a process of verification/validation from the current tenants/tenant systems 102i-1023 in the peer-to-peer blockchain network 108.
  • the membership service 302A determines at operation 202 that the peer-to-peer blockchain network 108 includes the tenant systems 102i-1023, which represent tenants/peers.
  • each of the tenant systems 1021-1023 may include a separate virtual space/organization within the multi -tenant server 104.
  • Each virtual space/organization includes separate tenant level objects 104B that are only accessible to that tenant system 1021-1023 and is inaccessible to other tenant systems 102i-1023 (e.g., tenant systems 102i-1023 cannot read and/or write tenant level objects 104B of another tenant system 102i-l 023), in addition to services used by the multi-tenant server 104 on behalf of the corresponding tenant systems 102i- 1023 (e.g., blockchain services 104D).
  • each tenant system 102I-1023 may be associated with a separate virtual space/organization 314i-3143 with corresponding tenant level objects 104Bi-104B3 (e.g., physical objects 306I-3063, shadow objects 308I-3083, peer ledgers 310i-3 IO3, and mapping objects 316i-3163) and blockchain services l04Di-l04D3.
  • tenant level objects 104Bi-104B3 e.g., physical objects 306I-3063, shadow objects 308I-3083, peer ledgers 310i-3 IO3, and mapping objects 316i-3163
  • blockchain services l04Di-l04D3 e.g., physical objects 306I-3063, shadow objects 308I-3083, peer ledgers 310i-3 IO3, and mapping objects 316i-3163
  • each virtual space/organization 314i-3143 may instead have separate access to a single instantiation of the blockchain services 104D as shown in Figure 3B.
  • the membership service 302A may generate a set of public keys (PKs) and private/secret keys (SKs) for each tenant/tenant system 102i-1023 in the peer-to-peer blockchain network 108.
  • the public keys are generated based on a determined private key.
  • a one-way cryptographic hash function e.g., SHA256
  • the public keys and the private/secret keys may be stored by the membership service 302A in the wallet object 304C following generation at operation 204.
  • the transaction queue 104 A may utilize the private/secret keys stored in the wallet object 304C for generating transaction objects and sets of permission keys for each of the tenant systems 102i-1023.
  • the public keys and private/secret keys may be used by the transaction queue 104A for implementing cryptographic elements of transactions used by the peer-to-peer blockchain network 108 and the security service 112 may use the permission keys for enforcing permission/privileges of tenant systems l02i-l02 3 .
  • the membership service 302A may determine an exchange object for the peer-to-peer blockchain network 108.
  • the exchange object is defined by a set of exchange fields and mapping metadata that defines mappings between each exchange field and fields in physical objects of the tenant systems 102i-1023.
  • Figure 4 shows physical objects 306I-3063 for the tenant systems 102i-1023, respectively.
  • the physical object 306i corresponding to the tenant system 102i, includes records 404I-404M, which are composed of fields 406I-406N, and each record 404I-404M includes values 408I,I-M,N for each field 406I-406N.
  • the physical object 3062 corresponding to the tenant system 1022.
  • the physical object 3063 corresponding to the tenant system 1023, includes records 4l6i-4l6Q, which are composed of fields 4l8i-4l8s, and each record 4l6i-4l6Q includes values 420I,I-Q,S for each field 4l8i-4l8s.
  • Each of the physical objects 306I-3063 may represent any type of data.
  • the tenant system 102i may operate in or otherwise correspond to a medical laboratory.
  • the physical object 306i may represent medical lab reports (e.g., each of the records 404I-404M may correspond to separate medical lab reports).
  • the tenant system 1022 may operate in or otherwise correspond to a doctor’s office.
  • the physical object 3062 may represent a patient file (e.g., each of the records 4101 -41 ()G may correspond to separate patient files).
  • the membership service 302A may determine an exchange object 502 as shown in Figure 5, which may be stored in the digital assets object 304D.
  • the exchange object 502 is defined by the exchange fields 504I-5043 and the mapping metadata that maps exchange fields 504 to fields of physical objects 306.
  • the exchange field 504i maps to the field 406 2 of the physical object 306i, the field 412H of the physical object 306 2 , and the field 418 2 of the physical object 3063.
  • the exchange field 504 2 maps to the field 406N of the physical object 306i and the field 4l2i of the physical object 306 2 , and the field 418i of the physical object 3063.
  • the exchange field 5043 maps to the field 406i of the physical object 306i and the field 4l2 2 of the physical object 306 2 . Accordingly, the mapping metadata of the exchange object 502 maps/links exchange fields 504 to fields of physical objects 306.
  • the number of exchange fields 504I-5043 i.e., three is less than (1) the number of fields 406I-406N in the physical object 306i (i.e., N), (2) the number of fields 412I-412H in the physical object 306 2 (i.e., H), and/or (3) the number of fields 4l8i-4l8s in the physical object 3063 (i.e., S). Accordingly, a generated transaction object, which will be distributed amongst the tenant systems 1021-1023, and corresponding data/information included in distributed peer ledgers 310 may not include sensitive data.
  • the mapping of exchange fields 504 to fields 406, 412, and 418 of physical objects 306I-3063 indicates a relationship between the fields 406, 412, and 418 of physical objects 306i- 3063.
  • the field 406 2 of the physical object 306i may correspond to a patient identifier for which a corresponding medical lab report was generated and the field 412H of the physical object 306 2 may correspond to a patient identifier for which a corresponding patient file represents.
  • these fields 406 2 and 412H are mapped to the same exchange field 504i, indicating that these fields 406 2 and 412H represent similar data (e.g., the fields 406 2 and 412H both represent patient identifiers).
  • each tenant/tenant system 102i-1023 may be part of multiple blockchain networks, including the blockchain network 108. Each of these blockchain networks may include overlapping membership with the blockchain network 108 and/or may include additional peers/tenant systems 102.
  • the network object 304A may include identifiers for each blockchain network managed by the multi -tenant server 104
  • the peers object 304B may include identifiers for each peer/tenant system 102 in the blockchain networks managed by the multi -tenant server 104
  • the wallet object 304C may include keys for each peer/tenant system 102 in the blockchain networks managed by the multi -tenant server 104
  • the digital assets object 304D may include exchange objects 502 for each blockchain network managed by the multi -tenant server 104.
  • the tenant level objects 104B for each tenant system 102 may include a mapping object 316.
  • Each mapping object 316 includes the mapping metadata for the corresponding tenant system 102.
  • the mapping object 3l6i which corresponds to the tenant system 102i, includes mapping metadata that maps exchange field 504i to field 406 2 of the physical object 306i;
  • mapping object 3 162. which corresponds to the tenant system 1022. includes mapping metadata that maps exchange field 504i to field 412H of the physical object 306 2 ; exchange field 504 2 to field 4l2i of the physical object 306 2 ; and exchange field 504 3 to field 4l2 2 of the physical object 306 2 .
  • mapping object 3l6 3 which corresponds to the tenant system l02 3 , includes mapping metadata that maps exchange field 504i to field 4182 of the physical object 306 3 and exchange field 504 2 to field 4181 of the physical object 3063. Accordingly, each mapping object 316 only includes mapping metadata associated with a corresponding tenant system 102.
  • the security service 112 may determine permissions/privileges (sometimes referred to as permission/privilege levels) per each exchange field 504 and tenant system 102.
  • the blockchain network 108 may offer read, update, and insert privileges per each exchange field 504.
  • the security service 112 may determine that the tenant system 102i has read, update, and insert permissions for the exchange fields 504i- 5043.
  • the tenant system l02 2 may only have read permission for the exchange field 504i and read and update permissions for the exchange fields 504 2 and 5043.
  • the tenant system 1023 may have no permissions/privileges in relation to the exchange field 504i and read, update, and insert privileges for the exchange fields 504 2 and 5043.
  • the determination of privileges/permissions at operation 208 may be based on an indication from an administrator or a subscription level of the tenant systems 102.
  • the security service 112 may generate a set of permissions keys for each tenant system 102.
  • the sets of permissions keys may be used by or on behalf of the tenant systems 102 for accessing one or more exchange fields 504.
  • each set of permission keys may include a separate key for each exchange field 504 and each
  • FIG. 6 shows security objects 318i-3183 for each of the tenant systems 102i-1023, respectively.
  • sets of keys 604i- 6043 are provided per exchange field 504 for each permission/privilege level 606 associated with a corresponding tenant system 102.
  • These sets of keys 604I-6043 may be generated based on one or more of the public and private keys of each respective tenant system 102 and may be used for reading, updating, and inserting exchange fields 504 into the blockchain network 108 via corresponding transaction objects and peer ledgers 310.
  • the transaction management service 302B of the blockchain services 104D may receive (1) a proposed new record to add to a physical object 306I-3063 or (2) a modification to an existing record of a physical object 306I-3063.
  • the physical object 306i may correspond to medical lab reports and the transaction management service 302B of the virtual space/organization 3l4i may receive a request to add/insert a new lab report record 404 at operation 212 from the tenant system 102i.
  • the physical object 306i may correspond to medical lab reports and the transaction management service 302B of the virtual space/organization 3l4i may receive a request to modify an existing lab report record 404 at operation 212 from the tenant system 102i.
  • the method 200 will be described in relation to the transaction management service 302B of the virtual space/organization 3l4i receiving a request to add/insert a record to the physical object 306i at operation 212 from the tenant system 102i.
  • the method 200 may work in a similar fashion for modification of a physical object 306.
  • the security service 112 may determine if the tenant system 102i has adequate permissions/privileges to perform the received request from operation 212 (i.e., the security service 112 determines whether the tenant system 102i is authorized to add/insert a new lab report record 404). In one implementation, this determination is based on the security object 318i, which includes keys for each permission/privilege level 606 of the tenant system 102i.
  • the security service 112 may determine at operation 214 that the tenant system 102i does not have adequate permissions/privi privileges to perform the received request from operation 212 and the method 200 may move to operation 216 to reject the request from operation 212.
  • the security service 112 may determine at operation 214 that the tenant system 102i has adequate
  • permissions/privileges to perform the received request from operation 212 and the method 200 may move to operation 218.
  • the transaction management service 302B of the virtual space/organization 3l4i generates a record in a shadow object 308i corresponding to the received request (i.e., the new record) of operation 212.
  • the shadow object 308i may correspond to the tenant system 102i and may include all the fields 406I-406N of the physical object 306i.
  • the shadow object 308i represents un-committed data to the physical object 306i.
  • the data in the shadow object 308i of the tenant system 102i needs to be validated/verified through consensus by the other tenant systems 102 and 102 before being committed to the physical object 306i and represented by the peer ledger 310i of the tenant system 102i.
  • This committal and representation may also extend to the physical objects 3062 and 306 3 and peer ledgers 3l0 2 and 310 3 of the tenant systems 1022 and l02 3 as will be described in greater detail below.
  • FIG. 7 shows an example of a shadow object 308i corresponding to the tenant system 102i and the physical object 306i, according to one example implementation.
  • the shadow object 308i includes two records 704i and 7042. corresponding to two separate proposed alterations to the physical object 306i.
  • the first record 704i corresponds to the addition/insertion of a record 404 in the physical object 306i
  • the second record 704r corresponds to the modification/update of one or more field values 408 for the newly added/inserted record 404 in the physical object 306i.
  • the first record 704i may propose the addition/insertion of a record 404 corresponding to a medical lab report
  • the second record 704r may propose the modification of several fields values 408 of the new medical lab report record 404 (e.g., modification/update of a field value 408 corresponding to the status of the medical lab report).
  • the event management service 302C and/or the transaction queue 104A may generate a transaction object based on (1) the record 704i added to the shadow object 308i at operation 218 and (2) the exchange object 502 of the peer-to-peer blockchain network 108.
  • the transaction object may include values for each of the exchange fields 504I-504 3 and data/field values from the record 704i added to the shadow object 308i at operation 218 in corresponding exchange fields 504I-504 3 .
  • Figure 8 shows an example of a transaction object 802, according to one example implementation.
  • the transaction object 802 includes all the exchange fields 504I-504 3 of the exchange object 502 and field values 706 from the record 704i in the shadow object 308i in the appropriate positions based on the mapping between exchange fields 504i- 504 3 and fields 406 of the physical object 306i.
  • a separate transaction object 802 may be generated for the record 7042.
  • the transaction object 802 which will be used hereinafter for purposes of illustration, may be passed or otherwise made available to the other tenant systems 1022 and l02 3 to determine if there is consensus in the blockchain network 108 to commit the proposed record 404 (e.g., to verify/validate the transaction object 802).
  • generation of the transaction object 802 may include adding a signature to the transaction object based on (1) the record 704i from the shadow object 308i, (2) a unique assigned identifier of the transaction object 802 (e.g., an identifier assigned sequentially to transaction objects 802 as they are generated), and (3) the private key of the tenant system 102i (i.e., the private key of the tenant system 102 proposing the alteration).
  • the record 704i and the unique assigned identifier of the transaction object 802 may be merged or otherwise combined together to form a single message and the private key of the tenant system 102i may be used to encrypt the message (e.g., using a one-way cryptographic hash function, such as SHA256) to form a digital signature.
  • the transaction object 802 includes the record 704i from the shadow object 308i along with the signature generated using the private key of the tenant system 102i.
  • the security service 112 may separately encrypt each exchange field 504 of the transaction object 802 using (1) the private key of the tenant system 102i (i.e., the private key of the tenant system 102 proposing the alteration); (2) a permission key of each tenant system 102 that has a permission/privilege 606 related to the exchange field 504 (i.e., permission keys of tenant systems 102 that have read, update, and/or insert privileges associated with the exchange fields 504); and/or (3) a public key of each tenant system 102 that has a permission/privilege related to the exchange field 504.
  • the private key of the tenant system 102i i.e., the private key of the tenant system 102 proposing the alteration
  • a permission key of each tenant system 102 that has a permission/privilege 606 related to the exchange field 504 i.e., permission keys of tenant systems 102 that have read, update, and/or insert privileges associated with the exchange fields 504
  • permission keys of each tenant system 102 that has a permission/privilege related to the exchange field 504 ensures that only these tenant systems 102 have access (e.g., read access) to corresponding exchange fields 504.
  • private keys, public keys, and/or permission keys may be used along with a cryptographic function (e.g., SHA256) to generate encrypted data.
  • the event management service 302C and the transaction queue 104A may make the transaction object 802 available to the other tenant systems 102 and 1023.
  • making the transaction object 802 available to the other tenant systems 1022 and l02 3 includes the transaction queue 104 A placing the transaction object 802 in a portion/partition of the multi-tenant server 104 accessible to the tenant systems 1022 and l02 3 .
  • the multi-tenant server 104 may include a separate virtual space/organization 314 for each of the tenant systems 102i-102 3 .
  • Each virtual space/organization 314 for each of the tenant systems 102i-102 3 .
  • the multi tenant server 104 may pass the transaction object 802 from the virtual space/organization 3l4i of the tenant system 102i to the virtual spaces/organizations 3142 and 3l4 3 of the tenant systems l02 2 and l02 3 such that the virtual spaces/organizations 3 142 and 3l4 3 of the tenant systems 1022 and 1023 can process/analyze the transaction object 802 for possible vabdation/verification.
  • exchange fields 504 may be encrypted using private keys, public keys, and/or permission keys, only those tenant systems 102 with read access to an exchange field 504 may be able to determine the contents of that exchange field 504.
  • the transaction management service 302B may monitor responses from the tenant systems l02 2 and l02 3 to determine if consensus has been reached regarding the transaction object 802 or if consensus has failed to be reached.
  • the consensus management service 302D may define the threshold or rules for use by the transaction management service 302B in determining when consensus has been reached by the tenant systems l02 2 and l02 3 regarding the transaction object 802. For example, in some
  • the consensus management service 302D may indicate that consensus requires all of the tenant systems l02 2 and l02 3 to verify/validate the transaction object 802, while in other implementations, the consensus management service 302D may indicate that consensus requires a majority of the tenant systems l02 2 and l02 3 to verify/validate the transaction object 802.
  • the consent management service 302E indicates the rules and/or operations used by the tenant systems l02 2 and l02 3 , and in particular the virtual
  • the consent management service 302E may indicate that the public key of the tenant system 102i is used along with the signature and message in the transaction object 802 for determining whether the transaction object 802 originated from and was authorized by the tenant system 102i.
  • the transaction management service 302B and the transaction queue 104A may discard the transaction object 802 in response to failing to obtain consensus from the tenant systems l02 2 and l02 3 (e.g., failing to obtain consensus as defined/indicated by the consensus management service 302D).
  • discarding the transaction object 802 may include indicating to the tenant system 102i that the transaction object 802 and corresponding alteration to the physical object 306i (i.e., addition of a new record 404 to the physical object 306i or modification of an existing record 404 to the physical object 306i) has been rejected by the peer-to-peer blockchain network 108 (i.e., consensus in the peer-to-peer blockchain network 108 was not achieved/obtained).
  • the virtual space/organization 3l4i may delete the record 704i in the shadow object 308i corresponding to the transaction object 802.
  • the transaction management service 302B may commit the transaction object 802 and/or the record 704i in the shadow object 308i corresponding to the transaction object 802 for which consensus was achieved on behalf of a leader tenant system 102I-1023.
  • a leader tenant system 102i-1023 may be randomly selected from amongst the tenant systems 102i-1023 in the peer-to-peer blockchain network 108 by the membership service 302A.
  • the transaction management service 302B in the virtual space/organization 3l4i of the tenant system 102i may commit the record 704i in the shadow object 308i, which corresponds to the transaction object 802 for which consensus was achieved, on behalf of the tenant system 102i at operation 220.
  • committal may include adding the record 704i from the shadow object 308i to the physical object 306i.
  • committal may include adding a record 410/416 to or modifying a record 410/416 in the physical object 306 2 /3063 that includes the field values 706 from the shadow object 308i mapped to corresponding fields 412/418 in the physical objects 3062/3063 as indicated by the exchange object 502 or corresponding mapping object 316.
  • the transaction management service 302B may add an entry /block in the peer ledger 310i-3 I O3 corresponding to the transaction object 802 on behalf the leader tenant system 102i-1023.
  • the transaction management service 302B of the virtual space/organization 314i-3143 of the leader tenant system 102i-1023 may add an entry /block in the peer ledger 310i-3103 corresponding to the transaction object 802 on behalf the leader tenant system 102i-1023.
  • the entry /block added to the peer ledger 310i-3 I O3 may include several pieces of information.
  • each entry /block 904I-904T in the peer ledger 3 lOi may include a reference to the previous entry /block 904 in the peer ledger 3 lOi, the transaction object 802 (along with one or more other transaction objects), and a nonce (i.e., an arbitrary number used to meet a requirement of the peer-to-peer blockchain network 108).
  • the transaction management service 302B and/or the transaction queue 104A may transmit a request or otherwise trigger the other tenant systems 102i-1023 on behalf of the leader tenant system 102i-1023 to commit the transaction object 802 to
  • the space/organization 314i-3143 of the leader tenant system 102i-1023 passes or otherwise makes available a request or otherwise triggers the transaction management service 302B of the virtual spaces/organizations 314i-3143 of the other tenant systems 102i-1023 to commit the transaction object 802 to corresponding physical objects 306I-3063 and add a block/entry to corresponding peer ledgers 310i-3103.
  • the peer ledgers 310i-3103 allow the computing environments 100, 300A, and/or 300B to maintain the transparency and auditability of data.
  • the multi -tenant server 104 provides immutability to each transaction by recording/reflecting the transaction in the peer ledgers 310i-3 IO3, which are replicated across all the tenant systems 102I-1023.
  • the tenant systems 102i-1023 participate in a consensus mechanism to verify/validate transactions/transaction objects 802 and only after the
  • the peer ledgers 3 IO1-3IO3 may be stored in a Merkle directed acyclic graph (DAG) structure.
  • the Merkle DAG may be represented in an Oracle and/or HBase store.
  • relevant physical objects 306I-3063 will be updated with the most recent data in the peer ledgers 310i-3 IO3.
  • the peer ledgers 310i-3 IO3 may also hold data describing the tenants/tenant systems 102i-1023 that can view data or otherwise operate in the peer-to-peer blockchain network 108.
  • one or more tenant systems 102 may attempt to read one or more exchange fields 504 in a corresponding peer ledger 310.
  • the transaction object 802 that was added to the peer ledgers 310i-3103 of the tenant systems 102i-1023 in the example above included the exchange fields 504I-5043.
  • each of the tenant systems 102I-1023 have assigned permission/privilege levels, which are indicated in corresponding security objects 318i-3183. Accordingly, permission/privilege levels of tenant systems 102i- 1023 in relation to exchange fields 504 are independent.
  • the virtual space/organization 3l4i of the tenant system 102i may attempt to read the exchange field 504i of a transaction object 802 stored in the peer ledger 3 lOi. Since the security object 3181 of the tenant system 102i includes a permission key for reading the exchange field 504i (i.e., KEY_A), the virtual space/organization 3l4i of the tenant system 102i will be able to successfully to decode the value in the exchange field 504i for the transaction object 802 stored in the peer ledger 310i based on this permission key (i.e., KEY_A).
  • KEY_A permission key for reading the exchange field 504i
  • the security object 3182 of the tenant system l02 2 includes a permission key for reading the exchange field 504i (i.e., KEY_J)
  • the virtual space/organization 3l4 2 of the tenant system l02 2 will be able to successfully to decode the value in the exchange field 504i for the transaction object 802 stored in the peer ledger 3l0 2 based on this permission key (i.e., KEY_J).
  • the security object 3183 of the tenant system 1023 does not include a permission key for reading the exchange field 504i, the virtual space/organization 3143 of the tenant system l02 3 will not be able to successfully to decode the value in the exchange field 504i for the transaction object 802 stored in the peer ledger 310 3 .
  • the method 200 allows the multi -tenant server 104 to manage data in the peer-to-peer blockchain network 108 on behalf of the tenant systems 102i-102 3 .
  • the cloud environment provided by the multi -tenant server 104 may be used for securing data in transaction objects 802 stored in peer ledgers 310 such that unauthorized users/tenants/peers cannot view sensitive data.
  • the computing environments 300A and/or 300B may be built on top of a platform 312 comprised of services and/or metadata for implementing the other components of the multi -tenant server 104.
  • the blockchain services 104D may include additional services, such as a coin service 302F for tracking records and items associated with each tenant/peer.
  • the term“user” is a generic term referring to an entity (e.g., an individual person) using a system and/or service.
  • a multi-tenant architecture provides each tenant with a dedicated share of a software instance and the ability (typically) to input tenant specific data for user management, tenant-specific functionality, configuration, customizations, non-functional properties, associated applications, etc. Multi-tenancy contrasts with multi instance architectures, where separate software instances operate on behalf of different tenants.
  • a tenant includes a group of users who share a common access with specific privileges to a software instance providing a service.
  • a tenant may be an organization (e.g., a company, department within a company, etc.).
  • a tenant may have one or more roles relative to a system and/or service.
  • CRM customer relationship management
  • a tenant may be a vendor using the CRM system or service to manage information the tenant has regarding one or more customers of the vendor.
  • DAAS Data as a Service
  • one set of tenants may be vendors providing data and another set of tenants may be customers of different ones or all of the vendors’ data.
  • one set of tenants may be third party application developers providing applications/services and another set of tenants may be customers of different ones or all of the third-party application developers.
  • a user may have one or more roles relative to a system and/or service.
  • a user may be a representative (sometimes referred to as an“end user”) of a tenant (e.g., a vendor or customer), a representative (e.g., an administrator) of the company providing the system and/or service, and/or a representative (e.g., a programmer) of a third-party application developer that is creating and maintaining an application(s) on a Platform as a Service (PAAS).
  • PAAS Platform as a Service
  • An electronic device also referred to as a computing device, computer, etc.
  • An electronic device includes hardware and software, such as a set of one or more processors coupled to one or more machine-readable storage media (e.g., magnetic disks, optical disks, read only memory (ROM), Flash memory, phase change memory, solid state drives (SSDs)) to store code (which is composed of software instructions and which is sometimes referred to as computer program code or a computer program) for execution on the set of processors and/or to store data.
  • machine-readable storage media e.g., magnetic disks, optical disks, read only memory (ROM), Flash memory, phase change memory, solid state drives (SSDs)
  • code which is composed of software instructions and which is sometimes referred to as computer program code or a computer program
  • an electronic device may include non-volatile memory (with slower read/write times, e.g., magnetic disks, optical disks, read only memory (ROM), Flash memory, phase change memory, SSDs) and volatile memory (e.g., dynamic random access memory (DRAM), static random access memory (SRAM)), where the non-volatile memory persists code/data even when the electronic device is turned off or when power is otherwise removed, and the electronic device copies that part of the code that is to be executed by the set of processors of that electronic device from the non-volatile memory into the volatile memory of that electronic device during operation because volatile memory typically has faster read/write times.
  • non-volatile memory with slower read/write times, e.g., magnetic disks, optical disks, read only memory (ROM), Flash memory, phase change memory, SSDs
  • volatile memory e.g., dynamic random access memory (DRAM), static random access memory (SRAM)
  • an electronic device may include a non-volatile memory (e.g., phase change memory) that persists code/data when the electronic device is turned off, and that has sufficiently fast read/write times such that, rather than copying the part of the code/data to be executed into volatile memory, the code/data may be provided directly to the set of processors (e.g., loaded into a cache of the set of processors); in other words, this non-volatile memory operates as both long term storage and main memory, and thus the electronic device may have no or only a small amount of volatile memory for main memory.
  • a non-volatile memory e.g., phase change memory
  • typical electronic devices can transmit code and/or data over one or more machine-readable transmission media (also called a carrier) (e.g., electrical, optical, radio, acoustical or other form of propagated signals - such as carrier waves, infrared signals).
  • machine-readable transmission media also called a carrier
  • typical electronic devices also include a set of one or more physical network interface(s) to establish network connections (to transmit and/or receive code and/or data using propagating signals) with other electronic devices.
  • an electronic device may store and transmit (internally and/or with other electronic devices over a network) code and/or data with one or more machine-readable media (also referred to as computer-readable media).
  • Electronic devices are used for a variety of purposes.
  • an electronic device (sometimes referred to as a server electronic device) may execute code that cause it to operate as one or more servers used to provide a service to another electronic device(s)
  • client electronic device (sometimes referred to as a client electronic device, a client computing device, or a client device) that executes client software (sometimes referred to as client code or a tenant system) to communicate with the service.
  • client software sometimes referred to as client code or a tenant system
  • the server and client electronic devices may be operated by users respectively in the roles of administrator (also known as an administrative user) and end user.
  • Figure 10A is a block diagram illustrating an electronic device 1000 according to some example implementations.
  • Figure 10A includes hardware 1020 comprising a set of one or more processor(s) 1022, a set of one or more network interfaces 1024 (wireless and/or wired), and non-transitory machine-readable storage media 1026 having stored therein software 1028 (which includes instructions executable by the set of one or more processor(s) 1022).
  • Each of the previously described tenant systems 102 and the transaction queue 104 A, the tenant level objects 104B, the network level objects 104C, and the blockchain services 104D may be implemented in one or more electronic devices 1000.
  • each of the tenant systems 102 is implemented in a separate one of the electronic devices 1000 (e.g., in user electronic devices operated by users where the software 1028 represents the software to implement tenant systems 102 to interface with the transaction queue 104A, the tenant level objects 104B, the network level objects 104C, and the blockchain services 104D (e.g., a web browser, a native client, a portal, a command-line interface, and/or an application program interface (API) based upon protocols such as Simple Object Access Protocol (SOAP),
  • SOAP Simple Object Access Protocol
  • the electronic devices 1000 e.g., a set of one or more server electronic devices where the software 1028 represents the software to implement the transaction queue 104 A, the tenant level objects 104B, the network level objects 104C, and the blockchain services 104D; and 3) in operation, the electronic devices implementing the tenant systems 102 and the transaction queue 104 A, the tenant level objects 104B, the network level objects 104C, and the blockchain services 104D would be communicatively coupled (e.g., by a network) and would establish between them (or through one or more other layers) connections for submitting a proposed new record or a proposed modification to an existing record in a physical object to the multi -tenant server 104.
  • Other configurations of electronic devices may be used in other implementations (e.g., an implementation in which the tenant systems 102 and the multi -tenant server 104 are implemented on a single electronic device 1000).
  • the set of one or more processor(s) 1022 typically execute software to instantiate a virtualization layer 1008 and software container(s) 1004A-R (e.g., with operating system-level virtualization, the
  • virtualization layer 1008 represents the kernel of an operating system (or a shim executing on a base operating system) that allows for the creation of multiple software containers 1004A-R (representing separate user space instances and also called virtualization engines, virtual private servers, or jails) that may each be used to execute a set of one or more applications; with full virtualization, the virtualization layer 1008 represents a hypervisor (sometimes referred to as a virtual machine monitor (VMM)) or a hypervisor executing on top of a host operating system, and the software containers 1004A-R each represent a tightly isolated form of a software container called a virtual machine that is run by the hypervisor and may include a guest operating system; with para-virtualization, an operating system or application running with a virtual machine may be aware of the presence of virtualization for optimization purposes).
  • VMM virtual machine monitor
  • an instance of the software 1028 (illustrated as instance 1006 A) is executed within the software container 1004A on the virtualization layer 1008.
  • instance 1006A on top of a host operating system is executed on the“bare metal” electronic device 1000.
  • the instantiation of the instance 1006 A, as well as the virtualization layer 1008 and software containers 1004A-R if implemented, are collectively referred to as software instance(s) 1002.
  • a network device is an electronic device that communicatively interconnects other electronic devices on the network (e.g., other network devices, user electronic devices, server electronic devices).
  • Some network devices are“multiple services network devices” that provide support for multiple networking functions (e.g., routing, bridging, switching, Layer 2 aggregation, session border control, Quality of Service, and/or subscriber management), and/or provide support for multiple application services (e.g., data, voice, and video).
  • FIG. 10B is a block diagram of an environment where the tenant systems 102i-1023 and the multi -tenant server 104 may be deployed, according to some implementations.
  • a system 1040 includes hardware (a set of one or more electronic devices) and software to provide service(s) 1042, including the transaction queue 104A, the tenant level objects 104B, the network level objects 104C, and the blockchain services 104D.
  • the system 1040 is coupled to user electronic devices 1080A-S over a network 1082.
  • the service(s) 1042 may be on-demand services that are made available to one or more of the users 1084A-S working for one or more other organizations (sometimes referred to as outside users) so that those organizations do not need to necessarily be concerned with building and/or maintaining a system, but instead makes use of the service(s) 1042 when needed (e.g., on the demand of the users 1084A-S).
  • the service(s) 1042 may communication with each other and/or with one or more of the user electronic devices 1080A-S via one or more Application Programming Interface(s) (APIs) (e.g., a Representational State Transfer (REST) API).
  • APIs Application Programming Interface
  • the user electronic devices 1080A-S are operated by users 1084A-S.
  • the system 1040 is a multi -tenant cloud computing architecture supporting multiple services, such as a customer relationship management (CRM) service (e.g., Sales Cloud by salesforce.com, Inc.), a contracts/proposals/quotes service (e.g., Salesforce CPQ by salesforce.com, Inc.), a customer support service (e.g., Service Cloud and Field Service Lightning by salesforce.com, Inc.), a marketing service (e.g., Marketing Cloud, Salesforce DMP, and Pardot by salesforce.com, Inc.), a commerce service (e.g., Commerce Cloud Digital, Commerce Cloud Order Management, and Commerce Cloud Store by salesforce.com, Inc.), communication with external business data sources (e.g., Salesforce Connect by salesforce.com, Inc.), a productivity service (e.g., Quip by salesforce.com, Inc.), database as a service (e.g., Database.comTM by salesforce.com, Inc.), Data as a Service (DAAS) (e
  • CRM customer relationship management
  • Sales Analytics, and/or Service Analytics by salesforce.com, Inc. a community service (e.g., Community Cloud and Chatter by salesforce.com, Inc.), an Internet of Things (IoT) service (e.g., Salesforce IoT and IoT Cloud by salesforce.com, Inc.), industry specific services (e.g., Financial Services Cloud and Health Cloud by salesforce.com, Inc.), and/or Infrastructure as a Service (IAAS) (e.g., virtual machines, servers, and/or storage).
  • IoT Internet of Things
  • Salesforce IoT and IoT Cloud by salesforce.com, Inc. Salesforce IoT and IoT Cloud by salesforce.com, Inc.
  • industry specific services e.g., Financial Services Cloud and Health Cloud by salesforce.com, Inc.
  • IAAS Infrastructure as a Service
  • system 1040 may include an application platform 1044 that enables PAAS for creating, managing, and executing one or more applications developed by the provider of the application platform 1044, users accessing the system 1040 via one or more of user electronic devices 1080A-S, or third-party application developers accessing the system 1040 via one or more of user electronic devices 1080A-S.
  • application platform 1044 that enables PAAS for creating, managing, and executing one or more applications developed by the provider of the application platform 1044, users accessing the system 1040 via one or more of user electronic devices 1080A-S, or third-party application developers accessing the system 1040 via one or more of user electronic devices 1080A-S.
  • one or more of the service(s) 1042 may utilize one or more multi-tenant databases 1046 for tenant data 1048, as well as system data storage 1050 for system data 1052 accessible to system 1040.
  • the system 1040 includes a set of one or more servers that are running on server electronic devices and that are configured to handle requests for any authorized user associated with any tenant (there is no server affinity for a user and/or tenant to a specific server).
  • the user electronic devices 1080A-S communicate with the server(s) of system 1040 to request and update tenant-level data and system-level data hosted by system 1040, and in response the system 1040 (e.g., one or more servers in system 1040) automatically may generate one or more Structured Query Language (SQL) statements (e.g., one or more SQL queries) that are designed to access the desired information from the one or more multi -tenant database 1046 and/or system data storage 1050.
  • SQL Structured Query Language
  • the service(s) 1042 are implemented using virtual applications dynamically created at run time responsive to queries from the user electronic devices 1080A-S and in accordance with metadata, including: 1) metadata that describes constructs (e.g., forms, reports, workflows, user access privileges, business logic) that are common to multiple tenants; and/or 2) metadata that is tenant specific and describes tenant specific constructs (e.g., tables, reports, dashboards, interfaces, etc.) and is stored in a multi tenant database.
  • constructs e.g., forms, reports, workflows, user access privileges, business logic
  • tenant specific constructs e.g., tables, reports, dashboards, interfaces, etc.
  • the program code 1060 may be a runtime engine that materializes application data from the metadata; that is, there is a clear separation of the compiled runtime engine (also known as the system kernel), tenant data, and the metadata, which makes it possible to independently update the system kernel and tenant-specific applications and schemas, with virtually no risk of one affecting the others.
  • the application platform 1044 includes an application setup mechanism that supports application developers' creation and management of applications, which may be saved as metadata by save routines.
  • Invocations to such applications may be coded using Procedural Language/Structured Object Query Language (PL/SOQL) that provides a programming language style interface.
  • PL/SOQL Procedural Language/Structured Object Query Language
  • a detailed description of some PL/SOQL language implementations is discussed in U.S. Pat. No. 7,730,478 entitled, METHOD AND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA A MULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, filed Sep. 21, 2007.
  • Invocations to applications may be detected by one or more system processes, which manages retrieving application metadata for the tenant making the invocation and executing the metadata as an application in a software container (e.g., a virtual machine).
  • Network 1082 may be any one or any combination of a LAN (local area network), WAN (wide area network), telephone network, wireless network, point-to-point network, star network, token ring network, hub network, or other appropriate configuration.
  • the network may comply with one or more network protocols, including an Institute of Electrical and Electronics Engineers (IEEE) protocol, a 3rd Generation Partnership Project (3 GPP) protocol, or similar wired and/or wireless protocols, and may include one or more intermediary devices for routing data between the system 1040 and the user electronic devices 1080A-S.
  • IEEE Institute of Electrical and Electronics Engineers
  • 3 GPP 3rd Generation Partnership Project
  • Each user electronic device 1080A-S typically includes one or more user interface devices, such as a keyboard, a mouse, a trackball, a touch pad, a touch screen, a pen or the like, for interacting with a graphical user interface (GUI) provided on a display (e.g., a monitor screen, a liquid crystal display (LCD), etc.) in conjunction with pages, forms, applications and other information provided by system 1040.
  • GUI graphical user interface
  • the user interface device can be used to access data and applications hosted by system 1040, and to perform searches on stored data, and otherwise allow a user 1084 to interact with various GUI pages that may be presented to a user 1084.
  • User electronic devices 1080A-S might communicate with system 1040 using TCP/IP (Transfer Control Protocol and Internet Protocol) and, at a higher network level, use other networking protocols to communicate, such as
  • HTTP Hypertext Transfer Protocol
  • FTP Andrew File System
  • WAP Wireless Application Protocol
  • FTP File Transfer Protocol
  • NFS Network File System
  • API application program interface
  • SOAP Simple Object Access Protocol
  • REST Representational State Transfer
  • one or more user electronic devices 1080A-S might include an HTTP client, commonly referred to as a “browser,” for sending and receiving HTTP messages to and from server(s) of system 1040, thus allowing users 1084 of the user electronic device 1080A-S to access, process and view information, pages and applications available to it from system 1040 over network 1082.
  • partitioning/sharing/dupli cation implementations types and interrelationships of system components, and logic partitioning/integration choices are set forth in order to provide a more thorough understanding. It will be appreciated, however, by one skilled in the art, that the invention may be practiced without such specific details. In other instances, control structures, logic implementations, opcodes, means to specify operands, and full software instruction sequences have not been shown in detail since those of ordinary skill in the art, with the included descriptions, will be able to implement what is described without undue
  • references in the specification to“one implementation,”“an implementation,”“an example implementation,” etc., indicate that the implementation described may include a particular feature, structure, or characteristic, but every implementation may not necessarily include the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same implementation. Further, when a particular feature, structure, or characteristic is described in connection with an implementation, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other implementations whether or not explicitly described. [0079] Bracketed text and blocks with dashed borders (e.g., large dashes, small dashes, dot- dash, and dots) may be used herein to illustrate optional operations and/or structures that add additional features to some implementations. However, such notation should not be taken to mean that these are the only options or optional operations, and/or that blocks with solid borders are not optional in certain implementations.
  • dashed borders e.g., large dashes, small dashes, dot- dash, and dots
  • Coupled is used to indicate that two or more elements, which may or may not be in direct physical or electrical contact with each other, co-operate or interact with each other.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Databases & Information Systems (AREA)
  • Computer Hardware Design (AREA)
  • Software Systems (AREA)
  • Accounting & Taxation (AREA)
  • Data Mining & Analysis (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • Computing Systems (AREA)
  • Strategic Management (AREA)
  • General Business, Economics & Management (AREA)
  • Power Engineering (AREA)
  • Finance (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
PCT/US2019/051783 2018-09-19 2019-09-18 Field-based peer permissions in a blockchain network Ceased WO2020061226A1 (en)

Priority Applications (6)

Application Number Priority Date Filing Date Title
JP2021515119A JP7268140B2 (ja) 2018-09-19 2019-09-18 ブロックチェーンネットワークにおけるフィールドベースのピア許可
AU2019345041A AU2019345041A1 (en) 2018-09-19 2019-09-18 Field-based peer permissions in a blockchain network
CN201980076006.8A CN113168622B (zh) 2018-09-19 2019-09-18 区块链网络中的基于字段的对等许可
EP19782823.9A EP3853794A1 (en) 2018-09-19 2019-09-18 Field-based peer permissions in a blockchain network
AU2023216803A AU2023216803A1 (en) 2018-09-19 2023-08-16 Field-based peer permissions in a blockchain network
AU2025248682A AU2025248682A1 (en) 2018-09-19 2025-10-09 Field-based peer permissions in a blockchain network

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201862733535P 2018-09-19 2018-09-19
US62/733,535 2018-09-19
US16/228,555 US11080247B2 (en) 2018-09-19 2018-12-20 Field-based peer permissions in a blockchain network
US16/228,555 2018-12-20

Publications (1)

Publication Number Publication Date
WO2020061226A1 true WO2020061226A1 (en) 2020-03-26

Family

ID=69774544

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2019/051783 Ceased WO2020061226A1 (en) 2018-09-19 2019-09-18 Field-based peer permissions in a blockchain network

Country Status (6)

Country Link
US (1) US11080247B2 (https=)
EP (1) EP3853794A1 (https=)
JP (1) JP7268140B2 (https=)
CN (1) CN113168622B (https=)
AU (3) AU2019345041A1 (https=)
WO (1) WO2020061226A1 (https=)

Cited By (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11770445B2 (en) 2022-01-25 2023-09-26 Salesforce, Inc. Decentralized information management database system
US11782904B2 (en) 2018-09-19 2023-10-10 Salesforce, Inc. Advanced smart contract with decentralized ledger in a multi-tenant environment
US11810031B2 (en) 2021-01-29 2023-11-07 Salesforce, Inc. On-site appointment assistant
US11809409B2 (en) 2018-09-19 2023-11-07 Salesforce, Inc. Multi-tenant distributed ledger interfaces
US11816098B2 (en) 2021-08-06 2023-11-14 Salesforce, Inc. Database system public trust ledger contract linkage
US11868321B2 (en) 2018-06-12 2024-01-09 Salesforce, Inc. Cryptographically secure multi-tenant data exchange platform
US11880372B2 (en) 2022-05-10 2024-01-23 Salesforce, Inc. Distributed metadata definition and storage in a database system for public trust ledger smart contracts
US11902852B2 (en) 2021-01-29 2024-02-13 Salesforce, Inc. On-site appointment assistant
US11921887B2 (en) 2022-01-25 2024-03-05 Salesforce, Inc. Decentralized identity metaverse database system
USD1023041S1 (en) 2021-01-29 2024-04-16 Salesforce, Inc. Display screen or portion thereof with graphical user interface
USD1024089S1 (en) 2021-01-29 2024-04-23 Salesforce, Inc. Display screen or portion thereof with graphical user interface
US11989726B2 (en) 2021-09-13 2024-05-21 Salesforce, Inc. Database system public trust ledger token creation and exchange
US12002039B2 (en) 2021-09-13 2024-06-04 Salesforce, Inc. Database system public trust ledger multi-owner token architecture
US12380430B2 (en) 2022-11-30 2025-08-05 Salesforce, Inc. Intermediary roles in public trust ledger actions via a database system
US12469077B2 (en) 2022-05-10 2025-11-11 Salesforce, Inc. Public trust ledger smart contract representation and exchange in a database system
US12526155B2 (en) 2022-06-06 2026-01-13 Salesforce, Inc. Multi-signature wallets in public trust ledger actions via a database system

Families Citing this family (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11611440B2 (en) * 2018-09-20 2023-03-21 Intralinks, Inc. Deal room platform using blockchain
US11349653B2 (en) * 2018-12-18 2022-05-31 Hewlett Packard Enterprise Development Lp Multiple-site private network secured by IPsec using blockchain network for key exchange
CN109658236A (zh) * 2019-01-31 2019-04-19 北京京东尚科信息技术有限公司 基于区块链的信息交互方法、区块链节点和征信系统
US11995647B2 (en) 2019-04-30 2024-05-28 Salesforce, Inc. System and method of providing interoperable distributed and decentralized ledgers using consensus on consensus and delegated consensus
US11880349B2 (en) 2019-04-30 2024-01-23 Salesforce, Inc. System or method to query or search a metadata driven distributed ledger or blockchain
US11764950B2 (en) 2019-05-22 2023-09-19 Salesforce, Inc. System or method to implement right to be forgotten on metadata driven blockchain using shared secrets and consensus on read
US11823120B2 (en) 2019-12-13 2023-11-21 Salesforce, Inc. System or method of verifying an asset using blockchain and collected asset and device information
US11144335B2 (en) 2020-01-30 2021-10-12 Salesforce.Com, Inc. System or method to display blockchain information with centralized information in a tenant interface on a multi-tenant platform
US11893002B2 (en) 2020-05-04 2024-02-06 Salesforce, Inc. System or method to run distributed validation of workflows across a network in a shared distributed ledger in multi-tenant cloud environment
US11954183B2 (en) 2020-10-09 2024-04-09 Salesforce, Inc. System and method using metadata to manage packaged applications components based on tenant licenses
US11271716B1 (en) 2021-01-28 2022-03-08 Emtruth, Inc. Blockchain-based data management of distributed binary objects
US20230021962A1 (en) * 2021-07-15 2023-01-26 Zuora, Inc. Subscription metric generation from storage-efficient subscription charge segment change logs
US20240305484A1 (en) * 2023-03-12 2024-09-12 International Business Machines Corporation Task mining data network architecture incorporating a private or hybrid blockchain
US12395836B2 (en) 2023-03-31 2025-08-19 T-Mobile Innovations Llc Smart contract filtration in a wireless communication system

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7730478B2 (en) 2006-10-04 2010-06-01 Salesforce.Com, Inc. Method and system for allowing access to developed applications via a multi-tenant on-demand database service

Family Cites Families (58)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7092914B1 (en) * 1997-11-06 2006-08-15 Intertrust Technologies Corporation Methods for matching, selecting, narrowcasting, and/or classifying based on rights management and/or other information
GB0011426D0 (en) 2000-05-11 2000-06-28 Charteris Limited A method for transforming documents written in different XML-based languages
US20020194501A1 (en) * 2001-02-25 2002-12-19 Storymail, Inc. System and method for conducting a secure interactive communication session
US9406063B2 (en) * 2002-10-01 2016-08-02 Dylan T X Zhou Systems and methods for messaging, calling, digital multimedia capture, payment transactions, global digital ledger, and national currency world digital token
EA015549B1 (ru) * 2003-06-05 2011-08-30 Интертраст Текнолоджис Корпорейшн Переносимая система и способ для приложений одноранговой компоновки услуг
US8271641B2 (en) * 2006-10-04 2012-09-18 Salesforce.Com, Inc. Method and system for governing resource consumption in a multi-tenant system
WO2009132444A1 (en) 2008-04-28 2009-11-05 Sitemasher Corporation Object-oriented system for creating and managing websites and their content
US8356274B2 (en) 2008-07-07 2013-01-15 International Business Machines Corporation System and methods to create a multi-tenancy software as a service application
US20110276490A1 (en) * 2010-05-07 2011-11-10 Microsoft Corporation Security service level agreements with publicly verifiable proofs of compliance
US9223892B2 (en) 2010-09-30 2015-12-29 Salesforce.Com, Inc. Device abstraction for page generation
US8935360B2 (en) 2010-12-03 2015-01-13 Salesforce.Com, Inc. Techniques for metadata-driven dynamic content serving
US10740353B2 (en) 2010-12-23 2020-08-11 Mongodb, Inc. Systems and methods for managing distributed database deployments
US20130081109A1 (en) 2011-09-23 2013-03-28 Corent Technology, Inc. Multi-Tenant Agile Database Connector
US9572614B2 (en) 2012-04-03 2017-02-21 Salesforce.Com, Inc. Mechanism for facilitating user-controlled management of webpage elements for dynamic customization of information
US9075889B2 (en) 2012-04-09 2015-07-07 Salesforce.Com, Inc. Mechanism for facilitating user-controlled management of site network mapping and synchronization
US20130290406A1 (en) 2012-04-26 2013-10-31 Salesforce.Com, Inc. Mechanism for providing a cloud platform for facilitating and supporting user-controlled development and management of user products
US20150379510A1 (en) * 2012-07-10 2015-12-31 Stanley Benjamin Smith Method and system to use a block chain infrastructure and Smart Contracts to monetize data transactions involving changes to data included into a data supply chain.
US9448773B2 (en) 2013-04-03 2016-09-20 Salesforce.Com, Inc. Systems and methods for implementing a uniform application user interface across a multi-tenant environment
US8886671B1 (en) 2013-08-14 2014-11-11 Advent Software, Inc. Multi-tenant in-memory database (MUTED) system and method
US20160012465A1 (en) 2014-02-08 2016-01-14 Jeffrey A. Sharp System and method for distributing, receiving, and using funds or credits and apparatus thereof
US20150348017A1 (en) * 2014-06-03 2015-12-03 Jonathan Allmen Method for integrating cryptocurrency transfer on a social network interface
US9438673B2 (en) * 2014-07-16 2016-09-06 Microsoft Technology Licensing, Llc Dynamic update streams for real time provisioning
US20160098723A1 (en) 2014-10-01 2016-04-07 The Filing Cabinet, LLC System and method for block-chain verification of goods
HK1249791A1 (zh) 2015-03-31 2018-11-09 Nasdaq, Inc. 区块链交易记录的系统和方法
WO2016189488A2 (en) * 2015-05-27 2016-12-01 Vishal Gupta Universal original document validation platform
US9882851B2 (en) * 2015-06-29 2018-01-30 Microsoft Technology Licensing, Llc User-feedback-based tenant-level message filtering
USD768690S1 (en) 2015-08-24 2016-10-11 Salesforce.Com, Inc. Display screen or portion thereof with animated graphical user interface
US11941588B2 (en) * 2015-11-06 2024-03-26 Cable Television Laboratories, Inc. Systems and methods for blockchain virtualization and scalability
US20170140408A1 (en) 2015-11-16 2017-05-18 Bank Of America Corporation Transparent self-managing rewards program using blockchain and smart contracts
US10489786B2 (en) 2015-11-24 2019-11-26 Vesta Corporation Optimization of fraud detection model in real time
US20170178127A1 (en) 2015-12-18 2017-06-22 International Business Machines Corporation Proxy system mediated legacy transactions using multi-tenant transaction database
AU2017216289A1 (en) 2016-02-04 2018-09-27 Nasdaq Technology Ab Systems and methods for storing and sharing transactional data using distributed computer systems
WO2018006072A1 (en) 2016-06-30 2018-01-04 Clause, Inc. Systems and method for forming, storing, managing,and executing contracts
GB201611948D0 (en) 2016-07-08 2016-08-24 Kalypton Int Ltd Distributed transcation processing and authentication system
US10755327B2 (en) 2016-07-18 2020-08-25 Royal Bank Of Canada Distributed ledger platform for vehicle records
JP6971019B2 (ja) * 2016-09-26 2021-11-24 Ｇｍｏインターネット株式会社 データ管理システム、情報処理装置、プログラム、及び、データ管理方法
US10552381B2 (en) 2016-12-16 2020-02-04 International Business Machines Corporation Shared document editing in the blockchain
WO2018140830A1 (en) 2017-01-27 2018-08-02 Walmart Apollo, Llc Managing smart appliances using blockchain technology
US9992022B1 (en) * 2017-02-06 2018-06-05 Northern Trust Corporation Systems and methods for digital identity management and permission controls within distributed network nodes
US10356102B2 (en) 2017-02-24 2019-07-16 Verizon Patent And Licensing Inc. Permissions using blockchain
CN107169371B (zh) * 2017-04-27 2019-11-22 北京众享比特科技有限公司 一种基于区块链的数据库操作方法和系统
JP6302592B2 (ja) * 2017-06-23 2018-03-28 株式会社エヌ・ティ・ティ・データ 情報処理装置、情報処理方法およびプログラム
EP3665696A4 (en) 2017-08-08 2020-12-30 QuiO Technologies LLC AUTOMATICALLY EXECUTED HEALTH INFORMATION COLLECTION AGENTS BETWEEN TRUSTED PARTIES
US20190058709A1 (en) 2017-08-16 2019-02-21 Telefonaktiebolaget Lm Ericsson (Publ) Tenant management method and system in a cloud computing environment
US11003654B2 (en) 2017-09-20 2021-05-11 AppExtremes, LLC Systems and methods for requesting, tracking and reporting modifications to a record
US11294943B2 (en) 2017-12-08 2022-04-05 International Business Machines Corporation Distributed match and association of entity key-value attribute pairs
US20190236559A1 (en) 2018-01-31 2019-08-01 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing smart flow contracts using distributed ledger technologies in a cloud based computing environment
US20190238316A1 (en) 2018-01-31 2019-08-01 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing intelligent consensus, smart consensus, and weighted consensus models for distributed ledger technologies in a cloud based computing environment
US20190236606A1 (en) 2018-01-31 2019-08-01 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing a virtual chain model for distributed ledger technologies in a cloud based computing environment
US20190236562A1 (en) 2018-01-31 2019-08-01 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing document interface and collaboration using quipchain in a cloud based computing environment
US10701054B2 (en) 2018-01-31 2020-06-30 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing super community and community sidechains with consent management for distributed ledger technologies in a cloud based computing environment
US11257073B2 (en) 2018-01-31 2022-02-22 Salesforce.Com, Inc. Systems, methods, and apparatuses for implementing machine learning models for smart contracts using distributed ledger technologies in a cloud based computing environment
US10901974B2 (en) 2018-03-29 2021-01-26 Salesforce.Com, Inc. Hybrid cloud chain management of centralized and decentralized data
US10585657B2 (en) 2018-03-29 2020-03-10 Salesforce.Com, Inc. Setup, management, and packaging of applications accessing centralized and decentralized data
US11868321B2 (en) 2018-06-12 2024-01-09 Salesforce, Inc. Cryptographically secure multi-tenant data exchange platform
US11468406B2 (en) 2018-07-31 2022-10-11 Salesforce, Inc. Method of converting language-based written contract to smart legal contract using natural language processing
US11379828B2 (en) 2018-08-30 2022-07-05 International Business Machines Corporation Distributed computing and storage network implementing high integrity, high bandwidth, low latency, secure processing
US20200084027A1 (en) 2018-09-06 2020-03-12 Bank Of Montreal Systems and methods for encryption of data on a blockchain

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7730478B2 (en) 2006-10-04 2010-06-01 Salesforce.Com, Inc. Method and system for allowing access to developed applications via a multi-tenant on-demand database service

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
QI XIA ET AL: "MeDShare: Trust-Less Medical Data Sharing Among Cloud Service Providers via Blockchain", IEEE ACCESS, vol. 5, 14 August 2017 (2017-08-14), pages 14757 - 14767, XP055646950, DOI: 10.1109/ACCESS.2017.2730843 *
SATOSHI NAKAMOTO: "Bitcoin: A Peer-to-Peer Electronic Cash System", 31 October 2008 (2008-10-31), pages 1 - 9, XP055192574, Retrieved from the Internet <URL:https://nakamotoinstitute.org/static/docs/bitcoin.pdf> [retrieved on 20150601] *
YU FEI RICHARD ET AL: "Virtualization for Distributed Ledger Technology (vDLT)", IEEE ACCESS, vol. 6, 24 May 2018 (2018-05-24), pages 25019 - 25028, XP011684182, DOI: 10.1109/ACCESS.2018.2829141 *

Cited By (21)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11868321B2 (en) 2018-06-12 2024-01-09 Salesforce, Inc. Cryptographically secure multi-tenant data exchange platform
US11809409B2 (en) 2018-09-19 2023-11-07 Salesforce, Inc. Multi-tenant distributed ledger interfaces
US11782904B2 (en) 2018-09-19 2023-10-10 Salesforce, Inc. Advanced smart contract with decentralized ledger in a multi-tenant environment
USD1023041S1 (en) 2021-01-29 2024-04-16 Salesforce, Inc. Display screen or portion thereof with graphical user interface
US11810031B2 (en) 2021-01-29 2023-11-07 Salesforce, Inc. On-site appointment assistant
USD1105113S1 (en) 2021-01-29 2025-12-09 Salesforce, Inc. Display screen or portion thereof with graphical user interface
US11902852B2 (en) 2021-01-29 2024-02-13 Salesforce, Inc. On-site appointment assistant
USD1073710S1 (en) 2021-01-29 2025-05-06 Salesforce, Inc. Display screen or portion thereof with graphical user interface
USD1024089S1 (en) 2021-01-29 2024-04-23 Salesforce, Inc. Display screen or portion thereof with graphical user interface
US12099496B2 (en) 2021-08-06 2024-09-24 Salesforce, Inc. Database system public trust ledger contract linkage
US11816098B2 (en) 2021-08-06 2023-11-14 Salesforce, Inc. Database system public trust ledger contract linkage
US11954094B2 (en) 2021-08-06 2024-04-09 Salesforce, Inc. Database system public trust ledger architecture
US12354089B2 (en) 2021-09-13 2025-07-08 Salesforce, Inc. Database system public trust ledger multi-owner token architecture
US12002039B2 (en) 2021-09-13 2024-06-04 Salesforce, Inc. Database system public trust ledger multi-owner token architecture
US11989726B2 (en) 2021-09-13 2024-05-21 Salesforce, Inc. Database system public trust ledger token creation and exchange
US11770445B2 (en) 2022-01-25 2023-09-26 Salesforce, Inc. Decentralized information management database system
US11921887B2 (en) 2022-01-25 2024-03-05 Salesforce, Inc. Decentralized identity metaverse database system
US12469077B2 (en) 2022-05-10 2025-11-11 Salesforce, Inc. Public trust ledger smart contract representation and exchange in a database system
US11880372B2 (en) 2022-05-10 2024-01-23 Salesforce, Inc. Distributed metadata definition and storage in a database system for public trust ledger smart contracts
US12526155B2 (en) 2022-06-06 2026-01-13 Salesforce, Inc. Multi-signature wallets in public trust ledger actions via a database system
US12380430B2 (en) 2022-11-30 2025-08-05 Salesforce, Inc. Intermediary roles in public trust ledger actions via a database system

Also Published As

Publication number Publication date
CN113168622A (zh) 2021-07-23
JP7268140B2 (ja) 2023-05-02
CN113168622B (zh) 2022-03-18
JP2022501712A (ja) 2022-01-06
AU2019345041A1 (en) 2021-04-22
AU2025248682A1 (en) 2025-10-30
AU2023216803A1 (en) 2023-09-07
EP3853794A1 (en) 2021-07-28
US11080247B2 (en) 2021-08-03
US20200089663A1 (en) 2020-03-19

Similar Documents

Publication Publication Date Title
US11782904B2 (en) Advanced smart contract with decentralized ledger in a multi-tenant environment
US11080247B2 (en) Field-based peer permissions in a blockchain network
US11868321B2 (en) Cryptographically secure multi-tenant data exchange platform
US11100091B2 (en) Lightweight node in a multi-tenant blockchain network
US11995647B2 (en) System and method of providing interoperable distributed and decentralized ledgers using consensus on consensus and delegated consensus
US11809409B2 (en) Multi-tenant distributed ledger interfaces
US12547980B2 (en) System or method of verifying an asset using blockchain and collected asset and device information
US11893002B2 (en) System or method to run distributed validation of workflows across a network in a shared distributed ledger in multi-tenant cloud environment
US11764978B2 (en) Method and system for certificate management

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19782823

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2021515119

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2019345041

Country of ref document: AU

Date of ref document: 20190918

Kind code of ref document: A

ENP Entry into the national phase

Ref document number: 2019782823

Country of ref document: EP

Effective date: 20210419