WO2022237574A1 - 权益分享处理的方法及装置 - Google Patents

权益分享处理的方法及装置 Download PDF

Info

Publication number
WO2022237574A1
WO2022237574A1 PCT/CN2022/090142 CN2022090142W WO2022237574A1 WO 2022237574 A1 WO2022237574 A1 WO 2022237574A1 CN 2022090142 W CN2022090142 W CN 2022090142W WO 2022237574 A1 WO2022237574 A1 WO 2022237574A1
Authority
WO
WIPO (PCT)
Prior art keywords
equity
user
sharing
resource
resources
Prior art date
Application number
PCT/CN2022/090142
Other languages
English (en)
French (fr)
Inventor
汪翔
Original Assignee
支付宝(杭州)信息技术有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 支付宝(杭州)信息技术有限公司 filed Critical 支付宝(杭州)信息技术有限公司
Priority to US18/560,048 priority Critical patent/US20240232932A1/en
Publication of WO2022237574A1 publication Critical patent/WO2022237574A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0224—Discounts or incentives, e.g. coupons or rebates based on user history
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00—Commerce
    • G06Q30/02—Marketing; Price estimation or determination; Fundraising
    • G06Q30/0207—Discounts or incentives, e.g. coupons or rebates
    • G06Q30/0239—Online discounts or incentives

Definitions

  • This document relates to the technical field of data processing, and in particular to a method and device for processing rights and interests.
  • the method for processing rights and interests includes: obtaining a sharing request from a sharing user to share rights and interests resources with at least one shared user. Perform credible verification on the at least one shared user based on the sharing request, and obtain a user set composed of target users who pass the verification. Judging whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; if so, adding the target user to the rights and interests relationship between the sharing user and the rights and interests resources, so that the target users can obtain the rights and interests of the rights and interests resources Resource permissions.
  • One or more embodiments of this specification provide a block chain-based equity write-off processing method, including: according to the write-off request of the sharing user or the shared user sent by the server, invoking the intelligence deployed by the block chain node
  • the contract queries the equity resource corresponding to the service type of the equity write-off request. Detect whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table; if so, if the resource status of the equity resource read in the blockchain is unused, then send the The server sends an availability reminder, and writes off the equity resource when receiving the write-off confirmation request sent by the server. Return the equity write-off result to the server, and update the write-off status of the equity resource to the blockchain.
  • One or more embodiments of this specification provide another block chain-based equity write-off processing method, including: obtaining a service request for a service type submitted by a sharing user or a shared user, and using the service request as an equity
  • the write-off request is sent to the blockchain nodes in the blockchain.
  • a write-off confirmation request is sent to the blockchain node.
  • an equity sharing processing device including: an acquisition module configured to acquire a sharing request from a sharing user to share equity resources with at least one shared user.
  • the verification module is configured to perform credible verification on the at least one shared user based on the sharing request, and obtain a user set composed of target users who pass the verification.
  • the judging module is configured to judge whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; if so, run the adding module, and the adding module is configured to add the target user to the sharing user and the rights and interests In the rights and interests relationship of resources, the target user can obtain the resource authority of the rights and interests resources.
  • One or more embodiments of this specification provide a blockchain-based rights and interests write-off processing device, including: a query module configured to call the area
  • the smart contract deployed by the block chain node queries the equity resource corresponding to the service type of the equity write-off request.
  • the detection module is configured to detect whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table; if so, if the resource status of the equity resource read in the blockchain is unused state, running the write-off module, and the write-off module is configured to send an available reminder to the server, and write off the equity resource when receiving the write-off confirmation request sent by the server.
  • the update module is configured to return the equity write-off result to the server, and update the write-off status of the equity resource to the block chain.
  • One or more embodiments of this specification provide another block chain-based equity write-off processing device, including: a service request receiving module configured to obtain a service request for a service type submitted by a sharing user or a shared user, And the service request is sent to the blockchain node in the blockchain as an equity write-off request.
  • the available reminder receiving module is configured to receive the available reminder of the rights and interests resources sent by the blockchain node and send it to the sharing user or the shared user.
  • the write-off request module is configured to send a write-off confirmation request to the block chain node after the settlement is performed based on the equity resources and the settlement is successful.
  • One or more embodiments of the present specification provide a benefit-sharing processing device, including: a processor; and a memory configured to store computer-executable instructions that, when executed, cause the processor to : Obtain a sharing request from the sharing user to share the rights and interests resources with at least one shared user. Perform credible verification on the at least one shared user based on the sharing request, and obtain a user set composed of target users who pass the verification. Judging whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; if so, adding the target user to the rights and interests relationship between the sharing user and the rights and interests resources, so that the target users can obtain the rights and interests of the rights and interests resources Resource permissions.
  • One or more embodiments of this specification provide a block chain-based equity write-off processing device, including: a processor; and a memory configured to store computer-executable instructions, and the computer-executable instructions are executed
  • the processor : according to the write-off request of the sharing user or the shared user sent by the server, invokes the smart contract deployed by the blockchain node to query the equity resource corresponding to the service type of the equity write-off request. Detect whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table; if so, if the resource status of the equity resource read in the blockchain is unused, then send the The server sends an availability reminder, and writes off the equity resource when receiving the write-off confirmation request sent by the server. Return the equity write-off result to the server, and update the write-off status of the equity resource to the blockchain.
  • One or more embodiments of this specification provide another block chain-based equity write-off processing device, including: a processor; and a memory configured to store computer-executable instructions, the computer-executable instructions being executed During execution, the processor: acquires a service request for a service type submitted by a sharing user or a shared user, and sends the service request to a blockchain node in the blockchain as an equity write-off request. Receive the available reminder of the rights and interests resources sent by the block chain node and send it to the sharing user or the shared user. After settlement is performed based on the equity resources and the settlement is successful, a write-off confirmation request is sent to the blockchain node.
  • One or more embodiments of this specification provide a first storage medium, which is used to store computer-executable instructions.
  • the computer-executable instructions When the computer-executable instructions are executed, the following process is implemented: acquire a sharing user and transfer rights and interests resources to at least one shared user A share request to make a share. Perform credible verification on the at least one shared user based on the sharing request, and obtain a user set composed of target users who pass the verification. Judging whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; if so, adding the target user to the rights and interests relationship between the sharing user and the rights and interests resources, so that the target users can obtain the rights and interests of the rights and interests resources Resource permissions.
  • One or more embodiments of this specification provide a second storage medium, which is used to store computer-executable instructions.
  • the computer-executable instructions implement the following process: Cancellation request, call the smart contract deployed by the blockchain node to query the equity resource corresponding to the service type of the equity cancellation request. Detect whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table; if so, if the resource status of the equity resource read in the blockchain is unused, then send the The server sends an availability reminder, and writes off the equity resource when receiving the write-off confirmation request sent by the server. Return the equity write-off result to the server, and update the write-off status of the equity resource to the blockchain.
  • One or more embodiments of this specification provide a third storage medium, which is used to store computer-executable instructions.
  • the following process is implemented: obtain the service type submitted by the sharing user or the shared user service request, and send the service request to the blockchain nodes in the blockchain as an equity write-off request.
  • a write-off confirmation request is sent to the blockchain node.
  • Fig. 1 is a processing flowchart of a method for processing rights and interests provided by one or more embodiments of this specification;
  • FIG. 2 is a method for processing rights and interests applied to a multi-user sharing scenario provided by one or more embodiments of this specification;
  • Fig. 3 is a processing flow chart of a block chain-based equity write-off processing method provided by one or more embodiments of this specification;
  • FIG. 4 is a processing flow chart of another blockchain-based equity write-off processing method provided by one or more embodiments of this specification;
  • Fig. 5 is a schematic diagram of a benefit sharing processing device provided by one or more embodiments of this specification.
  • Fig. 6 is a schematic diagram of a block chain-based equity write-off processing device provided by one or more embodiments of this specification;
  • Fig. 7 is a schematic diagram of another block chain-based equity write-off processing device provided by one or more embodiments of this specification.
  • Fig. 8 is a schematic structural diagram of a benefit sharing processing device provided by one or more embodiments of this specification.
  • Fig. 9 is a schematic structural diagram of a block chain-based equity write-off processing device provided by one or more embodiments of this specification.
  • Fig. 10 is a schematic structural diagram of another block chain-based equity write-off processing device provided by one or more embodiments of this specification.
  • FIG. 1 An embodiment of a method for processing rights and interests provided in this specification: refer to Figure 1, which shows a processing flow chart of a method for processing rights and interests provided by this embodiment, and refer to Figure 2, which shows a process flow chart of a method for processing rights and interests provided by this embodiment.
  • Figure 1 shows a processing flow chart of a method for processing rights and interests provided by this embodiment
  • Figure 2 shows a process flow chart of a method for processing rights and interests provided by this embodiment.
  • the benefit sharing processing method provided in this embodiment specifically includes steps S102 to S108.
  • Step S102 obtaining a sharing request from the sharing user to share the rights and interests resources with at least one shared user.
  • this embodiment provides The rights and interests sharing processing method, through the way that the user who has received the rights and interests resources shares the rights and interests resources with other users, realizes the use of rights and interests resources by multiple accounts. Specifically, the sharing user chooses the shared user to share the rights and interests resources.
  • the shared user When the credible verification of the shared user passes and the shared equity resource meets the sharing conditions, the shared user will be added to the equity relationship between the sharing user and the equity resource, so that both the sharing user and the shared user can obtain the resource of the equity resource To achieve greater utilization of rights and interests resources and improve the utilization rate of rights and interests resources.
  • the sharing users mentioned in this embodiment include users who receive the rights and interests resources and share the rights and interests resources received with other users, and the other users who are shared are the shared users.
  • the rights and interests resources mentioned above include targets with economic value or other dimensional value provided by the recommended project to users, such as cash red envelopes, coupons, cycle cards, etc. It should be noted that after users receive rights and interests resources, they can view and use rights and interests Resources. In addition, rights and interests resources can be issued to user accounts so that users can use them in specific scenarios or channels.
  • the recommended items refer to service items that increase user participation by distributing rights and interests resources to users, such as public transportation travel promotion activities, shared vehicle travel promotion activities, and the like.
  • the sharing request includes the resource label of the rights and interests resource, the user ID of the sharing user, the user ID of the shared user and/or the sharing time; in addition, it may also include other information that needs to be processed by the server. The example is not limited here.
  • the sharing user wants to share the rights and interests resources with the shared users, he needs to obtain the rights and interests resources first.
  • users to avoid resource loss, in an optional implementation mode provided by this embodiment, in the process of distributing rights and interests resources to sharing users, credible verification is performed on the sharing users, and the credible verification passes Establish the equity relationship between sharing users and equity resources to issue equity resources to sharing users.
  • the equity resources are distributed in the following way: according to the sharing user’s access request for recommended items, the sharing user is credible Verifying; if the verification is passed, sending the resource label of the recommended benefit resource to the sharing user; establishing the recommended benefit relationship between the sharing user and the recommended benefit resource according to the sharing user's request for receiving the recommended benefit resource; Wherein, the equity resource is part or all of the recommended equity resource, and the recommended equity relationship includes the equity relationship.
  • a sharing user accesses a recommended item
  • credible verification is performed on the sharing user, and if the verification is passed, at least one corresponding recommended equity resource is queried from the equity platform according to the item identification of the recommended item, and displayed to the sharing user
  • the resource tag of the recommended equity resources establishes the equity relationship between the sharing user and the recommended equity resources to be claimed when the sharing user submits a request for claiming any one or more recommended equity resources.
  • the recommended equity resources include 5 binary cash red envelopes, 50% discount for purchasing a monthly card once, and send the corresponding resources to the sharing users label, get the user's request for receiving 5 binary cash red envelopes, establish an association relationship between user A and the 5 binary cash red envelopes, and show user A the rights to establish the association relationship when user A views it after the establishment The resource tag for the resource.
  • sharing users after sharing users receive recommended rights and interests resources, they can share all or part of the received recommended rights and interests resources.
  • sharing users need to choose the users to be shared. The process that needs to be executed when sharing improves the sharing experience of the sharing user.
  • the sharing user can set the default shared user in advance. If the user sets the default shared user in advance, then the sharing When the user triggers the sharing control of the rights and interests resources, the default shared user set by the sharing user is shared by default. There is no need for the sharing user to select the shared user again.
  • the sharing user selects and submits the shared user, wherein the shared user is acquired by the following method: when it is detected that the sharing user triggers the sharing control of the equity resource, query the sharing user Whether to configure the default shared user; if so, the default shared user is determined as the at least one shared user; if not, a user selection page is generated according to the friend list of the shared user; when the shared user is detected When the sharing confirmation control configured on the user selection page is triggered, 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 A user is the at least one shared user.
  • the sharing user when it is detected that the sharing user triggers the sharing control of the rights and interests resources, query whether the sharing user is configured with the default shared user. If so, the default shared user is used as the shared user;
  • the friend list generates a user selection page, and the friend users selected by the sharing user through the user selection page or the non-friend users queried and selected are taken as the shared users.
  • user A obtains 5 binary cash red envelopes
  • user A obtains 5 binary cash red envelopes
  • user A triggers the sharing control configured in the resource label display area of the 5 binary cash red envelopes
  • user A has not set the default to be shared
  • the user generates a user selection page according to the friend list of user A, and user A selects user B and user C in the friend list through the user selection page, and user D who is not a friend through search is selected as the shared user.
  • Step S104 performing credible verification on the at least one shared user based on the sharing request, and obtaining a user set composed of target users who pass the verification.
  • the credible verification refers to verifying whether the at least one shared user is a black and gray list user.
  • the target user refers to the shared user who passes the credible verification.
  • the user set includes at least one shared user who passes the credible verification.
  • equity resources can only be shared with the shared users when the shared user’s credible verification passes. Therefore, the shared user submitted by the sharing user is at least One time, share the rights and interests resources to the shared users who pass the credible verification.
  • Step S106 judging whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions.
  • the resource parameters include: resource type, sharing time and/or resource status. In addition, it may also include thresholds for the amount of rights and interests resources, and resource parameters are determined according to actual service requirements, which are not limited in this embodiment.
  • the judgment of whether the resource parameters of the equity resources meet the corresponding sharing conditions is mainly realized by the following method: judging whether the resource type of the equity resources is a shareable resource Type, to determine whether the sharing time is in the sharing time interval, and/or determine whether the resource status of the rights and interests resource is unused. In addition, it may also be determined whether the resource amount of the equity resource exceeds an amount threshold.
  • the target user will be added to the sharing user and rights In the relationship of rights and interests of resources.
  • user A shares 5 binary cash red envelopes with user B, user C, and user D, and after user B, user C, and user D pass the credible verification, determine the shared bicycles corresponding to the 5 binary cash red envelopes Whether the promotion activity belongs to a project that can share rights and interests; if not, return a reminder to user A that the resource type cannot be shared; if so, determine whether the sharing time of the 5 binary cash red envelopes is within the sharing time interval; Return the reminder that the current time cannot be shared, and the sharing time is from xx to xx; if so, determine whether the resource status of the 5 binary cash red envelopes is unused; if not, return a reminder that the resource has been used to user A; if so , add user B, user C, and user D to the equity relationship between user A and the 5 binary cash red envelopes.
  • Step S108 adding the target user to the equity relationship between the sharing user and the equity resource.
  • the target user is added to the equity relationship between the sharing user and the equity resource, so that the target user can obtain the resource authority of the equity resource.
  • the target user can view and use the equity resource in the account.
  • both the sharing users and the target users can view and use the rights and interests resources.
  • the resource label is displayed in the following manner: if it is detected that the sharing user or the target user submits an access request for the rights and interests resources, query the resource status of the rights and interests resources; The resource status displays the resource label of the equity resource to the sharing user or the target user.
  • the resource status of the resource resource is queried. If the resource status of the resource resource is in the used state, the resource label carrying the used mark is displayed to the sharing user or target user. If the resource If the status is unused, display the resource tag with the available flag to the sharing user or target user.
  • the sharing user or the target if there are multiple rights and interests resources, in order to improve the awareness of the use of rights and interests resources, in an optional implementation mode provided by this embodiment, if the sharing user or the target is detected The user submits an access request for the rights and interests resources, queries the resource status of the rights and interests resources, and obtains the remaining rights and interests resources whose resource status is unused; The target user displays the resource label of the equity resource.
  • user A shares 5 binary cash red envelopes with user B, user C, and user D.
  • User B wants to check the obtained rights and interests resources.
  • the resource status of the yuan cash red envelope is queried. If the resource status of the three binary cash red envelopes is used and two are unused, then the resource label with the amount of available resources of 2 will be displayed to user B.
  • the sharing user or target user can use the benefit resource when accessing the service corresponding to the benefit resource.
  • the following steps are performed: Operation: If it is detected that the sharing user or the target user submits a service request for the recommended item corresponding to the equity resource, query the resource status of the equity resource; if the resource status is unused, send a request to the The sharing user or the target user sends a resource reminder; according to the settlement request based on the equity resource submitted by the sharing user or the target user, the settlement process is performed; when the settlement is successful, the equity platform calculates the equity resource Perform resource write-off.
  • the resource status of the equity resource is queried, and if there is an equity resource whose resource status is unused, then the sharing user or target user Send a resource reminder, and then perform settlement processing according to the settlement request submitted by the sharing user or target user, and after the settlement process, the equity platform will mark the resource status of the used equity resources as used.
  • the settlement process is specifically performed in the following manner: send a write-off request to the equity platform according to the settlement request, and obtain the resource settlement of the equity resources from the equity platform amount; 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; wherein, the payment platform transfers funds to the equity
  • the platform sends a write-off confirmation reminder, so that the equity platform marks the resource status of the equity resource as used according to the write-off confirmation reminder.
  • user A shares 5 binary cash red envelopes with user B, user C, and user D, and detects that user B accesses the shared bicycle promotion activity, then queries the resource status of 5 binary cash red envelopes, and finds 3 binary cash red envelopes. If the resource status of the cash red envelope is used and the two are unused, a resource reminder of the binary cash red envelope will be sent to user B, and if the settlement request submitted by user B for the binary cash red envelope is obtained, the settlement request will be processed according to the settlement request Obtain a binary cash red envelope from the equity platform, and then calculate the actual fee that user B needs to pay based on the three yuan to be paid by user B and the binary cash red envelope, and then deduct one yuan from user B's account and transfer it to the shared bicycle In the account corresponding to the promotion activity, the resource status of the binary cash red envelope used at last is marked as used.
  • resource write-off can also be performed through the following steps: If it is detected that the sharing user or the shared user submits a recommendation corresponding to the equity resource The service request of the project, query the resource status of the rights and interests resources; if the resource status is unused, send a resource reminder to the sharing user or the target user; according to the sharing user or the target user submit Send a write-off request to the equity platform based on the settlement request of the equity resource; the equity platform marks the resource status of the equity resource as used based on the write-off request, and sends the resource settlement of the equity resource to the server Amount and write-off result; based on the write-off result, the server uses the resource settlement amount and the settlement amount in the settlement request to determine the actual settlement amount
  • the following uses the application of a rights sharing processing method provided in this embodiment in a multi-user sharing scenario as an example to further explain the rights sharing processing method provided in this embodiment. See Figure 2, the rights sharing applied to a multi-user sharing scenario
  • the processing method specifically includes step S202 to step S216.
  • Step S202 according to the sharing user's request for claiming the rights and interests resources of the shared travel service, establish the rights and interests relationship between the sharing user and the rights and interests resources.
  • Step S204 according to the sharing request of the sharing user to share the rights and interests resources to at least one shared user, perform authenticity verification on at least one shared user.
  • Step S206 after obtaining the shared users who pass the credible verification, determine whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; if so, execute step S208; if not, send a sharing failure reminder to the sharing user.
  • Step S208 adding the shared user who passes the credible verification to the equity relationship between the sharing user and the equity resource.
  • Step S210 if it is detected that the sharing user or the shared user submits a service request for the shared travel service, query the resource status of the rights and interests resources.
  • Step S212 if the resource status is unused, send a resource reminder to the sharing user or the shared user.
  • Step S214 performing settlement processing according to the settlement request submitted by the sharing user or the shared user based on the equity resource.
  • Step S216 if the settlement is successful, mark the resource status of the equity resource as used.
  • the resource status of the equity resource can be marked as used, and then the settlement process can be performed according to the equity resource.
  • the method for processing rights and interests provided by this embodiment first obtains a sharing request from a sharing user to share rights and interests resources with at least one shared user, and then performs a credible verification on at least one shared user based on the sharing request. Obtain the user set composed of target users who have passed the verification, and then judge whether the resource parameters of the equity resource meet the corresponding sharing conditions. If so, add the target user to the equity relationship between the sharing user and the equity resource, so that the target user can obtain the equity resource resource permissions to improve the utilization of equity resources.
  • Embodiment of a method for processing equity write-off based on blockchain provided in this specification refer to FIG. 3 , which shows a processing flow chart of a method for processing equity write-off based on blockchain provided in this embodiment.
  • the block chain-based equity write-off processing method provided in this embodiment is applied to block chain nodes in the block chain; the method specifically includes steps S302 to S308.
  • Step S302 According to the write-off request of the sharing user or the shared user sent by the server, call the smart contract deployed by the blockchain node to query the equity resource corresponding to the service type of the equity write-off request.
  • the block chain is used to store the resource status of the equity relationship table and the equity resource, and the equity relationship in the equity relationship table is created after the equity resource is claimed, and is updated after the equity resource is shared.
  • the sharing users mentioned in this embodiment include users who receive the rights and interests resources and share the rights and interests resources received with other users, and the other users who are shared are the shared users.
  • the rights and interests resources mentioned above include targets with economic value or other dimensional value provided by the recommended project to users, such as cash red envelopes, coupons, cycle cards, etc. It should be noted that after users receive rights and interests resources, they can view and use rights and interests Resources. In addition, rights and interests resources can be issued to user accounts so that users can use them in specific scenarios or channels.
  • the recommended items refer to service items that increase user participation by distributing rights and interests resources to users, such as public transportation travel promotion activities, shared vehicle travel promotion activities, and the like.
  • this embodiment provides According to the block chain-based rights and interests write-off processing method, after the sharing user shares the rights and interests resources with the non-shared users, the sharing user or the shared user submits a resource write-off request, an optional implementation mode provided by this embodiment Among them, the equity relationship in the equity relationship table stored in the blockchain is created in the following way: according to the sharing user’s access request for the service type, the sharing user is credibly verified; if the verification If passed, the recommended rights and interests resources are sent to the sharing user; the recommended rights and interests resources include the rights and interests resources; the rights and interests relationship between the sharing user and the rights and interests resources is established according to the sharing user's request for receiving the rights and interests resources .
  • the server when a sharing user accesses a recommended item, the server performs credible verification on the sharing user, and if the verification is passed, queries the equity platform for at least one recommended equity resource corresponding to the item ID of the recommended item, and sends the shared user Display the resource label of the recommended equity resource.
  • the sharing user submits a request for claiming any one or more recommended equity resources, establish the equity relationship between the sharing user and the recommended equity resources that need to be claimed. After the equity relationship is established, Send the equity relationship to the blockchain node, so that the blockchain node records the equity relationship in the equity relationship table and uploads it to the blockchain for storage.
  • the server can also perform credible verification on the sharing user when it detects that the sharing user accesses the recommended item, and if the verification is passed, send the user ID of the sharing user and the resource tag of the rights and interests resource to Blockchain node:
  • the blockchain node invokes the deployed smart contract to establish the equity relationship between shared users and equity resources and records it in the equity relationship table, and then uploads the equity relationship table to the blockchain for storage.
  • the sharing user after the sharing user receives the recommended equity resources, they can share all or part of the received recommended equity resources.
  • the sharing user needs to choose the shared user.
  • the security of the shared user can only be shared with the shared user if the shared user passes the credible verification. Therefore, when the shared user submits at least one shared user, the shared user who passes the credible verification Users share rights and interests resources. In the case of credible verification of the shared user and the verification is passed, the rights and interests relationship in the rights and interests relationship table is updated.
  • the rights and interests relationship is updated in the following way: Get The sharing user makes a sharing request for sharing the rights and interests resources to at least one shared user; based on the sharing request, performs a credible verification on the at least one shared user, and obtains the shared resources that pass the verification. A user set composed of users; judging whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; The relationship is updated.
  • the shared user is added to the equity relationship between the sharing user and the equity resource, so that the shared user can obtain the resource authority of the equity resource, and after obtaining the resource authority, can view and use the equity resource in the account.
  • the equity resources can be shared with the shared users only when the shared users pass the credible verification. Therefore, when the shared user submits at least one shared user, the Shared users who pass the credible verification share rights and interests resources.
  • the server After the server performs credible verification on at least one shared user according to the sharing request and obtains the user set composed of the shared users who pass the verification, it judges whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions.
  • the sharing user is added to the equity relationship between the sharing user and the equity resource, and then the updated equity relationship is sent to the blockchain node, and 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 thresholds for the amount of rights and interests resources, and resource parameters are determined according to actual service requirements, which are not limited in this embodiment.
  • the server when the server receives the sharing request from the sharing user to increase the price, it will perform credible verification according to the user ID of the shared user in the sharing request, and if the verification passes In this case, the sharing information carried in the sharing request is sent to the blockchain node. After receiving the sharing information, the blockchain node invokes the smart contract deployed by the blockchain node to determine whether the resource parameters of the equity resources meet the corresponding sharing conditions.
  • the judgment of whether the resource parameters of the equity resources meet the corresponding sharing conditions is mainly realized by the following methods: judging whether the resource type of the equity resources is a shareable resource type, judging whether the sharing time is in the sharing time interval, and/or Or judge whether the resource state of the rights and interests resource is an unused state. In addition, it may also be determined whether the resource amount of the equity resource exceeds an amount threshold. Specifically, it may be a judgment on all of the above, or it may be a judgment on any one or more of them. If it is determined that the resource parameters meet the corresponding sharing conditions, the result of successful sharing is sent to the server, and the shared user is added to the equity relationship between the sharing user and the equity resource, so as to update the equity relationship in the equity relationship table. After receiving the successful sharing result, the server sends the resource tags of the rights and interests resources to the sharing user and the shared user.
  • sharing users can share all or part of the received recommended rights and interests resources.
  • sharing users need to choose the users to be shared. The process that needs to be executed when sharing resources improves the sharing experience of the sharing user.
  • the sharing user can set the default shared user in advance. The default shared user set by the sharing user is used for sharing. There is no need for the sharing user to select the shared user again. If the sharing user does not set the default shared user, the sharing user needs to select and submit when the sharing user triggers the sharing control of the rights and interests resources.
  • the shared user wherein, the shared user is obtained by the following method: in the case of detecting that the shared user triggers the sharing control of the equity resource, query whether the shared user is configured as a default shared user; The default shared user is determined to be the at least one shared user; if not, a user selection page is generated according to the friend list of the shared user; when the sharing confirmation control configured on the user selection page is detected to be triggered by the shared user In this case, it is determined that 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 the at least one shared user. In addition, due to different types of resources, different sharing times, or other factors, the sharing may fail. Whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions and the execution result after the step is no, read the reason for the sharing failure according to the judgment result; based on the reason for the sharing failure, send a sharing failure reminder to the sharing user.
  • the sharing user when it is detected that the sharing user triggers the sharing control of the rights and interests resources, query whether the sharing user is configured with the default shared user. If so, the default shared user is used as the shared user;
  • the friend list generates a user selection page, and the friend users selected by the sharing user through the user selection page or the non-friend users queried and selected are taken as the shared users.
  • Step S304 detecting whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table.
  • the server After determining the corresponding equity resource, check whether the user who submitted the write-off request has an equity relationship with the equity resource. If so, it indicates that the user can use the equity resource. If not, the user cannot use the equity resource.
  • equity resources After the equity relationship is found, the resource status of the equity resource is queried from the blockchain. If the resource status is unused, a reminder of the availability of the equity resource is sent to the server. Based on the available reminder, the server displays the resource label of the benefit resource to the sharing user or the shared user.
  • an available reminder is sent to the user in the following way: from the The block chain reads the resource status of the rights and interests resources, and obtains the remaining rights and interests resources whose resource status is unused; sends the availability reminder to the server based on the quantity of the remaining rights and interests resources.
  • Step S306 sending an availability reminder to the server, and canceling the equity resource when receiving the cancellation confirmation request sent by the server.
  • the server after sending an availability reminder to the server, the server sends a write-off confirmation request to the blockchain node after the settlement is performed based on the equity resources and the settlement is successful. Specifically, the server performs settlement processing according to the settlement request based on the equity resource submitted by the sharing user or the target user, and sends a write-off confirmation request to the blockchain node if the settlement is successful.
  • the blockchain marks the resource status of the equity resource as used based on the write-off confirmation request.
  • Step S308 returning the equity write-off result to the server, and updating the write-off status of the equity resource to the blockchain.
  • the write-off result is returned to the server, and the server sends a write-off reminder to the sharing user or the shared user based on the write-off result; the blockchain node uploads the updated status of the rights and interests resources to the blockchain for storage.
  • the server sends a write-off confirmation request to the blockchain node after the settlement is performed based on the equity resource and the settlement is successful.
  • the server performs settlement processing according to the settlement request based on the equity resource submitted by the sharing user or the target user, and sends a write-off confirmation request to the blockchain node if the settlement is successful.
  • the blockchain marks the resource status of the equity resource as used based on the write-off confirmation request.
  • resource write-off can also be performed through the following steps: If the server detects that the sharing user or the shared user submits the corresponding Recommend the service request of the project, and send the service request to the blockchain node; the blockchain node queries the resource status of the equity resource; if the resource status is unused, send a resource reminder to the server, so that the server sends to the sharing user or the shared user; the server sends a write-off request to the block chain node according to the settlement request based on the equity resource submitted by the sharing user or the shared user request; the blockchain node marks the resource status of the equity resource as used based on the write-off request, and sends the resource settlement amount and write-off result of the equity resource to the server; the
  • both the sharing user and the shared user can view and use the rights and interests resources.
  • the following methods are used to view the rights and interests resources: Label display: if it is detected that the sharing user or the shared user submits an access request for the rights and interests resources, query the resource status of the rights and interests resources; The shared user displays the resource label of the said rights and interests resource.
  • the sharing user or the shared user accesses the rights and interests resources, query the resource status of the rights and interests resources, if the resource status of the rights and interests resources is in the used state, then display the resource label with the used mark to the sharing user or the shared users, If the resource status is unused, display the resource label with the available flag to the sharing user or the shared user.
  • the server receives the access request of the sharing user or the shared user for the rights and interests resources, it sends the access request to the blockchain node, and the blockchain node queries the resource status of the rights and interests resources from the blockchain according to the access request and sends Sent by the server, the server displays the resource label to the sharing user or the shared user according to the resource status. For example, setting the tag of a resource whose status is in use can only be viewed but not accessed, and setting the tag of a resource whose status is in an unused status can be viewed and accessed.
  • FIG. 4 shows a processing flow chart of a blockchain-based equity write-off processing method provided in this embodiment.
  • the block chain-based equity write-off processing method provided in this embodiment is applied to a server; the method specifically includes steps S402 to S406.
  • the blockchain-based equity write-off processing method applied to the server provided in this embodiment cooperates with the above-mentioned blockchain-based equity write-off processing method applied to the blockchain node in the blockchain during execution Therefore, in the process of reading the method for processing equity write-off based on blockchain provided in this embodiment, please combine the implementation of the above-mentioned method for processing equity write-off based on blockchain applied to blockchain nodes in the blockchain example.
  • Step S402 obtain the service request for the service type submitted by the sharing user or the shared user, and send the service request to the blockchain node in the blockchain as an equity write-off request.
  • the block chain is used to store the resource status of the equity relationship table and the equity resource, and the equity relationship in the equity relationship table is created after the equity resource is claimed, and is updated after the equity resource is shared.
  • the sharing users mentioned in this embodiment include users who receive the rights and interests resources and share the rights and interests resources received with other users, and the other users who are shared are the shared users.
  • the rights and interests resources mentioned above include targets with economic value or other dimensional value provided by the recommended project to users, such as cash red envelopes, coupons, cycle cards, etc. It should be noted that after users receive rights and interests resources, they can view and use rights and interests Resources. In addition, rights and interests resources can be issued to user accounts so that users can use them in specific scenarios or channels.
  • the recommended items refer to service items that increase user participation by distributing rights and interests resources to users, such as public transportation travel promotion activities, shared vehicle travel promotion activities, and the like.
  • this embodiment provides According to the block chain-based rights and interests write-off processing method, after the sharing user shares the rights and interests resources with the non-shared users, the sharing user or the shared user submits a resource write-off request, an optional implementation mode provided by this embodiment Among them, the equity relationship in the equity relationship table stored in the blockchain is created in the following way: according to the sharing user’s access request for the service type, the sharing user is credibly verified; if the verification If passed, the recommended rights and interests resources are sent to the sharing user; the recommended rights and interests resources include the rights and interests resources; the rights and interests relationship between the sharing user and the rights and interests resources is established according to the sharing user's request for receiving the rights and interests resources .
  • the server when a sharing user accesses a recommended item, the server performs credible verification on the sharing user, and if the verification is passed, queries the equity platform for at least one recommended equity resource corresponding to the item ID of the recommended item, and sends the shared user Display the resource label of the recommended equity resource.
  • the sharing user submits a request for claiming any one or more recommended equity resources, establish the equity relationship between the sharing user and the recommended equity resources that need to be claimed. After the equity relationship is established, Send the equity relationship to the blockchain node, so that the blockchain node records the equity relationship in the equity relationship table and uploads it to the blockchain for storage.
  • the server can also perform credible verification on the sharing user when it detects that the sharing user accesses the recommended item, and if the verification is passed, send the user ID of the sharing user and the resource tag of the rights and interests resource to Blockchain node:
  • the blockchain node invokes the deployed smart contract to establish the equity relationship between shared users and equity resources and records it in the equity relationship table, and then uploads the equity relationship table to the blockchain for storage.
  • the sharing user after the sharing user receives the recommended equity resources, they can share all or part of the received recommended equity resources.
  • the sharing user needs to choose the shared user.
  • the security of the shared user can only be shared with the shared user if the shared user passes the credible verification. Therefore, when the shared user submits at least one shared user, the shared user who passes the credible verification Users share rights and interests resources. In the case of credible verification of the shared user and the verification is passed, the rights and interests relationship in the rights and interests relationship table is updated.
  • the rights and interests relationship is updated in the following way: Obtain a sharing request from the sharing user to share the rights and interests resources with at least one shared user; based on the sharing request, perform a credible verification on the at least one shared user, and obtain the verified share the user set composed of users; determine whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; if so, add the shared users to the rights and interests relationship between the sharing users and the rights and interests resources to Equity relationships are updated.
  • the shared user is added to the equity relationship between the sharing user and the equity resource, so that the shared user can obtain the resource authority of the equity resource, and after obtaining the resource authority, can view and use the equity resource in the account.
  • the equity resources can be shared with the shared users only when the shared users pass the credible verification. Therefore, when the shared user submits at least one shared user, the Shared users who pass the credible verification share rights and interests resources.
  • the server After the server performs credible verification on at least one shared user according to the sharing request and obtains the user set composed of the shared users who pass the verification, it judges whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions.
  • the sharing user is added to the equity relationship between the sharing user and the equity resource, and then the updated equity relationship is sent to the blockchain node, and 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 thresholds for the amount of rights and interests resources, and resource parameters are determined according to actual service requirements, which are not limited in this embodiment.
  • the server when the server receives the sharing request from the sharing user to increase the price, it will perform credible verification according to the user ID of the shared user in the sharing request, and if the verification passes In this case, the sharing information carried in the sharing request is sent to the blockchain node. After receiving the sharing information, the blockchain node invokes the smart contract deployed by the blockchain node to determine whether the resource parameters of the equity resources meet the corresponding sharing conditions.
  • the judgment of whether the resource parameters of the equity resources meet the corresponding sharing conditions is mainly realized by the following methods: judging whether the resource type of the equity resources is a shareable resource type, judging whether the sharing time is in the sharing time interval, and/or Or judge whether the resource state of the rights and interests resource is an unused state. In addition, it may also be determined whether the resource amount of the equity resource exceeds an amount threshold. Specifically, it may be a judgment on all of the above, or it may be a judgment on any one or more of them. If it is determined that the resource parameters meet the corresponding sharing conditions, the sharing success result is sent to the server, and the shared user is added to the equity relationship between the sharing user and the equity resource, so as to update the equity relationship in the equity relationship table. After receiving the successful sharing result, the server sends the resource tags of the rights and interests resources to the sharing user and the shared user.
  • sharing users can share all or part of the received recommended rights and interests resources.
  • sharing users need to choose the users to be shared. The process that needs to be executed when sharing resources improves the sharing experience of the sharing user.
  • the sharing user can set the default shared user in advance. The default shared user set by the sharing user is used for sharing. There is no need for the sharing user to select the shared user again. If the sharing user does not set the default shared user, the sharing user needs to select and submit when the sharing user triggers the sharing control of the rights and interests resources.
  • the shared user wherein, the shared user is obtained by the following method: in the case of detecting that the shared user triggers the sharing control of the equity resource, query whether the shared user is configured as a default shared user; The default shared user is determined to be the at least one shared user; if not, a user selection page is generated according to the friend list of the shared user; when the sharing confirmation control configured on the user selection page is detected to be triggered by the shared user In this case, it is determined that 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 the at least one shared user.
  • sharing failures may occur. Whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions and the execution result after the step is no, read the reason for the sharing failure according to the judgment result; based on the reason for the sharing failure, send a sharing failure reminder to the sharing user.
  • the sharing user when it is detected that the sharing user triggers the sharing control of the rights and interests resources, query whether the sharing user is configured with the default shared user. If so, the default shared user is used as the shared user;
  • the friend list generates a user selection page, and the friend users selected by the sharing user through the user selection page or the non-friend users queried and selected are taken as the shared users.
  • Step S404 receiving the reminder of the availability of equity resources sent by the blockchain node and sending it to the sharing user or the shared user.
  • the blockchain node after receiving the write-off request, invokes the smart contract deployed by the blockchain node to query the equity resource corresponding to the service type of the equity write-off request; after determining the corresponding equity resource, then Query whether the user who submitted the write-off request has an equity relationship with the equity resource. If yes, it indicates that the user can use the equity resource. If not, the user cannot use the equity resource. After the equity relationship is found, the resource status of the equity resource is queried from the blockchain. If the resource status is unused, a reminder of the availability of the equity resource is sent to the server. Based on the available reminder, the server displays the resource label of the benefit resource to the sharing user or the shared user.
  • the blockchain node sends an available reminder to the user in the following way: read the rights and interests from the blockchain The resource status of the resource is to obtain the remaining entitlement resources whose resource status is unused; and send the availability reminder to the server based on the quantity of the remaining entitlement resources. Send an availability reminder to the server, and write off the equity resource when receiving the write-off confirmation request sent by the server.
  • Step S406 after the settlement is performed based on the equity resources and the settlement is successful, a write-off confirmation request is sent to the blockchain node.
  • the server after sending an availability reminder to the server, the server sends a write-off confirmation request to the blockchain node after the settlement is performed based on the equity resources and the settlement is successful. Specifically, the server performs settlement processing according to the settlement request based on the equity resource submitted by the sharing user or the target user, and sends a write-off confirmation request to the blockchain node if the settlement is successful.
  • the blockchain marks the resource status of the equity resource as used based on the write-off confirmation request. Return the equity write-off result to the server, and update the write-off status of the equity resource to the blockchain.
  • the write-off result is returned to the server, and the server sends a write-off reminder to the sharing user or the shared user according to the write-off result; the blockchain node uploads the updated status of the equity resource to the blockchain for storage.
  • the server specifically performs settlement processing in the following manner: send a write-off request to the blockchain node according to the settlement request, and obtain the resource settlement of the equity resource from the blockchain node amount; 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; wherein, the payment platform transfers funds to the district after successful fund transfer
  • the block chain node sends a write-off confirmation reminder, so that the block chain node marks the resource status of the equity resource as a used state according to the write-off confirmation reminder.
  • resource write-off can also be performed through the following steps: If the server detects that the sharing user or the shared user submits the corresponding Recommend the service request of the project, and send the service request to the blockchain node; the blockchain node queries the resource status of the equity resource; if the resource status is unused, send a resource reminder to the server, so that the server sends to the sharing user or the shared user; the server sends a write-off request to the block chain node according to the settlement request based on the equity resource submitted by the sharing user or the shared user request; the blockchain node marks the resource status of the equity resource as used based on the write-off request, and sends the resource settlement amount and write-off result of the equity resource to the server; the
  • both the sharing user and the shared user can view and use the rights and interests resources.
  • the following methods are used to view the rights and interests resources: Label display: if it is detected that the sharing user or the shared user submits an access request for the rights and interests resources, query the resource status of the rights and interests resources; The shared user displays the resource label of the said rights and interests resource.
  • the sharing user or the shared user accesses the rights and interests resources, query the resource status of the rights and interests resources, if the resource status of the rights and interests resources is in the used state, then display the resource label with the used mark to the sharing user or the shared users, If the resource status is unused, display the resource label with the available flag to the sharing user or the shared user.
  • the server receives the access request of the sharing user or the shared user for the rights and interests resources, it sends the access request to the blockchain node, and the blockchain node queries the resource status of the rights and interests resources from the blockchain according to the access request and sends Sent by the server, the server displays the resource label to the sharing user or the shared user according to the resource status. For example, set the tag of a resource whose status is used to only viewable but not accessible, and set the tag of a resource whose status is unused to be both viewable and accessible.
  • FIG. 5 it shows a schematic diagram of a benefit sharing processing device provided in this embodiment.
  • the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above.
  • the device embodiments described below are illustrative only.
  • This embodiment provides a device for processing rights and interests, including: an acquisition module 502 configured to obtain a sharing request from a sharing user to share rights resources with at least one shared user; a verification module 504 configured to Request credible verification of the at least one shared user, and obtain a user set composed of target users who pass the verification; the judging module 506 is configured to judge whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; if , running the adding module 508, the adding module 508 is configured to add the target user to the equity relationship between the sharing user and the equity resource, so that the target user can obtain the resource authority of the equity resource .
  • a block chain-based equity write-off processing device provided in this specification is as follows:
  • a block chain-based equity write-off processing method is provided, which is applied to the block chain
  • the block chain node also provides a block chain-based rights and interests write-off processing device, which runs on the block chain node in the block chain, and will be described below with reference to the accompanying drawings.
  • FIG. 6 it shows a schematic diagram of a block chain-based equity write-off processing device provided in this embodiment.
  • the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above.
  • the device embodiments described below are illustrative only.
  • This embodiment provides a block chain-based equity write-off processing device, including: a query module 602, configured to call the block chain node deployment according to the share user or shared user write-off request sent by the server The smart contract queries the equity resource corresponding to the service type of the equity write-off request; the detection module 604 is configured to detect whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table; if yes, if The resource status of the rights and interests resources read in the block chain is unused, and the write-off module 606 is run.
  • a query module 602 configured to call the block chain node deployment according to the share user or shared user write-off request sent by the server
  • the smart contract queries the equity resource corresponding to the service type of the equity write-off request
  • the detection module 604 is configured to detect whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table; if yes, if The resource status of the rights and interests resources read in the block chain is unused, and the write-off module 606 is run
  • the write-off module 606 is configured to send an availability reminder to the server, and upon receiving the Write-off of the rights and interests resources when the cancellation confirmation request sent by the server; the update module 608 is configured to return the rights and interests cancellation results to the server, and update the cancellation status of the rights and interests resources to the block chain .
  • FIG. 1 Another embodiment of a block chain-based equity write-off processing device provided in this specification is as follows: In the above-mentioned embodiment, a block chain-based equity write-off processing method is provided, which is applied to a server. Correspondingly, a block chain-based equity write-off processing device is also provided, running on a server, which will be described below with reference to the accompanying drawings.
  • FIG. 7 it shows a schematic diagram of a block chain-based equity write-off processing device provided in this embodiment.
  • the description is relatively simple. For relevant parts, please refer to the corresponding description of the method embodiment provided above.
  • the device embodiments described below are illustrative only.
  • This embodiment provides a blockchain-based rights and interests write-off processing device, including: a service request receiving module 702 configured to obtain a service request for a service type submitted by a sharing user or a shared user, and send the service request It is sent to the blockchain node in the blockchain as a rights write-off request; the available reminder receiving module 704 is configured to receive the available reminder of the rights and interests resources sent by the blockchain node and send the notification to the sharing user or the The sharing user sends; the write-off request module 706, configured to send a write-off confirmation request to the block chain node after the settlement is performed based on the equity resource and the settlement is successful.
  • a service request receiving module 702 configured to obtain a service request for a service type submitted by a sharing user or a shared user, and send the service request It is sent to the blockchain node in the blockchain as a rights write-off request
  • the available reminder receiving module 704 is configured to receive the available reminder of the rights and interests resources sent by the blockchain node and send the notification to the sharing user or
  • FIG. 8 is a schematic structural diagram of a device for processing rights sharing provided by one or more embodiments of this specification.
  • a benefit sharing processing device includes: as shown in FIG. 8 , the benefit sharing processing device may have relatively large differences due to different configurations or performances, and may include one or more than one processor 801 and memory 802 , one or more stored application programs or data may be stored in the memory 802 .
  • the storage 802 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 802 may include one or more modules (not shown), and each module may include a series of computer-executable instructions in the benefit sharing processing device.
  • the processor 801 may be configured to communicate with the memory 802, and execute a series of computer-executable instructions in the memory 802 on the benefit sharing processing device.
  • the benefit sharing processing device may also include one or more power sources 803, one or more wired or wireless network interfaces 804, one or more input/output interfaces 805, one or more keyboards 806, and the like.
  • the benefit sharing processing device includes a memory, and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include one or more modules, and Each module may include a series of computer-executable instructions in a benefit-sharing processing device, and configured to be executed by one or more processors.
  • the one or more programs include computer-executable instructions for performing the following: A sharing request for sharing rights and interests resources to at least one shared user; performing credible verification on the at least one shared user based on the sharing request, and obtaining a user set composed of target users who have passed the verification; judging the rights and interests Whether the resource parameter of the resource satisfies the corresponding sharing condition; if so, adding the target user to the equity relationship between the sharing user and the equity resource, so that the target user can obtain the resource authority of the equity resource.
  • FIG. 9 is a schematic structural diagram of a blockchain-based equity write-off processing device provided by one or more embodiments of this specification.
  • a block chain-based equity write-off processing device provided in this embodiment is applied to block chain nodes in the block chain, including: as shown in Figure 9, the block chain-based equity write-off processing device can be There are relatively large differences due to different configurations or performances, and may include one or more processors 901 and memories 902, and one or more storage applications or data may be stored in the memories 902. Wherein, the storage 902 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 902 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the equity write-off processing device based on blockchain.
  • the processor 901 may be configured to communicate with the memory 902, and execute a series of computer-executable instructions in the memory 902 on the block chain-based equity write-off processing device.
  • the block chain-based equity write-off processing device may also include one or more power sources 903, one or more wired or wireless network interfaces 904, one or more input/output interfaces 905, one or more keyboards 906, and the like.
  • the block chain-based equity write-off processing device includes a memory, and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include a or more than one module, and each module may include a series of computer-executable instructions in the block chain-based equity write-off processing device, and is configured to be executed by one or more processors.
  • the one or more programs include It is used to perform the following computer-executable instructions: according to the write-off request of the sharing user or the shared user sent by the server, call the smart contract deployed by the blockchain node to query the equity resource corresponding to the service type of the equity write-off request; Detect whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table; if so, if the resource status of the equity resource read in the blockchain is unused, then send the The server sends an available reminder, and writes off the rights and interests resources when receiving the cancellation confirmation request sent by the server; returns the rights and interests cancellation result to the server, and updates the cancellation status of the rights and interests resources to the blockchain.
  • FIG. 10 is a schematic structural diagram of a block chain-based equity write-off processing device provided by one or more embodiments of this specification.
  • a block chain-based equity write-off processing device provided in this embodiment is applied to a server, including: as shown in Figure 10, the block chain-based equity write-off processing device may have a relatively large difference, may include one or more processors 1001 and memory 1002, and one or more storage application programs or data may be stored in the memory 1002.
  • the memory 1002 may be a short-term storage or a persistent storage.
  • the application program stored in the memory 1002 may include one or more modules (not shown in the figure), and each module may include a series of computer-executable instructions in the equity write-off processing device based on blockchain.
  • the processor 1001 may be configured to communicate with the memory 1002, and execute a series of computer-executable instructions in the memory 1002 on the block chain-based equity write-off processing device.
  • the block chain-based equity write-off processing device may also include one or more power sources 1003, one or more wired or wireless network interfaces 1004, one or more input/output interfaces 1005, one or more keyboards 1006, etc.
  • the block chain-based equity write-off processing device includes a memory, and one or more programs, wherein one or more programs are stored in the memory, and one or more programs may include a or more than one module, and each module may include a series of computer-executable instructions in the block chain-based equity write-off processing device, and is configured to be executed by one or more processors.
  • the one or more programs include It is used to carry out the following computer-executable instructions: obtain the service request for the service type submitted by the sharing user or the shared user, and send the service request to the blockchain node in the blockchain as a request for equity write-off; The available reminder of the rights and interests resources sent by the block chain node is sent to the sharing user or the shared user; after the settlement is made based on the rights and interests resources and the settlement is successful, a write-off confirmation request is sent to the block chain node .
  • An embodiment of a storage medium provided in this specification is as follows: corresponding to the above-described method for processing rights and interests, based on the same technical concept, one or more embodiments of this specification also provide a storage medium.
  • the storage medium provided in this embodiment is used to store computer-executable instructions, and the computer-executable instructions implement the following process when executed: obtain a sharing request from a sharing user to share rights and interests resources with at least one shared user; based on the The sharing request performs credible verification on the at least one shared user, and obtains a user set composed of target users who pass the verification; judges whether the resource parameters of the rights and interests resources meet the corresponding sharing conditions; if so, sends the target user The user is added to the equity relationship between the sharing user and the equity resource, so that the target user can obtain the resource authority of the equity resource.
  • the second storage medium embodiment provided in this specification is as follows: corresponding to a blockchain-based equity write-off processing method described above, it is 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.
  • the storage medium provided in this embodiment is used to store computer-executable instructions, and when the computer-executable instructions are executed, the following process is implemented: according to the verification request sent by the server for the sharing user or the shared user, call the block
  • the smart contract deployed by the chain node queries the equity resource corresponding to the service type of the equity write-off request; detects whether the equity relationship of the sharing user or the shared user is recorded in the equity relationship table; If the resource status of the rights and interests resources read in the block chain is unused, an available reminder is sent to the server, and the rights and interests resources are written off when the verification request sent by the server is received;
  • the server returns the equity write-off result, and updates the write-off status of the equity resource to the blockchain.
  • the third storage medium embodiment provided in this specification is as follows: Corresponding to a block chain-based equity write-off processing method described above, applied to the server, based on the same technical concept, one or more embodiments of this specification also provide A storage medium.
  • the storage medium provided in this embodiment is used to store computer-executable instructions.
  • the computer-executable instructions When executed, the following procedures are implemented: obtain a service request for a service type submitted by a sharing user or a shared user, and convert the The service request is sent to the block chain node in the block chain as a rights and interests write-off request; the available reminder of the rights and interests resources sent by the block chain node is received and sent to the sharing user or the shared user; After the above equity resources are settled and the settlement is successful, a write-off confirmation request is sent to the blockchain node.
  • the improvement of a technology can be clearly distinguished as an improvement in hardware (for example, improvements in circuit structures such as diodes, transistors, switches, etc.) or improvements in software (improvement in method flow).
  • improvements in many current method flows can be regarded as the direct improvement of the hardware circuit structure.
  • Designers almost always get the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be realized by hardware physical modules.
  • a Programmable Logic Device such as a Field Programmable Gate Array (FPGA)
  • FPGA Field Programmable Gate Array
  • HDL Hardware Description Language
  • the controller may be implemented in any suitable way, for example the controller may take the form of a microprocessor or processor and a computer readable medium storing computer readable program code (such as software or firmware) executable by the (micro)processor , logic gates, switches, application specific integrated circuits (Application Specific Integrated Circuit, ASIC), 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 Silicone Labs C8051F320, the memory controller can also be implemented as part of the control logic of the memory.
  • controller in addition to realizing the controller in a purely computer-readable program code mode, it is entirely possible to make the controller use logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded The same function can be realized in the form of a microcontroller or the like. Therefore, such a controller can be regarded as a hardware component, and the devices included in it for realizing various functions can also be regarded as structures within the hardware component. Or even, means for realizing various functions can be regarded as a structure within both a software module realizing a method and a hardware component.
  • a typical implementing device is a computer.
  • the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or Combinations of any of these devices.
  • one or more embodiments of this specification may be provided as a method, system or computer program product. Accordingly, one or more embodiments of the present description may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present description 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.) having computer-usable program code embodied therein.
  • computer-usable storage media including but not limited to disk storage, CD-ROM, optical storage, etc.
  • These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions
  • the device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.
  • a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • Memory may include non-permanent storage in computer-readable media, in the form of random access memory (RAM) and/or nonvolatile memory such as read-only memory (ROM) or flash RAM.
  • RAM random access memory
  • ROM read-only memory
  • Memory is an example of computer readable media.
  • Computer-readable media including both permanent and non-permanent, removable and non-removable media, can be implemented by any method or technology for storage of information.
  • Information may be computer readable instructions, data structures, modules of a program, 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 technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, Magnetic tape cartridge, tape disk storage or other magnetic storage device or any other non-transmission medium that can be used to store information that can be accessed by a computing device.
  • computer-readable media excludes transitory computer-readable media, such as modulated data signals and carrier waves.
  • program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types.
  • program modules may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
  • program modules may be located in both local and remote computer storage media including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Engineering & Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Finance (AREA)
  • Economics (AREA)
  • Game Theory and Decision Science (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Marketing (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Storage Device Security (AREA)

Abstract

本说明书实施例提供了权益分享处理方法及装置，其中，一种权益分享处理方法包括：获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求；基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集；判断所述权益资源的资源参数是否满足对应的分享条件；若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。

Description

权益分享处理的方法及装置 技术领域
本文件涉及数据处理技术领域，尤其涉及一种权益分享处理方法及装置。
背景技术
随着互联网技术的快速发展，网络消费得到了广泛的普及，越来越多的商家通过网络平台进行商品的销售，同时也有各种各样网络平台的出现，因此，各个网络平台之间以及各个商家之间的竞争也日益加剧，为了提高自身的竞争力，网络平台或者商家经常会开展一些线上营销活动，如向参加营销活动的用户发放红包、优惠券、赠品券等权益，由此可见，实现权益资源的更大化利用，提升权益资源的使用率已经尤为重要。
发明内容
本说明书一个或多个实施例提供了一种权益分享处理方法。所述权益分享处理方法，包括：获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求。基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集。判断所述权益资源的资源参数是否满足对应的分享条件；若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
本说明书一个或多个实施例提供了一种基于区块链的权益核销处理方法，包括：根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源。检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销。向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
本说明书一个或多个实施例提供了另一种基于区块链的权益核销处理方法，包括：获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送。接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送。在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
本说明书一个或多个实施例提供了一种权益分享处理装置，包括：获取模块，被配置为获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求。校验模块，被配置为基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集。判断模块，被配置为判断所述权益资源的资源参数是否满足对应的分享条件；若是，运行添加模块，所述添加模块，被配置为将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
本说明书一个或多个实施例提供了一种基于区块链的权益核销处理装置，包括：查询模块，被配置为根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源。检测模块，被配置为检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，运行核销模块，所述核销模块，被配置为则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销。更新模块，被配置为向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
本说明书一个或多个实施例提供了另一种基于区块链的权益核销处理装置，包括：服务请求接收模块，被配置为获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送。可用提醒接收模块，被配置为接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送。核销请求模块，被配置为在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
本说明书一个或多个实施例提供了一种权益分享处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求。基于所述 分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集。判断所述权益资源的资源参数是否满足对应的分享条件；若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
本说明书一个或多个实施例提供了一种基于区块链的权益核销处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源。检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销。向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
本说明书一个或多个实施例提供了另一种基于区块链的权益核销处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送。接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送。在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
本说明书一个或多个实施例提供了第一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求。基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集。判断所述权益资源的资源参数是否满足对应的分享条件；若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
本说明书一个或多个实施例提供了第二种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源。检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销。向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
本说明书一个或多个实施例提供了第三种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送。接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送。在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
附图说明
图1为本说明书一个或多个实施例提供的一种权益分享处理方法处理流程图；
图2为本说明书一个或多个实施例提供的一种应用于多用户分享场景的权益分享处理方法；
图3为本说明书一个或多个实施例提供的一种基于区块链的权益核销处理方法处理流程图；
图4为本说明书一个或多个实施例提供的另一种基于区块链的权益核销处理方法处理流程图；
图5为本说明书一个或多个实施例提供的一种权益分享处理装置示意图；
图6为本说明书一个或多个实施例提供的一种基于区块链的权益核销处理装置示意图；
图7为本说明书一个或多个实施例提供的另一种基于区块链的权益核销处理装置示意图；
图8为本说明书一个或多个实施例提供的一种权益分享处理设备的结构示意图；
图9为本说明书一个或多个实施例提供的一种基于区块链的权益核销处理设备的结构示意图；
图10为本说明书一个或多个实施例提供的另一种基于区块链的权益核销处理设备的结构示意图。
具体实施方式
本说明书提供的一种权益分享处理方法实施例：参照图1，其示出了本实施例提供的一种权益分享处理方法处理流程图，参照图2，其示出了本实施例提供的一种应用于多用户分享场景的权益分享处理方法。
参照图1，本实施例提供的权益分享处理方法，具体包括步骤S102至步骤S108。
步骤S102，获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求。
实际应用中，往往会出现领取权益资源的用户并没有使用权益资源，而有使用需求的用户却因为各种原因未能领取到相关的权益资源，影响了权益资源的使用率；本实施例提供的权益分享处理方法，通过由领取了权益资源的用户向其他用户分享权益资源的方式，实现多账户对权益资源的使用，具体的，由分享用户选择被分享用户进行权益资源的分享，在对被分享用户的可信校验通过且分享的权益资源满足分享条件的时候，将被分享用户添加至分享用户与权益资源的权益关系中，以使分享用户与被分享用户都获得权益资源的资源权限，实现权益资源的更大化利用，提升权益资源的使用率。
本实施例所述分享用户，包括领取权益资源并且向其他用户分享领取的权益资源的用户，被分享的其他用户即为所述被分享用户。所述权益资源，包括推荐项目向用户提供的有经济价值或其他维度价值的标的，比如现金红包、优惠券、周期卡等；需要说明的是，用户在领取权益资源后，可查看并使用权益资源，此外，权益资源可发放至用户账户中，以使用户在特定场景或渠道使用。所述推荐项目，是指通过向用户发放权益资源以提升用户参与度的服务项目，如公共交通出行推广活动、共享车辆出行推广活动等。所述分享请求，包括所述权益资源的资源标签，所述分享用户的用户标识，所述被分享用户的用户标识和/或分享时间；此外，还可包括服务器需要处理的其他信息，本实施例在次不做限定。
具体实施时，分享用户要向被分享用户进行权益资源的分享，需要先获取到该权益资源，分享用户对权益资源的资源权限通过两者之间的权益关系确定，为了保证分享用户为可信用户，避免资源损失，本实施例提供的一种可选实施方式中，在向分享用户发放权益资源的过程中，对分享用户进行可信校验，并在可信校验通过的情况下通过建立分享用户与权益资源的权益关系来向分享用户进行权益资源的发放，具体的，通过如下方式进行权益资源发放：根据所述分享用户针对推荐项目的访问请求，对所述分享用户进行可信校验；若校验通过，则向所述分享用户发送推荐权益资源的资源标签；根据所述分享用户针对推荐权益资源的领取请求建立所述分享用户与所述推荐权益资源的推荐权益关系；其中，所述权益资源为所述推荐权益资源的部分或者全部，所述推荐权益关系包含所述权益关系。
具体的，分享用户访问推荐项目时，对分享用户进行可信校验，并在校验通过的情况下，根据推荐项目的项目标识向权益平台查询对应的至少一个推荐权益资源，向分享用户展示该推荐权益资源的资源标签，在分享用户提交对任意一个或多个推荐权益资源的领取请求时，建立分享用户与需要领取的推荐权益资源之间的权益关系。
例如，获取到用户A对共享单车推广活动的访问请求后，根据账户平台存储的黑灰名单表，校验用户A是否为黑灰名单用户，在校验用户A不属于黑灰名单之后，根据访问请求中携带的项目类型，向权益平台查询共享单车推广活动对应的推荐权益资源，查询到的推荐权益资源包括二元现金红包5个，五折购买月卡一次，向分享用户发送对应的资源标签，获取到用户对于二元现金红包5个的领取请求，则建立用户A与5个二元现金红包之间的关联关系，在建立后在用户A查看时向用户A展示建立关联关系的权益资源的资源标签。
具体实施时，分享用户领取推荐权益资源后，可将领取到的推荐权益资源的全部或部分进行分享，在进行权益资源分享时，分享用户需要选择被分享用户，为了减少分享用户在进行权益资源分享时需要执行的流程，提升分享用户的分享体验，本实施例提供的一种可选实施方式中，分享用户可提前设置默认被分享用户，若用户提前设置了默认被分享用户，则在分享用户触发对权益资源的分享控件时，默认对分享用户设置的默认 被分享用户进行分享，无需分享用户再次选择被分享用户，若分享用户未设置默认被分享用户，则需要在分享用户触发对权益资源的分享控件时，由分享用户选择并提交被分享用户，其中，通过如下方式获取被分享用户：在检测到所述分享用户触发所述权益资源的分享控件的情况下，查询所述分享用户是否配置默认被分享用户；若是，则将所述默认被分享用户确定为所述至少一个被分享用户；若否，根据所述分享用户的好友列表生成用户选择页面；在检测到所述分享用户触发所述用户选择页面配置的分享确认控件的情况下，确定所述分享用户通过所述用户选择页面选择的至少一个用户，和/或所述分享用户通过所述用户选择页面查询并选择的至少一个用户为所述至少一个被分享用户。
具体的，在检测到分享用户触发对权益资源的分享控件的情况下，查询分享用户是否配置了默认被分享用户，若是，将默认被分享用户作为被分享用户，若不是，则根据分享用户的好友列表生成用户选择页面，将分享用户通过该用户选择页面选择的好友用户或者查询并选择的非好友用户作为被分享用户。
例如，用户A在获取到5个二元现金红包后，在检测到用户A触发这5个二元现金红包的资源标签展示区域内配置的分享控件时，检测用户A是否设置默认被分享用户，检测到用户A将用户B、用户C以及用户D设置成了默认被分享用户，则将这5个二元现金红包分享至用户B、用户C以及用户D。
再例如，用户A在获取到5个二元现金红包后，在检测到用户A触发这5个二元现金红包的资源标签展示区域内配置的分享控件时，检测到用户A没有设置默认被分享用户，则根据用户A的好友列表生成用户选择页面，用户A通过用户选择页面选择了好友列表中的用户B、用户C以及通过搜索选择了非好友关系的用户D作为被分享用户。
步骤S104，基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集。
所述可信校验，是指校验所述至少一个被分享用户是否为黑灰名单用户。所述目标用户，是指所述可信校验通过的被分享用户。所述用户集，包括至少一个可信校验通过的被分享用户。
具体实施时，为了提升权益分享过程中权益资源的安全性，只有在被分享用户可信校验通过的情况下才能向被分享用户分享权益资源，因此，在分享用户提交的被分享用户为至少一个时，向可信校验通过的被分享用户分享权益资源。
步骤S106，判断所述权益资源的资源参数是否满足对应的分享条件。
所述资源参数，包括：资源类型、分享时间和/或资源状态。此外，还可包括权益资源的数额阈值等，对于资源参数，根据实际服务需求确定，本实施例在此不做限定。
具体实施时，为了进一步保证权益分享过程中权益资源的安全性，本实施例提供的一种可选实施方式中，在对被分享用户进行可信校验且可信校验通过之后，需要进一步判断权益资源的资源参数是否满足对应的分享条件，具体的，对于权益资源的资源参数是否满足对应的分享条件的判断，主要通过如下方式实现：判断所述权益资源的资源类型是否为可分享资源类型，判断所述分享时间是否处于分享时间区间，和/或判断所述权益资源的资源状态是否为未使用状态。此外，还可以判断所述权益资源的资源数额是否超过数额阈值。
具体的，可以是对上述三者的判断，也可以是对上述三者中任意一者或两者的判断；经过判断，若资源参数满足对应的分享条件，将目标用户添加至分享用户与权益资源的权益关系中。
除此之外，由于资源类型的不同，分享时间的不同或其他因素等都可能导致分享失败，为了提升分享用户对于分享失败原因的感知程度，本实施例提供的一种可选实施方式中，若判断所述权益资源的资源参数是否满足对应的分享条件步骤执行之后的执行结果为否，根据判断结果读取分享失败原因；基于所述分享失败原因，向所述分享用户发送分享失败提醒。
例如，用户A将5个二元现金红包向用户B、用户C以及用户D分享，对用户B、用户C以及用户D可信校验通过后，判断这5个二元现金红包对应的共享单车推广活动是否属于权益可分享项目；若否，则向用户A返回资源类型不可分享的提醒；若是，判断这5个二元现金红包的分享时间是否处于分享时间区间；若否，则向用户A返回当前时间不可分享，分享时间为xx时至xx时的提醒；若是，判断5个二元现金红包的资源状态是否为未使用状态；若否，则向用户A返回资源已使用的提醒；若是，则将用户 B、用户C以及用户D添加至用户A与5个二元现金红包的权益关系中。
步骤S108，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中。
具体实施时，将目标用户添加至分享用户与权益资源的权益关系中，以使目标用户获得权益资源的资源权限，目标用户获得资源权限后，可在账户中查看并使用该权益资源。权益资源分享后，分享用户与目标用户都可查看并使用权益资源，为了提升对权益资源的使用情况的感知程度，本实施例提供的一种可选实施方式中，在分享用户或者目标用户查看权益资源的情况下，通过如下方式进行资源标签的展示：若检测到所述分享用户或所述目标用户提交针对所述权益资源的访问请求，则查询所述权益资源的资源状态；基于所述资源状态向所述分享用户或所述目标用户展示所述权益资源的资源标签。
具体的，在分享用户或者目标用户访问权益资源时，查询权益资源的资源状态，若权益资源的资源状态为已使用状态，则向分享用户或目标用户展示携带已使用标记的资源标签，若资源状态为未使用状态，则向分享用户或目标用户展示携带可用标记的资源标签。
除此之外，若权益资源的数量为多个，为了提升对权益资源的使用情况的感知程度，本实施例提供的一种可选实施方式中，若检测到所述分享用户或所述目标用户提交针对所述权益资源的访问请求，查询所述权益资源的资源状态，获得所述资源状态为未使用状态的剩余权益资源；基于所述剩余权益资源的数量向所述分享用户或所述目标用户展示所述权益资源的资源标签。
例如，用户A将5个二元现金红包向用户B、用户C以及用户D分享，用户B要查看获取到的权益资源，在检测到用户B对账户权益的访问请求时，查询这5个二元现金红包的资源状态，查询到3个二元现金红包的资源状态为已使用状态，两个为未使用状态，则向用户B展示携带可使用资源数额为2的资源标签。
具体实施时，分享用户或目标用户在访问权益资源对应的服务时可使用该权益资源，本实施例提供的一种可选实施方式中，在分享用户或者目标用户访问对应的服务时，执行如下操作：若检测到所述分享用户或所述目标用户提交针对所述权益资源对应的推荐项目的服务请求时，查询所述权益资源的资源状态；若所述资源状态为未使用状态，向所述分享用户或所述目标用户发送资源提醒；根据所述分享用户或所述目标用户提交的基于所述权益资源的结算请求进行结算处理；在结算成功的情况下由权益平台对所述权益资源进行资源核销。
具体的，若检测到分享用户或目标用户提交对权益资源对应的服务项目的服务请求时，查询权益资源的资源状态，若存在资源状态为未使用状态的权益资源，则向分享用户或目标用户发送资源提醒，再根据分享用户或目标用户提交的结算请求进行结算处理，并在结算处理后由权益平台将使用的权益资源的资源状态标记为已使用状态。
本实施例提供的一种可选实施方式中，具体通过如下方式进行结算处理：根据所述结算请求向所述权益平台发送核销请求，并从所述权益平台获取所述权益资源的资源结算数额；基于所述资源结算数额与所述结算请求中的结算数额确定实际结算数额，由支付平台根据所述实际结算数额进行资金转移；其中，所述支付平台在资金转移成功后向所述权益平台发送核销确认提醒，以使权益平台根据所述核销确认提醒将所述权益资源的资源状态标记为已使用状态。
例如，用户A将5个二元现金红包向用户B、用户C以及用户D分享，检测奥用户B访问共享单车推广活动，则查询5个二元现金红包的资源状态，查询到3个二元现金红包的资源状态为已使用状态，两个为未使用状态，则向用户B发送二元现金红包的资源提醒，获取到用户B针对该二元现金红包提交的结算请求，则根据该结算请求从权益平台获取二元现金红包，然后根据用户B要支付的费用三元与该二元现金红包计算用户B实际需要支付的费用为一元，则从用户B的账户中扣除一元并转移至共享单车推广活动对应的账户中，最后将使用的二元现金红包的资源状态标记为已使用状态。
需要说明的是，上述对于权益资源的核销过程中，为了保证核销的有效性，先进行结算处理，在结算成功的情况下再进行核销。除此之外，为了保证结算的过程中对于权益资源的有效使用，也可以通过如下步骤进行资源核销：若检测到所述分享用户或所述被分享用户提交针对所述权益资源对应的推荐项目的服务请求，查询所述权益资源的资源状态；若所述资源状态为未使用状态，向所述分享用户或所述目标用户发送资源提醒；根据所述分享用户或所述目标用户提交的基于所述权益资源的结算请求向权益平台发 送核销请求；所述权益平台基于所述核销请求将所述权益资源的资源状态标记为已使用状态，向服务器发送所述权益资源的资源结算数额以及核销结果；服务器基于所述核销结果，利用所述资源结算数额与所述结算请求中的结算数额确定实际结算数额，并由支付平台根据所述实际结算数额进行资金转移。即：先进行资源核销再进行结算处理；核销失败则结算失败。
下述以本实施例提供的一种权益分享处理方法在多用户分享场景的应用为例，对本实施例提供的权益分享处理方法进行进一步说明，参见图2，应用于多用户分享场景的权益分享处理方法，具体包括步骤S202至步骤S216。
步骤S202，根据分享用户对共享出行服务的权益资源的领取请求，建立分享用户与权益资源的权益关系。
步骤S204，根据分享用户将权益资源向至少一个被分享用户进行分享的分享请求对至少一个被分享用户进行可信校验。
步骤S206，获取到可信校验通过的被分享用户后，判断权益资源的资源参数是否满足对应的分享条件；若是，则执行步骤S208；若否，则向分享用户发送分享失败提醒。
步骤S208，将可信校验通过的被分享用户添加至分享用户与权益资源的权益关系中。
步骤S210，若检测到分享用户或被分享用户提交对共享出行服务的服务请求，查询权益资源的资源状态。
步骤S212，若资源状态为未使用状态，则向分享用户或被分享用户发送资源提醒。
步骤S214，根据分享用户或被分享用户基于该权益资源提交的结算请求进行结算处理。
步骤S216，在结算成功的情况下将权益资源的资源状态标记为已使用状态。
此外，还可在接收到结算请求的情况下，先将所述权益资源的资源状态标记为已使用状态，再根据该权益资源进行结算处理。
综上所述，本实施例提供的权益分享处理方法，首先获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求，然后基于分享请求对至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集，再判断权益资源的资源参数是否满足对应的分享条件，若是，将目标用户添加至分享用户与权益资源的权益关系中，以使目标用户获得权益资源的资源权限，以提升权益资源的使用率。
本说明书提供的一种基于区块链的权益核销处理方法实施例：参照图3，其示出了本实施例提供的一种基于区块链的权益核销处理方法处理流程图。
本实施例提供的基于区块链的权益核销处理方法，应用于区块链中的区块链节点；所述方法具体包括步骤S302至步骤S308。
步骤S302，根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源。
所述区块链用于存储权益关系表以及权益资源的资源状态，所述权益关系表中的权益关系在权益资源被领取后创建，并在权益资源被分享后更新。本实施例所述分享用户，包括领取权益资源并且向其他用户分享领取的权益资源的用户，被分享的其他用户即为所述被分享用户。所述权益资源，包括推荐项目向用户提供的有经济价值或其他维度价值的标的，比如现金红包、优惠券、周期卡等；需要说明的是，用户在领取权益资源后，可查看并使用权益资源，此外，权益资源可发放至用户账户中，以使用户在特定场景或渠道使用。所述推荐项目，是指通过向用户发放权益资源以提升用户参与度的服务项目，如公共交通出行推广活动、共享车辆出行推广活动等。
实际应用中，往往会出现领取权益资源的用户并没有使用权益资源，而有使用需求的用户却因为各种原因未能领取到相关的权益资源，影响了权益资源的使用率；本实施例提供的基于区块链的权益核销处理方法，在分享用户将权益资源分享非被分享用户之后，由分享用户或者被分享用户提交资源核销的请求，本实施例提供的一种可选实施方式中，对于区块链中存储的权益关系表中的权益关系，采用如下方式创建：根据所述分享用户针对所述服务类型的访问请求，对所述分享用户进行可信校验；若校验通过，则向所述分享用户发送推荐权益资源；所述推荐权益资源包含所述权益资源；根据所述分享用户对所述权益资源的领取请求建立所述分享用户与所述权益资源的权益关系。
具体的，分享用户访问推荐项目时，服务器对分享用户进行可信校验，并在校验通过的情况下，根据推荐项目的项目标识向权益平台查询对应的至少一个推荐权益资源， 向分享用户展示该推荐权益资源的资源标签，在分享用户提交对任意一个或多个推荐权益资源的领取请求时，建立分享用户与需要领取的推荐权益资源之间的权益关系，建立好该权益关系后，将权益关系向区块链节点发送，以使区块链节点在权益关系表中记录该权益关系并上传至区块链进行存储。
除此之外，还可以是服务器在检测到分享用户访问推荐项目时对分享用户进行可信校验，并在校验通过的情况下，将分享用户的用户标识与权益资源的资源标签发送至区块链节点；区块链节点调用部署的智能合约建立分享用户与权益资源的权益关系并在权益关系表中记录，再将权益关系表上传至区块链进行存储。
具体实施时，分享用户领取推荐权益资源后，可将领取到的推荐权益资源的全部或部分进行分享，在进行权益资源分享时，分享用户需要选择被分享用户，为了提升权益分享过程中权益资源的安全性，只有在被分享用户可信校验通过的情况下才能向被分享用户分享权益资源，因此，在分享用户提交的被分享用户为至少一个时，向可信校验通过的被分享用户分享权益资源。在对被分享用户进行可信校验且校验通过的情况下，对权益关系表中的权益关系进行更新，本实施例提供的一种可选实施方式中，权益关系采用如下方式更新：获取所述分享用户将所述权益资源向至少一个被分享用户进行分享的分享请求；基于所述分享请求，对所述至少一个被分享用户进行可信校验，获得校验通过的所述被分享用户组成的用户集；判断所述权益资源的资源参数是否满足对应的分享条件；若是，将所述被分享用户添加至所述分享用户与所述权益资源的权益关系中，以对所述权益关系进行更新。
具体的，将被分享用户添加至分享用户与权益资源的权益关系中，以使被分享用户获得权益资源的资源权限，获得资源权限后，可在账户中查看并使用该权益资源。为了提升权益分享过程中权益资源的安全性，只有在被分享用户可信校验通过的情况下才能向被分享用户分享权益资源，因此，在分享用户提交的被分享用户为至少一个时，向可信校验通过的被分享用户分享权益资源。
服务器在根据分享请求对至少一个被分享用户进行可信校验后获得校验通过的被分享用户组成的用户集后，判断权益资源的资源参数是否满足对应的分享条件，若满足，则将被分享用户添加至分享用户与权益资源的权益关系中，然后将更新获得的权益关系向区块链节点发送，区块链节点根据权益关系对权益关系表中的权益关系进行更新。所述资源参数，包括：资源类型、分享时间和/或资源状态。此外，还可包括权益资源的数额阈值等，对于资源参数，根据实际服务需求确定，本实施例在此不做限定。
除此之外，在进行权益关系更新的过程中，服务器在接收到分享用户提价的分享请求时，根据分享请求中的被分享用户的用户标识进行可信校验，并在校验通过的情况下将分享请求中携带的分享信息向区块链节点发送，区块链节点接收到分享信息后调用区块链节点部署的智能合约判断权益资源的资源参数是否满足是对应的分享条件，其中，对于权益资源的资源参数是否满足对应的分享条件的判断，主要通过如下方式实现：判断所述权益资源的资源类型是否为可分享资源类型，判断所述分享时间是否处于分享时间区间，和/或判断所述权益资源的资源状态是否为未使用状态。此外，还可以判断所述权益资源的资源数额是否超过数额阈值。具体的，可以是对上述所有的判断，也可以是对任意一者或多者的判断。若判断后资源参数满足对应的分享条件，则向服务器发送分享成功结果，并将被分享用户添加至分享用户与权益资源的权益关系中，以对权益关系表中的权益关系进行更新。服务器在接收到分享成功结果之后，向分享用户和被分享用户发送权益资源的资源标签。
需要说明的是，分享用户领取推荐权益资源后，可将领取到的推荐权益资源的全部或部分进行分享，在进行权益资源分享时，分享用户需要选择被分享用户，为了减少分享用户在进行权益资源分享时需要执行的流程，提升分享用户的分享体验，分享用户可提前设置默认被分享用户，若用户提前设置了默认被分享用户，则在分享用户触发对权益资源的分享控件时，默认对分享用户设置的默认被分享用户进行分享，无需分享用户再次选择被分享用户，若分享用户未设置默认被分享用户，则需要在分享用户触发对权益资源的分享控件时，由分享用户选择并提交被分享用户，其中，通过如下方式获取被分享用户：在检测到所述分享用户触发所述权益资源的分享控件的情况下，查询所述分享用户是否配置默认被分享用户；若是，则将所述默认被分享用户确定为所述至少一个被分享用户；若否，根据所述分享用户的好友列表生成用户选择页面；在检测到所述分 享用户触发所述用户选择页面配置的分享确认控件的情况下，确定所述分享用户通过所述用户选择页面选择的至少一个用户，和/或所述分享用户通过所述用户选择页面查询并选择的至少一个用户为所述至少一个被分享用户。此外，由于资源类型的不同，分享时间的不同或其他因素等都可能导致分享失败，为了提升分享用户对于分享失败原因的感知程度，本实施例提供的一种可选实施方式中，若判断所述权益资源的资源参数是否满足对应的分享条件步骤执行之后的执行结果为否，根据判断结果读取分享失败原因；基于所述分享失败原因，向所述分享用户发送分享失败提醒。
具体的，在检测到分享用户触发对权益资源的分享控件的情况下，查询分享用户是否配置了默认被分享用户，若是，将默认被分享用户作为被分享用户，若不是，则根据分享用户的好友列表生成用户选择页面，将分享用户通过该用户选择页面选择的好友用户或者查询并选择的非好友用户作为被分享用户。
步骤S304，检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系。
具体实施时，确定对应的权益资源之后，则查询提交核销请求的用户是否与该权益资源具有权益关系，若有，则表明该用户可以使用该权益资源，若否，则该用户不能使用该权益资源。在查询到具有权益关系后，向区块链查询权益资源的资源状态，若资源状态为未使用状态，则向服务器发送对权益资源的可用提醒。服务器基于该可用提醒向分享用户或被分享用户展示权益资源的资源标签。
除此之外，若权益资源的数量为多个，为了提升对权益资源的使用情况的感知程度，本实施例提供的一种可选实施方式中，通过如下方式向用户发送可用提醒：从所述区块链读取所述权益资源的资源状态，获得所述资源状态为未使用状态的剩余权益资源；基于所述剩余权益资源的数量向所述服务器发送所述可用提醒。
步骤S306，向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销。
具体实施时，向服务器发送可用提醒后，服务器在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。具体的，服务器根据所述分享用户或所述目标用户提交的基于所述权益资源的结算请求进行结算处理在结算成功的情况下向区块链节点发送核销确认请求。区块链基于核销确认请求将权益资源的资源状态标记为已使用状态。
步骤S308，向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
具体实施时，向服务器返回核销结果，服务器根据该核销结果向分享用户或者被分享用户发送核销提醒；区块链节点将更新后的权益资源的状态上传至区块链进行存储。具体的，向服务器发送可用提醒后，服务器在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。具体的，服务器根据所述分享用户或所述目标用户提交的基于所述权益资源的结算请求进行结算处理在结算成功的情况下向区块链节点发送核销确认请求。区块链基于核销确认请求将权益资源的资源状态标记为已使用状态。向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。向服务器返回核销结果，服务器根据该核销结果向分享用户或者被分享用户发送核销提醒；区块链节点将更新后的权益资源的状态上传至区块链进行存储。
需要说明的是，上述对于权益资源的核销过程中，为了保证核销的有效性，先进行结算处理，在结算成功的情况下再进行核销。除此之外，为了保证结算的过程中对于权益资源的有效使用，也可以通过如下步骤进行资源核销：服务器若检测到所述分享用户或所述被分享用户提交针对所述权益资源对应的推荐项目的服务请求，将该服务请求向区块链节点发送；所述区块链节点查询所述权益资源的资源状态；若所述资源状态为未使用状态，向所述服务器发送资源提醒，以使所述服务器向所述分享用户或所述被分享用户发送；服务器根据所述分享用户或所述被分享用户提交的基于所述权益资源的结算请求向所述区块链节点发送核销请求；所述区块链节点基于所述核销请求将所述权益资源的资源状态标记为已使用状态，向服务器发送所述权益资源的资源结算数额以及核销结果；服务器基于所述核销结果，利用所述资源结算数额与所述结算请求中的结算数额确定实际结算数额，并由支付平台根据所述实际结算数额进行资金转移。即：先进行资源核销再进行结算处理；核销失败则结算失败。
除此之外，分享用户与被分享用户都可查看并使用权益资源，为了提升对权益资源的使用情况的感知程度，在分享用户或者被分享用户查看权益资源的情况下，通过如下方式进行资源标签的展示：若检测到所述分享用户或所述被分享用户提交针对所述权益资源的访问请求，则查询所述权益资源的资源状态；基于所述资源状态向所述分享用户或所述被分享用户展示所述权益资源的资源标签。
具体的，在分享用户或者被分享用户访问权益资源时，查询权益资源的资源状态，若权益资源的资源状态为已使用状态，则向分享用户或被分享用户展示携带已使用标记的资源标签，若资源状态为未使用状态，则向分享用户或被分享用户展示携带可用标记的资源标签。其中，服务器在接收到分享用户或被分享用户针对权益资源的访问请求，则向区块链节点发送该访问请求，区块链节点根据该访问请求从区块链查询权益资源的资源状态并向服务器发送，服务器根据资源状态向分享用户或者被分享用户展示资源标签。例如，将资源状态为已使用状态的资源标签设置为仅可查看不可访问，将资源状态为未使用状态的资源标签设置为即可查看也可访问。
本说明书提供的另一种基于区块链的权益核销处理方法实施例：参照图4，其示出了本实施例提供的一种基于区块链的权益核销处理方法处理流程图。
本实施例提供的基于区块链的权益核销处理方法，应用于服务器；所述方法具体包括步骤S402至步骤S406。
本实施例提供的应用于服务器的基于区块链的权益核销处理方法，在执行过程中与上述应用于区块链中的区块链节点的基于区块链的权益核销处理方法相互配合，因此，在阅读本实施例提供的基于区块链的权益核销处理方法过程中，请结合上述应用于区块链中的区块链节点的基于区块链的权益核销处理方法的实施例。
步骤S402，获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送。
所述区块链用于存储权益关系表以及权益资源的资源状态，所述权益关系表中的权益关系在权益资源被领取后创建，并在权益资源被分享后更新。本实施例所述分享用户，包括领取权益资源并且向其他用户分享领取的权益资源的用户，被分享的其他用户即为所述被分享用户。所述权益资源，包括推荐项目向用户提供的有经济价值或其他维度价值的标的，比如现金红包、优惠券、周期卡等；需要说明的是，用户在领取权益资源后，可查看并使用权益资源，此外，权益资源可发放至用户账户中，以使用户在特定场景或渠道使用。所述推荐项目，是指通过向用户发放权益资源以提升用户参与度的服务项目，如公共交通出行推广活动、共享车辆出行推广活动等。
实际应用中，往往会出现领取权益资源的用户并没有使用权益资源，而有使用需求的用户却因为各种原因未能领取到相关的权益资源，影响了权益资源的使用率；本实施例提供的基于区块链的权益核销处理方法，在分享用户将权益资源分享非被分享用户之后，由分享用户或者被分享用户提交资源核销的请求，本实施例提供的一种可选实施方式中，对于区块链中存储的权益关系表中的权益关系，采用如下方式创建：根据所述分享用户针对所述服务类型的访问请求，对所述分享用户进行可信校验；若校验通过，则向所述分享用户发送推荐权益资源；所述推荐权益资源包含所述权益资源；根据所述分享用户对所述权益资源的领取请求建立所述分享用户与所述权益资源的权益关系。
具体的，分享用户访问推荐项目时，服务器对分享用户进行可信校验，并在校验通过的情况下，根据推荐项目的项目标识向权益平台查询对应的至少一个推荐权益资源，向分享用户展示该推荐权益资源的资源标签，在分享用户提交对任意一个或多个推荐权益资源的领取请求时，建立分享用户与需要领取的推荐权益资源之间的权益关系，建立好该权益关系后，将权益关系向区块链节点发送，以使区块链节点在权益关系表中记录该权益关系并上传至区块链进行存储。
除此之外，还可以是服务器在检测到分享用户访问推荐项目时对分享用户进行可信校验，并在校验通过的情况下，将分享用户的用户标识与权益资源的资源标签发送至区块链节点；区块链节点调用部署的智能合约建立分享用户与权益资源的权益关系并在权益关系表中记录，再将权益关系表上传至区块链进行存储。
具体实施时，分享用户领取推荐权益资源后，可将领取到的推荐权益资源的全部或部分进行分享，在进行权益资源分享时，分享用户需要选择被分享用户，为了提升权益分享过程中权益资源的安全性，只有在被分享用户可信校验通过的情况下才能向被分享 用户分享权益资源，因此，在分享用户提交的被分享用户为至少一个时，向可信校验通过的被分享用户分享权益资源。在对被分享用户进行可信校验且校验通过的情况下，对权益关系表中的权益关系进行更新，本实施例提供的一种可选实施方式中，权益关系，采用如下方式更新：获取所述分享用户将所述权益资源向至少一个被分享用户进行分享的分享请求；基于所述分享请求，对所述至少一个被分享用户进行可信校验，获得校验通过的所述被分享用户组成的用户集；判断所述权益资源的资源参数是否满足对应的分享条件；若是，将所述被分享用户添加至所述分享用户与所述权益资源的权益关系中，以对所述权益关系进行更新。
具体的，将被分享用户添加至分享用户与权益资源的权益关系中，以使被分享用户获得权益资源的资源权限，获得资源权限后，可在账户中查看并使用该权益资源。为了提升权益分享过程中权益资源的安全性，只有在被分享用户可信校验通过的情况下才能向被分享用户分享权益资源，因此，在分享用户提交的被分享用户为至少一个时，向可信校验通过的被分享用户分享权益资源。
服务器在根据分享请求对至少一个被分享用户进行可信校验后获得校验通过的被分享用户组成的用户集后，判断权益资源的资源参数是否满足对应的分享条件，若满足，则将被分享用户添加至分享用户与权益资源的权益关系中，然后将更新获得的权益关系向区块链节点发送，区块链节点根据权益关系对权益关系表中的权益关系进行更新。所述资源参数，包括：资源类型、分享时间和/或资源状态。此外，还可包括权益资源的数额阈值等，对于资源参数，根据实际服务需求确定，本实施例在此不做限定。
除此之外，在进行权益关系更新的过程中，服务器在接收到分享用户提价的分享请求时，根据分享请求中的被分享用户的用户标识进行可信校验，并在校验通过的情况下将分享请求中携带的分享信息向区块链节点发送，区块链节点接收到分享信息后调用区块链节点部署的智能合约判断权益资源的资源参数是否满足是对应的分享条件，其中，对于权益资源的资源参数是否满足对应的分享条件的判断，主要通过如下方式实现：判断所述权益资源的资源类型是否为可分享资源类型，判断所述分享时间是否处于分享时间区间，和/或判断所述权益资源的资源状态是否为未使用状态。此外，还可以判断所述权益资源的资源数额是否超过数额阈值。具体的，可以是对上述所有的判断，也可以是对任意一者或多者的判断。若判断后资源参数满足对应的分享条件，则向服务器发送分享成功结果，并将被分享用户添加至分享用户与权益资源的权益关系中，以对权益关系表中的权益关系进行更新。服务器在接收到分享成功结果之后，向分享用户和被分享用户发送权益资源的资源标签。
需要说明的是，分享用户领取推荐权益资源后，可将领取到的推荐权益资源的全部或部分进行分享，在进行权益资源分享时，分享用户需要选择被分享用户，为了减少分享用户在进行权益资源分享时需要执行的流程，提升分享用户的分享体验，分享用户可提前设置默认被分享用户，若用户提前设置了默认被分享用户，则在分享用户触发对权益资源的分享控件时，默认对分享用户设置的默认被分享用户进行分享，无需分享用户再次选择被分享用户，若分享用户未设置默认被分享用户，则需要在分享用户触发对权益资源的分享控件时，由分享用户选择并提交被分享用户，其中，通过如下方式获取被分享用户：在检测到所述分享用户触发所述权益资源的分享控件的情况下，查询所述分享用户是否配置默认被分享用户；若是，则将所述默认被分享用户确定为所述至少一个被分享用户；若否，根据所述分享用户的好友列表生成用户选择页面；在检测到所述分享用户触发所述用户选择页面配置的分享确认控件的情况下，确定所述分享用户通过所述用户选择页面选择的至少一个用户，和/或所述分享用户通过所述用户选择页面查询并选择的至少一个用户为所述至少一个被分享用户。此外，由于资源类型的不同，分享时间的不同或其他因素等都可能导致分享失败，为了提升分享用户对于分享失败原因的感知程度，本实施例提供的一种可选实施方式中，若判断所述权益资源的资源参数是否满足对应的分享条件步骤执行之后的执行结果为否，根据判断结果读取分享失败原因；基于所述分享失败原因，向所述分享用户发送分享失败提醒。
具体的，在检测到分享用户触发对权益资源的分享控件的情况下，查询分享用户是否配置了默认被分享用户，若是，将默认被分享用户作为被分享用户，若不是，则根据分享用户的好友列表生成用户选择页面，将分享用户通过该用户选择页面选择的好友用户或者查询并选择的非好友用户作为被分享用户。
步骤S404，接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送。
具体实施时，区块链节点在接收到核销请求后，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源；确定对应的权益资源之后，则查询提交核销请求的用户是否与该权益资源具有权益关系，若有，则表明该用户可以使用该权益资源，若否，则该用户不能使用该权益资源。在查询到具有权益关系后，向区块链查询权益资源的资源状态，若资源状态为未使用状态，则向服务器发送对权益资源的可用提醒。服务器基于该可用提醒向分享用户或被分享用户展示权益资源的资源标签。
除此之外，若权益资源的数量为多个，为了提升对权益资源的使用情况的感知程度，区块链节点通过如下方式向用户发送可用提醒：从所述区块链读取所述权益资源的资源状态，获得所述资源状态为未使用状态的剩余权益资源；基于所述剩余权益资源的数量向所述服务器发送所述可用提醒。向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销。
步骤S406，在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
具体实施时，向服务器发送可用提醒后，服务器在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。具体的，服务器根据所述分享用户或所述目标用户提交的基于所述权益资源的结算请求进行结算处理在结算成功的情况下向区块链节点发送核销确认请求。区块链基于核销确认请求将权益资源的资源状态标记为已使用状态。向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。向服务器返回核销结果，服务器根据该核销结果向分享用户或者被分享用户发送核销提醒；区块链节点将更新后的权益资源的状态上传至区块链进行存储。
在进行结算处理的过程中，服务器具体通过如下方式进行结算处理：根据所述结算请求向所述区块链节点发送核销请求，并从所述区块链节点获取所述权益资源的资源结算数额；基于所述资源结算数额与所述结算请求中的结算数额确定实际结算数额，由支付平台根据所述实际结算数额进行资金转移；其中，所述支付平台在资金转移成功后向所述区块链节点发送核销确认提醒，以使区块链节点根据所述核销确认提醒将所述权益资源的资源状态标记为已使用状态。
需要说明的是，上述对于权益资源的核销过程中，为了保证核销的有效性，先进行结算处理，在结算成功的情况下再进行核销。除此之外，为了保证结算的过程中对于权益资源的有效使用，也可以通过如下步骤进行资源核销：服务器若检测到所述分享用户或所述被分享用户提交针对所述权益资源对应的推荐项目的服务请求，将该服务请求向区块链节点发送；所述区块链节点查询所述权益资源的资源状态；若所述资源状态为未使用状态，向所述服务器发送资源提醒，以使所述服务器向所述分享用户或所述被分享用户发送；服务器根据所述分享用户或所述被分享用户提交的基于所述权益资源的结算请求向所述区块链节点发送核销请求；所述区块链节点基于所述核销请求将所述权益资源的资源状态标记为已使用状态，向服务器发送所述权益资源的资源结算数额以及核销结果；服务器基于所述核销结果，利用所述资源结算数额与所述结算请求中的结算数额确定实际结算数额，并由支付平台根据所述实际结算数额进行资金转移。即：先进行资源核销再进行结算处理；核销失败则结算失败。
除此之外，分享用户与被分享用户都可查看并使用权益资源，为了提升对权益资源的使用情况的感知程度，在分享用户或者被分享用户查看权益资源的情况下，通过如下方式进行资源标签的展示：若检测到所述分享用户或所述被分享用户提交针对所述权益资源的访问请求，则查询所述权益资源的资源状态；基于所述资源状态向所述分享用户或所述被分享用户展示所述权益资源的资源标签。
具体的，在分享用户或者被分享用户访问权益资源时，查询权益资源的资源状态，若权益资源的资源状态为已使用状态，则向分享用户或被分享用户展示携带已使用标记的资源标签，若资源状态为未使用状态，则向分享用户或被分享用户展示携带可用标记的资源标签。其中，服务器在接收到分享用户或被分享用户针对权益资源的访问请求，则向区块链节点发送该访问请求，区块链节点根据该访问请求从区块链查询权益资源的资源状态并向服务器发送，服务器根据资源状态向分享用户或者被分享用户展示资源标签。例如，将资源状态为已使用状态的资源标签设置为仅可查看不可访问，将资源状态 为未使用状态的资源标签设置为即可查看也可访问。
本说明书提供的一种权益分享处理装置实施例如下：在上述的实施例中，提供了一种权益分享处理方法，与之相对应的，还提供了一种权益分享处理装置，下面结合附图进行说明。
参照图5，其示出了本实施例提供的一种权益分享处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种权益分享处理装置，包括：获取模块502，被配置为获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求；校验模块504，被配置为基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集；判断模块506，被配置为判断所述权益资源的资源参数是否满足对应的分享条件；若是，运行添加模块508，所述添加模块508，被配置为将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
本说明书提供的一种基于区块链的权益核销处理装置实施例如下：在上述的实施例中，提供了一种基于区块链的权益核销处理方法，应用于区块链中的区块链节点，与之相对应的，还提供了一种基于区块链的权益核销处理装置，运行于区块链中的区块链节点，下面结合附图进行说明。
参照图6，其示出了本实施例提供的一种基于区块链的权益核销处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种基于区块链的权益核销处理装置，包括：查询模块602，被配置为根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源；检测模块604，被配置为检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，运行核销模块606，所述核销模块606，被配置为则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销；更新模块608，被配置为向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
本说明书提供的另一种基于区块链的权益核销处理装置实施例如下：在上述的实施例中，提供了一种基于区块链的权益核销处理方法，应用于服务器，与之相对应的，还提供了一种基于区块链的权益核销处理装置，运行于服务器，下面结合附图进行说明。
参照图7，其示出了本实施例提供的一种基于区块链的权益核销处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种基于区块链的权益核销处理装置，包括：服务请求接收模块702，被配置为获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送；可用提醒接收模块704，被配置为接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送；核销请求模块706，被配置为在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
本说明书提供的一种权益分享处理设备实施例如下：对应上述描述的一种权益分享处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种权益分享处理设备，该权益分享处理设备用于执行上述提供的权益分享处理方法，图8为本说明书一个或多个实施例提供的一种权益分享处理设备的结构示意图。
本实施例提供的一种权益分享处理设备，包括：如图8所示，权益分享处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器801和存储器802，存储器802中可以存储有一个或一个以上存储应用程序或数据。其中，存储器802可以是短暂存储或持久存储。存储在存储器802的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括权益分享处理设备中的一系列计算机可执行指令。更进一步地，处理器801可以设置为与存储器802通信，在权益分享处理设备上执行存储器802中的一系列计算机可执行指令。权益分享处理设备还可以包括一个或一 个以上电源803，一个或一个以上有线或无线网络接口804，一个或一个以上输入/输出接口805，一个或一个以上键盘806等。
在一个具体的实施例中，权益分享处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对权益分享处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求；基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集；判断所述权益资源的资源参数是否满足对应的分享条件；若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
本说明书提供的一种基于区块链的权益核销处理设备实施例如下：对应上述描述的一种基于区块链的权益核销处理方法，应用于区块链中服务器对应的区块链节点，基于相同的技术构思，本说明书一个或多个实施例还提供一种基于区块链的权益核销处理设备，该基于区块链的权益核销处理设备用于执行上述提供的基于区块链的权益核销处理方法，图9为本说明书一个或多个实施例提供的一种基于区块链的权益核销处理设备的结构示意图。
本实施例提供的一种基于区块链的权益核销处理设备，应用于区块链中的区块链节点，包括：如图9所示，基于区块链的权益核销处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器901和存储器902，存储器902中可以存储有一个或一个以上存储应用程序或数据。其中，存储器902可以是短暂存储或持久存储。存储在存储器902的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括基于区块链的权益核销处理设备中的一系列计算机可执行指令。更进一步地，处理器901可以设置为与存储器902通信，在基于区块链的权益核销处理设备上执行存储器902中的一系列计算机可执行指令。基于区块链的权益核销处理设备还可以包括一个或一个以上电源903，一个或一个以上有线或无线网络接口904，一个或一个以上输入/输出接口905，一个或一个以上键盘906等。
在一个具体的实施例中，基于区块链的权益核销处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对基于区块链的权益核销处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源；检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销；向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
本说明书提供的另一种基于区块链的权益核销处理设备实施例如下：对应上述描述的一种基于区块链的权益核销处理方法，应用于服务器，基于相同的技术构思，本说明书一个或多个实施例还提供一种基于区块链的权益核销处理设备，该基于区块链的权益核销处理设备用于执行上述提供的基于区块链的权益核销处理方法，图10为本说明书一个或多个实施例提供的一种基于区块链的权益核销处理设备的结构示意图。
本实施例提供的一种基于区块链的权益核销处理设备，应用于服务器，包括：如图10所示，基于区块链的权益核销处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器1001和存储器1002，存储器1002中可以存储有一个或一个以上存储应用程序或数据。其中，存储器1002可以是短暂存储或持久存储。存储在存储器1002的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括基于区块链的权益核销处理设备中的一系列计算机可执行指令。更进一步地，处理器1001可以设置为与存储器1002通信，在基于区块链的权益核销处理设备上执行存储器1002中的一系列计算机可执行指令。基于区块链的权益核销处理设备还可以包括一个或一个以上电源1003，一个或一个以上有线或无线网络接口1004，一个或一个以 上输入/输出接口1005，一个或一个以上键盘1006等。
在一个具体的实施例中，基于区块链的权益核销处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对基于区块链的权益核销处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送；接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送；在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
本说明书提供的一种存储介质实施例如下：对应上述描述的一种权益分享处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求；基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集；判断所述权益资源的资源参数是否满足对应的分享条件；若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于权益分享处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
本说明书提供的第二种存储介质实施例如下：对应上述描述的一种基于区块链的权益核销处理方法，应用于区块链中服务器对应的区块链节点，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源；检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销；向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于基于区块链的权益核销处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
本说明书提供的第三种存储介质实施例如下：对应上述描述的一种基于区块链的权益核销处理方法，应用于服务器，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送；接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送；在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
需要说明的是，本说明书中关于存储介质的实施例与本说明书中关于基于区块链的权益核销处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在20世纪30年代，对于一个技术的改进可以很明显地区分是硬件上的改进(例如，对二极管、晶体管、开关等电路结构的改进)还是软件上的改进(对于方法流程的改进)。 然而，随着技术的发展，当今的很多方法流程的改进已经可以视为硬件电路结构的直接改进。设计人员几乎都通过将改进的方法流程编程到硬件电路中来得到相应的硬件电路结构。因此，不能说一个方法流程的改进就不能用硬件实体模块来实现。例如，可编程逻辑器件(Programmable Logic Device，PLD)(例如现场可编程门阵列(Field Programmable Gate Array，FPGA))就是这样一种集成电路，其逻辑功能由用户对器件编程来确定。由设计人员自行编程来把一个数字系统“集成”在一片PLD上，而不需要请芯片制造厂商来设计和制作专用的集成电路芯片。而且，如今，取代手工地制作集成电路芯片，这种编程也多半改用“逻辑编译器(logic compiler)”软件来实现，它与程序开发撰写时所用的软件编译器相类似，而要编译之前的原始代码也得用特定的编程语言来撰写，此称之为硬件描述语言(Hardware Description Language，HDL)，而HDL也并非仅有一种，而是有许多种，如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、RHDL(Ruby Hardware Description Language)等，目前最普遍使用的是VHDL(Very-High-Speed Integrated Circuit Hardware Description Language)与Verilog。本领域技术人员也应该清楚，只需要将方法流程用上述几种硬件描述语言稍作逻辑编程并编程到集成电路中，就可以很容易得到实现该逻辑方法流程的硬件电路。
控制器可以按任何适当的方式实现，例如，控制器可以采取例如微处理器或处理器以及存储可由该(微)处理器执行的计算机可读程序代码(例如软件或固件)的计算机可读介质、逻辑门、开关、专用集成电路(Application Specific Integrated Circuit，ASIC)、可编程逻辑控制器和嵌入微控制器的形式，控制器的例子包括但不限于以下微控制器：ARC 625D、Atmel AT91SAM、Microchip PIC18F26K20以及Silicone Labs C8051F320，存储器控制器还可以被实现为存储器的控制逻辑的一部分。本领域技术人员也知道，除了以纯计算机可读程序代码方式实现控制器以外，完全可以通过将方法步骤进行逻辑编程来使得控制器以逻辑门、开关、专用集成电路、可编程逻辑控制器和嵌入微控制器等的形式来实现相同功能。因此这种控制器可以被认为是一种硬件部件，而对其内包括的用于实现各种功能的装置也可以视为硬件部件内的结构。或者甚至，可以将用于实现各种功能的装置视为既可以是实现方法的软件模块又可以是硬件部件内的结构。
上述实施例阐明的系统、装置、模块或单元，具体可以由计算机芯片或实体实现，或者由具有某种功能的产品来实现。一种典型的实现设备为计算机。具体的，计算机例如可以为个人计算机、膝上型计算机、蜂窝电话、相机电话、智能电话、个人数字助理、媒体播放器、导航设备、电子邮件设备、游戏控制台、平板计算机、可穿戴设备或者这些设备中的任何设备的组合。
为了描述的方便，描述以上装置时以功能分为各种单元分别描述。当然，在实施本说明书实施例时可以把各单元的功能在同一个或多个软件和/或硬件中实现。
本领域内的技术人员应明白，本说明书一个或多个实施例可提供为方法、系统或计算机程序产品。因此，本说明书一个或多个实施例可采用完全硬件实施例、完全软件实施例、或结合软件和硬件方面的实施例的形式。而且，本说明书可采用在一个或多个其中包含有计算机可用程序代码的计算机可用存储介质(包括但不限于磁盘存储器、CD-ROM、光学存储器等)上实施的计算机程序产品的形式。
本说明书是参照根据本说明书实施例的方法、设备(系统)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程数据处理设备的处理器以产生一个机器，使得通过计算机或其他可编程数据处理设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程数据处理设备以特定方式工作的计算机可读存储器中，使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品，该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程数据处理设备上，使得在计算 机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理，从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
在一个典型的配置中，计算设备包括一个或多个处理器(CPU)、输入/输出接口、网络接口和内存。内存可能包括计算机可读介质中的非永久性存储器，随机存取存储器(RAM)和/或非易失性内存等形式，如只读存储器(ROM)或闪存(flash RAM)。内存是计算机可读介质的示例。计算机可读介质包括永久性和非永久性、可移动和非可移动媒体可以由任何方法或技术来实现信息存储。信息可以是计算机可读指令、数据结构、程序的模块或其他数据。计算机的存储介质的例子包括，但不限于相变内存(PRAM)、静态随机存取存储器(SRAM)、动态随机存取存储器(DRAM)、其他类型的随机存取存储器(RAM)、只读存储器(ROM)、电可擦除可编程只读存储器(EEPROM)、快闪记忆体或其他内存技术、只读光盘只读存储器(CD-ROM)、数字多功能光盘(DVD)或其他光学存储、磁盒式磁带，磁带磁盘存储或其他磁性存储设备或任何其他非传输介质，可用于存储可以被计算设备访问的信息。按照本文中的界定，计算机可读介质不包括暂存电脑可读媒体(transitory media)，如调制的数据信号和载波。
还需要说明的是，术语“包括”、“包含”或者其任何其他变体意在涵盖非排他性的包含，从而使得包括一系列要素的过程、方法、商品或者设备不仅包括那些要素，而且还包括没有明确列出的其他要素，或者是还包括为这种过程、方法、商品或者设备所固有的要素。在没有更多限制的情况下，由语句“包括一个……”限定的要素，并不排除在包括所述要素的过程、方法、商品或者设备中还存在另外的相同要素。
本说明书一个或多个实施例可以在由计算机执行的计算机可执行指令的一般上下文中描述，例如程序模块。一般地，程序模块包括执行特定任务或实现特定抽象数据类型的例程、程序、对象、组件、数据结构等等。也可以在分布式计算环境中实践本说明书的一个或多个实施例，在这些分布式计算环境中，由通过通信网络而被连接的远程处理设备来执行任务。在分布式计算环境中，程序模块可以位于包括存储设备在内的本地和远程计算机存储介质中。
本说明书中的各个实施例均采用递进的方式描述，各个实施例之间相同相似的部分互相参见即可，每个实施例重点说明的都是与其他实施例的不同之处。尤其，对于系统实施例而言，由于其基本相似于方法实施例，所以描述的比较简单，相关之处参见方法实施例的部分说明即可。
以上所述仅为本文件的实施例而已，并不用于限制本文件。对于本领域技术人员来说，本文件可以有各种更改和变化。凡在本文件的精神和原理之内所作的任何修改、等同替换、改进等，均应包含在本文件的权利要求范围之内。

Claims (25)

  1. 一种权益分享处理方法，包括：
    获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求；
    基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集；
    判断所述权益资源的资源参数是否满足对应的分享条件；
    若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
  2. 根据权利要求1所述的权益分享处理方法，还包括：
    若检测到所述分享用户或所述目标用户提交针对所述权益资源的访问请求，则查询所述权益资源的资源状态；
    基于所述资源状态向所述分享用户或所述目标用户展示所述权益资源的资源标签。
  3. 根据权利要求1所述的权益分享处理方法，还包括：
    若检测到所述分享用户或所述目标用户提交针对所述权益资源对应的推荐项目的服务请求，查询所述权益资源的资源状态；
    若所述资源状态为未使用状态，向所述分享用户或所述目标用户发送资源提醒。
  4. 根据权利要求3所述的权益分享处理方法，所述向所述分享用户或所述目标用户发送资源提醒操作执行之后，还包括：
    根据所述分享用户或所述目标用户提交的基于所述权益资源的结算请求进行结算处理；
    在结算成功的情况下由权益平台对所述权益资源进行资源核销。
  5. 根据权利要求4所述的权益分享处理方法，所述结算处理，包括：
    根据所述结算请求向所述权益平台发送核销请求，并从所述权益平台获取所述权益资源的资源结算数额；
    基于所述资源结算数额与所述结算请求中的结算数额确定实际结算数额，由支付平台根据所述实际结算数额进行资金转移；
    其中，所述支付平台在资金转移成功后向所述权益平台发送核销确认提醒，以使权益平台根据所述核销确认提醒将所述权益资源的资源状态标记为已使用状态。
  6. 根据权利要求1所述的权益分享处理方法，所述获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求步骤执行之前，还包括：
    根据所述分享用户针对推荐项目的访问请求，对所述分享用户进行可信校验；
    若校验通过，则向所述分享用户发送推荐权益资源的资源标签；
    根据所述分享用户针对推荐权益资源的领取请求建立所述分享用户与所述推荐权益资源的推荐权益关系；
    其中，所述权益资源为所述推荐权益资源的部分或者全部，所述推荐权益关系包含所述权益关系。
  7. 根据权利要求1所述的权益分享处理方法，所述权益资源的数量为多个；
    所述方法，还包括：
    若检测到所述分享用户或所述目标用户提交针对所述权益资源的访问请求，查询所述权益资源的资源状态，获得所述资源状态为未使用状态的剩余权益资源；
    基于所述剩余权益资源的数量向所述分享用户或所述目标用户展示所述权益资源的资源标签。
  8. 根据权利要求1所述的权益分享处理方法，所述资源参数，包括：资源类型、分享时间和/或资源状态；
    相应的，所述权益资源的资源参数是否满足对应的分享条件的判断，包括：
    判断所述权益资源的资源类型是否为可分享资源类型，判断所述分享时间是否处于分享时间区间，和/或判断所述权益资源的资源状态是否为未使用状态。
  9. 根据权利要求1所述的权益分享处理方法，所述至少一个被分享用户，采用如下方式确定：
    在检测到所述分享用户触发所述权益资源的分享控件的情况下，查询所述分享用户是否配置默认被分享用户；
    若是，则将所述默认被分享用户确定为所述至少一个被分享用户。
  10. 根据权利要求9所述的权益分享处理方法，若所述查询所述分享用户是否配置默认被分享用户操作执行之后的执行结果为否，执行如下子步骤：
    根据所述分享用户的好友列表生成用户选择页面；
    在检测到所述分享用户触发所述用户选择页面配置的分享确认控件的情况下，确定所述分享用户通过所述用户选择页面选择的至少一个用户，和/或所述分享用户通过所述用户选择页面查询并选择的至少一个用户为所述至少一个被分享用户。
  11. 根据权利要求1所述的权益分享处理方法，若所述判断所述权益资源的资源参数是否满足对应的分享条件步骤执行之后的执行结果为否，执行如下操作：
    根据判断结果读取分享失败原因；
    基于所述分享失败原因，向所述分享用户发送分享失败提醒。
  12. 一种基于区块链的权益核销处理方法，应用于区块链中的区块链节点，所述区块链用于存储权益关系表以及权益资源的资源状态，所述权益关系表中的权益关系在权益资源被领取后创建，并在权益资源被分享后更新；
    所述方法，包括：
    根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源；
    检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；
    若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销；
    向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
  13. 根据权利要求12所述的基于区块链的权益核销处理方法，所述权益关系，采用如下方式创建：
    根据所述分享用户针对所述服务类型的访问请求，对所述分享用户进行可信校验；
    若校验通过，则向所述分享用户发送推荐权益资源；所述推荐权益资源包含所述权益资源；
    根据所述分享用户对所述权益资源的领取请求建立所述分享用户与所述权益资源的权益关系。
  14. 根据权利要求12所述的基于区块链的权益核销处理方法，所述权益关系，采用如下方式更新：
    获取所述分享用户将所述权益资源向至少一个被分享用户进行分享的分享请求；
    基于所述分享请求，对所述至少一个被分享用户进行可信校验，获得校验通过的所述被分享用户组成的用户集；
    判断所述权益资源的资源参数是否满足对应的分享条件；
    若是，将所述被分享用户添加至所述分享用户与所述权益资源的权益关系中，以对所述权益关系进行更新。
  15. 根据权利要求12所述的基于区块链的权益核销处理方法，所述权益资源的数量为多个；
    相应的，所述可用提醒，通过如下方式向所述服务器发送：
    从所述区块链读取所述权益资源的资源状态，获得所述资源状态为未使用状态的剩余权益资源；
    基于所述剩余权益资源的数量向所述服务器发送所述可用提醒。
  16. 一种基于区块链的权益核销处理方法，应用于服务器，包括：
    获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送；
    接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送；
    在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
  17. 一种权益分享处理装置，包括：
    获取模块，被配置为获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求；
    校验模块，被配置为基于所述分享请求对所述至少一个被分享用户进行可信校验， 获得校验通过的目标用户组成的用户集；
    判断模块，被配置为判断所述权益资源的资源参数是否满足对应的分享条件；
    若是，运行添加模块，所述添加模块，被配置为将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
  18. 一种基于区块链的权益核销处理装置，包括：
    查询模块，被配置为根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源；
    检测模块，被配置为检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；
    若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，运行核销模块，所述核销模块，被配置为则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销；
    更新模块，被配置为向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
  19. 一种基于区块链的权益核销处理装置，包括：
    服务请求接收模块，被配置为获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送；
    可用提醒接收模块，被配置为接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送；
    核销请求模块，被配置为在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
  20. 一种权益分享处理设备，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求；
    基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集；
    判断所述权益资源的资源参数是否满足对应的分享条件；
    若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
  21. 一种基于区块链的权益核销处理设备，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源；
    检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；
    若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销；
    向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
  22. 一种基于区块链的权益核销处理设备，包括：
    处理器；以及，
    被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送；
    接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送；
    在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
  23. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行 时实现以下流程：
    获取分享用户将权益资源向至少一个被分享用户进行分享的分享请求；
    基于所述分享请求对所述至少一个被分享用户进行可信校验，获得校验通过的目标用户组成的用户集；
    判断所述权益资源的资源参数是否满足对应的分享条件；
    若是，将所述目标用户添加至所述分享用户与所述权益资源的权益关系中，以使所述目标用户获得所述权益资源的资源权限。
  24. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：
    根据服务器发送的分享用户或者被分享用户的核销请求，调用所述区块链节点部署的智能合约查询所述权益核销请求的服务类型对应的权益资源；
    检测所述权益关系表中是否记录所述分享用户或者所述被分享用户的权益关系；
    若是，若在所述区块链中读取的权益资源的资源状态为未使用状态，则向所述服务器发送可用提醒，并在接收到所述服务器发送的核销确认请求时对所述权益资源进行核销；
    向所述服务器返回权益核销结果，并将权益资源的核销状态更新至所述区块链。
  25. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被执行时实现以下流程：
    获取分享用户或者被分享用户提交的对服务类型的服务请求，并将所述服务请求作为权益核销请求向区块链中的区块链节点发送；
    接收所述区块链节点发送的权益资源的可用提醒并向所述分享用户或者所述被分享用户发送；
    在基于所述权益资源进行结算且结算成功后向所述区块链节点发送核销确认请求。
PCT/CN2022/090142 2021-05-13 2022-04-29 权益分享处理的方法及装置 WO2022237574A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US18/560,048 US20240232932A1 (en) 2021-05-13 2022-04-29 Stake sharing processing method and apparatus

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110521430.8 2021-05-13
CN202110521430.8A CN113222667B (zh) 2021-05-13 2021-05-13 权益分享处理方法及装置

Publications (1)

Publication Number Publication Date
WO2022237574A1 true WO2022237574A1 (zh) 2022-11-17

Family

ID=77095545

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/090142 WO2022237574A1 (zh) 2021-05-13 2022-04-29 权益分享处理的方法及装置

Country Status (3)

Country Link
US (1) US20240232932A1 (zh)
CN (2) CN113222667B (zh)
WO (1) WO2022237574A1 (zh)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113222667B (zh) * 2021-05-13 2023-04-18 支付宝(杭州)信息技术有限公司 权益分享处理方法及装置
CN114493711B (zh) * 2022-01-30 2023-08-22 上海烈熊网络技术有限公司 一种会员权益数字化管理方法和系统
CN114548988B (zh) * 2022-02-25 2023-11-28 北京天德科技有限公司 一种nfr权益流转兑换的部署执行方法及系统

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105243569A (zh) * 2015-11-06 2016-01-13 上海畅捷信息技术有限公司 一种利用优惠券分享进行的社交营销系统及其方法
CN110148017A (zh) * 2019-04-29 2019-08-20 阿里巴巴集团控股有限公司 基于区块链的权益发放方法及装置、电子设备、存储介质
WO2020000766A1 (zh) * 2018-06-29 2020-01-02 北京金山安全软件有限公司 区块链红包的处理方法、装置、电子设备及介质
CN111767496A (zh) * 2019-09-11 2020-10-13 北京京东尚科信息技术有限公司 服务信息分享方法、装置、设备和可读存储介质
CN113222667A (zh) * 2021-05-13 2021-08-06 支付宝(杭州)信息技术有限公司 权益分享处理方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110009350A (zh) * 2019-03-26 2019-07-12 阿里巴巴集团控股有限公司 一种基于区块链智能合约的操作记录核对方法及装置
CN112581178A (zh) * 2020-12-24 2021-03-30 广州华多网络科技有限公司 权益发放方法、装置、电子设备及计算机可读介质
CN112633954B (zh) * 2021-03-08 2021-06-25 支付宝(杭州)信息技术有限公司 基于区块链的权益处理方法及装置

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105243569A (zh) * 2015-11-06 2016-01-13 上海畅捷信息技术有限公司 一种利用优惠券分享进行的社交营销系统及其方法
WO2020000766A1 (zh) * 2018-06-29 2020-01-02 北京金山安全软件有限公司 区块链红包的处理方法、装置、电子设备及介质
CN110148017A (zh) * 2019-04-29 2019-08-20 阿里巴巴集团控股有限公司 基于区块链的权益发放方法及装置、电子设备、存储介质
CN111767496A (zh) * 2019-09-11 2020-10-13 北京京东尚科信息技术有限公司 服务信息分享方法、装置、设备和可读存储介质
CN113222667A (zh) * 2021-05-13 2021-08-06 支付宝(杭州)信息技术有限公司 权益分享处理方法及装置

Also Published As

Publication number Publication date
CN113222667A (zh) 2021-08-06
US20240232932A1 (en) 2024-07-11
CN113222667B (zh) 2023-04-18
CN116385063A (zh) 2023-07-04

Similar Documents

Publication Publication Date Title
WO2022237574A1 (zh) 权益分享处理的方法及装置
TWI698762B (zh) 資源分享方法、裝置及設備
US10929198B2 (en) Blockchain-based resource allocation method and apparatus
WO2021103909A1 (zh) 风险预测和风险预测模型的训练方法、装置及电子设备
CN110992038B (zh) 交易处理方法、装置及设备
WO2022022245A1 (zh) 数字物权凭证的生成方法、装置及设备
CN111737583B (zh) 数据处理方法及装置、推荐处理方法及装置
CN109118315A (zh) 基于信用担保的业务处理方法、装置以及设备
WO2022267766A1 (zh) 访问聚合码支付页面的方法、装置、设备及介质
CN110992162A (zh) 一种资源处理方法、装置、设备及系统
CN111784356A (zh) 支付验证方法、装置、设备及存储介质
WO2024198539A1 (zh) 支付处理方法及装置
CN112766854B (zh) 基于区块链的数字商品交易方法和装置
CN114092250A (zh) 区块链中数字资源的创建和验证方法及装置
CN113643030B (zh) 交易处理方法、装置及设备
CN116700868A (zh) 页面处理方法及装置
CN106779712B (zh) 网络支付方法及装置
CN110008358B (zh) 一种资源信息展示方法和系统、客户端及服务端
CN112927031B (zh) 商品代购处理方法及装置
CN115865365B (zh) 基于区块链的分账处理方法、装置及系统
CN112215602B (zh) 数据查询方法、装置、系统及电子设备
CN117252661A (zh) 交易处理方法及装置
CN115238305A (zh) 一种营销信息发送方法、装置及设备
CN118537000A (zh) 订单支付处理方法及装置
CN118195795A (zh) 保障项目的交互处理方法及装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22806542

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 18560048

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 11202308281P

Country of ref document: SG

122 Ep: pct application non-entry in european phase

Ref document number: 22806542

Country of ref document: EP

Kind code of ref document: A1