Abstract:
The present disclosure provides an approach for a blockchain system in which (a) data of past transactions can be removed from the storage of network nodes based on node permissions, and (b) in which data can be made invisible to users based on user-specific or group-specific permissions. The blockchain system stores cryptographic proofs of data on an immutable ledger. The data itself is maintained within the blockchain system such that it can be partially or fully removed, while maintaining the integrity of the ledger.
Abstract:
In various implementations, a method of identifying anomalies is performed by a first network node that is configured to maintain a distributed ledger in coordination with a plurality of network nodes. In various implementations, the first network node includes one or more processors, a non-transitory memory, and one or more network interfaces. In various implementations, the method includes determining a characteristic value based on information associated with the distributed ledger. In some implementations, the distributed ledger stores blocks of transactions that were added to the distributed ledger based on a consensus determination between the plurality of network nodes. In various implementations, the method includes determining whether a current transaction satisfies the characteristic value. In various implementations, the method include indicating whether there is an anomaly based on a function of the current transaction in relation to the characteristic value.
Abstract:
Systems, methods, and devices are disclosed for authenticating a product. An internal component of a product is identified by identifying an intrinsic attribute of the internal component, where the intrinsic attribute is received at a time subsequent to independently storing the intrinsic attribute in a database. A match is determined between the intrinsic attribute and the stored intrinsic attribute. The product is confirmed to be authentic when the match is verified.
Abstract:
The present disclosure provides an approach for a blockchain system in which (a) data of past transactions can be removed from the storage of network nodes based on node permissions, and (b) in which data can be made invisible to users based on user-specific or group-specific permissions. The blockchain system stores cryptographic proofs of data on an immutable ledger. The data itself is maintained within the blockchain system such that it can be partially or fully removed, while maintaining the integrity of the ledger.
Abstract:
In various implementations, a method of managing transactions in a distributed ledger is performed by a first network node that is configured to maintain a distributed ledger in coordination with a plurality of network nodes. In various implementations, the first network node includes a processor, a non-transitory memory, and a network interface. In various implementations, the method includes synchronizing a first clock of the first network node with respective clocks maintained by one or more of the plurality of network nodes. In various implementations, the method includes obtaining a transaction indicator including respective transaction data. For example, in some implementations, the method includes receiving a transaction request from a client device. In various implementations, the method includes synthesizing, by the first network node, a timestamp for the transaction based on the first clock. In some implementations, the timestamp indicates a time that associates the first network node to the transaction.
Abstract:
Systems, methods, and devices are disclosed for authenticating a product. An internal component of a product is identified by identifying an intrinsic attribute of the internal component, where the intrinsic attribute is received at a time subsequent to independently storing the intrinsic attribute in a database. A match is determined between the intrinsic attribute and the stored intrinsic attribute. The product is confirmed to be authentic when the match is verified.
Abstract:
In various implementations, a method of managing transactions in a distributed ledger is performed by a first network node that is configured to maintain a distributed ledger in coordination with a plurality of network nodes. In various implementations, the first network node includes a processor, a non-transitory memory, and a network interface. In various implementations, the method includes synchronizing a first clock of the first network node with respective clocks maintained by one or more of the plurality of network nodes. In various implementations, the method includes obtaining a transaction indicator including respective transaction data. For example, in some implementations, the method includes receiving a transaction request from a client device. In various implementations, the method includes synthesizing, by the first network node, a timestamp for the transaction based on the first clock. In some implementations, the timestamp indicates a time that associates the first network node to the transaction.
Abstract:
A method is provided in one example and includes receiving data from a mobile network entity, parsing the data to determine a first identity and first attribute information associated with the first identity, determining whether the first identity exists in a database, storing the first identity in the database if the first identity does not exist in the database, and storing the first attribute information in association with the first identity in the database. The method further includes determining whether there is at least one identity related to the first identity in the database, and updating each of the related identities with the first attribute information when it is determined that there is at least one identity.
Abstract:
A method is provided in one example and includes receiving at least one first input indicating at least one network condition associated with a first user device having a user associated therewith. The first user device has a first bearer channel established between the first user device and a gateway, and the first bearer channel has a first quality of service level. The method further includes determining whether to modify the first user device to a second quality of service level based upon the received at least one first input, and sending a first request to a first network element instructing the first network element to modify the first user device to the second quality of service level.
Abstract:
A method is performed by a first fog node of a plurality of fog nodes. In some implementations, the first fog node includes a non-transitory memory and one or more processors coupled with the non-transitory memory. In some implementations, the method includes maintaining a distributed ledger in coordination with the remaining fog nodes of the plurality of fog nodes. In some implementations, the distributed ledger stores configuration information associated with one or more devices. In some implementations, the method includes obtaining a request for configuration information from a device that breaches a resource threshold associated with the distributed ledger. In some implementations, the method includes transmitting, to the device, the configuration information associated with the device in order to allow the device to be configured in accordance with the configuration information while the device breaches the resource threshold associated with the distributed ledger.