Equity sharing processing method and apparatus

Abstract

The embodiments of the present specification provide a benefit sharing processing method and device, wherein a benefit sharing processing method comprises: obtaining a sharing request of a sharing user sharing a benefit resource to at least one shared user; performing a trusted check on the at least one shared user based on the sharing request to obtain a user set composed of target users that pass the check; judging whether a resource parameter of the benefit resource meets a corresponding sharing condition; if yes, adding the target user to a benefit relationship between the sharing user and the benefit resource, so that the target user obtains a resource permission of the benefit resource.

Description

[0001] This application is a divisional application of Chinese invention patent application filed on May 13, 2021, with application number CN202110521430.8 and title “Rights Sharing Processing Method and Apparatus”. Technical Field

[0002] This document relates to the field of data processing technology, and in particular to a method and apparatus for rights sharing processing. Background Technology

[0003] With the rapid development of internet technology, online consumption has become widespread, and more and more merchants are selling goods through online platforms. At the same time, various online platforms have emerged, leading to increasingly fierce competition among them and among merchants. To enhance their competitiveness, online platforms and merchants often conduct online marketing activities, such as distributing red envelopes, coupons, and gift certificates to participating users. Therefore, maximizing the utilization of these benefits and increasing their usage rate has become particularly important. Summary of the Invention

[0004] This specification provides one or more embodiments of a rights-sharing processing method. The rights-sharing processing method includes: obtaining a sharing request from a sharing user to share rights resources with at least one recipient user; performing a trust verification on the at least one recipient user based on the sharing request to obtain a user set consisting of verified target users; determining whether the resource parameters of the rights resource meet the corresponding sharing conditions; if so, adding the target user to the rights relationship between the sharing user and the rights resource, so that the target user obtains resource permissions for the rights resource.

[0005] This specification provides one or more embodiments of a blockchain-based rights verification processing method, comprising: based on a verification request sent by a sharing user or a shared user from a server, invoking a smart contract deployed on the blockchain node to query the rights resources corresponding to the service type of the rights verification request; detecting whether the rights relationship of the sharing user or the shared user is recorded in the rights relationship table; if so, if the resource status of the rights resource read from the blockchain is unused, sending an availability reminder to the server, and verifying the rights resource upon receiving a verification confirmation request sent by the server; returning the rights verification result to the server, and updating the verification status of the rights resource to the blockchain.

[0006] This specification provides one or more embodiments of another blockchain-based rights verification processing method, including: obtaining a service request for a service type submitted by a sharing user or a shared user, and sending the service request as a rights verification request to a blockchain node in the blockchain; receiving a notification of the availability of rights resources sent by the blockchain node and sending it to the sharing user or the shared user; and sending a verification confirmation request to the blockchain node after settlement based on the rights resources and successful settlement.

[0007] This specification provides one or more embodiments of a rights-sharing processing apparatus, comprising: an acquisition module configured to acquire a sharing request from a sharing user to share rights resources with at least one shared user; a verification module configured to perform a trusted verification on the at least one shared user based on the sharing request, thereby obtaining a user set consisting of verified target users; and a judgment module configured to determine whether the resource parameters of the rights resources meet the corresponding sharing conditions; if so, to run an addition module, wherein the addition module is configured to add the target users to the rights relationship between the sharing user and the rights resources, so that the target users obtain the resource permissions of the rights resources.

[0008] This specification provides one or more embodiments of a blockchain-based rights verification processing device, comprising: a query module configured to query the rights resources corresponding to the service type of the rights verification request by invoking a smart contract deployed on the blockchain node, based on a rights verification request sent by a sharing user or a shared user from a server; a detection module configured to detect whether the rights relationship of the sharing user or the shared user is recorded in the rights relationship table; if so, and if the resource status of the rights resource read from the blockchain is unused, the verification module is run, configured to send an availability reminder to the server and verify the rights resource upon receiving a verification confirmation request from the server; and an update module configured to return the rights verification result to the server and update the verification status of the rights resource to the blockchain.

[0009] This specification provides one or more embodiments of another blockchain-based rights verification processing apparatus, comprising: a service request receiving module configured to acquire service requests for a service type submitted by a sharing user or a shared user, and send the service request as a rights verification request to a blockchain node in the blockchain; an availability reminder receiving module configured to receive availability reminders of rights resources sent by the blockchain node and send them to the sharing user or the shared user; and a verification request module configured to send a verification confirmation request to the blockchain node after settlement based on the rights resources and successful settlement.

[0010] This specification provides one or more embodiments of a rights-sharing processing device, including: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire a sharing request from a sharing user to share rights resources with at least one shared user; perform a trusted verification on the at least one shared user based on the sharing request to obtain a user set consisting of verified target users; determine whether the resource parameters of the rights resources meet the corresponding sharing conditions; if so, add the target users to the rights relationship between the sharing user and the rights resources, so that the target users obtain resource permissions for the rights resources.

[0011] This specification provides one or more embodiments of a blockchain-based rights verification processing device, comprising: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: query the rights resources corresponding to the service type of the rights verification request by invoking a smart contract deployed on the blockchain node, based on a rights verification request sent by a server from a sharing user or a shared user; detect whether the rights relationship of the sharing user or the shared user is recorded in the rights relationship table; if so, if the resource status of the rights resource read from the blockchain is unused, send an availability reminder to the server, and verify the rights resource upon receiving a verification confirmation request from the server; return the rights verification result to the server, and update the verification status of the rights resource to the blockchain.

[0012] This specification provides one or more embodiments of another blockchain-based rights verification processing device, comprising: a processor; and a memory configured to store computer-executable instructions, which, when executed, cause the processor to: acquire a service request for a service type submitted by a sharing user or a shared user, and send the service request as a rights verification request to a blockchain node in the blockchain; receive a notification of the availability of rights resources sent by the blockchain node and send it to the sharing user or the shared user; and send a verification confirmation request to the blockchain node after settlement based on the rights resources and successful settlement.

[0013] This specification provides one or more embodiments of a first storage medium for storing computer-executable instructions, which, when executed, perform the following process: Obtaining a sharing request from a sharing user to share a resource with at least one recipient user; performing a trusted verification on the at least one recipient user based on the sharing request to obtain a user set consisting of verified target users; determining whether the resource parameters of the resource satisfy the corresponding sharing conditions; if so, adding the target user to the rights and interests relationship between the sharing user and the resource, so that the target user obtains the resource permissions of the resource.

[0014] This specification provides one or more embodiments of a second storage medium for storing computer-executable instructions. When executed, these instructions implement the following process: based on a redemption request sent by the server from a sharing user or a shared user, the smart contract deployed on the blockchain node is invoked to query the equity resources corresponding to the service type of the equity redemption request. The equity relationship table is checked to see if the equity relationship of the sharing user or the shared user is recorded; if so, and if the resource status of the equity resource read from the blockchain is unused, an availability reminder is sent to the server, and the equity resource is redeemed upon receiving a redemption confirmation request from the server. The equity redemption result is returned to the server, and the redemption status of the equity resource is updated to the blockchain.

[0015] This specification provides one or more embodiments of a third storage medium for storing computer-executable instructions, which, when executed, perform the following processes: obtaining a service request for a service type submitted by the sharing user or the shared user, and sending the service request as a rights verification request to a blockchain node in the blockchain; receiving a notification of the availability of rights resources sent by the blockchain node and sending it to the sharing user or the shared user; and sending a verification confirmation request to the blockchain node after settlement based on the rights resources and successful settlement. Attached Figure Description

[0016] To more clearly illustrate the technical solutions in one or more embodiments of this specification or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this specification. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0017] Figure 1 A flowchart illustrating a rights-sharing processing method provided in one or more embodiments of this specification;

[0018] Figure 2 This specification provides a method for processing rights sharing in a multi-user sharing scenario, which is provided in one or more embodiments.

[0019] Figure 3 A flowchart illustrating a blockchain-based rights verification processing method provided for one or more embodiments of this specification;

[0020] Figure 4 A flowchart illustrating another blockchain-based rights verification processing method provided in one or more embodiments of this specification;

[0021] Figure 5 A schematic diagram of a rights-sharing processing device provided for one or more embodiments of this specification;

[0022] Figure 6 A schematic diagram of a blockchain-based rights verification processing device provided for one or more embodiments of this specification;

[0023] Figure 7 A schematic diagram of another blockchain-based rights verification processing device provided for one or more embodiments of this specification;

[0024] Figure 8 A schematic diagram of the structure of a rights-sharing processing device provided for one or more embodiments of this specification;

[0025] Figure 9 A schematic diagram of the structure of a blockchain-based rights verification processing device provided for one or more embodiments of this specification;

[0026] Figure 10 This is a schematic diagram of another blockchain-based rights verification processing device provided for one or more embodiments of this specification. Detailed Implementation

[0027] To enable those skilled in the art to better understand the technical solutions in one or more embodiments of this specification, the technical solutions in one or more embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of the embodiments. Based on one or more embodiments of this specification, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of this document.

[0028] This specification provides an example of a rights-sharing processing method:

[0029] Reference Figure 1It shows a flowchart of a rights-sharing processing method provided in this embodiment, with reference to... Figure 2 This embodiment illustrates a method for processing rights sharing in a multi-user sharing scenario.

[0030] Reference Figure 1 The rights-sharing processing method provided in this embodiment specifically includes steps S102 to S108.

[0031] Step S102: Obtain a sharing request from the sharing user to share the rights and resources with at least one shared user.

[0032] In practical applications, it often happens that users who claim rights and resources do not use them, while users who need to use them are unable to claim them for various reasons, affecting the utilization rate of rights and resources. The rights and resources sharing processing method provided in this embodiment enables multiple accounts to use rights and resources by having users who have claimed them share them with other users. Specifically, the sharing user selects the user to whom the rights and resources are shared. When the trust verification of the user to be shared with is passed and the shared rights and resources meet the sharing conditions, the user to be shared with is added to the rights and resources relationship between the sharing user and the user to the sharing, so that both the sharing user and the user to be shared with obtain the resource permissions of the rights and resources, thereby maximizing the utilization of rights and resources and improving the utilization rate of rights and resources.

[0033] In this embodiment, the sharing user includes a user who receives a benefit resource and shares it with other users; the other users who receive the resource are the shared users. The benefit resource includes items with economic or other value provided to users by recommended projects, such as cash bonuses, coupons, or periodic cards. It should be noted that after receiving the benefit resource, users can view and use it. Furthermore, the benefit resource can be issued to the user's account for use in specific scenarios or channels. The recommended project refers to a service project that increases user participation by issuing benefit resources to users, such as public transportation promotion activities or shared vehicle promotion activities. The sharing request includes the resource tag of the benefit resource, the user identifier of the sharing user, the user identifier of the shared user, and / or the sharing time; in addition, it may include other information that the server needs to process, which is not limited in this embodiment.

[0034] In practice, for a sharing user to share rights and resources with a shared user, the user must first acquire those rights and resources. The sharing user's access to the rights and resources is determined through the rights and interests relationship between the two. To ensure that the sharing user is a trustworthy user and to avoid resource loss, in an optional implementation of this embodiment, a trust verification is performed on the sharing user during the process of distributing rights and resources. If the trust verification passes, the rights and interests relationship between the sharing user and the rights and interests resource is established before distributing the rights and interests resource to the sharing user. Specifically, the rights and interests resource is distributed in the following manner:

[0035] Based on the sharing user's access request for the recommended project, the sharing user is verified for trustworthiness.

[0036] If the verification passes, a resource tag for the recommended benefits resource will be sent to the sharing user;

[0037] A referral benefit relationship is established between the sharing user and the referral benefit resource based on the sharing user's request to claim the referral benefit resource.

[0038] Wherein, the rights and interests resources are part or all of the recommended rights and interests resources, and the recommended rights and interests relationships include the rights and interests relationships.

[0039] Specifically, when a user accesses a recommended project, the sharing user is verified for trustworthiness. If the verification is successful, the platform queries at least one recommended benefit resource based on the project identifier of the recommended project and displays the resource tag of the recommended benefit resource to the sharing user. When the sharing user submits a request to claim any one or more recommended benefit resources, a benefit relationship is established between the sharing user and the recommended benefit resource to be claimed.

[0040] For example, after receiving a user A's access request for a shared bicycle promotion activity, the system checks whether user A is on the blacklist or graylist stored on the account platform. If user A is not on the blacklist or graylist, the system queries the rights and benefits platform for recommended rights and benefits resources corresponding to the shared bicycle promotion activity based on the project type carried in the access request. The recommended rights and benefits resources found include 5 two-yuan cash red envelopes and a one-time 50% discount on a monthly card. The system sends the corresponding resource tags to the sharing user and obtains the user's request to claim the 5 two-yuan cash red envelopes. Then, a relationship is established between user A and the 5 two-yuan cash red envelopes. After the relationship is established, the system displays the resource tags of the rights and benefits resources with the established relationship to user A when user A views the content.

[0041] In practice, after receiving recommended benefits, users can share all or part of them. When sharing, the sharing user needs to select a recipient. To reduce the steps required and improve the sharing experience, this embodiment provides an optional implementation where the sharing user can pre-set a default recipient. If a default recipient is set, the sharing will default to that user when triggering the sharing control, eliminating the need for the user to select a recipient again. If no default recipient is set, the user must select and submit the recipient when triggering the sharing control. The recipient is obtained as follows:

[0042] If the sharing user triggers the sharing control of the rights and benefits resources, query whether the sharing user has configured a default sharing user;

[0043] If so, then the default shared user is determined as the at least one shared user;

[0044] If not, generate a user selection page based on the sharing user's friend list; if the sharing user triggers the sharing confirmation control configured on the user selection page, determine at least one user selected by the sharing user through the user selection page, and / or at least one user queried and selected by the sharing user through the user selection page as the at least one shared user.

[0045] Specifically, when it is detected that a user has triggered the sharing control for rights and resources, it checks whether the user has configured a default user to share with. If so, the default user is used as the user to share with. If not, a user selection page is generated based on the user's friend list, and the friend user selected by the user through the user selection page or the non-friend user selected by the user is used as the user to share with.

[0046] For example, after user A receives 5 two-yuan cash red envelopes, when the sharing control configured in the resource label display area of ​​these 5 two-yuan cash red envelopes is detected, it is checked whether user A has set the default sharing users. If it is detected that user A has set user B, user C and user D as the default sharing users, then these 5 two-yuan cash red envelopes will be shared with user B, user C and user D.

[0047] For example, after user A receives 5 two-yuan cash red envelopes, when it is detected that user A has triggered the sharing control configured in the resource label display area of ​​these 5 two-yuan cash red envelopes, it is detected that user A has not set a default user to share with. Then, a user selection page is generated based on user A's friend list. User A selects user B, user C from the friend list and user D, who is not a friend, as the user to share with through the user selection page.

[0048] Step S104: Based on the sharing request, perform a trusted verification on the at least one shared user to obtain a user set consisting of target users who have passed the verification.

[0049] The trusted verification refers to verifying whether the at least one shared user is a user on a blacklist or graylist. The target user refers to the shared user who has passed the trusted verification. The user set includes at least one shared user who has passed the trusted verification.

[0050] In practice, to enhance the security of rights and interests during the sharing process, rights and interests can only be shared with the recipient after the recipient has passed the trusted verification. Therefore, when the sharing user submits at least one recipient, the rights and interests are shared with the recipient who has passed the trusted verification.

[0051] Step S106: Determine whether the resource parameters of the equity resource meet the corresponding sharing conditions.

[0052] The resource parameters include: resource type, sharing time, and / or resource status. Additionally, they may include threshold values ​​for the amount of equity resources. These resource parameters are determined based on actual service needs, and this embodiment does not impose any limitations on them.

[0053] In specific implementation, to further ensure the security of rights and interests resources during the sharing process, in an optional implementation method provided in this embodiment, after the trusted verification of the user being shared with is performed and the trusted verification passes, it is necessary to further determine whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions. Specifically, the determination of whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions is mainly achieved through the following methods:

[0054] The system determines whether the resource type of the equity resource is a shareable resource type, whether the sharing time is within a sharing time interval, and / or whether the resource status of the equity resource is unused. Additionally, it can determine whether the resource amount of the equity resource exceeds an amount threshold.

[0055] Specifically, it can be a judgment on the above three factors, or a judgment on any one or two of the above three factors; after judgment, if the resource parameters meet the corresponding sharing conditions, the target user is added to the rights and interests relationship between the sharing user and the rights and interests resource.

[0056] In addition, due to differences in resource types, sharing times, or other factors, sharing may fail. To improve the user's awareness of the reasons for sharing failure, in one optional implementation of this embodiment, if the execution result after determining whether the resource parameters of the right resource meet the corresponding sharing conditions is negative, the reason for sharing failure is read based on the determination result; and based on the reason for sharing failure, a sharing failure reminder is sent to the user.

[0057] For example, User A shares 5 two-yuan cash red envelopes with Users B, C, and D. After verifying the trustworthiness of Users B, C, and D, the system determines whether the shared bicycle promotion corresponding to these 5 two-yuan cash red envelopes is a shareable benefit. If not, a reminder is returned to User A that the resource type is not shareable. If yes, the system determines whether the sharing time of these 5 two-yuan cash red envelopes falls within the sharing time range. If not, a reminder is returned to User A that the current time is not shareable, and the sharing time is from xx o'clock to xx o'clock. If yes, the system determines whether the resource status of the 5 two-yuan cash red envelopes is unused. If not, a reminder is returned to User A that the resource has been used. If yes, Users B, C, and D are added to the benefit relationship between User A and the 5 two-yuan cash red envelopes.

[0058] Step S108: Add the target user to the rights and interests relationship between the sharing user and the rights and interests resource.

[0059] In practical implementation, the target user is added to the rights and interests relationship between the sharing user and the rights and interests resource, so that the target user obtains resource permissions for the rights and interests resource. After obtaining resource permissions, the target user can view and use the rights and interests resource in their account. After the rights and interests resource is shared, both the sharing user and the target user can view and use the rights and interests resource. In order to improve the awareness of the usage of the rights and interests resource, in an optional implementation method provided in this embodiment, when the sharing user or the target user views the rights and interests resource, the resource tag is displayed in the following way:

[0060] If it is detected that the sharing user or the target user submits an access request for the rights and benefits resource, then query the resource status of the rights and benefits resource;

[0061] Based on the resource status, the resource tag of the benefit resource is displayed to the sharing user or the target user.

[0062] Specifically, when a sharing user or target user accesses a rights and benefits resource, the resource status of the rights and benefits resource is queried. If the resource status is "used", a resource tag with a "used" mark is displayed to the sharing user or target user. If the resource status is "unused", a resource tag with an "available" mark is displayed to the sharing user or target user.

[0063] In addition, if there are multiple rights and benefits resources, in order to improve the awareness of the usage of rights and benefits resources, in an optional implementation of this embodiment, if the sharing user or the target user submits an access request for the rights and benefits resources, the resource status of the rights and benefits resources is queried to obtain the remaining rights and benefits resources whose resource status is unused; based on the number of remaining rights and benefits resources, the resource tags of the rights and benefits resources are displayed to the sharing user or the target user.

[0064] For example, user A shares 5 two-yuan cash red packets with users B, C, and D. When user B wants to view the acquired benefits, the system detects user B's access request to the account benefits and queries the resource status of the 5 two-yuan cash red packets. If it finds that 3 of the two-yuan cash red packets are in a used state and 2 are in an unused state, then it displays a resource tag with a usable resource amount of 2 to user B.

[0065] In practice, when a sharing user or a target user accesses the service corresponding to a rights resource, they can use that rights resource. In one optional implementation of this embodiment, when a sharing user or a target user accesses the corresponding service, the following operations are performed:

[0066] If it is detected that the sharing user or the target user submits a service request for the recommended project corresponding to the rights and benefits resource, query the resource status of the rights and benefits resource;

[0067] If the resource is in an unused state, send a resource reminder to the sharing user or the target user;

[0068] Settlement processing is performed based on the settlement request submitted by the sharing user or the target user based on the rights and resources.

[0069] Upon successful settlement, the rights and interests platform will verify and cancel the rights and interests resources.

[0070] Specifically, if a sharing user or target user submits a service request for a service item corresponding to a rights and benefits resource, the resource status of the rights and benefits resource is queried. If there are rights and benefits resources with an unused status, a resource reminder is sent to the sharing user or target user. Then, settlement processing is carried out according to the settlement request submitted by the sharing user or target user. After the settlement processing, the rights and benefits platform marks the resource status of the used rights and benefits resource as used.

[0071] In one optional implementation method provided in this embodiment, the settlement process is specifically performed in the following manner:

[0072] According to the settlement request, a cancellation request is sent to the rights and interests platform, and the settlement amount of the rights and interests resources is obtained from the rights and interests platform;

[0073] The actual settlement amount is determined based on the resource settlement amount and the settlement amount in the settlement request, and the payment platform transfers funds according to the actual settlement amount.

[0074] After the payment platform successfully transfers funds, it sends a verification confirmation reminder to the rights platform, so that the rights platform can mark the resource status of the rights resource as used based on the verification confirmation reminder.

[0075] For example, user A shares 5 two-yuan cash red envelopes with users B, C, and D. If user B accesses a shared bicycle promotion activity, the system checks the resource status of the 5 two-yuan cash red envelopes. It finds that 3 of the red envelopes are in a used state and 2 are in an unused state. A resource reminder for the two-yuan cash red envelopes is sent to user B. The system then receives a settlement request from user B regarding these red envelopes. Based on this request, the system retrieves the two-yuan cash red envelopes from the platform. Then, based on the 3 yuan fee that user B needs to pay and the amount from the two-yuan cash red envelopes, it calculates that user B's actual payment is 1 yuan. This 1 yuan is deducted from user B's account and transferred to the account corresponding to the shared bicycle promotion activity. Finally, the resource status of the used two-yuan cash red envelopes is marked as used.

[0076] It should be noted that, in the above-mentioned process of reclaiming rights and resources, to ensure the effectiveness of the reclaiming, settlement is performed first, and reclaiming is only performed if the settlement is successful. In addition, to ensure the effective use of rights and resources during the settlement process, resource reclaiming can also be performed through the following steps: If a service request for a recommended project corresponding to the rights and resources is detected by the sharing user or the shared user, the resource status of the rights and resources is queried; if the resource status is unused, a resource reminder is sent to the sharing user or the target user; a reclaiming request is sent to the rights and resources platform based on the settlement request submitted by the sharing user or the target user; the rights and resources platform marks the resource status of the rights and resources as used based on the reclaiming request, and sends the resource settlement amount and reclaiming result to the server; the server determines the actual settlement amount based on the reclaiming result, using the resource settlement amount and the settlement amount in the settlement request, and the payment platform transfers funds based on the actual settlement amount. That is: resource reclaiming is performed first, then settlement is performed; if reclaiming fails, settlement fails.

[0077] The following description uses the application of a rights-sharing processing method provided in this embodiment in a multi-user sharing scenario as an example to further illustrate the rights-sharing processing method provided in this embodiment. (See also...) Figure 2 The method for handling rights sharing in multi-user sharing scenarios specifically includes steps S202 to S216.

[0078] Step S202: Based on the sharing user's request to claim the rights and resources of the shared mobility service, establish the rights and interests relationship between the sharing user and the rights and interests resources.

[0079] Step S204: Based on the sharing request from the sharing user to share the rights and resources with at least one shared user, perform a trusted verification on at least one shared user.

[0080] Step S206: After obtaining the trusted user who has passed the verification, determine whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions.

[0081] If so, proceed to step S208;

[0082] If not, a sharing failure notification will be sent to the sharing user.

[0083] Step S208: Add the shared user who has passed the trust verification to the rights and interests relationship between the sharing user and the rights and interests resource.

[0084] Step S210: If a service request for the shared mobility service is detected by either the sharing user or the user being shared with, query the resource status of the rights and benefits resources.

[0085] Step S212: If the resource status is unused, send a resource reminder to the sharing user or the user to whom the resource is shared.

[0086] Step S214: Perform settlement processing based on the settlement request submitted by the sharing user or the shared user based on the rights and resources.

[0087] Step S216: If the settlement is successful, mark the resource status of the equity resource as used.

[0088] In addition, upon receiving a settlement request, the resource status of the equity resource can be marked as used before settlement processing is performed based on the equity resource.

[0089] In summary, the rights-sharing processing method provided in this embodiment first obtains a sharing request from a sharing user to share rights resources with at least one shared user. Then, based on the sharing request, a trust verification is performed on at least one shared user to obtain a user set composed of verified target users. Next, it is determined whether the resource parameters of the rights resources meet the corresponding sharing conditions. If so, the target user is added to the rights relationship between the sharing user and the rights resources so that the target user obtains the resource permissions of the rights resources, thereby improving the utilization rate of the rights resources.

[0090] This specification provides an example of a blockchain-based rights verification processing method:

[0091] Reference Figure 3 The diagram illustrates a flowchart of a blockchain-based rights verification process provided in this embodiment.

[0092] The blockchain-based rights verification processing method provided in this embodiment is applied to blockchain nodes in a blockchain; the method specifically includes steps S302 to S308.

[0093] Step S302: Based on the redemption request sent by the server from the sharing user or the shared user, the smart contract deployed on the blockchain node is invoked to query the rights and interests resources corresponding to the service type of the rights and interests redemption request.

[0094] The blockchain is used to store the rights and interests relationship table and the resource status of rights and interests resources. The rights and interests relationships in the table are created after the rights and interests resources are claimed and updated after they are shared. In this embodiment, the sharing user includes a user who claims rights and interests resources and shares them with other users; the other users who are shared with are the shared users. The rights and interests resources include assets with economic or other value provided to users by recommended projects, such as cash bonuses, coupons, and periodic cards. It should be noted that after claiming rights and interests resources, users can view and use them. Furthermore, rights and interests resources can be issued to user accounts for use in specific scenarios or channels. The recommended project refers to a service project that increases user participation by issuing rights and interests resources to users, such as public transportation promotion activities or shared vehicle promotion activities.

[0095] In practical applications, it often happens that users who claim rights and resources do not use them, while users who need to use them are unable to claim the relevant rights and resources for various reasons, affecting the utilization rate of rights and resources. The rights and resources redemption processing method based on blockchain provided in this embodiment involves the sharing user or the shared user submitting a resource redemption request after the sharing user shares rights and resources with a non-shared user. In one optional implementation of this embodiment, the rights and resources relationships in the rights and resources relationship table stored in the blockchain are created in the following way:

[0096] Based on the sharing user's access request for the service type, the sharing user is verified for trustworthiness.

[0097] If the verification passes, recommended benefits resources are sent to the sharing user; the recommended benefits resources include the benefits resources mentioned above.

[0098] The rights and interests relationship between the sharing user and the rights and interests resource is established based on the sharing user's request to claim the rights and interests resource.

[0099] Specifically, when a user accesses a recommended project, the server performs a trust verification on the user. If the verification is successful, the server queries the rights platform for at least one corresponding recommended rights resource based on the project identifier of the recommended project, and displays the resource tag of the recommended rights resource to the user. When the user submits a request to claim any one or more recommended rights resources, a rights relationship is established between the user and the recommended rights resource to be claimed. After the rights relationship is established, it is sent to the blockchain node so that the blockchain node records the rights relationship in the rights relationship table and uploads it to the blockchain for storage.

[0100] In addition, the server can perform a trusted verification of the sharing user when it detects that the sharing user has accessed the recommended project. If the verification is successful, the server can send the user's identifier and the resource tag of the rights and interests to the blockchain node. The blockchain node can then call the deployed smart contract to establish the rights and interests relationship between the sharing user and the rights and interests, record it in the rights and interests relationship table, and then upload the rights and interests relationship table to the blockchain for storage.

[0101] In practice, after a user receives recommended benefits, they can share all or part of those benefits. When sharing, the sharing user needs to select a recipient. To enhance the security of the benefits during sharing, the benefits can only be shared with the recipient after the recipient's trust verification is passed. Therefore, when the sharing user submits at least one recipient, the benefits are shared with the recipient whose trust verification has passed. After the recipient's trust verification is passed, the benefit relationships in the benefit relationship table are updated. In one optional implementation of this embodiment, the benefit relationships are updated in the following way:

[0102] Obtain a sharing request from the sharing user to share the rights and resources with at least one recipient user;

[0103] Based on the sharing request, a trusted verification is performed on the at least one shared user to obtain a user set consisting of the shared users that have passed the verification.

[0104] Determine whether the resource parameters of the equity resource meet the corresponding sharing conditions;

[0105] If so, the user being shared with is added to the rights and interests relationship between the sharing user and the rights and interests resource to update the rights and interests relationship.

[0106] Specifically, the user to be shared with is added to the rights and interests relationship between the sharing user and the rights and interests resource, thereby granting the shared user resource access. After obtaining resource access, the shared user can view and use the rights and interests resource in their account. To enhance the security of rights and interests resources during the sharing process, rights and interests resources can only be shared with the shared user if the shared user's trust verification is passed. Therefore, when the sharing user submits at least one shared user, the rights and interests resource is shared with the shared user whose trust verification has passed.

[0107] After the server performs trusted verification on at least one user to be shared with based on the sharing request, and obtains a user set consisting of verified users, it determines whether the resource parameters of the equity resource meet the corresponding sharing conditions. If they do, the server adds the users to be shared with to the equity relationship between the sharing user and the equity resource, and then sends the updated equity relationship to the blockchain node. The blockchain node updates the equity relationship in the equity relationship table according to the equity relationship. The resource parameters include: resource type, sharing time and / or resource status. In addition, it may also include the threshold amount of the equity resource, etc. The resource parameters are determined according to the actual service needs, and this embodiment does not limit them.

[0108] In addition, during the process of updating the rights and interests relationship, when the server receives a sharing request from a sharing user to raise the price, it performs a trusted verification based on the user identifier of the user being shared with in the sharing request. If the verification passes, the server sends the sharing information carried in the sharing request to the blockchain node. After receiving the sharing information, the blockchain node calls the smart contract deployed on the blockchain node to determine whether the resource parameters of the rights and interests resource meet the corresponding sharing conditions. The determination of whether the resource parameters of the rights and interests resource meet the corresponding sharing conditions is mainly achieved through the following methods: determining whether the resource type of the rights and interests resource is a shareable resource type, determining whether the sharing time is within the sharing time interval, and / or determining whether the resource status of the rights and interests resource is unused. In addition, it can also determine whether the resource amount of the rights and interests resource exceeds the amount threshold. Specifically, it can be all of the above judgments, or any one or more of them. If the resource parameters meet the corresponding sharing conditions after the judgment, a sharing success result is sent to the server, and the user being shared with is added to the rights and interests relationship between the sharing user and the rights and interests resource to update the rights and interests relationship table. After receiving the sharing success result, the server sends the resource tag of the rights and interests resource to the sharing user and the user being shared with.

[0109] It should be noted that after receiving recommended benefits, users can share all or part of them. When sharing, the sharing user needs to select a recipient. To reduce the process for sharing and improve the user experience, users can pre-set a default recipient. If a default recipient is set, the sharing will automatically proceed to that recipient when the user triggers the share control, eliminating the need for the user to select a recipient again. If no default recipient is set, the user will need to manually select a recipient when triggering the share control. The sharing user selects and submits the user to be shared with. The user to be shared with is obtained as follows: when the sharing user triggers the sharing control of the benefit resource, it is queried whether the sharing user has configured a default user to be shared with; if so, the default user to be shared with is determined as the at least one user to be shared with; if not, a user selection page is generated based on the sharing user's friend list; when the sharing user triggers the sharing confirmation control configured on the user selection page, at least one user selected by the sharing user through the user selection page, and / or at least one user queried and selected by the sharing user through the user selection page, is determined as the at least one user to be shared with. Furthermore, due to differences in resource types, sharing times, or other factors, sharing may fail. To improve the sharing user's awareness of the reasons for sharing failure, in an optional implementation of this embodiment, if the execution result after determining whether the resource parameters of the benefit resource meet the corresponding sharing conditions is negative, the reason for sharing failure is read based on the determination result; based on the reason for sharing failure, a sharing failure reminder is sent to the sharing user.

[0110] Specifically, when it is detected that a user has triggered the sharing control for rights and resources, it checks whether the user has configured a default user to share with. If so, the default user is used as the user to share with. If not, a user selection page is generated based on the user's friend list, and the friend user selected by the user through the user selection page or the non-friend user selected by the user is used as the user to share with.

[0111] Step S304: Detect whether the rights and interests relationship of the sharing user or the shared user is recorded in the rights and interests relationship table.

[0112] In practice, after identifying the corresponding rights and resources, the system checks whether the user submitting the reimbursement request has a rights and resource relationship with that resource. If so, the user can use the resource; otherwise, they cannot. After confirming a relationship, the system queries the blockchain for the resource's status. If the resource is unused, an availability notification is sent to the server. Based on this notification, the server displays the resource's tag to the sharing user or the user to whom the resource is shared.

[0113] In addition, if there are multiple rights and interests resources, in order to improve the awareness of the usage status of rights and interests resources, in an optional implementation method provided in this embodiment, an availability reminder is sent to the user in the following way: read the resource status of the rights and interests resources from the blockchain to obtain the remaining rights and interests resources whose resource status is unused; and send the availability reminder to the server based on the number of remaining rights and interests resources.

[0114] Step S306: Send an availability notification to the server, and cancel the rights and resources upon receiving a cancellation confirmation request from the server.

[0115] In practice, after sending an availability notification to the server, the server, upon successful settlement based on the stated rights and resources, sends a verification confirmation request to the blockchain node. Specifically, the server processes the settlement request based on the stated rights and resources submitted by the sharing user or the target user, and sends a verification confirmation request to the blockchain node upon successful settlement. The blockchain then marks the rights and resources as used based on the verification confirmation request.

[0116] Step S308: Return the rights and interests verification result to the server and update the verification status of the rights and interests resources to the blockchain.

[0117] In practice, the system returns a verification result to the server, which then sends a verification reminder to the sharing user or the user to whom the resource was shared, based on the result. Blockchain nodes upload the updated status of the equity resources to the blockchain for storage. Specifically, after sending an availability reminder to the server, the server performs settlement based on the equity resources, and after successful settlement, sends a verification confirmation request to the blockchain node. Specifically, the server processes the settlement request based on the equity resources submitted by the sharing user or the target user, and sends a verification confirmation request to the blockchain node upon successful settlement. The blockchain marks the resource status of the equity resources as used based on the verification confirmation request. The system returns an equity verification result to the server and updates the verification status of the equity resources to the blockchain. The system returns a verification result to the server, which then sends a verification reminder to the sharing user or the user to whom the resource was shared, based on the result. Blockchain nodes upload the updated status of the equity resources to the blockchain for storage.

[0118] It should be noted that, in the above-mentioned process of reclaiming rights and resources, to ensure the effectiveness of the reclaiming, settlement is performed first, and reclaiming is only performed if the settlement is successful. In addition, to ensure the effective use of rights and resources during the settlement process, resource reclaiming can also be performed through the following steps: If the server detects that the sharing user or the shared user has submitted a service request for a recommended project corresponding to the rights and resources, it sends the service request to the blockchain node; the blockchain node queries the resource status of the rights and resources; if the resource status is unused, it sends a resource reminder to the server, so that the server sends it to the sharing user or the shared user; the server sends a reclaiming request to the blockchain node based on the settlement request submitted by the sharing user or the shared user based on the rights and resources; the blockchain node marks the resource status of the rights and resources as used based on the reclaiming request, and sends the resource settlement amount and reclaiming result of the rights and resources to the server; based on the reclaiming result, the server determines the actual settlement amount using the resource settlement amount and the settlement amount in the settlement request, and the payment platform transfers funds based on the actual settlement amount. In other words, resource verification is performed first, followed by settlement processing; if verification fails, settlement fails.

[0119] In addition, both the sharing user and the shared user can view and use the privilege resources. To improve awareness of the usage of privilege resources, resource tags will be displayed in the following way when either the sharing user or the shared user views the privilege resources:

[0120] If it is detected that the sharing user or the user whose rights and interests are shared submits an access request for the rights and interests resource, then query the resource status of the rights and interests resource;

[0121] Based on the resource status, the resource tag of the benefit resource is displayed to the sharing user or the user to whom the resource is shared.

[0122] Specifically, when a sharing user or a shared user accesses a resource, the resource status is queried. If the resource status is "used," a resource tag with a "used" indicator is displayed to the sharing user or the shared user. If the resource status is "unused," a resource tag with an "available" indicator is displayed. When the server receives an access request for a resource from a sharing user or a shared user, it sends the request to a blockchain node. The blockchain node then queries the blockchain for the resource status based on the request and sends it to the server. The server then displays the resource tag to the sharing user or the shared user based on the resource status. For example, a resource tag with a "used" status can be set to "viewable but not accessible," while a resource tag with an "unused" status can be set to "viewable and accessible."

[0123] This specification provides another example of a blockchain-based rights verification processing method:

[0124] Reference Figure 4 The diagram illustrates a flowchart of a blockchain-based rights verification process provided in this embodiment.

[0125] The blockchain-based rights verification processing method provided in this embodiment is applied to a server; the method specifically includes steps S402 to S406.

[0126] The blockchain-based rights verification processing method for servers provided in this embodiment cooperates with the blockchain-based rights verification processing method for blockchain nodes in the blockchain described above during execution. Therefore, when reading the blockchain-based rights verification processing method provided in this embodiment, please refer to the embodiments of the blockchain-based rights verification processing method for blockchain nodes in the blockchain described above.

[0127] Step S402: Obtain the service request for the service type submitted by the sharing user or the user being shared with, and send the service request as a rights verification request to the blockchain node in the blockchain.

[0128] The blockchain is used to store the rights and interests relationship table and the resource status of rights and interests resources. The rights and interests relationships in the table are created after the rights and interests resources are claimed and updated after they are shared. In this embodiment, the sharing user includes a user who claims rights and interests resources and shares them with other users; the other users who are shared with are the shared users. The rights and interests resources include assets with economic or other value provided to users by recommended projects, such as cash bonuses, coupons, and periodic cards. It should be noted that after claiming rights and interests resources, users can view and use them. Furthermore, rights and interests resources can be issued to user accounts for use in specific scenarios or channels. The recommended project refers to a service project that increases user participation by issuing rights and interests resources to users, such as public transportation promotion activities or shared vehicle promotion activities.

[0129] In practical applications, it often happens that users who claim rights and resources do not use them, while users who need to use them are unable to claim the relevant rights and resources for various reasons, affecting the utilization rate of rights and resources. The rights and resources redemption processing method based on blockchain provided in this embodiment involves the sharing user or the shared user submitting a resource redemption request after the sharing user shares rights and resources with a non-shared user. In one optional implementation of this embodiment, the rights and resources relationships in the rights and resources relationship table stored in the blockchain are created in the following way:

[0130] Based on the sharing user's access request for the service type, the sharing user is verified for trustworthiness.

[0131] If the verification passes, recommended benefits resources are sent to the sharing user; the recommended benefits resources include the benefits resources mentioned above.

[0132] The rights and interests relationship between the sharing user and the rights and interests resource is established based on the sharing user's request to claim the rights and interests resource.

[0133] Specifically, when a user accesses a recommended project, the server performs a trust verification on the user. If the verification is successful, the server queries the rights platform for at least one corresponding recommended rights resource based on the project identifier of the recommended project, and displays the resource tag of the recommended rights resource to the user. When the user submits a request to claim any one or more recommended rights resources, a rights relationship is established between the user and the recommended rights resource to be claimed. After the rights relationship is established, it is sent to the blockchain node so that the blockchain node records the rights relationship in the rights relationship table and uploads it to the blockchain for storage.

[0134] In addition, the server can perform a trusted verification of the sharing user when it detects that the sharing user has accessed the recommended project. If the verification is successful, the server can send the user's identifier and the resource tag of the rights and interests to the blockchain node. The blockchain node can then call the deployed smart contract to establish the rights and interests relationship between the sharing user and the rights and interests, record it in the rights and interests relationship table, and then upload the rights and interests relationship table to the blockchain for storage.

[0135] In practice, after a user receives recommended benefits, they can share all or part of those benefits. When sharing, the sharing user needs to select a recipient. To enhance the security of the benefits during sharing, the benefits can only be shared with the recipient after the recipient's trust verification is passed. Therefore, when the sharing user submits at least one recipient, the benefits are shared with the recipient whose trust verification has passed. After the recipient's trust verification is passed, the benefit relationships in the benefit relationship table are updated. In one optional implementation of this embodiment, the benefit relationships are updated in the following way:

[0136] Obtain a sharing request from the sharing user to share the rights and resources with at least one recipient user;

[0137] Based on the sharing request, a trusted verification is performed on the at least one shared user to obtain a user set consisting of the shared users that have passed the verification.

[0138] Determine whether the resource parameters of the equity resource meet the corresponding sharing conditions;

[0139] If so, the user being shared with is added to the rights and interests relationship between the sharing user and the rights and interests resource to update the rights and interests relationship.

[0140] Specifically, the user to be shared with is added to the rights and interests relationship between the sharing user and the rights and interests resource, thereby granting the shared user resource access. After obtaining resource access, the shared user can view and use the rights and interests resource in their account. To enhance the security of rights and interests resources during the sharing process, rights and interests resources can only be shared with the shared user if the shared user's trust verification is passed. Therefore, when the sharing user submits at least one shared user, the rights and interests resource is shared with the shared user whose trust verification has passed.

[0141] After the server performs trusted verification on at least one user to be shared with based on the sharing request, and obtains a user set consisting of verified users, it determines whether the resource parameters of the equity resource meet the corresponding sharing conditions. If they do, the server adds the users to be shared with to the equity relationship between the sharing user and the equity resource, and then sends the updated equity relationship to the blockchain node. The blockchain node updates the equity relationship in the equity relationship table according to the equity relationship. The resource parameters include: resource type, sharing time and / or resource status. In addition, it may also include the threshold amount of the equity resource, etc. The resource parameters are determined according to the actual service needs, and this embodiment does not limit them.

[0142] In addition, during the process of updating the rights and interests relationship, when the server receives a sharing request from a sharing user to raise the price, it performs a trusted verification based on the user identifier of the user being shared with in the sharing request. If the verification passes, the server sends the sharing information carried in the sharing request to the blockchain node. After receiving the sharing information, the blockchain node calls the smart contract deployed on the blockchain node to determine whether the resource parameters of the rights and interests resource meet the corresponding sharing conditions. The determination of whether the resource parameters of the rights and interests resource meet the corresponding sharing conditions is mainly achieved through the following methods: determining whether the resource type of the rights and interests resource is a shareable resource type, determining whether the sharing time is within the sharing time interval, and / or determining whether the resource status of the rights and interests resource is unused. In addition, it can also determine whether the resource amount of the rights and interests resource exceeds the amount threshold. Specifically, it can be all of the above judgments, or any one or more of them. If the resource parameters meet the corresponding sharing conditions after the judgment, a sharing success result is sent to the server, and the user being shared with is added to the rights and interests relationship between the sharing user and the rights and interests resource to update the rights and interests relationship table. After receiving the sharing success result, the server sends the resource tag of the rights and interests resource to the sharing user and the user being shared with.

[0143] It should be noted that after receiving recommended benefits, users can share all or part of them. When sharing, the sharing user needs to select a recipient. To reduce the process for sharing and improve the user experience, users can pre-set a default recipient. If a default recipient is set, the sharing will automatically proceed to that recipient when the user triggers the share control, eliminating the need for the user to select a recipient again. If no default recipient is set, the user will need to manually select a recipient when triggering the share control. The sharing user selects and submits the user to be shared with. The user to be shared with is obtained as follows: when the sharing user triggers the sharing control of the benefit resource, it is queried whether the sharing user has configured a default user to be shared with; if so, the default user to be shared with is determined as the at least one user to be shared with; if not, a user selection page is generated based on the sharing user's friend list; when the sharing user triggers the sharing confirmation control configured on the user selection page, at least one user selected by the sharing user through the user selection page, and / or at least one user queried and selected by the sharing user through the user selection page, is determined as the at least one user to be shared with. Furthermore, due to differences in resource types, sharing times, or other factors, sharing may fail. To improve the sharing user's awareness of the reasons for sharing failure, in an optional implementation of this embodiment, if the execution result after determining whether the resource parameters of the benefit resource meet the corresponding sharing conditions is negative, the reason for sharing failure is read based on the determination result; based on the reason for sharing failure, a sharing failure reminder is sent to the sharing user.

[0144] Specifically, when it is detected that a user has triggered the sharing control for rights and resources, it checks whether the user has configured a default user to share with. If so, the default user is used as the user to share with. If not, a user selection page is generated based on the user's friend list, and the friend user selected by the user through the user selection page or the non-friend user selected by the user is used as the user to share with.

[0145] Step S404: Receive the availability notification of the rights and resources sent by the blockchain node and send it to the sharing user or the user to whom the resources are shared.

[0146] In practice, upon receiving a revocation request, a blockchain node invokes a smart contract deployed on the node to query the equity resources corresponding to the service type of the revocation request. After identifying the corresponding equity resources, it checks whether the user submitting the revocation request has an equity relationship with those resources. If so, the user can use the equity resources; otherwise, the user cannot. After finding an equity relationship, the node queries the blockchain for the resource status. If the resource status is unused, it sends an availability notification to the server. Based on this notification, the server displays the resource tag to the sharing user or the user being shared with.

[0147] In addition, if there are multiple equity resources, to improve the awareness of their usage, blockchain nodes send availability reminders to users in the following way: They read the resource status of the equity resources from the blockchain to obtain the remaining equity resources that are in an unused state; based on the quantity of the remaining equity resources, they send the availability reminder to the server. The availability reminder is then sent to the server, and upon receiving a verification confirmation request from the server, the equity resources are verified.

[0148] Step S406: After settlement is completed based on the equity resources and the settlement is successful, a verification confirmation request is sent to the blockchain node.

[0149] In practice, after sending an availability notification to the server, the server, upon successful settlement based on the equity resources, sends a verification confirmation request to the blockchain node. Specifically, the server processes the settlement request based on the equity resources submitted by the sharing user or the target user, and sends a verification confirmation request to the blockchain node upon successful settlement. The blockchain marks the equity resources as used based on the verification confirmation request. The server returns the equity verification result to the server and updates the verification status of the equity resources to the blockchain. The server then sends a verification notification to the sharing user or the user being shared with based on the verification result; the blockchain node uploads the updated status of the equity resources to the blockchain for storage.

[0150] During the settlement process, the server performs settlement processing in the following ways:

[0151] According to the settlement request, a reversal request is sent to the blockchain node, and the resource settlement amount of the equity resources is obtained from the blockchain node;

[0152] The actual settlement amount is determined based on the resource settlement amount and the settlement amount in the settlement request, and the payment platform transfers funds according to the actual settlement amount.

[0153] After the payment platform successfully transfers funds, it sends a verification confirmation reminder to the blockchain node, so that the blockchain node marks the resource status of the equity resource as used based on the verification confirmation reminder.

[0154] It should be noted that, in the above-mentioned process of reclaiming rights and resources, to ensure the effectiveness of the reclaiming, settlement is performed first, and reclaiming is only performed if the settlement is successful. In addition, to ensure the effective use of rights and resources during the settlement process, resource reclaiming can also be performed through the following steps: If the server detects that the sharing user or the shared user has submitted a service request for a recommended project corresponding to the rights and resources, it sends the service request to the blockchain node; the blockchain node queries the resource status of the rights and resources; if the resource status is unused, it sends a resource reminder to the server, so that the server sends it to the sharing user or the shared user; the server sends a reclaiming request to the blockchain node based on the settlement request submitted by the sharing user or the shared user based on the rights and resources; the blockchain node marks the resource status of the rights and resources as used based on the reclaiming request, and sends the resource settlement amount and reclaiming result of the rights and resources to the server; based on the reclaiming result, the server determines the actual settlement amount using the resource settlement amount and the settlement amount in the settlement request, and the payment platform transfers funds based on the actual settlement amount. In other words, resource verification is performed first, followed by settlement processing; if verification fails, settlement fails.

[0155] In addition, both the sharing user and the shared user can view and use the privilege resources. To improve awareness of the usage of privilege resources, resource tags will be displayed in the following way when either the sharing user or the shared user views the privilege resources:

[0156] If it is detected that the sharing user or the user whose rights and interests are shared submits an access request for the rights and interests resource, then query the resource status of the rights and interests resource;

[0157] Based on the resource status, the resource tag of the benefit resource is displayed to the sharing user or the user to whom the resource is shared.

[0158] Specifically, when a sharing user or a shared user accesses a resource, the resource status is queried. If the resource status is "used," a resource tag with a "used" indicator is displayed to the sharing user or the shared user. If the resource status is "unused," a resource tag with an "available" indicator is displayed. When the server receives an access request for a resource from a sharing user or a shared user, it sends the request to a blockchain node. The blockchain node then queries the blockchain for the resource status based on the request and sends it to the server. The server then displays the resource tag to the sharing user or the shared user based on the resource status. For example, a resource tag with a "used" status can be set to "viewable but not accessible," while a resource tag with an "unused" status can be set to "viewable and accessible."

[0159] The following is an embodiment of a rights-sharing processing device provided in this specification:

[0160] In the above embodiments, a rights-sharing processing method is provided, and correspondingly, a rights-sharing processing apparatus is also provided, which will be described below with reference to the accompanying drawings.

[0161] Reference Figure 5 The diagram shows a rights-sharing processing device provided in this embodiment.

[0162] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0163] This embodiment provides a rights-sharing processing device, including:

[0164] The acquisition module 502 is configured to acquire a sharing request from a sharing user to share rights and resources with at least one shared user;

[0165] Verification module 504 is configured to perform trusted verification on the at least one shared user based on the sharing request, and obtain a user set consisting of target users who have passed the verification.

[0166] The judgment module 506 is configured to determine whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions;

[0167] If so, the add module 508 is run. The add module 508 is configured to add the target user to the rights and interests relationship between the sharing user and the rights and interests resource, so that the target user can obtain the resource permissions of the rights and interests resource.

[0168] The following is an embodiment of a blockchain-based rights verification and processing device provided in this specification:

[0169] In the above embodiments, a blockchain-based rights verification processing method is provided, which is applied to a blockchain node in the blockchain. Correspondingly, a blockchain-based rights verification processing device is also provided, which runs on a blockchain node in the blockchain. The following description is in conjunction with the accompanying drawings.

[0170] Reference Figure 6 The diagram illustrates a blockchain-based rights verification processing device provided in this embodiment.

[0171] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0172] This embodiment provides a blockchain-based rights verification processing device, including:

[0173] The query module 602 is configured to query the rights and interests resources corresponding to the service type of the rights and interests verification request based on the verification request sent by the sharing user or the sharing user from the server, by calling the smart contract deployed by the blockchain node.

[0174] The detection module 604 is configured to detect whether the rights and interests relationship table records the rights and interests relationship between the sharing user and the shared user;

[0175] If the resource status of the equity resource read in the blockchain is unused, the revocation module 606 is run. The revocation module 606 is configured to send an availability reminder to the server and revoke the equity resource upon receiving a revocation confirmation request from the server.

[0176] The update module 608 is configured to return the rights and interests redemption results to the server and update the redemption status of the rights and interests resources to the blockchain.

[0177] Another embodiment of the blockchain-based rights verification processing device provided in this specification is as follows:

[0178] In the above embodiments, a blockchain-based rights verification processing method is provided and applied to a server. Correspondingly, a blockchain-based rights verification processing device is also provided and runs on the server. The following description is in conjunction with the accompanying drawings.

[0179] Reference Figure 7 The diagram illustrates a blockchain-based rights verification processing device provided in this embodiment.

[0180] Since the apparatus embodiments correspond to the method embodiments, the descriptions are relatively simple. For relevant parts, please refer to the corresponding descriptions of the method embodiments provided above. The apparatus embodiments described below are merely illustrative.

[0181] This embodiment provides a blockchain-based rights verification processing device, including:

[0182] The service request receiving module 702 is configured to obtain service requests for a service type submitted by the sharing user or the user being shared with, and send the service request as a rights verification request to the blockchain node in the blockchain.

[0183] The availability reminder receiving module 704 is configured to receive the availability reminder of the rights and resources sent by the blockchain node and send it to the sharing user or the user to whom the information is shared;

[0184] The reversal request module 706 is configured to send a reversal confirmation request to the blockchain node after settlement based on the equity resources is completed and the settlement is successful.

[0185] The following is an embodiment of a rights-sharing processing device provided in this specification:

[0186] Corresponding to the rights-sharing processing method described above, based on the same technical concept, one or more embodiments of this specification also provide a rights-sharing processing device for executing the rights-sharing processing method provided above. Figure 8 This is a schematic diagram of the structure of a rights-sharing processing device provided for one or more embodiments of this specification.

[0187] This embodiment provides a rights-sharing processing device, including:

[0188] like Figure 8 As shown, the rights-sharing processing device can vary significantly due to differences in configuration or performance. It may include one or more processors 801 and memory 802, and the memory 802 may store one or more application programs or data. The memory 802 may be temporary or persistent storage. The application programs stored in the memory 802 may include one or more modules (not shown), each module may include a series of computer-executable instructions in the rights-sharing processing device. Furthermore, the processor 801 may be configured to communicate with the memory 802 and execute the series of computer-executable instructions in the memory 802 on the rights-sharing processing device. The rights-sharing processing device may also include one or more power supplies 803, one or more wired or wireless network interfaces 804, one or more input / output interfaces 805, one or more keyboards 806, etc.

[0189] In one specific embodiment, the rights-sharing processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the rights-sharing processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0190] Obtain a sharing request from a sharing user to share rights and resources with at least one recipient user;

[0191] Based on the sharing request, a trust verification is performed on the at least one shared user to obtain a user set consisting of target users who have passed the verification.

[0192] Determine whether the resource parameters of the equity resource meet the corresponding sharing conditions;

[0193] If so, the target user is added to the rights and interests relationship between the sharing user and the rights and interests resource, so that the target user obtains the resource rights and interests resource.

[0194] The following is an example of a blockchain-based rights verification processing device provided in this specification:

[0195] Corresponding to the blockchain-based rights verification processing method described above, applied to the blockchain node corresponding to the server in the blockchain, based on the same technical concept, one or more embodiments of this specification also provide a blockchain-based rights verification processing device, which is used to execute the blockchain-based rights verification processing method provided above. Figure 9 This is a schematic diagram of the structure of a blockchain-based rights verification processing device provided for one or more embodiments of this specification.

[0196] This embodiment provides a blockchain-based rights verification processing device, applied to blockchain nodes in a blockchain, including:

[0197] like Figure 9As shown, blockchain-based claims verification processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 901 and memory 902, with memory 902 storing one or more applications or data. Memory 902 can be temporary or persistent storage. The applications stored in memory 902 may include one or more modules (not shown), each module including a series of computer-executable instructions within the blockchain-based claims verification processing device. Furthermore, processor 901 may be configured to communicate with memory 902, executing the series of computer-executable instructions in memory 902 on the blockchain-based claims verification processing device. The blockchain-based claims verification processing device may also include one or more power supplies 903, one or more wired or wireless network interfaces 904, one or more input / output interfaces 905, one or more keyboards 906, etc.

[0198] In one specific embodiment, the blockchain-based claims verification processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the blockchain-based claims verification processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0199] Based on the redemption request sent by the server from the sharing user or the shared user, the smart contract deployed on the blockchain node is invoked to query the rights and interests resources corresponding to the service type of the rights and interests redemption request;

[0200] Check whether the rights and interests relationship of the sharing user or the shared user is recorded in the rights and interests relationship table;

[0201] If the resource status of the equity resource read from the blockchain is unused, an availability reminder is sent to the server, and the equity resource is cancelled upon receiving a cancellation confirmation request from the server.

[0202] The system returns the rights and interests redemption results to the server and updates the redemption status of the rights and interests resources to the blockchain.

[0203] Another embodiment of a blockchain-based rights verification processing device is provided in this specification as follows:

[0204] Corresponding to the blockchain-based rights verification processing method described above, applied to a server, and based on the same technical concept, one or more embodiments of this specification also provide a blockchain-based rights verification processing device, which is used to execute the blockchain-based rights verification processing method described above. Figure 10 This is a schematic diagram of the structure of a blockchain-based rights verification processing device provided for one or more embodiments of this specification.

[0205] This embodiment provides a blockchain-based rights verification processing device, applied to a server, comprising:

[0206] like Figure 10 As shown, blockchain-based rights verification processing devices can vary significantly due to differences in configuration or performance. They may include one or more processors 1001 and memory 1002, with memory 1002 storing one or more application programs or data. Memory 1002 can be temporary or persistent storage. The application programs stored in memory 1002 may include one or more modules (not shown), each module including a series of computer-executable instructions within the blockchain-based rights verification processing device. Furthermore, processor 1001 may be configured to communicate with memory 1002, executing the series of computer-executable instructions in memory 1002 on the blockchain-based rights verification processing device. The blockchain-based rights verification processing device may also include one or more power supplies 1003, one or more wired or wireless network interfaces 1004, one or more input / output interfaces 1005, one or more keyboards 1006, etc.

[0207] In one specific embodiment, the blockchain-based claims verification processing device includes a memory and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer-executable instructions for the blockchain-based claims verification processing device, and is configured to be executed by one or more processors. The one or more programs include computer-executable instructions for performing the following:

[0208] Obtain service requests for a service type submitted by the sharing user or the user being shared with, and send the service requests as rights verification requests to the blockchain nodes in the blockchain;

[0209] Receive the availability notification of rights and resources sent by the blockchain node and send it to the sharing user or the user to whom the resources are shared;

[0210] After settlement is completed based on the equity resources and the settlement is successful, a verification confirmation request is sent to the blockchain node.

[0211] This specification provides an example of a storage medium as follows:

[0212] Corresponding to the above-described method for sharing rights, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0213] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0214] Obtain a sharing request from a sharing user to share rights and resources with at least one recipient user;

[0215] Based on the sharing request, a trust verification is performed on the at least one shared user to obtain a user set consisting of target users who have passed the verification.

[0216] Determine whether the resource parameters of the equity resource meet the corresponding sharing conditions;

[0217] If so, the target user is added to the rights and interests relationship between the sharing user and the rights and interests resource, so that the target user obtains the resource rights and interests resource.

[0218] It should be noted that the embodiments concerning storage media in this specification and the embodiments concerning the rights-sharing processing method in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding method described above, and the repeated parts will not be described again.

[0219] The second type of storage medium provided in this specification is as follows:

[0220] Corresponding to the blockchain-based rights verification processing method described above, applied to the blockchain node corresponding to the server in the blockchain, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0221] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0222] Based on the redemption request sent by the server from the sharing user or the shared user, the smart contract deployed on the blockchain node is invoked to query the rights and interests resources corresponding to the service type of the rights and interests redemption request;

[0223] Check whether the rights and interests relationship of the sharing user or the shared user is recorded in the rights and interests relationship table;

[0224] If the resource status of the equity resource read from the blockchain is unused, an availability reminder is sent to the server, and the equity resource is cancelled upon receiving a cancellation confirmation request from the server.

[0225] The system returns the rights and interests redemption results to the server and updates the redemption status of the rights and interests resources to the blockchain.

[0226] It should be noted that the embodiments concerning storage media in this specification and the embodiments concerning blockchain-based rights verification processing methods in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0227] The third storage medium embodiment provided in this specification is as follows:

[0228] Corresponding to the blockchain-based rights verification processing method described above, applied to a server, and based on the same technical concept, one or more embodiments of this specification also provide a storage medium.

[0229] The storage medium provided in this embodiment is used to store computer-executable instructions, which, when executed, implement the following process:

[0230] Obtain service requests for a service type submitted by the sharing user or the user being shared with, and send the service requests as rights verification requests to the blockchain nodes in the blockchain;

[0231] Receive the availability notification of rights and resources sent by the blockchain node and send it to the sharing user or the user to whom the resources are shared;

[0232] After settlement is completed based on the equity resources and the settlement is successful, a verification confirmation request is sent to the blockchain node.

[0233] It should be noted that the embodiments concerning storage media in this specification and the embodiments concerning blockchain-based rights verification processing methods in this specification are based on the same inventive concept. Therefore, the specific implementation of this embodiment can be referred to the implementation of the corresponding methods described above, and the repeated parts will not be described again.

[0234] The foregoing has described specific embodiments of this specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recited in the claims may be performed in a different order than that shown in the embodiments and may still achieve the desired result. Furthermore, the processes depicted in the drawings do not necessarily require the specific or sequential order shown to achieve the desired result. In some embodiments, multitasking and parallel processing are possible or may be advantageous.

[0235] In the 1930s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many improvements to the methodology today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that an improvement to the methodology cannot be implemented using a hardware physical module. For example, a Programmable Logic Device (PLD) (e.g., a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0236] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0237] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0238] For ease of description, the above apparatus is described by dividing it into various functional units. Of course, when implementing the embodiments of this specification, the functions of each unit can be implemented in one or more software and / or hardware.

[0239] Those skilled in the art will understand that one or more embodiments of this specification can be provided as a method, system, or computer program product. Therefore, one or more embodiments of this specification may take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this specification may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0240] This specification is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this specification. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create a machine for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0241] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0242] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0243] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0244] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0245] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media 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 memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0246] It should also be noted that 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 limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0247] One or more embodiments of this specification can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a particular task or implement a particular abstract data type. One or more embodiments of this specification can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0248] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to interchangeably. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions in the method embodiments.

[0249] The above description is merely an embodiment of this document and is not intended to limit the scope of this document. Various modifications and variations can be made to this document by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this document should be included within the scope of the claims of this document.

Claims

1. A method for processing rights sharing, comprising: Obtain a sharing request from a sharing user to share rights and resources with at least one recipient user; If the trusted verification of at least one shared user passes and the resource parameters of the rights and interests resource meet the sharing conditions, the at least one shared user is added to the rights and interests relationship between the sharing user and the rights and interests resource, so that the at least one shared user and the sharing user obtain the resource permissions of the rights and interests resource.

2. The rights-sharing processing method according to claim 1 further includes: If it is detected that the sharing user or the user whose rights and interests are shared submits an access request for the rights and interests resource, then query the resource status of the rights and interests resource; Based on the resource status, the resource tag of the benefit resource is displayed to the sharing user or the user to whom the resource is shared.

3. The rights-sharing processing method according to claim 1 further includes: If it is detected that the sharing user or the shared user submits a service request for the recommended project corresponding to the rights and benefits resource, query the resource status of the rights and benefits resource; If the resource is in an unused state, a resource reminder is sent to the sharing user or the user to whom the resource is shared.

4. The rights-sharing processing method according to claim 3, after the step of sending a resource reminder to the sharing user or the shared user is executed, it further includes: Settlement processing is performed based on the settlement request submitted by the sharing user or the shared user based on the rights and resources. Upon successful settlement, the rights and interests platform will verify and cancel the rights and interests resources.

5. The rights-sharing processing method according to claim 4, wherein the settlement processing includes: According to the settlement request, a cancellation request is sent to the rights and interests platform, and the settlement amount of the rights and interests resources is obtained from the rights and interests platform; The actual settlement amount is determined based on the resource settlement amount and the settlement amount in the settlement request, and the payment platform transfers funds according to the actual settlement amount. After the payment platform successfully transfers funds, it sends a verification confirmation reminder to the rights platform, so that the rights platform can mark the resource status of the rights resource as used based on the verification confirmation reminder.

6. The rights-sharing processing method according to claim 1, before executing the step of obtaining a sharing request from a sharing user to share rights resources with at least one shared user, further comprising: Based on the sharing user's access request for the recommended project, the sharing user is verified for trustworthiness. If the verification passes, a resource tag for the recommended benefits resource will be sent to the sharing user; A referral benefit relationship is established between the sharing user and the referral benefit resource based on the sharing user's request to claim the referral benefit resource. Wherein, the rights and interests resources are part or all of the recommended rights and interests resources, and the recommended rights and interests relationships include the rights and interests relationships.

7. The rights-sharing processing method according to claim 1, wherein the number of rights resources is multiple; The method further includes: If the sharing user or the shared user submits an access request for the rights and benefits resource, query the resource status of the rights and benefits resource and obtain the remaining rights and benefits resources whose resource status is unused; Based on the quantity of remaining rights and benefits resources, the resource tags of the rights and benefits resources are displayed to the sharing user or the user to whom the rights and benefits resources are shared.

8. The rights-sharing processing method according to claim 1, wherein the resource parameters include: Resource type, sharing time and / or resource status; Accordingly, the determination of whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions includes: Determine whether the resource type of the equity resource is a shareable resource type, determine whether the sharing time is within the sharing time interval, and / or determine whether the resource status of the equity resource is unused.

9. The rights-sharing processing method according to claim 1, wherein the at least one user to whom rights are shared is determined in the following manner: If the sharing user triggers the sharing control of the rights and benefits resources, query whether the sharing user has configured a default sharing user; If so, the default shared user is determined as the at least one shared user.

10. The rights-sharing processing method according to claim 9, if the result of the query to see if the sharing user has configured the default shared user is no, the following sub-steps are performed: A user selection page is generated based on the shared user's friend list; If the sharing user triggers the sharing confirmation control configured on the user selection page, at least one user selected by the sharing user through the user selection page, and / or at least one user queried and selected by the sharing user through the user selection page, is determined to be the at least one shared user.

11. The rights-sharing processing method according to claim 1, if the resource parameters of the rights resource do not meet the sharing conditions, the following operation is performed: Read the reason for sharing failure based on the judgment result; Based on the reason for the sharing failure, a sharing failure reminder is sent to the sharing user.

12. A blockchain-based rights and interests verification processing method, applied to a blockchain node in a blockchain, wherein the blockchain is used to store a rights and interests relationship table and the resource status of rights and interests resources, wherein the rights and interests relationship in the rights and interests relationship table is created after the rights and interests resources are claimed and updated after the rights and interests resources are shared, and both the sharing user and the shared user obtain the resource rights of the rights and interests resources after the rights and interests resources are shared. The method includes: Based on the revocation request sent by the server from the sharing user or the shared user, the smart contract deployed by the blockchain node is invoked to query the rights and resources corresponding to the service type of the revocation request; Check whether the rights and interests relationship of the sharing user or the shared user is recorded in the rights and interests relationship table; If the resource status of the equity resource read from the blockchain is unused, then an availability reminder is sent to the server. Receive and, based on the settlement request from the server according to the settlement request from the sharing user or the shared user, and if the settlement is successful, send a verification confirmation request to verify the rights and resources; The server returns the rights and benefits verification result, and the server sends a verification reminder to the sharing user or the user to whom the rights and benefits are shared based on the verification result.

13. The blockchain-based rights verification processing method according to claim 12, wherein the rights relationship is created in the following manner: Based on the sharing user's access request for the service type, the sharing user is verified for trustworthiness. If the verification passes, recommended benefits and resources will be sent to the sharing user. The recommended rights and benefits resources include the rights and benefits resources; The rights and interests relationship between the sharing user and the rights and interests resource is established based on the sharing user's request to claim the rights and interests resource.

14. The blockchain-based rights verification processing method according to claim 12, wherein the rights relationship is updated in the following manner: Obtain a sharing request from the sharing user to share the rights and resources with at least one recipient user; Based on the sharing request, a trusted verification is performed on the at least one shared user to obtain a user set consisting of the shared users that have passed the verification. Determine whether the resource parameters of the equity resource meet the corresponding sharing conditions; If so, the user being shared with is added to the rights and interests relationship between the sharing user and the rights and interests resource to update the rights and interests relationship.

15. The blockchain-based rights verification processing method according to claim 12, wherein the number of rights resources is multiple; Accordingly, the availability alert is sent to the server in the following manner: Read the resource status of the equity resources from the blockchain to obtain the remaining equity resources whose resource status is unused; The availability alert is sent to the server based on the amount of remaining equity resources.

16. A blockchain-based rights verification processing method, applied to a server, comprising: Obtain service requests for a service type submitted by the sharing user or the user being shared with, and send the service requests as rights verification requests to the blockchain nodes in the blockchain; The system receives a notification from the blockchain node indicating the availability of rights and resources and sends it to either the sharing user or the user to whom the rights and resources are shared; after the rights and resources are shared, both the sharing user and the user to whom the rights and resources are shared acquire the resource permissions for the rights and resources. Settlement processing is performed based on the settlement request submitted by the sharing user or the shared user based on the rights and resources, and a verification confirmation request is sent to the blockchain node if the settlement is successful. Based on the rights and interests verification results returned by the blockchain node, a verification reminder is sent to the sharing user or the user to whom the information is shared.

17. A rights-sharing processing device, comprising: The acquisition module is configured to acquire sharing requests from sharing users who intend to share their rights and resources with at least one shared user. The addition module is configured to add the at least one shared user to the rights and interests relationship between the sharing user and the rights and interests resource when the trusted verification of the at least one shared user is passed and the resource parameters of the rights and interests resource meet the sharing conditions, so that the at least one shared user obtains the resource permissions of the rights and interests resource.

18. A blockchain-based rights verification processing device, operating on a blockchain node in the blockchain, wherein the blockchain is used to store a rights relationship table and the resource status of rights resources, wherein the rights relationship in the rights relationship table is created after the rights resources are claimed and updated after the rights resources are shared, and both the sharing user and the shared user obtain the resource rights of the rights resources after the rights resources are shared. The device includes: The query module is configured to query the rights and resources corresponding to the service type of the revocation request by calling the smart contract deployed on the blockchain node based on the revocation request sent by the sharing user or the sharing user. The detection module is configured to detect whether the rights and interests relationship table records the rights and interests relationship between the sharing user and the shared user; If the resource status of the equity resource read in the blockchain is unused, the reversal module is run. The reversal module is configured to send an availability reminder to the server, receive and process the settlement request of the sharing user or the shared user according to the settlement request of the server, and reversal the equity resource if the settlement is successful. The update module is configured to return the rights verification result to the server, and the server sends a verification reminder to the sharing user or the shared user.

19. A blockchain-based rights verification processing device, comprising: The service request receiving module is configured to obtain service requests for a service type submitted by the sharing user or the user being shared with, and send the service request as a rights verification request to the blockchain node in the blockchain. The availability notification receiving module is configured to receive availability notifications of equity resources sent by the blockchain node and send them to the sharing user or the user to whom the equity resources are shared; after the equity resources are shared, both the sharing user and the user to whom the equity resources are shared obtain resource permissions for the equity resources; The reversal request module is configured to process settlement requests based on the rights and resources submitted by the sharing user or the shared user, and send a reversal confirmation request to the blockchain node if the settlement is successful; and send a reversal reminder to the sharing user or the shared user based on the rights and resources reversal result returned by the blockchain node.

20. A rights-sharing processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Obtain a sharing request from a sharing user to share rights and resources with at least one recipient user; If the trusted verification of at least one shared user passes and the resource parameters of the rights and interests resource meet the sharing conditions, the at least one shared user is added to the rights and interests relationship between the sharing user and the rights and interests resource, so that the at least one shared user and the sharing user obtain the resource permissions of the rights and interests resource.

21. A blockchain-based rights verification and processing device, wherein the blockchain is used to store a rights relationship table and the resource status of rights resources, wherein the rights relationship in the rights relationship table is created after the rights resources are claimed and updated after the rights resources are shared, and both the sharing user and the shared user obtain the resource rights of the rights resources after the rights resources are shared. The device includes: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Based on the revocation request sent by the server from the sharing user or the shared user, the smart contract deployed on the blockchain node is invoked to query the rights and resources corresponding to the service type of the revocation request; Check whether the rights and interests relationship of the sharing user or the shared user is recorded in the rights and interests relationship table; If the resource status of the equity resource read from the blockchain is unused, then an availability reminder is sent to the server. Receive and, based on the settlement request from the server according to the settlement request from the sharing user or the shared user, and if the settlement is successful, send a verification confirmation request to verify the rights and resources; The server returns the rights and benefits verification result, and the server sends a verification reminder to the sharing user or the user to whom the rights and benefits are shared based on the verification result.

22. A blockchain-based rights verification processing device, comprising: processor; as well as, A memory configured to store computer-executable instructions, which, when executed, cause the processor to: Obtain the service request for the service type submitted by the sharing user or the user being shared with, and send the service request as a verification request to the blockchain node in the blockchain; The system receives a notification from the blockchain node indicating the availability of rights and resources and sends it to either the sharing user or the user to whom the rights and resources are shared; after the rights and resources are shared, both the sharing user and the user to whom the rights and resources are shared acquire the resource permissions for the rights and resources. Settlement processing is performed based on the settlement request submitted by the sharing user or the shared user based on the rights and resources, and a verification confirmation request is sent to the blockchain node if the settlement is successful. Based on the rights and interests verification results returned by the blockchain node, a verification reminder is sent to the sharing user or the user to whom the information is shared.

23. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Obtain a sharing request from a sharing user to share rights and resources with at least one recipient user; If the trusted verification of at least one shared user passes and the resource parameters of the rights and interests resource meet the sharing conditions, the at least one shared user is added to the rights and interests relationship between the sharing user and the rights and interests resource, so that the at least one shared user and the sharing user obtain the resource permissions of the rights and interests resource.

24. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Based on the revocation request sent by the server from the sharing user or the shared user, the smart contract deployed on the blockchain node is invoked to query the rights and resources corresponding to the service type of the revocation request; after the rights and resources are shared, both the sharing user and the shared user obtain the resource permissions of the rights and resources. Check whether the rights and interests relationship table stored in the blockchain records the rights and interests relationship of the sharing user or the sharing user; If the resource status of the equity resource read from the blockchain is unused, then an availability reminder is sent to the server. Receive and, based on the settlement request from the server according to the settlement request from the sharing user or the shared user, and if the settlement is successful, send a verification confirmation request to verify the rights and resources; The server returns the rights and benefits verification result, and the server sends a verification reminder to the sharing user or the user to whom the rights and benefits are shared based on the verification result.

25. A storage medium for storing computer-executable instructions, which, when executed, perform the following process: Obtain the service request for the service type submitted by the sharing user or the user being shared with, and send the service request as a verification request to the blockchain node in the blockchain; The system receives a notification from the blockchain node indicating the availability of rights and resources and sends it to either the sharing user or the user to whom the rights and resources are shared; after the rights and resources are shared, both the sharing user and the user to whom the rights and resources are shared acquire the resource permissions for the rights and resources. Settlement processing is performed based on the settlement request submitted by the sharing user or the shared user based on the rights and resources, and a verification confirmation request is sent to the blockchain node if the settlement is successful. Based on the rights and interests verification results returned by the blockchain node, a verification reminder is sent to the sharing user or the user to whom the information is shared.

Images