Resource Transfer Method and Device in Batches

Abstract

The embodiments of this specification provide a method and device for batch resource transfer, which are used in the resource transfer process where the resource transferor holds the first resource, the receiving target of the resource recipient is the second resource, and the first resource of the resource transferor cannot transfer the resource at one time. During the resource transfer process, the client corresponding to the resource transferor sends a resource transfer request to the conversion server. The conversion server feeds back the transfer share and the service identifier to the client. According to the fed-back transfer share and the service identifier, the client performs the first share transfer of the first resource via the associated transfer platform. The associated transfer platform can transfer the transfer record of the first resource to the conversion server according to the service identifier. The conversion server dynamically updates the share to be transferred until the updated share to be transferred does not exceed the predetermined threshold. The conversion server can convert the transferred first resource into the second resource according to the predetermined conversion conditions. In this way, an effective resource batch transfer scheme can be provided.

Description

Technical Field

[0001] One or more embodiments of this specification relate to the field of computer technology, and in particular, to a method and apparatus for batch-wise online resource transfer. Background Art

[0002] Resource transfer is a very common life phenomenon in people's daily lives. For example, if user or institution A borrows money from user or institution B, then the "money" as a resource is transferred from B to A. Here, the resource can be a physical resource, a virtual resource on the network, or an identifier with the same value as the physical resource in a network platform, such as bank card balance, network data traffic, the amount of data contained in a data table, and so on.

[0003] During the resource transfer process, there are often situations that need to be carried out in batches. For example, the bank card balance is insufficient and multiple bank cards are required for separate payments. Another example is that the network data traffic has a daily limit, which is equivalent to transferring a certain amount of network data traffic in batches every day. The amount of data contained in the data table is too large and needs to be transmitted in packets, and so on. Therefore, an effective and feasible resource transfer solution is needed to complete the batch transfer of resources. Summary of the Invention

[0004] One or more embodiments of this specification describe a method and apparatus for batch-wise resource transfer to solve one or more problems mentioned in the background art.

[0005] According to a first aspect, there is provided a method for batch resource transfer, which is applicable to a resource transfer system. The resource transfer system includes a client, a conversion server, and an associated transfer platform. The resource transfer system converts, through the conversion server, a first resource transferred out by a resource transferor through the client from the associated transfer platform into a second resource that is the receiving target of the resource recipient. The first resource and the second resource are resources in different forms. The method is applicable to the conversion server and includes: receiving a resource transfer request submitted by the client, where the resource transfer request corresponds to a resource share described by the first resource or the second resource; determining, based on the resource share described by the first resource or the second resource, the share of the first resource to be transferred, and determining a service identifier for the resource transfer request; feeding back the share to be transferred and the service identifier to the client, so that the client provides, according to the share to be transferred, a first share of the first resource to the conversion server through the associated transfer platform, and then the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server; receiving the transfer record, updating the share to be transferred according to the service identifier and the first share, and feeding back the updated share to be transferred to the client, so that the client sends a new resource transfer request to the associated transfer platform again until the updated share to be transferred does not exceed a predetermined share; and when it is detected that a predetermined conversion condition is satisfied, converting the total share of the transferred first resource into the second resource according to each transfer record corresponding to the service identifier to complete the resource transfer operation for the resource transfer request.

[0006] In one embodiment, the share to be transferred also corresponds to a transfer time limit, and the transfer time limit can indicate the start time and / or end time for the client to provide the first resource.

[0007] In one embodiment, the first share is determined through at least one round of resource transfer interaction operations between the client and the associated transfer platform and by the client confirming the end of the current batch of resource transfer.

[0008] In one embodiment, when the resource transfer request includes a resource share described by the second resource, determining the share of the first resource to be transferred based on the resource share described by the first resource or the second resource includes: obtaining a conversion rule between the first resource and the second resource; and determining the share of the first resource to be transferred based on the resource share described by the second resource and the conversion rule.

[0009] In one embodiment, receiving the transfer record and updating the share to be transferred according to the service identifier and the first share includes: detecting the timeliness of the conversion rule at the current moment; in the case that the timeliness of the conversion rule is not satisfied at the current moment, obtaining the current conversion rule between the first resource and the second resource; combining the current conversion rule to re-determine the total share to be transferred of the first resource; and updating the share to be transferred according to the difference between the total share to be transferred and the first share.

[0010] In one embodiment, the predetermined conversion condition is one of the following: the updated share to be transferred does not exceed the predetermined share; an early conversion request sent by the client is received; a batch conversion request submitted by the client is received.

[0011] According to a second aspect, there is provided a method for batch resource transfer, which is applicable to a resource transfer system. The resource transfer system includes a client, a conversion server, and an associated transfer platform. The resource transfer system converts, through the conversion server, a first resource transferred out by a resource transferor through the client from the associated transfer platform into a second resource that is the receiving target of the resource recipient. The first resource and the second resource are resources in different forms. The method is applicable to the client and includes: sending a resource transfer request to the conversion server, where the resource transfer request corresponds to a resource share described by the first resource or the second resource, so that the conversion server determines the share to be transferred of the first resource based on the resource share described by the first resource or the second resource, and determines a service identifier for the resource transfer request; receiving from the conversion server the share to be transferred of the first resource and the service identifier; according to the share to be transferred, providing, through the associated transfer platform, a first share of the first resource to the conversion server, so that the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server, for the conversion server to receive the transfer record, update the share to be transferred according to the service identifier and the first share, and in the case that the updated share to be transferred exceeds the predetermined share, feedback the updated share to be transferred to the client; and in the case of receiving the updated share to be transferred feedback by the conversion server, continue to provide the first resource to the conversion server via the associated transfer platform.

[0012] In one embodiment, the share to be transferred also corresponds to a transfer time limit, and the transfer time limit can indicate the start time and / or end time for the client to provide the first resource.

[0013] In one embodiment, the providing, by the associated transfer platform to the conversion server, of the first share of the first resource according to the share to be transferred includes: after at least one round of resource transfer interaction operations with the associated transfer platform, confirming the end of the current batch of resource transfer, so that the associated transfer platform determines the first share transferred by the at least one round of resource transfer interaction operations.

[0014] In one embodiment, after the providing, by the associated transfer platform to the conversion server, of the first share of the first resource according to the share to be transferred, the method further includes: sending a batch conversion request for the first share of the first resource to the conversion server, so that the server converts the first resource of the first share into a second resource according to the batch conversion request.

[0015] In one embodiment, the method further includes: sending an early conversion request to the conversion server, so that the server converts the first resource in a plurality of transfer records corresponding to the service identifier into a second resource according to the early conversion request.

[0016] According to a third aspect, there is provided a resource transfer device in batches, applicable to a resource transfer system. The resource transfer system converts, via the conversion server, the first resource transferred out by a client into a second resource that is the receiving target of a resource recipient. The first resource and the second resource are resources in different forms. The device is disposed in the conversion server and includes:

[0017] A communication unit configured to receive a resource transfer request submitted by a client, where the resource transfer request corresponds to a resource share described by a first resource or a second resource;

[0018] A determination unit configured to determine, based on the resource share described by the first resource or the second resource, the share of the first resource to be transferred and determine a service identifier for the resource transfer request;

[0019] The communication unit is further configured to feedback the share to be transferred and the service identifier to the client, so that the client provides, according to the share to be transferred, the first share of the first resource to the conversion server through the associated transfer platform, and thus the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server;

[0020] An update unit configured to receive the transfer record, update the share to be transferred according to the service identifier and the first share, and feedback the updated share to be transferred to the client, so that the client sends a new resource transfer request to the associated transfer platform again until the updated share to be transferred does not exceed a predetermined share;

[0021] A conversion unit, configured to, when it is detected that a predetermined conversion condition is satisfied, convert the total share of the first resource that has been transferred into the second share of the target resource according to each transfer record corresponding to the service identifier, so as to complete the resource transfer operation for the resource transfer request.

[0022] According to a fourth aspect, there is provided a resource transfer device in batches, applicable to a resource transfer system. The resource transfer system includes a client, a conversion server, and an associated transfer platform. The resource transfer system converts, through the conversion server, the first resource transferred out by the client as the resource transferor into the second resource as the target received by the resource recipient. The first resource and the second resource are resources in different forms. The device is disposed in the client and includes:

[0023] A communication unit, configured to send a resource transfer request to the conversion server. The resource transfer request corresponds to a resource share described by the first resource or the second resource, so that the conversion server determines the share of the first resource to be transferred based on the resource share described by the first resource or the second resource, and determines a service identifier for the resource transfer request; and

[0024] Receive the share of the first resource to be transferred and the service identifier from the conversion server;

[0025] A transfer unit, configured to provide, according to the share to be transferred, a first share of the first resource to the conversion server through the associated transfer platform, so that the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server, for the conversion server to receive the transfer record, update the share to be transferred according to the service identifier and the first share, and feedback the updated share to be transferred to the client when the updated share to be transferred exceeds a predetermined share;

[0026] When the communication unit receives the updated share to be transferred fed back by the conversion server, the transfer unit is further configured to continue to provide the first resource to the conversion server via the associated transfer platform.

[0027] According to a fifth aspect, there is provided a computer-readable storage medium, on which a computer program is stored. When the computer program is executed on a computer, the computer is made to execute the method according to the first aspect or the second aspect.

[0028] According to a sixth aspect, there is provided a computing device, including a memory and a processor. The memory stores executable code, and when the processor executes the executable code, the method according to the first aspect or the second aspect is implemented.

[0029] The methods and devices provided in the embodiments of this specification are applicable to a resource transfer system. Here, the resource transfer system includes a client, a conversion server, and an associated transfer platform. Among them, the resource transfer system, through the conversion server, converts the first resource transferred out by the resource transferor from the client through the associated transfer platform into the second resource that is the target received by the resource recipient. It is particularly applicable to the situation where the resource transferor cannot transfer out sufficient shares at one time, such as the limit of the share transferred out each time, and the first resource shares held are not in one resource entity, etc.

[0030] Under the method or device architecture provided in this specification, the client sends a resource transfer request to the conversion server. The conversion server feeds back the transfer share and business identifier of the first resource to the client. The client performs resource transfer via the associated transfer platform according to the feedback transfer share and business identifier. After completing the resource transfer of the first share, the associated transfer platform transmits the transfer record of the resource transfer to the conversion server. The conversion server dynamically updates the share to be transferred and feeds it back to the client until the updated share to be transferred does not exceed a predetermined threshold. The conversion server can convert the first resource in the relevant transfer records transmitted by the associated transfer platform into the second resource according to the predetermined conversion conditions and the business identifier. This solution can provide an effective resource transfer method for resource transfer in the case of resource transfer share limitations. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the following drawings are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0032] Figure 1 Show a schematic diagram of a specific implementation architecture under the technical concept of this specification;

[0033] Figure 2 Show a timing diagram of the interaction among all parties of the batch-by-batch resource transfer according to an embodiment;

[0034] Figure 3 Show a flowchart of the batch-by-batch resource transfer method of the conversion server according to an embodiment;

[0035] Figure 4 Show a schematic block diagram of the batch-by-batch resource transfer device of the client according to an embodiment;

[0036] Figure 5 Show a schematic block diagram of the batch-by-batch resource transfer device provided in the conversion server according to an embodiment;

[0037] Figure 6 Schematic block diagram of a batch-based resource transfer device provided at a client according to an embodiment is shown. Detailed implementation

[0038] The solution provided in this specification will be described below in conjunction with the accompanying drawings.

[0039] First, an explanation will be given in conjunction with Figure 1 a specific implementation scenario shown. As Figure 1 shown, in the implementation framework of this specification, it may include a client, a conversion server, an associated transfer platform, etc. The conversion server can convert resources in a first form (hereinafter referred to as the first resource, such as US dollars, Bitcoin, etc.) into resources in a second form (hereinafter referred to as the second resource, such as RMB, etc.).

[0040] A specific business scenario may be that the current business party transfers resources to the opposite business party via the client through the conversion server. Among them, the current business party (resource transferor) holds the first resource, and the opposite business party (resource recipient) receives the target as the second resource. The associated transfer platform is used to provide resource shares for the client to the conversion server. It may be a part of the conversion server or a third-party transfer platform, which is not limited herein.

[0041] The specific resource form may be determined according to the specific business scenario. For example, it may be network data traffic, funds, data, etc. Here, the opposite business party may be the business party opposite to the client. For example, when the client is a consumer client, the opposite business party may be the business party providing products or services, such as a merchant. It can be understood that if the client is the client corresponding to the merchant, the opposite business party may also be the consumer.

[0042] Suppose Figure 1 in the implementation scenario shown, the client needs to transfer a certain share of the target resources, such as document data, funds, virtual assets, etc., to the opposite business party. The first resource provided by the client can also be called the transfer resource, and the second resource required by the opposite business party can be called the target resource. When both the transfer resource and the target resource are funds, for example, the first resource is RMB, and the second resource is US dollars or Bitcoin, etc. In a specific business scenario, the share of the first resource transferred out and the target share of the second resource may be equal or unequal. For example, in addition to providing the target share of the second resource, the first resource also needs to provide an additional share for the labor payment of the conversion server, such as handling fees and usage fees during the fund transfer process. Another example is in data transfer. In addition to the share of the effective data transmitted, it may also include the share occupied by the file header in a fixed format, etc.

[0043] When the client provides transfer resources, it can send a resource transfer request to the conversion server. This resource transfer request can correspond to the resource forms of the first resource and the second resource, and include the resource share described by the first resource or the second resource. For example, in the resource transfer request, the second resource corresponds to RMB and the first resource corresponds to US dollars. That is, the first resource transferred by the current business party through the client is in the form of US dollars, and the second resource received by the business party is in the form of RMB. The resource transfer request can also include the resource share described by US dollars or RMB, such as a resource share of 60,000 yuan described in RMB form.

[0044] The conversion server can determine the share of the first resource to be transferred that the client needs to provide according to the resource transfer request. For example, if the exchange rate between RMB and US dollars is 1:6, the share of the transferable resources can be 10,000 US dollars. At this time, the target share of the second resource is equal to the transfer share of the first resource. In the case where the conversion server needs to deduct a 1% handling fee, the transferable share can also be 10,100 US dollars. The transferable share provided by the conversion server can carry a service identifier corresponding to the resource transfer request, and this service identifier can be retained throughout the resource transfer process to indicate the resource transfer operation for this resource transfer request.

[0045] After that, the client can provide transfer resources through the associated transfer platform and generate a transfer record corresponding to the above service identifier. The associated transfer platform can provide this transfer record to the conversion server. The conversion server can dynamically adjust the transferable share according to the transfer record and other relevant information and send it to the client. Here, the transfer record can include the resource share transferred in the current round. Other relevant information can be determined according to the actual situation. For example, in the scenario of fund transfer, other relevant information can be relevant information such as exchange rate and handling fee rate. Repeat the above process until the transferable resource share does not exceed a predetermined threshold, such as 0. At this time, the conversion server can perform the conversion according to the corresponding relationship between the target resource and the transfer resource, thereby completing the resource transfer.

[0046] In this implementation scenario, the conversion server can generate an association between the resource transfer request and the transfer record of the associated transfer platform through the service identifier, so as to support the resource transfer process in which the client provides resource shares in batches. In addition, the conversion server can dynamically update the transferable share according to the actual situation to improve the effectiveness of the resource transfer process.

[0047] The technical concept of this specification will be described in detail below.

[0048] Figure 2 The timing diagram of the resource transfer process in batches according to an embodiment of this specification is shown. Figure 2In it, the resource transfer process in batches is completed through a resource transfer system, which may include a client, a conversion server, and an associated transfer platform. The resources here can be any resources that can be divided online and collected by a computer, such as transmitted data, network data traffic, funds, etc. The conversion server and the associated transfer platform can be implemented by a computer, device, or server with certain data transmission capabilities respectively. As an example, in the case where the transferred resource is data, for example, in the scenario where the resource transferor sends data to other devices (resource recipients) through a rate-limiting gateway (associated transfer platform) and a local area network server (conversion server) via the client. In the case where the transferred resource is funds, for example, it is the scenario where a consumer (resource transferor) pays a merchant (resource recipient) through a consumption client of a shopping platform via a payment platform (associated transfer platform) and a shopping platform server (conversion server). Another example is the scenario where a user makes a cross-border remittance payment to an overseas user (such as an overseas school, etc., resource recipient) through a cross-border remittance client via a payment platform (associated transfer platform) and a remittance server (conversion server), and so on. The associated transfer platform can be a platform associated with the conversion server, which can be a part of the conversion server or an independent third-party platform, etc., and is not limited here.

[0049] As Figure 2 shown, first, in step 201, the client submits a resource transfer request to the conversion server. Among them, the resource transfer request may correspond to a resource share described by a first resource or a second resource. Here, the first resource may correspond to the resource form provided by the client to the associated transfer platform, such as document data, and the second resource may correspond to the target resource form of the resource recipient, such as a compressed data packet.

[0050] When the resource transferor has a resource transfer requirement, it can send a resource transfer request to the conversion server via the client. For example, in the aforementioned example, the cross-border remittance client submits a cross-border transfer request (resource transfer request) to the remittance server. In this scenario, the first resource corresponding to the resource transfer request may be, for example, US dollars, and the second resource may be, for example, RMB. The resource transfer request may include the resource share described by the first resource, such as 10,000 US dollars, or the resource share described by the second resource, such as 60,000 RMB, and so on.

[0051] Then, in step 202, the conversion server feeds back the share of the first resource to be transferred and the service identifier to the client. Here, the conversion server can determine the share of the first resource to be transferred according to the resource transfer request and determine a service identifier for the resource transfer request. The service identifier may be a mark that uniquely identifies the resource transfer request, which may include at least one of numbers, letters, and symbols. For example, the service identifier may be a serial number determined for a remittance request, etc.

[0052] The conversion server can determine the share of the first resource to be transferred according to the resource share described by the first resource or the second resource included in the resource transfer request. When the resource share of the first resource is included in the resource transfer request, the share of the first resource to be transferred can be the resource share in the resource transfer request or the resource share determined according to the associated factors. For example, the associated factors for the share to be transferred in a remittance request can be handling fees, etc., and the associated factors for the share to be transferred in a data transmission request can be the size of the transmission protocol and other contents added on the basis of the effective data in the transmission data packet. When the resource share of the second resource is included in the resource transfer request, the associated factors for the share of the first resource to be transferred can also include the conversion rule between the second resource and the first resource on the basis of the foregoing factors. This conversion rule can be variable or fixed. For example, the conversion rule in cross-border remittance can be the exchange rate between RMB and US dollars, and this exchange rate can be updated daily. At this time, it can also be said that the conversion rule has timeliness, such as the exchange rate between US dollars and RMB is only valid on the same day.

[0053] In a possible implementation manner, before step 202, the conversion server can also perform a legality verification on the resource transfer request. This legality verification can be determined according to the specific business scenario. For example, when the first resource is document data, the legality verification can be the verification of at least one piece of information such as the identity and / or permission information of the client user, the document confidentiality level, etc. When the first resource is funds, the legality verification can be the verification of at least one of the identity of the client user, whether the account ID is correct and legal, whether the user ID appears in the anti-money laundering blacklist, whether the submitted remittance purpose note includes illegal remittance sensitive words, etc. After the legality verification is passed, the operation of step 202 is performed.

[0054] In an embodiment, when the conversion server feeds back the share to be transferred and the service identifier to the client, there can be corresponding time limit information, and this time limit information can indicate the start time and / or end time for the client to provide the transferred resources. For example, this time limit information can indicate that the start time of this remittance is the current time, and the end time is 24:00 the next day, or 24:00 on the same day or other times. Optionally, for the case of indicating the end time of this remittance, it can be understood that transferring any share of resources before the end time is regarded as meeting the time limit requirements of this remittance.

[0055] In step 203, the client provides the first share of the first resource to the conversion server through the associated transfer platform according to the share to be transferred. Generally, as a medium for resource transfer, the conversion server may not have the transfer function. When the client transfers resources to it, it can be carried out through a resource transfer medium, that is, the associated transfer platform. Especially when the transferred resource is funds, etc., in order to protect the interests of both parties as the resource transferor and recipient, the fund transfer is usually completed through a third-party platform. For example, when a user purchases goods from a merchant on a shopping platform, the fund transfer is usually carried out through a third-party payment platform (associated transfer platform), such as the transfer platforms provided by UnionPay, WeChat, Alipay, etc.

[0056] If the client encounters resource share restrictions through the associated transfer platform, such as insufficient bank card balance, exceeding the single transaction limit or daily limit, etc., the payment (resource transfer) may not be completed. Under the technical architecture of this specification, the idea of batch resource transfer is provided, which allows the client to perform multiple resource transfers for a single resource transfer request.

[0057] In this step, the client can provide the first share of the first resource to the conversion server through the associated transfer platform. Here, the first share can be less than or equal to the share to be transferred. The first share can be determined by the client according to the share information of the resource transfer subject. For example, if the resource transfer subject is a bank card, its share information can include the daily limit, single transaction limit, current balance, etc. Generally, the first share does not exceed the minimum of the daily limit, single transaction limit, current balance, etc. Optionally, the client can correspond to multiple resource transfer subjects, and the current resource transfer subject can be any one selected from them.

[0058] According to a possible design, when the client transfers the first resource of the first share through the associated transfer platform in a certain batch, it can also interact with the associated transfer platform multiple times. For example, when the first resource is funds, the client can determine the resource share transferred in a batch according to the single transaction limit or the balance of the current resource subject (such as a bank card). For example, when the daily limit is reached, confirm the end of the resource transfer in the current batch. The first share can be the total share of the first resource transferred in the current batch. Optionally, the client can also select the resource transfer time for the next batch, such as continuing the resource transfer the next day, etc.

[0059] In the case where the conversion server also provides time limit information, the client can also complete the resource transfer of the first share within the indicated time limit. For example, if the time limit information indicates the start time of the resource transfer, the client can perform the resource transfer of the first share after the start time. If the time limit information indicates the end time of the resource transfer, the client performs the resource transfer of the first share after the start time.

[0060] It can be understood that when the client performs a resource transfer operation through the associated transfer platform, it can pass the service identifier obtained from the conversion server to the associated transfer platform to ensure that the client's resource transfer operation is targeted at the above-mentioned resource transfer request.

[0061] Then, in step 204, the associated transfer platform sends a transfer record corresponding to the service identifier and the first share transferred to the conversion server. It can be understood that in addition to implementing resource transfer, the associated transfer platform can also record resource transfer events to generate a transfer record.

[0062] The transfer record can at least include a service identifier and a transferred share. In an alternative embodiment, the transfer record may further include one or more of a resource transferor, a resource recipient, a resource entity, etc. Among them: the service identifier can indicate the resource transfer request being targeted; the transferred share is, for example, the above-mentioned first share; the resource entity is, for example, a bank card used by a client user.

[0063] After the resource transfer operation of the first share is completed, the associated transfer platform can send a transfer record corresponding to the service identifier and the first share transferred to the conversion server. In an alternative embodiment, the associated transfer platform is a third-party platform different from the conversion server, and the service identifier may further include the identity information of the conversion server, such as the platform domain name, APP name, platform ID, etc. of a certain shopping platform, so that the associated transfer platform can send the transfer record to the corresponding conversion server according to this identity information.

[0064] Step 205, the conversion server receives the transfer record and updates the share to be transferred according to the service identifier and the first share. It can be understood that the conversion server can determine the resource transfer request targeted by the current transfer record according to the service identifier, and can determine the completed resource transfer share according to the first share, so as to update the share to be transferred for the corresponding resource transfer request.

[0065] In one embodiment, the conversion server can update the share to be transferred to the difference between the current share to be transferred and the first share.

[0066] In one embodiment, if the conversion rule between the first resource and the second resource changes dynamically, the conversion server can re-determine the share to be transferred according to the timeliness of the conversion rule and the first share that has been transferred. For example, in the scenario of cross-border remittance, step 201 involves a resource share of 60,000 yuan described by the second resource. The conversion rule "RMB to US dollar exchange rate" used in step 202 is 6:1, and the share to be transferred determined at that time in step 202 is 10,000 US dollars. A transfer record of 2,000 US dollars for the first share is generated the next day. When the conversion server receives this transfer record, it can first query the timeliness of the conversion rule "RMB to US dollar exchange rate". Assuming it has been updated to 5:1 currently, the conversion server can recalculate the share to be transferred of the first resource. For example, after recalculation, the total share to be transferred is 12,000 US dollars, and a resource transfer of 2,000 US dollars for the first share has been generated currently. Therefore, the updated share to be transferred is still 10,000 US dollars.

[0067] In a possible design, the resource transferor can also send an advance conversion request or a batch conversion request to the conversion server through the client, for converting the corresponding share of the first resource to be transferred into the second resource in advance or in real time. In this way, when the conversion server updates the share to be transferred, it can also do so according to the second resource after the conversion is implemented. For example, in the above example, if the resource transferor provides 2,000 US dollars to the resource conversion server on the same day, it will be converted into 12,000 yuan of the second resource in real time. When the exchange rate becomes 5:1 the next day, the remaining share of the second resource is 48,000 yuan, then the share to be transferred of the first resource in US dollars can be determined as 9,600 US dollars. That is, the updated share to be transferred by the conversion server is 9,600 US dollars.

[0068] Generally, in the case where the updated share to be transferred exceeds the predetermined threshold (such as 0) and the resource transfer is not completed, steps 202 to 205 are repeated, that is, the conversion server feeds back the updated share to be transferred to the client, and the client sends a transfer request to the associated transfer platform again...

[0069] For the conversion server, the conditions for performing the resource conversion operation described above can be referred to as predetermined conversion conditions. The predetermined conversion conditions can be, for example, receiving an advance conversion request sent by the client, or receiving a batch conversion request sent by the client, or the updated share to be transferred not exceeding a predetermined share (such as 0 yuan, 1 megabyte of data, etc.). When it is detected that the predetermined conversion condition is met, through step 206, the conversion server converts the transferred first resource into the second resource according to each transfer record corresponding to the service identifier, so as to complete the resource transfer operation for the above-mentioned resource transfer request.

[0070] In one embodiment, the transferred resource may be funds, or virtual currency. The conversion server queries and obtains the transfer records corresponding to each of the above business identifiers, and merges the transferred resource shares involved therein. For example, it is merged into the first resource of 12,000 US dollars. Then, according to the current exchange rate (US dollar: RMB = 1:5), it is exchanged into the second resource of 60,000 RMB. After the conversion server converts to the second resource, it can perform the next part of the resource transfer operation according to the resource recipient involved in the resource transfer request. For example, transfer the converted second resource to the resource recipient's corresponding bank card, financial platform ID and other resource entities.

[0071] In another embodiment, the transferred resource is document data. For example, the conversion server queries and obtains the transfer records corresponding to each of the above business identifiers, and merges the document data involved therein into a data set. The conversion server can also convert the merged first resource into the second resource, such as a compressed data packet, and send the compressed data packet to the indicated resource recipient according to the resource transfer request.

[0072] In other embodiments, according to different business scenarios, the transferred resources are different, and the conversion server can also perform various conversion operations, which will not be elaborated here.

[0073] To make the technical solutions described in this specification more clear, as a specific example, a technical solution applying the technical concept of this specification is given in the case of a cross-border payment scenario where the e-wallet has a single-day single-transaction limit.

[0074] In this scenario, first, the cross-border remittance application (client) can receive the remittance information filled in by the user, such as the remitter, the payee, the currency form of the remittance (the first resource, such as US dollars), the currency form of the receipt (the second resource, such as RMB), and the remittance amount (the resource share described by the first resource) or the received amount (the resource share described by the second resource). Based on this information, the client sends a remittance request (resource transfer request) to the remittance server (conversion server). The remittance server determines the amount that the user needs to pay through the client based on the remittance request, in combination with at least one relevant factor such as the handling fee and the exchange rate. Among them, when the remittance request contains the remittance amount, the remittance server can determine the amount to be paid by the client (the share to be transferred) in combination with the handling fee. If the handling fee is 0, the amount to be paid is the same as the remittance amount. When the remittance request contains the received amount, the amount to be paid can be determined in combination with the handling fee and the current exchange rate. On the other hand, the remittance server can also determine a unique corresponding remittance identifier (business identifier) for the remittance request. The remittance server feeds back the amount to be paid and the remittance identifier to the client. It can be understood that the exchange rates of different currency forms may be time-sensitive, for example, updated daily. Therefore, the amount to be paid fed back by the remittance server to the client can also be time-sensitive, for example, valid until 12:00 noon the next day, and so on. Optionally, before generating the remittance identifier, the remittance server can also first perform a legality verification based on the information such as the remittance account, the target account, and the remittance remarks submitted by the client, such as whether it involves illegal activities, etc. Only when the verification passes can subsequent operations be carried out. Otherwise, the request can be rejected or a risk warning can be given.

[0075] The client initiates a payment request to the payment server (associated transfer platform). Among them, the payment request may include a remittance identifier. The remittance identifier may also include the identifier of the remittance service end, so that the payment service end can parse the payment platform. The payment server interacts with the client, thereby using the remittance amount (first share) determined by the client to complete the current payment operation. Among them, the remittance amount can be determined by the payment subject selected by the client user, for example, the payment subject is an electronic wallet, there is a balance of 10,000 US dollars in the electronic wallet, the electronic wallet has a daily limit of 5,000 US dollars, and a single limit of 2,000 US dollars, then the remittance amount can be an amount not exceeding 2,000 US dollars. Optionally, in the case of incomplete payment, the payment server can also interact with the client to confirm whether to continue to pay or pay later (such as the next day). If the client user chooses to continue to pay, it can also continue to pay to the electronic wallet daily limit of 5,000 US dollars or less, as the amount paid for the current payment request (first share). In the case where the user chooses to pay later, the payment server can generate a payment record based on all the amounts paid by the current payment request. In an optional example, the user can also send an advance conversion request through the client to convert the paid first resource into the second resource at any time before the payment is completed. The user can also send batch conversion requests to the remittance server through the client, so that after each batch of resource transfer is completed, an attempt can be made to convert it into the second resource.

[0076] After the payment is completed, the payment server can determine the remittance service end according to the remittance identifier and send the payment record to the remittance service end. The payment record may contain the remittance identifier, so that the remittance service end can determine the remittance request for the payment according to the payment record. Then, the remittance service end can update the amount to be paid according to the payment amount in the payment record, combined with the current exchange rate, etc. Assuming that the subsequent payment fed back by the client is paid on the next day, the remittance service end can re-determine the amount to be paid on the next day according to the real-time exchange rate. Until the amount to be paid is 0 (not exceeding the predetermined share).

[0077] The remittance service end can settle the amount paid according to the remittance identifier and convert it into the target currency (such as RMB), thereby completing the cross-border remittance operation.

[0078] Looking back at the above process, in a more complex resource transfer process, the conversion server can comprehensively refer to various factors, dynamically update the share of transferred resources to be transferred, and complete the transfer process of transferred resources in batches, thereby providing an effective resource transfer method under the condition of transfer resource share restrictions.

[0079] exist Figure 2 In the sequence diagram shown, from the perspective of the conversion server, the execution process is as follows Figure 3 As shown:

[0080] Step 301: Receive a resource transfer request submitted by a client. The resource transfer request corresponds to a resource share described by a first resource and a second resource.

[0081] Step 302: Based on the resource share described by the first resource or the second resource, determine the share of the second resource to be transferred, and determine a service identifier for the resource transfer request.

[0082] Step 303: Feedback the share to be transferred and the service identifier to the client, so that the client can provide a first share of the first resource to the conversion server through the associated transfer platform according to the share to be transferred, and then the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server.

[0083] Step 304: Receive the transfer record, update the share to be transferred according to the service identifier and the first share, and feedback the updated share to be transferred to the client, so that the client can send a new resource transfer request to the associated transfer platform again until the updated share to be transferred does not exceed a predetermined share.

[0084] Step 305: When it is detected that a predetermined conversion condition is met, convert the total share of the transferred first resource into the second resource according to each transfer record corresponding to the service identifier, so as to complete the resource transfer operation for the resource transfer request.

[0085] As Figure 4 shown, from the perspective of the client, the operations performed in the Figure 2 illustrated sequence diagram include:

[0086] Step 401: Send a resource transfer request to the conversion server. The resource transfer request corresponds to a resource share described by the first resource or the second resource, so that the conversion server can determine the share of the first resource to be transferred based on the resource share described by the first resource or the second resource, and determine a service identifier for the resource transfer request.

[0087] Step 402: Receive the share of the first resource to be transferred and the service identifier from the conversion server.

[0088] Step 403: Provide a first share of the first resource to the conversion server through the associated transfer platform according to the share to be transferred, so that the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server, so that the conversion server can receive the transfer record, update the share to be transferred according to the service identifier and the first share, and feedback the updated share to be transferred to the client when the updated share to be transferred exceeds the predetermined share.

[0089] Step 404, when receiving the updated share to be transferred feedback from the conversion server, continue to provide the first resource to the conversion server via the associated transfer platform.

[0090] It should be noted that Figure 3 、 Figure 4 are descriptions of the resource transfer method process in batches from the perspectives of the conversion server and the client respectively. Figure 2 The relevant descriptions involved in the shown sequence diagram are also applicable to Figure 3 、 Figure 4 the process, which will not be elaborated here.

[0091] According to an embodiment of another aspect, a resource transfer device in batches is also provided. The device can be set in the conversion server. As Figure 5 described, the device 500 includes:

[0092] A communication unit 51, configured to receive a resource transfer request submitted by the client, and the resource transfer request corresponds to a resource share described by the first resource or the second resource;

[0093] A determination unit 52, configured to determine the share of the first resource to be transferred based on the resource share described by the first resource or the second resource, and determine a service identifier for the resource transfer request;

[0094] The communication unit 51 is further configured to feedback the share to be transferred and the service identifier to the client, so that the client provides the first share of the first resource to the conversion server through the associated transfer platform according to the share to be transferred, and then the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server;

[0095] An update unit 53, configured to receive the transfer record, update the share to be transferred according to the service identifier and the first share, and feedback the updated share to be transferred to the client, so that the client sends a new resource transfer request to the associated transfer platform again until the updated share to be transferred does not exceed the predetermined share;

[0096] A conversion unit 54, configured to, when detecting that a predetermined conversion condition is met, convert the total share of the transferred first resource into the second share of the target resource according to each transfer record corresponding to the service identifier, so as to complete the resource transfer operation for the resource transfer request.

[0097] It should be noted that Figure 5 the shown device 500 is a device embodiment corresponding to the Figure 3 shown method embodiment. Figure 2 The shown sequence diagram and Figure 3 the corresponding descriptions in the shown method embodiment are also applicable to the device 500, which will not be elaborated here.

[0098] According to an embodiment of another aspect, another resource transfer device in batches is further provided, which is disposed on the client side. As Figure 6 shown, the resource transfer device 600 in batches disposed on the client side may include:

[0099] A communication unit 61, configured to send a resource transfer request to the conversion server. The resource transfer request corresponds to a resource share described by a first resource or a second resource, so that the conversion server determines the share of the first resource to be transferred based on the resource share described by the first resource or the second resource, and determines a service identifier for the resource transfer request; and

[0100] Receive the share of the first resource to be transferred and the service identifier from the conversion server;

[0101] A transfer unit 62, configured to provide a first share of the first resource to the conversion server through an associated transfer platform according to the share to be transferred, so that the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server, for the conversion server to receive the transfer record, update the share to be transferred according to the service identifier and the first share, and in the case where the updated share to be transferred exceeds a predetermined share, feedback the updated share to be transferred to the client;

[0102] In the case where the communication unit 61 receives the updated share to be transferred fed back by the conversion server, the transfer unit 62 is further configured to continue to provide the first resource to the conversion server via the associated transfer platform.

[0103] It should be noted that Figure 6 the shown device 600 is a device embodiment corresponding to the method embodiment shown in Figure 4 The corresponding descriptions in the timing diagram shown and the method embodiment shown in Figure 2 also apply to the device 600, and will not be elaborated here. Figure 4

[0104] According to an embodiment of another aspect, a computer-readable storage medium is further provided, on which a computer program is stored. When the computer program is executed in a computer, the computer is made to execute the method described in conjunction with Figure 3 or Figure 4 or

[0105] Figure 3 According to an embodiment of still another aspect, a computing device is further provided, including a memory and a processor. An executable code is stored in the memory. When the processor executes the executable code, the method described in conjunction with Figure 4 or or

[0106] ​Those skilled in the art should be able to realize that in one or more of the above examples, the functions described in the embodiments of this specification can be implemented by hardware, software, firmware, or any combination thereof. When implemented using software, these functions can be stored in a computer-readable medium or transmitted as one or more instructions or codes on a computer-readable medium.

[0107] The specific implementation manners described above further elaborate on the purpose, technical solutions, and beneficial effects of the technical concept of this specification. It should be understood that the above are only specific implementation manners of the technical concept of this specification and are not used to limit the protection scope of the technical concept of this specification. Any modifications, equivalent replacements, improvements, etc. made on the basis of the technical solutions in the embodiments of this specification should be included within the protection scope of the technical concept of this specification.

Claims

1. A resource transfer method in batches, applicable to a resource transfer system, the resource transfer system including a client, a conversion server, and an associated transfer platform. The resource transfer system, through the conversion server, converts a first resource transferred out by an associated transfer platform from a resource transferor via the client into a second resource that is the receiving target of a resource recipient. The first resource and the second resource are resources in different forms; The method is applicable to the conversion server and includes: Receiving a resource transfer request submitted by a client, where the resource transfer request corresponds to a resource share described by a first resource or a second resource; Based on the resource share described by the first resource or the second resource, determining the share of the first resource to be transferred and determining a service identifier for the resource transfer request; Feeding back the share to be transferred and the service identifier to the client, so that the client provides a first share of the first resource to the conversion server through an associated transfer platform according to the share to be transferred, and then the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server; Receiving the transfer record, updating the share to be transferred according to the service identifier and the first share, and feeding back the updated share to be transferred to the client for the client to send a new resource transfer request to the associated transfer platform again until the updated share to be transferred does not exceed a predetermined share; When it is detected that a predetermined conversion condition is satisfied, converting the total share of the transferred first resource into a second resource according to each transfer record corresponding to the service identifier to complete the resource transfer operation for the resource transfer request.

2. The method according to claim 1, wherein The share to be transferred also corresponds to a transfer time limit, and the transfer time limit can indicate the start time and / or end time for the client to provide the first resource.

3. The method according to claim 1, wherein The first share is determined through at least one round of resource transfer interaction operations between the client and the associated transfer platform and by the client confirming the end of the current batch of resource transfers.

4. The method according to claim 1, wherein, When the resource transfer request includes a resource share described by a second resource, the determining the share of the first resource to be transferred based on the resource share described by the first resource or the second resource includes: Obtaining a conversion rule between the first resource and the second resource; Based on the resource share described by the second resource and the conversion rule, determining the share of the first resource to be transferred.

5. The method according to claim 4, wherein The conversion rule has timeliness; The receiving the transfer record and updating the share to be transferred according to the service identifier and the first share includes: Detecting the timeliness of the conversion rule at the current moment; When the current moment does not meet the timeliness of the conversion rule, obtaining the current conversion rule between the first resource and the second resource; Combining the current conversion rule to re-determine the total share of the first resource to be transferred; Updating the share to be transferred according to the difference between the total share to be transferred and the first share.

6. The method according to claim 1, wherein the predetermined conversion condition is one of the following: The updated share to be transferred does not exceed a predetermined share; Receiving an early conversion request sent by the client; Receiving a batch conversion request submitted by the client.

7. A batch-based resource transfer method, applicable to a resource transfer system, the resource transfer system including a client, a conversion server, and an associated transfer platform, the resource transfer system converting, through the conversion server, a first resource transferred out by an associated transfer platform via the client by a resource transferor into a second resource as the receiving target of a resource recipient, the first resource and the second resource being resources in different forms; The method is applicable to the client and includes: Sending a resource transfer request to the conversion server, where the resource transfer request corresponds to a resource share described by a first resource or a second resource, so that the conversion server determines the share of the first resource to be transferred based on the resource share described by the first resource or the second resource and determines a service identifier for the resource transfer request; Receive the share of the first resource to be transferred and the service identifier from the conversion server. According to the share to be transferred, provide, via the associated transfer platform, the first share of the first resource to the conversion server, so that the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server, for the conversion server to receive the transfer record, update the share to be transferred according to the service identifier and the first share, and in the case where the updated share to be transferred exceeds the predetermined share, feedback the updated share to be transferred to the client. In the case of receiving the updated share to be transferred fed back by the conversion server, continue to provide the first resource to the conversion server via the associated transfer platform.

8. The method according to claim 7, wherein The share to be transferred also corresponds to a transfer time limit, and the transfer time limit may indicate the start time and / or end time for the client to provide the first resource.

9. The method according to claim 7, wherein The providing, via the associated transfer platform, the first share of the first resource according to the share to be transferred includes: After at least one round of resource transfer interaction operations with the associated transfer platform, confirm the end of the current batch of resource transfer, so that the associated transfer platform determines the first share transferred by the at least one round of resource transfer interaction operations.

10. The method according to claim 7, wherein, After the providing, via the associated transfer platform, the first share of the first resource according to the share to be transferred, the method further includes: Send a batch conversion request for the first share of the first resource to the conversion server, for the server to convert the first resource of the first share into a second resource according to the batch conversion request.

11. The method according to claim 7, wherein, The method further includes: Send an early conversion request to the conversion server, for the server to convert the first resource in a plurality of transfer records corresponding to the service identifier into a second resource according to the early conversion request.

12. A batch-based resource transfer device is applicable to a resource transfer system. The resource transfer system includes a client, a conversion server, and an associated transfer platform. The resource transfer system converts a first resource transferred out by the client into a second resource that is the receiving target of the resource recipient via the conversion server. The first resource and the second resource are resources in different forms; The device is provided in the conversion server and includes: A communication unit configured to receive a resource transfer request submitted by a client, where the resource transfer request corresponds to a resource share described by a first resource or a second resource. A determination unit configured to determine, based on the resource share described by the first resource or the second resource, the share of the first resource to be transferred and determine a service identifier for the resource transfer request. The communication unit is further configured to feedback the share to be transferred and the service identifier to the client, for the client to provide, via the associated transfer platform, the first share of the first resource to the conversion server according to the share to be transferred, so that the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server. An update unit configured to receive the transfer record, update the share to be transferred according to the service identifier and the first share, and feedback the updated share to be transferred to the client, for the client to send a new resource transfer request to the associated transfer platform again until the updated share to be transferred does not exceed the predetermined share. A conversion unit, configured to, when it is detected that a predetermined conversion condition is satisfied, convert the total share of the transferred first resource into a second share of the target resource according to each transfer record corresponding to the service identifier, so as to complete the resource transfer operation for the resource transfer request.

13. A batch-based resource transfer device is applicable to a resource transfer system, which includes a client, a conversion server, and an associated transfer platform. The resource transfer system converts the first resource transferred out by the resource transferor from the client into the second resource that is the target received by the resource recipient through the conversion server. The first resource and the second resource are resources in different forms; The device is disposed in the client and includes: A communication unit, configured to send a resource transfer request to the conversion server, where the resource transfer request corresponds to a resource share described by a first resource or a second resource, so that the conversion server determines a share of the first resource to be transferred based on the resource share described by the first resource or the second resource, and determines a service identifier for the resource transfer request; and Receive the share of the first resource to be transferred and the service identifier from the conversion server; A transfer unit, configured to provide a first share of the first resource to the conversion server through an associated transfer platform according to the share to be transferred, so that the associated transfer platform sends a transfer record corresponding to the service identifier and the transferred first share to the conversion server, so that the conversion server receives the transfer record, updates the share to be transferred according to the service identifier and the first share, and feeds back the updated share to be transferred to the client when the updated share to be transferred exceeds a predetermined share; When the communication unit receives the updated share to be transferred fed back by the conversion server, the transfer unit is further configured to continue to provide the first resource to the conversion server via the associated transfer platform.

14. A computer-readable storage medium, on which a computer program is stored, and when the computer program is executed in a computer, the computer is made to execute the method according to any one of claims 1-11.

15. A computing device, comprising a memory and a processor, characterized in that, An executable code is stored in the memory, and when the processor executes the executable code, the method according to any one of claims 1-11 is implemented.

Images