WO2024149010A1 - 资源额度处理方法及装置 - Google Patents

资源额度处理方法及装置 Download PDF

Info

Publication number
WO2024149010A1
WO2024149010A1 PCT/CN2023/138088 CN2023138088W WO2024149010A1 WO 2024149010 A1 WO2024149010 A1 WO 2024149010A1 CN 2023138088 W CN2023138088 W CN 2023138088W WO 2024149010 A1 WO2024149010 A1 WO 2024149010A1
Authority
WO
WIPO (PCT)
Prior art keywords
resource quota
platform
quota
resource
application
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2023/138088
Other languages
English (en)
French (fr)
Inventor
沈海涛
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
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 Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Publication of WO2024149010A1 publication Critical patent/WO2024149010A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
    • G06Q20/405—Establishing or using transaction specific rules
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management

Definitions

  • This document relates to the field of data processing technology, and in particular to a resource quota processing method and device.
  • institutions With the continuous development of Internet technology, more and more institutions choose to allocate corresponding resource quotas to institutional members online. Institutional members can conduct transactions based on the resource quotas allocated by the institutions. In actual application scenarios, institutions allocate corresponding resource quotas to institutional members on multiple platforms, allowing institutional members to trade on multiple platforms, thereby improving the convenience of transactions based on resource quotas.
  • One or more embodiments of this specification provide a resource quota processing method, which is applied to a first platform, including: freezing a first resource quota according to a jump instruction for application jump submitted by an institutional member in a first application based on a payment request. Synchronizing the first resource quota to a second platform, and unfreezing the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing. If a successful payment result returned by the second platform is detected, freezing the remaining resource quota of the second platform through an interface call. Unfreeze the first resource quota and perform quota update processing.
  • One or more embodiments of this specification provide another resource quota processing method, which is applied to a second platform, including: receiving a first resource quota synchronized by a jump instruction based on an application jump of the first platform, and updating a second resource quota based on the first resource quota; the second resource quota is frozen after the previous payment processing based on the institution identification.
  • Calling a payment interface after jumping from the first application to the second application, performing payment processing on a transaction order submitted by an institution member based on the institution identification according to the first resource quota. Performing quota update processing on the first resource quota based on the payment processing result.
  • One or more embodiments of the present specification provide a resource quota processing device, which runs on a first platform and includes: a first resource quota freezing module, which is configured to freeze the first resource quota according to a jump instruction for application jump submitted by an institutional member in the first application based on a payment request.
  • a resource quota synchronization module which is configured to synchronize the first resource quota to the second platform and unfreeze the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing.
  • a remaining resource quota freezing module which is configured to freeze the remaining resource quota of the second platform through an interface call if a successful payment result returned by the second platform is detected.
  • a first quota update module which is configured to unfreeze the first resource quota and perform quota update processing.
  • One or more embodiments of this specification provide another resource quota processing device, which runs on a second platform and includes: a resource quota receiving module, which is configured to receive a first resource quota synchronized by a jump instruction of the first platform based on an application jump, and update a second resource quota based on the first resource quota; the second resource quota is frozen after the previous payment processing based on the institution identification.
  • a payment processing module which is configured to call a payment interface, and after jumping from the first application to the second application, perform payment processing on a transaction order submitted by an institution member based on the institution identification according to the first resource quota.
  • a second quota updating module which is configured to perform quota update processing on the first resource quota based on the payment processing result.
  • a resource quota processing device including: a processor; and a memory configured to store computer executable instructions, wherein when the computer executable instructions are executed, the processor: freezes the first resource quota according to the jump instruction for application jump submitted by the institution member in the first application based on the payment request. Synchronizes the first resource quota to the second platform, and unfreezes the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing. If a successful payment result returned by the second platform is detected, freeze the remaining resource quota of the second platform through an interface call. Unfreeze the first resource quota and perform quota update processing.
  • One or more embodiments of the present specification provide another resource quota processing device, including: a processor; and a memory configured to store computer executable instructions, wherein the computer executable instructions enable the processor to Processor: Receive the first resource quota synchronized by the jump instruction of the first platform based on the application jump, and update the second resource quota based on the first resource quota; the second resource quota is frozen after the previous payment processing based on the institution identification. Call the payment interface, and after jumping from the first application to the second application, perform payment processing on the transaction order submitted by the institution member based on the institution identification according to the first resource quota. Perform quota update processing on the first resource quota based on the payment processing result.
  • One or more embodiments of this specification provide a storage medium for storing computer executable instructions, which implement the following process when executed by a processor: Freeze the first resource quota according to the jump instruction for application jump submitted by the institution member in the first application based on the payment request. Synchronize the first resource quota to the second platform, and unfreeze the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing. If a successful payment result returned by the second platform is detected, freeze the remaining resource quota of the second platform through an interface call. Unfreeze the first resource quota and perform quota update processing.
  • One or more embodiments of this specification provide another storage medium for storing computer executable instructions, which implement the following process when executed by a processor: receiving a first resource quota synchronized by a jump instruction based on an application jump of a first platform, and updating a second resource quota based on the first resource quota; the second resource quota is frozen after the previous payment processing based on the institution identification.
  • Calling a payment interface after jumping from the first application to the second application, performing payment processing on a transaction order submitted by an institution member based on the institution identification according to the first resource quota. Performing quota update processing on the first resource quota based on the payment processing result.
  • FIG1 is a processing flow chart of a resource quota processing method provided by one or more embodiments of this specification.
  • FIG2 is a processing sequence diagram of a resource quota processing method applied to a rights and interests scenario provided by one or more embodiments of this specification.
  • FIG3 is a processing flow chart of another resource quota processing method provided by one or more embodiments of this specification.
  • FIG4 is a schematic diagram of a resource quota processing device provided by one or more embodiments of this specification.
  • FIG5 is a schematic diagram of another resource quota processing device provided by one or more embodiments of this specification.
  • FIG6 is a schematic diagram of the structure of a resource quota processing device provided by one or more embodiments of this specification.
  • FIG. 7 is a schematic diagram of the structure of another resource quota processing device provided by one or more embodiments of this specification.
  • the present specification provides an embodiment of a resource quota processing method:
  • the resource quota processing method provided in this embodiment can be applied to a first platform. After obtaining a jump instruction for application jump submitted by an institutional member based on a payment request in a first application, the first resource quota is frozen, the first resource quota is synchronized to a second platform, and the second resource quota of the second platform is unfrozen, so as to update the second resource quota based on the first resource quota after unfreezing, and after detecting a successful payment result returned by the second platform, the remaining resource quota of the second platform is frozen.
  • the first resource quota is unfrozen and the quota update processing is performed, thereby realizing synchronous processing of the resource quotas of the first platform and the second platform.
  • the resource quota of another platform is frozen until the payment is completed, thereby avoiding overpayment by institutional members and resource loss of institutional members and institutions, and ensuring the resource quota. To achieve reasonable control.
  • the resource quota processing method provided in this embodiment specifically includes steps S102 to S108 .
  • Step S102 freezing the first resource quota according to the jump instruction for application jump submitted by the institution member in the first application based on the payment request.
  • the organization includes various forms of organizations such as enterprises, institutions, social groups, etc.
  • the organization includes not only the organization at the same level, but also the internal organization of the organization, such as the enterprise department or branch.
  • the organization members include the organization staff and/or organization-related personnel.
  • the first application includes an application that runs independently on a member terminal of an institution member, or a subprogram or applet installed in a third-party application.
  • the first platform includes a platform corresponding to the first application, and the first platform may be a platform for issuing resource quotas to the institution members of the institution.
  • the application jump includes jumping from the first application to the second application; optionally, the first application includes an application that runs on a member terminal of the institution member; the second application includes a subprogram installed in a third-party application, and the third-party application can run independently on a member terminal of an institution member.
  • the member terminal includes a terminal device of an institution member; the second platform includes a platform corresponding to the second application.
  • institutional members can conduct transactions based on resource quotas on the first platform and the second platform, that is, the first platform and the second platform are trading platforms for institutional members to conduct transactions based on resource quotas, and the first platform and the second platform may have their own resource quotas.
  • the institution can directly issue resource quotas to the first platform, and the institutional members of the institution can conduct transactions based on the resource quota, that is, the institutional members of the institution correspond to the same resource quota.
  • the institution can also issue resource quotas to institutional members on the first platform, that is, the institutional members of the institution correspond to the same or different resource quotas; the first resource quota includes the first equity resource quota.
  • the first resource quota can be the resource quota of the institutional members or the resource quota of the institution.
  • the first resource quota is the welfare resource quota of the institutional members, or the welfare resource quota of the institution, and the institutional members can consume the welfare resource quota of the institution.
  • the organization can issue resources to its members.
  • it can be detected whether the initial resource quota of the first platform is in a frozen state. If the initial resource quota is not in a frozen state, the initial resource quota is updated based on the issued resource quota, that is, before the first resource quota is frozen and executed according to the jump instruction for application jump submitted by the organization member in the first application based on the payment request, if the initial resource quota detected according to the resource issuance instruction submitted by the organization member to which the organization member belongs is not in a frozen state, the resource issuance quota carried by the resource issuance instruction is updated to the first application based on the issued resource quota.
  • the initial resource quota is updated to obtain the first resource quota.
  • the following operation is also performed: according to the resource issuance instruction submitted by the institution to which the institutional member belongs, check whether the initial resource quota is in a frozen state; if not, update the initial resource quota based on the issuance resource quota carried by the resource issuance instruction to obtain the first resource quota; if so, do not process it or recheck whether the initial resource quota is in a frozen state at a preset time interval.
  • the initial resource quota refers to the resource quota of the first platform before the quota is updated based on the issued resource quota; the issued resource quota refers to the resource quota issued to the members of the institution.
  • the initial resource quota of the first platform is in a frozen state. If not, the initial resource quota of the first platform is updated based on the issuance resource quota carried by the resource issuance instruction to obtain the first resource quota.
  • institutional members can conduct transactions based on resource quotas on the first platform, and on the other hand, they can also conduct transactions based on resource quotas on the second platform.
  • the following operations are also performed: obtaining the transaction order submitted by the institutional member through the first application; deducting the initial resource quota according to the transaction order to obtain the first resource quota.
  • the initial order of the first platform will be adjusted according to the order amount of the transaction order submitted by the institutional members through the first application.
  • the initial resource quota is deducted to obtain the first resource quota.
  • the jump instruction for application jump submitted by the organization member based on the payment request in the first application is obtained, and the first resource quota of the first platform is frozen according to the jump instruction, so as to avoid the organization member from making payments based on the resource quota on the first platform and the second platform at the same time, and effectively manage the resource quota of multiple platforms.
  • the jump instruction for application jump submitted by the organization member based on the payment request in the first application can be obtained, the jump instruction is intercepted and processed, and the first resource quota of the first platform is frozen. After that, the first platform can configure a preset time period.
  • the organization After the organization registers for services on the first platform, it can allocate resource quotas to its members on the first platform, and the first platform configures the resource quotas of its members on the second platform through interface calls.
  • Step S104 synchronize the first resource quota to the second platform, and unfreeze the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing.
  • the first resource quota is frozen according to the jump instruction for application jump submitted by the institution member in the first application based on the payment request.
  • the first resource quota is synchronized to the second platform, and the second resource quota of the second platform is unfrozen, so as to update the second resource quota based on the first resource quota after unfreezing.
  • the first resource quota of the first platform can be synchronized to the second platform, and the second resource quota of the second platform can be unfrozen, so that the second resource quota can be updated based on the first resource quota after unfreezing.
  • the second resource quota is frozen after the previous payment processing based on the institution identification.
  • the first platform synchronizes the first resource quota of the first platform to the second platform, and calls the resource processing interface to unfreeze the second resource quota of the second platform, so that the second resource quota can be updated based on the first resource quota after unfreezing.
  • the member terminal of the institution member jumps from the first application to the second application.
  • the second platform After the second platform receives the synchronized first resource quota, it can process the payment of the transaction orders submitted by the institutional members based on the institutional identification according to the first resource quota, calculate the remaining resource quota of the second platform, and mark the transaction data to obtain the transaction data.
  • the second platform after the second platform receives the synchronized first resource quota, it performs the following operations: calling the payment interface, and processing the payment of the transaction orders submitted by the institutional members based on the institutional identification according to the first resource quota after the application jumps; calculating the remaining resource quota based on the initial transaction data obtained from the payment processing and the first resource quota, and marking the initial transaction data based on the jump parameters of the application jump to obtain the transaction data.
  • the organization identification includes an organization code, which refers to an identification code set by the organization for the payment of organization members, etc.
  • the organization code can uniquely identify the organization.
  • the organization code can exist in the form of identification codes such as QR code, bar code, and sound code.
  • the organization code can be associated with the resource quota of the organization on the second platform or the resource quota of the organization members on the second platform.
  • the organization members can use the organization code to make payments based on the resource quota of the second platform.
  • the organization code can also be used for invoicing, reimbursement and other processing.
  • the transaction order is submitted after the organization identification displayed on the member terminal of the organization member is scanned.
  • the jump parameter includes a transaction identifier assigned to the second platform.
  • the first platform may assign a transaction identifier to the second platform, and pass it through the jump parameter during the process of jumping from the first application to the second application.
  • the second platform after the second platform receives the synchronized first resource quota, it updates the second resource quota of the second platform based on the first resource quota, calls the payment interface, and processes the payment of the transaction order submitted by the institution member based on the institution identification according to the first resource quota after the application jumps, deducts the first resource quota according to the transaction amount obtained from the payment processing to obtain the remaining resource quota, and marks the initial transaction data based on the transaction identification to obtain the transaction data.
  • the second platform stores the remaining resource quota, that is, updates the first resource quota of the second platform to the remaining resource quota, and returns a payment success result to the first platform.
  • the payment success result returned by the second platform may be lost.
  • the preset time period is configured after the first resource quota is frozen.
  • the remaining resource quota of the second platform is frozen through an interface call, and if the freezing fails, the remaining resource quota is frozen according to the retry time interval until the freezing is successful, and then the first resource quota is unfrozen and the quota update is performed.
  • Step S106 If a successful payment result is detected returned by the second platform, the remaining resource amount of the second platform is frozen through an interface call.
  • the above-mentioned first platform synchronizes the first resource quota to the second platform, and unfreezes the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing.
  • the remaining resource quota of the second platform is frozen through an interface call. If no successful payment result returned by the second platform is detected, no processing is performed.
  • the remaining resource quota of the second platform is frozen through an interface call. If the freezing fails, the transaction of the representative organization member on the second platform has not been completed, and no processing is required at this time.
  • the payment success result is returned by the second platform within a preset time period, and the payment success result carries the remaining resource amount; the preset time period is configured after the first resource amount is frozen, that is, the first platform configures the preset time period after freezing the first resource amount of the first platform as described above.
  • the payment success result returned by the second platform is detected within the preset time period, the remaining resource amount of the second platform is frozen through an interface call.
  • this embodiment provides an optional implementation, in which the preset time period is calculated in the following way: obtaining the historical transaction duration and/or transaction preference data of the institutional members on the second platform; calculating the preset time period based on the historical transaction duration and/or the transaction preference data; optionally, the transaction preference data includes the display duration of the transaction store type and/or the institutional logo.
  • the process of calculating the preset time period based on the transaction preference data can be as follows: if the transaction store type is the first type, the preset time period is determined to be the first time period; if the transaction store type is the second type, the preset time period is determined to be the second time period; for example, the first type is a type where the transaction waiting time is greater than or equal to a time threshold, and the second type is a type where the transaction waiting time is less than a time threshold.
  • the transaction data can be queried from the second platform based on the detection of the successful payment result returned by the second platform.
  • the jump parameters include a transaction identifier assigned to the second platform.
  • the transaction identifier refers to a current transaction performed by an institution member on the second platform based on the institution identifier.
  • Step S108 unfreeze the first resource quota and perform quota update processing.
  • the remaining resource quota of the second platform is frozen through an interface call.
  • the first resource quota of the first platform is unfrozen and the quota is updated.
  • the payment success result may be lost, and on the other hand, the remaining resource quota of the second platform carried in the payment success result may also be lost.
  • the first resource quota in order to improve the comprehensiveness and accuracy of the quota update processing, on the one hand, the first resource quota can be updated according to the remaining resource quota carried in the payment success result, and on the other hand, the first resource quota can be updated according to the transaction data of the institution members on the second platform. Processing, thereby improving the flexibility of the quota update processing.
  • the quota update processing includes: calculating the transaction resource amount based on the transaction data of the institutional members on the second platform; updating the first resource quota based on the transaction resource amount; or, updating the first resource quota based on the remaining resource quota carried in the successful payment result.
  • the quota update processing can be performed in combination with the transaction data and the remaining resource quota.
  • the quota update processing can also be achieved in the following way: if the transaction resource amount of the institutional member on the second platform is consistent with the remaining resource amount carried in the successful payment result, the first resource quota of the first platform is updated based on the remaining resource amount; if the transaction resource amount of the institutional member on the second platform is inconsistent with the remaining resource amount carried in the successful payment result, the first resource quota of the first platform is updated based on the transaction resource amount; optionally, the transaction resource quota is calculated based on the transaction data of the institutional member on the second platform.
  • institutional members can conduct transactions on the second platform based on institutional identification, or they can conduct online transactions on the first platform.
  • the following operations are also performed: obtaining the transaction order submitted by the institutional member through the first application; deducting the target resource quota obtained by the update process according to the transaction order.
  • the organization can also issue resources. It should be noted that the organization can issue resources on the first platform.
  • the following operations are also performed: according to the resource issuance instruction submitted by the organization to which the organization member belongs, it is detected whether the target resource quota obtained by the update processing is in a frozen state; if not, the target resource quota is updated based on the issuance resource quota carried by the resource issuance instruction to obtain an updated resource quota.
  • institutional members can conduct continuous online transactions on the first platform, and can also conduct continuous offline transactions on the second platform based on the institutional identity.
  • the resource quota processing method applied to the rights and interests scenario includes the following steps.
  • Step S202 Freeze the first resource quota according to a jump instruction for application jump submitted by the institution member in the equity application based on the payment request.
  • Step S204 synchronize the first resource quota to the institution code platform, and unfreeze the second resource quota of the institution code platform through an interface call.
  • Step S214 If a successful payment result is detected from the institution code platform within a preset time period, the remaining resource amount of the institution code platform is frozen through an interface call.
  • Step S216 calling the data interface to query transaction data from the institution code platform according to the jump parameters of the application jump.
  • Step S218, calculating the transaction resource amount according to the queried transaction data, and updating the first resource quota of the equity platform according to the transaction resource amount.
  • the implementation process of the resource quota processing method applied to the equity scenario provided above is executed by the first platform, and the implementation process of the resource quota processing method applied to the equity scenario provided in the following method embodiment is executed by the second platform.
  • the two cooperate with each other during the execution process. Therefore, please refer to the corresponding content of the following method embodiment when reading the above implementation process. Correspondingly, please refer to the corresponding content of this method embodiment when reading the implementation process of the resource quota processing method applied to the equity scenario below.
  • the resource quota processing method provided in this embodiment can be applied to the second platform, receiving the first resource quota synchronized by the jump instruction of the first platform based on the application jump, so as to update the second resource quota based on the first resource quota, and after jumping from the first application to the second application, performing payment processing on the transaction order submitted by the institution member based on the institution identification according to the first resource quota, and performing quota update processing on the first resource quota based on the payment processing result, thereby realizing the synchronous processing of the resource quota of the first platform and the second platform, and freezing the resource quota of the other platform until the payment is completed while the institution member is making payment on one platform. It can avoid overpayment by members of the organization, avoid loss of resources for members and the organization, and achieve reasonable control over resource quotas.
  • the resource quota processing method provided in this embodiment specifically includes steps S302 to S306 .
  • the implementation process of the resource quota processing method provided in this embodiment can be executed by the second platform, and the implementation process of the resource quota processing method provided in the above method embodiment can be executed by the first platform.
  • the two cooperate with each other during the execution process. Therefore, please refer to the corresponding content of the present method embodiment for reading the implementation process of the resource quota processing method provided in the above method embodiment.
  • the corresponding content of the above method embodiment for reading the implementation process of the resource quota processing method provided in this embodiment.
  • Step S302 receiving a first resource quota synchronized by a jump instruction of a first platform based on an application jump, so as to update a second resource quota based on the first resource quota.
  • the organization includes various forms of organizations such as enterprises, institutions, social groups, etc.
  • the organization includes not only the organization at the same level, but also the internal organization of the organization, such as the enterprise department or branch.
  • the organization members include the organization staff and/or organization-related personnel.
  • the first application includes an application that runs independently on a member terminal of an institution member, or a subprogram or applet installed in a third-party application.
  • the first platform includes a platform corresponding to the first application, and the first platform may be a platform for issuing resource quotas to the institution members of the institution.
  • the application jump includes jumping from the first application to the second application; optionally, the first application includes an application that runs on a member terminal of the institution member; the second application includes a subprogram installed in a third-party application, and the third-party application can run independently on a member terminal of an institution member.
  • the member terminal includes a terminal device of an institution member; the second platform includes a platform corresponding to the second application.
  • institutional members can conduct transactions based on resource quotas on the first platform and the second platform, that is, the first platform and the second platform are trading platforms for institutional members to conduct transactions based on resource quotas, and the first platform and the second platform may have their own resource quotas.
  • the first platform freezes the first resource quota according to the jump instruction for application jump submitted by the institution member in the first application based on the payment request, and synchronizes the first resource quota to the second platform, and unfreezes the second resource quota of the second platform.
  • the second platform receives the first resource quota synchronized by the jump instruction of the first platform based on the application jump, so as to update the second resource quota based on the first resource quota.
  • the second resource quota was frozen after the previous payment processing based on the institution identification.
  • the first platform before synchronizing the first resource quota, the first platform further performs the following operation: freezing the first resource quota according to a jump instruction for application jump submitted by the institution member in the first application based on the payment request.
  • the institution can directly issue resource quotas to the first platform, and the institutional members of the institution can conduct transactions based on the resource quota, that is, the institutional members of the institution correspond to the same resource quota.
  • the institution can also issue resource quotas to institutional members on the first platform, that is, the institutional members of the institution correspond to the same or different resource quotas; the first resource quota includes the first equity resource quota.
  • the first resource quota can be the resource quota of the institutional members or the resource quota of the institution.
  • the first resource quota is the welfare resource quota of the institutional members, or the welfare resource quota of the institution, and the institutional members can consume the welfare resource quota of the institution.
  • the organization can issue resources to the organization members.
  • the first platform can detect whether the initial resource quota of the first platform is in a frozen state.
  • the initial resource quota is updated based on the issued resource quota, that is, before freezing and executing the first resource quota according to the jump instruction for application jump submitted by the organization member in the first application based on the payment request, if the initial resource quota detected according to the resource issuance instruction submitted by the organization to which the organization member belongs is not in a frozen state, the initial resource quota is updated based on the issuance resource quota carried by the resource issuance instruction to obtain the first resource quota.
  • the first platform before freezing and executing the first resource quota according to the jump instruction for application jump submitted by the organization member in the first application based on the payment request, the first platform also performs the following operations: according to the organization to which the organization member belongs The resource issuance instruction submitted is used to detect whether the initial resource quota is in a frozen state; if not, the initial resource quota is updated based on the resource issuance quota carried by the resource issuance instruction to obtain the first resource quota; if so, no processing is performed or the initial resource quota is re-checked at a preset time interval to determine whether it is in a frozen state.
  • the initial resource quota refers to the resource quota of the first platform before the quota is updated based on the issued resource quota; the issued resource quota refers to the resource quota issued to the members of the institution.
  • the initial resource quota of the first platform is in a frozen state. If not, the initial resource quota of the first platform is updated based on the issuance resource quota carried by the resource issuance instruction to obtain the first resource quota.
  • institutional members can conduct transactions based on resource quotas on the first platform, and on the other hand, they can also conduct transactions based on resource quotas on the second platform.
  • the first platform freezes and executes the first resource quota according to the jump instruction for application jump submitted by the institutional member in the first application based on the payment request, it also performs the following operations: obtaining the transaction order submitted by the institutional member through the first application; deducting the initial resource quota according to the transaction order to obtain the first resource quota.
  • the first platform deducts the initial resource quota of the first platform according to the order amount of the transaction order submitted by the institution member through the first application to obtain the first resource quota.
  • the first platform obtains the jump instruction for application jump submitted by the organization member in the first application based on the payment request, and freezes the first resource quota of the first platform according to the jump instruction, so as to avoid the organization member from making payments based on the resource quota on the first platform and the second platform at the same time, and effectively manages the resource quota of multiple platforms.
  • the first platform can obtain the jump instruction for application jump submitted by the organization member in the first application based on the payment request, intercept and process the jump instruction, and freeze the first resource quota of the first platform. After that, the first platform can configure a preset time period.
  • the above-mentioned first platform freezes the first resource quota according to the jump instruction for application jump submitted by the institution member in the first application based on the payment request. After that, the first platform synchronizes the first resource quota to the second platform and unfreezes the second resource quota of the second platform to update the second resource quota based on the first resource quota after unfreezing.
  • the first platform may synchronize the first resource quota of the first platform to the second platform, and unfreeze the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing.
  • the second resource quota is frozen after the previous payment processing based on the institution identification.
  • the first platform synchronizes the first resource quota of the first platform to the second platform, and calls the resource processing interface to unfreeze the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing.
  • the second platform receives the first resource quota synchronized by the first platform, and updates the second resource quota based on the first resource quota.
  • the member terminal of the institution member jumps from the first application to the second application.
  • Step S304 calling the payment interface, and performing payment processing on the transaction order submitted by the institution member based on the institution identifier according to the first resource quota after jumping from the first application to the second application.
  • the above-mentioned first platform receives the first resource quota synchronized by the jump instruction of the first platform based on the application jump, so as to update the second resource quota based on the first resource quota.
  • the payment interface is called, and after jumping from the first application to the second application, the transaction order submitted by the institutional member based on the institutional identifier is processed according to the first resource quota.
  • the organization identification described in this embodiment includes an organization code, which refers to an identification code set by the organization for the payment of organization members, etc.
  • the organization code can uniquely identify the organization.
  • the organization code can exist in the form of identification codes such as QR code, bar code, and sound code.
  • the organization code can be associated with the resource quota of the organization on the second platform or the resource quota of the organization members on the second platform.
  • the organization members can use the organization code to make payments based on the resource quota of the second platform.
  • the organization code can also be used for invoicing, reimbursement and other processing.
  • the transaction order is submitted after the organization identification displayed on the member terminal of the organization member is scanned.
  • Step S306 updating the first resource quota based on the payment processing result.
  • the above-mentioned payment interface is called, and after jumping from the first application to the second application, payment processing is performed on the transaction order submitted by the institution member based on the institution identification according to the first resource quota. In this step, the first resource quota is updated based on the payment processing result.
  • the first resource quota is deducted according to the initial transaction amount obtained by payment processing to obtain the remaining resource quota.
  • the second platform stores the remaining resource quota, that is, updates the first resource quota of the second platform to the remaining resource quota, and marks the initial transaction data based on the jump parameters of the application jump, obtains the transaction data, and returns the payment success result to the first platform.
  • the quota update processing includes: calculating the remaining resource quota according to the initial transaction data in the payment processing result and the first resource quota; and updating the first resource quota to the remaining resource quota.
  • initial transaction data is marked based on the jump parameter of the application jump to obtain transaction data.
  • the jump parameter includes a transaction identifier assigned to the second platform.
  • the first platform may assign a transaction identifier to the second platform, and pass it through the jump parameter during the process of jumping from the first application to the second application.
  • the following operation is also performed: returning the payment success result to the first platform to freeze the remaining resource quota of the second platform through an interface call, unfreeze the first resource quota of the first platform and perform quota update processing.
  • this embodiment provides an optional implementation in which the first platform synchronizes the first resource quota to the second platform and unfreezes the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing, and then performs the following operations: if the payment success result is not detected within the preset time period, freeze the remaining resource quota through an interface call; if the freezing fails, retry the freezing operation according to the retry time interval.
  • the preset time period is configured after the first resource quota is frozen.
  • the first platform if it does not detect a successful payment result returned by the second platform within a preset time period, it freezes the remaining resource quota of the second platform through an interface call, and if the freezing fails, freezes the remaining resource quota according to the retry time interval until the freezing is successful, then unfreezes the first resource quota and performs quota update processing.
  • the above-mentioned first platform synchronizes the first resource quota to the second platform, and unfreezes the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing. After that, if the first platform detects the successful payment result returned by the second platform, it freezes the remaining resource quota of the second platform through an interface call. If the successful payment result returned by the second platform is not detected, no processing is performed.
  • the first platform detects a successful payment result returned by the second platform, it freezes the remaining resource quota of the second platform through an interface call. If the freezing fails, the transaction of the representative organization members on the second platform has not been completed, and no processing is required at this time.
  • the payment success result is returned by the second platform within a preset time period, and the payment success result carries the remaining resource amount; the preset time period is configured after the first resource amount is frozen, that is, the first platform configures the preset time period after freezing the first resource amount of the first platform as described above.
  • the payment success result returned by the second platform is detected within the preset time period, the remaining resource amount of the second platform is frozen through an interface call.
  • the preset time period is calculated by the following method: obtaining the historical payment history of the institution members on the second platform; Transaction duration and/or transaction preference data; calculating the preset time period based on the historical transaction duration and/or the transaction preference data; optionally, the transaction preference data includes the display duration of the transaction store type and/or institution logo.
  • the process of calculating the preset time period based on the transaction preference data can be as follows: if the transaction store type is the first type, the preset time period is determined to be the first time period; if the transaction store type is the second type, the preset time period is determined to be the second time period; for example, the first type is a type where the transaction waiting time is greater than or equal to a time threshold, and the second type is a type where the transaction waiting time is less than a time threshold.
  • the first platform detects a successful payment result returned by the second platform, it freezes the remaining resource quota of the second platform through an interface call. After that, the first platform unfreezes the first resource quota and performs quota update processing.
  • the transaction data can be queried from the second platform based on the detection of the successful payment result returned by the second platform.
  • the jump parameters include a transaction identifier assigned to the second platform.
  • the transaction identifier refers to a current transaction performed by an institution member on the second platform based on the institution identifier.
  • the result of successful payment may be lost, and on the other hand, the remaining resource quota of the second platform carried in the result of successful payment may also be lost.
  • the first platform in order to improve the comprehensiveness and accuracy of the quota update processing, on the one hand, the first platform can update the first resource quota according to the remaining resource quota carried in the result of successful payment, and on the other hand, the first platform can update the first resource quota according to the transaction data of the institutional members on the second platform, thereby improving the flexibility of the quota update processing.
  • the above-mentioned first platform performs quota update processing in the following manner: calculating the transaction resource amount according to the transaction data of the institutional members on the second platform; updating the first resource quota according to the transaction resource amount; or, updating the first resource quota according to the remaining resource amount carried in the result of successful payment.
  • the first platform can perform quota update processing on two levels: transaction data and remaining resource quota. Specifically, the first platform performs quota update processing in the following manner: if the transaction resource amount of the institutional member on the second platform is consistent with the remaining resource amount carried in the successful payment result, the first resource quota of the first platform is updated based on the remaining resource amount; if the transaction resource amount of the institutional member on the second platform is inconsistent with the remaining resource amount carried in the successful payment result, the first resource quota of the first platform is updated based on the transaction resource amount; optionally, the transaction resource amount is calculated based on the transaction data of the institutional member on the second platform.
  • institutional members can conduct transactions on the second platform based on institutional identification, or they can conduct online transactions on the first platform.
  • the first platform after the first platform unfreezes the first resource quota and performs quota update processing, it also performs the following operations: obtaining the transaction order submitted by the institutional member through the first application; deducting the target resource quota obtained by the update processing according to the transaction order.
  • the organization can also distribute resources. It should be noted that the organization can distribute resources on the first platform.
  • the first platform after the first platform unfreezes the first resource quota and performs quota update processing, it also performs the following operations: according to the resource issuance instruction submitted by the organization to which the organization member belongs, check whether the target resource quota obtained by the update processing is in a frozen state; if not, update the target resource quota based on the issuance resource quota carried by the resource issuance instruction to obtain an updated resource quota.
  • the resource quota processing method applied to the rights and interests scenario specifically includes the following steps.
  • Step S206 receiving the first resource quota synchronized by the equity platform based on the jump instruction of the application jump, and based on The first resource quota updates the second resource quota.
  • Step S208 calling the payment interface, after jumping from the equity application to the institution code application, performing payment processing on the transaction order submitted by the institution member based on the institution code according to the first resource quota.
  • Step S210 calculating the remaining resource quota according to the initial transaction data obtained by the payment processing and the first resource quota, and marking the initial transaction data based on the jump parameter of the application jump to obtain transaction data.
  • Step S212 returning the payment success result to the equity platform.
  • An embodiment of a resource quota processing device provided in this specification is as follows: In the above embodiment, a resource quota processing method applied to a first platform is provided, and correspondingly, a resource quota processing device running on the first platform is also provided, which is described below in conjunction with the accompanying drawings.
  • FIG. 4 it shows a schematic diagram of a resource quota processing device provided by this embodiment.
  • the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above.
  • the device embodiment described below is only illustrative.
  • This embodiment provides a resource quota processing device, which runs on a first platform, including: a first resource quota freezing module 402, configured to freeze a first resource quota according to a jump instruction for application jump submitted by an institution member in a first application based on a payment request; a resource quota synchronization module 404, configured to synchronize the first resource quota to a second platform, and unfreeze the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing; a remaining resource quota freezing module 406, configured to freeze the remaining resource quota of the second platform through an interface call if a successful payment result returned by the second platform is detected; a first quota update module 408, configured to unfreeze the first resource quota and perform quota update processing.
  • a first resource quota freezing module 402 configured to freeze a first resource quota according to a jump instruction for application jump submitted by an institution member in a first application
  • Another embodiment of a resource quota processing device provided in this specification is as follows: In the above embodiment, a resource quota processing method applied to a second platform is provided, and correspondingly, a resource quota processing device running on the second platform is also provided, which is described below in conjunction with the accompanying drawings.
  • FIG. 5 there is shown a schematic diagram of a resource quota processing device provided in this embodiment.
  • the description is relatively simple, and the relevant parts can refer to the corresponding description of the method embodiment provided above.
  • the device embodiment described below is only illustrative.
  • This embodiment provides a resource quota processing device, which runs on a second platform, including: a resource quota receiving module 502, which is configured to receive a first resource quota synchronized by a jump instruction of a first platform based on an application jump, and update a second resource quota based on the first resource quota; the second resource quota is frozen after the previous payment processing based on the institution identification; a payment processing module 504, which is configured to call a payment interface, and after jumping from the first application to the second application, perform payment processing on a transaction order submitted by an institution member based on the institution identification according to the first resource quota; a second quota updating module 506, which is configured to perform quota update processing on the first resource quota based on the payment processing result.
  • a resource quota receiving module 502 which is configured to receive a first resource quota synchronized by a jump instruction of a first platform based on an application jump, and update a second resource quota based on the first resource
  • FIG. 6 is a structural schematic diagram of a resource quota processing device provided by one or more embodiments of this specification.
  • a resource quota processing device includes: as shown in FIG6, the resource quota processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 601 and memory 602, and the memory 602 may store one or more storage applications or data. Among them, the memory 602 can be a temporary storage or a permanent storage.
  • the application stored in the memory 602 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the resource quota processing device.
  • the processor 601 may be configured to communicate with the memory 602 to execute a series of computer executable instructions in the memory 602 on the resource quota processing device.
  • the resource quota processing device may also include one or more processors 601 and a memory 602. One or more power supplies 603, one or more wired or wireless network interfaces 604, one or more input/output interfaces 605, one or more keyboards 606, etc.
  • a resource quota processing device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the resource quota processing device, and is configured to be executed by one or more processors.
  • the one or more programs include the following computer executable instructions: freezing the first resource quota according to a jump instruction for application jump submitted by an institution member in the first application based on a payment request; synchronizing the first resource quota to the second platform, and unfreezing the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing; if a successful payment result returned by the second platform is detected, freezing the remaining resource quota of the second platform through an interface call; unfreezing the first resource quota and performing quota update processing.
  • FIG. 7 is a structural schematic diagram of a resource quota processing device provided by one or more embodiments of this specification.
  • a resource quota processing device includes: As shown in FIG. 7, the resource quota processing device may have relatively large differences due to different configurations or performances, and may include one or more processors 701 and memory 702, and the memory 702 may store one or more storage applications or data. Among them, the memory 702 may be a temporary storage or a permanent storage.
  • the application stored in the memory 702 may include one or more modules (not shown in the figure), and each module may include a series of computer executable instructions in the resource quota processing device.
  • the processor 701 may be configured to communicate with the memory 702, and execute a series of computer executable instructions in the memory 702 on the resource quota processing device.
  • the resource quota processing device may also include one or more power supplies 703, one or more wired or wireless network interfaces 704, one or more input/output interfaces 705, one or more keyboards 706, etc.
  • a resource quota processing device includes a memory, and one or more programs, wherein the one or more programs are stored in the memory, and the one or more programs may include one or more modules, and each module may include a series of computer executable instructions in the resource quota processing device, and is configured to be executed by one or more processors.
  • the one or more programs include the following computer executable instructions: receiving a first resource quota synchronized by a jump instruction of a first platform based on an application jump, and updating a second resource quota based on the first resource quota; the second resource quota is frozen after the previous payment processing based on the institution identification; calling a payment interface, and after jumping from the first application to the second application, performing payment processing on a transaction order submitted by an institution member based on the institution identification according to the first resource quota; and performing quota update processing on the first resource quota based on the payment processing result.
  • An embodiment of a storage medium provided in this specification is as follows: Corresponding to the resource quota processing method applied to the first platform described above, 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 by the processor: freezing the first resource quota according to the jump instruction for application jump submitted by the institution member in the first application based on the payment request; synchronizing the first resource quota to the second platform, and unfreezing the second resource quota of the second platform, so as to update the second resource quota based on the first resource quota after unfreezing; if a successful payment result returned by the second platform is detected, freezing the remaining resource quota of the second platform through an interface call; unfreezing the first resource quota and performing quota update processing.
  • Another storage medium embodiment provided in this specification is as follows: Corresponding to the resource quota processing method applied to the second platform described above, 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, which implement the following process when executed by a processor: receiving a first resource quota synchronized by a jump instruction based on an application jump of a first platform, and updating a second resource quota based on the first resource quota; the second resource quota is frozen after the previous payment processing based on the institution identification; calling a payment interface, and performing payment processing on a transaction order submitted by an institution member based on the institution identification according to the first resource quota after jumping from the first application to the second application; and performing quota update processing on the first resource quota based on the payment processing result.
  • a hardware improvement for example, improvements to the circuit structure of diodes, transistors, switches, etc.
  • a software improvement improvement of the method flow.
  • PLD programmable logic device
  • FPGA field programmable gate array
  • HDL Hardware Description Language
  • HDL Very-High-Speed Integrated Circuit Hardware Description Language
  • ABEL Advanced Boolean Expression Language
  • AHDL Altera Hardware Description Language
  • HDCal Joint CHDL
  • JHDL Java Hardware Description Language
  • Lava Lava
  • Lola MyHDL
  • PALASM RHDL
  • VHDL Very-High-Speed Integrated Circuit Hardware Description Language
  • Verilog Verilog
  • the controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (such as software or firmware) executable by the (micro)processor, a logic gate, a switch, an application specific integrated circuit (ASIC),
  • a computer-readable program code such as software or firmware
  • 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.
  • the controller can be implemented in the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers and embedded microcontrollers by logically programming the method steps. Therefore, this controller can be considered as a hardware component, and the devices included therein for implementing various functions can also be regarded as structures within the hardware component. Or even, the devices for implementing various functions can be regarded as both software modules for implementing the method and structures within the hardware component.
  • a typical implementation 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 a combination of any of these devices.
  • the above device is described by dividing it into various units according to its functions.
  • the functions of each unit can be implemented in the same or multiple software and/or hardware.
  • one or more embodiments of this specification may be provided as a method, system or computer program product. Therefore, one or more embodiments of this specification may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, this specification may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
  • 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 that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device that implements the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and/or one or more boxes in the block diagram.
  • a computing device includes one or more processors (CPU), input/output interfaces, network interfaces, and memory.
  • processors CPU
  • input/output interfaces network interfaces
  • memory volatile and non-volatile memory
  • Memory may include non-permanent storage in a computer-readable medium, in the form of random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
  • RAM random access memory
  • ROM read-only memory
  • flash RAM flash memory
  • Computer-readable media include permanent and non-permanent, removable and non-removable media that can store information by any method or technology.
  • the information can be computer-readable instructions, data structures, program modules 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 disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device.
  • computer-readable media does not include transitory media such as modulated data signals and carrier waves.
  • One or more embodiments of the present specification may be described in the general context of computer-executable instructions executed by a computer, such as program modules.
  • program modules include routines, programs, objects, components, data structures, etc. that perform specific tasks or implement specific abstract data types.
  • One or more embodiments of the present specification may also be practiced in distributed computing environments where tasks are performed by remote processing devices connected through a communication network.
  • program modules may be located in local and remote computer storage media, including storage devices.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Finance (AREA)
  • Theoretical Computer Science (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

提供一种资源额度处理方法及装置。所述资源额度处理方法包括：根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度；若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度；对所述第一资源额度进行解冻并进行额度更新处理。

Description

资源额度处理方法及装置 技术领域
本文件涉及数据处理技术领域，尤其涉及一种资源额度处理方法及装置。
背景技术
随着互联网技术的不断发展，越来越多的机构选择线上方式向机构成员分配相应的资源额度，机构成员基于机构分配的资源额度可进行交易，在实际的应用场景中，机构在多个平台针对机构成员分配对应的资源额度，使得机构成员可在多个平台进行交易，提升基于资源额度进行交易的便捷性。
发明内容
本说明书一个或多个实施例提供了一种资源额度处理方法，应用于第一平台，包括：根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结。向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度。若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度。对所述第一资源额度进行解冻并进行额度更新处理。
本说明书一个或多个实施例提供了另一种资源额度处理方法，应用于第二平台，包括：接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结。调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理。基于支付处理结果对所述第一资源额度进行额度更新处理。
本说明书一个或多个实施例提供了一种资源额度处理装置，运行于第一平台，包括：第一资源额度冻结模块，被配置为根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结。资源额度同步模块，被配置为向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度。剩余资源额度冻结模块，被配置为若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度。第一额度更新模块，被配置为对所述第一资源额度进行解冻并进行额度更新处理。
本说明书一个或多个实施例提供了另一种资源额度处理装置，运行于第二平台，包括：资源额度接收模块，被配置为接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结。支付处理模块，被配置为调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理。第二额度更新模块，被配置为基于支付处理结果对所述第一资源额度进行额度更新处理。
本说明书一个或多个实施例提供了一种资源额度处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结。向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度。若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度。对所述第一资源额度进行解冻并进行额度更新处理。
本说明书一个或多个实施例提供了另一种资源额度处理设备，包括：处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处 理器：接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结。调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理。基于支付处理结果对所述第一资源额度进行额度更新处理。
本说明书一个或多个实施例提供了一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结。向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度。若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度。对所述第一资源额度进行解冻并进行额度更新处理。
本说明书一个或多个实施例提供了另一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结。调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理。基于支付处理结果对所述第一资源额度进行额度更新处理。
附图说明
为了更清楚地说明本说明书一个或多个实施例的技术方案，下面将对实施例中所需要使用的附图作简单地介绍，显而易见地，下面描述中的附图仅仅是本说明书中记载的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本说明书一个或多个实施例提供的一种资源额度处理方法处理流程图。
图2为本说明书一个或多个实施例提供的一种应用于权益场景的资源额度处理方法处理时序图。
图3为本说明书一个或多个实施例提供的另一种资源额度处理方法处理流程图。
图4为本说明书一个或多个实施例提供的一种资源额度处理装置示意图。
图5为本说明书一个或多个实施例提供的另一种资源额度处理装置示意图。
图6为本说明书一个或多个实施例提供的一种资源额度处理设备的结构示意图。
图7为本说明书一个或多个实施例提供的另一种资源额度处理设备的结构示意图。
具体实施方式
为了使本技术领域的人员更好地理解本说明书一个或多个实施例中的技术方案，下面将结合本说明书一个或多个实施例中的附图，对本说明书一个或多个实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例仅仅是本说明书的一部分实施例，而不是全部的实施例。基于本说明书一个或多个实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都应当属于本文件的保护范围。
本说明书提供的一种资源额度处理方法实施例：本实施例提供的资源额度处理方法，可应用于第一平台，在获取到机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令后，对第一资源额度进行冻结，向第二平台同步第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度，并在检测到第二平台返回的支付成功结果后，冻结第二平台的剩余资源额度，在此基础山，对第一资源额度进行解冻并进行额度更新处理，以此，实现对第一平台和第二平台的资源额度的同步处理，在机构成员在一个平台进行支付的过程中，冻结另一个平台的资源额度直至支付完成，避免机构成员的超额支付，避免机构成员和机构的资源损失，对资源额 度实现合理的把控。
参照图1，本实施例提供的资源额度处理方法，具体包括步骤S102至步骤S108。
步骤S102，根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结。
本实施例中，机构包括企业、事业单位、社会团体等各种形式的组织，此外，机构不仅包括本级组织，还包括机构的内部组织，比如企业部门或者分部。所述机构成员包括机构工作人员和/或机构相关人员。
所述第一应用，包括独立运行于机构成员的成员终端的应用程序，或者搭载于第三方应用程序内的子程序或者小程序。所述第一平台包括第一应用对应的平台，所述第一平台可以是针对机构的机构成员进行资源额度发放的平台。可选的，所述应用跳转，包括从所述第一应用跳转至第二应用；可选的，所述第一应用，包括运行于所述机构成员的成员终端的应用程序；所述第二应用，包括搭载于第三方应用内的子程序，所述第三方应用可独立运行于机构成员的成员终端。所述成员终端包括机构成员的终端设备；第二平台包括所述第二应用对应的平台。
需要说明的是，机构成员可以在第一平台和第二平台基于资源额度进行交易，即第一平台和第二平台为机构成员基于资源额度进行交易的交易平台，第一平台和第二平台可存在各自的资源额度。
实际应用中，机构可以直接向第一平台发放资源额度，机构的机构成员可基于该资源额度进行交易，即机构的机构成员对应同一资源额度，机构也可以针对机构成员在第一平台发放资源额度，即机构的机构成员对应相同或者不同的资源额度；所述第一资源额度，包括第一权益资源额度，所述第一资源额度可以是机构成员的资源额度，也可以是机构的资源额度，比如第一资源额度是机构成员的福利资源额度，或者机构的福利资源额度，机构成员可以对机构的福利资源额度进行消费。
在实际的应用过程中，机构可向机构成员进行资源发放，在此过程中，为了能够顺利进行资源额度的额度更新，可检测第一平台的初始资源额度是否处于冻结状态，在初始资源额度未处于冻结状态的情况下，基于发放资源额度对初始资源额度进行额度更新，即在根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结执行之前，若根据机构成员所属机构提交的资源发放指令检测到的初始资源额度未处于冻结状态，基于所述资源发放指令携带的发放资源额度对所述初始资源额度进行额度更新，获得所述第一资源额度，本实施例提供的一种可选实施方式中，在根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结执行之前，还执行如下操作：根据所述机构成员所属机构提交的资源发放指令，检测初始资源额度是否处于冻结状态；若否，基于所述资源发放指令携带的发放资源额度对所述初始资源额度进行额度更新，获得所述第一资源额度；若是，不作处理即可或者按照预设时间间隔重新检测初始资源额度是否处于冻结状态。
其中，所述初始资源额度是指第一平台的未基于发放资源额度进行额度更新之前的资源额度；所述发放资源额度是指向机构成员发放的资源额度。
具体的，根据机构成员所属机构提交的资源发放指令，检测第一平台的初始资源额度是否处于冻结状态，若否，基于资源发放指令携带的发放资源额度对第一平台的初始资源额度进行额度更新，获得所述第一资源额度。
实际应用中，机构成员一方面可以基于资源额度在第一平台进行交易，另一方面也可基于资源额度在第二平台进行交易，基于此，本实施例提供的一种可选实施方式中，在根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结执行之前，还执行如下操作：获取所述机构成员通过所述第一应用提交的交易订单；根据所述交易订单对初始资源额度进行扣减，获得所述第一资源额度。
具体的，根据机构成员通过第一应用提交的交易订单的订单数额，对第一平台的初 始资源额度进行扣减，获得第一资源额度。
具体实施时，获取机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，并根据该跳转指令对第一平台的第一资源额度进行冻结，以避免机构成员同时在第一平台和第二平台基于资源额度进行支付，对多平台的资源额度进行有效管理，具体可获取机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对该跳转指令进行拦截处理，并对第一平台的第一资源额度进行冻结。在此之后，第一平台可配置预设时间周期。
需要说明的是，机构在第一平台进行服务注册后，可在第一平台向机构成员分配资源额度，第一平台通过接口调用在第二平台配置机构成员的资源额度。
步骤S104，向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度。
上述根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结，本步骤中，向第二平台同步第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度。
具体实施时，为了保持第一平台和第二平台的资源额度的实时同步，可向第二平台同步第一平台的第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新第二资源额度，可选的，所述第二资源额度在前一次基于机构标识进行支付处理后被冻结。具体的，第一平台向第二平台同步第一平台的第一资源额度，调用资源处理接口对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度。在第一平台对第二平台的第二资源额度进行解冻之后，机构成员的成员终端从第一应用跳转至第二应用。
第二平台接收到同步的第一资源额度后，可按照第一资源额度对机构成员基于机构标识提交的交易订单进行支付处理，并计算第二平台的剩余资源额度，以及对交易数据进行标记处理，获得交易数据，本实施例提供的一种可选实施方式中，所述第二平台接收到同步的第一资源额度后，执行如下操作：调用支付接口，在所述应用跳转后按照所述第一资源额度对所述机构成员基于机构标识提交的交易订单进行支付处理；根据支付处理获得的初始交易数据和所述第一资源额度计算所述剩余资源额度，以及基于所述应用跳转的跳转参数对所述初始交易数据进行标记处理，获得交易数据。
其中，所述机构标识包括机构码，所述机构码是指机构为机构成员的支付等所设置的标识码，该机构码能够唯一标识机构，机构码的存在形式可以是二维码、条形码、声音码等标识码，该机构码可关联机构在第二平台的资源额度或者关联机构成员在第二平台的资源额度，机构成员可通过该机构码基于第二平台的资源额度实现支付。此外，所述机构码也可用于开票、报销等处理。可选的，所述交易订单在机构成员的成员终端展示的机构标识被扫描后提交。
可选的，所述跳转参数，包括向所述第二平台分配的交易标识；实际应用中，在从第一应用跳转至第二应用之前，第一平台可向第二平台分配交易标识，在第一应用跳转至第二应用的过程中通过跳转参数进行传递。
具体的，第二平台接收到同步的第一资源额度后，基于第一资源额度更新第二平台的第二资源额度，调用支付接口，在应用跳转后按照第一资源额度对机构成员基于机构标识提交的交易订单进行支付处理，根据支付处理获得的交易数额对第一资源额度进行扣减，获得所述剩余资源额度，并基于交易标识对初始交易数据进行标记处理，获得交易数据。
在此之后，第二平台对所述剩余资源额度进行存储，即将第二平台的第一资源额度更新为剩余资源额度，并向第一平台返回支付成功结果。
实际应用中，第二平台返回的支付成功结果存在丢失的情况，针对于此，为了及时对第一平台和第二平台的资源额度进行同步，防止机构成员在多个平台出现超额支付的 问题，本实施例提供的一种可选实施方式中，在向第二平台同步第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度执行之后，还执行如下操作：若在预设时间周期内未检测到所述支付成功结果，通过接口调用冻结所述剩余资源额度；在冻结失败的情况下，按照重试时间间隔重试冻结操作。
可选的，所述预设时间周期在所述第一资源额度被冻结后进行配置。
具体的，若在预设时间周期内未检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度，并在冻结失败的情况下，按照重试时间间隔冻结所述剩余资源额度，直至冻结成功后对第一资源额度进行解冻并进行额度更新处理。
步骤S106，若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度。
上述第一平台向第二平台同步第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度，本步骤中，若检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度，若未检测到第二平台返回的支付成功结果，不作处理即可。
具体实施时，若检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度，在冻结失败的情况下，代表机构成员在第二平台的交易还未完成，此时不作处理即可。
可选的，所述支付成功结果，由所述第二平台在预设时间周期内返回，所述支付成功结果中携带所述剩余资源额度；所述预设时间周期在所述第一资源额度被冻结后进行配置，即第一平台在上述对第一平台的第一资源额度进行冻结之后配置预设时间周期。可选的，若在所述预设时间周期内检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度。
在此基础上，为了提升预设时间周期的有效性和合理性，避免影响机构成员下一次基于第二应用进行支付的过程，提升成员体验，本实施例提供的一种可选实施方式中，所述预设时间周期，通过如下方式计算获得：获取所述机构成员在所述第二平台的历史交易时长和/或交易偏好数据；根据所述历史交易时长和/或所述交易偏好数据计算所述预设时间周期；可选的，所述交易偏好数据包括交易门店类型和/或机构标识的展示时长。
具体的，根据交易偏好数据计算预设时间周期的过程，可通过若交易门店类型为第一类型，确定预设时间周期为第一时间周期；若交易门店类型为第二类型，确定预设时间周期为第二时间周期；比如第一类型为交易等待时长大于或者等于时长阈值的类型，第二类型为交易等待时长为小于时长阈值的类型。
实际应用中，为了提升对第一资源额度进行额度更新的更新精确度，提升额度更新的更新全面性，在上述第二平台接收到同步的第一资源额度后执行的操作的基础上，可在检测到第二平台返回的支付成功结果的基础上，从第二平台查询交易数据，可选的，所述跳转参数，包括向所述第二平台分配的交易标识，本实施例提供的一种可选实施方式中，若检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度执行之后，还执行如下操作：根据所述交易标识调用数据接口从所述第二平台查询所述交易数据。
其中，所述交易标识是指表征机构成员在第二平台基于机构标识进行的当前交易。
步骤S108，对所述第一资源额度进行解冻并进行额度更新处理。
上述在检测到第二平台返回的支付成功结果的情况下，通过接口调用冻结第二平台的剩余资源额度，本步骤中，对第一平台的第一资源额度进行解冻并进行额度更新处理。
实际应用中，一方面支付成功结果存在丢失的情况，另一方面支付成功结果中携带的第二平台的剩余资源额度也可存在丢失的情况，针对于此，为了提升额度更新处理的全面性和精确性，一方面可根据支付成功结果中携带的剩余资源额度对第一资源额度进行更新处理，另一方面可根据机构成员在第二平台的交易数据对第一资源额度进行更新 处理，以此，提升额度更新处理的灵活性，本实施例提供的一种可选实施方式中，所述额度更新处理，包括：根据所述机构成员在所述第二平台的交易数据计算交易资源数额；根据所述交易资源数额对所述第一资源额度进行更新处理；或者，根据所述支付成功结果中携带的所述剩余资源额度，对所述第一资源额度进行更新处理。
此外，为了进一步提升额度更新处理的精确性和全面性，可结合交易数据和剩余资源额度两个层面进行额度更新处理，具体的，所述额度更新处理，也可通过如下方式实现：若机构成员在第二平台的交易资源数额与支付成功结果中携带的剩余资源额度一致，基于所述剩余资源额度对第一平台的第一资源额度进行更新处理；若机构成员在第二平台的交易资源数额与支付成功结果中携带的剩余资源额度不一致，基于交易资源数额对第一平台的第一资源额度进行更新处理；可选的，所述交易资源额度基于所述机构成员在第二平台的交易数据计算获得。
实际应用中，机构成员可以在第二平台基于机构标识进行交易，也可以在第一平台进行在线交易，本实施例提供的一种可选实施方式中，在对第一资源额度进行解冻并进行额度更新处理执行之后，还执行如下操作：获取所述机构成员通过所述第一应用提交的交易订单；根据所述交易订单对更新处理获得的目标资源额度进行扣减。
在实际的应用过程中，在第一平台对第一资源额度进行解冻并进行额度更新处理之后，机构也可进行资源发放，需要说明的是，机构进行资源发放可在第一平台进行，本实施例提供的一种可选实施方式中，在对第一资源额度进行解冻并进行额度更新处理之后，还执行如下操作：根据所述机构成员所属机构提交的资源发放指令，检测更新处理获得的目标资源额度是否处于冻结状态；若否，基于所述资源发放指令携带的发放资源额度对目标资源额度进行额度更新，获得更新资源额度。
需要补充的是，机构成员可在第一平台实现持续性地在线交易，也可在第二平台基于机构标识实现持续性地线下交易。
下述以本实施例提供的一种资源额度处理方法在权益场景的应用为例，对本实施例提供的资源额度处理方法进行进一步说明，参见图2，应用于权益场景的资源额度处理方法，包括如下步骤。
步骤S202，根据机构成员基于支付请求在权益应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结。
步骤S204，向机构码平台同步第一资源额度，并通过接口调用对机构码平台的第二资源额度进行解冻。
步骤S214，若在预设时间周期内检测到机构码平台返回的支付成功结果，通过接口调用冻结机构码平台的剩余资源额度。
步骤S216，根据应用跳转的跳转参数调用数据接口从机构码平台查询交易数据。
步骤S218，根据查询到的交易数据计算交易资源数额，并根据交易资源数额对权益平台的第一资源额度进行更新处理。
上述提供的应用于权益场景的资源额度处理方法的实现过程，由第一平台执行，下述方法实施例提供的应用于权益场景的资源额度处理方法的实现过程，由第二平台执行，二者在执行过程中相互配合，因此，阅读上述实现过程请参照下述方法实施例的对应内容，相应的，阅读下述应用于权益场景的资源额度处理方法的实现过程请参照本方法实施例的对应内容。
本说明书提供的另一种资源额度处理方法实施例：本实施例提供的资源额度处理方法，可应用于第二平台，接收第一平台基于应用跳转的跳转指令同步的第一资源额度，以基于第一资源额度更新第二资源额度，在从第一应用跳转至第二应用后根据第一资源额度对机构成员基于机构标识提交的交易订单进行支付处理，并基于支付处理结果对第一资源额度进行额度更新处理，以此，实现对第一平台和第二平台的资源额度的同步处理，在机构成员在一个平台进行支付的过程中，冻结另一个平台的资源额度直至支付完 成，避免机构成员的超额支付，避免机构成员和机构的资源损失，对资源额度实现合理的把控。
参照图3，本实施例提供的资源额度处理方法，具体包括步骤S302至步骤S306。
需要说明的是，本实施例提供的资源额度处理方法的实现过程，可由第二平台执行，上述方法实施例提供的资源额度处理方法的实现过程，可由第一平台执行，二者在执行过程中相互配合，因此，阅读上述方法实施例提供的资源额度处理方法的实现过程请参照本方法实施例的对应内容，相应的，阅读本实施例提供的资源额度处理方法的实现过程请参照上述方法实施例的对应内容。
步骤S302，接收第一平台基于应用跳转的跳转指令同步的第一资源额度，以基于所述第一资源额度更新第二资源额度。
本实施例中，机构包括企业、事业单位、社会团体等各种形式的组织，此外，机构不仅包括本级组织，还包括机构的内部组织，比如企业部门或者分部。所述机构成员包括机构工作人员和/或机构相关人员。
第一应用，包括独立运行于机构成员的成员终端的应用程序，或者搭载于第三方应用程序内的子程序或者小程序。所述第一平台包括第一应用对应的平台，所述第一平台可以是针对机构的机构成员进行资源额度发放的平台。可选的，所述应用跳转，包括从所述第一应用跳转至第二应用；可选的，所述第一应用，包括运行于所述机构成员的成员终端的应用程序；所述第二应用，包括搭载于第三方应用内的子程序，所述第三方应用可独立运行于机构成员的成员终端。所述成员终端包括机构成员的终端设备；第二平台包括所述第二应用对应的平台。
需要说明的是，机构成员可以在第一平台和第二平台基于资源额度进行交易，即第一平台和第二平台为机构成员基于资源额度进行交易的交易平台，第一平台和第二平台可存在各自的资源额度。
具体实施时，第一平台根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结，并向第二平台同步所述第一资源额度，对所述第二平台的第二资源额度进行解冻，相应的，第二平台接收第一平台基于应用跳转的跳转指令同步的第一资源额度，以基于所述第一资源额度更新第二资源额度。可选的，所述第二资源额度在前一次基于机构标识进行支付处理后被冻结。
本实施例提供的一种可选实施方式中，所述第一平台在同步第一资源额度之前，还执行如下操作：根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结。
实际应用中，机构可以直接向第一平台发放资源额度，机构的机构成员可基于该资源额度进行交易，即机构的机构成员对应同一资源额度，机构也可以针对机构成员在第一平台发放资源额度，即机构的机构成员对应相同或者不同的资源额度；所述第一资源额度，包括第一权益资源额度，所述第一资源额度可以是机构成员的资源额度，也可以是机构的资源额度，比如第一资源额度是机构成员的福利资源额度，或者机构的福利资源额度，机构成员可以对机构的福利资源额度进行消费。
在实际的应用过程中，机构可向机构成员进行资源发放，在此过程中，为了能够顺利进行资源额度的额度更新，第一平台可检测第一平台的初始资源额度是否处于冻结状态，在初始资源额度未处于冻结状态的情况下，基于发放资源额度对初始资源额度进行额度更新，即在根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结执行之前，若根据机构成员所属机构提交的资源发放指令检测到的初始资源额度未处于冻结状态，基于所述资源发放指令携带的发放资源额度对所述初始资源额度进行额度更新，获得所述第一资源额度，本实施例提供的一种可选实施方式中，第一平台在根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结执行之前，还执行如下操作：根据所述机构成员所属机构 提交的资源发放指令，检测初始资源额度是否处于冻结状态；若否，基于所述资源发放指令携带的发放资源额度对所述初始资源额度进行额度更新，获得所述第一资源额度；若是，不作处理即可或者按照预设时间间隔重新检测初始资源额度是否处于冻结状态。
其中，所述初始资源额度是指第一平台的未基于发放资源额度进行额度更新之前的资源额度；所述发放资源额度是指向机构成员发放的资源额度。
具体的，根据机构成员所属机构提交的资源发放指令，检测第一平台的初始资源额度是否处于冻结状态，若否，基于资源发放指令携带的发放资源额度对第一平台的初始资源额度进行额度更新，获得所述第一资源额度。
实际应用中，机构成员一方面可以基于资源额度在第一平台进行交易，另一方面也可基于资源额度在第二平台进行交易，基于此，本实施例提供的一种可选实施方式中，第一平台在根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结执行之前，还执行如下操作：获取所述机构成员通过所述第一应用提交的交易订单；根据所述交易订单对初始资源额度进行扣减，获得所述第一资源额度。
具体的，第一平台根据机构成员通过第一应用提交的交易订单的订单数额，对第一平台的初始资源额度进行扣减，获得第一资源额度。
具体实施时，第一平台获取机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，并根据该跳转指令对第一平台的第一资源额度进行冻结，以避免机构成员同时在第一平台和第二平台基于资源额度进行支付，对多平台的资源额度进行有效管理，具体第一平台可获取机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对该跳转指令进行拦截处理，并对第一平台的第一资源额度进行冻结。在此之后，第一平台可配置预设时间周期。
上述第一平台根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结，在此之后，第一平台向第二平台同步第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度。
具体实施时，为了保持第一平台和第二平台的资源额度的实时同步，第一平台可向第二平台同步第一平台的第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新第二资源额度，可选的，所述第二资源额度在前一次基于机构标识进行支付处理后被冻结。具体的，第一平台向第二平台同步第一平台的第一资源额度，调用资源处理接口对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度。相应的，第二平台接收第一平台同步的第一资源额度，并基于第一资源额度更新第二资源额度，第一平台向第二平台同步第一平台的第一资源额度之后，机构成员的成员终端从第一应用跳转至第二应用。
步骤S304，调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理。
上述第一平台接收第一平台基于应用跳转的跳转指令同步的第一资源额度，以基于所述第一资源额度更新第二资源额度，本步骤中，调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理。
本实施例所述机构标识包括机构码，所述机构码是指机构为机构成员的支付等所设置的标识码，该机构码能够唯一标识机构，机构码的存在形式可以是二维码、条形码、声音码等标识码，该机构码可关联机构在第二平台的资源额度或者关联机构成员在第二平台的资源额度，机构成员可通过该机构码基于第二平台的资源额度实现支付。此外，所述机构码也可用于开票、报销等处理。可选的，所述交易订单在机构成员的成员终端展示的机构标识被扫描后提交。
步骤S306，基于支付处理结果对所述第一资源额度进行额度更新处理。
上述调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理，本步骤中，基于支付处理结果对第一资源额度进行额度更新处理。
具体实施时，根据支付处理获得的初始交易数额对第一资源额度进行扣减，获得所述剩余资源额度，在此之后，第二平台对所述剩余资源额度进行存储，即将第二平台的第一资源额度更新为剩余资源额度，并基于应用跳转的跳转参数对初始交易数据进行标记处理，获得交易数据，向第一平台返回支付成功结果。
本实施例提供的一种可选实施方式中，所述额度更新处理，包括：根据所述支付处理结果中的初始交易数据和所述第一资源额度计算剩余资源额度；将所述第一资源额度更新为所述剩余资源额度。
本实施例提供的一种可选实施方式中，在基于支付处理结果对所述第一资源额度进行额度更新处理执行之后，还执行如下操作：基于所述应用跳转的跳转参数对初始交易数据进行标记处理，获得交易数据。
可选的，所述跳转参数，包括向所述第二平台分配的交易标识；实际应用中，在从第一应用跳转至第二应用之前，第一平台可向第二平台分配交易标识，在第一应用跳转至第二应用的过程中通过跳转参数进行传递。
本实施例提供的一种可选实施方式中，在基于支付处理结果对所述第一资源额度进行额度更新处理执行之后，还执行如下操作：向所述第一平台返回支付成功结果，以通过接口调用冻结所述第二平台的剩余资源额度，对所述第一平台的第一资源额度进行解冻并进行额度更新处理。
实际应用中，第二平台返回的支付成功结果存在丢失的情况，针对于此，为了及时对第一平台和第二平台的资源额度进行同步，防止机构成员在多个平台出现超额支付的问题，本实施例提供的一种可选实施方式中，第一平台在向第二平台同步第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度执行之后，还执行如下操作：若在预设时间周期内未检测到所述支付成功结果，通过接口调用冻结所述剩余资源额度；在冻结失败的情况下，按照重试时间间隔重试冻结操作。
可选的，所述预设时间周期在所述第一资源额度被冻结后进行配置。
具体的，第一平台若在预设时间周期内未检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度，并在冻结失败的情况下，按照重试时间间隔冻结所述剩余资源额度，直至冻结成功后对第一资源额度进行解冻并进行额度更新处理。
上述第一平台向第二平台同步第一资源额度，并对第二平台的第二资源额度进行解冻，以在解冻后基于第一资源额度更新第二资源额度，在此之后，第一平台若检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度，若未检测到第二平台返回的支付成功结果，不作处理即可。
具体实施时，第一平台若检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度，在冻结失败的情况下，代表机构成员在第二平台的交易还未完成，此时不作处理即可。
可选的，所述支付成功结果，由所述第二平台在预设时间周期内返回，所述支付成功结果中携带所述剩余资源额度；所述预设时间周期在所述第一资源额度被冻结后进行配置，即第一平台在上述对第一平台的第一资源额度进行冻结之后配置预设时间周期。可选的，若在所述预设时间周期内检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度。
在此基础上，为了提升预设时间周期的有效性和合理性，避免影响机构成员下一次基于第二应用进行支付的过程，提升成员体验，本实施例提供的一种可选实施方式中，所述预设时间周期，通过如下方式计算获得：获取所述机构成员在所述第二平台的历史 交易时长和/或交易偏好数据；根据所述历史交易时长和/或所述交易偏好数据计算所述预设时间周期；可选的，所述交易偏好数据包括交易门店类型和/或机构标识的展示时长。
具体的，根据交易偏好数据计算预设时间周期的过程，可通过若交易门店类型为第一类型，确定预设时间周期为第一时间周期；若交易门店类型为第二类型，确定预设时间周期为第二时间周期；比如第一类型为交易等待时长大于或者等于时长阈值的类型，第二类型为交易等待时长为小于时长阈值的类型。
第一平台若检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度，在此之后，第一平台对所述第一资源额度进行解冻并进行额度更新处理。
实际应用中，为了提升对第一资源额度进行额度更新的更新精确度，提升额度更新的更新全面性，在上述第二平台接收到同步的第一资源额度后执行的操作的基础上，可在检测到第二平台返回的支付成功结果的基础上，从第二平台查询交易数据，可选的，所述跳转参数，包括向所述第二平台分配的交易标识，本实施例提供的一种可选实施方式中，第一平台若检测到第二平台返回的支付成功结果，通过接口调用冻结第二平台的剩余资源额度执行之后，还执行如下操作：根据所述交易标识调用数据接口从所述第二平台查询所述交易数据。
其中，所述交易标识是指表征机构成员在第二平台基于机构标识进行的当前交易。
实际应用中，一方面支付成功结果存在丢失的情况，另一方面支付成功结果中携带的第二平台的剩余资源额度也可存在丢失的情况，针对于此，为了提升额度更新处理的全面性和精确性，一方面第一平台可根据支付成功结果中携带的剩余资源额度对第一资源额度进行更新处理，另一方面第一平台可根据机构成员在第二平台的交易数据对第一资源额度进行更新处理，以此，提升额度更新处理的灵活性，本实施例提供的一种可选实施方式中，上述第一平台通过如下方式进行额度更新处理：根据所述机构成员在所述第二平台的交易数据计算交易资源数额；根据所述交易资源数额对所述第一资源额度进行更新处理；或者，根据所述支付成功结果中携带的所述剩余资源额度，对所述第一资源额度进行更新处理。
此外，为了进一步提升额度更新处理的精确性和全面性，第一平台可结合交易数据和剩余资源额度两个层面进行额度更新处理，具体的，第一平台通过如下方式进行额度更新处理：若机构成员在第二平台的交易资源数额与支付成功结果中携带的剩余资源额度一致，基于所述剩余资源额度对第一平台的第一资源额度进行更新处理；若机构成员在第二平台的交易资源数额与支付成功结果中携带的剩余资源额度不一致，基于交易资源数额对第一平台的第一资源额度进行更新处理；可选的，所述交易资源额度基于所述机构成员在第二平台的交易数据计算获得。
实际应用中，机构成员可以在第二平台基于机构标识进行交易，也可以在第一平台进行在线交易，本实施例提供的一种可选实施方式中，第一平台在对第一资源额度进行解冻并进行额度更新处理执行之后，还执行如下操作：获取所述机构成员通过所述第一应用提交的交易订单；根据所述交易订单对更新处理获得的目标资源额度进行扣减。
在实际的应用过程中，在第一平台对第一资源额度进行解冻并进行额度更新处理之后，机构也可进行资源发放，需要说明的是，机构进行资源发放可在第一平台进行，本实施例提供的一种可选实施方式中，第一平台在对第一资源额度进行解冻并进行额度更新处理之后，还执行如下操作：根据所述机构成员所属机构提交的资源发放指令，检测更新处理获得的目标资源额度是否处于冻结状态；若否，基于所述资源发放指令携带的发放资源额度对目标资源额度进行额度更新，获得更新资源额度。
下述以本实施例提供的一种资源额度处理方法在权益场景的应用为例，对本实施例提供的资源额度处理方法进行进一步说明，参见图2，应用于权益场景的资源额度处理方法，具体包括如下步骤。
步骤S206，接收权益平台基于应用跳转的跳转指令同步的第一资源额度，并基于 第一资源额度更新第二资源额度。
步骤S208，调用支付接口，在从权益应用跳转至机构码应用后根据第一资源额度对机构成员基于机构码提交的交易订单进行支付处理。
步骤S210，根据支付处理获得的初始交易数据和第一资源额度计算剩余资源额度，以及基于应用跳转的跳转参数对初始交易数据进行标记处理，获得交易数据。
步骤S212，向权益平台返回支付成功结果。
本说明书提供的一种资源额度处理装置实施例如下：在上述的实施例中，提供了一种应用于第一平台的资源额度处理方法，与之相对应的，还提供了一种运行于第一平台的资源额度处理装置，下面结合附图进行说明。
参照图4，其示出了本实施例提供的一种资源额度处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种资源额度处理装置，运行于第一平台，包括：第一资源额度冻结模块402，被配置为根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；资源额度同步模块404，被配置为向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度；剩余资源额度冻结模块406，被配置为若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度；第一额度更新模块408，被配置为对所述第一资源额度进行解冻并进行额度更新处理。
本说明书提供的另一种资源额度处理装置实施例如下：在上述的实施例中，提供了一种应用于第二平台的资源额度处理方法，与之相对应的，还提供了一种运行于第二平台的资源额度处理装置，下面结合附图进行说明。
参照图5，其示出了本实施例提供的一种资源额度处理装置示意图。
由于装置实施例对应于方法实施例，所以描述得比较简单，相关的部分请参见上述提供的方法实施例的对应说明即可。下述描述的装置实施例仅仅是示意性的。
本实施例提供一种资源额度处理装置，运行于第二平台，包括：资源额度接收模块502，被配置为接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结；支付处理模块504，被配置为调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理；第二额度更新模块506，被配置为基于支付处理结果对所述第一资源额度进行额度更新处理。
本说明书提供的一种资源额度处理设备实施例如下：对应上述描述的一种应用于第一平台的资源额度处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种资源额度处理设备，该资源额度处理设备用于执行上述提供的资源额度处理方法，图6为本说明书一个或多个实施例提供的一种资源额度处理设备的结构示意图。
本实施例提供的一种资源额度处理设备，包括：如图6所示，资源额度处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器601和存储器602，存储器602中可以存储有一个或一个以上存储应用程序或数据。其中，存储器602可以是短暂存储或持久存储。存储在存储器602的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括资源额度处理设备中的一系列计算机可执行指令。更进一步地，处理器601可以设置为与存储器602通信，在资源额度处理设备上执行存储器602中的一系列计算机可执行指令。资源额度处理设备还可以包括一个或一 个以上电源603，一个或一个以上有线或无线网络接口604，一个或一个以上输入/输出接口605，一个或一个以上键盘606等。
在一个具体的实施例中，资源额度处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对资源额度处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度；若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度；对所述第一资源额度进行解冻并进行额度更新处理。
本说明书提供的另一种资源额度处理设备实施例如下：对应上述描述的一种应用于第二平台的资源额度处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种资源额度处理设备，该资源额度处理设备用于执行上述提供的资源额度处理方法，图7为本说明书一个或多个实施例提供的一种资源额度处理设备的结构示意图。
本实施例提供的一种资源额度处理设备，包括：如图7所示，资源额度处理设备可因配置或性能不同而产生比较大的差异，可以包括一个或一个以上的处理器701和存储器702，存储器702中可以存储有一个或一个以上存储应用程序或数据。其中，存储器702可以是短暂存储或持久存储。存储在存储器702的应用程序可以包括一个或一个以上模块(图示未示出)，每个模块可以包括资源额度处理设备中的一系列计算机可执行指令。更进一步地，处理器701可以设置为与存储器702通信，在资源额度处理设备上执行存储器702中的一系列计算机可执行指令。资源额度处理设备还可以包括一个或一个以上电源703，一个或一个以上有线或无线网络接口704，一个或一个以上输入/输出接口705，一个或一个以上键盘706等。
在一个具体的实施例中，资源额度处理设备包括有存储器，以及一个或一个以上的程序，其中一个或者一个以上程序存储于存储器中，且一个或者一个以上程序可以包括一个或一个以上模块，且每个模块可以包括对资源额度处理设备中的一系列计算机可执行指令，且经配置以由一个或者一个以上处理器执行该一个或者一个以上程序包含用于进行以下计算机可执行指令：接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结；调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理；基于支付处理结果对所述第一资源额度进行额度更新处理。
本说明书提供的一种存储介质实施例如下：对应上述描述的一种应用于第一平台的资源额度处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度；若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度；对所述第一资源额度进行解冻并进行额度更新处理。
需要说明的是，本说明书中关于一种存储介质的实施例与本说明书中关于一种应用于第一平台的资源额度处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
本说明书提供的另一种存储介质实施例如下：对应上述描述的一种应用于第二平台的资源额度处理方法，基于相同的技术构思，本说明书一个或多个实施例还提供一种存储介质。
本实施例提供的存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结；调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理；基于支付处理结果对所述第一资源额度进行额度更新处理。
需要说明的是，本说明书中关于另一种存储介质的实施例与本说明书中关于一种应用于第二平台的资源额度处理方法的实施例基于同一发明构思，因此该实施例的具体实施可以参见前述对应方法的实施，重复之处不再赘述。
上述对本说明书特定实施例进行了描述。其它实施例在所附权利要求书的范围内。在一些情况下，在权利要求书中记载的动作或步骤可以按照不同于实施例中的顺序来执行并且仍然可以实现期望的结果。另外，在附图中描绘的过程不一定要求示出的特定顺序或者连续顺序才能实现期望的结果。在某些实施方式中，多任务处理和并行处理也是可以的或者可能是有利的。
在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 (21)

  1. 一种资源额度处理方法，应用于第一平台，包括：
    根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；
    向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度；
    若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度；
    对所述第一资源额度进行解冻并进行额度更新处理。
  2. 根据权利要求1所述的资源额度处理方法，其中，所述额度更新处理，包括：
    根据所述机构成员在所述第二平台的交易数据计算交易资源数额；
    根据所述交易资源数额对所述第一资源额度进行更新处理；
    或者，
    根据所述支付成功结果中携带的所述剩余资源额度，对所述第一资源额度进行更新处理。
  3. 根据权利要求1所述的资源额度处理方法，其中，所述应用跳转，包括从所述第一应用跳转至第二应用；
    其中，所述第一应用，包括运行于所述机构成员的成员终端的应用程序；所述第二应用，包括搭载于第三方应用内的子程序。
  4. 根据权利要求1所述的资源额度处理方法，其中，所述第二平台接收到同步的所述第一资源额度后，执行如下操作：
    调用支付接口，在所述应用跳转后按照所述第一资源额度对所述机构成员基于机构标识提交的交易订单进行支付处理；
    根据支付处理获得的初始交易数据和所述第一资源额度计算所述剩余资源额度，以及基于所述应用跳转的跳转参数对所述初始交易数据进行标记处理，获得交易数据。
  5. 根据权利要求4所述的资源额度处理方法，其中，所述跳转参数，包括向所述第二平台分配的交易标识；
    相应的，所述若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度步骤执行之后，且所述对所述第一资源额度进行解冻并进行额度更新处理步骤执行之前，还包括：
    根据所述交易标识调用数据接口从所述第二平台查询所述交易数据。
  6. 根据权利要求1所述的资源额度处理方法，其中，对所述第一资源额度进行解冻并进行额度更新处理步骤执行之后，还包括：
    获取所述机构成员通过所述第一应用提交的交易订单；
    根据所述交易订单对更新处理获得的目标资源额度进行扣减。
  7. 根据权利要求1所述的资源额度处理方法，其中，根据所述机构成员基于所述支付请求在所述第一应用提交的进行应用跳转的所述跳转指令，对所述第一资源额度进行冻结步骤执行之前，还包括：
    根据所述机构成员所属机构提交的资源发放指令，检测初始资源额度是否处于冻结状态；
    若否，基于所述资源发放指令携带的发放资源额度对所述初始资源额度进行额度更新，获得所述第一资源额度。
  8. 根据权利要求1所述的资源额度处理方法，其中，所述支付成功结果，由所述第二平台在预设时间周期内返回；
    所述预设时间周期在所述第一资源额度被冻结后进行配置。
  9. 根据权利要求8所述的资源额度处理方法，其中，所述预设时间周期，通过如 下方式计算获得：
    获取所述机构成员在所述第二平台的历史交易时长和/或交易偏好数据；
    根据所述历史交易时长和/或所述交易偏好数据计算所述预设时间周期；
    其中，所述交易偏好数据包括交易门店类型。
  10. 根据权利要求1所述的资源额度处理方法，还包括：
    若在预设时间周期内未检测到所述支付成功结果，通过接口调用冻结所述剩余资源额度；
    在冻结失败的情况下，按照重试时间间隔重试冻结操作。
  11. 一种资源额度处理方法，应用于第二平台，包括：
    接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结；
    调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理；
    基于支付处理结果对所述第一资源额度进行额度更新处理。
  12. 根据权利要求11所述的资源额度处理方法，其中，所述额度更新处理，包括：
    根据所述支付处理结果中的初始交易数据和所述第一资源额度计算剩余资源额度；
    将所述第一资源额度更新为所述剩余资源额度。
  13. 根据权利要求11所述的资源额度处理方法，其中，所述第一应用，包括运行于所述机构成员的成员终端的应用程序；
    所述第二应用，包括搭载于第三方应用内的子程序。
  14. 根据权利要求11所述的资源额度处理方法，其中，基于所述支付处理结果对所述第一资源额度进行额度更新处理步骤执行之后，还包括：
    基于所述应用跳转的跳转参数对初始交易数据进行标记处理，获得交易数据。
  15. 根据权利要求11所述的资源额度处理方法，其中，所述第一平台在同步所述第一资源额度之前，执行如下操作：
    根据所述机构成员基于支付请求在所述第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；
    相应的，所述基于支付处理结果对所述第一资源额度进行额度更新处理步骤执行之后，还包括：
    向所述第一平台返回支付成功结果，以通过接口调用冻结所述第二平台的剩余资源额度，对所述第一平台的第一资源额度进行解冻并进行额度更新处理。
  16. 一种资源额度处理装置，运行于第一平台，包括：
    第一资源额度冻结模块，被配置为根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；
    资源额度同步模块，被配置为向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度；
    剩余资源额度冻结模块，被配置为若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度；
    第一额度更新模块，被配置为对所述第一资源额度进行解冻并进行额度更新处理。
  17. 一种资源额度处理装置，运行于第二平台，包括：
    资源额度接收模块，被配置为接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结；
    支付处理模块，被配置为调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理；
    第二额度更新模块，被配置为基于支付处理结果对所述第一资源额度进行额度更新处理。
  18. 一种资源额度处理设备，包括：
    处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；
    向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度；
    若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度；
    对所述第一资源额度进行解冻并进行额度更新处理。
  19. 一种资源额度处理设备，包括：
    处理器；以及，被配置为存储计算机可执行指令的存储器，所述计算机可执行指令在被执行时使所述处理器：
    接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结；
    调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理；
    基于支付处理结果对所述第一资源额度进行额度更新处理。
  20. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：
    根据机构成员基于支付请求在第一应用提交的进行应用跳转的跳转指令，对第一资源额度进行冻结；
    向第二平台同步所述第一资源额度，并对所述第二平台的第二资源额度进行解冻，以在解冻后基于所述第一资源额度更新所述第二资源额度；
    若检测到所述第二平台返回的支付成功结果，通过接口调用冻结所述第二平台的剩余资源额度；
    对所述第一资源额度进行解冻并进行额度更新处理。
  21. 一种存储介质，用于存储计算机可执行指令，所述计算机可执行指令在被处理器执行时实现以下流程：
    接收第一平台基于应用跳转的跳转指令同步的第一资源额度，并基于所述第一资源额度更新第二资源额度；所述第二资源额度在前一次基于机构标识进行支付处理后被冻结；
    调用支付接口，在从第一应用跳转至第二应用后根据所述第一资源额度对机构成员基于所述机构标识提交的交易订单进行支付处理；
    基于支付处理结果对所述第一资源额度进行额度更新处理。
PCT/CN2023/138088 2023-01-11 2023-12-12 资源额度处理方法及装置 Ceased WO2024149010A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202310041674.5A CN116071073B (zh) 2023-01-11 2023-01-11 资源额度处理方法及装置
CN202310041674.5 2023-01-11

Publications (1)

Publication Number Publication Date
WO2024149010A1 true WO2024149010A1 (zh) 2024-07-18

Family

ID=86178125

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/138088 Ceased WO2024149010A1 (zh) 2023-01-11 2023-12-12 资源额度处理方法及装置

Country Status (2)

Country Link
CN (1) CN116071073B (zh)
WO (1) WO2024149010A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116071073B (zh) * 2023-01-11 2024-09-03 支付宝(杭州)信息技术有限公司 资源额度处理方法及装置

Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101226617A (zh) * 2007-01-19 2008-07-23 阿里巴巴公司 一种基于多平台数据交互处理的方法和系统
CN104408614A (zh) * 2014-11-25 2015-03-11 苏州米谷网络科技有限公司 网络游戏虚拟物品交易系统及方法
CN112862430A (zh) * 2021-01-19 2021-05-28 浙江网商银行股份有限公司 资源发放处理方法及装置
CN112967046A (zh) * 2021-03-01 2021-06-15 支付宝(杭州)信息技术有限公司 关联支付处理方法及装置
CN113554426A (zh) * 2020-04-23 2021-10-26 河北雄安链点科技有限公司 一种多数字资产交换平台
CN113807834A (zh) * 2021-09-17 2021-12-17 支付宝(杭州)信息技术有限公司 资源处理方法及装置
CN114493577A (zh) * 2022-01-27 2022-05-13 支付宝(杭州)信息技术有限公司 一种支付订单处理方法、装置、设备及系统
CN116071073A (zh) * 2023-01-11 2023-05-05 支付宝(杭州)信息技术有限公司 资源额度处理方法及装置

Patent Citations (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101226617A (zh) * 2007-01-19 2008-07-23 阿里巴巴公司 一种基于多平台数据交互处理的方法和系统
CN104408614A (zh) * 2014-11-25 2015-03-11 苏州米谷网络科技有限公司 网络游戏虚拟物品交易系统及方法
CN113554426A (zh) * 2020-04-23 2021-10-26 河北雄安链点科技有限公司 一种多数字资产交换平台
CN112862430A (zh) * 2021-01-19 2021-05-28 浙江网商银行股份有限公司 资源发放处理方法及装置
CN112967046A (zh) * 2021-03-01 2021-06-15 支付宝(杭州)信息技术有限公司 关联支付处理方法及装置
CN113807834A (zh) * 2021-09-17 2021-12-17 支付宝(杭州)信息技术有限公司 资源处理方法及装置
CN114493577A (zh) * 2022-01-27 2022-05-13 支付宝(杭州)信息技术有限公司 一种支付订单处理方法、装置、设备及系统
CN116071073A (zh) * 2023-01-11 2023-05-05 支付宝(杭州)信息技术有限公司 资源额度处理方法及装置

Also Published As

Publication number Publication date
CN116071073B (zh) 2024-09-03
CN116071073A (zh) 2023-05-05

Similar Documents

Publication Publication Date Title
KR102340223B1 (ko) 블록체인 합의 방법 및 디바이스
JP6804668B2 (ja) ブロックデータ検証方法および装置
TWI722256B (zh) 業務處理方法及裝置
CN111899008B (zh) 资源转移方法、装置、设备及系统
KR20190088535A (ko) 블록체인 기반 데이터 처리 방법 및 장치
CN107038042A (zh) 一种业务执行的方法及装置
CN110503435A (zh) 基于区块链的交易预警方法、装置及设备
CN110428304B (zh) 一种订单结算系统、方法及装置
CN108830705B (zh) 一种交易数据的汇总方法、装置及设备
TW201915867A (zh) 虛擬卡的開卡方法、系統和支付系統、發卡系統
WO2019179235A1 (zh) 一种数据缓存方法、装置及系统
CN110992038A (zh) 交易处理方法、装置及设备
US20240394345A1 (en) Data interaction processing
US20240232932A1 (en) Stake sharing processing method and apparatus
TW202008267A (zh) 記帳方法、裝置及業務財務一體化系統
US20250117770A1 (en) Credit-based transaction processing method and apparatus
WO2021239087A1 (zh) 一种数据处理方法、装置、设备及介质
WO2024149010A1 (zh) 资源额度处理方法及装置
CN112258295A (zh) 记录处理方法、装置及设备
CN110782253B (zh) 基于区块链的交易处理方法、装置及设备
WO2026082163A1 (zh) 交易提醒处理
CN106980920A (zh) 一种互联网业务的执行方法及装置
HK40088814B (zh) 资源额度处理方法及装置
HK40088814A (zh) 资源额度处理方法及装置
CN113377796B (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: 23915765

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 23915765

Country of ref document: EP

Kind code of ref document: A1

122 Ep: pct application non-entry in european phase

Ref document number: 23915765

Country of ref document: EP

Kind code of ref document: A1