Patent classifications
H04L9/0643
Community data aggregation with automated followup
A system and method are disclosed for the collection and aggregation of data from contributing members of a community, such as health-related, personal, genomic, medical, and other data of interest for individuals and populations. Contributors become members of a community upon creation of an account and providing of data or files. The data is received and processed, such as to analyze, structure, perform quality control, and curate the data. Value or shares in one or more community databases are computed and attributed to each contributing member. The data is controlled to avoid identification or personalization. Steps are taken to determine incompleteness and incorrectness of the data, and the data may be improved or completed automatically, based upon interaction with members, additional contributions of data, and so forth.
Cryptographic data encoding method with enhanced data security
Data security and privacy are improved by a client providing a hashed version of collected data to a remote analysis service, and having the analysis service determine the relevancy of the data from the hashes before requesting the plaintext of the data. In one example, a browser plug-in obtains data which is divided into overlapping three-character sequences, and the sequences are hashed to produce a sequence of hashes. The sequence of hashes is sent by the plug-in to the remote service, which uses the hashes to determine if the associated data is relevant to the analysis performed by the remote service, without requiring access to the associated plaintext. After making the determination, the remote service may request that relevant data be provided to the service in plaintext form, while data that is not relevant need not be sent to the remote service.
Decentralized robot cooperation platform
Systems and methods of the present disclosure leverage distributed ledger technology (DLT) to provide decentralized control of cooperative tasks performed by a plurality of robots. Characteristics of the plurality of robots may be stored in a distribute ledger, which may be provided by a blockchain or a distributed database system. When a service request is received, a set of tasks may be identified for providing the requested service and the robot characteristics recorded to the distributed ledger may be used to identify a list of candidate robots possessing characteristics corresponding to the set of tasks may be identified. A smart contract may be utilized to select one or more candidate robots for performing the task and to verify the selected robot(s) successfully completed the task. State information associated with operation of the selected robot(s) may be monitored to verify task completion.
Systems and methods to timestamp and authenticate digital documents using a secure ledger
Systems and methods to timestamp and authenticate digital documents using a secure ledger are described. Some implementations can include computer-implemented method to timestamp and authenticate electronic documents. The method can include receiving, by a timestamp and authentication server and from a user device, a unique hash value that is generated at the user device based on a source document and a device identifier of the user device, and verifying, by the timestamp and authentication server, the device identifier. The method can also include, upon verifying the device identifier, inserting, by the timestamp and authentication server, the hash value and the device identifier into a secure ledger, and upon successful insertion into the secure ledger, transmitting, from the timestamp and authentication server to the user device, a success status message including a location in the secure ledger where the hash value was inserted.
Systems and methods of providing immutable records
Systems and methods of providing immutable records, and immutable ordering of records, in a computing system are disclosed. The computing system can be a member of a blockchain network of a plurality of blockchains. Each block can include a cryptographic digest (or hash) conforming to a minimum degree of difficulty, a nonce by which the cryptographic digest was generated in conformation with the degree of difficulty, and a list of cryptographic digests of most recent blocks of participating neighbor blockchains. Blocks may be passed between blockchains of the plurality of blockchains, which enables each member of the blockchain network to verify an immutable record of data transactions free of the mutual trust requirement of a typical blockchain environment. In conjunction with the generation of each block, an event record may be entered into an event log of the computing system wherein the block was generated. The event record, which may contain actionable instructions, requests, etc., may be transmitted to computing systems of participating neighbor blockchains, where actionable items may be acted upon. Further, the event logs of each computing system may be exchanged, compared, and adjusted to reflect the earliest appearance of each block of each participating neighbor blockchain.
Recordation of device usage to public/private blockchains
A personal blockchain is generated as a cloud-based software service in a blockchain environment. The personal blockchain immutably archives usage of any device, perhaps as requested by a user. However, some of the usage may be authorized for public disclosure, while other usage may be designated as private and restricted from public disclosure. The public disclosure may permit public ledgering by still other blockchains, thus providing two-way public/private ledgering for improved record keeping. Private usage, though, may only be documented by the personal blockchain.
Efficient deduplication using block-based convergent encryption
Systems and methods are described for providing secure storage of data sets while enabling efficient deduplication of data. Each data set can be divided into fixed-length blocks. The plaintext of each block can be convergently encrypted, such as by using a hash of the plaintext as an encryption key, to result in block-level ciphertext that can be stored. If two data sets share blocks, the resulting block-level ciphertext can be expected to overlap, and thus duplicative block-level ciphertexts need not be stored. A manifest can be created to facilitate re-creation of the data set, which manifest identifies the block-level ciphertexts of the data set and a key by which each block-level ciphertext was encrypted. By use of block-level encryption, nearly identical data sets can be largely deduplicated, even if they are not perfectly identical.
Unbiased drug selection for audit using distributed ledger technology
A computer-implemented method of auditing drug supply chain data gathered from a distributed ledger is disclosed. The method includes receiving a population of drug product records from the distributed ledger. The method includes receiving a first set of drug product criteria. The method includes determining a weighted probability for one or more drug product records of the population of drug product records. The method includes generating a randomized first subset of drug product records from the population of drug product records based on the weighted probability of the one or more drug product records. Other methods, systems, and the like for unbiased drug selection for audit are also disclosed.
Split chain of trust for secure device boot
The secure chain of trust steps to boot-up a computing device are split between the shutdown procedure of the computing device and the boot-up procedure of the computing device to reduce the time required for the computing device to boot-up. The main image associated with a central processing unit of the computing device is validated during the shutdown procedure of the computing device such that the operating system for the central processing unit is available when the computing device receives an action to power on. The boot-up time for the computing device is reduced, which allows the computing device to boot-up within an established time frame.
Multi-client transaction validation
An example operation may include one or more of identifying a plurality of instances of a blockchain storage request that have been independently submitted by a plurality of clients, respectively, verifying whether execution content of the plurality of instances of the blockchain storage request match, and in response to verifying the match, storing the blockchain storage request within a block among a hash-linked chain of blocks.