Ryalty management method, device and system and storage medium

Abstract

The embodiment of the invention provides a royalty management method, device and system and a storage medium. The method comprises the following steps: determining a contribution degree vector of a digital work; constructing an authorization authentication information packet of the works according to the contribution degree vector; associating the authorization and authentication information packet with a media file of the work, and decoding the media file by a terminal where a user is located so as to obtain a contribution degree vector in the authorization and authentication information packet; the defect that an existing static royalty scheme cannot respond to contribution subjects and weight changes is overcome; according to the method, deep binding of the contribution distribution rule and the digital work is achieved, it is ensured that a user can directly obtain the contribution degree vector through decoding, a transparent and compliant interaction basis is provided for the user, and transaction trust is improved; through cooperation of under-chain accurate data processing and on-chain credible payment guidance, automation, fairness and transparency of royalty distribution are realized, and the blank of royalty management in an AIGC dynamic cooperation scene in the prior art is effectively filled.

Description

Technical Field

[0001] This application belongs to the field of blockchain technology, and in particular relates to a royalty management method, device, system and storage medium. Background Technology

[0002] In the realm of digital content, especially in the collaborative creation model of AIGC (Artificial Intelligence Generated Content), the creation of works often involves the dynamic input of multiple contributors (such as initial creators, model optimizers, prompt engineers, and secondary creators). Existing technical solutions, such as royalty distribution standards based on static rules (e.g., EIP-2981), only pre-determine fixed beneficiaries and distribution ratios at the time of creation, failing to adapt to the dynamic changes in contributor roles and contributions after creation. On the other hand, although existing research has been dedicated to qualitatively tracing the contribution sources of AIGC works by analyzing model weights and generation logs, these studies typically stop at ownership analysis and do not form a closed loop with an automated economic benefit distribution mechanism. This results in existing technologies failing to meet the actual needs of the AIGC ecosystem for efficient, fair, and dynamic royalty management. Summary of the Invention

[0003] This application provides a royalty management method, apparatus, system, and storage medium that can solve the technical problem of how to dynamically, efficiently, and fairly distribute royalties for digital works.

[0004] In a first aspect, embodiments of this application provide a royalty management method, the method being applied to an off-chain server, the method comprising: Determine the contribution vector of the digital work; wherein the contribution vector includes the addresses of multiple contributors participating in the royalty distribution and the royalty distribution ratio corresponding to each contributor address; Construct the authorization and authentication information package of the digital work based on the contribution vector; The authorization and authentication information package is associated with the media file of the digital work so that the user's terminal can decode the media file and obtain the contribution vector in the authorization and authentication information package.

[0005] In one feasible implementation, the step of determining the contribution vector of the digital work includes: Based on the creation log of the digital work and the blockchain events associated with the digital work, a draft contribution rating for the digital work is generated; wherein, the draft contribution rating includes multiple contributor addresses of the digital work and the royalty distribution ratio corresponding to each contributor address; The draft contribution is submitted to a multi-party signature governance contract deployed on a blockchain network, so that each contributor can sign and confirm the draft contribution through their respective terminal. If the multi-party signature governance contract verifies that the signatures corresponding to all contributor addresses in the contribution draft have been completed, the contribution vector of the digital work is determined based on the contribution draft.

[0006] In one feasible implementation, the authorization and authentication information package includes the contribution vector of the digital work, the perceptual hash value of the digital work, and the address of the royalty escrow contract for receiving royalty payments.

[0007] In one feasible implementation, the step of associating the authorization and authentication information package with the media file of the digital work includes: The watermark carrying format of the digital work is determined according to the media file type of the digital work; The authorization and authentication information packet is encoded and modulated to generate watermark data that matches the watermark carrier format; The watermark data is embedded into the corresponding carrying area of ​​the media file of the digital work to complete the association between the authorization and authentication information package and the media file of the digital work.

[0008] In one feasible implementation, the step of associating the authorization and authentication information package with the media file of the digital work, so that the user's terminal can decode the media file and obtain the contribution vector in the authorization and authentication information package, includes: The authorization and authentication information package is associated with the media file of the digital work so that the user's terminal can decode the media file, obtain the contribution vector and royalty escrow contract address in the authorization and authentication information package, and pay royalties to the royalty escrow contract address to obtain the right to use the digital work.

[0009] Secondly, embodiments of this application provide a royalty management method, which is applied to a node server of a blockchain network, and the method includes: Upon receiving a royalty distribution transaction request, determine the digital work for which royalties are to be distributed and the address of the requesting party; The off-chain decoding service is invoked to obtain the authorization and authentication information package from the media file of the digital work; wherein, the authorization and authentication information package is constructed by the off-chain server based on the contribution vector of the digital work; the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; The address of the request initiator is compared with the addresses of multiple contributors in the authorization and authentication information packet; If the request initiator address exists among the multiple contributor addresses, royalties are allocated to the request initiator address through a royalty escrow contract.

[0010] In one feasible implementation, the step of allocating royalties to the requester's address via a royalty escrow contract includes: Obtain the total escrow royalties of the digital works and the royalty allocation ratio of each contributor's address in the authorization and authentication information package; The royalty share of the request initiator's address is determined based on the royalty allocation ratio of each contributor's address and the total amount of escrowed royalties. The royalty share is transferred to the address of the request initiator through the royalty escrow contract.

[0011] Thirdly, embodiments of this application provide a royalty management device, which is applied to an off-chain server and includes: A vector determination module is used to determine the contribution vector of a digital work; wherein, the contribution vector includes the addresses of multiple contributors participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; An information construction module is used to construct an authorization and authentication information package for the digital work based on the contribution vector. The information association module is used to associate the authorization and authentication information package with the media file of the digital work, so that the user's terminal can decode the media file and obtain the contribution vector in the authorization and authentication information package.

[0012] Fourthly, this application provides a royalty management device, which is applied to a node server in a blockchain network. The device includes: The information determination module is used to determine the digital work to be allocated royalties and the address of the requester when a royalty distribution transaction request is received; The service invocation module is used to invoke the off-chain decoding service to obtain the authorization and authentication information package from the media file of the digital work; wherein, the authorization and authentication information package is constructed by the off-chain server based on the contribution vector of the digital work; the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; The address comparison module is used to compare the address of the request initiator with the addresses of multiple contributors in the authorization and authentication information packet; The royalty distribution module is used to distribute royalties to the request initiator address through a royalty escrow contract when the request initiator address exists among the multiple contributor addresses.

[0013] Fifthly, this application provides a royalty management system, characterized in that the royalty management system includes an off-chain server, a node server, and a user's terminal; The off-chain server is used to determine the contribution vector of the digital work; wherein, the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; The off-chain server is also used to construct an authorization and authentication information package for the digital work based on the contribution vector; The off-chain server is also used to associate the authorization and authentication information package with the media file of the digital work; The user's terminal is used to decode the media file of the digital work, decode the media file, obtain the contribution vector and royalty escrow contract address in the authorization and authentication information package, and pay royalties to the royalty escrow contract address in order to obtain the right to use the digital work. The node server is used to determine the digital work to be allocated royalties and the address of the requester when it receives a royalty distribution transaction request. The node server is also used to call the off-chain decoding service to obtain the authorization and authentication information packet from the media file of the digital work; The node server is also used to compare the address of the request initiator with the addresses of multiple contributors in the authorization and authentication information packet; The node server is also used to distribute royalties to the request initiator address through a royalty escrow contract when the request initiator address exists among the multiple contributor addresses.

[0014] Sixthly, embodiments of this application provide a computer storage medium storing computer program instructions, which, when executed by a processor, implement the royalty management method of the first aspect, or implement the royalty management method of the second aspect.

[0015] In a seventh aspect, embodiments of this application provide a server, the server comprising: a processor, and a memory storing computer program instructions; the processor reads and executes the computer program instructions to implement the royalty management method of the first aspect, or the royalty management method of the second aspect.

[0016] Eighthly, embodiments of this application provide a computer program product in which instructions, when executed by a processor of an electronic device, cause the electronic device to perform the royalty management method of the first aspect, or cause the electronic device to perform the royalty management method of the second aspect.

[0017] The royalty management method, apparatus, system, and storage medium of this application, by determining a contribution vector containing dynamic contribution information through an off-chain server, can accurately adapt to the characteristics of multi-party collaboration and dynamic changes in contribution relationships in AIGC works, solving the shortcomings of existing static royalty schemes that cannot respond to changes in the contributing subject and weight. Based on the contribution vector, an authorization and authentication information package is constructed and associated with the media file, achieving a deep binding between contribution allocation rules and digital works. This ensures that users can directly obtain the contribution vector through decoding, providing users with a transparent and compliant interaction basis and enhancing transaction trust. Without relying on complex on-chain additional logic, through the synergy of precise off-chain data processing and on-chain trusted payment guidance, the royalty allocation is automated, fair, and transparent, effectively filling the gap in existing technology for royalty management in AIGC dynamic collaboration scenarios. Attached Figure Description

[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a schematic flowchart of an embodiment of a royalty management method provided in this application. Figure 2 This is a schematic flowchart of Embodiment 2 of a royalty management method provided in this application; Figure 3 This is a flowchart illustrating Embodiment 3 of a royalty management method provided in this application. Figure 4 This is a schematic diagram of the structure of a royalty management device applied to an off-chain server, provided in an embodiment of this application; Figure 5 This is a schematic diagram of the structure of a royalty management device for a node server in a blockchain network, provided in an embodiment of this application. Figure 6 This is a schematic diagram of the structure of a royalty management system provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a server provided in an embodiment of this application. Detailed Implementation

[0020] The features and exemplary embodiments of various aspects of this application will be described in detail below. To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are only intended to explain this application and not to limit it. For those skilled in the art, this application can be implemented without some of these specific details. The following description of the embodiments is merely to provide a better understanding of this application by illustrating examples.

[0021] It should be noted that, in this document, relational terms such as "first" and "second" are used merely to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising..." does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes said element.

[0022] It should be noted that the acquisition, storage, use, and processing of data in this application embodiment all comply with the relevant provisions of national laws and regulations.

[0023] It should be noted that in the embodiments of this application, certain software, components, models and other existing solutions in the industry may be mentioned. These should be regarded as exemplary and are only intended to illustrate the feasibility of implementing the technical solution of this application. However, it does not mean that the applicant has used or necessarily used the solution.

[0024] In the scenario of collaborative creation and royalty management of AIGC works, existing technical solutions have significant limitations and defects: static royalty allocation standards (such as EIP-2981) rely on off-chain human negotiation to determine a fixed allocation ratio, which is difficult to adjust after minting, and lacks an objective and automated contribution evaluation mechanism adapted to the collaborative and dynamic evolution characteristics of AIGC; the on-chain content tracing system only records work information through a single cryptographic hash, which cannot identify compressed or slightly modified works of the same source in the real network environment, and its ability to trace and associate value in scenarios such as social media is greatly reduced; multi-signature control contracts and research on AIGC content ownership are limited to joint asset management and qualitative tracing of contribution sources, respectively, and have not formed an automated closed loop for the distribution of economic benefits. At the same time, existing technologies disperse core elements such as content hashes, royalty rules, and access permissions across the chain, IPFS (InterPlanetary File System), and centralized servers, failing to achieve a strong binding of the three, and the automated allocation relies heavily on centralized servers, resulting in insufficient credibility, while a fully decentralized solution lacks efficient dynamic decision-making capabilities.

[0025] Based on the shortcomings of the existing technology, the core technical problem to be solved by the embodiments of this application is: how to construct a highly integrated automated system that can inseparably bind the authenticity of the work's content in a real network environment, the rights distribution rules reflecting the dynamic contributions of all parties, and the final stablecoin royalty payment execution. The system needs to be able to continuously update the contribution level using objective evaluation methods, and solidify this dynamic contribution right together with the enhanced certified work content identifier in digital assets. This solidified information can serve as a unique and credible credential, driving a process that is triggered only by legitimate contributors and strictly allocates stablecoin royalties automatically according to the latest contribution ratio, thereby effectively incentivizing continuous creation and promotion.

[0026] To address the problems of the prior art, embodiments of this application provide a royalty management method, apparatus, system, and storage medium. The royalty management method provided by embodiments of this application will be described first.

[0027] Figure 1 A flowchart illustrating a royalty management method according to an embodiment of this application is shown. Figure 1 As shown, this method is applied to an off-chain server and may include steps 210-230: Step 210: Determine the contribution vector of the digital work; wherein the contribution vector includes the addresses of multiple contributors participating in the royalty distribution and the royalty distribution ratio corresponding to each contributor address.

[0028] The execution entity in this embodiment can be an off-chain server in the royalty management system. The royalty management system includes an off-chain server, node servers of the blockchain network, the user's terminal, and the contributor's terminal. The off-chain server, as the core processing engine of the system, carries an AI (Artificial Intelligence)-assisted dynamic contribution attribution and content authentication module, as well as a blind watermark embedding module that integrates content authentication and contribution permissions. It is responsible for performing contribution analysis, constructing an AAP (Authorization & Authentication Packet), and dynamically embedding it into the digital work's media file. The node servers of the blockchain network constitute the system's trusted arbitration and execution layer, running smart contracts (such as royalty escrow contracts) specifically deployed for the digital work and belonging to a royalty payment, distribution, and re-incentive system driven by NFT embedded information. These contracts are responsible for securely holding assets, verifying permissions, and automatically executing distribution rules. The user's terminal serves as the system's payment entry point, decoding the AAP in the work and completing royalty payments through an integrated SDK (Software Development Kit). The contributor's terminal serves as the system's revenue claim interface, authorizing and triggering on-chain distribution functions to obtain their due share. This architecture achieves full automation of the entire process, from contribution assessment and content authentication to payment allocation, through the division of labor and collaboration among its various components.

[0029] An off-chain server refers to an independent server deployed outside the blockchain network that has powerful data processing and logic execution capabilities. It does not participate in on-chain consensus, but serves as the core computing and coordination engine of the system. It is specifically responsible for performing AI-assisted dynamic contribution attribution, building authorization and authentication information packages (AAP), and driving the dynamic embedding of blind watermarks. This server can be operated and maintained by the initiator of the digital work or a neutral third-party management organization.

[0030] Digital works refer to creative creations existing in digital form, such as images, music, videos, text, or 3D models created using AIGC tools. In this implementation, ownership or usage rights are represented on a blockchain network through NFTs.

[0031] The contribution vector is used to quantify and record the contribution weight of all participants in the creation, modification, or promotion of digital works. Its core data fields include, but are not limited to, at least one contributor address and the corresponding royalty allocation ratio. The contributor address refers to the unique identifier (i.e., its blockchain wallet address) of the participant in the royalty allocation; the royalty allocation ratio refers to the weighted value used to calculate the royalty share due to each contributor address, which can be expressed as a percentage or decimal, and the sum of the royalty allocation ratios of all contributor addresses should be 100%.

[0032] Optionally, the project initiator can upload the contribution credentials of each contributor through an off-chain server. The off-chain server calls a preset weighting algorithm (such as a weighted model based on contribution type) to calculate the allocation ratio, and after generating a vector, it is confirmed by multiple parties' signatures to obtain the contributor vector.

[0033] In addition to the methods described above, contribution vectors can also be determined using methods including but not limited to the following: An off-chain server connects to the AIGC creation platform's log system to automatically capture contributor operation records (such as model call records and prompt word input logs), generates an allocation ratio based on the frequency of contribution behaviors and effect scores, and directly outputs the contribution vector. In this implementation, the contribution vector of digital works can be dynamically adjusted and updated.

[0034] Step 220: Construct the authorization and authentication information package of the digital work based on the contribution vector.

[0035] The authorization and authentication information package serves as the core carrier connecting digital works, contribution rules, and payment execution. It includes at least an identifier for content identification (such as the perceptual hash of the digital work), a contribution vector, and a royalty escrow contract address, thereby achieving a reliable binding from a specific work to a compliant payment path. The royalty escrow contract address refers to the unique identifier address of a smart contract deployed on the blockchain. This contract is responsible for receiving, holding, and securely transferring royalty funds. Its fund allocation logic can be limited to executing the contribution rules defined in the authorization and authentication information package, thus ensuring the automation and objectivity of the allocation.

[0036] Optionally, the blind watermarking embedding module in the off-chain server, which integrates content authentication and contribution permissions, integrates elements such as identifiers used for content identification (e.g., perceptual hashes of digital works), contribution vectors, and royalty escrow contract addresses, and organizes them into an indivisible, portable structured data set (i.e., digital asset ID card), thereby forming an authorization and authentication information package.

[0037] In one feasible implementation, the authorization and authentication information package includes the contribution vector of the digital work, the perceptual hash value of the digital work, and the address of the royalty escrow contract for receiving royalty payments.

[0038] The perceptual hash value of a digital work refers to the hash value calculated from the original media file of the digital work to capture its macroscopic characteristics. Hash algorithms, including but not limited to pHash and dHash, can be used. Even after undergoing common lossy operations (such as automatic compression) during the dissemination and promotion of a digital work, its calculated perceptual hash values ​​remain highly similar, enabling the system to recognize the same digital work that has been slightly modified during online distribution.

[0039] Among them, the perceptual hash value of the digital work can be calculated after the digital work is generated; at the same time, the AI-assisted dynamic contribution attribution and content authentication module in the system will perform parallel calculations on the original, lossless media files of the digital work to obtain the cryptographic hash value of the digital work. Its function is to generate a unique and highly secure content fingerprint, which is used for strict and unambiguous identity registration and integrity comparison on the blockchain network.

[0040] By combining two types of hash values ​​and using the perceptual hash as the core identifier for subsequent payment and verification processes, the problem of reliably identifying and associating the value of lossy media files in a real network environment is solved. The cryptographic hash ensures the absoluteness of the root trust on the chain, while the perceptual hash ensures the robustness of off-chain application scenarios.

[0041] Optionally, the authorization and authentication information package includes at least a contribution vector of the digital work, a perceptual hash value, and a royalty escrow contract address for receiving royalty payments; wherein each contributor's address in the contribution vector is used for access control; the royalty allocation ratio corresponding to each contributor's address is used for value distribution; the perceptual hash value is used for content identification; and the royalty escrow contract address is used to guide payment. In this embodiment, elements such as content identification, payment guidance, access control, and value distribution are bundled together, providing a data foundation for achieving asset independence and portability.

[0042] Step 230: Associate the authorization and authentication information package with the media file of the digital work so that the user's terminal can decode the media file and obtain the contribution vector in the authorization and authentication information package.

[0043] The user's terminal refers to the user device used to access and use digital works, including mobile phones, computers, tablets, etc., and must have the ability to decode media files.

[0044] In some embodiments, the blind watermarking embedding module in the off-chain server, which integrates content authentication and contribution permissions, associates the authorization authentication information package with the media file of the digital work, thereby establishing and maintaining an inseparable, machine-readable binding relationship between the authorization authentication information package and the media file of the digital work. This association can be performed using a transform domain blind watermarking algorithm or other methods, and this embodiment does not impose any limitations on this approach.

[0045] Once a user's terminal obtains the media file of a digital work, the SDK can scan the media file, decode the App Application File (AAP), and obtain the contribution vector contained in the AAP. By using the contributor addresses contained in the contribution vector and the royalty distribution ratio corresponding to each contributor address, users can also understand the royalty distribution rules of the digital work, thereby improving transaction transparency.

[0046] In one feasible implementation, step 230 may further include steps A11-A13: Step A11: Determine the watermark carrying format of the digital work based on the media file type of the digital work.

[0047] Step A12: Encode and modulate the authorization and authentication information packet to generate watermark data that matches the watermark carrier format.

[0048] Step A13: Embed the watermark data into the corresponding carrier area of ​​the media file of the digital work to complete the association between the authorization and authentication information package and the media file of the digital work.

[0049] Media file type refers to the specific format category of a digital work, including but not limited to images, audio, and text. Watermark carrier format is the technical form used to carry watermark data; its core function is to achieve a natural integration of watermark data with the digital work. Different media file types are adapted to different watermark carrier formats. Watermark carrier formats are divided into two categories: visible watermark formats and invisible watermark formats. Visible watermark formats include, but are not limited to, image formats and QR code formats; invisible watermark formats include, but are not limited to, spectral formats and frequency domain coefficient formats.

[0050] Optionally, the watermark carrier format can be selected in ways including but not limited to the following: 1. First, determine the visibility or invisibility requirements of the watermark based on user needs, and then select a format that matches the media file type of the digital work from the corresponding set of watermark carrier formats; 2. Directly select a watermark carrier format that matches the media file type of the digital work. For example, when the media file type is an image, the frequency domain coefficient format can be selected as the watermark carrier format; when the media file type is audio, the spectrum format can be selected as the watermark carrier format.

[0051] Optionally, the blind watermark embedding module for integrating content authentication and contribution permissions, hosted on the off-chain server, first calls a serialization tool to convert the structured information contained in the AAP, such as the perceptual hash, contribution vector, and royalty escrow contract address, into a continuous data stream in a standard format (e.g., using Protocol Buffers to ensure data compactness). A general compression algorithm is then used to reduce the size of this data stream, removing redundant information, ultimately resulting in a streamlined, directly embeddable data. Following the encoding method corresponding to the selected watermark carrier format, the data to be embedded undergoes signal adjustment and modulation to generate watermark data matching that watermark carrier format. Here, watermark data refers to the target data, after encoding and modulation, that can be directly embedded into the digital work's carrying area; its form is determined by the watermark carrier format and is the carrier-based presentation of the authorization and authentication information package.

[0052] The carrying area corresponding to the media file refers to the specific area used to embed watermark data. It must meet the dual requirements of not destroying the core content of the work and ensuring the robustness of the watermark. The specific location can be determined by the media file type of the digital work and the watermark carrying format.

[0053] In some embodiments, the blind watermark embedding module for merging content authentication and contribution permissions, carried in the off-chain server, selects a corresponding highly robust mathematical transformation algorithm for the watermark carrying form (e.g., when the watermark carrying form is in the frequency domain coefficient form, a discrete cosine transform or discrete wavelet transform domain blind watermarking algorithm can be selected). This algorithm places the watermark data in the corresponding carrying area of ​​the digital work media file, thereby completing the association between the AAP and the media file. At this point, the AAP is inseparably bound to the media file through the digital watermark, and this binding has high robustness (resistant to common lossy operations). When a new contribution vector takes effect, a new AAP is constructed based on the new contribution vector, and the above steps A11-A13 will be automatically repeated to update the watermark in the media file with the new AAP, realizing the dynamic iteration of the AAP.

[0054] In this implementation, by adapting the selected watermark carrier format according to the media file type of the digital work, the AAP containing information such as perceptual hash and contribution vector is processed into matching watermark data and embedded in the corresponding carrier area, achieving an inseparable binding between the AAP and the media file. While balancing visible / invisible watermark scenarios and high robustness, it also supports dynamic iterative updates of the AAP when a new contribution vector takes effect. This allows the NFT media file itself to directly carry and update the complete authorization and authentication information package in real time, completing AAP iteration without frequent on-chain transactions, ensuring the continuity and robustness of the binding between the digital work and contribution rules and payment execution.

[0055] In one feasible implementation, the step of associating the authorization authentication information package with the media file of the digital work so that the user's terminal can decode the media file and obtain the contribution vector in the authorization authentication information package includes: associating the authorization authentication information package with the media file of the digital work so that the user's terminal can decode the media file, obtain the contribution vector and royalty escrow contract address in the authorization authentication information package, and paying royalties to the royalty escrow contract address to obtain the work usage rights of the digital work.

[0056] Optionally, after a user's terminal obtains the media file of a digital work, the following operations can be performed: The accompanying SDK scans the media file, decodes the Authorization Authentication Package (AAP) associated with the media file, and obtains the core information contained in the AAP, including but not limited to contribution vectors and royalty escrow contract addresses; while clearly displaying the addresses of each contributor to the digital work and their corresponding royalty distribution weights through the contribution vectors, clarifying the legal flow and distribution rules of royalty revenue, the user is guided to pay royalties to the royalty escrow contract address specified in the AAP through their terminal; after the royalty escrow contract payment is confirmed, the user can obtain legal usage rights to the digital work, thereby unlocking and obtaining the original lossless media file content of the digital work, ensuring that the user fully enjoys the usage rights of the digital work under compliant conditions.

[0057] In this implementation, by associating the authorization and authentication information package with the digital work media file, the user terminal can decode and obtain the contribution vector and the royalty escrow contract address. This clarifies the royalty distribution rules to protect the fair rights of contributors, provides a legitimate royalty payment address, and establishes a reliable connection link between contribution value and royalty payment. Under the premise of protecting the interests of all parties, this greatly improves the transparency, convenience, and automation of digital asset transactions.

[0058] This embodiment determines a contribution vector containing dynamic contribution information through an off-chain server. This accurately adapts to the characteristics of multi-party collaboration and dynamic changes in contribution relationships in AIGC works, solving the shortcomings of existing static royalty schemes that cannot respond to changes in the contributing subject and weight. Based on the contribution vector, an authorization and authentication information package is constructed and associated with the media file, realizing a deep binding between contribution allocation rules and digital works. This ensures that users can directly obtain the contribution vector through decoding, providing users with a transparent and compliant basis for interaction and enhancing transaction trust. Without relying on complex on-chain additional logic, the collaboration between precise off-chain data processing and on-chain trusted payment guidance achieves automated, fair, and transparent royalty allocation, effectively filling the gap in royalty management in AIGC dynamic collaboration scenarios.

[0059] Based on the first embodiment of this application, in the second embodiment of this application, the content that is the same as or similar to that in the first embodiment described above can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 2 In the royalty management method, step 210 may include steps 310-330: Step 310: Based on the creation log of the digital work and the blockchain events associated with the digital work, generate a draft contribution rating for the digital work; wherein the draft contribution rating includes multiple contributor addresses of the digital work and the royalty distribution ratio corresponding to each contributor address.

[0060] The creation log refers to all operational data recorded by the AIGC tool during the generation of digital works, including but not limited to model call parameters, prompt input records, creative iteration trajectory, and initial operation records of participants. It is the core data source for tracing original creative contributions. Blockchain events refer to publicly verifiable and tamper-proof on-chain behaviors and derivative records associated with digital works and recorded on the blockchain network. These include but are not limited to NFT circulation and transaction records corresponding to digital works, royalty payment records, on-chain rights confirmation records of secondary creations based on the work, on-chain transaction traceability records related to promotional activities, and records of changes in contributor-related rights. They are the core data source for quantifying visible on-chain contributions (such as on-chain promotion conversion and public secondary creation).

[0061] Optionally, a draft contribution score can be formed by extracting core contribution behaviors (such as initial creation, parameter optimization, and content correction) from the generated logs and valid contribution credentials (such as collaboration records signed by contributors and compliant payment records) from blockchain events, combined with a preset contribution type weight library (such as the original contribution ratio benchmark and the promotion contribution converted according to the traffic amount). The corresponding contributor address can be matched and the allocation ratio calculated.

[0062] In addition to the methods mentioned above, contribution attribution drafts can also be generated using methods including but not limited to the following: An AI-assisted dynamic contribution attribution and content authentication module hosted on an off-chain server collects the creation logs of digital works and related blockchain events. After preprocessing these two types of data according to a preset format, they are input into a large contribution attribution model. The model automatically identifies all contributing entities by analyzing dimensions such as creative participation behavior, contribution impact weight, and downstream value conversion, generating a contribution attribution draft that includes the addresses of each contributor and their corresponding royalty distribution ratio, ensuring the objectivity and comprehensiveness of the allocation scheme. The large contribution attribution model refers to an AI model with dynamic contribution analysis capabilities, used to quantify the contribution weight of each contributor (creator, promoter, etc.) and output an objective contribution attribution draft.

[0063] In the above approach, the contribution draft only becomes effective after consensus confirmation. Furthermore, in the process of generating the contribution draft, in addition to the creation logs of digital works and blockchain events associated with them, off-chain events can also be incorporated to further improve the accuracy of the draft. Off-chain events refer to offline or off-chain behaviors and derivative events related to the creation, promotion, and value transformation of digital works but not recorded on the blockchain network. These include, but are not limited to, early creative draft iteration records not on the blockchain, unauthorized non-public secondary creation operations, and communication and execution records of offline collaborations between contributors. Such events can supplement the on-chain event dimension and provide a reference for comprehensively quantifying contributions.

[0064] Step 320: Submit the draft contribution score to the multi-party signature governance contract deployed on the blockchain network, so that each contributor can sign and confirm the draft contribution score through the corresponding contributor's terminal.

[0065] Multi-signature governance contracts refer to smart contracts deployed on blockchain networks that have signature verification and consensus confirmation functions. They are used to receive contribution drafts and collect signature feedback from each contributor. The draft only takes effect when preset signature conditions are met, ensuring the fairness, transparency and non-repudiation of the distribution process.

[0066] Optionally, the AI-assisted dynamic contribution attribution and content authentication module hosted on the off-chain server uploads the generated contribution draft to the multi-party signature governance contract deployed on the blockchain network. The contract automatically sends signature notifications to the blockchain wallets corresponding to the addresses of all contributors in the draft. Each contributor accesses the blockchain network through their own contributor terminal, views the contribution draft published in the contract (including the allocation ratio corresponding to their own address), and if they approve of the scheme, initiates an on-chain signature operation through the terminal, uploading the signature result to the multi-party signature governance contract to complete the individual consensus confirmation.

[0067] Step 330: If the multi-party signature governance contract verifies that the signatures corresponding to all contributor addresses in the contribution draft have been completed, determine the contribution vector of the digital work based on the contribution draft.

[0068] Optionally, the multi-signature governance contract continuously monitors and verifies the signature status of each contributor, matching the contributor addresses recorded in the draft with the signatures submitted on-chain. When the contract verifies that all contributor addresses in the draft have completed valid signatures, the consensus mechanism is triggered. The AI-assisted dynamic contribution attribution and content authentication module hosted on the off-chain server officially confirms the contribution draft as the contribution vector of the digital work, serving as the core basis for the subsequent Authorization Authentication Package (AAP) construction and royalty distribution. If there are unsigned or invalid signatures, the contract remains in a draft pending confirmation state and is temporarily ineffective.

[0069] Subsequently, when the user's terminal pays the royalties for the digital work, the royalty escrow contract deployed on the blockchain automatically records the income and binds the user's wallet address to a specific event representing the promotional contribution, thus obtaining an updated blockchain event. Based on the updated blockchain event, the contribution attribution model can update the contribution draft and re-execute steps 310-330 to obtain a new contribution vector.

[0070] This implementation method establishes an end-to-end automated path from user acquisition of a work to completion of compliant payment. Through a smart contract mechanism, payment behavior is automatically recorded as a valid promotional contribution, and the payer's address is linked to potential future revenue opportunities. This not only injects an incentive for viral spread into the system, but also ensures that all revenue generated from payments is immediately and automatically deposited into the work's dedicated royalty escrow contract account, achieving real-time collection and secure custody of royalty funds and guaranteeing the foundation for subsequent distribution.

[0071] This embodiment generates a draft contribution score for a digital work based on its creation log and associated blockchain events. The draft contribution score includes multiple contributor addresses and their corresponding royalty distribution ratios. The draft contribution score is submitted to a multi-party signature governance contract deployed on the blockchain network, allowing each contributor to sign and confirm the draft contribution score through their respective terminals. Once the multi-party signature governance contract verifies that all contributor addresses in the draft contribution score have completed their signatures, the contribution vector for the digital work is determined based on the draft contribution score. By automatically analyzing contribution data and generating a draft contribution score using the digital work's creation log and associated blockchain events, the efficiency bottleneck and subjectivity of manual evaluation are overcome. Simultaneously, the consensus confirmation of the draft contribution score through the on-chain multi-party signature governance contract ensures the fairness, transparency, and non-repudiation of the final contribution vector, effectively resolving trust and acceptance issues that may arise from purely intelligent decision-making, and achieving a unity of objective attribution and consensus recognition.

[0072] Based on any one or more embodiments of this application, in the third embodiment of this application, the content that is the same as or similar to the above embodiments can be referred to the above description, and will not be repeated hereafter. Based on this, please refer to... Figure 3 This method, applied to node servers in a blockchain network, may include steps 410-440: Step 410: Upon receiving a royalty distribution transaction request, determine the digital work to be distributed and the address of the requesting party.

[0073] In this embodiment, the executing entity can be a node server in the blockchain network of the royalty management system. A node server refers to a participating node device deployed in the blockchain network, possessing the core capabilities of receiving transaction requests, calling off-chain services, executing contract interactions, and verifying data.

[0074] A royalty distribution transaction request is an on-chain transaction request initiated by an entity qualified to distribute royalties, used to claim royalties for a corresponding digital work. The digital work to be distributed is one that has been bound to a royalty escrow contract through an authorization and authentication information package and has distributable royalty funds. Its media file contains the latest AAP (Application Programming Interface), which can be uniquely represented on-chain using NFTs. The request initiator's address refers to the unique identifier (i.e., blockchain wallet address) of the entity initiating the royalty distribution transaction request within the blockchain network.

[0075] The node servers in the blockchain network run royalty escrow contracts specifically deployed for the digital work, belonging to a royalty payment, distribution, and re-incentivization system driven by embedded NFT information. They continuously monitor on-chain transaction requests. When a royalty distribution transaction request is received (which can be initiated by the subject by calling the claimMyShare() function), the node server parses the core fields in the transaction request, extracts the digital work identifier to be distributed (such as the unique NFT identifier corresponding to the digital work), and obtains the address of the requester of the transaction request. This completes the collection of basic information for royalty distribution, providing a prerequisite for subsequent permission verification and distribution execution.

[0076] Step 420: Invoke the off-chain decoding service to obtain the authorization and authentication information package from the media file of the digital work; wherein, the authorization and authentication information package is constructed by the off-chain server based on the contribution vector of the digital work; the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address.

[0077] Off-chain decoding service refers to a decoding service deployed off-chain with trusted standardization capabilities. It is used to extract and decode embedded AAPs from media files of digital works. The decoding results need to be fed back to the blockchain network through an oracle to ensure the authenticity and reliability of the data.

[0078] When the node server executes the royalty escrow contract code, the contract logic initiates a data request to a specific off-chain decoding service through the blockchain oracle interface. After receiving the request, the off-chain decoding service performs the following operations: obtains the corresponding media file based on the digital work identifier in the request (such as the cryptographic hash of the media file pointed to in the NFT metadata); extracts the embedded, serialized data from the media file using the corresponding decoding algorithm (such as the blind watermark extraction algorithm); deserializes the data, reconstructs the structured authorization and authentication information packet (AAP), and returns it to the on-chain royalty escrow contract through the oracle network.

[0079] Step 430: Compare the address of the request initiator with the addresses of multiple contributors in the authorization and authentication information packet.

[0080] Optionally, upon receiving the AAP, the royalty escrow contract on the node server executes its verification logic: comparing the request initiator's address with the list of contributor addresses carried in the AAP one by one; if the request initiator's address exists in the list of contributor addresses in the AAP, the authorization verification is passed. If the request initiator's address does not exist in the list of contributor addresses in the AAP, the contract immediately terminates the transaction execution and rolls back all state changes, and the request initiator cannot receive royalty distribution.

[0081] Step 440: If the request initiator address exists among the multiple contributor addresses, royalties are allocated to the request initiator address through a royalty escrow contract.

[0082] Optionally, if a request initiator address exists among multiple contributor addresses, the royalty escrow contract automatically triggers the allocation function after authorization verification, using the contribution vector in AAP to allocate royalties to the request initiator address.

[0083] In one feasible implementation, step 440 may further include steps B11-B13: Step B11: Obtain the total escrow royalties of the digital work and the royalty allocation ratio of each contributor's address in the authorization and authentication information package; Step B12: Determine the royalty share of the request initiator's address based on the royalty allocation ratio of each contributor's address and the total amount of escrowed royalties; Step B13: Transfer the royalty share to the address of the request initiator through the royalty escrow contract.

[0084] The total escrow royalties refer to the total amount of all distributable royalties for the digital work that has been collected in the royalty escrow contract deployed on the blockchain network. The source of the funds is stablecoins paid by users when they obtain the legal right to use the digital work, and it has the characteristics of being publicly verifiable and tamper-proof.

[0085] Optionally, after the royalty escrow contract in the node server passes the authorization verification of the request initiator, it extracts the total escrow royalty amount corresponding to the digital work to be allocated from the contract account; and extracts the contributor addresses and corresponding royalty allocation ratios recorded in the contribution vector from the obtained Authorization Authentication Information Packet (AAP); it locates the specific royalty allocation ratio matching the request initiator address from the contributor addresses and corresponding allocation ratios; it multiplies the allocation ratio with the total escrow royalty amount to determine the royalty share currently due to the request initiator address; after completing the royalty share calculation, the royalty escrow contract automatically triggers the fund transfer function, extracts stablecoins equal to the royalty share from the digital work royalty fund account held by the contract, and completes the targeted transfer to the blockchain wallet address corresponding to the request initiator address.

[0086] In this implementation, by automatically obtaining the total amount of escrowed royalties and the royalty distribution rules in the AAP, the royalty share due to the requesting party is accurately calculated and the targeted transfer is completed based on the royalty escrow contract. This achieves automated and precise royalty distribution covering both creative and promotional contributions, ensuring that the distribution process is publicly verifiable and non-repudiable, and efficiently realizing the distribution goal of matching the value and contribution of digital works.

[0087] In some embodiments, for ease of understanding, the overall process of the royalty management method is illustrated below: In the "AI-assisted dynamic contribution attribution" module, after AIGC content generation or subsequent promotion events occur, the generation log / promotion event is input into the contribution attribution AI model to generate a draft contribution vector containing contributor addresses and suggested weights (i.e., royalty allocation ratios). This draft is then used to achieve human-machine collaborative consensus (signatures of all core contributors) through a multi-party signature governance contract to form an effective contribution vector. After AIGC content generation or subsequent promotion events occur, the module simultaneously inputs the original media file into a hybrid content hash generator to generate perceptual hashes and cryptographic hashes. The effective contribution vector and perceptual hashes are input into the Authorization and Authentication Package (AAP) builder in the "Blind Watermark Embedding with Fusion Authentication and Permissions" module to generate an AAP containing hashes, a list of contributor addresses, weights, and contract addresses. The AAP, as watermark information, is used by a dynamic blind watermark embedder to generate NFT media files carrying new watermarks, using NFT media files as the carrier. Finally, in the "Royalty Payment, Distribution, and Re-incentive" module... In the system, users / consumers scan NFT media files through the front-end SDK / payment portal. The SDK decodes the App Access Point (AAP) and guides the payment. Stablecoins are deposited into the royalty escrow contract, and the payment is recorded and bound to the promoter. After the contributor / promoter initiates a request by calling the claimMyShare() function, the trusted decoding service / oracle extracts the latest AAP. After the royalty escrow contract verifies the permissions, it distributes compliant stablecoins to the corresponding contributors / promoters according to the rules, completing the entire royalty management process.

[0088] This embodiment, upon receiving a royalty distribution transaction request, determines the digital work to be distributed and the address of the requesting party; it then invokes an off-chain decoding service to obtain an authorization and authentication information package from the media file of the digital work; wherein, the authorization and authentication information package is constructed by the off-chain server based on the contribution vector of the digital work; the contribution vector includes multiple contributor addresses participating in the royalty distribution and the corresponding royalty distribution ratio for each contributor address; the requesting party address is compared with the multiple contributor addresses in the authorization and authentication information package; if the requesting party address exists among the multiple contributor addresses, royalty is distributed to the requesting party address through a royalty escrow contract. By implementing a complete process of receiving requests, decoding AAP, verifying permissions, and automatically allocating resources, a unified, hierarchical, dynamic allocation mechanism has been established. This mechanism can handle the complex contribution levels of the initial creation of digital works and seamlessly integrate subsequent market promotion contributions into the same value allocation system. Furthermore, by strictly binding royalty extraction permissions with the dynamically updated authorization list embedded in the NFT, and leveraging the robust advantages of dynamic AAP iteration and blind watermark embedding, flexible adaptation of allocation rules can be achieved without frequent on-chain transactions. This achieves automation, fairness, and flexibility in the allocation process, ensuring the continuity and reliability of value allocation and contribution rule binding.

[0089] It should be noted that the acquisition, storage, use, and processing of data in the embodiments of this application all comply with the relevant provisions of national laws and regulations. Furthermore, it should be noted that certain software, components, models, and other existing industry solutions may be mentioned in the embodiments of this application. These should be considered exemplary, intended only to illustrate the feasibility of implementing the technical solution of this application, and do not imply that the applicant has already used or necessarily used such solutions.

[0090] like Figure 4 As shown, this application embodiment provides a royalty management device 200, which is applied to an off-chain server and may include a vector determination module 201, an information construction module 202, and an information association module 203; The vector determination module 201 is used to determine the contribution vector of the digital work; wherein, the contribution vector includes the addresses of multiple contributors participating in the royalty distribution and the royalty distribution ratio corresponding to each contributor address; Information construction module 202 is used to construct the authorization and authentication information package of the digital work based on the contribution vector; The information association module 203 is used to associate the authorization and authentication information package with the media file of the digital work, so that the user's terminal can decode the media file and obtain the contribution vector in the authorization and authentication information package.

[0091] Optionally, the vector determination module 201 is also used for: Based on the creation log of the digital work and the blockchain events associated with the digital work, a draft contribution rating for the digital work is generated; wherein, the draft contribution rating includes multiple contributor addresses of the digital work and the royalty distribution ratio corresponding to each contributor address; The draft contribution is submitted to a multi-party signature governance contract deployed on a blockchain network, so that each contributor can sign and confirm the draft contribution through their respective terminal. If the multi-party signature governance contract verifies that the signatures corresponding to all contributor addresses in the contribution draft have been completed, the contribution vector of the digital work is determined based on the contribution draft.

[0092] Optionally, the information construction module 202 is further configured to: The authorization and authentication information package includes the contribution vector of the digital work, the perceptual hash value of the digital work, and the address of the royalty escrow contract for receiving royalty payments.

[0093] Optionally, the information association module 203 is further configured to: The watermark carrying format of the digital work is determined according to the media file type of the digital work; The authorization and authentication information packet is encoded and modulated to generate watermark data that matches the watermark carrier format; The watermark data is embedded into the corresponding carrying area of ​​the media file of the digital work to complete the association between the authorization and authentication information package and the media file of the digital work.

[0094] Optionally, the information association module 203 is further configured to: The authorization and authentication information package is associated with the media file of the digital work so that the user's terminal can decode the media file, obtain the contribution vector and royalty escrow contract address in the authorization and authentication information package, and pay royalties to the royalty escrow contract address to obtain the right to use the digital work.

[0095] like Figure 5 As shown, this application embodiment provides a royalty management device 300, which is applied to a node server of a blockchain network and may include an information determination module 401, a service call module 402, an address comparison module 403, and a royalty allocation module 404. The information determination module 401 is used to determine the digital work to be allocated royalties and the address of the requester when a royalty allocation transaction request is received; Service invocation module 402 is used to invoke the off-chain decoding service to obtain an authorization and authentication information package from the media file of the digital work; wherein, the authorization and authentication information package is constructed by the off-chain server based on the contribution vector of the digital work; the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; Address comparison module 403 is used to compare the address of the request initiator with the addresses of multiple contributors in the authorization and authentication information packet; The royalty distribution module 404 is used to distribute royalties to the request initiator address through a royalty escrow contract when the request initiator address exists among the multiple contributor addresses.

[0096] Optionally, the royalty allocation module 404 is further configured to: Obtain the total escrow royalties of the digital works and the royalty allocation ratio of each contributor's address in the authorization and authentication information package; The royalty share of the request initiator's address is determined based on the royalty allocation ratio of each contributor's address and the total amount of escrowed royalties. The royalty share is transferred to the address of the request initiator through the royalty escrow contract.

[0097] like Figure 6 As shown, this application embodiment provides a royalty management system 500, which may include an off-chain server 501, a node server 502, and a user's terminal 503; The off-chain server 501 is used to determine the contribution vector of the digital work; wherein, the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; The off-chain server 501 is also used to construct the authorization and authentication information package of the digital work based on the contribution vector; The off-chain server 501 is also used to associate the authorization and authentication information package with the media file of the digital work; The user's terminal 503 is used to decode the media file of the digital work, decode the media file, obtain the contribution vector and royalty escrow contract address in the authorization and authentication information package, and pay royalties to the royalty escrow contract address in order to obtain the right to use the digital work. The node server 502 is used to determine the digital work to be allocated royalties and the address of the request initiator when it receives a royalty distribution transaction request. The node server 502 is also used to call the off-chain decoding service to obtain the authorization and authentication information packet from the media file of the digital work; The node server 502 is also used to compare the address of the request initiator with the addresses of multiple contributors in the authorization and authentication information packet; The node server 502 is also used to distribute royalties to the request initiator address through a royalty escrow contract when the request initiator address exists among the multiple contributor addresses.

[0098] Figure 7 A schematic diagram of the hardware structure of the server provided in an embodiment of this application is shown.

[0099] The server may include a processor 301 and a memory 302 storing computer program instructions.

[0100] Specifically, the processor 301 may include a central processing unit (CPU), an application specific integrated circuit (ASIC), or one or more integrated circuits that can be configured to implement the embodiments of this application.

[0101] Memory 302 may include mass storage for data or instructions. For example, and not limitingly, memory 302 may include a hard disk drive (HDD), floppy disk drive, flash memory, optical disk, magneto-optical disk, magnetic tape, or Universal Serial Bus (USB) drive, or a combination of two or more of these. In one instance, memory 302 may include removable or non-removable (or fixed) media, or memory 302 may be non-volatile solid-state memory. Memory 302 may be internal or external to the integrated gateway disaster recovery device.

[0102] In one instance, memory 302 may be read-only memory (ROM). In one instance, the ROM may be a mask-programmed ROM, a programmable ROM (PROM), an erasable PROM (EPROM), an electrically erasable PROM (EEPROM), an electrically rewritable ROM (EAROM), or flash memory, or a combination of two or more of these.

[0103] Memory 302 may include read-only memory (ROM), random access memory (RAM), disk storage media device, optical storage media device, flash memory device, electrical, optical, or other physical / tangible memory storage device. Therefore, generally, memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described with reference to the method according to one aspect of this disclosure.

[0104] The processor 301 reads and executes computer program instructions stored in the memory 302 to achieve... Figure 1 The royalty management method in the illustrated embodiment.

[0105] In one example, the server may also include a communication interface 303 and a bus 304. Wherein, as... Figure 7 As shown, the processor 301, memory 302, and communication interface 303 are connected through bus 304 and complete communication with each other.

[0106] The communication interface 303 is mainly used to realize communication between various modules, devices, units and / or equipment in the embodiments of this application.

[0107] Bus 304 includes hardware, software, or both, that couples server components together. For example, and not limitingly, the bus may include an Accelerated Graphics Port (AGP) or other graphics bus, an Extended Industry Standard Architecture (EISA) bus, a Front Side Bus (FSB), a Hyper Transport (HT) interconnect, an Industry Standard Architecture (ISA) bus, an Infinite Bandwidth Interconnect, a Low Pin Count (LPC) bus, a memory bus, a Microchannel Architecture (MCA) bus, a Peripheral Component Interconnect (PCI) bus, a PCI-Express (PCI-X) bus, a Serial Advanced Technology Attachment (SATA) bus, a Video Electronics Standards Association Local (VLB) bus, or other suitable buses, or combinations of two or more of these. Where appropriate, bus 304 may include one or more buses. Although specific buses are described and illustrated in embodiments of this application, this application contemplates any suitable bus or interconnect.

[0108] This server can be based on royalty management methods, thereby achieving integration Figures 1-3 Describes the methods for managing royalties.

[0109] Furthermore, in conjunction with the royalty management methods in the above embodiments, this application embodiment can provide a computer storage medium for implementation. The computer storage medium stores computer program instructions; when these computer program instructions are executed by a processor, they implement any of the royalty management methods in the above embodiments.

[0110] This application also provides a computer program product, including a computer program that, when executed by a processor, implements any of the royalty management methods described in the above embodiments.

[0111] It should be clarified that this application is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of this application is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of this application.

[0112] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware, or a combination thereof. When implemented in hardware, they can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this application are programs or code segments used to perform the required tasks. Programs or code segments can be stored on a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried on a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, read-only memory (ROM), flash memory, erasable read-only memory (EROM), floppy disks, compact disc read-only memory (CD-ROM), optical disks, hard disks, fiber optic media, radio frequency (RF) links, etc. Code segments can be downloaded via computer networks such as the Internet, intranets, etc.

[0113] It should also be noted that the exemplary embodiments mentioned in this application describe methods or systems based on a series of steps or apparatus. However, this application is not limited to the order of the above steps; that is, the steps can be performed in the order mentioned in the embodiments, or in a different order, or several steps can be performed simultaneously.

[0114] The aspects of this disclosure have been described above with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this disclosure. It should be understood that each block in the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that these instructions, executable via the processor of the computer or other programmable data processing apparatus, enable the implementation of the functions / actions specified in one or more blocks of the flowchart illustrations and / or block diagrams. Such a processor can be, but is not limited to, a general-purpose processor, a special-purpose processor, a special application processor, or a field-programmable logic circuit. It is also understood that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can also be implemented by special-purpose hardware performing the specified functions or actions, or can be implemented by a combination of special-purpose hardware and computer instructions.

[0115] The above description is merely a specific implementation of this application. Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, modules, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here. It should be understood that the protection scope of this application is not limited thereto. Any person skilled in the art can easily conceive of various equivalent modifications or substitutions within the technical scope disclosed in this application, and these modifications or substitutions should all be covered within the protection scope of this application.

Claims

1. A royalty management method, characterized in that, The method is applied to an off-chain server, and the method includes: Determine the contribution vector of the digital work; wherein the contribution vector includes the addresses of multiple contributors participating in the royalty distribution and the royalty distribution ratio corresponding to each contributor address; Construct the authorization and authentication information package of the digital work based on the contribution vector; The authorization and authentication information package is associated with the media file of the digital work so that the user's terminal can decode the media file and obtain the contribution vector in the authorization and authentication information package.

2. The method according to claim 1, characterized in that, The steps for determining the contribution vector of digital works include: Based on the creation log of the digital work and the blockchain events associated with the digital work, a draft contribution rating for the digital work is generated; wherein, the draft contribution rating includes multiple contributor addresses of the digital work and the royalty distribution ratio corresponding to each contributor address; The draft contribution is submitted to a multi-party signature governance contract deployed on a blockchain network, so that each contributor can sign and confirm the draft contribution through their respective terminal. If the multi-party signature governance contract verifies that the signatures corresponding to all contributor addresses in the contribution draft have been completed, the contribution vector of the digital work is determined based on the contribution draft.

3. The method according to claim 1, characterized in that, The authorization and authentication information package includes the contribution vector of the digital work, the perceptual hash value of the digital work, and the address of the royalty escrow contract for receiving royalty payments.

4. The method according to claim 1, characterized in that, The step of associating the authorization and authentication information package with the media file of the digital work includes: The watermark carrying format of the digital work is determined according to the media file type of the digital work; The authorization and authentication information packet is encoded and modulated to generate watermark data that matches the watermark carrier format; The watermark data is embedded into the corresponding carrying area of ​​the media file of the digital work to complete the association between the authorization and authentication information package and the media file of the digital work.

5. The method according to claim 1, characterized in that, The step of associating the authorization and authentication information package with the media file of the digital work, so that the user's terminal can decode the media file and obtain the contribution vector in the authorization and authentication information package, includes: The authorization and authentication information package is associated with the media file of the digital work so that the user's terminal can decode the media file, obtain the contribution vector and royalty escrow contract address in the authorization and authentication information package, and pay royalties to the royalty escrow contract address to obtain the right to use the digital work.

6. A royalty management method, characterized in that, The method is applied to a node server in a blockchain network, and the method includes: Upon receiving a royalty distribution transaction request, determine the digital work for which royalties are to be distributed and the address of the requesting party; The off-chain decoding service is invoked to obtain the authorization and authentication information package from the media file of the digital work; wherein, the authorization and authentication information package is constructed by the off-chain server based on the contribution vector of the digital work; the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; The address of the request initiator is compared with the addresses of multiple contributors in the authorization and authentication information packet; If the request initiator address exists among the multiple contributor addresses, royalties are allocated to the request initiator address through a royalty escrow contract.

7. The method according to claim 6, characterized in that, The step of allocating royalties to the request initiator's address through a royalty escrow contract includes: Obtain the total escrow royalties of the digital works and the royalty allocation ratio of each contributor's address in the authorization and authentication information package; The royalty share of the request initiator's address is determined based on the royalty allocation ratio of each contributor's address and the total amount of escrowed royalties. The royalty share is transferred to the address of the request initiator through the royalty escrow contract.

8. A royalty management device, characterized in that, The device is used in an off-chain server, and the device includes: A vector determination module is used to determine the contribution vector of a digital work; wherein, the contribution vector includes the addresses of multiple contributors participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; An information construction module is used to construct an authorization and authentication information package for the digital work based on the contribution vector. The information association module is used to associate the authorization and authentication information package with the media file of the digital work, so that the user's terminal can decode the media file and obtain the contribution vector in the authorization and authentication information package.

9. A royalty management device, characterized in that, The device is used as a node server in a blockchain network, and the device includes: The information determination module is used to determine the digital work to be allocated royalties and the address of the requester when a royalty distribution transaction request is received; The service invocation module is used to invoke the off-chain decoding service to obtain the authorization and authentication information package from the media file of the digital work; wherein, the authorization and authentication information package is constructed by the off-chain server based on the contribution vector of the digital work; the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; The address comparison module is used to compare the address of the request initiator with the addresses of multiple contributors in the authorization and authentication information packet; The royalty distribution module is used to distribute royalties to the request initiator address through a royalty escrow contract when the request initiator address exists among the multiple contributor addresses.

10. A royalty management system, characterized in that, The royalty management system includes an off-chain server, a node server, and the user's terminal. The off-chain server is used to determine the contribution vector of the digital work; wherein, the contribution vector includes multiple contributor addresses participating in royalty distribution and the royalty distribution ratio corresponding to each contributor address; The off-chain server is also used to construct an authorization and authentication information package for the digital work based on the contribution vector; The off-chain server is also used to associate the authorization and authentication information package with the media file of the digital work; The user's terminal is used to decode the media file of the digital work, decode the media file, obtain the contribution vector and royalty escrow contract address in the authorization and authentication information package, and pay royalties to the royalty escrow contract address in order to obtain the right to use the digital work. The node server is used to determine the digital work to be allocated royalties and the address of the requester when it receives a royalty distribution transaction request. The node server is also used to call the off-chain decoding service to obtain the authorization and authentication information packet from the media file of the digital work; The node server is also used to compare the address of the request initiator with the addresses of multiple contributors in the authorization and authentication information packet; The node server is also used to distribute royalties to the request initiator address through a royalty escrow contract when the request initiator address exists among the multiple contributor addresses.

11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer program instructions, which, when executed by a processor, implement the royalty management method as described in any one of claims 1-5, or, when executed by a processor, implement the royalty management method as described in any one of claims 6-7.

Images