CN111191271B - Computer-implemented method, system and storage medium - Google Patents
Computer-implemented method, system and storage medium Download PDFInfo
- Publication number
- CN111191271B CN111191271B CN201911075193.6A CN201911075193A CN111191271B CN 111191271 B CN111191271 B CN 111191271B CN 201911075193 A CN201911075193 A CN 201911075193A CN 111191271 B CN111191271 B CN 111191271B
- Authority
- CN
- China
- Prior art keywords
- digital asset
- digital
- processors
- request
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
- G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/50—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols using hash chains, e.g. blockchains or hash trees
Abstract
Software for preventing fraud in digital content licensing and distribution using distributed ledger technology. The software performs the following operations: (i) Receiving a request for a license for the digital asset, wherein a record of the digital asset is stored in a first distributed ledger; (ii) verifying a consensus of the request for permission for the digital asset; and (iii) a consensus in response to a request to verify a license to the digital asset: the transaction settlement record is stored in a second distributed ledger, a sliced copy of the digital asset is created that includes a plurality of sliced digital assets, and at least one slice of the sliced copy of the digital asset is stored in the second distributed ledger by a slicing instruction for reconstructing the digital asset from the sliced copy.
Description
Technical Field
The present invention relates generally to the field of blockchain systems, and more particularly to blockchain systems for digital licensing and the effectuation of content distribution.
Background
Blockchains refer to distributed, licensed and immutable ledgers (ledgers) that are capable of recording transactions (transactions). Blockchains are a decentralization technique that involves a peer-to-peer (P2P) network that includes computers called nodes. The blockchain further includes a method for node validation transactions. Once a transaction is validated by a node, a new block will be added to the existing blockchain that contains information that validates the transaction.
Disclosure of Invention
According to an aspect of the present invention, there is a method, computer program product, and/or computer system that performs the following operations (not necessarily in the order below): (i) Receiving a request for a license for a digital asset, wherein a record of the digital asset is stored in a first distributed ledger; (ii) Verifying a consensus (consensus) of requests for permissions for the digital asset; and (iii) a consensus in response to a request to verify a license to the digital asset: the transaction settlement record is stored in a second distributed ledger, a sliced copy of the digital asset is created that includes a plurality of slices of the digital asset, and at least one slice of the sliced copy of the digital asset is stored in the second distributed ledger with slicing instructions for reconstructing the digital asset from the sliced copy.
Drawings
To facilitate identification of a discussion of any particular element or act, the most significant digit(s) in a reference number refers to the figure number in which that element was first introduced.
FIG. 1 is a block diagram depicting a networked computer system 100 according to an embodiment of the invention.
FIG. 2 shows a flowchart 200 depicting a method of providing permissions for digital assets stored in a blockchain ledger in accordance with an embodiment of the invention.
FIG. 3 shows a flowchart 300 depicting a method of rebuilding a sliced digital asset stored in a blockchain ledger in accordance with an embodiment of the invention.
Fig. 4 is a block diagram depicting a procedure 400 according to an embodiment of the invention.
Fig. 5 shows a flowchart 500 depicting a method of capturing digital content and pushing it to a blockchain service in accordance with an embodiment of the invention.
FIG. 6 shows a flowchart 600 depicting a method of storing digital assets in a blockchain ledger in accordance with an embodiment of the invention.
Detailed Description
Digital rights management (Digital rights management, DRM) is a technology useful for restricting the use of copyrighted material, such as audiovisual material. Typically, the DRM software will provide access control for the use, modification, and/or distribution of the managed material. However, DRM generally operates in a centralized manner and makes it difficult to monitor the actual use of materials. To address this shortcoming, as well as others, a blockchain digital licensing system is disclosed.
The present invention may be a system, method, and/or computer program product. The computer program product may include a computer readable storage medium having computer readable program instructions embodied thereon for causing a processor to implement aspects of the present invention.
The computer readable storage medium may be a tangible device that can hold and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium would include the following: portable computer disks, hard disks, random Access Memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static Random Access Memory (SRAM), portable compact disk read-only memory (CD-ROM), digital Versatile Disks (DVD), memory sticks, floppy disks, mechanical coding devices, punch cards or in-groove structures such as punch cards or grooves having instructions stored thereon, and any suitable combination of the foregoing. Computer-readable storage media, as used herein, are not to be construed as transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (e.g., optical pulses through fiber optic cables), or electrical signals transmitted through wires.
The computer readable program instructions described herein may be downloaded from a computer readable storage medium to a respective computing/processing device or to an external computer or external storage device over a network, such as the internet, a local area network, a wide area network, and/or a wireless network. The network may include copper transmission cables, fiber optic transmissions, wireless transmissions, routers, firewalls, switches, gateway computers and/or edge servers. The network interface card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium in the respective computing/processing device.
Computer program instructions for carrying out operations of the present invention may be assembly instructions, instruction Set Architecture (ISA) instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source or object code written in any combination of one or more programming languages, including an object oriented programming language such as Smalltalk, c++ or the like and a procedural programming language such as the "C" language or similar programming languages. The computer readable program instructions may be executed entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider). In some embodiments, aspects of the present invention are implemented by personalizing electronic circuitry, such as programmable logic circuitry, field Programmable Gate Arrays (FPGAs), or Programmable Logic Arrays (PLAs), with state information for computer readable program instructions, which can execute the computer readable program instructions.
Various aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer-readable program instructions.
These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable medium having the instructions stored therein includes an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer, other programmable apparatus or other devices implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
Embodiments of possible hardware and software environments of software and/or methods according to the present invention will now be described in detail with reference to the accompanying drawings. FIG. 1 is a functional block diagram illustrating portions of a networked computer system 100, including: a server subsystem 102; client subsystem 104; a client subsystem 106; customer premises subsystem 108, customer premises subsystem 110, customer premises subsystem 112; a communication network 114; a server computer 116; a communication unit 118; a processor group 120; an input/output (I/O) interface group 122; a memory device 124; persistent storage 126; a display device 132; an external device group 134; a Random Access Memory (RAM) device 128; a cache memory device 130; and procedure 400.
Subsystem 102 represents in many respects the various computer subsystem(s) of the present invention. Accordingly, several portions of subsystem 102 will now be discussed in the following paragraphs.
Subsystem 102 may be a laptop computer, tablet computer, netbook computer, personal Computer (PC), desktop computer, personal Digital Assistant (PDA), smart phone, or any programmable electronic device capable of communicating with the client subsystem via network 114. Program 400 is a collection of machine-readable instructions and/or data for creating, managing, and controlling certain software functions, as will be discussed in detail below.
Subsystem 102 is capable of communicating with other computer subsystems via network 114. The network 114 may be, for example, a Local Area Network (LAN), a Wide Area Network (WAN) such as the internet, or a combination of both, and may include wired, wireless, or fiber optic connections. In general, network 114 may be any combination of connections and protocols that support communication between server and client subsystems.
Subsystem 102 is shown as a block diagram with a number of double-headed arrows. These double arrows (without separate reference numerals) represent communication structures that provide communication between the various components of subsystem 102. The communication structure may be implemented with any architecture designed to communicate data and/or control information between processors (such as microprocessors, communication and network processors, etc.), system memory, peripheral devices, and any other hardware components within the system. For example, the communication structure may be implemented at least in part with one or more buses.
Memory device 124 and persistent storage device 126 are computer-readable storage media. In general, memory device 124 may include any suitable volatile or non-volatile computer-readable storage media. It should further be noted that now and/or in the near future: (i) External device group 134 may be capable of providing some or all of the memory for subsystem 102; and/or (ii) devices external to subsystem 102 may be capable of providing memory for subsystem 102.
The media used by persistent storage 126 also may be removable. For example, a removable hard drive may be used for persistent storage 126. Other examples include optical and magnetic disks, thumb drives, and smart cards, which are inserted into drives for transfer onto another computer-readable storage medium that is also part of persistent storage 126.
In these examples, communication unit 118 provides communication with other data processing systems or devices external to subsystem 102. In these examples, communication unit 118 includes one or more network interface cards. The communication unit 118 may provide communication through the use of one or both of physical and wireless communication links. Any of the software modules discussed herein may be downloaded to a persistent storage device (such as persistent storage device 126) via a communication unit (such as communication unit 118).
The set of I/O interfaces 122 allows for the input and output of data with other devices that may be connected locally in data communication with the server computer 116. For example, the I/O interface group 122 provides connectivity to the external device group 134. The external device group 134 will typically include devices such as a keyboard, keypad, touch screen, and/or some other suitable input device. External device group 134 may also include portable computer-readable storage media such as thumb drives, portable optical or magnetic disks, and memory cards. Software and data for practicing embodiments of the invention, such as program 400, may be stored on such portable computer-readable storage media. In these embodiments, the relevant software may (or may not) be loaded in whole or in part onto persistent storage 126 via I/O interface group 122. The set of I/O interfaces 122 is also connected in data communication with a display device 132.
The display device 132 provides a mechanism for displaying data to a user and may be, for example, a computer monitor or a smart phone display screen.
The programs described herein are identified based upon the application for which they are implemented in a specific embodiment of the invention. However, it should be appreciated that any particular program nomenclature that follows is used merely for convenience, and thus the invention should not be limited to use solely in any specific application identified and/or implied by such nomenclature.
The foregoing description of embodiments of the invention has been presented for purposes of illustration and description, and is not intended to be exhaustive or limited to the embodiments disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the various embodiments described. The terminology used herein was chosen in order to best explain the principles of the embodiments, the practical application, or the technical improvement of the technology in the marketplace, or to enable others of ordinary skill in the art to understand the embodiments disclosed herein.
Fig. 2 shows a flow chart 200 depicting a method according to the present invention. Fig. 3 shows a flow chart 300 depicting a method according to the present invention. Fig. 4 shows a program 400 for performing at least some of the method operations of flowcharts 200 and 300. The methods of flow diagrams 200 and 300 and the associated software of program 400 will now be discussed in the following paragraphs with reference to fig. 2 and 3 (for the method operational blocks) and fig. 4 (for the software module ("mod") block).
Referring to flowchart 200 (see FIG. 2), the process begins at operation 202 where blockchain module 402 (see FIG. 4) receives a request for a license for a digital asset. In some embodiments of the invention, a record of the digital asset may be stored in a first distributed ledger. In some embodiments, the first distributed ledger is a blockchain. In some embodiments, the first licensed blockchain network includes an owner of the digital asset and the second licensed blockchain network includes a potential licensee (prospective licensee) of the digital asset. In some embodiments, the second licensed blockchain network initiates a request for a license for the digital asset. In some embodiments, the request for permission for the digital asset may include a consensus method (e.g., if the request is received from a licensed blockchain network having a plurality of members).
In an exemplary embodiment, sarah and Ben are legal owners of photographs (i.e., digital assets). Sarah and Ben form a licensed blockchain network A. Sarah and Ben initiate a vote (or alternative consensus method) as a member of the licensed blockchain network to store the photograph in the first distributed ledger for the purpose of providing licensing for the photograph. In response to validating that the consensus of the photograph for the license is provided in licensed blockchain network a, blockchain module 402 stores the photograph in the first distributed ledger. In response to the photo being added to the first distributed ledger, a watermarked (watermark) version of the photo is included in the public digital asset directory. Some of these aspects of the invention are discussed in more detail below with reference to fig. 5 and 6.
Bob and Lisa, members of the licensed blockchain network B, after having reviewed the public directory and found the watermarked version of their favorite photo, initiate a vote (or alternative consensus method) to request the license for the photo. In response to validating the consensus in licensed blockchain network B that requests permission for photos, intelligent contract agreement module 404 can initiate a request for permission for photos.
Processing continues at operation 204 where intelligent contract agreement module 404 (see FIG. 3) verifies the consensus of the request for permission to grant the digital asset. In some embodiments of the invention, the consensus method may include an endorsement policy to specify which particular members of the licensed blockchain network must endorse a certain transaction class. The consensus method may include determining that an endorsement policy is to be enforced, for example, by verifying that there is sufficient endorsement and/or verifying that the endorsement originated from an appropriate member of the licensed blockchain network. In some embodiments, the member of the first blockchain network, including the owner of the digital asset, is an appropriate member of the licensed blockchain network to grant the request for the license for the digital asset.
In an exemplary embodiment, members Sarah and Ben of network A initiate a request to vote (or alternative consensus method) to grant permission to the photograph. The intelligent contract agreement module 404 may verify the transaction by determining that Sarah and Ben are actually members of the licensed blockchain network A that are required to approve the request for photograph license. The intelligent contract agreement module 404 may further use one or more other known consensus methods to validate the transaction.
Processing proceeds to operation 206 where intelligent contract agreement module 404 (see fig. 4) stores the transaction settlement record in a second distributed ledger. In some embodiments of the invention, the second distributed ledger is also a blockchain. In some embodiments, a second distributed ledger is created to store transaction settlement records between the first licensed blockchain network and the second licensed blockchain network. In some embodiments, the second distributed ledger is shared between the first licensed blockchain network and the second licensed blockchain network. In some embodiments, the second distributed ledger is also used to distribute licensed digital assets and/or to enforce the use of licensed digital assets.
In an exemplary embodiment, the intelligent contract agreement module 404 creates a second distributed ledger and stores the licensed transaction settlement records of the photographs in the second distributed ledger. The transaction settlement record contains a transaction summary that facilitates creation of a second distributed ledger.
Processing continues at operation 208 where intelligent contract agreement module 404 (see FIG. 4) creates a fragmented copy of the plurality of fragmented digital assets that include the digital asset. In some embodiments of the invention, the intelligent contract agreement module 404 uses a sharding algorithm (e.g., transaction sharding, network sharding, and/or status sharding) to uniquely shard (tile) and decompose the digital asset. In some embodiments, the slicing algorithm is selected for efficient distribution of digital assets and enforcement of permissions for digital assets. In a method of using network sharding, a digital asset is sharded into a plurality of shards corresponding to a plurality of nodes of a second distributed ledger. For example, each of the plurality of tiles may be stored in a different node of the plurality of nodes (i.e., one tile per node in a one-to-one allocation). In this approach, rebuilding the digital asset may require access to multiple nodes, where each node independently enforces the license for the digital asset (e.g., by implementing a consensus method for efficient use of the digital asset under the granted license). These aspects of the present invention represent an improvement over the prior art by allowing license enforcement and content distribution in a decentralized manner.
In an exemplary embodiment, the intelligent contract agreement module 404 creates a fragmented copy of the photograph. The intelligent contract agreement module 404 further implements a network fragmentation algorithm using the first node of the second distributed ledger and the second node of the second distributed ledger. In this example, a first node is associated with licensed blockchain network a and a second node is associated with licensed blockchain network B.
Processing proceeds to operation 210 where intelligent contract agreement module 404 (see fig. 3) stores the fragmented copies of the digital asset in a second distributed ledger by way of instructions for reconstructing the digital asset from the fragmented copies. In some embodiments of the invention, the sharding algorithm determines which shards are to be stored in a first node of the second distributed ledger and which shards are to be stored in a second node of the second distributed ledger. In some embodiments, a first node is associated with licensed blockchain network a and a second node is associated with licensed blockchain network B. In some embodiments, the instructions for reconstructing the digital asset from the sliced copy comprise computer instructions for reorganizing and distributing the digital asset. In some embodiments, the additional nodes may be used to store shards of the sharded copy of the digital asset. In these and other embodiments, the node may verify and enforce access to licensed digital assets.
In an exemplary embodiment, intelligent contract agreement module 404, along with computer instructions to reorganize the digital asset from the first node and the second node, stores a first shard of the sharded copy of the photograph in the first node and a second shard of the sharded copy of the photograph in the second node.
Referring now to flowchart 300 (see FIG. 3), processing begins at operation 302 where intelligent contract agreement module 404 (see FIG. 4) receives a request for access to a licensed digital asset. In some embodiments of the invention, a request for a licensed digital asset is received in response to a user requesting access to the licensed digital asset. In some embodiments, the intelligent contract agreement module 404 may include a consensus method that enforces the use of digital assets. In some embodiments, the consensus method includes validating the transaction to ensure that the intended use is supported by the license for the digital asset. In some embodiments, a consensus method of enforcing use of a digital asset may include (e.g., in a network sharding method) each of a plurality of nodes independently enforcing a license for the digital asset.
In an exemplary embodiment, bob and Lisa use photos of permissions in the website. When a user opens a website, a request for licensed digital assets is automatically generated. Upon receiving the request, the intelligent contract agreement module 404 verifies that the request is a valid use of the photograph, for example, by verifying that the request is from an authorized user.
Processing continues at operation 304 where intelligent contract agreement module 404 (see FIG. 4) executes stored instructions for reconstructing the digital asset from the sliced copy of the digital asset stored in the second distributed ledger and transmits the reconstructed digital asset for digital use. In some embodiments, reconstructing the digital asset may include reconstructing the digital asset (e.g., in a network sharding method) from a plurality of shards stored in a plurality of nodes of the second distributed ledger. For example, each of the plurality of shards may be retrieved from a different node of the plurality of nodes (i.e., one shard per node in a one-to-one allocation).
In an exemplary embodiment, the intelligent contract agreement module 404 reorganizes the digital assets from the first and second distributed ledgers by retrieving a first shard of the sharded copy of the photograph from the first distributed ledger and retrieving a second shard of the sharded copy of the photograph from the second distributed ledger. The intelligent contract agreement module 404 reorganizes licensed digital assets for use in the website as authorized by license terms obtained by Bob and Lisa, and sends reconstructed photos for use in the website.
In some embodiments of the present invention, a workflow is provided for storing the digital content itself (e.g., in a watermarked format) on a licensed blockchain ledger. Fig. 5 and 6 show a flow chart 500 and a flow chart 600, respectively, depicting a method according to one of these embodiments.
Referring first to flowchart 500 (see fig. 5), in operation 502 a content author registers a content creation device (e.g., a smart phone or an internet-enabled camera, such as client subsystem 104, for example) with a blockchain service. For example, the author uses the device to establish an ownership identity that includes the author's authentication details (e.g., fingerprint) and the device's authentication details (e.g., serial number), and then the device provides the ownership identity to the blockchain service (e.g., via blockchain module 402). At operation 504, the author uses the device to capture digital content (e.g., photographs, drawings, recordings, etc.) on the device. Then, at operation 506, the device automatically pushes the digital content to the blockchain service by sending the digital content to the blockchain module 402 in response to the author capturing the digital content. In this embodiment, when pushing digital content to the blockchain service, the device also sends identifying details of the author, identifying details of the device, metadata of the digital content (e.g., time, location, device manufacturer, device model, etc.), and a digital hash (hash) of the digital content to the blockchain module 402.
Referring now to flowchart 600 (see FIG. 6), in operation 602 blockchain module 402 receives from a device of an author identification details of the author, identification details of the device of the author, metadata of the digital content, a digital hash of the digital content, and the digital content. Processing proceeds to operation 604 where the blockchain module 402 then uses the identifying details of the author and the authenticating details of the author's device to verify the authenticity of the author and the author's device in operation 604. For example, in some embodiments, the blockchain module 402 compares the identifying details of the author and the identifying details of the author's device to the blockchain service stored registration information (e.g., registration from operation 502 discussed above).
The process then proceeds to operation 606, where, based on the approval of the authenticity, the smart contract agreement module 404 creates a record of the originality of the digital content and the unique watermark on the digital content using the received metadata (record of originality). In some embodiments, the watermark is created based on the identity information (identification information) of the owner, metadata of the digital asset, and the digital hash. Many known (or to be known) watermarking techniques may be used, including techniques for watermarking that are visible to a human user, as well as techniques for digital watermarking that are only detectable by a computer. Similarly, many known (or to be known) techniques for providing digital records of originality and/or authenticity may be used; in fact, in some cases, the watermark itself is used as the original record.
Processing then proceeds to operation 608 where blockchain module 402 stores the watermarked digital content and the record of originality in the licensed blockchain ledger in operation 608. Many known (or to be known) methods for storing items in blockchain ledgers may be used, including those discussed elsewhere in this detailed description with respect to other embodiments. Furthermore, in some embodiments, the watermarked digital content is stored in a blockchain ledger along with the original digital content, either in the same node, or in a neighboring node. In yet other embodiments, the watermarked digital content is stored on a node in a first distributed ledger having a link to a node in a second distributed ledger in which the original digital content is stored, wherein the link is stored in the same node or in a node adjacent to the watermarked digital content.
In some embodiments of the invention, the blockchain service includes intelligent contractual agreements and blockchain architectures to allow cross-network licensing of digital content and to preserve links between networks. In some embodiments, the blockchain service provides the advantage of properly licensing content between multiple licensed blockchain networks through intelligent contractual agreements. In some embodiments, the intelligent contract agreement allows permissions to be granted to digital content while preserving the originality of the digital content across multiple licensed blockchain networks.
In some embodiments of the present invention, there is a centralized or decentralized transaction (exchange) for licensed blockchain networks to grant a watermark protected view of digital content to licensed users. In some embodiments, the digital content is archived and cataloged (cataloged) for licensing. In some embodiments, users may submit requests for permissions for digital content for their use or on behalf of another blockchain network.
In some embodiments of the invention, the intelligent contract agreement processes the digital signature of the original author and receives the fingerprint signature of the licensed user in preparation for recording the links in the intermediate sub-ledgers. In some embodiments, the intermediate sub-ledgers are blockchain ledgers. In some embodiments, a network voting protocol may be used to receive fingerprint signatures of multi-member licensed blockchain networks.
In an exemplary embodiment of the present invention, two licensed blockchain networks (e.g., network a and network B) are interested in digital content. In this exemplary embodiment, network a is the owner of the original digital content and network B seeks to license the original digital content for its use. In this exemplary embodiment, network a and network B have unique administrators (and members) with their own intelligent contracts and voting consensus.
In this exemplary embodiment, the primary ledger of network a contains digital content that includes a watermarked version of the digital content and a record of the originality of the digital content. Network a may also place the watermarked image in a digital content catalog as a representation of the digital content and issue the digital content catalog for licensing. Network B may issue a request for a license to the digital content to a member of network B. Once the request for permission from network B is granted, network a creates a sub-ledger that is shared by both networks, where the sub-ledger tracks the beginning of transaction history between the two licensed blockchain networks. Network a collects metadata signatures, member data and agreements from network B and stores them in sub-ledgers. The blocks in the shared sub-ledger contain links between transaction settlement records in the two networks. A smart contract agreement set (central) votes between licensed blockchain networks for consensus among all members and signing of responsibility and use of digital content.
In this exemplary embodiment, once consensus is reached, the intelligent peer uniquely slices and breaks down the digital content using a slicing algorithm before distributing the digital content to network B. The smart contract may then store the fragmented digital content in a block of shared sub-ledgers to provide access to network B. At settlement, the respective primary ledgers of network a and network B may include transactions with encrypted links to shared sub-ledgers. Network B does not directly receive access to the original digital content, but may access only the fragmented digital content stored in the sub ledger. The shared sub-ledger may also include a slicing algorithm (e.g., as part of a smart contract agreement) used by network B to reorganize and consume digital content (e.g., display pictures on web pages or play audio in an audio player). The master ledger of network a may also include a history of permitted transactions by storing metadata of consumers and signatures of members of network B.
Network a, as a representation of the digital content owner, may be exclusively responsible for writing into the sub ledger. Network a may also reserve the shared sub-ledgers as all of the administrative capabilities of the initiator and manager of the transaction. Network a may reserve the right to revoke the slicing algorithm that assembles the digital content. Thus, network B may be a read-only user sharing a sub-ledger.
The master ledger of network a may include an encrypted original copy of the digital content. For example, a member is allowed to access a private directory of digital content, but cannot copy or move the digital content without performing a smart contract. In other words, the signing license agreement provides access to the decryption key that created the private sub-ledger. This provides the licensed user with a new sliced watermarked copy of the original digital content, including a record of the fingerprint and originality of the digital content. The slicing algorithm may reorganize the digital content based on authorized use in the licensing agreement.
Once the encrypted version of the original image is entered into the block on the primary ledger, the smart contract effectively obfuscates the image into slices by using a random algorithm in the smart contract agreement, dividing the image into many encrypted slices (i.e., slices) on the shared sub-ledger block between the original author and the licensed user. The creation of a shared sub-ledger may be shown as a transaction on the primary ledger of the original author. The shared sub-ledger becomes a peer-to-peer (P2P) transaction between the original author and the network member, where the transfer of funds results in the generation of code and encrypted slices (i.e., fragmented digital content) to securely embed the image onto their website under a copyright licensing agreement. The slicing of the original digital content may be part of a smart contract agreement that is implemented using the private key of the original author, agreement-based, decrypting (i.e., reorganizing) the original digital content, obfuscating for the smart contract for licensing. In some embodiments, the blockchain service may also utilize existing digital media Digital Rights Management (DRM) techniques.
Once the transaction is completed, the agreement is stored with the randomized slice and its assembly algorithm and key signature on the network a main ledger and shared sub-ledger that maintain links to the original work owner main ledger node. Network B (licensed user) may have a read-only link to a shared sub-ledger containing a confusing version of digital content, an assembly algorithm, and embedded code that the licensed user may execute to display or otherwise access licensed digital content. This makes the transaction completely private to the public world, while also giving full control and ownership exclusively to network a. Thus, network a may remove the shared sub-ledger node from the network (e.g., if fraud, unauthorized use, or violation of a contract is determined).
Definition of the definition
The invention comprises the following steps: it is not to be taken as an absolute indication of the coverage of the claims that the subject matter described by the term "invention" is filed or that the claims that may ultimately issue after prosecution; while the term "present invention" is used to assist the reader in obtaining a general sense, the disclosure herein is considered to be a potential novelty, such understanding is transient and may vary during the course of a patent application as the term "present invention" is used and as related information evolves and the claims become potentially amended.
Examples: see definition of "invention" above-similar warnings apply to the term "embodiment"
And/or: includes or is; for example, "a, b" and/or "c" means that at least one of a, b or c is true and applicable.
Include (include)/include (include): unless expressly stated otherwise, it is meant to be "including but not necessarily limited to".
Module/submodule: any set of hardware, firmware, and/or software for performing a function, regardless of whether the module: (i) in the vicinity of a single local site; (ii) distributed over a broad area; (iii) A single adjacency within a larger piece of software code; (iv) within a single piece of software code; (v) located in a single storage device, memory, or medium; (vi) mechanical connection; (vii) an electrical connection; and/or (viii) connected in data communication.
And (3) a computer: any device having significant data processing and/or machine readable instruction reading capabilities, including, but not limited to: desktop computers, mainframe computers, laptop computers, field Programmable Gate Array (FPGA) based devices, smart phones, personal Digital Assistants (PDAs), vehicle-mounted or plug-in computers, embedded device type computers, application Specific Integrated Circuit (ASIC) based devices.
Claims (20)
1. A computer-implemented method, comprising:
receiving, by one or more processors, a request for a license for a digital asset, wherein a record of the digital asset is stored in a first distributed ledger;
verifying, by one or more processors, a consensus of a request for a license for the digital asset; and
a consensus in response to a request to verify a license to the digital asset:
(i) The transaction settlement records are stored by the one or more processors in a second distributed ledger,
(ii) Creating, by one or more processors, a sliced copy of the digital asset including a plurality of slices of the digital asset, and
(iii) At least one shard of the shard copy of the digital asset is stored in a second distributed ledger by one or more processors with shard instructions for reconstructing the digital asset from the shard copy.
2. The method of claim 1, further comprising:
receiving, by one or more processors, a request to reconstruct the digital asset from a sliced copy of the digital asset;
verifying, by one or more processors, a consensus of a request to reconstruct the digital asset; and
responsive to verifying a consensus of a request to reconstruct the digital asset, reconstructing, by one or more processors, the digital asset from a sliced copy of the digital asset according to the slicing instructions.
3. The method of claim 2, wherein the request to reconstruct the digital asset from the fragmented copy of the digital asset is received in response to selecting the watermarked copy of the digital asset in a public digital asset directory.
4. The method of claim 1, wherein storing at least one shard of the shard copy of the digital asset in a second distributed ledger by shard instructions for reconstructing the digital asset from the shard copy further comprises:
storing, by the one or more processors, a first shard of the plurality of shards of the digital asset in a first node of a second distributed ledger; and
a second one of the plurality of slices of the digital asset is stored in a second node of a second distributed ledger by one or more processors.
5. The method of claim 4, further comprising:
receiving, by one or more processors, a request to reconstruct the digital asset from a sliced copy of the digital asset;
verifying, by one or more processors, a consensus of a request to reconstruct the digital asset from a fragmented copy of the digital asset; and
in response to verifying a consensus of a request for the rebuilt digital asset:
(i) A first one of a plurality of slices of the digital asset is received by one or more processors from a first node,
(ii) Receiving, by the one or more processors, a second shard of the plurality of shards of the digital asset from a second node, and
(iii) Reconstructing the digital asset from the first and second slices according to the slice instruction.
6. The method of claim 5, wherein verifying a consensus of a request to reconstruct the digital asset from a sliced copy of the digital asset comprises receiving independent verification from a first node and a second node, wherein the verification enforces a license for the digital asset.
7. The method of claim 4, wherein the first node is associated with a first licensed blockchain network and the second node is associated with a second licensed blockchain network.
8. A computer readable storage medium having program instructions embodied thereon, the program instructions being executable by a computing device to cause the computing device to perform method steps of the method according to any of claims 1 to 7.
9. A computer-implemented system, comprising:
A processor; and
a memory storing program instructions executable by the processor to cause the system to perform method steps of the method according to any one of claims 1 to 7.
10. A computer-implemented system comprising modules individually configured to perform each step of the method according to any one of claims 1 to 7.
11. A computer-implemented method, comprising:
receiving, by one or more processors, identification information of an owner of a digital asset, metadata of the digital asset, a digital hash of the digital asset, and the digital asset;
verifying, by the one or more processors, authenticity of the owner based at least in part on the received identification information;
creating, by one or more processors, a watermarked version of the digital asset based on the identity information of the owner, the metadata of the digital asset, and the digital hash in response to verifying the authenticity of the owner; and
the digital asset and the watermarked version of the digital asset are stored by one or more processors in a first distributed ledger, wherein the first distributed ledger has a link to a node in a second distributed ledger in which the original digital content is stored, wherein the link is stored on the same node or on a node adjacent to the watermarked digital content.
12. The method of claim 11, further comprising providing, by one or more processors, a public digital asset directory, wherein the public digital asset directory allows a user to request a license for a digital asset, including the digital asset, and validating the license request using one or more licensed blockchain networks.
13. The method of claim 12, further comprising storing, by one or more processors, the watermarked version of the digital asset in the public digital asset directory as a representation of the digital asset.
14. The method of claim 13, further comprising, in response to a user requesting a license for the digital asset via the public digital asset directory:
verifying, by one or more processors, a consensus of a request for a license for the digital asset using the one or more licensed blockchain networks; and
in response to verifying the consensus of the request for permission for the digital asset, access to the digital asset is provided to a user.
15. The method of claim 14, wherein providing a user with access to the digital asset comprises providing a read-only link to a node on the first distributed ledger in which the digital asset is stored, wherein the node is associated with a licensed blockchain network.
16. The method of claim 14, wherein providing a user with access to the digital asset comprises providing code for securely embedding the digital asset within a website.
17. The method of claim 11, wherein the received identification information, metadata, digital hashes, and digital assets are received from an owner's device in response to the owner capturing the digital assets using the device.
18. A computer readable storage medium having program instructions embodied thereon, the program instructions being executable by a computing device to cause the computing device to perform method steps of the method according to any of claims 11 to 17.
19. A computer-implemented system, comprising:
a processor; and
a memory storing program instructions executable by the processor to cause the system to perform method steps of the method according to any one of claims 11 to 17.
20. A computer-implemented system comprising modules individually configured to perform each step of the method according to any one of claims 11 to 17.
Applications Claiming Priority (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US16/191,684 | 2018-11-15 | ||
| US16/191,657 | 2018-11-15 | ||
| US16/191,657 US11048780B2 (en) | 2018-11-15 | 2018-11-15 | Preventing fraud in digital content licensing and distribution using distributed ledgers |
| US16/191,684 US20200159890A1 (en) | 2018-11-15 | 2018-11-15 | Securely storing digital content using a distributed ledger |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111191271A CN111191271A (en) | 2020-05-22 |
| CN111191271B true CN111191271B (en) | 2023-06-23 |
Family
ID=70709080
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911075193.6A Active CN111191271B (en) | 2018-11-15 | 2019-11-06 | Computer-implemented method, system and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111191271B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111930847B (en) * | 2020-09-16 | 2021-01-08 | 深圳壹账通智能科技有限公司 | Data processing method and device based on block chain and storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2017194976A1 (en) * | 2016-05-13 | 2017-11-16 | De La Rue International Limited | Methods and systems for processing assets |
| CN107392608A (en) * | 2017-07-11 | 2017-11-24 | 北京博晨技术有限公司 | Digital asset method of commerce and block catenary system based on block catenary system |
| CN107430619A (en) * | 2015-04-21 | 2017-12-01 | 谷歌公司 | System for associating correlated digital assets |
| CN107481140A (en) * | 2017-07-24 | 2017-12-15 | 湖南搜云网络科技股份有限公司 | Voucher identification code processing method and system, server and storage medium |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2696970C (en) * | 2007-08-17 | 2015-04-28 | Phoenix Myrrh Technology Pty Ltd. | Method and system for content delivery |
| US20160321435A1 (en) * | 2015-05-01 | 2016-11-03 | Monegraph, Inc. | Managing digital content via block chain registers |
| US20170116693A1 (en) * | 2015-10-27 | 2017-04-27 | Verimatrix, Inc. | Systems and Methods for Decentralizing Commerce and Rights Management for Digital Assets Using a Blockchain Rights Ledger |
| GB2573426A (en) * | 2016-12-22 | 2019-11-06 | Walmart Apollo Llc | Systems and methods for monitoring item distribution |
| US10509891B2 (en) * | 2017-05-03 | 2019-12-17 | Cisco Technology, Inc. | Method and system for content and service sharing |
-
2019
- 2019-11-06 CN CN201911075193.6A patent/CN111191271B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107430619A (en) * | 2015-04-21 | 2017-12-01 | 谷歌公司 | System for associating correlated digital assets |
| WO2017194976A1 (en) * | 2016-05-13 | 2017-11-16 | De La Rue International Limited | Methods and systems for processing assets |
| CN107392608A (en) * | 2017-07-11 | 2017-11-24 | 北京博晨技术有限公司 | Digital asset method of commerce and block catenary system based on block catenary system |
| CN107481140A (en) * | 2017-07-24 | 2017-12-15 | 湖南搜云网络科技股份有限公司 | Voucher identification code processing method and system, server and storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111191271A (en) | 2020-05-22 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20200159890A1 (en) | Securely storing digital content using a distributed ledger | |
| US11934497B2 (en) | Content anti-piracy management system and method | |
| US11048780B2 (en) | Preventing fraud in digital content licensing and distribution using distributed ledgers | |
| Dagher et al. | Ancile: Privacy-preserving framework for access control and interoperability of electronic health records using blockchain technology | |
| US10846416B2 (en) | Method for managing document on basis of blockchain by using UTXO-based protocol, and document management server using same | |
| CN110024357B (en) | System and method for data processing using distributed ledgers | |
| US11645369B2 (en) | Blockchain digital rights management streaming library | |
| US20180294957A1 (en) | System for Recording Ownership of Digital Works and Providing Backup Copies | |
| Konashevych | General concept of real estate tokenization on blockchain: The right to choose | |
| US9595034B2 (en) | System and method for monitoring third party access to a restricted item | |
| RU2656995C2 (en) | System and method for monitoring third party access to restricted item | |
| TWI571765B (en) | A system and method to protect user privacy in multimedia uploaded to internet sites | |
| US20220327153A1 (en) | Media attribution systems and methods | |
| CN110870253A (en) | System and method for managing a common software component ecosystem using a distributed ledger | |
| CN112069165A (en) | Document redaction and coordination | |
| US20230004970A1 (en) | Distributed Ledgers with Ledger Entries Containing Redactable Payloads | |
| CN115033919A (en) | Data acquisition method, device and equipment based on trusted equipment | |
| KR20210037274A (en) | Apparatus and method for managing contents | |
| Konashevych | Cross-blockchain protocol for public registries | |
| CN112052474A (en) | Blu-ray copy service | |
| US11687904B2 (en) | Downstream tracking of content consumption | |
| CN117043772A (en) | Block chain data separation | |
| CN111191271B (en) | Computer-implemented method, system and storage medium | |
| US20220182237A1 (en) | Entangled token structure for blockchain networks | |
| US20230245102A1 (en) | Non Fungible Token (NFT) Based Licensing and Digital Rights Management (DRM) for Software and Other Digital Assets |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |