Method and system involving blu-ray copy service
By building a decentralized Blu-ray copy service system using blockchain technology, the single point of failure and network dependency issues of centralized databases are resolved, achieving high availability and security for Blu-ray copies and improving the user experience.
Patent Information
- Application Number
- CN202010412988.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2019-06-07
- Filing Date
- 2020-05-15
- Publication Date
- 2024-11-01
- Estimated Expiration
- 2040-05-15
AI Technical Summary
Existing centralized databases suffer from single points of failure, high network dependence, slow access speed, insufficient data redundancy, and inability to access the same data simultaneously. Furthermore, existing Blu-ray copying systems lack decentralized means, making it impossible to effectively achieve high availability and user experience.
A decentralized Blu-ray copying service system is built using blockchain technology. It receives copy requests through the blockchain network, calls smart contracts to verify copy tokens, generates media copying keys, and records the copy tokens on the blockchain network's ledger to achieve the legality and traceability of Blu-ray copies.
It achieves high availability and decentralization of Blu-ray copy service, improves system security and reliability, reduces the risk of single point of failure, and enhances user experience and data immutability.
Smart Images

Figure CN112052474B_ABST
Abstract
Description
Technical Field
[0001] The present application generally relates to copy service systems, and more specifically, to Blu-ray copy services. Background Art
[0002] A centralized database stores and maintains data in a single database at one location (e.g., a database server). The location is typically a central computer, such as a desktop central processing unit (CPU), a server CPU, or a mainframe computer. The information stored in a centralized database can typically be accessed from multiple different points. Multiple users or client workstations can work on the centralized database simultaneously, for example, based on a client / server configuration. A centralized database is easy to manage, maintain, and control because of its single location, especially for security purposes. In a centralized database, data redundancy is minimized because a single storage location for all data also means that there is only one master record for a given set of data.
[0003] However, there are obvious disadvantages to centralized databases. For example, centralized databases have a single point of failure. In particular, if there is no fault tolerance consideration and a failure occurs (e.g., hardware, firmware, and / or software failure), all data in the database will be lost and the work of all users will be interrupted. In addition, centralized databases are highly dependent on network connections. Therefore, the slower the connection, the amount of time required for each database access will increase. Another disadvantage is that bottlenecks occur when centralized databases experience high traffic due to a single location. In addition, centralized databases provide limited access to data because the database only maintains one copy of the data. Therefore, multiple devices cannot access the same piece of data at the same time without causing major problems or the risk of overwriting the stored data. In addition, because the database storage system has little or no data redundancy, accidentally lost data is difficult to retrieve from backup storage unless manually operated.
[0004] Therefore, a blockchain-based solution is needed to overcome these shortcomings and limitations. Blu-ray disc technology remains a highly relevant way to consume audiovisual media. The Blu-ray market is in full growth as it is the de facto standard for video and gaming devices. One of the key requirements of Blu-ray is the ability to make legal copies. This is where Blu-ray Managed Copy or Blu-ray Copy comes in. The Access Content System Two (AACS2) specification has defined the specifications and application formats for Ultra HD Blu-ray specific version copies (called Blu-ray Copy) for Ultra HD Blu-ray. However, most implementations lack the features required to deliver the necessary functionality required by studios, the correct user experience, or the required high availability. The current implementation of Blu-ray Copy assumes the presence of a central server (called Copy Server) that will authorize the copies. The protocol is defined by using a SOAP-like service that allows Blu-ray devices and Copy Servers to exchange messages over the Internet. However, existing solutions do not provide any decentralized means to implement Blu-ray Copy by using blockchain technology.
[0005] Therefore, it is desirable to have a method and system for providing a highly available decentralized means to achieve Blu-ray copying by using blockchain technology, thereby improving the user experience. Summary of the invention
[0006] An example embodiment provides a system including a processor and a memory, wherein the processor is configured to perform one or more of the following: receiving a copy request from a user node via a blockchain network, the request including a copy token; calling a smart contract associated with the copy token to verify the copy token; in response to the verification, generating a media copy key for generating a Blu-ray copy, and recording the copy token on a ledger of the blockchain network to indicate that the copy token is spent.
[0007] Another example embodiment provides a method comprising one or more of the following: receiving, by a verification node, a copy request from a user node through a blockchain network, the request comprising a copy token; calling, by the verification node, a smart contract associated with the copy token to verify the copy token; in response to the verification, generating, by the verification node, a media copy key for generating a Blu-ray copy; and recording, by the verification node, the copy token on a ledger of the blockchain network to indicate that the copy token has been spent.
[0008] Another example embodiment provides a non-transitory computer-readable medium comprising instructions that, when read by a processor, cause the processor to perform one or more of the following: receiving a copy request from a user node via a blockchain network, the request comprising a copy token; calling a smart contract associated with the copy token to verify the copy token; in response to the verification, generating a media copy key for generating a Blu-ray copy; and recording the copy token on a ledger of the blockchain network to indicate that the copy token has been spent. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] Figure 1 A network diagram of a system including a database according to an example embodiment is shown.
[0010] Figure 2A An example blockchain architecture configuration is shown according to an example embodiment.
[0011] Figure 2B A blockchain transaction flow according to an example embodiment is shown.
[0012] Figure 3A A permission network according to an example embodiment is shown.
[0013] Figure 3B Another permission network according to an example embodiment is shown.
[0014] Figure 4A A flow chart according to an example embodiment is shown.
[0015] Figure 4B Another flowchart according to an example embodiment is shown.
[0016] Figure 5A An example system configured to perform one or more operations described herein is shown in accordance with an example embodiment.
[0017] Figure 5B Another example system configured to perform one or more operations described herein is shown in accordance with an illustrative embodiment.
[0018] Figure 5C Another example system configured to utilize smart contracts according to an example embodiment is shown.
[0019] Figure 5D Yet another example system configured to utilize blockchain according to example embodiments is shown.
[0020] Fig. 6A A process of adding a new block to a distributed ledger is shown according to an example embodiment.
[0021] Figure 6B The content of a new data block according to an example embodiment is shown.
[0022] Figure 6C A blockchain of digital content is shown according to an example embodiment.
[0023] Fig.6D Blocks that may represent a block structure in a blockchain are shown according to example embodiments.
[0024] Fig. 7A An example blockchain storing machine learning (artificial intelligence) data is shown according to an example embodiment.
[0025] Figure 7B An example quantum-secure blockchain is shown according to an example embodiment.
[0026] Figure 8 An example system is shown that supports one or more example embodiments. DETAILED DESCRIPTION
[0027] It is readily understood that the components of the present invention, as generally described and illustrated in the figures herein, may be arranged and designed in a variety of different configurations. Therefore, the following detailed description of embodiments of at least one of the methods, devices, non-transitory computer-readable media, and systems, as illustrated in the figures, is not intended to limit the scope of the claimed application, but is merely representative of selected embodiments.
[0028] The current features, structures or characteristics of the present invention described throughout this specification may be combined or removed in any suitable manner in one or more embodiments. For example, throughout the specification, the use of the phrases "exemplary embodiments", "some embodiments" or other similar language refers to the fact that a specific feature, structure or characteristic described in conjunction with the embodiment may be included in at least one embodiment. Therefore, the phrases "exemplary embodiments", "in some embodiments", "in other embodiments" or other similar language appearing throughout the specification do not necessarily all refer to the same set of embodiments, and the described features, structures or characteristics may be combined or removed in any suitable manner in one or more embodiments. In addition, in the figures, any connection between elements may allow unidirectional and / or bidirectional communication, even if the depicted connection is a unidirectional or bidirectional arrow. In addition, any device depicted in the drawings may be a different device. For example, if a mobile device is shown sending information, a wired device may also be used to send information.
[0029] In addition, although the term "message" may have been used in the description of the embodiment, the application can be applied to many types of networks and data. In addition, although specific types of connections, messages and signaling can be described in exemplary embodiments, the application is not limited to specific types of connections, messages and signaling.
[0030] Example embodiments provide methods, systems, components, non-transitory computer-readable media, devices, and / or networks for a blockchain-based Blu-ray copy service.
[0031] In one embodiment, the present application utilizes a decentralized database (such as a blockchain), which is a distributed storage system including multiple nodes that communicate with each other. The decentralized database includes an append-only immutable data structure similar to a distributed ledger that can maintain records between mutually untrusted parties. Untrusted parties are referred to herein as peers or peer nodes. Each peer keeps a copy of the database record, and no single peer can modify the database record without consensus among the distributed peers. For example, peers can execute a consensus protocol to verify blockchain storage transactions, group storage transactions into blocks, and establish a hash chain on the blocks. Because it is necessary to maintain consistency, the process forms a ledger by sorting storage transactions. In various embodiments, permissioned and / or permissionless blockchains can be used. In a public or permissionless blockchain, anyone can participate without a specific identity. Public blockchains can involve local cryptocurrencies and use consensus based on various protocols such as Proof of Work (PoW). On the other hand, permissioned blockchain databases provide secure interactions between a group of entities that share common goals but do not fully trust each other, such as businesses exchanging funds, goods, information, etc.
[0032] The present application can utilize blockchain to operate any programmable logic suitable for decentralized storage solutions, and it is called "smart contract" or "chain code". In some cases, there may be a dedicated chain code for management functions and parameters, called system chain code. The present application can further utilize smart contracts, which are trusted distributed applications that utilize the tamper-proof properties of the blockchain database and the underlying protocol between nodes, which is called endorsement or endorsement policy. Blockchain transactions associated with the application can be "endorsed" before being submitted to the blockchain, and unendorsed transactions will be ignored. The endorsement policy allows the chain code to specify the endorser of the transaction in the form of a set of peer nodes required for endorsement. When the client sends the transaction to the peer specified in the endorsement policy, the transaction is executed to verify the transaction. After verification, the transaction enters the sorting phase, in which a consensus protocol is used to produce an ordered sequence of endorsed transactions grouped into blocks.
[0033] The present application may utilize nodes as communication entities of a blockchain system. A "node" may perform a logical function, i.e., multiple nodes of different types may run on the same physical server. Nodes are grouped in trust domains and are associated with logical entities that control them in various ways. Nodes may include different types, such as clients or submitting client nodes that submit transaction invocations to endorsers (e.g., peers) and broadcast transaction proposals to ordering services (e.g., ordering nodes). Another type of node is a peer node, which may receive transactions submitted by clients, submit transactions, and maintain the state and copy of the ledger of blockchain transactions. Peers may also have the role of endorsers, although this is not required. Ordering service nodes or orderers are nodes that run communication services for all nodes and implement delivery guarantees, such as broadcasts to each peer node in the system when submitting transactions and modifying the world state of the blockchain, which is another name for the initial blockchain transaction that typically includes control and setup information.
[0034] The present application may utilize a ledger that is an ordered, tamper-proof record of all state transitions of a blockchain. State transitions may result from chaincode invocations (i.e., transactions) submitted by parties (e.g., client nodes, ordering nodes, endorser nodes, peer nodes, etc.). Each party (e.g., peer nodes) may maintain a copy of the ledger. Transactions may result in a set of asset key-value pairs being submitted to the ledger as one or more operands (e.g., create, update, delete, etc.). The ledger includes a blockchain (also referred to as a chain) for storing immutable, ordered records in blocks. The ledger also includes a state database that maintains the current state of the blockchain.
[0035] The present application can utilize a chain as a transaction log that is constructed as hash-linked blocks, and each block contains a series of N transactions, where N is equal to or greater than 1. The header of the block includes the hash of the transactions of the block, and the hash of the header of the previous block. In this way, all transactions on the ledger can be ordered sequentially and cryptographically linked together. Therefore, it is impossible to tamper with the ledger data without breaking the hash link. The hash of the most recently added blockchain block represents every transaction that has come before it on the chain, which makes it possible to ensure that all peer nodes are in a consistent and trusted state. The chain can be stored on the peer node file system (i.e., local, attached storage, cloud, etc.), effectively supporting the only attached nature of blockchain workloads.
[0036] The current state of the immutable ledger represents the latest values for all keys included in the chain's transaction log. Because the current state represents the latest key values known to the channel, the current state is sometimes referred to as the world state. Chaincode invocations execute transactions based on the current state data of the ledger. In order for these chaincode interactions to be efficient, the latest values for the keys can be stored in a state database. The state database can be just an indexed view into the chain's transaction log, so the state database can be regenerated from the chain at any time. The state database can be automatically restored (or generated, if necessary) at peer startup and before transactions are accepted.
[0037] Some benefits of the instant solution described and depicted herein include methods and systems for blockchain-based Blu-ray copy services. Exemplary embodiments address issues of time and trust by extending features of databases such as immutability, digital signatures, and serving as a single source of truth. Exemplary embodiments provide solutions for blockchain-based Blu-ray copy services. Blockchain networks can be homogeneous based on asset types and rules for managing assets based on smart contracts.
[0038] The difference between blockchain and traditional database is that blockchain is not a central storage, but a decentralized, immutable, secure storage, where nodes must share changes to records in the storage. Some properties inherent in blockchain and helpful for realizing blockchain include, but are not limited to, immutable ledgers, smart contracts, security, privacy, decentralization, consensus, endorsement, accessibility, etc., which will be further described in this article. According to various aspects, due to the inherent and unique immutable accountability, security, privacy, permissioned decentralization, availability, endorsement and accessibility of smart contracts in blockchain, a system for blockchain-based Blu-ray copy services is implemented. In particular, blockchain ledger data is immutable, which provides an effective method for blockchain-based Blu-ray copy services. In addition, the use of encryption in blockchain can provide security and establish trust. Smart contracts manage the status of assets to complete the life cycle. The example of blockchain is permissioned decentralization. Therefore, each end user can have his own copy of the ledger for access. There can be multiple organizations (and peers) on the blockchain network. Key organizations can act as endorsement peers to verify smart contract execution results, read-sets and write-sets. In other words, the inherent characteristics of blockchain provide an effective implementation method for blockchain-based Blu-ray copy services.
[0039] One of the benefits of the example embodiment is that it improves the functionality of a computing system by implementing a method of a Blu-ray copy service in a blockchain-based system. Through the blockchain system described herein, a computing system can perform the functionality of a blockchain-based Blu-ray copy service by providing access to capabilities such as distributed ledgers, peers, encryption technology, MSP, event processing, etc. In addition, blockchain is able to create a business network and enable any user or organization to participate. Therefore, blockchain is more than just a database. Blockchain has the ability to create a business network of users and on-site / off-site organizations to collaborate and execute service processes in the form of smart contracts.
[0040] Example embodiments provide many benefits over traditional databases. For example, through blockchain, these embodiments provide blockchain's inherent and unique immutable accountability, security, privacy, permissioned decentralization, availability of smart contracts, endorsement, and accessibility.
[0041] At the same time, a traditional database cannot be used to implement the example embodiments because it does not bring all parties onto the business network, it does not create trusted collaboration, and it does not provide efficient storage of digital assets. A traditional database does not provide tamper-proof storage, nor does it provide preservation of the digital assets being stored. Therefore, the method proposed for the blockchain-based Blu-ray copy service cannot be implemented in a traditional database.
[0042] Meanwhile, if the example embodiment is to be implemented using a traditional database, the example embodiment will suffer from unnecessary disadvantages such as search capability, lack of security, and slow transaction speed. In addition, it is simply impossible to implement an automated method for blockchain-based Blu-ray copy services.
[0043] Thus, the example embodiments provide a specific solution to a problem in the art / field of producing Blu-ray copies.
[0044] Example embodiments also change how data is stored within the block structure of the blockchain. For example, digital asset data can be securely stored in a specific part of the data block (i.e., in the header, data segment, or metadata). By storing digital asset data within the data blocks of the blockchain, the digital asset data can be attached to the immutable blockchain ledger through the hash link chain of the blocks. In some embodiments, the data block can be different from the traditional data block in that it can store personal data associated with the digital asset without storing it with the asset in the traditional block structure of the blockchain. By removing personal data associated with the digital asset, the blockchain can provide the benefits of anonymity based on immutable accountability and security.
[0045] According to an exemplary embodiment, a system and method for providing a highly available decentralized means to enable Blu-ray copying by using blockchain technology. According to an exemplary embodiment, a single copy server is replaced by a Blu-ray dedicated blockchain called BluChain. Blu-ray Chain can contain all copy requests and copy history for all Blu-ray media. If necessary, Blu-ray Chain can allow different studios to participate in the same blockchain, or studios can choose to run their own blockchain and provide multiple entry points (servers) to the blockchain. All copies of each media may be visible, so the studio may audit and detect any illegal activities that affect its rights (title). In one embodiment, the copy code can be replaced by a copy token. The copy token can be associated with a smart contract that specifies how to handle specific Blu-ray rights for Blu-ray copies. For example, when a copy token is issued to a user, the user can use any Blu-ray format-specific copy machine (Format-specific Copy Machine, FCM) to make its legal format-specific copy output technology Blu-ray copy.
[0046] Copy Tokens can be one-time use tokens, and output copies can be watermarked for tracking purposes, as well as recorded in the blockchain. Because all devices need to request a means to "spend" a copy token before making a copy, if a device or user is known to make illegal copies (e.g., pirated copies), the user may have their rights to make copies revoked, and any smart contract attempting to "spend" a copy token will be blocked.
[0047] According to an exemplary embodiment, users can purchase copy codes from online retailers or load copy codes from media they own. These copy codes can then be used to request copy tokens from the Copy Tokenissuing service. Users can download an application or client software that will generate a public / private key pair that can be used to register with the blockchain service (Blu-ray Chain) and be assigned a unique Blu-ray Chain address that the user can use to receive copy tokens. The copy token is then sent to the address. Users can use their own private key to prove ownership of the token or spend it when they need to copy their own Blu-ray media. The copy token is associated with a smart contract that specifies how the FCM generates a format-specific copy output technology Blu-ray copy. All copy token requests, copy requests, etc. are recorded in the Blu-ray Chain structure, allowing the studio to monitor how the Blu-ray copy is made. This may be useful from both a legal and business perspective. The studio can monitor how the copy is made and use this data to provide incentives to users, not just copies. Similarly, the Blu-ray copy is watermarked with Blu-ray Chain-specific metadata (e.g., user / device Blu-ray Chain address). Thus, the user can track the source of any illegal copies shared in the file sharing network. The user can load the media copy code via the mobile device. The code is stored as a QR code and is unique to the media. Similarly, when the user wishes to copy his Blu-ray disc, the user can type the code on the media. The user can also purchase the copy code from an online retailer.
[0048] The Blu-ray Chain service consists of several copy / verification nodes, copy token issuers, and Blu-ray copy clients. The ecosystem is similar to a traditional blockchain, where users have wallets that allow them to store public / private key pairs (for exporting user addresses), copy / verification nodes, and a structure that provides a set of REST APIs for connecting and verifying blockchain services, deploying and calling smart contracts, and viewing transaction history. The baseline consensus protocol can be adjusted to meet studio and traffic needs.
[0049] According to an exemplary embodiment, smart contracts are dynamically defined by different studios and can be fine-tuned based on specific regions or seasons. For example, a studio might limit the time a user can copy Blu-ray media based on region and theatrical release windows.
[0050] According to an exemplary embodiment, the blockchain may include a token storage node and a copy token issuer node. The token storage node and the copy token issuer node are responsible for issuing copy tokens to users and associating the tokens with specific smart contracts. According to an exemplary embodiment, users may interact primarily with a Blu-ray copy client software package, which serves as the main driver for a format-specific copy machine (FCM). Similarly, the client may act as an interface between the blockchain service and the FCM. The FCM may interact with the Blu-ray Chain service in two ways. First, the FCM may be implemented without blockchain support. This means that the FCM does not need to be modified, however, the client software (e.g., the resident program of the player) will need to add the necessary libraries / calls to engage with the blockchain service via software / firmware updates. The second version of the FCM is a blockchain or Blu-ray Chain-ready FCM that has the necessary hardware / firmware to communicate with the Blu-ray Chain. This may allow studios to have better end-to-end security and better control over the content played inside the FCM. The client may interact with the Blu-ray Chain service through a RESTful service, which may allow the client to communicate with the backend through an encrypted channel (e.g., HTTPS). Whenever a Blu-ray copy operation is required, a RESTful service needs to be called, allowing the Blu-ray copy source to be provided (e.g., capturing all copy requests, token issuance, token expenditure, etc.). The Blu-ray copy client may be responsible for generating and maintaining the software public / private key pairs required to use copy tokens and communicate with the Blu-ray Chain service. In a sense, the Blu-ray copy client may contain some wallet functions similar to software wallets. The Blu-ray copy client can generate unique Blu-ray Chain addresses for users and FCMs. These addresses can be used to send copy tokens to identified users / devices, and to track the use / expenditure of copy tokens. Similarly, additional functionality can be added to bind copy tokens to specific FCM addresses, meaning that users can only copy in FCMs authorized by his / her Blu-ray Chain. This will allow studios to implement a higher degree of control over where media is copied. By requiring users to register their devices / software clients with the Blu-ray Chain service, this also allows the introduction of the concept of trusted FCM / Blu-ray copy clients.
[0051] According to an exemplary embodiment, a smart contract can run on a Blu-ray chain copy / verification node and verify / authorize FCM to make legal format-specific copy output technology Blu-ray copies. Blu-ray chain may allow multiple studios to coexist in the same structure. One value added by this is that different studios can benefit from real-time detection of illegal copy activities by parties in the Blu-ray chain ecosystem. These nodes are replicated across sites and can be hosted by many studios similar to IBM Hyperledger verification nodes. According to an exemplary embodiment, the idea is to allow Blu-ray copy clients to connect to any of these nodes in order to execute smart contracts associated with copy tokens. These nodes maintain the complete history of the Blu-ray chain and replicate it across sites, thereby removing the single point of failure that exists in the current architecture of the AACS2 Blu-ray copy system model. Similarly, the more studios participate in the Blu-ray chain, the more verification nodes are available, which will benefit the entire ecosystem. The verification node is responsible for verifying the copy token by verifying that the user who attempts to spend the token does have (multiple) tokens. This can be achieved by issuing a challenge to the user who attempts to spend the token. The user can use his / her private key to sign the challenge provided by the verification node. When verifying, the node will continue to spend tokens that it has not spent before. This can be achieved by looking up the hash of the token, which is used to look up the token information and the smart contract associated with the token. Smart contracts can be called and evaluated via the smart contract hash. When completed, the smart contract will generate the MediaCopy Key required by FCM to make the copy, and also generate any metadata required to create the final copy.
[0052] According to an exemplary embodiment, a Blu-ray copy service is provided. Blu-ray copy can be implemented as follows. First, a copy token is generated for a user at address A of the Blu-ray chain. The address uniquely identifies the user. The address is also associated with a given device. Similarly, a smart contract is associated with token T and deployed in the Blu-ray chain structure. Therefore, when the token is spent, the smart contract is called by the copy / verification node. Next, the user may decide to request the FCM to make a copy of the Blu-ray disc. In order to make a copy, the client software can load the unique ID (UUID) of the FCM, its public key PK cm , and request copy permission from the copy / verification node. The user copies the token ID of the token T, the PK of the FCM cmThe copy / verification node can record the request in the Blu-ray chain structure and call the smart contract associated with the copy token T. The smart contract can evaluate the token, verify that the user can spend the token, verify that there is no double spending (for example, only one copy can be made), and generate media copy keys, as well as the output format metadata required to generate Blu-ray copies of format-specific copy output technology. The data generated by the smart contract is then used by the FCM's PK cm The FCM then uses its secret key SK to make a copy of the media. cm The metadata and necessary media copy keys are decrypted. Finally, FCM makes a copy and watermarks the media with the necessary information to mark the media and identify the origin of the copy (e.g., FCM's UUID, the user's Blu-ray link address, timestamp, etc.).
[0053] Figure 1 A logical network diagram of a Blu-ray copy service in a blockchain network according to an example embodiment is shown.
[0054] refer to Figure 1 , the example network 100 includes a verification node 102 connected to a user node 107 and a copy token issuer node 105 through a blockchain network (blockchain) 106. The blockchain network 106 may have a ledger (ledger DB (database)) 108 for storing copy tokens and copy transactions. The user node 107 may be connected to a blockchain-ready Blu-ray duplicator (not shown). Although this example describes only one verification node 102 in detail, multiple such nodes may be connected to the blockchain 106. It should be understood that the verification node 102 may include additional components, and some components described herein may be removed and / or modified without departing from the scope of the verification node 102 disclosed herein. The verification node 102 may be a computing device or a server computer, etc., and may include a processor 104, which may be a semiconductor-based microprocessor, a central processing unit (CPU), an application specific integrated circuit (ASIC), a field-programmable gate array (FPGA), and / or another hardware device. Although a single processor 104 is depicted, it should be understood that the verification node 102 may include multiple processors, multiple cores, etc. without departing from the scope of the verification node 102 system.
[0055] The verification node 102 may also include a non-transitory computer-readable medium 112 on which machine-readable instructions executable by the processor 104 may be stored. Examples of machine-readable instructions are shown as 114-120 and are further discussed below. Examples of non-transitory computer-readable media 112 may include electronic, magnetic, optical, or other physical storage devices containing or storing executable instructions. For example, the non-transitory computer-readable medium 112 may be a random access memory (Random Access memory, RAM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a hard disk, an optical disk, or other type of storage device.
[0056] The processor 104 can obtain, decode and execute machine-readable instructions 114 to receive a copy request from a user node 107 through the blockchain network 106. The request may include a copy token. As described above, the blockchain ledger 108 can store the spent copy tokens and transactions 110. The blockchain network 106 can be configured to use one or more smart contracts that manage transactions of multiple participating nodes. The processor 104 can obtain, decode and execute machine-readable instructions 116 to call a smart contract associated with the copy token to verify the copy token. The processor 104 can obtain, decode and execute machine-readable instructions 118 to generate a media copy key for generating a Blu-ray copy in response to the verification. The processor 104 can obtain, decode and execute machine-readable instructions 120 to record the copy token on the ledger of the blockchain network to indicate that the copy token is spent. Therefore, an efficient blockchain-based Blu-ray copy service can be provided.
[0057] Figure 2A A blockchain architecture configuration 200 is shown according to an example embodiment. Figure 2A, the blockchain architecture 200 may include certain blockchain elements, such as a set of blockchain nodes 202. The blockchain nodes 202 may include one or more nodes 204-210 (these four nodes are depicted by way of example only). These nodes participate in many activities, such as blockchain transaction addition and verification processes (consensus). One or more blockchain nodes 204-210 may endorse transactions based on endorsement policies and may provide ordering services for all blockchain nodes in the architecture 200. The blockchain node may initiate blockchain authentication and attempt to write to the blockchain immutable ledger stored in the blockchain layer 216, a copy of which may also be stored on the underlying physical infrastructure 214. The blockchain configuration may include one or more applications 224, which are linked to application programming interfaces (APIs) 222 to access and execute stored program / application code 220 (e.g., chaincode, smart contracts, etc.), which may be created based on the customized configuration sought by the participants and may maintain their own state, control their own assets, and receive external information. This may be deployed as a transaction and installed on all blockchain nodes 204-210 via attachment to the distributed ledger.
[0058] The blockchain base or platform 212 may include various layers of blockchain data, services (e.g., cryptographic trust services, virtual execution environments, etc.), and support physical computer infrastructure that can be used to receive and store new transactions and provide access to auditors seeking to access data entries. The blockchain layer 216 may expose an interface that provides access to the virtual execution environment necessary to process program code and participate in the physical infrastructure 214. Cryptographic trust services 218 may be used to verify transactions (such as asset exchange transactions) and keep the information private.
[0059] Figure 2A The blockchain architecture configuration of the blockchain platform 212 can process and execute program / application code 220 via one or more interfaces exposed and services provided by the blockchain platform 212. The code 220 can control blockchain assets. For example, the code 220 can store and transmit data and can be executed by the nodes 204-210 in the form of smart contracts and chain codes, which are associated with conditions or other code elements subject to their execution. As a non-limiting example, smart contracts can be created to perform reminders, updates, and / or other notifications subject to changes, updates, etc. The smart contract itself can be used to identify rules associated with authorization and access requirements and the use of the ledger. For example, the copy token information 226 can be processed by one or more processing entities (e.g., virtual machines) included in the blockchain layer 216. The result 228 can include a data block reflecting the tokens spent. The physical infrastructure 214 can be used to retrieve any data or information described herein.
[0060] Smart contracts can be created via high-level applications and programming languages, and then written into blocks of a blockchain. A smart contract can include executable code that is registered, stored, and / or replicated with a blockchain (e.g., a distributed network of blockchain peers). A transaction is the execution of smart contract code, which can be executed in response to satisfying a condition associated with the smart contract. The execution of a smart contract can trigger (multiple) trusted modifications to the state of a digital blockchain ledger. (Multiple) modifications to the blockchain ledger caused by the execution of a smart contract can be automatically replicated throughout the distributed network of blockchain peers through one or more consensus protocols.
[0061] Smart contracts can write data to the blockchain in the format of key-value pairs. In addition, smart contract code can read values stored in the blockchain and use them in application operations. Smart contract code can write the output of various logical operations to the blockchain. The code can be used to create temporary data structures in virtual machines or other computing platforms. The data written to the blockchain can be public and / or can be encrypted and maintained as private. Temporary data used / generated by smart contracts is held in memory by the provided execution environment and deleted once the data required by the blockchain is identified.
[0062] Chaincode may include a code interpretation of a smart contract, with additional features. As described herein, chaincode may be a program code deployed on a computing network where it is executed and validated by multiple chain validators together in a consensus process. The chaincode receives the hash and retrieves from the blockchain a hash associated with a data template created by using a previously stored feature extractor. If the hash of the hashed identifier and the hash created from the stored identifier template data match, the chaincode sends an authorization key for the requested service. The chaincode may write data associated with cryptographic details to the blockchain.
[0063] Figure 2B An example of a blockchain transaction flow 250 between blockchain nodes according to an example embodiment is shown. Figure 2B, the transaction flow may include sending a transaction proposal (transaction) 291 by the application client node 260 to the endorsing peer node (first peer node) 281. The endorsing peer node 281 may verify the client signature and execute the chaincode function to initiate the transaction. The output may include the chaincode result, the set of key / value versions read in the chaincode (read set), and the set of key / values written in the chaincode (write set). If approved, the proposal response 292 is sent back to the client 260 along with the endorsement signature. The client 260 assembles the endorsement into the transaction payload (transaction data) 293 and broadcasts it to the sorting service node (fourth peer node or sorting node) 284. The sorting service node 284 then delivers the sorted transaction as a block to all peers 281-283 on the channel. Each peer 281-283 may validate the transaction before submitting it to the blockchain. For example, the peer may check the endorsement policy to ensure that the correct provisioning of the specified peer has signed the result and that the signature is authenticated against the transaction payload 293 .
[0064] Reference again Figure 2B , the client node 260 initiates a transaction 291 by constructing a request and sending it to the peer node 281 acting as an endorser. The client 260 may include an application utilizing a supported software development kit (SDK) that utilizes the available APIs to generate a transaction proposal. The proposal is a request to invoke a chaincode function so that data can be read and / or written to the ledger (i.e., to write a new key-value pair for an asset). The SDK can be used as a shim to package the transaction proposal into a format for the appropriate architecture (e.g., protocol buffers via remote procedure call (RPC)) and utilize the client's cryptographic credentials to produce a unique signature for the transaction proposal.
[0065] In response, the endorsing peer 281 may verify that (a) the transaction proposal is well-formed, (b) the transaction has not been submitted in the past (replay attack protection), (c) the signature is valid, and (d) the submitter (in the example, client 260) is properly authorized to perform the proposed operation on the channel. The endorsing peer 281 may input the transaction proposal as a parameter to the invoked chaincode function. The chaincode is then executed against the current state database to produce a transaction result including a response value, a read collection, and a write collection. However, no updates are made to the ledger at this time. In 292, the set of values is passed back to the SDK of client 260 along with the signature of the endorsing peer 281 as a proposal response 292, and client 260 parses the payload for the application to consume.
[0066] In response, the client 260 application checks / verifies the signatures of the endorsing peers and compares the proposal responses to determine if the proposal responses are identical. If the chaincode is only querying the ledger, the application will check the query response and will typically not submit the transaction to the ordering service node 284. If the client application intends to submit the transaction to the ordering service node 284 to update the ledger, the application determines whether the specified endorsement policy has been satisfied (i.e., whether all peer nodes required for the transaction have endorsed the transaction) before submitting. Here, the client may include only one of the multiple parties to the transaction. In this case, each client may have its own endorsing node, and each endorsing node will need to endorse the transaction. The architecture is such that even if the application chooses not to check the response or otherwise forward unendorsed transactions, the endorsement policy will still be enforced by the peers and maintained during the submission verification phase.
[0067] After a successful check, in step 293, client 260 assembles the endorsement into a transaction and broadcasts the transaction proposal and response in a transaction message to ordering node 284. The transaction may contain read / write sets, signatures of endorsing peers, and channel IDs. Ordering node 284 does not need to examine the entire contents of a transaction to perform its operations, instead, ordering node 284 can simply receive transactions from all channels in the network, sort them chronologically by channel, and create a block of transactions for each channel.
[0068] The transaction block is delivered from the ordering node 284 to all peer nodes 281-283 on the channel. The transactions 294 within the block are validated to ensure that any endorsement policies are met and that there have been no changes to the ledger state for the read set variables since the transaction execution generated the read set. The transactions in the block are marked as valid or invalid. In addition, in step 295, each peer node 281-283 attaches the block to the channel's chain, and for each valid transaction, the write set is committed to the current state database. An event is published to notify the client application that the transaction (call) has been immutably attached to the chain and whether the transaction is verified or unverified.
[0069] Figure 3AAn example of a permissioned blockchain network 300 is shown, featuring a decentralized, decentralized peer-to-peer structure. In this example, a blockchain user 302 can initiate a transaction to a permissioned blockchain 304. In this example, a transaction can be a deployment, call, or query, and can be issued through a client application utilizing an SDK, directly through an API, etc. The network can provide access to regulators 306 (such as auditors). The blockchain network operator 308 manages member permissions, such as registering regulators 306 as "auditors" and blockchain users 302 as "clients." Auditors can be limited to querying the ledger, while clients can be authorized to deploy, call, and query certain types of chaincodes.
[0070] Blockchain developers 310 can write chaincodes and client-side applications. Blockchain developers 310 can deploy chaincodes directly to the network through an interface. To include credentials from traditional data sources 312 in chaincodes, developers 310 can use out-of-band connections to access data. In this example, blockchain users 302 connect to a permissioned blockchain 304 through peer nodes 314. Before conducting any transactions, peer nodes 314 retrieve the user's registration and transaction certificates from a certificate authority 316 that manages user roles and permissions. In some cases, blockchain users must have these digital certificates before they can conduct transactions on the permissioned blockchain 304. At the same time, users attempting to use chaincodes may need to verify their credentials on traditional data sources 312. To confirm the user's authorization, the chaincode may use an out-of-band connection to the data through a traditional processing platform 318.
[0071] Figure 3B Another example of a permissioned blockchain network 320 is shown, featuring a decentralized, decentralized peer-to-peer structure. In this example, a blockchain user 322 can submit transactions to a permissioned blockchain 324. In this example, a transaction can be a deployment, call, or query, and can be issued through a client-side application utilizing an SDK, directly through an API, etc. The network can provide access to regulators 326 (such as auditors). The blockchain network operator 328 manages member permissions, such as registering regulators 326 as "auditors" and blockchain users 322 as "clients." Auditors can be limited to querying the ledger, while clients can be authorized to deploy, call, and query certain types of chaincodes.
[0072] Blockchain developers 330 write chaincodes and client applications. Blockchain developers 330 can deploy chaincodes directly to the network through interfaces. To include credentials from traditional data sources 332 in chaincodes, blockchain developers 330 can use out-of-band connections to access data. In this example, blockchain users 322 connect to the network through peer nodes 334. Before conducting any transactions, peer nodes 334 retrieve the user's registration and transaction certificates from certificate authorities 336. In some cases, blockchain users must have these digital certificates before they can conduct transactions on the permissioned blockchain 324. At the same time, users attempting to use chaincodes may need to verify their credentials on traditional data sources 332. To confirm the user's authorization, chaincodes can use out-of-band connections to this data through traditional processing platforms 338.
[0073] Figure 4A A flowchart 400 of an example method for a blockchain-based Blu-ray copy service according to an example embodiment is shown. Figure 4A , method 400 may include one or more of the steps described below.
[0074] Figure 4A The verification node 102 (see Figure 1 ) is a flowchart of an example method performed. It should be understood that Figure 4A The method 400 depicted in the embodiment may include additional operations, and some of the operations described therein may be removed and / or modified without departing from the scope of the method 400. For illustrative purposes, the description of the method 400 also refers to Figure 1 In particular, the processor 104 of the verification node 102 may perform some or all of the operations included in the method 400.
[0075] refer to Figure 4A At block 412, the processor 104 may receive a copy request from a user node via the blockchain network, the request including a copy token. At block 414, the processor 104 may call a smart contract associated with the copy token to verify the copy token. At block 416, the processor 104 may generate a media copy key for generating a Blu-ray copy in response to the verification. At block 418, the processor 104 may record the copy token on a ledger of the blockchain network to indicate that the copy token was spent.
[0076] Figure 4B A flowchart 450 of an example method for a blockchain-based Blu-ray copy service according to an example embodiment is shown. Figure 4B, method 450 may also include one or more of the following steps. In box 452, processor 104 may output format metadata to generate a format-specific Blu-ray copy. In box 454, processor 104 may encrypt the media copy key with the public key of the format-specific copier associated with the user node. In box 456, processor 104 may verify that the copy token belongs to the user node. In box 458, processor 104 may call a smart contract when it is detected that the user node attempts to spend the copy token. In box 460, processor 104 may issue a challenge signed by the private key of the user node to the user node to verify the copy token. In box 462, processor 104 may record a transaction on a ledger of the blockchain network to indicate that a Blu-ray copy associated with the copy request was made.
[0077] Figure 5A An example system 500 is shown, including a physical infrastructure 510 configured to perform various operations, according to an example embodiment. Figure 5A , the physical infrastructure 510 includes a module 512 and a module 514. The module 514 includes a blockchain 520 and a smart contract 530 (which may reside on the blockchain 520), and the blockchain 520 and the smart contract 530 may perform any operation step 508 (in the module 512) included in any example embodiment. The step / operation 508 may include one or more embodiments described or depicted, and may represent output or write information written to or read from one or more smart contracts 530 and / or blockchain 520. The physical infrastructure 510, the module 512, and the module 514 may include one or more computers, servers, processors, memories, and / or wireless communication devices. In addition, the module 512 and the module 514 may be the same module.
[0078] Figure 5B Another example system 540 is shown that is configured to perform various operations according to an example embodiment. Figure 5B , system 540 includes module 512 and module 514. Module 514 includes blockchain 520 and smart contract 530 (which may reside on blockchain 520), which can perform any operation step 508 (in module 512) included in any example embodiment. Step / operation 508 may include one or more embodiments described or depicted, and may represent output or write information written or read to / from one or more smart contracts 530 and / or blockchain 520. Physical infrastructure 510, module 512, and module 514 may include one or more computers, servers, processors, memories, and / or wireless communication devices. In addition, module 512 and module 514 may be the same module.
[0079] Figure 5CAn example system using a smart contract configuration between parties to a contract and an intermediary server configured to implement smart contract terms on a blockchain is shown according to an example embodiment. Figure 5C , configuration 550 may represent a communication session, an asset transfer session, or a process or procedure driven by a smart contract 530 that explicitly identifies one or more user devices 552 and / or 556. The execution, operation, and results of the smart contract execution may be managed by a server 554. The content of the smart contract 530 may require digital signatures of one or more entities 552 and 556 of the parties to the smart contract transaction. The results of the smart contract execution may be written to the blockchain 520 as a blockchain transaction. The smart contract 530 resides on the blockchain 520, which may reside on one or more computers, servers, processors, memories, and / or wireless communication devices.
[0080] Figure 5D A system 560 including a blockchain is shown according to an example embodiment. Figure 5D In the example of , an application programming interface (API) gateway 562 provides a public interface for accessing blockchain logic (e.g., smart contracts 530 or other chaincodes) and data (e.g., distributed ledgers, etc.). In this example, the API gateway 562 is a public interface for executing transactions (calls, queries, etc.) on the blockchain by connecting one or more entities 552 and 556 to blockchain peers (i.e., servers 554). Here, the server 554 is a blockchain network peer component that holds a copy of the world state and distributed ledger, allowing clients 552 and 556 to query data about the world state and submit transactions to the blockchain network, where, according to the smart contract 530 and the endorsement policy, the endorsing peer will run the smart contract 530.
[0081] The above embodiments may be implemented in hardware, a computer program executed by a processor, firmware, or a combination thereof. The computer program may be embodied on a computer-readable medium, such as a storage medium. For example, the computer program may reside in a random access memory ("RAM"), flash memory, read-only memory ("ROM"), erasable programmable read-only memory ("EPROM"), electrically erasable programmable read-only memory ("EEPROM"), registers, a hard disk, a removable disk, a compact disk read-only memory ("CD-ROM"), or any other form of storage medium known in the art.
[0082] An exemplary storage medium may be coupled to a processor such that the processor can read information from and write information to the storage medium. Alternatively, the storage medium may be integrated into the processor. The processor and the storage medium may reside in an application specific integrated circuit ("ASIC"). Alternatively, the processor and the storage medium may reside as discrete components.
[0083] Fig. 6A 6 shows a process 600 in which a new block is added to a distributed ledger 620 according to an example embodiment, and Figure 6B The content of a new data block structure 630 of a blockchain according to an example embodiment is shown. Fig. 6A , a client (not shown) may submit a transaction to a blockchain node 611, 612, and / or 613. A client may be an instruction received from any source to enact an activity on a blockchain 622. For example, a client may be an application acting on behalf of a requester (such as a device, person, or entity) to propose a transaction for a blockchain. Multiple blockchain peers (e.g., blockchain nodes 611, 612, and 613) may maintain the state of the blockchain network and a copy of the distributed ledger 620. Different types of blockchain nodes / peers may appear in a blockchain network, including endorsement peers, which simulate and approve transactions proposed by clients, and approval peers, which verify endorsements, validate transactions, and submit transactions to the distributed ledger 620. In this example, blockchain nodes 611, 612, and 613 may perform the roles of endorser nodes, submitter nodes, or both.
[0084] The distributed ledger 620 includes a blockchain that stores immutable, ordered records in the form of blocks, and includes a state database 624 (current world state) that maintains the current state of the blockchain 622. There can be one distributed ledger 620 per channel, and each peer maintains its own copy of the distributed ledger 620 for each channel it belongs to. The blockchain 622 is a transaction log structured as hash-linked blocks, where each block contains a sequence of N transactions. A block can include various components, such as Figure 6B Block links (by Fig. 6A ) can be generated by adding a hash of the header of the previous block within the block header of the current block. In this way, all transactions on the blockchain 622 are ordered and cryptographically linked together to prevent tampering of the blockchain data without breaking the hash link. In addition, due to the link, the latest block in the blockchain 622 represents every transaction before it. The blockchain 622 can be stored on a peer-to-peer file system (local or attached storage) that supports append-only blockchain workloads.
[0085] The current state of the blockchain 622 and the distributed ledger 620 can be stored in the state database 624. Here, the current state data represents the latest values of all keys included in the chain transaction log of the blockchain 622. Chaincode calls execute transactions against the current state in the state database 624. In order to make these chaincode interactions very efficient, the latest values of all keys are stored in the state database 624. The state database 624 can include an indexed view in the transaction log of the blockchain 622, so it can be regenerated from the chain at any time. The state database 624 can be automatically restored (or generated if necessary) at the start of the peer before the transaction is accepted.
[0086] The endorsing node receives the transaction from the client and endorses the transaction based on the simulation results. The endorsing node holds the smart contract that simulates the transaction proposal. When the endorsing node endorses the transaction, the endorsing node creates a transaction endorsement, which is a signed response from the endorsing node to the client application indicating the endorsement of the simulated transaction. The method of endorsing the transaction depends on the endorsement policy that can be specified in the chaincode. An example of an endorsement policy is "a majority of endorsing peers must endorse the transaction". Different channels may have different endorsement policies. The client application forwards the endorsed transaction to the sorting service 610.
[0087] The ordering service 610 accepts endorsed transactions, orders them into blocks, and delivers the blocks to the committing peers. For example, when a transaction threshold is reached, a timer expires, or other conditions, the ordering service 610 can start a new block. Fig. 6A In the example of , blockchain node 612 is a commit peer that has received a new data block 630 for storage on blockchain 622. The first block of a blockchain may be referred to as a genesis block, which includes information about the blockchain, its members, data stored therein, and the like.
[0088] The ordering service 610 consists of a cluster of orderers. The ordering service 610 does not process transactions, smart contracts, or maintain a shared ledger. Instead, the ordering service 610 can accept endorsed transactions and specify the order in which these transactions are submitted to the distributed ledger 620. The architecture of the blockchain network can be designed so that "ordering" becomes a specific implementation of a pluggable component (e.g., Solo, Kafka, BFT, etc.).
[0089] Transactions are written to the distributed ledger 620 in a consistent order. The order of transactions is established to ensure that updates to the state database 624 are valid when they are submitted to the network. Unlike cryptocurrency blockchain systems where ordering occurs by solving cryptographic puzzles, in this example, the parties to the distributed ledger 620 can choose the ordering mechanism that best suits the network.
[0090] When the ordering service 610 initializes a new data block 630, the new data block 630 may be broadcast to the submitting peers (e.g., blockchain nodes 611, 612, and 613). In response, each submitting peer verifies the transactions within the new data block 630 by checking to ensure that the read set and the write set still match the current world state in the state database 624. Specifically, the submitting peer may determine whether the read data that existed when the endorser simulated the transaction is the same as the current world state in the state database 624. When the submitting peer verifies the transaction, the transaction is written to the blockchain 622 on the distributed ledger 620, and the state database 624 is updated with the write data from the read-write set. If the transaction fails, that is, if the submitting peer finds that the read-write set does not match the current world state in the state database 624, the transaction that was ordered into the block will still be included in the block, but it will be marked as invalid and the state database 624 will not be updated.
[0091] refer to Figure 6B , a new data block 630 (also referred to as a data block) stored on the blockchain 622 of the distributed ledger 620 may include multiple data segments, such as a block header 640, block data 650, and block metadata 660. It should be understood that the various depicted blocks and their contents, e.g. Figure 6B The illustrated new data block 630 and its contents are merely examples and are not meant to limit the scope of the example embodiments. The new data block 630 may store transaction information for N (e.g., 1, 10, 100, 500, 1000, 2000, 3000, etc.) transactions within the block data 650. The new data block 630 may also include a previous block (e.g., in the block header 640) within the block header 640. Fig. 6A Specifically, the block header 640 may include a hash of the header of the previous block. The block header 640 may also include a unique block number, a hash of the block data 650 of the new data block 630, etc. The block number of the new data block 630 may be unique and assigned in various sequences, such as increments / sequences starting from zero.
[0092] The block data 650 may store transaction information for each transaction recorded in the new data block 630. For example, the transaction data may include one or more of the following: transaction type, version, timestamp, channel ID of the distributed ledger 620, transaction ID, epoch, payload visibility, chaincode path (deploy tx), chaincode name, chaincode version, inputs (chaincode and function), client (creator) identifier such as public key and certificate, client signature, endorser identity, endorser signature, proposal hash, chaincode event, response status, namespace, read set (list of keys and versions read by the transaction, etc.), write set (list of keys and values, etc.), start key, end key, key list, Merkel tree query summary, etc. Transaction data may be stored for each of the N transactions.
[0093] In some embodiments, block data 650 may also store new data 662 that adds additional information to the hashed chain of blocks in blockchain 622. The additional information includes one or more steps, features, processes, and / or actions described or depicted herein. Thus, new data 662 may be stored in an immutable block log on distributed ledger 620. Some benefits of storing such new data 662 are reflected in various embodiments disclosed and depicted herein. Although in Figure 6B , new data 662 is depicted in block data 650 , but may also be located in block header 640 or block metadata 660 .
[0094] The block metadata 660 may store a plurality of metadata fields (e.g., as a byte array, etc.). The metadata fields may include a signature on the creation of the block, a reference to the last configuration block, a transaction filter identifying valid and invalid transactions within the block, a last offset maintained by the sorting service that sorts the block, etc. The signature, last configuration block, and sorting party metadata may be added by the sorting service 610. Meanwhile, the submitter of the block (e.g., blockchain node 612) may add validity / invalidity information based on endorsement policies, verification of read / write collections, etc. The transaction filter may include a byte array of size equal to the number of transactions in the block data 650 and a verification code identifying whether the transaction is valid or invalid.
[0095] Figure 6CAn embodiment of a blockchain 670 for digital content is shown in accordance with embodiments described herein. Digital content may include one or more files and associated information. These files may include media, images, video, audio, text, links, graphics, animations, web pages, documents, or other forms of digital content. The immutable, append-only aspect of the blockchain serves as a security measure to protect the integrity, validity, and authenticity of the digital content, making it suitable for use in legal proceedings where admissibility rules apply, or in other environments where evidence is considered or the presentation and use of digital information is of interest. In such cases, the digital content may be referred to as digital evidence.
[0096] A blockchain can be formed in a variety of ways. In one embodiment, digital content can be contained in and accessed from the blockchain itself. For example, each block of the blockchain can store a hash value of reference information (e.g., header, value, etc.) and its associated digital content. The hash value and associated digital content can then be encrypted together. Therefore, the digital content of each block can be accessed by decrypting each block in the blockchain, and the hash value of each block can be used as a basis for referencing the previous block. This can be illustrated as follows:
[0097]
[0098] In one embodiment, the digital content may not be included in the blockchain. For example, the blockchain may store a cryptographic hash of the content of each block without any digital content. The digital content may be stored in another storage area or memory address in association with the hash value of the original file. The other storage area may be the same storage device used to store the blockchain, or may be a different storage area, or even a separate relational database. The digital content of each block may be referenced or accessed by obtaining or querying the hash value of the block of interest and then looking up the hash value in a storage area where the actual digital content is stored. This operation may be performed by, for example, a database keeper. This may be illustrated as follows:
[0099]
[0100]
[0101] exist Figure 6C In the example embodiment of FIG. 670 , blockchain 670 includes a plurality of blocks 678 1 , 678 2 , . . . 678 , which are cryptographically linked in an ordered sequence. N , where N ≥ 1. Used to link blocks 6781, 6782, ... 678 N The encryption can be any of a number of keyed or non-keyed hash functions. In one embodiment, blocks 6781, 6782, ... 678 NSubject to a hash function that produces an n-bit alphanumeric output (where n is 256 or another number) from an input based on the information in the block. Examples of such hash functions include, but are not limited to, SHA-type (SHA stands for Secure Hash Algorithm) algorithms, Merkle-Damgard algorithms, HAIFA algorithms, Merkle tree algorithms, nonce-based algorithms, and non-collision-resistant PRF algorithms. In another embodiment, blocks 6781, 6782, ..., 678 N May be cryptographically linked by a function other than a hash function.For purposes of illustration, the following description is made with reference to a hash function (eg, SHA-2).
[0102] Each block in the blockchain is 6781, 6782, ..., 678 N Includes a header, a file version, and a value. Due to the hashing operation performed on the blockchain, the header and value are different for each block. In one embodiment, the value can be included in the header. As described in more detail below, the version of the file can be the original file or a different version of the original file.
[0103] The first block 6781 in the blockchain is called a genesis block and includes a header 6721, an original file 6741, and an initial value 6761. The hashing scheme used for the genesis block and all subsequent blocks may be different. For example, all the information in the first block 6781 may be hashed together and hashed at once, or each or a portion of the information in the first block 6781 may be hashed separately, and then the hashing of the separately hashed portions may be performed.
[0104] The header 6721 may include one or more initial parameters, which may include, for example, a version number, a timestamp, a freshness value, root information, a difficulty level, a consensus protocol, a duration, a media format, a source, descriptive keywords, and / or other information associated with the original file 6741 and / or the blockchain. The header 6721 may be automatically generated (e.g., by blockchain network management software) or manually generated by a blockchain participant. N Unlike the header in , header 6721 in the origin block does not reference the previous block, simply because there is no previous block.
[0105] The original file 6741 in the origin block can be data captured by a device with or without processing, such as before being included in the blockchain. The original file 6741 is received from a device, media source, or node through a system interface. The original file 6741 is associated with metadata, which can be manually or automatically generated by a user, device, and / or system processor, for example. The metadata can be included in the first block 6781 in association with the original file 6741.
[0106] The value 6761 in the origin block is an initial value generated based on one or more unique attributes of the original file 6741. In one embodiment, the one or more unique attributes may include a hash value of the original file 6741, metadata of the original file 6741, and other information associated with the file. In one implementation, the initial value 6761 may be based on the following unique attributes:
[0107] 1) SHA-2 calculated hash value of the original file
[0108] 2) Originating equipment identification
[0109] 3) The start timestamp of the original file
[0110] 4) The original storage location of the original file
[0111] 5) Blockchain network member ID, used for the software that currently controls the original file and associated metadata
[0112] The other blocks of the blockchain are 6782 to 678 N There are also headers, files, and values. However, unlike the first block 6721, each header 6722 to 672 N Include the hash value of the immediately preceding block. The hash value of the immediately preceding block may be just the hash value of the header of the preceding block, or may be the hash value of the entire preceding block. As indicated by arrow 680, by including the hash value of the preceding block in each remaining block, tracing from the Nth block to the origin block (and associated original file) may be performed block by block to establish an auditable and immutable chain-of-custody.
[0113] Header 6722 to 672 in other blocks N Each of the files may also include other information, such as a version number, a timestamp, a freshness value, root information, a difficulty level, a consensus protocol, and / or other parameters or information associated with the corresponding file and / or the blockchain as a whole.
[0114] Files 6742 to 674 in other blocks N May be equal to the original file (the file with metadata), or may be a modified version of the original file in the origin block, depending on, for example, the type of processing performed. The type of processing performed may vary from block to block. The processing may include, for example, any modifications to the file in the preceding block, such as revising information or otherwise changing content, extracting information from the file, or adding or appending information to the file.
[0115] Additionally, or alternatively, the processing may simply involve copying a file from a previous block, changing a storage location of a file, analyzing a file from one or more previous blocks, moving a file from one storage or storage location to another storage or storage location, or performing actions related to the blockchain file and / or its associated metadata. Processing involving analyzing a file may include, for example, appending, including, or otherwise associating various analytics, statistics, or other information associated with the file.
[0116] In other blocks each other block value 6762 to 676 N Is a unique value and all different due to the processing performed. For example, the value in any one block corresponds to an updated version of the value in the previous block. The update is reflected in the hash of the block to which the value is assigned. The value of the block therefore provides an indication of what processing was performed in the block and also allows tracking to the original file through the blockchain. This tracking confirms the chain of custody of the archive throughout the blockchain.
[0117] For example, consider a situation where, in order to protect the identity of the person shown in the file, portions of a file in a previous block are redacted, masked, or pixelated. In this case, the block that includes the redacted file will include metadata associated with the redacted file, such as how the redaction was performed, who performed the redaction, a timestamp when the redaction(s) occurred, etc. The metadata can be hashed to form a value. Because the metadata of the block is different from the information that was hashed to form the value in the previous block, the values are different from each other and can be recovered upon decryption.
[0118] In one embodiment, when any one or more of the following occurs, the value of the previous block can be updated (e.g., a new hash value is calculated) to form the value of the current block. In this example embodiment, a new hash value can be calculated by hashing all or part of the information mentioned below.
[0119] a) A new SHA-2 computed hash value if the file has been manipulated in any way (e.g., if the file has been revised, copied, changed, accessed, or some other action has been taken)
[0120] b) New storage location for the file
[0121] c) Identify new metadata associated with the file
[0122] d) Transferring access to or control of a file from one blockchain participant to another
[0123] Fig.6D An embodiment of a block that can represent the structure of a block in blockchain 690 is shown, according to one embodiment. i Include header 672 i 、File 674i Total value 676 i .
[0124] Header 672 i Including the previous Block i-1 The hash value of the previous block and additional reference information, which can be any type of information discussed in this article (for example, header information including references, features, parameters, etc.). All blocks reference the hash of the previous block, of course, except for the origin block. The hash value of the previous block can be just the hash of the header in the previous block, or the hash of all or part of the information in the previous block (including files and metadata).
[0125] File 674 i In sequence, a plurality of data are included, for example, Data 1, Data 2, ..., Data N. The data are marked with metadata Metadata 1, Metadata 2, ..., Metadata N describing the content and / or characteristics associated with the data. For example, the metadata of each data may include information indicating a timestamp of the data, information used to process the data, keywords indicating a person or other content depicted in the data, and / or other characteristics that may be helpful in establishing the validity and content of the file as a whole, in particular its use for digital evidence, for example, as described in conjunction with the embodiments discussed below. In addition to the metadata, each data may be marked with a reference REF 1, REF 2, ..., REF N to previous data to prevent tampering, gaps in the file, and sequential references through the file.
[0126] Once metadata is assigned to data (e.g., by a smart contract), the metadata cannot be changed without the hash changing, which can be easily identified as invalid. Metadata thus creates a data log of the information that can be used by participants of the blockchain.
[0127] Value 676 i is a hash value or other value calculated based on any of the types of information discussed previously. For example, for any given block i , the value of the block can be updated to reflect the processing performed on the block, such as a new hash value, a new storage location, new metadata for the associated file, a transfer of control or access, an identifier, or other action or information to be added. Although the value in each block is shown as separate from the metadata of the data of the file and header, in another embodiment, the value can be based in part or in whole on the metadata.
[0128] Once the blockchain 670 is formed, at any point in time, the immutable chain of custody of the file can be obtained by querying the blockchain for the transaction history of values between blocks. The query or tracking process can start by decrypting the value of the current most contained block (e.g., the last (Nth) block), and then continue to decrypt the values of other blocks until the origin block is reached and the original file is restored. Decryption can also include decrypting the header and file and associated metadata for each block.
[0129] Decryption is performed based on the type of encryption that occurred in each block. This may involve the use of a private key, a public key, or a public-private key pair. For example, when asymmetric encryption is used, a blockchain participant or a processor in the network can generate a public and private key pair using a predetermined algorithm. The public and private keys are related to each other through some mathematical relationship. The public key can be distributed publicly to be used as an address to receive messages from other users, for example, an IP address or a home address. The private key is kept secret and is used to digitally sign messages sent to other blockchain participants. The signature is included in the message so that the recipient can verify it using the sender's public key. This way, the recipient can be sure that only the sender could have sent this message.
[0130] Generating a key pair may be similar to creating an account on the blockchain, but you don’t actually have to register it anywhere. In addition, every transaction performed on the blockchain is digitally signed by the sender using his private key. This signature ensures that only the owner of the account can track and process (if the processing is within the scope of permission determined by the smart contract) the files on the blockchain.
[0131] Fig. 7A and Figure 7B Additional examples of use cases for blockchain are shown, which may be incorporated and used herein. Specifically, Fig. 7A An example 700 of a blockchain 710 storing machine learning (artificial intelligence) data is shown. Machine learning relies on large amounts of historical data (or training data) to build predictive models in order to make accurate predictions about new data. Machine learning software (e.g., neural networks, etc.) can often sift through millions of records to discover non-intuitive patterns.
[0132] exist Fig. 7A In the example of , host platform 720 builds and deploys a machine learning model for predictive monitoring of asset 730. Here, host platform 720 may be a cloud platform, an industrial server, a network server, a personal computer, a user device, etc. Asset 730 may be any type of asset (e.g., a machine or equipment, etc.), such as an airplane, a locomotive, a turbine, medical machinery and equipment, oil and gas equipment, a ship, a vessel, a vehicle, etc. As another example, asset 730 may be a non-tangible asset such as a stock, a currency, a digital coin, an insurance, etc.
[0133] Blockchain 710 can be used to significantly improve the training process 702 of the machine learning model and the prediction process 704 based on the trained machine learning model. For example, in 702, historical data can be stored on blockchain 710 by the asset 730 itself (or through an intermediary, not shown), rather than requiring data scientists / engineers or other users to collect data. This can significantly reduce the collection time required by the host platform 720 when performing predictive model training. For example, using smart contracts, data can be directly and reliably transmitted directly from its source location to blockchain 710. By using blockchain 710 to ensure the security and ownership of the collected data, smart contracts can send data from assets directly to individuals who use the data to build machine learning models. This allows data to be shared between assets 730.
[0134] The collected data can be stored in the blockchain 710 based on a consensus mechanism. The consensus mechanism introduces (permission nodes) to ensure that the data being recorded is verified and accurate. The recorded data is time-stamped, cryptographically signed and immutable. Therefore, it is auditable, transparent and secure. In some cases, adding IoT devices that write directly to the blockchain (i.e., supply chain, healthcare, logistics, etc.) increases the frequency and accuracy of recorded data.
[0135] In addition, the training of the machine learning model based on the collected data can be performed by the host platform 720 for multiple rounds of refinement and testing. Each round can help expand the knowledge of the machine learning model based on additional data or data that has not been considered before. In 702, the different training and testing steps (and the data associated therewith) can be stored on the blockchain 710 by the host platform 720. Each refinement of the machine learning model (e.g., changes in variables, weights, etc.) can be stored on the blockchain 710. This provides verifiable evidence of how the model was trained and what data was used to train the model. In addition, when the host platform 720 has obtained the final trained model, the resulting model can be stored on the blockchain 710.
[0136] After the model has been trained, it can be deployed into a field environment where it can make predictions / decisions based on the execution of the final trained machine learning model. For example, in 704, the machine learning model can be used for condition-based maintenance (CBM) of assets such as aircraft, wind turbines, medical machines, etc. In this example, data fed back from the asset 730 can be input into the machine learning model and used to make event predictions, such as failure events, error codes, etc. The determination made by the execution of the machine learning model at the host platform 720 can be stored on the blockchain 710 to provide auditable / verifiable proof. As a non-limiting example, the machine learning model can predict a future crash / failure of a portion of the asset 730 and create an alert or notification to replace the portion. The data behind the decision can be stored on the blockchain 710 by the host platform 720. In one embodiment, the features and / or actions described and / or depicted herein can occur on or relative to the blockchain 710.
[0137] New transactions for a blockchain can be collected into a new block and added to an existing hash. This is then encrypted to create a new hash for the new block. When the transaction is encrypted, this is added to the next list of transactions, and so on. The result is a blockchain where each block contains the hashes of all the previous blocks. The computers storing these blocks periodically compare their hashes to make sure they all agree. Any computer that disagrees discards the record that caused the problem. This method is good for ensuring the blockchain is tamper-proof, but it is not perfect.
[0138] One way to cheat the system is for a dishonest user to change the list of transactions in their favor, but keep the hash the same. This can be done by brute force, in other words, by changing the record, encrypting the result, and seeing if the hash is the same. If the hash is not the same, it is tried again and again until a matching hash is found. The security of the blockchain is based on the belief that ordinary computers can only perform such brute force attacks on completely impractical timescales, such as the age of the universe. Quantum computers, by contrast, are much faster (1,000 times faster) and therefore pose a much greater threat.
[0139] Figure 7BAn example 750 of a quantum-safe blockchain 752 is shown that implements quantum key distribution (QKD) to prevent quantum computing attacks. In this example, blockchain users can verify each other's identities using QKD. This technology uses quantum particles (such as photons) to send information that an eavesdropper cannot copy without destroying these quantum particles. In this way, senders and receivers through the blockchain can determine each other's identities.
[0140] exist Figure 7B In the example of , there are four users 754, 756, 758, and 760. Each pair of users can share a secret key 762 (i.e., QKD) between them. Because there are four nodes in this example, there are six pairs of nodes, so six different secret keys 762 are used, including QKD AB , QKD AC , QKD AD , QKD BC , QKD BD and QKD CD Each pair can create QKD by sending information using quantum particles, such as photons, that an eavesdropper cannot copy without destroying them. In this way, a pair of users can determine each other's identity.
[0141] The operation of blockchain 752 is based on two processes: (i) creating transactions, and (ii) building blocks that aggregate new transactions. New transactions can be created similar to traditional blockchain networks. Each transaction can contain information about the sender, the receiver, the creation time, the amount (or value) to be transferred, a reference transaction list that proves that the sender has the operating funds, etc. The transaction record is then sent to all other nodes, where it is entered into a pool of unconfirmed transactions. Here, both parties (i.e., a pair of users among 754-760) authenticate the transaction by providing their shared secret key 762 (QKD). This quantum signature can be attached to each transaction, making it very difficult to tamper with. Each node checks their entries against the local copy of blockchain 752 to verify that each transaction has sufficient funds. However, the transaction has not yet been confirmed.
[0142] Blocks can be created in a decentralized manner using a broadcast protocol. The network can apply the broadcast protocol to any unconfirmed transactions in a predetermined time period (e.g., seconds, minutes, hours, etc.) to obtain a Byzantine agreement (consensus) on the correct version of the transaction. For example, each node can have a private value (transaction data for that particular node). In the first round, nodes pass their private values to each other. In subsequent rounds, nodes pass the information they received from other nodes in the previous round. Here, honest nodes are able to create a complete set of transactions in a new block. This new module can be added to blockchain 752. In one embodiment, the features and / or actions described and / or depicted herein may occur on blockchain 752 or relative to blockchain 710.
[0143] Figure 8 An example system 800 is shown that supports one or more example embodiments described and / or depicted herein. The system 800 includes a computer system / server 802 that can operate with many other general or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations suitable for use with the computer system / server 802 include, but are not limited to, personal computer systems, server computer systems, thin clients, fat clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, minicomputer systems, mainframe computer systems, and distributed cloud computing environments including any of the above systems or devices, etc.
[0144] Computer system / server 802 may be described in the general context of computer system executable instructions (such as program modules) executed by a computer system. In general, program modules may include routines, programs, objects, components, logic, data structures, etc., which perform specific tasks or implement specific abstract data types. Computer system / server 802 may be practiced in a distributed cloud computing environment where tasks are performed by remote processing devices linked through a communication network. In a distributed cloud computing environment, program modules may be located in local and remote computer system storage media including memory storage devices.
[0145] like Figure 8 As shown, the computer system / server 802 in the cloud computing node 800 is in the form of a general-purpose computing device. The components of the computer system / server 802 may include, but are not limited to: one or more processors or processing units 804, a system memory 806, and a bus connecting different system components (including the system memory 806 and the processing unit 804).
[0146] The term "bus" refers to one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus that uses any of a variety of bus structures. For example, these architectures include, but are not limited to, the Industry Standard Architecture (ISA) bus, the Micro Channel Architecture (MAC) bus, the Enhanced ISA bus, the Video Electronics Standards Association (VESA) local bus, and the Peripheral Component Interconnect (PCI) bus.
[0147] In one embodiment, the system memory 806 implements the flowcharts in other figures. The system memory 806 may include a computer system readable medium in the form of a volatile memory, such as a random access memory (RAM) 810 and / or a cache memory 812. The computer system / server 802 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, the storage system 814 may be used to read and write non-removable, non-volatile magnetic media (not shown in the figure, commonly referred to as a "hard drive"). Although not shown in the figure, a disk drive for reading and writing a removable non-volatile disk (such as a "floppy disk"), and an optical disk drive for reading and writing a removable non-volatile optical disk (such as a CD-ROM, DVD-ROM or other optical media) may be provided. In these cases, each drive may be connected to the bus via one or more data medium interfaces. The memory 806 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present application.
[0148] A program / utility 816 having a set (at least one) of program modules 818 may be stored, for example, in the memory 806, such program modules 818 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment. The program modules 818 generally perform the functions and / or methods of the embodiments described herein.
[0149] The computer system / server 802 may also communicate with one or more external devices 820 (e.g., keyboards, pointing devices, displays 822, etc.), may communicate with one or more devices that enable a user to interact with the computer system / server 802, and / or may communicate with any device that enables the computer system / server 802 to communicate with one or more other computing devices (e.g., network cards, modems, etc.). Such communication may be performed via an I / O interface 824. In addition, the computer system / server 802 may also communicate with one or more networks (e.g., local area networks (LANs), wide area networks (WANs), and / or public networks, such as the Internet) via a network adapter 826. As shown, the network adapter 826 communicates with other modules of the computer system / server 802 via a bus. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the computer system / server 802, including, but not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.
[0150] Although the exemplary embodiments of at least one of the system, method and non-transitory computer-readable medium have been shown in the drawings and described in the above detailed description, it should be understood that the present application is not limited to the disclosed embodiments, but can be rearranged, modified and replaced as described and defined in the attached claims. For example, the ability of the system of various drawings can be performed by one or more of the modules or components described herein, or performed with a distributed architecture, and can include a transmitter, a receiver, or a transmitter and a receiver pair. For example, all or part of the functions performed by a separate module can be performed by one or more of these modules. In addition, the functions described here can be performed at different times inside or outside a module or component and in relation to different events. In addition, the information sent between various modules can be sent between modules via at least one of the following: data network, Internet, voice network, Internet protocol network, wireless device, wired device and / or multiple protocols. In addition, the message sent or received by any module can be sent or received directly and / or via one or more other modules.
[0151] Those skilled in the art will appreciate that a "system" may be implemented as a personal computer, server, console, personal digital assistant (PDA), cellular phone, tablet computing device, smart phone, or any other suitable computing device, or a combination of devices. Presenting the above functions as being performed by a "system" is not intended to limit the scope of the present application in any way, but is intended to provide an example of many embodiments. In practice, the methods, systems, and apparatus disclosed herein may be implemented in localized and distributed forms consistent with computing technology.
[0152] It should be noted that some of the system features described in this specification have been presented as modules in order to more specifically emphasize their implementation independence. For example, modules can be implemented as hardware circuits, including custom very large-scale integrated circuits (VLSI) or gate arrays, off-the-shelf semiconductors (such as logic chips, transistors, or other discrete components). Modules can also be implemented in programmable hardware devices (such as field programmable gate arrays, programmable array logic, programmable logic devices, graphics processing units, etc.).
[0153] Modules may also be implemented at least in part in software so as to be executed by various types of processors. The identified unit of executable code may, for example, include one or more physical or logical blocks of computer instructions, which may, for example, be organized as objects, processes, or functions. However, the executable program of the identified module need not be physically located together, but may include different instructions stored in different locations, which, when logically combined together, constitute the module and achieve the purpose of the module. In addition, the module may be stored on a computer-readable medium, which may be, for example, a hard drive, a flash memory device, a random access memory (RAM), a magnetic tape, or any other such medium for storing data.
[0154] In practice, an executable code module may be a single instruction or multiple instructions, and may even be distributed across several different code segments, across different programs, and across several storage devices. Similarly, operational data may be identified and illustrated in a module here, and may be embodied in any suitable form, and organized in any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed across different locations (including across different storage devices), and may exist at least in part only as electronic signals on a system or network.
[0155] It is easy to understand that the components of the present application can be arranged and designed in a variety of different configurations, as generally described and shown in the figures herein. Therefore, the detailed description of the embodiments is not intended to limit the scope of the claimed application, but is merely representative of selected application embodiments.
[0156] Those skilled in the art will readily appreciate that the above may be implemented with steps in a different order and / or with hardware elements in a configuration different from that disclosed. Therefore, although the application has been described based on these preferred embodiments, certain modifications, variations, and alternative structures will be apparent to those skilled in the art.
[0157] Although preferred embodiments of the present application have been described, it should be understood that the described embodiments are merely illustrative and that the scope of the present application is limited solely by the appended claims when considering the full range of equivalents and modifications thereto (e.g., protocols, hardware devices, software platforms, etc.).
Claims
1. A method for providing a Blu-ray copy service, comprising: receiving a copy request from a user node of the blockchain network, the copy request including a copy token; Based on detecting that the user node attempts to spend the copied token, verifying the copied token by requiring the copied token to be signed by a private key of the user node; In response to the verification, generating a media copy key for generating a Blu-ray copy; as well as The copied token is recorded on a ledger of the blockchain network to indicate that the copied token is spent.
2. The method of claim 1 further comprising outputting format metadata to generate a format-specific Blu-ray copy.
3. The method of claim 1, further comprising encrypting the media copy key using a public key of a format-specific copier associated with the user node.
4. The method of claim 1 further comprises verifying that the copied token belongs to the user node.
5. The method of claim 1 , further comprising recording a transaction on a ledger of the blockchain network to indicate that a Blu-ray copy associated with the copy request was made.
6. A system for Blu-ray copy service, comprising: processor; A memory having machine-readable instructions stored thereon, which, when executed by a processor, causes the processor to perform the method according to any one of claims 1 to 5.
7. A non-transitory computer-readable medium comprising instructions, which, when read by a processor, causes the processor to execute the method according to any one of claims 1 to 5.
8. A system related to a Blu-ray copy service, the system comprising modules respectively used to execute each step of the method according to any one of claims 1 to 5.
