Data transmission method, system and equipment based on digital rights and interests and storage medium

Abstract

The invention provides a data transmission method, system and device based on digital rights and interests and a storage medium, and the method comprises the steps: generating a corresponding identifier for to-be-transmitted digital rights and interests information sent by user equipment through employing a block chain technology and a hash function; transmitting the digital right information and the identifier through an end-to-end encryption technology; verifying the equipment accessing the digital right information and the identifier through multi-factor authentication and fine-grained authority control; a cross-platform synchronization engine is called to monitor an update event, data synchronization operation of each platform is triggered, and a safe, reliable, transparent and efficient digital right data transmission and management method is provided by combining a block chain, an encryption technology, multi-factor authentication, fine-grained permission control and the cross-platform synchronization engine.

Description

Technical Field

[0001] The present invention relates to the field of big data, and in particular to a data transmission method, system, device and storage medium based on digital rights. Background Art

[0002] With the development of the digital economy, digital rights such as digital currency, virtual goods and copyrighted content have become a key part of user assets.

[0003] However, existing technologies have deficiencies in cross-platform management, data security, ease of operation, unified standard setting, smart contract application, user interface friendliness and synchronization efficiency, which leads to data silos, security risks, complex operations, inconsistent standards, limited applications, unfriendly interfaces and inefficient synchronization when users manage these assets. In addition, the inflexibility and scalability of the technology and the challenges of legal supervision have also exacerbated these problems. Summary of the invention

[0004] The main purpose of the present invention is to provide a data transmission method, system, device and storage medium based on digital rights and interests. By combining blockchain, encryption technology, multi-factor authentication and fine-grained permission control and a cross-platform synchronization engine, a safe, reliable, transparent and efficient digital rights and interests data transmission and management method is provided.

[0005] In order to achieve the above objectives, the embodiments of the present application provide the following technical solutions:

[0006] According to a first aspect of an embodiment of the present application, a data transmission method based on digital rights is provided, the method comprising:

[0007] For the digital rights information to be transmitted sent by the user device, a corresponding identifier is generated using blockchain technology and hash functions;

[0008] The digital rights information and identifiers are transmitted through end-to-end encryption technology;

[0009] Verify the devices that access the digital rights information and identifiers through multi-factor authentication and fine-grained permission control;

[0010] Call the cross-platform synchronization engine to listen for update events and trigger data synchronization operations on each platform.

[0011] Optionally, the transmitting of the digital rights and interests information and the identifier by end-to-end encryption technology includes:

[0012] Encrypting the digital rights and interests information, and storing the encrypted digital rights and interests information in a database, while storing a key for decrypting the data;

[0013] Receive digital rights information access requests initiated by users;

[0014] Retrieving corresponding encrypted data according to the digital rights information access request;

[0015] A decryption operation is performed on the retrieved encrypted data and the identifier, and the decrypted data is sent to the user.

[0016] Optionally, for the digital rights and interests information to be transmitted sent by the user device, a corresponding identifier is generated using blockchain technology and a hash function, including:

[0017] Establish a digital rights identification framework based on blockchain; the digital rights information includes digital currency, digital certificates and digital assets;

[0018] Processing the digital rights and interests information using a hash function, wherein the digital rights and interests information includes the type of rights and interests information, the issuing platform and data of a specific instance;

[0019] Based on the processing results, a unique hash value is generated for each digital equity information as an identifier corresponding to the digital equity information; the identifier is used to verify and track the digital equity information in the blockchain network;

[0020] The identifier is associated with the corresponding digital rights information and stored on the blockchain for subsequent retrieval and verification.

[0021] Optionally, call the cross-platform synchronization engine to listen for update events and trigger data synchronization operations on each platform, including:

[0022] According to the detected update event, extract the version number and content in the data of the update event; the content includes a timestamp; the timestamp is used to identify the last update time of the data;

[0023] Determine the latest status of the data according to the timestamp in the data of the update event;

[0024] If the data is determined to be the latest according to the timestamp, a synchronization operation is triggered;

[0025] The event data, version number and update timestamp are sent to other platforms that need to be synchronized; the cross-platform synchronization engine is deployed on at least two different platforms to achieve real-time synchronization of data.

[0026] Optionally, the method further comprises:

[0027] After receiving the data update request, the other platforms that need to be synchronized compare the local data with the event data, version number and update timestamp carried in the data update request;

[0028] If the local data update timestamp is earlier than or the version number is lower than the data in the request, the update is accepted and the local data is updated;

[0029] If the local data update timestamp is later than or the version number is higher than the data in the request, the update is rejected or handled according to the conflict resolution strategy.

[0030] Optionally, it also includes:

[0031] Write and test smart contract code, compile smart contracts and deploy them to the blockchain network;

[0032] Set up a smart contract monitoring mechanism to monitor specific events or conditions;

[0033] When a preset event or condition is triggered, the smart contract automatically executes according to the programmed logic;

[0034] After execution is completed, the smart contract generates an execution result, which includes a state change and / or data writing;

[0035] Update the smart contract status based on the execution results and record the update on the blockchain;

[0036] The execution results and update status are fed back to the user through the user interface, allowing the user to view the execution results and the current status of the contract.

[0037] Optionally, the multi-factor authentication includes a password, biometrics, a smart card, or a one-time password; and verifying the device accessing the digital equity information and identifier through multi-factor authentication and fine-grained permission control includes:

[0038] Based on the user's identity and permission level, the system controls the user's access to digital rights information and identifiers;

[0039] Allow or deny the user's operation request based on the user's identity authentication and permission control results;

[0040] If the user is verified and has the corresponding authority, the user is allowed to access the digital rights information and identifier;

[0041] If user access is denied, the reason for the denial will be fed back to the user's device.

[0042] According to a second aspect of an embodiment of the present application, a digital rights-based data transmission system is provided, the system comprising:

[0043] An identifier module, used to generate a corresponding identifier for the digital rights information to be transmitted sent by the user device using blockchain technology and hash functions;

[0044] An encryption transmission module, used to transmit the digital rights and interests information and identifiers through end-to-end encryption technology;

[0045] A verification module, used to verify the device accessing the digital equity information and identifier through multi-factor authentication and fine-grained permission control;

[0046] The monitoring module is used to call the cross-platform synchronization engine to monitor update events and trigger data synchronization operations on each platform.

[0047] According to a third aspect of an embodiment of the present application, an electronic device is provided, comprising: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method described in the first aspect above.

[0048] According to a fourth aspect of an embodiment of the present application, a computer-readable storage medium is provided, on which computer-readable instructions are stored. The computer-readable instructions can be executed by a processor to implement the method described in the first aspect above.

[0049] In summary, the embodiments of the present application provide a data transmission method, system, device and storage medium based on digital rights and interests, which generates a corresponding identifier by using blockchain technology and hash function for the digital rights and interests information to be transmitted sent by the user device; transmits the digital rights and interests information and identifiers through end-to-end encryption technology; verifies the device accessing the digital rights and interests information and identifiers through multi-factor authentication and fine-grained permission control; calls a cross-platform synchronization engine to listen to update events and triggers data synchronization operations on each platform. By combining blockchain, encryption technology, multi-factor authentication and fine-grained permission control as well as a cross-platform synchronization engine, a safe, reliable, transparent and efficient method for transmitting and managing digital rights and interests data is provided. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the structures shown in these drawings without paying creative work.

[0051] The structures, proportions, sizes, etc. illustrated in this specification are only used to match the contents disclosed in the specification so as to facilitate understanding and reading by persons familiar with the technology. They are not used to limit the conditions under which the present invention can be implemented, and therefore have no substantial technical significance. Any structural modification, change in proportion or adjustment of size shall still fall within the scope of the technical contents disclosed in the present invention without affecting the effects and purposes that can be achieved by the present invention.

[0052] Figure 1 A schematic diagram of a data transmission method based on digital rights provided in an embodiment of the present application;

[0053] Figure 2 A flowchart of the digital rights identification system identification generation and storage provided in the embodiment of the present application;

[0054] Figure 3 A flowchart of a digital rights identification search provided in an embodiment of the present application;

[0055] Figure 4 A flowchart of the retrieval and decryption workflow of the encrypted storage mechanism provided in the embodiment of the present application;

[0056] Figure 5 A flowchart of data encryption and storage of the encryption storage mechanism provided in an embodiment of the present application;

[0057] Figure 6 A schematic diagram of the architecture and operation steps of a cross-platform synchronization engine provided in an embodiment of the present application;

[0058] Figure 7 A flow chart of the deployment and execution of the smart contract framework provided for the embodiment of the present application;

[0059] Figure 8 A schematic diagram of the design layout of the user interface (UI) provided in an embodiment of the present application;

[0060] Fig. 9 A flowchart of the security verification and authorization mechanism provided for the embodiment of the present application;

[0061] Fig.10 A flow chart of a data synchronization and conflict resolution strategy provided in an embodiment of the present application;

[0062] Fig.11 A framework diagram of legal compliance support provided for embodiments of the present application;

[0063] Fig.12 A system architecture diagram for the scalability and compatibility design provided by the embodiments of the present application;

[0064] Fig.13 A block diagram of a digital rights-based data transmission system provided in an embodiment of the present application;

[0065] Fig.14 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application is shown;

[0066] Fig.15 A schematic diagram of a computer-readable storage medium provided in an embodiment of the present application is shown.

[0067] The realization of the purpose, functional features and advantages of the present invention will be further explained in conjunction with embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION

[0068] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0069] It should be noted that all directional indications in the embodiments of the present invention (such as up, down, left, right, front, back, etc.) are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0070] In addition, in the present invention, descriptions such as "first", "second", etc. are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" or "second" may explicitly or implicitly include at least one of the features. In the description of the present invention, the meaning of "plurality" is at least two, such as two, three, etc., unless otherwise clearly and specifically defined.

[0071] In the present invention, unless otherwise clearly specified and limited, the terms "connection", "fixation", etc. should be understood in a broad sense. For example, "fixation" can be a fixed connection, a detachable connection, or an integral connection; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, it can be the internal connection of two elements or the interaction relationship between two elements, unless otherwise clearly defined. For ordinary technicians in this field, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0072] In addition, the technical solutions between the various embodiments of the present invention can be combined with each other, but it must be based on the fact that ordinary technicians in the field can implement it. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such combination of technical solutions does not exist and is not within the scope of protection required by the present invention.

[0073] Existing technologies have the following deficiencies in cross-platform management and synchronization:

[0074] 1. Data island problem: The data between platforms are not interconnected, forming data islands, which makes it impossible for users to conveniently manage and synchronize their digital rights between different platforms.

[0075] 2. Security issues: Existing technologies often lack adequate security measures in the storage and transmission of rights and interests information, making them vulnerable to hacker attacks and data leaks.

[0076] 3. Operational complexity: When users transfer and manage digital rights between different platforms, they need to perform complex operations, which not only increases the user's learning cost but also reduces management efficiency.

[0077] 4. Lack of unified standards: There is currently a lack of unified digital rights management standards. The rights formats and protocols between different platforms are incompatible, which increases the difficulty of cross-platform operations. The lack of an effective synchronization mechanism makes the synchronization of digital rights between different platforms cumbersome and prone to errors.

[0078] 5. Limited application of smart contracts: Although smart contracts in blockchain technology provide the possibility for automated equity management, the application scope of smart contracts in existing technologies is limited and their potential has not been fully realized.

[0079] 6. Unfriendly user interface: The existing digital rights management interface is often complex in design, making it difficult for users to quickly get started, which affects the user experience.

[0080] 7. Low synchronization efficiency: The current synchronization mechanism is mostly manual operation and lacks automated synchronization function, resulting in low efficiency of equity synchronization and failure to meet user needs.

[0081] 8. Lack of flexibility and scalability: Existing technologies are often designed for specific types of digital rights and interests, lack flexibility and scalability, and are difficult to adapt to changing market demands.

[0082] 9. Legal and regulatory challenges: As digital rights become more diverse, the existing legal and regulatory framework may fail to fully cover all types of rights, leading to management uncertainties.

[0083] In order to overcome the above defects and shortcomings, the present invention proposes a cross-platform management and synchronization technology of digital rights, aiming to provide a safe, efficient and user-friendly solution to meet the needs of the digital economy era.

[0084] Figure 1 The digital rights-based data transmission method provided in an embodiment of the present application is shown, and the method includes:

[0085] Step 101: Generate a corresponding identifier for the digital rights information to be transmitted sent by the user device using blockchain technology and hash function;

[0086] Step 102: Transmitting the digital rights information and identifier through end-to-end encryption technology;

[0087] Step 103: Verify the device accessing the digital rights information and identifier through multi-factor authentication and fine-grained permission control;

[0088] Step 104: Call the cross-platform synchronization engine to listen to update events and trigger data synchronization operations on each platform.

[0089] In a possible implementation, the transmission of the digital rights information and the identifier by using end-to-end encryption technology includes:

[0090] The digital rights information is encrypted and stored in a database, and a key for decrypting the data is stored at the same time; a request for access to the digital rights information initiated by a user is received; corresponding encrypted data is retrieved according to the request for access to the digital rights information; the retrieved encrypted data and the identifier are decrypted, and the decrypted data is sent to the user.

[0091] In a possible implementation, for the digital rights information to be transmitted sent by the user device, a corresponding identifier is generated using blockchain technology and a hash function, including:

[0092] Establish a digital rights identification framework based on blockchain; the digital rights information includes digital currency, digital certificates and digital assets; use a hash function to process the digital rights information, the digital rights information includes the type of rights information, the issuance platform and the data of the specific instance; based on the processing result, generate a unique hash value for each digital rights information as the identifier corresponding to the digital rights information; the identifier is used to verify and track the digital rights information in the blockchain network; the identifier is associated with the corresponding digital rights information and stored on the blockchain for subsequent retrieval and verification.

[0093] In a possible implementation, calling a cross-platform synchronization engine to listen to update events and triggering data synchronization operations on each platform includes:

[0094] Based on the detection of an update event, the version number and content in the data of the update event are extracted; the content includes a timestamp; the timestamp is used to identify the last update time of the data; the latest status of the data is determined based on the timestamp in the data of the update event; if the data is determined to be the latest based on the timestamp, a synchronization operation is triggered; the event data, version number and update timestamp are sent to other platforms that need to be synchronized; the cross-platform synchronization engine is deployed on at least two different platforms to achieve real-time synchronization of data.

[0095] In a possible implementation, the method further includes: after receiving the data update request, the other platforms that need to be synchronized compare the local data with the event data, version number and update timestamp carried in the data update request; if the local data update timestamp is earlier than or the version number is lower than the data in the request, the update is accepted and the local data is updated; if the local data update timestamp is later than or the version number is higher than the data in the request, the update is rejected or processed according to the conflict resolution strategy.

[0096] In a possible implementation, it also includes: writing and testing smart contract code, compiling the smart contract and deploying it to the blockchain network; setting a smart contract monitoring mechanism to monitor specific events or conditions; when a preset event or condition is triggered, the smart contract automatically executes according to the written logic; after execution, the smart contract generates an execution result, and the execution result includes a state change and / or data writing; updating the smart contract status according to the execution result, and recording the update on the blockchain; feeding back the execution result and the updated status to the user through the user interface, so that the user can view the execution result and the current status of the contract.

[0097] In a possible implementation, the multi-factor authentication includes a password, biometrics, a smart card, or a one-time password; through multi-factor authentication and fine-grained permission control, the device accessing the digital rights information and identifier is verified, including: according to the user's identity and permission level, the system controls the user's access to the digital rights information and identifier; according to the user's identity authentication and permission control results, the user's operation request is allowed or denied; if the user passes the verification and has the corresponding permission, the user is allowed to access the digital rights information and identifier; if the user's access is denied, the rejection reason is fed back to the user's device.

[0098] The method provided in the embodiments of the present application is described in detail below.

[0099] Phase 1: Establish a digital rights identification system.

[0100] Define a unified digital rights identification framework to assign unique identifiers to different types of rights. The identifier adopts a hierarchical structure, including the base layer (such as the right type T), the middle layer (such as the issuance platform P) and the application layer (such as the specific right instance I).

[0101] Blockchain technology is used to generate an unalterable hash value to ensure the uniqueness and security of the equity identification. Assuming that the identifier of each digital equity is composed of the equity type T, the issuing platform P and the specific instance I, the identifier can be expressed as:

[0102] Identifier=H(T∣∣P∣∣I)

[0103] Among them, H is a hash function and ||||||| represents the concatenation of data.

[0104] A unique identifier is generated using the hash function H to ensure that each digital right is unique globally.

[0105] Further, the generated identifiers are stored in a distributed database to ensure data persistence and accessibility.

[0106] Figure 2 The process of generating and storing the digital rights identification system provided in the embodiment of the present application is shown, which specifically includes the following steps:

[0107] Step 1: User submits rights and interests information: The user submits the rights and interests information that he or she wishes to be identified to the identification generation module of the system.

[0108] Step 2: After receiving the rights and interests information submitted by the user, the identification generation module uses a specific algorithm (such as a hash function) to generate a unique identifier. The hash function is used to process it to ensure its uniqueness and security.

[0109] Step 3: Encrypt the identifier to protect the privacy and security of the information.

[0110] Step 4: Store the encrypted digital equity identifier in a distributed database. This storage method can improve data reliability and access speed.

[0111] Figure 3 The digital rights identification retrieval process provided by this application is shown, which specifically includes the following steps:

[0112] Step 1: Retrieval module: The system provides a retrieval module that allows users or other system components to retrieve equity information as needed, so that users can send retrieval requests.

[0113] Step 2: Retrieval identifier: When it is necessary to retrieve rights information, a user or other system component can query by entering a retrieval identifier.

[0114] Step 3: Data Decryption: The retrieved equity information may need to be decrypted before output to ensure that only authorized users can access the original data.

[0115] Step 4: The system outputs the retrieved rights information to the requester.

[0116] The entire process ensures the security, uniqueness and retrievability of rights and interests information, while using a distributed database to improve the scalability and stability of the system.

[0117] Phase 2: Implementing encrypted storage mechanism.

[0118] Implement end-to-end encryption to ensure the security of equity information during transmission. Use distributed storage solutions such as IPFS (InterPlanetary File System) to improve data persistence and anti-attack capabilities. Design an encryption key management system to ensure that only authorized users can access their digital equity information.

[0119] Data encryption can be expressed as: EncryptedData = E(PlainText, Key).

[0120] Among them, E is the encryption function, PlainText is the plaintext data, and Key is the encryption key.

[0121] This stage includes the following processes:

[0122] Step 1: The user initiates a request to the system to access or manipulate certain data.

[0123] Step 2: The system receives the user's data, which may be the original data submitted by the user.

[0124] Step 3: Before data storage, the system encrypts user data using an encryption algorithm to ensure data security and privacy.

[0125] Step 4: The encrypted data is stored securely, usually on a server or in cloud storage.

[0126] Step 5: The system provides a key management service to generate, store and manage the keys used in the encryption process. These keys are essential for encryption and decryption of data.

[0127] Step 6: When the user needs to access the stored data, the system retrieves the corresponding encrypted data based on the user's request.

[0128] Step 7: Before the retrieved encrypted data is provided to the user, it needs to be decrypted using the corresponding key in the key management service to restore the original data.

[0129] The entire process ensures the security of data during storage and transmission, and controls access to data through key management services to prevent unauthorized access. This mechanism is a common practice in modern data protection and privacy protection.

[0130] Figure 4 The retrieval and decryption workflow of the encrypted storage mechanism is shown, and the specific steps are as follows:

[0131] Step 1: The user initiates a request to access data.

[0132] Step 2: The system retrieves the corresponding data based on the request.

[0133] Step 3: Decrypt the retrieved encrypted data.

[0134] Step 4: The decrypted data is provided to the user.

[0135] Figure 5 The data encryption and storage process of the encrypted storage mechanism is shown, and the specific steps are as follows:

[0136] Step 1: Users generate or provide raw data.

[0137] Step 2: Encrypt user data to ensure data security.

[0138] Step 3: Store the encrypted data in a secure location.

[0139] Step 4: Manage and protect the keys used to decrypt the data.

[0140] Phase 3: Cross-platform synchronization engine.

[0141] Develop a central synchronization engine that can listen to update events from different platforms and trigger synchronization operations, responsible for coordinating data synchronization between different platforms.

[0142] Implement API interface to allow third-party platforms to easily integrate the synchronization engine and realize real-time data update. Design RESTful API to allow third-party platforms to synchronize data through standard HTTP requests.

[0143] The message queue and event-driven architecture are used to ensure the efficiency and reliability of synchronization operations.

[0144] The data synchronization of the synchronization engine can use the timestamp Ts to mark the last update time of the data:

[0145] SyncData = {D, Ts}

[0146] Where D is the data content and Ts is the timestamp of the data.

[0147] Figure 6 The architecture and operation steps of the cross-platform synchronization engine are shown as follows:

[0148] User interface: As the entry point for users to interact with the system, users can trigger synchronization operations through it.

[0149] API Gateway: Serves as an interface for the system to communicate with external third-party services and processes requests from third-party services.

[0150] Third-party services: interact with the synchronization engine through the API gateway and participate in cross-platform data synchronization.

[0151] Synchronization engine: As the core of the synchronization mechanism, it is responsible for coordinating the data synchronization process.

[0152] Data management component: manages data requests from local and remote databases to ensure data consistency and integrity.

[0153] Local database: stores local data and participates in data synchronization.

[0154] Remote database: stores remote data and participates in data synchronization.

[0155] Data synchronization component: performs actual data synchronization operations to ensure that the data in the local and remote databases are consistent.

[0156] Data update component: After data synchronization is completed, it updates the local database and notifies the user interface of the synchronization results.

[0157] Synchronization result notification: After the user interface receives the notification from the data update component, it displays the synchronization result to the user.

[0158] Phase 4: Smart Contract Framework:

[0159] 1. Contract deployment:

[0160] Deploy smart contracts on the blockchain platform to automate the creation and transfer of rights. Design a blockchain-based smart contract framework to automate the creation, transfer, and destruction of rights. Smart contracts support custom logic to adapt to different types of digital rights and transaction rules.

[0161] 2. Contract Execution:

[0162] Smart contracts are automatically executed according to predefined logic, ensuring the transparency and immutability of transactions. Smart contracts are auditable and upgradable to adapt to future legal and market changes.

[0163] The execution of a smart contract can be expressed as: ContractExecution = {C, P, R}.

[0164] Among them, C is the contract code, P is the contract parameter, and R is the execution result.

[0165] Figure 7 The deployment and execution process of the smart contract framework is demonstrated, including:

[0166] Step 1: Smart Contract Development: Developers write and test the smart contract code. Developers write the smart contract code and test it to ensure that the contract logic is correct.

[0167] Step 2: Contract deployment: After development is completed, the smart contract needs to be compiled and then deployed to the blockchain network.

[0168] Step 3: Blockchain network: The smart contract is deployed to the blockchain and becomes part of the network, accessible and executable by nodes in the network. The deployed smart contract becomes part of the blockchain network and can be accessed and executed by nodes in the network.

[0169] Step 4: Monitor events: Smart contracts can be set to monitor specific events or conditions. When these conditions are met, the contract will be triggered to execute. Smart contracts set up monitoring mechanisms to wait for specific events or conditions to occur.

[0170] Step 5: When an event is triggered, the smart contract automatically executes according to the preset logic. When a preset event or condition is triggered, the smart contract automatically executes according to the programmed logic.

[0171] Step 6: After the smart contract is executed, an execution result will be generated, which may be a change in state, data writing, or other operations. After the smart contract is executed, an execution result will be generated, which may include a change in state, data writing, or other predetermined operations.

[0172] Step 7: The execution results in the state of the smart contract being updated, and these updates will be recorded on the blockchain. The execution results in the state of the smart contract being updated, and these changes will be recorded and confirmed by the blockchain network.

[0173] Step 8: The smart contract status update is fed back to the user interface, allowing users to view the execution results and current status of the contract. The smart contract status update is fed back to the user through the user interface, allowing users to view the execution results and current status of the smart contract.

[0174] Phase 5: User Interface (UI) Design:

[0175] Design an intuitive and responsive user interface that supports multi-platform access, including desktop and mobile devices, to display users' digital rights and operation options. Provide clear rights display, including information such as right type, status, and history. Implement user-friendly operation processes to simplify the process of rights management, transfer, and synchronization. Implement intuitive interaction methods such as drag and drop and click, so that users can easily manage their rights. The response time of the user interface can be expressed as:

[0176] ResponseTime=(EndTime-StartTime) / UserActions

[0177] Among them, EndTime and StartTime are the end and start times of the user operation respectively.

[0178] Figure 8 The design layout of the user interface (UI) is shown, including rights display and operation options.

[0179] User login interface: Design a secure and user-friendly login interface to ensure that users can log in easily. The main page includes an operation option bar and a rights display area:

[0180] The Operation Options bar includes:

[0181] 1. Add benefit form: allows users to add new benefits.

[0182] 2. Equity transfer interface: allows users to transfer existing equity.

[0183] 3. Equity synchronization interface: displays the status and history of equity synchronization, allowing users to view the update records of equity.

[0184] 4. Settings interface: Allow users to adjust interface settings, such as theme color, font size, etc.

[0185] Benefits display area: displays all the benefits that the user currently owns. Each benefit is presented in the form of a card, containing key information such as benefit type and status.

[0186] 1. Add benefit form: allows users to add new benefits.

[0187] 2. Benefit details: After clicking the benefit card, more detailed benefit information will be displayed, such as history records, usage conditions, etc.

[0188] Finally, conduct user testing, collect feedback, and make iterative improvements based on that feedback to ensure that the final user interface is both intuitive and efficient.

[0189] Phase 6: Security verification and authorization mechanism:

[0190] 1. Multi-factor authentication: Implement a multi-factor authentication system that combines multiple authentication methods such as passwords, mobile phone verification codes, and biometrics.

[0191] 2. Permission control: Design a fine-grained permission control system to allow users to assign different levels of access rights as needed.

[0192] Regular security audits and vulnerability scans are used to ensure the security of the system. The success rate of security verification can be expressed as:

[0193] SuccessRate=SuccessfulAuthentications / TotalAuthentications×100%

[0194] Fig. 9 The process of security verification and authorization mechanism is demonstrated, including multi-factor authentication and permission control.

[0195] Step 1: User login request: The request made when a user tries to log in to the system.

[0196] Step 2: Authentication: The system first performs basic authentication, and the user needs to enter a username and password.

[0197] Step 3: Password Verification: The system verifies whether the entered username and password are correct. If the verification fails, the user will be prompted that the login failed. If the verification succeeds, the process enters the multi-factor authentication stage.

[0198] Step 4: Multi-factor authentication: To increase security, the system requires users to perform multi-factor authentication.

[0199] Step 5: Mobile phone / email verification: Users can verify by receiving a verification code via SMS or email.

[0200] Step 6: Fingerprint / Facial Recognition: Users can also use biometrics for authentication.

[0201] Step 7: Permission control: After multi-factor authentication is successful, the system controls the user based on their identity and permission level.

[0202] Step 8: High-privilege users: can access all functions of the system.

[0203] Step 9: Ordinary users: can only access some functions.

[0204] Step 10: Guest User: Can only access restricted functions.

[0205] Step 11: User operation: According to the permission level, the user can perform corresponding operations.

[0206] Phase 7: Data synchronization and conflict resolution strategy:

[0207] 1. Synchronization algorithm: Implement a timestamp-based synchronization algorithm to ensure data consistency and integrity.

[0208] 2. Conflict resolution: Design conflict detection and resolution mechanisms, such as “last write wins” or “version vector” strategies, to handle data inconsistencies.

[0209] Provide data backup and recovery functions to deal with possible data loss or damage. The conflict resolution strategy can be determined based on the version number V: ResolvedData = Datawithmax(V).

[0210] Fig.10 The process of data synchronization and conflict resolution strategy is presented, including synchronization algorithm and conflict resolution, which specifically includes the following steps:

[0211] Step 1: Start synchronization: Trigger the starting point of the data synchronization process.

[0212] Step 2: Check data updates: The system checks whether there are any data updates since the last synchronization. If there are no updates, the synchronization is completed directly. If there are updates, the data version check is started.

[0213] Step 3: Data version check: The system compares the version numbers of local data and remote data. If the versions are consistent, the data is synchronized directly. If the versions are inconsistent, conflict detection is performed.

[0214] Step 4: Conflict detection: The system detects whether there is a data conflict. If there is no conflict, continue to synchronize data. If there is a conflict, enter the conflict resolution strategy.

[0215] Step 5: Conflict resolution strategy: Depending on the type of conflict, the system selects different resolution strategies.

[0216] Step 6: Select the latest data: Select the latest version of data to synchronize.

[0217] Step 7: Select Merge Data: Merge different versions of data.

[0218] Step 8: Other strategies: Execute other predefined conflict resolution strategies.

[0219] Step 9: Synchronize the latest data / merge data / execute other strategies: Based on the selected strategy, the system performs corresponding operations.

[0220] Step 10: Synchronization Completed: After data synchronization and conflicts are resolved, the synchronization process is complete.

[0221] Phase 8: Legal compliance support:

[0222] 1. Compliance Check: Work with legal experts to ensure that technical solutions comply with international and regional data protection regulations. Provide legal compliance check tools to help users and platforms self-assess compliance.

[0223] 2. Compliance Guide: Regularly update the legal compliance guide to adapt to changes in the legal environment. Legal compliance checks can be expressed as:

[0224]

[0225] Where wi is the weight of the i-th compliance criterion and ci is the compliance score of that criterion.

[0226] Fig.11 The framework for legal compliance support is presented, including compliance checks and guidance updates, including:

[0227] Step 1: Start compliance support: Trigger the starting point of the legal compliance support process.

[0228] Step 2: Compliance Check: The system checks whether its operation complies with current laws and regulations regularly or after specific events.

[0229] Step 3: Compliance Status: After the inspection, determine the compliance status. If compliant, continue normal operations. If not compliant, identify the issues.

[0230] Step 4: Identify the issue: Identify the specific issue or area that is causing the noncompliance.

[0231] Step 5: Update guidance: Based on the issues identified, decide whether the legal compliance guidance needs to be updated.

[0232] Step 6: Update legal compliance guidance: Make necessary updates to the guidance to ensure compliance.

[0233] Step 7: Recheck compliance: After updating the guidelines, recheck compliance.

[0234] Step 8: Regular checks: To ensure continuous compliance, the system will perform regular compliance checks.

[0235] Phase 9: Scalability and compatibility design:

[0236] 1. Modular architecture: Design a modular system architecture that supports easy addition of new equity types and platform integration.

[0237] 2. Standardized API: Implement standardized API to improve compatibility with other systems.

[0238] Adopt containerization and microservice architecture to support rapid iteration and expansion of technology. The compatibility score of the system can be expressed as:

[0239] CompatibilityScore=TotalPlatforms / SupportedPlatforms×100%

[0240] Fig.12 Demonstrates a system architecture designed for scalability and compatibility, including modular design and standardized APIs.

[0241] System entry: The starting point for user or system access, which can be a web interface, mobile application or other interface.

[0242] Core service: The main service component of the system, responsible for coordinating and managing various modular components.

[0243] Modular components: The system is designed as multiple modular components, each responsible for a specific function or service.

[0244] Modular component 1, modular component 2, modular component 3: represent different functional modules of the system.

[0245] Submodules: Each modular component can be further broken down into submodules to improve flexibility and maintainability.

[0246] Standardized APIs: The system communicates with external services or third-party integrations through standardized APIs.

[0247] Third-party integration: Through standardized APIs, the system can be integrated with various third-party services.

[0248] Third-party services: represent various external services or applications that integrate with the system through APIs.

[0249] In summary, the embodiments of the present application provide a data transmission method based on digital rights and interests, which generates a corresponding identifier by using blockchain technology and hash function for the digital rights and interests information to be transmitted sent by the user device; transmits the digital rights and interests information and identifiers through end-to-end encryption technology; verifies the devices that access the digital rights and interests information and identifiers through multi-factor authentication and fine-grained permission control; calls a cross-platform synchronization engine to listen to update events and triggers data synchronization operations on each platform. By combining blockchain, encryption technology, multi-factor authentication and fine-grained permission control as well as a cross-platform synchronization engine, a safe, reliable, transparent and efficient method for transmitting and managing digital rights and interests data is provided.

[0250] Based on the same technical concept, the embodiment of the present application also provides a data transmission system based on digital rights, such as Fig.13 As shown, the system comprises:

[0251] The identifier module 1301 is used to generate a corresponding identifier for the digital rights and interests information to be transmitted sent by the user equipment using the blockchain technology and the hash function;

[0252] An encryption transmission module 1302, used to transmit the digital rights and interests information and identifiers through end-to-end encryption technology;

[0253] Verification module 1303, used to verify the device accessing the digital rights information and identifier through multi-factor authentication and fine-grained permission control;

[0254] The monitoring module 1304 is used to call the cross-platform synchronization engine to monitor update events and trigger data synchronization operations on each platform.

[0255] The present application also provides an electronic device corresponding to the method provided in the above embodiment. Fig.14 , which shows a schematic diagram of an electronic device provided by some embodiments of the present application. The electronic device 20 may include: a processor 200, a memory 201, a bus 202 and a communication interface 203, wherein the processor 200, the communication interface 203 and the memory 201 are connected via the bus 202; the memory 201 stores a computer program that can be run on the processor 200, and the processor 200 executes the method provided by any of the aforementioned embodiments of the present application when running the computer program.

[0256] The memory 201 may include a high-speed random access memory (RAM), and may also include a non-volatile memory, such as at least one disk memory. The communication connection between the system network element and at least one other network element is realized through at least one physical port (which may be wired or wireless), and the Internet, wide area network, local area network, metropolitan area network, etc. may be used.

[0257] The bus 202 may be an ISA bus, a PCI bus, or an EISA bus, etc. The bus may be divided into an address bus, a data bus, a control bus, etc. The memory 201 is used to store programs, and the processor 200 executes the programs after receiving execution instructions. The method disclosed in any implementation of the aforementioned embodiment of the present application may be applied to the processor 200, or implemented by the processor 200.

[0258] The processor 200 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the hardware integrated logic circuit or software instructions in the processor 200. The above processor 200 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a readily available programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components. The methods, steps and logic block diagrams disclosed in the embodiments of the present application can be implemented or executed. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor, etc. The steps of the method disclosed in the embodiments of the present application can be directly embodied as a hardware decoding processor to be executed, or the hardware and software modules in the decoding processor can be executed. The software module can be located in a mature storage medium in the field such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 201, and the processor 200 reads the information in the memory 201 and completes the steps of the above method in combination with its hardware.

[0259] The electronic device provided in the embodiment of the present application and the method provided in the embodiment of the present application are based on the same inventive concept and have the same beneficial effects as the method adopted, operated or implemented by them.

[0260] The present application also provides a computer-readable storage medium corresponding to the method provided in the above embodiment. Fig.15 The computer-readable storage medium shown is a CD 30 on which a computer program (ie, a program product) is stored. When the computer program is run by a processor, the method provided in any of the aforementioned embodiments is executed.

[0261] It should be noted that examples of the computer-readable storage medium may also include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other optical or magnetic storage media, which are not listed here one by one.

[0262] The computer-readable storage medium provided in the above-mentioned embodiments of the present application and the method provided in the embodiments of the present application are based on the same inventive concept and have the same beneficial effects as the method adopted, run or implemented by the application program stored therein.

[0263] It should be noted that:

[0264] The algorithm and display provided herein are not inherently related to any particular computer, virtual device or other equipment. Various general purpose devices can also be used together with the teachings based on this. According to the above description, it is obvious to construct the structure required for this type of device. In addition, the application is not directed to any specific programming language. It should be understood that the content of the application described herein can be realized using various programming languages, and the description of the specific language above is to disclose the best mode of implementation of the application.

[0265] In the description provided herein, a large number of specific details are described. However, it is understood that the embodiments of the present application can be practiced without these specific details. In some instances, well-known methods, structures and techniques are not shown in detail so as not to obscure the understanding of this description.

[0266] Similarly, it should be understood that in order to streamline the present application and help understand one or more of the various inventive aspects, in the above description of the exemplary embodiments of the present application, the various features of the present application are sometimes grouped together into a single embodiment, figure, or description thereof. However, the disclosed method should not be interpreted as reflecting the following intention: the claimed application requires more features than the features clearly stated in each claim. More specifically, as reflected in the claims below, the inventive aspects are less than all the features of the single embodiment disclosed above. Therefore, the claims following the specific embodiment are hereby expressly incorporated into the specific embodiment, wherein each claim itself serves as a separate embodiment of the present application.

[0267] Those skilled in the art will appreciate that the modules in the devices in the embodiments may be adaptively changed and arranged in one or more devices different from the embodiments. The modules or units or components in the embodiments may be combined into one module or unit or component, and in addition they may be divided into a plurality of submodules or subunits or subcomponents. Except that at least some of such features and / or processes or units are mutually exclusive, all features disclosed in this specification (including the accompanying claims, abstracts and drawings) and all processes or units of any method or device disclosed in this manner may be combined in any combination. Unless otherwise expressly stated, each feature disclosed in this specification (including the accompanying claims, abstracts and drawings) may be replaced by an alternative feature providing the same, equivalent or similar purpose.

[0268] In addition, those skilled in the art will appreciate that, although some embodiments described herein include certain features included in other embodiments but not other features, the combination of features of different embodiments is meant to be within the scope of the present application and form different embodiments. For example, in the claims below, any one of the claimed embodiments may be used in any combination.

[0269] The various component embodiments of the present application can be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. It should be understood by those skilled in the art that a microprocessor or digital signal processor (DSP) can be used in practice to implement some or all functions of some or all components in the creation device of the virtual machine according to the embodiment of the present application. The application can also be implemented as a device or device program (e.g., computer program and computer program product) for executing part or all of the methods described herein. Such a program implementing the present application can be stored on a computer-readable medium, or can have the form of one or more signals. Such a signal can be downloaded from an Internet website, or provided on a carrier signal, or provided in any other form.

[0270] It should be noted that the above embodiments illustrate the present application rather than limit the present application, and that those skilled in the art may design alternative embodiments without departing from the scope of the appended claims. In the claims, any reference symbol between brackets should not be constructed as a limitation to the claims. The word "comprising" does not exclude the presence of elements or steps not listed in the claims. The word "one" or "an" preceding an element does not exclude the presence of multiple such elements. The present application may be implemented by means of hardware including several different elements and by means of a suitably programmed computer. In a unit claim that lists several devices, several of these devices may be embodied by the same hardware item. The use of the words first, second, and third, etc. does not indicate any order. These words may be interpreted as names.

[0271] The above is only a preferred specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by a person skilled in the art within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

[0272] The above description is only a preferred embodiment of the present invention, and does not limit the patent scope of the present invention. All equivalent structural changes made by using the contents of the present invention specification and drawings under the concept of the present invention, or directly / indirectly applied in other related technical fields are included in the patent protection scope of the present invention.

Claims

1. A data transmission method based on digital rights, characterized in that: The method comprises: For the digital rights information to be transmitted sent by the user device, a corresponding identifier is generated using blockchain technology and hash functions; The digital rights information and identifiers are transmitted through end-to-end encryption technology; Verify the devices that access the digital rights information and identifiers through multi-factor authentication and fine-grained permission control; Call the cross-platform synchronization engine to listen for update events and trigger data synchronization operations on each platform.

2. The method according to claim 1, characterized in that The transmission of the digital rights information and identifier by end-to-end encryption technology includes: Encrypting the digital rights and interests information, and storing the encrypted digital rights and interests information in a database, while storing a key for decrypting the data; Receive digital rights information access requests initiated by users; Retrieving corresponding encrypted data according to the digital rights information access request; A decryption operation is performed on the retrieved encrypted data and the identifier, and the decrypted data is sent to the user.

3. The method according to claim 1, characterized in that For the digital rights information to be transmitted sent by the user device, the corresponding identifier is generated using blockchain technology and hash functions, including: Establish a digital rights identification framework based on blockchain; the digital rights information includes digital currency, digital certificates and digital assets; Processing the digital rights and interests information using a hash function, wherein the digital rights and interests information includes the type of rights and interests information, the issuing platform and data of a specific instance; Based on the processing results, a unique hash value is generated for each digital equity information as an identifier corresponding to the digital equity information; the identifier is used to verify and track the digital equity information in the blockchain network; The identifier is associated with the corresponding digital rights information and stored on the blockchain for subsequent retrieval and verification.

4. The method according to claim 1, characterized in that Call the cross-platform synchronization engine to listen for update events and trigger data synchronization operations on each platform, including: According to the detected update event, extract the version number and content in the data of the update event; the content includes a timestamp; the timestamp is used to identify the last update time of the data; Determine the latest status of the data according to the timestamp in the data of the update event; If the data is determined to be the latest according to the timestamp, a synchronization operation is triggered; The event data, version number and update timestamp are sent to other platforms that need to be synchronized; the cross-platform synchronization engine is deployed on at least two different platforms to achieve real-time synchronization of data.

5. The method according to claim 4, characterized in that The method further comprises: After receiving the data update request, the other platforms that need to be synchronized compare the local data with the event data, version number and update timestamp carried in the data update request; If the local data update timestamp is earlier than or the version number is lower than the data in the request, the update is accepted and the local data is updated; If the local data update timestamp is later than or the version number is higher than the data in the request, the update is rejected or handled according to the conflict resolution strategy.

6. The method according to claim 1, characterized in that Also includes: Write and test smart contract code, compile smart contracts and deploy them to the blockchain network; Set up a smart contract monitoring mechanism to monitor specific events or conditions; When a preset event or condition is triggered, the smart contract automatically executes according to the programmed logic; After execution is completed, the smart contract generates an execution result, which includes a state change and / or data writing; Update the smart contract status based on the execution results and record the update on the blockchain; The execution results and update status are fed back to the user through the user interface, allowing the user to view the execution results and the current status of the contract.

7. The method according to claim 1, characterized in that The multi-factor authentication includes a password, biometrics, smart card or one-time password; the verification of the device accessing the digital rights information and identifier through multi-factor authentication and fine-grained permission control includes: Based on the user's identity and permission level, the system controls the user's access to digital rights information and identifiers; Allow or deny the user's operation request based on the user's identity authentication and permission control results; If the user is verified and has the corresponding authority, the user is allowed to access the digital rights information and identifier; If user access is denied, the reason for the denial will be fed back to the user's device.

8. A data transmission system based on digital rights, characterized in that: The system comprises: An identifier module, used to generate a corresponding identifier for the digital rights information to be transmitted sent by the user device using blockchain technology and hash functions; An encryption transmission module, used to transmit the digital rights and interests information and identifiers through end-to-end encryption technology; A verification module, used to verify the device accessing the digital equity information and identifier through multi-factor authentication and fine-grained permission control; The monitoring module is used to call the cross-platform synchronization engine to monitor update events and trigger data synchronization operations on each platform.

9. An electronic device, comprising: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that: Computer-readable instructions are stored thereon, and the computer-readable instructions can be executed by a processor to implement the method according to any one of claims 1-7.

Images