A method, apparatus, device and medium for resource transfer

Abstract

Embodiments of the present specification disclose a resource transfer method, device, equipment and medium. The scheme comprises: acquiring a resource recharge trigger instruction sent by a first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to a plurality of entity red packets to an intermediate account corresponding to the plurality of entity red packets; based on the resource recharge trigger instruction, a resource recharge page is sent to the first terminal; acquiring the configured recharge resource parameters sent by the first terminal based on the resource recharge page; determining the total quantity of resources corresponding to the plurality of entity red packets to be transferred according to the configured recharge resource parameters; and transferring the total resources corresponding to the total quantity of resources from a first user account of the first terminal to the intermediate account.

Description

[0001] The present application is a divisional application of "A resource transfer method, device, equipment and medium (Filing date: May 18, 2023, Application number: 202310572455.X)". TECHNICAL FIELD

[0002] The present application relates to the technical field of computers, in particular to a resource transfer method, device, equipment and medium. BACKGROUND

[0003] Every year, festivals, weddings, funerals and weddings can be seen everywhere "give the younger generation lucky money", "marriage with a share", "opening a factory to make a profit" and other offline social package red envelope behaviors, but with the continuous penetration of mobile payment, a cashless society has become an irreversible trend. Users inevitably face the problem of cash storage and access.

[0004] Moreover, in the existing red envelope use process, if the user needs to use multiple red envelopes, the corresponding amount needs to be placed in each red envelope, and the user needs to repeatedly perform the action of packaging the red envelope, which is relatively cumbersome.

[0005] Therefore, how to improve the convenience of user using the red envelope is a technical problem to be solved. SUMMARY

[0006] The embodiments of the present specification provide a resource transfer method, device, equipment and medium to solve the inconvenience problem existing in the existing traditional red envelope use process.

[0007] To solve the above technical problems, the embodiments of the present specification are implemented as follows:

[0008] The resource transfer method provided by the embodiments of the present specification comprises:

[0009] Obtain a resource recharge trigger instruction sent by a first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to a plurality of entity red envelopes to intermediate accounts corresponding to the plurality of entity red envelopes; the entity red envelope has a code image thereon, and the code image is used to collect resources corresponding to the entity red envelope;

[0010] Based on the resource recharge trigger instruction, a resource recharge page is sent to the first terminal; the resource recharge page contains recharge resource parameters that can be configured by a user;

[0011] Obtain the configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0012] Determine the total number of resources corresponding to the plurality of entity red envelopes that need to be transferred according to the configured recharge resource parameters;

[0013] transfer the total resource corresponding to the total quantity of resources from a first user account of the first terminal to the intermediate account.

[0014] The embodiment of the present specification provides a resource transfer method, comprising:

[0015] obtain a resource taking trigger instruction sent by a second terminal based on a code image on a scanned entity red packet;

[0016] based on the resource taking trigger instruction, send a resource taking trigger page to the second terminal;

[0017] obtain a resource taking request sent by the second terminal based on the resource taking trigger page;

[0018] based on the resource taking request, transfer resources corresponding to the code image in the intermediate account to a second user account of the second terminal; the resources include resources transferred to the intermediate account according to the above method.

[0019] The embodiment of the present specification provides an entity red packet combination, comprising:

[0020] at least one first code image carrier, and a plurality of entity cards;

[0021] the first code image carrier carries a first code image; the first code image is used to transfer resources to an intermediate account according to the above method;

[0022] any one of the entity cards carries a second code image, and the second code image is used to take at least part of the resources.

[0023] The embodiment of the present specification provides a resource transfer device, comprising:

[0024] a recharge instruction obtaining module, configured to obtain a resource recharge trigger instruction sent by a first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to a plurality of entity red packets to an intermediate account corresponding to the plurality of entity red packets; the entity red packet has a code image, and the code image is used to take resources corresponding to the entity red packet;

[0025] a page sending module, configured to send a resource recharge page to the first terminal based on the resource recharge trigger instruction; the resource recharge page contains recharge resource parameters that can be configured by a user;

[0026] a parameter obtaining module, configured to obtain configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0027] a resource determining module, configured to determine a total quantity of resources corresponding to the plurality of entity red packets that need to be transferred according to the configured recharge resource parameters;

[0028] a resource transfer module, configured to transfer total resources corresponding to the total quantity of resources from a first user account of the first terminal to the intermediate account.

[0029] The embodiment of the present specification provides a resource transfer device, which comprises:

[0030] an obtaining module, configured to obtain a resource obtaining trigger instruction sent by a second terminal based on scanning a code image on an entity red packet;

[0031] a page sending module, configured to send a resource obtaining trigger page to the second terminal based on the resource obtaining trigger instruction;

[0032] a request obtaining module, configured to obtain a resource obtaining request sent by the second terminal based on the resource obtaining trigger page;

[0033] a resource transfer module, configured to transfer resources corresponding to the code image in the intermediate account to a second user account of the second terminal based on the resource obtaining request; the resources comprise resources transferred to the intermediate account according to the method.

[0034] The embodiment of the present specification provides a resource transfer device, which comprises:

[0035] at least one processor; and

[0036] a memory connected with the at least one processor in communication; wherein

[0037] the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to:

[0038] obtain a resource recharge trigger instruction sent by a first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to a plurality of entity red packets to an intermediate account corresponding to the plurality of entity red packets; the entity red packet has a code image thereon, and the code image is used to obtain resources corresponding to the entity red packet;

[0039] based on the resource recharge trigger instruction, send a resource recharge page to the first terminal; the resource recharge page contains recharge resource parameters that can be configured by a user;

[0040] obtain configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0041] determine a total quantity of resources to be transferred corresponding to the plurality of entity red packets according to the configured recharge resource parameters;

[0042] transfer the total resource corresponding to the total number of resources from a first user account of the first terminal to the intermediate account.

[0043] The device for resource transfer provided in the embodiments of the present specification comprises:

[0044] at least one processor; and

[0045] a memory in communication connection with the at least one processor; wherein

[0046] the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to:

[0047] obtain a resource taking trigger instruction sent by a second terminal based on scanning a code image on an entity red packet;

[0048] based on the resource taking trigger instruction, send a resource taking trigger page to the second terminal;

[0049] obtain a resource taking request sent by the second terminal based on the resource taking trigger page;

[0050] based on the resource taking request, transfer resources corresponding to the code image in the intermediate account to a second user account of the second terminal; the resources include resources transferred to the intermediate account according to the above method.

[0051] The computer readable medium provided in the embodiments of the present specification has computer readable instructions stored thereon, and the computer readable instructions can be executed by a processor to implement a resource transfer method.

[0052] One embodiment of the present specification achieves the following beneficial effects:

[0053] In the embodiments of the present specification, by obtaining a resource recharge trigger instruction sent by a first terminal, resources corresponding to a total number of resources to be transferred of a plurality of entity red packets can be transferred to an intermediate account according to a recharge resource parameter configured by a user, and then the plurality of entity red packets can be recharged, that is, a user can complete the recharge of a plurality of entity red packets by configuring a resource parameter once, and the user operation can be simplified. BRIEF DESCRIPTION OF DRAWINGS

[0054] In order to more clearly illustrate the technical solutions in the embodiments of the present specification or the prior art, the drawings needed in the embodiment or prior art description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments described in the present specification, and those skilled in the art can obtain other drawings according to these drawings without creative labor.

[0055] Figure 1 A structural schematic diagram of an entity red packet provided in an embodiment of the present specification;

[0056] Figure 2 An application scenario schematic diagram of a resource transfer method provided in an embodiment of the present specification;

[0057] Figure 3 A flow schematic diagram of a resource transfer method provided in an embodiment of the present specification;

[0058] Figure 4 A schematic diagram of a resource recharge page provided in an embodiment of the present specification;

[0059] Figure 5 A schematic diagram of a recharge result page provided in an embodiment of the present specification;

[0060] Figure 6 A schematic diagram of a resource recharge page provided in an embodiment of the present specification;

[0061] Figure 7 A schematic diagram of a resource transfer record page provided in an embodiment of the present specification;

[0062] Figure 8 A flow schematic diagram of a resource transfer method provided in an embodiment of the present specification;

[0063] Figure 9 A schematic diagram of a resource taking trigger page provided in an embodiment of the present specification;

[0064] Figure 10 A structural schematic diagram of a resource transfer apparatus provided in an embodiment of the present specification;

[0065] Figure 11 A structural schematic diagram of a resource transfer apparatus provided in an embodiment of the present specification;

[0066] Figure 12 A structural schematic diagram of a resource transfer device provided in an embodiment of the present specification. DETAILED DESCRIPTION

[0067] In order to make the purpose, technical solutions, and advantages of one or more embodiments of the present specification clearer, the technical solutions of one or more embodiments of the present specification will be described clearly and completely below in conjunction with specific embodiments of the present specification and corresponding drawings. Obviously, the described embodiments are only some of the embodiments of the present specification, rather than all the embodiments. Based on the embodiments in the present specification, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the scope of protection of one or more embodiments of the present specification.

[0068] The technical solutions provided by the embodiments of the present specification are described in detail below with reference to the drawings.

[0069] In order to solve the defects in the prior art, the present scheme provides the following embodiments:

[0070] An entity red packet combination is provided in the embodiments of the present specification, which can include at least one first code image carrier and a plurality of entity cards; wherein the first code image carrier carries a first code image; the first code image is used to transfer resources corresponding to the plurality of entity cards to an intermediate account; any one of the entity cards carries a second code image, and the second code image is used to claim at least part of the resources.

[0071] In actual application, a user can enter a process of charging the plurality of entity cards by scanning the first code image through a terminal. The terminal can display a resource charging page for charging the plurality of entity cards, and the user can configure the number of red packets, the number of resources, etc. for charging. For the charged entity card, the user can claim the resources corresponding to the card by scanning the second code image.

[0072] As an implementation manner, the first code image carrier in the embodiments of the present specification can be different from the plurality of entity cards described above, and the plurality of entity cards can include the second code image for claiming resources, and the first image carrier can include the first code image for charging the red packet. In actual application, the first code image carrier can be a cover, packaging, instruction manual, etc. of the entity red packet combination for the charging user to use, and does not need to be provided to the resource claiming party. The entity card in the entity red packet combination can be provided to the resource claiming party so that the resource claiming party can obtain the corresponding resources.

[0073] As another implementation manner, the first code image carrier in the embodiments of the present specification can be an entity card in the plurality of entity cards, specifically, it can be any card in the plurality of entity cards, or a specified card, for example, a card with a preset number. If it is any card in the plurality of entity cards, the user can charge the plurality of entity cards by scanning the code image on the card.

[0074] Wherein, the first code image can be the same code image as the second code image. If the entity card is not charged, the user can enter the charging process by scanning the code image on the card. If the entity card is charged, the user can enter the resource claiming process by scanning the code image on the card.

[0075] In actual application, the first code image and the second code image can also be different code images. If they exist on the same entity card, they can also correspond to a marking function, so that the user can charge or claim resources through the different code images.

[0076] Figure 1 A structural schematic diagram of an entity card provided in an embodiment of the present specification. The entity card can be an entity card in an entity red packet combination, as shown, the entity card can carry a code image 104, which can be used to send or receive red packet resources. Figure 1

[0077] The resource corresponding to the code image in the embodiment of the present specification can be at least part of the resources corresponding to a plurality of entity red packets transferred to the intermediate account through the resource parameters configured by the user.

[0078] The entity card can also carry a code image for sending a resource recharge trigger instruction; the resource recharge trigger instruction is used to transfer the recharge resources corresponding to a plurality of entity red packets to the intermediate accounts corresponding to the plurality of entity red packets. In actual application, the code image for sending resources or receiving resources can be the same code image, or can be different code images, which is not limited here.

[0079] The entity card can also carry a region 106 for extracting the verification information corresponding to the resource of the entity card, which can have at least a first state that can be read and a second state that cannot be read.

[0080] In order to ensure the security of the verification information, the verification information can be covered by a cover, or can be set to a form that can be displayed under certain specific conditions. The verification information can include a string, or a verification code image that can be identified by scanning the code.

[0081] As an implementation manner, the first state that can be read is specifically implemented by the following manner:

[0082] Removing the cover included on the entity card for covering the verification information, so that the verification information is in a display state;

[0083] Alternatively, the first state that can be read is specifically implemented by the following manner:

[0084] Placing the specific medium included on the entity card and carrying the verification information in a first preset environmental condition, so that the verification information is in a display state; the first preset environmental condition includes at least one condition of a preset temperature, a preset humidity, a preset light type, and a preset reading angle.

[0085] ​The cover can include a scratchable coating, a cover in the form of a sticker, and the like. The user can remove the cover to read the check information on the physical red envelope. The preset temperature, humidity, and light type can represent the temperature, humidity, and light in an abnormal environment, for example, 5 degrees below zero, 50 degrees above zero, and the like. The user can place the physical red envelope in a refrigerator or heat it to a high temperature so that the check information can be displayed. For example, it can be displayed under ultraviolet fluorescent light. For example, it can be displayed at a certain angle of inclination, and the like. When a specific medium is used, the physical card can contain instructions for obtaining check information so that the user can obtain the check information in the corresponding manner.

[0086] Similarly, the second state that cannot be read can be achieved by the following means:

[0087] The physical card can contain a cover for covering the check information, and the cover makes the check information in a hidden state.

[0088] Alternatively, the second state that cannot be read can be achieved by the following means:

[0089] The physical card can contain a specific medium carrying the check information, so that the check information is in a hidden state under natural conditions or normal viewing angle.

[0090] Natural conditions can be understood as conditions in a daily environment without the aid of other tools. Normal viewing angle can be understood as the viewing angle of normally looking at the physical red envelope, for example, the angle between the line of sight and the red envelope is perpendicular or within a predetermined range. By adjusting the viewing angle, for example, the angle between the line of sight and the red envelope is less than or equal to a predetermined angle, such as 5 degrees, 10 degrees, and the like, the hidden information can be seen. The hidden way of check information can be set according to actual needs, and then the check information can be viewed according to the corresponding way of the actual set hidden way. When the resource of the red envelope is taken, the check information can be in a hidden state, and the user who takes the red envelope can obtain the check information in the corresponding way to take the red envelope resource.

[0091] In practical applications, the physical card can also include an area for displaying a blessing. The area can be a blank area for the user to fill in the blessing; it can also contain at least part of the blessing printed on the card. In practical applications, the specific content of the blessing can be set according to the type of the red envelope, for example, the corresponding blessing can be set according to the use of the red envelope. The area for displaying the blessing can be located on the same side as the code image, or on different sides.

[0092] It can be understood that the code image in the embodiments of the present specification can be a two-dimensional code, a three-dimensional code, or other code image that can carry data information, and the specific form is not limited here. The hidden check information can be located below the code image, or above or on any side, or on the other side of the card carrier, and the specific location is not limited here.

[0093] In practical applications, the physical card can be a paper card, or a plastic material or other composite material. The preset shape can include quadrilaterals, polygons, circles, and other shapes, or a composite shape composed of multiple basic shapes, or a shape customized according to user needs, for example, a specific shape similar to an animal, a plant, a building, etc.

[0094] To make the physical card in the embodiments of the present specification closer to the traditional red envelope in the prior art, optionally, the physical red envelope combination provided in the embodiments of the present specification can also include a red envelope cover; the red envelope cover is used to load the physical card. The red envelope cover can also contain a blessing.

[0095] The check information used to extract the resources in the red envelope can be check information directly loaded on the physical card, or information obtained based on the check information on the red envelope. Assuming that the check information is a string of a preset number of digits, the string can be printed on the physical red envelope; or information used to obtain the string, such as a password or other string, can be printed on the physical card. When extracting resources, the user can input the password or other string in the designated application program, and the server can send the corresponding check information to the user terminal. The user can also extract resources according to the obtained check information.

[0096] In practical applications, the specific content of the check information can be set by the manufacturer, or set by the recharging user. For example, the recharging user can include a region for setting check information in the recharging page when recharging. The user can send the check information to the server, and the server can establish a corresponding relationship between the check information and the code image. The physical red envelope can contain a way or password, identifier, etc. for obtaining the check information. When extracting resources, the way or password, identifier, etc. for obtaining the check information can be used to obtain the check information from the server to extract the red envelope resources.

[0097] As shown in Figure 1 The physical card can also contain red envelope identifier information 108, such as a number, for distinguishing from other physical red envelopes. The identifier information can be numerical, alphabetical, or other character information.

[0098] Figure 2 An application scenario diagram for the resource transfer method in the embodiments of the present specification. As shown in Figure 2As shown, the scheme may include a first terminal 1, a server 2, physical red envelopes 3, and a second terminal 4. The first terminal 1 can send a resource recharge trigger command to the server 2 to recharge multiple physical red envelopes 3. The server 2 can then send a resource recharge page to the first terminal 1 based on this command. Users can configure recharge resource parameters on this page, such as the number of red envelopes to recharge and the amount of resources to recharge. The server 2 can obtain the configured recharge resource parameters sent through this page and transfer the total amount of resources corresponding to the multiple physical red envelopes 3 from the user's account on the first terminal to an intermediate account. When claiming a red envelope, the second terminal 4 can scan the QR code on the physical red envelope to obtain the corresponding resources from the intermediate account.

[0099] Next, a method for transferring resources provided in the embodiments of the specification will be described in detail with reference to the accompanying drawings:

[0100] Figure 3 This is a flowchart illustrating a resource transfer method provided in an embodiment of this specification. From a programming perspective, the entity executing the process can be a program hosted on an application server or an application client.

[0101] like Figure 3 As shown, the process may include the following steps:

[0102] Step 302: Obtain the resource recharge trigger instruction sent by the first terminal; the resource recharge trigger instruction is used to transfer the recharge resources corresponding to the multiple physical red envelopes to the intermediate accounts corresponding to the multiple physical red envelopes; the physical red envelope has a code image, and the code image is used to claim the resources corresponding to the physical red envelope.

[0103] Physical red envelopes can be distributed as described above. Figure 1 The physical cards shown may have a QR code image, which users can scan with their terminals to claim the corresponding resources. The resource recharge trigger command can recharge multiple physical red envelopes. Red envelope recharge can be understood as the server determining the correspondence between the physical red envelope and the corresponding resource based on the QR code image or other identification information on the physical red envelope. Subsequently, when claiming resources based on the QR code image, this correspondence can be used to determine the available resources.

[0104] Step 304: Based on the resource recharge trigger instruction, send a resource recharge page to the first terminal; the resource recharge page contains recharge resource parameters that can be configured by the user.

[0105] The resource recharge page can include an area for users to configure recharge resource parameters. Users can select or fill in recharge parameters, such as the number of recharge bonuses, the recharge amount, etc.

[0106] Step 306: obtaining the configured charging resource parameter sent by the first terminal based on the resource charging page.

[0107] Step 308: determining the total quantity of resources to be transferred corresponding to the multiple entity red packets according to the configured charging resource parameter.

[0108] The total quantity of resources can represent the total quantity of resources required for charging the multiple red packets, for example, the total charging amount.

[0109] Step 310: transferring the total quantity of resources corresponding to the total quantity of resources from the first user account of the first terminal to the intermediate account.

[0110] The first user account can represent a user account logged in the first terminal, or an account determined to provide the transferred resources, and the like. The intermediate account can represent an account temporarily storing the charging resources corresponding to the red packets, and the charging resources can be temporarily stored in the intermediate account before the resources are collected or within a preset time period after the charging. When the resources are collected, the resources can be sent from the intermediate account to the account of the collector.

[0111] It should be understood that the order of some steps in the method described in one or more embodiments of the present specification can be exchanged according to actual needs, or some steps can be omitted or deleted.

[0112] Figure 3 In the method in the present specification, by obtaining the resource charging trigger instruction sent by the first terminal, the total quantity of resources to be transferred corresponding to the multiple entity red packets can be transferred to the intermediate account according to the charging resource parameter configured by the user, and then the multiple entity red packets can be charged, that is, the user can configure the resource parameter once to complete the charging of the multiple entity red packets, and the user operation can be simplified.

[0113] In the present specification, the entity red packet can include a code image and an entity card carrier, the first terminal charges the code image, and the second terminal scans the charged code image to obtain the corresponding resources, so that the ritual of human relationship can be preserved while making and receiving gifts are more convenient, and the convenience of sending and collecting red packets between users is improved.

[0114] In addition, in the existing transfer method, the account information of the extractor or the payee is generally required to transfer the funds, and the method in the present specification does not require the account information of the extractor or the payee, but transfers the funds through the intermediate account. The charging party or the sender can scan the code image on the entity red packet to transfer the funds to the intermediate account, and the extractor or the payee can scan the code image to extract the funds from the intermediate account to the personal account, which can simplify the user operation and avoid problems caused by incorrect provision of the payee account, and the user experience is better.

[0115] based on Figure 3 In addition to the method described herein, this specification also provides some specific implementation schemes of the method, which will be described below.

[0116] In practical applications, the quantity of the aforementioned multiple physical red envelopes can be set by the user according to actual needs, and can also be set as optional according to actual needs. In the embodiments of this specification, the aforementioned recharge resource parameters include parameters representing the number of physical red envelopes being recharged, recharge method parameters, and recharge resource quantity parameters, etc.

[0117] Figure 4 This is a schematic diagram of a resource recharge page provided in an embodiment of this specification. Figure 4 As shown, this page may include an information area 402 for configuring the number of recharged red envelopes, and an information area 404 for configuring the number of recharged resources. This number may include the total resource quantity required for multiple physical red envelopes or the resource quantity for a single red envelope. It may also include an information area 406 for configuring the red envelope recharge method. In practical applications, users can fill in or select the red envelope data to be recharged in information area 402, and select the recharge method in information area 404. The recharge method may include a fixed amount recharge, a random amount recharge, or a method where part is filled with a first amount and part with a second amount, etc. The specific recharge method can be set according to actual needs and is not specifically limited here. As one implementation method, if the user selects the random filling method, area 404 can display the area for configuring the total resource quantity; if the user selects the fixed amount filling method, area 404 can display the area for configuring the resource quantity for a single red envelope.

[0118] In practical applications, the resource recharge page can also include the requirement to set notes. For example, users can set a blessing or other notes in this area, and users who receive resources can also obtain the blessing or configuration information after receiving the resources.

[0119] In the embodiments of this specification, after obtaining the recharge parameters configured by the user, the server can also determine information such as the resource quantity corresponding to each of the multiple physical red envelopes recharged, so as to facilitate the subsequent collection of red envelope resources. Optionally, the method in the embodiments of this specification may further include:

[0120] Based on the configured recharge method parameters, determine the target recharge method corresponding to the multiple physical red envelopes;

[0121] Based on the target recharge method and the configured recharge resource quantity parameters, determine the target resource quantity corresponding to each of the multiple entity red envelopes.

[0122] The server can also establish a correspondence between the target resource data and each entity red packet, so as to determine the resources that can be taken by the taking user according to the correspondence. The correspondence can include a correspondence between a code image, a code value or other identifier on the entity red packet and the corresponding resource.

[0123] For the fixed amount recharge mode, the user can configure the resource quantity corresponding to each entity red packet, and the resource quantity corresponding to multiple entity red packets can be configured to be the same, or the resource quantity can be configured respectively, and the like. Optionally, the above target recharge mode in the embodiments of the present specification can include a first recharge mode indicating a fixed amount configured by the user corresponding to each entity red packet; the above recharge resource quantity parameter can include a first resource quantity configured by the user corresponding to each entity red packet; and the above determining the target resource quantity corresponding to each entity red packet in the multiple entity red packets according to the target recharge mode and the configured recharge resource quantity parameter can specifically include:

[0124] determining the target resource quantity corresponding to each entity red packet in the multiple entity red packets according to the first recharge mode and the first resource quantity.

[0125] For the random amount recharge mode, the user can configure a total resource quantity corresponding to multiple entity red packets, and the server can determine the resource quantity corresponding to each entity red packet according to a random algorithm. Optionally, the target recharge mode in the embodiments of the present specification can include a second recharge mode of randomly determining the resource quantity corresponding to each entity on the basis of the configured total resource quantity; the recharge resource quantity parameter can include the configured total resource quantity; and the above determining the target resource quantity corresponding to each entity red packet in the multiple entity red packets according to the target recharge mode and the configured recharge resource quantity parameter can specifically include:

[0126] determining the target resource quantity corresponding to each entity red packet in the multiple entity red packets according to the second recharge mode, based on the total resource quantity configured by the user and using a preset random filling algorithm.

[0127] In actual application, the resource quantity corresponding to each entity red packet can be determined based on the configuration parameter provided by the recharge user, and after the recharge is completed, the resource corresponding to each entity red packet can have been determined; the resource corresponding to each red packet can also be determined according to the red packet taking situation, and the specific resource quantity corresponding to each red packet can be determined again in the taking stage. The preset random filling algorithm can be an existing red packet random recharge algorithm, which is not described herein again.

[0128] In actual application, the user can charge the multiple entity red packets through a terminal application in the first terminal, and the resource charging page can be an application page in the terminal application. As an implementation form, the terminal application can include an operation control, and the first terminal can generate the resource charging trigger instruction based on the operation of the user on the operation control.

[0129] As an implementation form, the resource charging trigger instruction can also be generated based on terminal code scanning. Optionally, in the embodiments of the present specification, the above-mentioned obtaining of the resource charging trigger instruction sent by the first terminal can specifically include:

[0130] Obtaining the resource charging trigger instruction sent by the first terminal based on scanning a code image on a preset entity red packet.

[0131] The preset entity red packet can be an entity red packet in the multiple entity red packets to be charged by the user, such as the entity card in the above-mentioned entity red packet combination, and the user can scan the code image on the entity red packet through the first terminal. The code image can be the same code image as the code image for receiving the red packet resource, or can be a different code image, which is not limited here. In the embodiments of the present specification, the multiple entity red packets to be charged can belong to the same red packet combination, and the user can scan the code image in the red packet combination to charge the multiple entity red packets. Optionally, in the embodiments of the present specification, the preset entity red packet can be one entity red packet in the multiple entity red packets; or the preset entity red packet can be one entity red packet in the red packet combination to which the multiple entity red packets belong; and one red packet combination can include multiple entity red packets having an association relationship.

[0132] The one red packet combination can include multiple entity red packets having an association relationship, and at least part of the red packets in the red packet combination can be charged through the code image on one red packet in the red packet combination. In order to facilitate user operation, reduce the understanding and use threshold of the user, and reduce the processing of the manufacturer or the server, as an implementation form, any red packet in the red packet combination can be used for charging, and the above-mentioned preset entity red packet can be any entity red packet in the red packet combination. The server can pre-store the code values or red packet identifiers of the red packets in the red packet combination, so as to determine the entity red packets to be charged when the user scans the code for charging.

[0133] As an implementation form, the red packet combination in the embodiments of the present specification can further include at least one main entity red packet and multiple secondary entity red packets; the above-mentioned multiple entity red packets to be charged can be multiple secondary entity red packets in the red packet combination; the above-mentioned preset entity red packet for charging the multiple entity red packets can be a main entity red packet, the code image on the preset entity red packet can be a code image on the main entity red packet, the code image on the main entity red packet is used for charging the secondary entity red packets; and the code image on the secondary entity red packet is used for receiving the resources corresponding to the secondary entity red packet.

[0134] In actual application, the main entity red packet can be the first code image carrier in the above-mentioned entity red packet combination. Specifically, the main entity red packet can be the entity red packet with the smallest or largest number in the red packet combination. If the red packet combination contains a cover red packet, the main entity red packet can also be the cover red packet. The cover red packet can be understood as a card containing relevant introduction information about how to charge and collect red packet resources. The cover red packet can be used by the charging party and can not be provided to the collecting party.

[0135] If the user charges at least part of the red packets in the red packet combination, the server can also select a preset number of red packets from the red packet combination as the red packets to be charged. Optionally, the preset entity red packet in the embodiment of the present specification can be one entity red packet in the red packet combination to which the plurality of entity red packets belong. One red packet combination can include a plurality of entity red packets having an association relationship. The charging resource parameter can include a parameter representing the number of red packets of the entity red packets to be charged. The method in the embodiment of the present specification can further include:

[0136] According to the code identifier of the code image on the preset entity red packet, a red packet identifier set corresponding to the red packet combination to which the preset entity red packet belongs is determined. One red packet identifier in the red packet identifier set corresponds to one entity red packet in the red packet combination.

[0137] A red packet identifier of the configured number of red packets is selected from the red packet identifier set. The selected red packet identifier is used to represent the entity red packet to be charged.

[0138] The server can save a red packet identifier set representing a red packet combination. The red packet identifier can be a number, a code value, or the like. After obtaining the number information of the red packets to be charged configured by the user, the server can select the identifiers of the number of red packets from the combination to represent the red packets to be charged. In actual application, the user can charge all the red packets in the red packet combination at one time, or can charge part of them. If the user has charged part of the red packets before, the server can also mark the red packet identifiers of the charged or uncharged red packets. The red packets to be charged can be selected from the uncharged red packet identifiers.

[0139] To facilitate the user to understand the charging situation of the red packets and to distribute the charged red packets, the entity red packet in the embodiment of the present specification can further include identifier information of the red packet identifier. The method in the embodiment of the present specification can further include: sending the identifier information of the red packet identifier representing the charged entity red packet to the first terminal, so that the first terminal displays the identifier information of the charged entity red packet.

[0140] Figure 5 A schematic diagram of a charging result page is provided in the embodiment of the present specification. As shown in FIG. 6, the red packet combination can include a plurality of entity red packets. The user can select a number of red packets to be charged. The server can select the red packet identifiers of the selected red packets from the red packet combination and send the identifier information of the selected red packets to the first terminal. The first terminal can display the identifier information of the selected red packets. Figure 5As shown, the page can include the identification information 502 of the recharged entity red packets, such as "NO. ABC-001 to NO. ABC.050", and the user can determine the recharged entity red packets according to the information, so as to avoid sending the uncharged red packets.

[0141] As an implementation, the user can also specify the recharged red packets in the embodiments of the present specification, and the above resource recharging page can further include an area for filling the identification information of the recharged red packets; and the configured recharging resource parameter can include the identification information of the recharged entity red packets configured by the user. The user can configure the identification information, such as the number, of the red packets to be filled in the area, which can be continuous or discontinuous, and the server can recharge the corresponding entity red packets according to the identification information configured by the user.

[0142] When selecting the red packets to be recharged in the embodiments of the present specification, the server can randomly or in a certain order, such as the red packet number order, select the red packets to be recharged; or the server can determine the red packets to be recharged according to the identification information of the recharged red packets configured by the user.

[0143] To ensure resource security, the entity red packets in the embodiments of the present specification can further include verification information; the verification information can be used to extract the resource corresponding to the entity red packet, and can have at least a first state that can be read and a second state that cannot be read.

[0144] Figure 6 A schematic diagram of a resource recharging page provided by the embodiments of the present specification is shown in FIG. 6. Figure 6 As shown, the resource recharging page can include information 602 indicating the collection method of the resource corresponding to the entity red packet collected by the recipient, wherein the collection method can include at least a first collection method for indicating that the recipient needs to input the verification information on the entity red packet to extract the resource in the code image and / or a second collection method for indicating that the recipient does not need to input the verification information on the entity red packet to extract the resource in the code image. The user can select one of the collection methods. In actual application, the resource recharging page can also display one collection method, and if the user does not select the collection method, it indicates that the recipient needs to handle according to another collection method. For example, as shown in FIG. 6, the resource recharging page displays the first collection method indicating that the recipient needs to input the verification information, such as "The recipient needs to input the password after the other party scans the code to collect the resource", and if the user selects the collection method, it indicates that the recipient needs to input the verification information to collect the red packet resource; if the user does not select the collection method, it can indicate that the recipient does not need to input the verification information, or it can indicate that the recipient can collect the red packet resource by scanning the code. Figure 6

[0145] ​After the user in the embodiment of the present specification configures the receiving mode on the recharge page, the server can also establish the correspondence between the receiving mode and the code image and the configured resource quantity parameter, so that when the subsequent receiving party receives the red packet resource, the resource corresponding to the configured resource quantity parameter is sent to the extracting party according to the receiving mode configured by the recharging party. Optionally, the method in the embodiment of the present specification can also include: obtaining the configured receiving mode information sent by the first terminal based on the resource recharge page;

[0146] Establishing the correspondence between the receiving mode corresponding to the configured receiving mode information and the configured recharge resource parameter.

[0147] It can be understood that the above Figure 4 and Figure 6 The page schematic diagram provided in the present specification is only an example given by the scheme in the embodiment of the present specification, and in actual application, specific page content can be displayed according to actual needs, for example, when the random filling mode is used, an information area for configuring the identification information of the recharge red packet can also be displayed, when the fixed amount filling mode is used, an information area for configuring the quantity of the recharge red packet can also be displayed, and the like.

[0148] In view of the fact that in actual application, the user may send or receive a plurality of times through the physical red packet, since each time may represent a piece of human relationship, the user needs to record, and usually the user may need to record the red packet receiving or sending situation each time through a physical notebook or an electronicized memorandum, the user may face the problems of a large amount of manual accounting and data loss risk. In order to improve the convenience of the user, the server in the embodiment of the present specification can also generate record information corresponding to the physical red packet for the user to view. Optionally, the method in the embodiment of the present specification can also include:

[0149] Obtaining a resource transfer record query instruction;

[0150] Based on the query instruction, obtaining record information of a plurality of resource transfer records generated by scanning a plurality of code images on the physical red packets; the record information includes a record of the first terminal sending resources through the code image on the physical red packet and / or a record of the first terminal receiving resources through the code image on the physical red packet;

[0151] Sending the record information to the first terminal, so that the first terminal displays a resource transfer record page.

[0152] The obtaining of the resource transfer record query instruction can specifically include:

[0153] Obtaining a resource transfer record query instruction generated by the first terminal based on a first operation of a user; the first operation includes an operation performed by the user on a display page presented by the first terminal after scanning a code image on the entity red packet;

[0154] Or,

[0155] Obtaining a resource transfer record query instruction generated by the first terminal based on a search keyword provided by the user; the search keyword is related to the entity red packet.

[0156] In the embodiment of the present specification, after completing the recharge, the terminal can display a page indicating that the recharge is completed, and the page can include a control for querying the record, such as Figure 5 As shown in "View my transaction record". In actual application, after the resource is taken or the code image on the entity red packet that has been taken is scanned, the terminal can also display a page indicating that the resource has been taken, and the page can also include a control for querying the record. The user operates the control, and the terminal can send a resource transfer record query instruction to the server, and the server can query the corresponding record information and feed back to the terminal.

[0157] In actual application, the user can take or recharge the entity red packet through the terminal application or applet in the terminal, and the terminal application or applet can include a search area for searching the record, and the user can input the keyword related to the entity red packet to view the record information. For example, the user inputs "no cash red packet" in the search box of the terminal application, can enter the corresponding applet, and the applet page can include a control for querying the record by the user, and the user can view the record information by operating the control. It can be understood that the above is only an example for more clearly illustrating the method provided in the embodiment of the present specification, and the specific search method can be set according to the actual situation in actual application, which is not limited here.

[0158] Figure 7 A schematic diagram of a resource transfer record page provided in the embodiment of the present specification is shown in FIG. 7. Figure 7 As shown in the figure, the record page can include record information 702 of a plurality of resource transfer records. The information can include the information of the sender or the taker, the specific resource quantity, and the time information. The page can also include a control 704 connected to the address of the purchased entity red packet, which can facilitate the user to purchase the required entity red packet.

[0159] Based on the same idea, the resource transfer method for taking resources corresponding to the above resource transfer method for recharging resources is also provided in the embodiment of the present specification.

[0160] Figure 8A flowchart of a method of resource transfer is provided in the embodiments of the present specification. From the perspective of a program, the execution subject of the flowchart can be a program or an application client loaded on an application server.

[0161] As shown in Figure 8 , the method can include:

[0162] Step 802: Obtain a resource taking trigger instruction sent by a second terminal based on a code image on a scanned physical red packet.

[0163] The physical red packet can include a physical red packet recharged according to the method described above, as shown in Figure 1 , which can contain a code image.

[0164] Step 804: Based on the resource taking trigger instruction, send a resource taking trigger page to the second terminal.

[0165] The resource taking trigger page can contain resource quantity information, sender information, and can also contain note information provided by the sender, such as a blessing.

[0166] Step 806: Obtain a resource taking request sent by the second terminal based on the resource taking trigger page.

[0167] The resource taking trigger page can contain a control for taking resources, such as an "immediately take" control. The second terminal can send a resource taking request to the server by operating the control.

[0168] Step 808: Based on the resource taking request, transfer the resources corresponding to the code image in the intermediate account to a second user account of the second terminal; the resources can include the resources transferred to the intermediate account according to the resource transfer method described above.

[0169] The code image can be a code image in a plurality of physical red packets recharged according to the resource transfer method described above; the second user account can be a user account logged in the second terminal, or a user account from which resources are extracted.

[0170] To ensure resource security, the physical red packet in the embodiments of the present specification can include verification information; the verification information is used to extract resources corresponding to the physical red packet, and at least has a first state that can be read and a second state that cannot be read. The method in the embodiments of the present specification can also include:

[0171] Obtain to-be-verified information sent by the second terminal based on the resource taking trigger page;

[0172] Determine whether the to-be-verified information is consistent with the verification information, and obtain a determination result;

[0173] The transferring the resource corresponding to the code image in the intermediate account to the second user account of the second terminal specifically includes:

[0174] If the judgment result indicates that the to-be-verified information is consistent with the verification information, the resource corresponding to the code image in the intermediate account is transferred to the second user account of the second terminal.

[0175] The verification information can have at least a first state that can be read and a second state that cannot be read, and can also be understood as hidden verification information, for example, covered, or can be seen or read under certain light conditions, temperature conditions or sight angles, and cannot be read under normal conditions.

[0176] The verification information can be a string that can be displayed on the physical red packet, or an image such as a code image. The user can obtain the corresponding verification information in the form of a string by scanning the code, or send the code image or the code value of the code image to the server for verification. The specific form is not specifically limited here.

[0177] Figure 9 A schematic diagram of a resource obtaining trigger page provided in an embodiment of the present specification is shown in FIG. 9, which can include a verification information area 902 for filling in the verification information. In order to facilitate the user to input the corresponding verification information, the page can also include prompt information indicating the verification information obtaining method, such as “please scratch off the coating and input the password”, and the specific content can be set according to actual needs and is not specifically limited here. Figure 9

[0178] After the second terminal user fills in the verification information, the second terminal can send the resource obtaining information in the resource obtaining trigger page to the server, which can include the to-be-verified information filled in by the user.

[0179] The server can save the correspondence between the code image on the physical red packet and the verification information carried on the physical red packet. If the to-be-verified information filled in by the user is consistent with the verification information carried on the physical red packet, it can indicate that the to-be-verified information provided by the user is consistent with the verification information stored in the server, which can indicate that the verification is passed, and the second terminal can obtain the resource in the physical red packet.

[0180] When the user obtains the resource in the physical red packet in the embodiment of the present specification, the resource can be obtained by inputting the verification information, which can ensure the security of the resource. Moreover, the verification information can be carried in the physical red packet, so that only the user who has the physical red packet can obtain the resource, which can effectively prevent the resource from being obtained by other users.

[0181] ​As described above about the embodiment of the resource taking of the resource sending, the resource sender can set whether the resource taker needs to input the verification information when taking the resource. In the taking process, the server can also determine the taking mode corresponding to the code image. If the taking mode is the taking mode that needs to input the verification information, the taking trigger page sent to the second terminal can include the verification information area for filling in the verification information. If the taking mode is the taking mode that does not need to input the verification information, the taking trigger page sent to the second terminal can not include the verification information area for filling in the verification information. Optionally, the embodiment of the present specification can also include:

[0182] determining the resource taking mode corresponding to the code image based on the resource taking trigger instruction;

[0183] The sending of the resource taking trigger page to the second terminal can specifically include:

[0184] If the resource taking mode is the taking mode that needs the taker to input the verification information on the physical red envelope to extract the resource in the code image, the resource taking trigger page including the verification information area for providing the verification information is sent to the second terminal.

[0185] In actual application, the physical red envelope can be taken to extract the resource after being charged. Optionally, the method in the embodiment of the present specification can also include:

[0186] acquiring the state information of the code image, the state information including the first state information indicating that the code image is in an uncharged state or the second state information indicating that the code image is in a charged state;

[0187] The sending of the resource taking trigger page to the second terminal specifically includes:

[0188] If the code image is in the second state of being charged, the resource taking trigger page is sent to the first terminal.

[0189] If the code image is in the first state of not being charged, the resource charging page can be sent to the second terminal, or the page including the prompt information indicating that the resource is not charged can be sent to the second terminal. In actual application, if the physical red envelope has been taken, the page including the prompt information indicating that the resource has been taken can be sent to the second terminal. In actual application, the page can also include the control for viewing the record of the taken physical red envelope resource, so that the user can view the record information of the taken or sent physical red envelope resource.

[0190] Similar to the resource transfer method described above, the second terminal user can also view the resource record of himself. Optionally, the method provided in the embodiments of the present specification can further include:

[0191] obtaining the resource transfer record query instruction generated by the second terminal;

[0192] based on the query instruction, obtaining record information of a plurality of resource transfer records generated by scanning the code image on the entity red packet; the record information includes the record of the second terminal sending resources through the code image on the entity red packet and / or the record information of the second terminal collecting resources through the code image on the entity red packet;

[0193] sending the record information to the second terminal, so that the second terminal displays the resource transfer record page.

[0194] In actual application, after completing the resource transfer, a page indicating the resource transfer result can also be sent to the second terminal, which can include information of the resource quantity, information of the user account transferring resources, etc. It can also include a control for viewing the resource transaction record in the form of the entity red packet. The resource transfer record query instruction described above can be generated based on the control. Optionally, the method in the embodiments of the present specification can further include:

[0195] generating a resource collection result page; the resource collection result page includes a query control for querying the record of the resource transfer service based on the entity red packet participated by the second terminal;

[0196] sending the resource collection result page to the second terminal;

[0197] the obtaining of the resource transfer record query instruction generated by the second terminal specifically includes:

[0198] the obtaining of the resource transfer record query instruction generated by the second terminal based on the query control.

[0199] In actual application, the record can also be viewed through other ways, such as searching for a keyword in the terminal application, and entering the record page through a preset path, etc.

[0200] Based on the same idea, the embodiments of the present specification also provide a device corresponding to the resource transfer method described above. Figure 3 The device can include: Figure 10 As shown in FIG. 8, the device can include: Figure 10

[0201] ​The recharge instruction acquisition module 1002 is used to acquire a resource recharge trigger instruction sent by the first terminal; the resource recharge trigger instruction is used to transfer the recharge resources corresponding to the multiple physical red envelopes to the intermediate accounts corresponding to the multiple physical red envelopes; the physical red envelope has a code image, and the code image is used to claim the resources corresponding to the physical red envelope;

[0202] The page sending module 1004 is used to send a resource recharge page to the first terminal based on the resource recharge trigger instruction; the resource recharge page contains recharge resource parameters that can be configured by the user;

[0203] The parameter acquisition module 1006 is used to acquire the configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0204] The resource determination module 1008 is used to determine the total number of resources to be transferred corresponding to the multiple entity red envelopes according to the configured recharge resource parameters;

[0205] The resource transfer module 1010 is used to transfer the total resources corresponding to the total number of resources from the first user account of the first terminal to the intermediate account.

[0206] Based on the same idea, the embodiments in this specification also provide the above-mentioned Figure 8 The apparatus corresponding to the resource transfer method shown. Figure 11 This is a schematic diagram of a resource transfer device provided in an embodiment of this specification. Figure 11 As shown, the device may include:

[0207] The receiving instruction acquisition module 1102 is used to acquire the resource receiving trigger instruction sent by the second terminal based on the scanned code image on the physical red envelope;

[0208] The page sending module 1104 is used to send a resource retrieval trigger page to the second terminal based on the resource retrieval trigger instruction;

[0209] The request acquisition module 1106 is used to acquire the resource acquisition request sent by the second terminal based on the resource acquisition trigger page;

[0210] The resource transfer module 1108 is used to transfer the resources corresponding to the code image in the intermediate account to the second user account of the second terminal based on the resource retrieval request; the resources include the resources transferred to the intermediate account according to the above method.

[0211] Based on the same idea, embodiments of this specification also provide devices corresponding to the above-described resource transfer method. Figure 12 This is a schematic diagram of a resource transfer device provided as an embodiment of this specification. Figure 12As shown, the device 1200 can include:

[0212] at least one processor 1210; and

[0213] a memory 1230 in communication with the at least one processor;

[0214] wherein, corresponding to Figure 3 the method for transferring resources, the memory 1230 stores instructions 1220 executable by the at least one processor 1210, and the instructions are executed by the at least one processor 1210 to enable the at least one processor 1210 to:

[0215] obtain a resource recharge trigger instruction sent by a first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to a plurality of entity red packets to intermediate accounts corresponding to the plurality of entity red packets; the entity red packet has a code image thereon, and the code image is used to collect resources corresponding to the entity red packet;

[0216] based on the resource recharge trigger instruction, send a resource recharge page to the first terminal; the resource recharge page contains recharge resource parameters that can be configured by a user;

[0217] obtain configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0218] determine a total amount of resources corresponding to the plurality of entity red packets that need to be transferred according to the configured recharge resource parameters;

[0219] transfer total resources corresponding to the total amount of resources from a first user account of the first terminal to the intermediate accounts.

[0220] wherein, corresponding to Figure 8 the method for transferring resources, the memory 1230 stores instructions 1220 executable by the at least one processor 1210, and the instructions are executed by the at least one processor 1210 to enable the at least one processor 1210 to:

[0221] obtain a resource collection trigger instruction sent by a second terminal based on scanning a code image on an entity red packet;

[0222] based on the resource collection trigger instruction, send a resource collection trigger page to the second terminal;

[0223] obtain a resource collection request sent by the second terminal based on the resource collection trigger page;

[0224] Based on the resource taking request, the resource corresponding to the code image in the intermediate account is transferred to a second user account of the second terminal; the resource includes the resource transferred to the intermediate account according to the method.

[0225] Based on the same idea, the present specification also provides a computer readable medium corresponding to the above method. The computer readable medium stores computer readable instructions, and the computer readable instructions can be executed by a processor to implement the above resource transfer method.

[0226] Each of the embodiments in the present specification is described in a progressive manner, and the same or similar parts between the embodiments can be referred to each other. Each embodiment mainly describes the difference from other embodiments. In particular, for the device shown in the embodiments, since it is basically similar to the method embodiments, the description is relatively simple, and the related parts can be referred to the part of the method embodiments. Figure 12 The device shown in the embodiments is basically similar to the method embodiments, and the description is relatively simple, and the related parts can be referred to the part of the method embodiments.

[0227] In the 1990s, it was quite obvious to distinguish whether an improvement in a technology was in hardware (e.g., improvement in circuit structures of diodes, transistors, switches, etc.) or in software (improvement in method flow). However, as technology has evolved, many improvements in method flow today can be considered as direct improvements in hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structures by programming the improved method flow into hardware circuits. Therefore, it cannot be said that an improvement in a method flow cannot be implemented by hardware entity modules. For example, a programmable logic device (PLD) (e.g., a field programmable gate array (FPGA)) is an integrated circuit whose logic function is determined by user programming of the device. A digital system is "integrated" on a PLD by the designer programming it, rather than by asking a chip manufacturer to design and fabricate a custom integrated circuit chip. Moreover, instead of manually fabricating integrated circuit chips, this programming is now mostly implemented by "logic compiler" software, which is similar to software compilers used in program development, and the original code to be compiled is written in a specific programming language, which is called a hardware description language (HDL), and there are many such languages, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc., and the most commonly used are VHDL (Very-High-Speed Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should be aware that, as long as the method flow is logically programmed in the above-mentioned hardware description languages and programmed into an integrated circuit, a hardware circuit implementing the logical method flow can be easily obtained.

[0228] The controller can be implemented in any suitable way, for example, the controller can take the form of a microprocessor or processor and a computer readable medium storing computer readable program code, such as software or firmware, executable by the (micro)processor, logic gates, switches, an application specific integrated circuit (ASIC), a programmable logic controller and an embedded microcontroller, examples of which 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. Those skilled in the art will also know that, in addition to being implemented in pure computer readable program code, the controller can also be implemented to perform the same functions in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps. Therefore, such a controller can be considered as a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can even be considered as both a software module implementing a method and a structure within a hardware component.

[0229] The systems, apparatuses, modules or units illustrated by the above embodiments can be specifically implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer can 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.

[0230] For the sake of description, the above apparatuses are described in various units by functions respectively. Of course, the functions of each unit can be implemented in the same or multiple software and / or hardware in the implementation of the present application.

[0231] Those skilled in the art will understand that the embodiments of the present application can be provided as a method, a system or a computer program product. Therefore, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Moreover, the present application can 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.

[0232] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0233] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0234] The computer program instructions can also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof. Figure 1 one or more flowcharts and / or blocks in the flowcharts and / or combination thereof.

[0235] In one typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

[0236] The memory can include non-persistent memory and / or volatile memory, such as random access memory (RAM) and / or cache memory, non-volatile memory, such as read-only memory (ROM), EPROM, and / or flash memory. The memory is an example of computer-readable media.

[0237] Computer-readable media includes permanent and non-permanent, movable and non-movable media that can be implemented by any method or technology to store information. 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 technologies, compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, magnetic cassette, magnetic tape disk storage or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to a computing device. According to the definition herein, computer-readable media does not include transitory media such as modulated data signals and carriers.

[0238] It should also be noted that the terms "comprising", "containing", or any other variant thereof are intended to cover non-exclusive inclusions, such that a process, method, article or apparatus that comprises a list of elements does not only include those elements, but can also include other elements not expressly listed or inherent to such process, method, article or apparatus. Without more limitations, the element defined by the phrase "comprising a" does not exclude the presence of additional identical elements in the process, method, article or apparatus that includes the element.

[0239] Those skilled in the art will appreciate that embodiments of the present application can be provided as a method, system or computer program product. Accordingly, the present application can take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application can 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-ROMs, optical storage devices, etc.) containing computer usable program code.

[0240] The present application can be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform particular tasks or implement particular abstract data types. The present application can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communication network. In a distributed computing environment, program modules can be located in both local and remote computer storage media including memory storage devices.

[0241] The above merely provides an example of the present application, but is not intended to limit the present application. Any modification, equivalent replacement, improvement, etc. within the spirit and principle of the present application should be included in the scope of claims of the present application.

Claims

1. A method for transferring resources, the method comprising: Obtain the resource recharge trigger command sent by the first terminal; The resource recharge trigger instruction is used to recharge multiple physical red envelopes in the physical red envelope combination; Each of the plurality of physical red envelopes has a code image, which is used to claim the resources corresponding to the physical red envelope; Based on the resource recharge trigger command, a resource recharge page is sent to the first terminal; the resource recharge page contains recharge resource parameters that can be configured by the user; Obtain the configured recharge resource parameters sent by the first terminal based on the resource recharge page; Based on the configured recharge resource parameters, determine the total amount of resources to be transferred corresponding to the multiple entity red envelopes; The total resources corresponding to the total number of resources are transferred from the first user account of the first terminal to the corresponding intermediate account.

2. The method according to claim 1, wherein the recharge resource parameters include at least one of the following: a red packet quantity parameter representing the physical red packet being recharged, a recharge method parameter, and a recharge resource quantity parameter.

3. The method according to claim 2, further comprising: Based on the configured recharge method parameters, determine the target recharge method corresponding to the multiple physical red envelopes; Based on the target recharge method and the configured recharge resource quantity parameters, determine the target resource quantity corresponding to each of the multiple entity red envelopes.

4. The method according to claim 3, wherein the target recharge method includes a first recharge method representing a fixed amount configured by the user for each physical red envelope; and the recharge resource quantity parameter includes a first resource quantity configured by the user for each physical red envelope. The step of determining the target resource quantity corresponding to each of the multiple entity red envelopes based on the target recharge method and the configured recharge resource quantity parameters specifically includes: Based on the first recharge method and the first resource quantity, determine the target resource quantity corresponding to each of the multiple physical red envelopes.

5. The method according to claim 3, wherein the target recharge method includes a second recharge method that randomly determines the resource quantity corresponding to each entity red packet based on the configured total resource quantity; the recharge resource quantity parameter includes the configured total resource quantity; The step of determining the target resource quantity corresponding to each of the multiple entity red envelopes based on the target recharge method and the configured recharge resource quantity parameters specifically includes: According to the second recharge method, based on the total number of resources configured by the user, a preset random filling algorithm is used to determine the target resource quantity corresponding to each of the multiple entity red envelopes.

6. The method according to claim 1, wherein obtaining the resource recharge trigger instruction sent by the first terminal specifically includes: Obtain the resource recharge trigger command sent by the first terminal based on scanning the code image on the preset physical red envelope; The preset physical red envelope is one of the multiple physical red envelopes; or, the preset physical red envelope is one of the physical red envelopes in a red envelope combination to which the multiple physical red envelopes belong; a red envelope combination includes multiple physical red envelopes that are related.

7. The method according to claim 6, wherein the preset physical red envelope is one of the physical red envelopes in a group of physical red envelopes to which the plurality of physical red envelopes belong; a group of physical red envelopes includes a plurality of physical red envelopes with an association relationship; the recharge resource parameter includes a parameter indicating the number of physical red envelopes being recharged; The method further includes: Based on the code identifier of the code image on the preset physical red envelope, determine the set of red envelope identifiers corresponding to the physical red envelope combination to which the preset physical red envelope belongs; One red envelope identifier in the set of red envelope identifiers corresponds to one physical red envelope in the set of physical red envelopes; Select the configured number of red envelope identifiers from the set of red envelope identifiers; wherein the selected red envelope identifiers are used to represent the physical red envelopes that have been recharged.

8. The method according to any one of claims 1 to 7, wherein the physical red envelope further includes identification information of the red envelope identifier; the method further includes: The system sends identification information, representing the physical red envelope that has been recharged, to the first terminal so that the first terminal can display the identification information of the physical red envelope that has been recharged.

9. The method according to any one of claims 1 to 7, wherein the physical red envelope further includes verification information; the verification information is used to extract the resources corresponding to the physical red envelope, and has at least a first readable state and a second unreadable state; the resource recharge page further includes information indicating the method of receiving the resources corresponding to the physical red envelope; the method of receiving includes at least a first method indicating that the recipient needs to input the verification information on the physical red envelope to extract the resources in the code image and / or a second method indicating that the recipient does not need to input the verification information on the physical red envelope to extract the resources in the code image; The method further includes: Obtain the configured claiming method information sent by the first terminal based on the resource recharge page; Establish the correspondence between the configured claim method information and the configured recharge resource parameters.

10. The method according to any one of claims 1 to 7, wherein the first terminal does not need to provide information about the recipient.

11. The method according to any one of claims 1 to 7, wherein the resource recharge trigger instruction is sent by the first terminal scanning the code image on one of the physical red envelopes in the physical red envelope combination, or the resource recharge trigger instruction is sent by the first terminal scanning the code image on the cover, packaging, or instruction manual of the physical red envelope combination.

12. A method for transferring resources, applied to a first terminal, comprising: The first terminal sends a resource recharge trigger command to the server; The resource recharge trigger instruction is used to recharge multiple physical red envelopes in the physical red envelope combination; Each of the plurality of physical red envelopes has a code image, which is used to claim the resources corresponding to the physical red envelope; Obtain the resource recharge page returned by the server; the resource recharge page contains recharge resource parameters that can be configured by the user; Obtain the recharged resource parameters configured by the user based on the resource recharge page; The configured recharge resource parameters are sent to the server so that the server can determine the total amount of resources to be transferred corresponding to the multiple entity red envelopes according to the configured recharge resource parameters; The total resources corresponding to the total number of resources will be transferred from the first user account of the first terminal to the corresponding intermediate account.

13. The method according to claim 12, wherein the resource recharge trigger instruction is generated by the first terminal scanning the code image on one of the physical red envelopes in the physical red envelope combination, or the resource recharge trigger instruction is generated by the first terminal scanning the code image on the cover, packaging or instruction manual of the physical red envelope combination; or the resource recharge trigger instruction is generated based on the user's operation of the operation controls in the terminal application of the first terminal.

14. The method according to claim 12, wherein the resource recharge page includes at least one of the following: an information area for configuring the quantity of recharge red envelopes, an information area for configuring the quantity of recharged resources, an information area for configuring the recharge method of red envelopes, a remarks information area for setting blessings or other remarks, an area for filling in the identification information of the recharged red envelopes, and information indicating the method of receiving the resources corresponding to the physical red envelopes received by the recipient.

15. The method according to claim 12, wherein the physical red envelope further includes identification information of the red envelope identifier; the method further includes: Obtain the identifier information sent by the server that represents the physical red envelope that has been recharged; Displays the identification information of the physical red envelope that has been recharged.

16. The method according to claim 12, further comprising: The recharge result page is displayed; the recharge result page includes at least one of the following: a prompt message indicating that the recharge is complete, identification information indicating that the recharged physical red envelope has been recharged, and a control for querying records.

17. The method according to any one of claims 12 to 16, the method further comprising: Send a resource transfer record query command to the server; Based on the query command, the server obtains record information of several resource transfer records generated by scanning the code images on several physical red envelopes; the record information includes records of the first terminal sending resources through the code images on the physical red envelopes and / or records of the first terminal receiving resources through the code images on the physical red envelopes; Display the resource transfer record page containing the recorded information.

18. The method according to claim 17, wherein the resource transfer record query instruction is generated by the first terminal based on the user's first operation; the first operation includes the operation performed by the user on the display page after scanning the code image on the physical red envelope by the first terminal; Alternatively, the resource transfer record query instruction is a resource transfer record query instruction generated by the first terminal based on the search keywords provided by the user; The search keywords are related to the physical red envelope.

19. The method according to claim 17, wherein the resource transfer record page includes record information of a plurality of resource transfer records; the record information includes at least one of the following: information of the sender or recipient, resource quantity information, and time information; And / or, the resource transfer record page includes a control that links to an address for purchasing physical red envelopes.

20. A method for resource transfer, comprising: Obtain the resource claiming trigger command sent by the second terminal based on the scanned QR code image on the physical red envelope; Based on the resource acquisition trigger instruction, a resource acquisition trigger page is sent to the second terminal; Obtain the resource claiming request sent by the second terminal based on the resource claiming trigger page; Based on the resource retrieval request, the resources corresponding to the code image in the intermediate account are transferred to the second user account of the second terminal; the resources include those transferred to the intermediate account according to the method of claim 1.

21. The method according to claim 20, wherein the physical red envelope includes verification information; The verification information is used to extract the resources corresponding to the physical red envelope, and has at least a first state that can be read and a second state that cannot be read; The method further includes: Obtain the verification information sent by the second terminal based on the resource acquisition trigger page; Determine whether the information to be verified is consistent with the information to be verified, and obtain the determination result; The step of transferring the resources corresponding to the code image in the intermediate account to the second user account of the second terminal specifically includes: If the judgment result indicates that the information to be verified is consistent with the verification information, then the resources corresponding to the code image in the intermediate account are transferred to the second user account of the second terminal.

22. The method according to claim 21, further comprising: Based on the resource acquisition trigger instruction, determine the resource acquisition method corresponding to the code image; Sending the resource acquisition trigger page to the second terminal specifically includes: If the resource claiming method indicates that the claimant needs to input verification information on the physical red envelope to extract the resource from the code image, then a resource claiming trigger page containing a verification information area for providing verification information is sent to the second terminal.

23. The method according to claim 20, further comprising: Obtain the status information of the code image, the status information including a first status information indicating that the code image is in a state that has not been recharged or a second status information indicating that the code image has been recharged; Sending the resource claiming trigger page to the second terminal specifically includes: if the code image is in a second state that has been recharged, then sending the resource claiming trigger page to the first terminal; If the code image is in a first state where it has not been recharged, a resource recharge page is sent to the second terminal, or a page containing a prompt message indicating that it has not been recharged is sent to the second terminal.

24. The method according to claim 20, further comprising: Obtain the resource transfer record query instruction sent by the second terminal; Based on the query command, obtain the record information of several resource transfer records generated by scanning the code images on several physical red envelopes; the record information includes the record information of the second terminal sending resources through the code images on the physical red envelopes and / or the record information of the second terminal receiving resources through the code images on the physical red envelopes; The recorded information is sent to the second terminal so that the second terminal can display the resource transfer record page.

25. The method according to claim 24, further comprising: Generate a resource claiming results page; the resource claiming results page includes a query control for querying records of resource transfer services based on physical red envelopes that the second terminal has participated in; Send the resource acquisition result page to the second terminal; The step of obtaining the resource transfer record query instruction generated by the second terminal specifically includes: Obtain the resource transfer record query instruction generated by the second terminal based on the query control.

26. A method for transferring resources, applied to a second terminal, comprising: The second terminal scans the QR code image on the physical red envelope and sends a resource claiming trigger command to the server. The physical red envelope refers to the physical red envelope in the physical red envelope combination; Obtain the resource claim trigger page returned by the server; Based on the resource claim trigger page, a resource claim request is sent to the server, so that the server transfers the resources corresponding to the code image in the intermediate account to the second user account of the second terminal; the resources include the resources transferred to the intermediate account according to the method of claim 1.

27. The method according to claim 26, wherein the resource acquisition trigger page includes at least one area of ​​resource quantity information, sender information, remarks provided by the sender, and areas for filling in verification information; Alternatively, the resource claiming trigger page may include a control for claiming resources, and the resource claiming request may be generated based on the user's operation on the control.

28. The method according to claim 26, further comprising: The system receives a resource acquisition result page from the server. The resource acquisition result page includes at least one of the following: information on the quantity of resources, information on the user account that transferred the resources, and a control for viewing resource transaction records generated in the form of physical red envelopes.

29. A physical red envelope combination, comprising: At least one first-code image carrier, and multiple physical cards; The first code image carrier carries the first code image; The first code image is used to transfer the resources corresponding to the multiple physical cards to an intermediate account; Each of the physical cards carries a second code image, which is used to claim at least a portion of the resources.

30. The physical red envelope combination according to claim 29, wherein the first code image carrier is a physical card among the plurality of physical cards, or the first code image carrier is the cover, packaging or instruction manual of the physical red envelope combination; And / or, the first code image and the second code image are the same code image, or the first code image and the second code image are different code images; And / or, the physical card may also include red envelope identification information; or, the physical card may include an area for displaying or writing blessings.

31. The physical red envelope combination according to claim 29, wherein the physical card further includes verification information; the verification information is used to extract the resources corresponding to the physical card, and has at least a first readable state and a second unreadable state; in, The readable first state is specifically implemented in the following way: Remove the covering material on the physical card that obscures the verification information, so that the verification information is displayed. Alternatively, the first readable state can be implemented in the following way: placing the specific medium containing the verification information on the physical card under a first preset environmental condition, so that the verification information is displayed; the first preset environmental condition includes at least one of preset temperature, preset humidity, preset light type, and preset reading angle. Alternatively, the unreadable second state can be implemented in the following way: the physical card contains a cover for obscuring the verification information, and the cover makes the verification information hidden. Alternatively, the unreadable second state can be achieved by the following method: the physical card contains a specific medium carrying the verification information, such that the verification information is hidden under natural conditions or from a normal perspective.

32. An apparatus for transferring resources, the apparatus comprising: The recharge instruction acquisition module is used to acquire the resource recharge trigger instruction sent by the first terminal; The resource recharge trigger instruction is used to recharge multiple physical red envelopes in the physical red envelope combination; each of the multiple physical red envelopes has a code image, and the code image is used to claim the resources corresponding to the physical red envelope; The page sending module is used to send a resource recharge page to the first terminal based on the resource recharge trigger instruction; the resource recharge page contains recharge resource parameters that can be configured by the user; The parameter acquisition module is used to acquire the configured recharge resource parameters sent by the first terminal based on the resource recharge page; The resource determination module is used to determine the total amount of resources to be transferred corresponding to the multiple entity red envelopes according to the configured recharge resource parameters; The resource transfer module is used to transfer the total resources corresponding to the total number of resources from the first user account of the first terminal to the intermediate account.

33. A resource transfer apparatus, comprising: The receiving instruction acquisition module is used to acquire the resource receiving trigger instruction sent by the second terminal based on the scanned QR code image on the physical red envelope; The page sending module is used to send a resource acquisition trigger page to the second terminal based on the resource acquisition trigger instruction; The request acquisition module is used to acquire the resource acquisition request sent by the second terminal based on the resource acquisition trigger page; A resource transfer module is used to transfer the resources corresponding to the code image in the intermediate account to the second user account of the second terminal based on the resource retrieval request; the resources include the resources transferred to the intermediate account according to the method of claim 1.

34. A resource transfer device, said device being applied to a combination of physical red envelopes comprising multiple related physical red envelopes, said device comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor to enable the at least one processor to perform the resource transfer method according to any one of claims 1 to 28.

35. A computer-readable medium having stored thereon computer-readable instructions that can be executed by a processor to implement the method of transferring resources according to any one of claims 1 to 28.

Images