The present invention discloses a cloud-side collaborative multi-mode private data circulation method based on a smart contract, including: S1, a system is initialized; S2, the original data are encrypted into private data, an encryption certificate z′ for storage is generated, and z′ includes metadata and a data certificate key′; S3, the DO calls a smart contract program to realize uplink of the encryption certificate z′ and releases z′ to a block chain through a smart contract, wherein the smart contract is open to all user accounts; S4, rapid data circulation is realized: when DO releases the data certificate, DU has been identified, a DU's account ID.sub.DU is set through an access policy, the DU obtains an encryption key for data access by executing a smart contract and a key algorithm, private data are obtained through metadata and decrypted to obtain a plaintext; and S5, the data circulation is confirmed.

The present invention discloses a cloud-side collaborative multi-mode private data circulation method based on a smart contract, including: S1, a system is initialized; S2, the original data are encrypted into private data, an encryption certificate z′ for storage is generated, and z′ includes metadata and a data certificate key′; S3, the DO calls a smart contract program to realize uplink of the encryption certificate z′ and releases z′ to a block chain through a smart contract, wherein the smart contract is open to all user accounts; S4, rapid data circulation is realized: when DO releases the data certificate, DU has been identified, a DU's account ID.sub.DU is set through an access policy, the DU obtains an encryption key for data access by executing a smart contract and a key algorithm, private data are obtained through metadata and decrypted to obtain a plaintext; and S5, the data circulation is confirmed.

An example operation may include one or more of initializing a smart contract (SC) and appending it to a blockchain, registering each of a plurality of participants as a party to the SC, receiving from at least some of the participants an encrypted confidential input commitment, appending the encrypted input commitments to the blockchain, decrypting the encrypted input commitments, executing by the SC at least one business rule using the decrypted input commitments to obtain a business rule result, and identifying a prevailing participant based at least in part on the business rule result.

An example operation may include one or more of initializing a smart contract (SC) and appending it to a blockchain, registering each of a plurality of participants as a party to the SC, receiving from at least some of the participants an encrypted confidential input commitment, appending the encrypted input commitments to the blockchain, decrypting the encrypted input commitments, executing by the SC at least one business rule using the decrypted input commitments to obtain a business rule result, and identifying a prevailing participant based at least in part on the business rule result.

An electric vehicle charger includes a power supply and a controller. The power supply is for supplying electric power over a charging connection to an electric vehicle. The charging connection employs charging conductors to supply electric power from the power supply to the electric vehicle for charging. The power supply is adapted to send data to and receive data from the electric vehicle over the charging conductors according to a power-line communications protocol. The controller coupled to the power supply to control supply of electric power to the electric vehicle, The controller is adapted to, prior to initiating supply of electric power by the power supply to the electric vehicle for charging, communicate with the electric vehicle to identify a payment method associated with the electric vehicle and with the payment network to authorize the payment method for payment for electric power supplied to the electric vehicle for charging.

A method for maintaining state and event information for all of a user's devices associated in a common location using a blockchain where each block includes an event block and a device block within it, where each event and device block refers to an earlier block of the respective type, resulting in a blockchain-in-a-blockchain architecture. The device and event blocks store data regarding each device associated with a user and events related to the devices/user, respectively. Any time a new event occurs, or a device is registered or removed, a new set of blocks is created, where submissions regarding device changes or events can be made by any participant due to the decentralized and public nature of a blockchain. The result is a system where all data regarding a user's registered devices and events is kept in a common location in a manner that is auditable and verifiable.

The present technology discloses methods and systems for receiving a security profile request from an integrity verifier, the request including a nonce; requesting, from a trusted platform module, a new nonce, wherein the new nonce is generated at least in part by the nonce and a current timestamp from a clock in the trusted platform module; receiving, from the trusted platform module, the new nonce; requesting, from a cryptoprocessor, a set of platform configuration registers; receiving, from the cryptoprocessor, the set of platform configuration registers; and sending a response to the integrity verifier, the response including the new nonce and the set of platform configuration registers to verify a security status of the trusted platform module and the cryptoprocessor.

The present technology discloses methods and systems for receiving a security profile request from an integrity verifier, the request including a nonce; requesting, from a trusted platform module, a new nonce, wherein the new nonce is generated at least in part by the nonce and a current timestamp from a clock in the trusted platform module; receiving, from the trusted platform module, the new nonce; requesting, from a cryptoprocessor, a set of platform configuration registers; receiving, from the cryptoprocessor, the set of platform configuration registers; and sending a response to the integrity verifier, the response including the new nonce and the set of platform configuration registers to verify a security status of the trusted platform module and the cryptoprocessor.

Devices can be configured to broadcast blocks incorporating artifact origination tokens. Devices can include network interfaces, memory; and processors. Processors can be configured to obtain artifact-to-time association elements. Artifact-to-time association elements can include artifact references and timestamps. Timestamps can include references to artifact references. Processors can be further configured to obtain artifact origination tokens. Artifact origination tokens can include artifact-to-time association element, certifier descriptors indicating certifier public keys, and/or certifier digital signatures. Certifier digital signatures can be generated based on certifier public keys and/or artifact-to-time association elements. Processors can be further configured to obtain ledger entries including artifact origination tokens with public keys, compute challenges based on ledger entries, and broadcast blocks incorporating the ledger entries. Blocks can be validated using cryptographic systems to obtain proof based challenges.

Devices can be configured to broadcast blocks incorporating artifact origination tokens. Devices can include network interfaces, memory; and processors. Processors can be configured to obtain artifact-to-time association elements. Artifact-to-time association elements can include artifact references and timestamps. Timestamps can include references to artifact references. Processors can be further configured to obtain artifact origination tokens. Artifact origination tokens can include artifact-to-time association element, certifier descriptors indicating certifier public keys, and/or certifier digital signatures. Certifier digital signatures can be generated based on certifier public keys and/or artifact-to-time association elements. Processors can be further configured to obtain ledger entries including artifact origination tokens with public keys, compute challenges based on ledger entries, and broadcast blocks incorporating the ledger entries. Blocks can be validated using cryptographic systems to obtain proof based challenges.