Method, device, equipment and medium for resource transfer

Abstract

The embodiments of this specification disclose a method, apparatus, device, and medium for resource transfer. The solution includes obtaining a resource recharge trigger instruction sent by a first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to multiple physical red envelopes to an intermediate account corresponding to the multiple physical red envelopes; based on the resource recharge trigger instruction, sending a resource recharge page to the first terminal; obtaining configured recharge resource parameters sent by the first terminal based on the resource recharge page; determining the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters; and transferring the total resources corresponding to the total amount of resources from a first user account of the first terminal to the intermediate account.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, apparatus, device, and medium for resource transfer. Background Art

[0002] During festivals, weddings, and funerals, the practice of giving red envelopes ("lucky money" for younger generations), wedding gifts, and red envelopes ("lucky money" for the start of a new job) is commonplace. However, with the increasing penetration of mobile payments, the trend towards a cashless society has become irreversible. This inevitably leads to the inconvenience of depositing and withdrawing cash.

[0003] Moreover, in the existing red envelope usage process, if the user needs to use multiple red envelopes, the corresponding amount needs to be put into each red envelope respectively. The user needs to repeat the red envelope packaging action, which is relatively cumbersome.

[0004] Therefore, how to improve the convenience of users using red envelopes is a technical problem that needs to be solved urgently. Summary of the Invention

[0005] The embodiments of this specification provide a method, apparatus, device, and medium for resource transfer to solve the inconvenience problem existing in the use of traditional red envelopes.

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

[0007] The embodiments of this specification provide a method for resource transfer, including:

[0008] Obtaining a resource recharge trigger instruction sent by the first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to the multiple physical red envelopes to the intermediate accounts corresponding to the multiple physical red envelopes; the physical red envelopes have a code image, and the code image is used to collect the resources corresponding to the physical red envelopes;

[0009] Based on the resource recharge trigger instruction, sending a resource recharge page to the first terminal; the resource recharge page includes recharge resource parameters that can be configured by the user;

[0010] Obtaining configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0011] Determining the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters;

[0012] The total resources corresponding to the total amount of resources are transferred from the first user account of the first terminal to the intermediate account.

[0013] The embodiments of this specification provide a method for resource transfer, including:

[0014] Obtaining a resource claim trigger instruction sent by the second terminal based on scanning a code image on the physical red envelope;

[0015] Based on the resource claim trigger instruction, sending a resource claim trigger page to the second terminal;

[0016] Obtaining a resource claim request sent by the second terminal based on the resource claim trigger page;

[0017] Based on the resource claiming 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 the resources transferred to the intermediate account according to the above method.

[0018] The embodiments of this specification provide a physical red envelope combination, including:

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

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

[0021] Any one of the physical cards carries a second code image, and the second code image is used to claim at least part of the resources.

[0022] An embodiment of this specification provides a resource transfer device, including:

[0023] a recharge instruction acquisition module, configured to acquire a resource recharge trigger instruction sent by the first terminal; the resource recharge trigger instruction is configured to transfer recharge resources corresponding to the plurality of physical red envelopes to intermediate accounts corresponding to the plurality of physical red envelopes; the physical red envelopes have a code image on them, the code image being used to claim the resources corresponding to the physical red envelopes;

[0024] 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 includes recharge resource parameters that can be configured by the user;

[0025] a parameter acquisition module, configured to acquire the configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0026] A resource determination module, configured to determine the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters;

[0027] The resource transfer module is configured to transfer the total resources corresponding to the total amount of resources from the first user account of the first terminal to the intermediate account.

[0028] An embodiment of this specification provides a resource transfer device, including:

[0029] A collection instruction acquisition module is used to obtain a resource collection trigger instruction sent by the second terminal based on scanning the code image on the physical red envelope;

[0030] a page sending module, configured to send a resource claim triggering page to the second terminal based on the resource claim triggering instruction;

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

[0032] 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 collection request; the resources include the resources transferred to the intermediate account according to the above method.

[0033] An embodiment of this specification provides a device for resource transfer, including:

[0034] at least one processor; and,

[0035] a memory communicatively connected to the at least one processor; wherein,

[0036] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0037] Obtaining a resource recharge trigger instruction sent by the first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to the multiple physical red envelopes to the intermediate accounts corresponding to the multiple physical red envelopes; the physical red envelopes have a code image, and the code image is used to collect the resources corresponding to the physical red envelopes;

[0038] Based on the resource recharge trigger instruction, sending a resource recharge page to the first terminal; the resource recharge page includes recharge resource parameters that can be configured by the user;

[0039] Obtaining configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0040] Determining the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters;

[0041] The total resources corresponding to the total amount of resources are transferred from the first user account of the first terminal to the intermediate account.

[0042] A resource transfer device provided in an embodiment of this specification includes:

[0043] at least one processor; and,

[0044] a memory communicatively connected to the at least one processor; wherein,

[0045] The memory stores instructions executable by the at least one processor, the instructions being executed by the at least one processor to enable the at least one processor to:

[0046] Obtaining a resource claim trigger instruction sent by the second terminal based on scanning a code image on the physical red envelope;

[0047] Based on the resource claim trigger instruction, sending a resource claim trigger page to the second terminal;

[0048] Obtaining a resource claim request sent by the second terminal based on the resource claim trigger page;

[0049] Based on the resource claiming 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 the resources transferred to the intermediate account according to the above method.

[0050] An embodiment of this specification provides a computer-readable medium having computer-readable instructions stored thereon. The computer-readable instructions can be executed by a processor to implement the above-mentioned resource transfer method.

[0051] One embodiment of this specification achieves the following beneficial effects:

[0052] In the embodiment of this specification, by obtaining the resource recharge trigger instruction sent by the first terminal, the total amount of resources to be transferred corresponding to multiple physical red envelopes can be transferred to the intermediate account according to the recharge resource parameters configured by the user, thereby realizing the recharge of multiple physical red envelopes, that is, the user can complete the recharge of multiple physical red envelopes by configuring the resource parameters once, which can simplify user operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] In order to more clearly illustrate the embodiments of this specification or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments recorded in this application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0054] Figure 1 This is a schematic diagram of the structure of a physical red envelope provided in an embodiment of this specification;

[0055] Figure 2This is a schematic diagram of an application scenario of a resource transfer method in an embodiment of this specification;

[0056] Figure 3 A flowchart of a resource transfer method provided in an embodiment of this specification;

[0057] Figure 4 A schematic diagram of a resource recharge page provided in an embodiment of this specification;

[0058] Figure 5 A schematic diagram of a recharge result page provided in an embodiment of this specification;

[0059] Figure 6 A schematic diagram of a resource recharge page provided in an embodiment of this specification;

[0060] Figure 7 A schematic diagram of a resource transfer record page provided in an embodiment of this specification;

[0061] Figure 8 A flowchart of a resource transfer method provided in an embodiment of this specification;

[0062] Figure 9 This is a schematic diagram of a resource claim triggering page provided in an embodiment of this specification;

[0063] Figure 10 A schematic diagram of the structure of a resource transfer device provided in an embodiment of this specification;

[0064] Figure 11 A schematic diagram of the structure of a resource transfer device provided in an embodiment of this specification;

[0065] Figure 12 A schematic diagram of the structure of a resource transfer device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0066] To make the purpose, technical solutions, and advantages of one or more embodiments of this specification more clear, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in conjunction with the specific embodiments of this specification and the corresponding drawings. Obviously, the embodiments described are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of one or more embodiments of this specification.

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

[0068] In order to solve the defects in the prior art, this solution provides the following embodiments:

[0069] In an embodiment of the present specification, a physical red envelope combination is provided, which may include: at least one first code image carrier, and multiple physical cards; wherein, the first code image carrier carries a first code image; the first code image is used to transfer resources corresponding to the multiple physical cards to an intermediate account; any one of the physical cards carries a second code image, and the second code image is used to collect at least part of the resources.

[0070] In practice, users can scan the first code image through a terminal to enter the process of recharging multiple physical cards. The terminal can display the resource recharge page for recharging multiple physical cards, where users can configure the amount of red envelopes and resources to be recharged. For the recharged physical cards, users can scan the second code image to claim the corresponding resources.

[0071] As an implementation method, the first code image carrier in the embodiments of this specification can be a different object from the multiple physical cards described above. The multiple physical cards can include a second code image for claiming resources, and the first image carrier can include a first code image for recharging red envelopes. In actual applications, the first code image carrier can be a cover, packaging, instruction manual, etc. in a physical red envelope combination for use by the recharging user, and does not need to be provided to the resource recipient. The physical card in the physical red envelope combination can be used to provide the resource recipient so that the resource recipient can obtain the corresponding resources.

[0072] As another embodiment, the first code image carrier in the embodiments of this specification can be a physical card from the multiple physical cards. Specifically, it can be any of the multiple physical cards, or a designated card, such as a card with a preset number. If it is any of the multiple physical cards, the user can top up multiple physical cards by scanning the code image on any of the cards.

[0073] Among them, the first code image and the second code image can be the same code image. If the physical card has not been recharged, the user can enter the recharge process by scanning the code image on the card. If the physical card has been recharged, the user can enter the resource collection process by scanning the code image on the card.

[0074] In actual applications, the first code image and the second code image can also be different code images. If they exist on the same physical card, they can also have corresponding marking functions so that users can recharge or receive resources through the code image of the enemy camp.

[0075] Figure 1This is a schematic diagram of the structure of a physical card provided in the embodiment of this specification. The physical card can be a physical card in a physical red envelope combination, such as Figure 1 As shown, the physical card may carry a code image 104, which may be used to send or receive red envelope resources.

[0076] In the embodiment of this specification, the resources corresponding to the code image may be at least part of the resources corresponding to multiple physical red envelopes transferred to the intermediate account through resource parameters configured by the user.

[0077] The physical card may 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 the multiple physical red envelopes to the intermediate accounts corresponding to the multiple physical red envelopes. In actual applications, the code image used to send resources or receive resources can be the same code image or different code images, and this is not specifically limited here.

[0078] The physical card may also carry an area 106 for extracting verification information of resources corresponding to the physical card. The verification information may have at least a first state in which it can be read and a second state in which it cannot be read.

[0079] To ensure the security of the verification information, the verification information can be covered by a cover or set to be displayed under certain conditions. The verification information can include a string of characters or a verification code image that can be scanned and identified.

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

[0081] removing a covering on the physical card that is used to cover the verification information, so that the verification information is displayed;

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

[0083] The specific medium containing the verification information on the physical card is placed under a first preset environmental condition so that the verification information is displayed; the first preset environmental condition includes at least one of a preset temperature, a preset humidity, a preset light type, and a preset reading angle.

[0084] Among them, the covering may include a scratchable coating, an adhesive covering, etc. The user can remove the covering and read the verification information on the physical red envelope. The preset temperature, humidity, and light type can represent the temperature, humidity, and light in abnormal environments. For example, at -5 degrees Celsius, 50 degrees Celsius, etc., the user can put the physical red envelope in the refrigerator, or heat it at a high temperature so that the verification information can be displayed; for example, it can be displayed under an ultraviolet fluorescent lamp; for example, it can be displayed at a certain tilt angle, etc. When using specific media, the physical card can contain instructions for obtaining the verification information so that the user can obtain the verification information in the corresponding manner.

[0085] Similarly, the second state that cannot be read can be achieved in the following ways:

[0086] The physical card may include a covering for covering the verification information, wherein the covering makes the verification information hidden;

[0087] Alternatively, the second state that cannot be read can be specifically achieved in the following manner:

[0088] The physical card may include a specific medium carrying the verification information, so that the verification information is hidden under natural conditions or normal viewing angles.

[0089] Natural conditions can be understood as conditions in daily environments without the help of other tools. The normal viewing angle can be understood as the normal viewing angle of a physical red envelope, for example, the line of sight is perpendicular to the red envelope, or at an angle within a preset range. By adjusting the viewing angle, for example, the angle with the plane of the red envelope is less than or equal to a preset angle, such as 5 degrees, 10 degrees, etc., the hidden information can be seen. The hiding method of the verification information can be set according to actual needs, and then the verification information can be viewed according to the method corresponding to the actual setting of the hiding method. When the resources of the red envelope are to be claimed, the verification information can be in a hidden state, and the claiming user can use the corresponding method to obtain the verification information in order to claim the red envelope resources.

[0090] In practice, the physical card may also include an area for displaying a greeting. This area may be blank for the user to enter a greeting, or it may contain a greeting that is at least partially printed on the card. The specific content of the greeting may be determined by the type of red envelope. For example, a corresponding greeting may be set based on the intended use of the red envelope. The area for displaying the greeting may be located on the same side as the code image or on a different side.

[0091] It is understood that the code image in the embodiments of this specification may be a QR code, a 3D code, or other code image that can carry data information, and the specific form is not specifically limited here. The hidden verification information may be located below, above, or to either side of the code image, or on the other side of the card carrier, and the specific location is not specifically limited here.

[0092] In practical applications, physical cards can be made of paper, plastic, or other composite materials. Preset shapes can include quadrilaterals, polygons, circles, and other shapes. They can also be composite shapes composed of multiple basic shapes. They can also be customized according to user needs, for example, shapes resembling animals, plants, buildings, and other specific shapes.

[0093] To make the physical card in this example more similar to the traditional red envelope in the prior art, the physical red envelope set provided in this example may optionally include a red envelope outer shell; the red envelope outer shell is used to hold the physical card. The red envelope outer shell may also contain a blessing message.

[0094] The verification information used to extract resources from the red envelope can be directly loaded with the verification information on the physical card, or it can be information obtained based on the verification information on the red envelope. Assuming that the verification information is a string of preset digits, this string can be printed on the physical red envelope. Alternatively, information used to obtain this string, such as a password or other string, can be printed on the physical card. When extracting resources, the user can enter this password or other string in a designated application. The server can then send the corresponding verification information to the user terminal, and the user can then extract the resources based on the obtained verification information.

[0095] In practical applications, the specific content of the verification information can be set by the manufacturer or by the recharging user. For example, when recharging, the recharging page can include an area for setting verification information. The user can send this verification information to the server, and the server can establish a correspondence between the verification information and the code image. The physical red envelope can also include a method, password, or identifier for obtaining this verification information. When extracting resources, the extracting user can obtain the verification information from the server based on the method, password, or identifier used to obtain the verification information and then extract the red envelope resources.

[0096] like Figure 1 As shown, the physical card may also include red envelope identification information 108, such as a number, for distinguishing it from other physical red envelopes. The identification information may be character information such as numbers, letters, etc.

[0097] Figure 2 This is a schematic diagram of an application scenario of a resource transfer method in an embodiment of this specification. Figure 2As shown, the solution may include a first terminal 1, a server 2, physical red envelopes 3, and a second terminal 4. The first terminal 1 may send a resource recharge trigger instruction for recharging multiple physical red envelopes 3 to the server 2. Based on the resource recharge trigger instruction, the server 2 may send a resource recharge page to the first terminal 1. The user may configure recharge resource parameters on this page, such as the number of recharged red envelopes, the number of recharged resources, and so on. The server 2 may obtain the configured recharge resource parameters sent via the page and transfer the total amount of resources corresponding to the multiple physical red envelopes 3 from the user account of the first terminal to the intermediate account. When receiving the red envelope, the second terminal 4 may scan the code image on the physical red envelope to obtain the corresponding resources from the intermediate account.

[0098] Next, a resource transfer method provided in an embodiment of the specification will be described in detail with reference to the accompanying drawings:

[0099] Figure 3 This is a flow chart of a resource transfer method provided by an embodiment of this specification. From a program perspective, the execution subject of the process can be a program installed on an application server or an application client.

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

[0101] Step 302: Obtain 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 envelopes have a code image, and the code image is used to collect the resources corresponding to the physical red envelopes.

[0102] Physical red envelopes can be as above Figure 1 The physical card shown may have a code image on it, and the user can scan the code image through the terminal to claim the corresponding resource. The resource recharge trigger instruction 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 code image or other identification information on the physical red envelope. Later, when claiming resources based on the code image, the available resources can be determined based on this correspondence.

[0103] Step 304: Based on the resource recharge trigger instruction, a resource recharge page is sent to the first terminal; the resource recharge page includes recharge resource parameters that can be configured by the user.

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

[0105] Step 306: Acquire the configured recharge resource parameters sent by the first terminal based on the resource recharge page.

[0106] Step 308: Determine the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters.

[0107] The total amount of resources may represent the total amount of resources required to recharge multiple red envelopes, such as the total recharge amount.

[0108] Step 310: Transferring the total resources corresponding to the total amount of resources from the first user account of the first terminal to the intermediate account.

[0109] The first user account can represent the user account logged in on the first terminal, or can also represent an account determined to provide the transferred resources, etc. The intermediate account can be an account that temporarily stores the recharged resources corresponding to the red envelope. The recharged resources can be temporarily stored in the intermediate account before the resources are claimed or within a preset time period after the recharge. When the resources are claimed, they can be transferred from the intermediate account to the recipient's account.

[0110] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted.

[0111] Figure 3 According to the method in the embodiment of this specification, by obtaining the resource recharge trigger instruction sent by the first terminal, the total amount of resources to be transferred corresponding to multiple physical red envelopes can be transferred to the intermediate account according to the recharge resource parameters configured by the user, thereby realizing the recharge of multiple physical red envelopes, that is, the user can complete the recharge of multiple physical red envelopes by configuring the resource parameters once, which can simplify the user operation.

[0112] In the embodiments of this specification, the physical red envelope may include a code image and a physical card carrier. The first terminal recharges the code image, and the second terminal scans the recharged code image to obtain the corresponding resources, thereby retaining the ritual sense of interpersonal communication while making gift giving and receiving more convenient, and improving the convenience of sending and receiving red envelopes between users.

[0113] In addition, the existing transfer methods generally require the account information of the withdrawer or the payee before the funds can be transferred. The method in the embodiments of this specification does not require the account information of the withdrawer or the payee. The funds transfer is undertaken through an intermediate account. The recharger or sender scans the code image on the physical red envelope to transfer the funds to the intermediate account. The withdrawer or the payee scans the code image to withdraw the funds from the intermediate account to his or her own account. This can simplify user operations and avoid problems caused by incorrect provision of the receiving account, providing a better user experience.

[0114] based on Figure 3 The present specification also provides some specific implementation plans of the method, which are described below.

[0115] In actual applications, the amount of the above-mentioned multiple physical red envelopes can be set by the user according to actual needs, and can also be set optionally according to actual needs. In the embodiment of this specification, the above-mentioned recharge resource parameters include red envelope quantity parameters representing the physical red envelopes being recharged, recharge method parameters, and recharge resource quantity parameters, etc.

[0116] Figure 4 This is a schematic diagram of a resource recharge page provided in the embodiment of this specification. Figure 4 As shown, the page may include an information area 402 for configuring the amount of recharged red envelopes, and an information area 404 for configuring the amount of recharged resources. This amount may include the total amount of resources required for multiple physical red envelopes or the amount of resources for a single red envelope. It may also include an information area 406 for configuring the red envelope recharge method. In actual 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 recharging with a fixed amount, recharging with a random amount, or recharging with a portion filled with a first amount and a portion filled with a second amount, etc. The specific recharge method can be set according to actual needs and is not specifically limited here. As an embodiment, if the user selects the random recharge method, area 404 may display an area for configuring the total amount of resources; if the user selects the fixed recharge method, area 404 may display an area for configuring the amount of resources for a single red envelope.

[0117] In actual applications, the resource recharge page can also include the need to set remark information. For example, the user can also set blessings or other remark information in this area, and the user who receives the resources can also obtain the blessings or configuration information after receiving the resources.

[0118] In the embodiment of this specification, after obtaining the recharge parameters configured by the user, the server can also determine the amount of resources 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 embodiment of this specification can also include:

[0119] Determine the target recharge methods corresponding to the multiple physical red envelopes according to the configured recharge method parameters;

[0120] According to the target recharge method and the configured recharge resource quantity parameter, the target resource quantity corresponding to each of the multiple physical red envelopes is determined.

[0121] The server may also establish a correspondence between the target resource data and each physical red envelope, so as to subsequently determine the resources that the receiving user can claim based on the correspondence. The correspondence may include a correspondence between a code image, code value, or other identifier on the physical red envelope and the corresponding resource.

[0122] For a fixed amount recharge method, the user can configure the resource quantity corresponding to each physical red envelope. For multiple physical red envelopes, the resource quantity can be configured to be the same, or the resource quantity can be configured separately, etc. Optionally, in the embodiments of this specification, the target recharge method may include a first recharge method indicating that each physical red envelope corresponds to a fixed amount configured by the user; the recharge resource quantity parameter may include a first resource quantity configured by the user corresponding to each physical red envelope; the above-mentioned determination of the target resource quantity corresponding to each physical red envelope in the multiple physical red envelopes based on the target recharge method and the configured recharge resource quantity parameter may specifically include:

[0123] According to the first recharge method and the first resource quantity, the target resource quantity corresponding to each physical red envelope in the multiple physical red envelopes is determined.

[0124] For the method of recharging with a random amount, the user can configure the total amount of resources corresponding to multiple entity red envelopes, and the server can determine the amount of resources corresponding to each entity red envelope according to a random algorithm. Optionally, the target recharge method described in the embodiment of this specification may include a second recharge method that randomly determines the amount of resources corresponding to each entity based on the configured total amount of resources; the recharge resource quantity parameter may include the configured total amount of resources; the above-mentioned determination of the target amount of resources corresponding to each entity red envelope in the multiple entity red envelopes based on the target recharge method and the configured recharge resource quantity parameter may specifically include:

[0125] According to the second recharging method, a preset random filling algorithm is used based on the total resource quantity configured by the user to determine the target resource quantity corresponding to each of the multiple physical red envelopes.

[0126] In practical applications, the amount of resources corresponding to each physical red envelope can be determined based on configuration parameters provided by the recharging user. After the recharge is completed, the resources corresponding to each physical red envelope can be determined. Alternatively, the resources corresponding to each red envelope can be determined based on the red envelope collection process, and the specific amount of resources can be determined during the collection process. The preset random filling algorithm can be an existing red envelope random recharge algorithm, which will not be further described here.

[0127] In actual applications, a user can recharge multiple physical red envelopes through a terminal application in the first terminal, and the resource recharge page can be an application page in the terminal application. As an embodiment, the terminal application can include an operation control, and the first terminal can generate a resource recharge trigger instruction based on the user's operation of the operation control.

[0128] As an implementation method, the resource recharge trigger instruction may also be generated based on terminal scanning. Optionally, in the embodiment of this specification, the resource recharge trigger instruction sent by the first terminal may be obtained, specifically including:

[0129] Obtain a resource recharge trigger instruction sent by the first terminal based on scanning a code image on a preset physical red envelope.

[0130] Among them, the preset physical red envelope can be a physical red envelope among multiple physical red envelopes to be recharged by the user, such as the physical card in the above-mentioned physical red envelope combination, and the user can scan the code image on the physical red envelope through the first terminal. The code image can be the same code image as the code image for receiving the red envelope resource, or it can be a different code image, which is not specifically limited here. In the embodiment of this specification, the multiple physical red envelopes to be recharged can belong to the same red envelope combination, and the user can also recharge multiple physical red envelopes by scanning the code image in the red envelope combination. Optionally, the preset physical red envelope in the embodiment of this specification can be a physical red envelope among the multiple physical red envelopes; or, the preset physical red envelope is a physical red envelope in the red envelope combination to which the multiple physical red envelopes belong; one of the red envelope combinations includes multiple physical red envelopes with associated relationships.

[0131] Among them, a red envelope combination can include multiple physical red envelopes with associated relationships. Through the code image on a red envelope in the red envelope combination, at least some of the red envelopes in the red envelope combination can be recharged. To facilitate user operation, reduce the user's understanding and usage threshold, and reduce the processing of manufacturers or servers, as an implementation method, any red envelope in the red envelope combination can be used for recharging. The above-mentioned preset physical red envelope can be any physical red envelope in the red envelope combination. The server can pre-store the code value or red envelope identifier of each red envelope in the red envelope combination so that when the user scans the code to recharge, it can determine the physical red envelope to be recharged.

[0132] As an implementation method, the red envelope combination in the embodiment of this specification may also include at least one main entity red envelope and multiple sub-entity red envelopes; wherein, the above-mentioned multiple entity red envelopes to be recharged can be multiple sub-entity red envelopes in the red envelope combination; the above-mentioned preset entity red envelope for recharging multiple entity red envelopes can be the main entity red envelope, the code image on the preset entity red envelope can be the code image on the main entity red envelope, and the code image on the main entity red envelope is used to recharge the sub-entity red envelope; the code image on the sub-entity red envelope is used to collect resources corresponding to the sub-entity red envelope.

[0133] In practical applications, the main physical red envelope can be the first code image carrier in the above-mentioned physical red envelope combination. Specifically, the main physical red envelope can be the physical red envelope with the smallest or largest number in the red envelope combination. If the red envelope combination includes a cover red envelope, the main physical red envelope can also be the cover red envelope. The cover red envelope can be understood as a card containing relevant information on how to top up and claim the red envelope resources. This cover red envelope can be used by the top-up party and may not be provided to the recipient.

[0134] If the user recharges at least part of the red envelopes in the red envelope combination, the server can also select a preset number of red envelopes from the red envelope combination as the red envelopes to be recharged. Optionally, the preset physical red envelope in the embodiment of this specification can be a physical red envelope in the red envelope combination to which the multiple physical red envelopes belong; a red envelope combination can include multiple physical red envelopes with associated relationships; the recharge resource parameter can include a parameter indicating the number of physical red envelopes to be recharged; the method in the embodiment of this specification can also include:

[0135] Determining, based on the code identifier of the code image on the preset physical red envelope, a red envelope identifier set corresponding to the red envelope combination to which the preset physical red envelope belongs; a red envelope identifier in the red envelope identifier set corresponds to a physical red envelope in the red envelope combination;

[0136] A red envelope identifier of the configured red envelope quantity is selected from the red envelope identifier set; wherein the selected red envelope identifier is used to represent the physical red envelope that is recharged.

[0137] The server can store a set of red envelope identifiers representing red envelope combinations. The red envelope identifiers can be numbers, code values, and other information. After the server obtains the number of recharge red envelopes configured by the user, it can select the identifiers of that number from the combination to represent the red envelopes to be recharged. In actual applications, users can recharge all the red envelopes in the red envelope combination at once, or recharge only part of them. If the user has previously recharged some of the red envelopes, the server can also mark the recharged or unrecharged red envelope identifiers, and the red envelope to be recharged can be selected from the unrecharged red envelope identifiers.

[0138] In order to facilitate users to understand the situation of recharged red envelopes and distribute recharged red envelopes, the physical red envelope in the embodiment of this specification may also include identification information of the red envelope identification; the method in the embodiment of this specification may also include: sending identification information of the red envelope identification used to represent the recharged physical red envelope to the first terminal, so that the first terminal displays the identification information of the recharged physical red envelope.

[0139] Figure 5 This is a schematic diagram of a recharge result page provided in an embodiment of this specification. Figure 5As shown, the page may include identification information 502 of the recharged physical red envelopes, such as "number NO.ABC-001 to NO.ABC.050". Users can determine the physical red envelopes that have been recharged based on this information and avoid sending out unrecharged red envelopes.

[0140] As an implementation method, in the embodiments of this specification, users can also specify a red envelope to be recharged. The resource recharge page may further include an area for entering identification information of the recharged red envelope; the configured recharge resource parameters may include the identification information of the physical red envelope to be recharged, as configured by the user. The user may configure the identification information of the red envelope to be recharged in this area, such as the serial number, which may be sequential or non-sequential. The server may then recharge the corresponding physical red envelope based on the user-configured identification information.

[0141] When selecting the red envelope to be recharged in the embodiment of this specification, the server can select the red envelope to be recharged randomly or in a certain order, such as the order of the red envelope numbers; the server can also determine the red envelope to be recharged based on the identification information of the recharge red envelope configured by the user.

[0142] To ensure resource security, the physical red envelope in the embodiment of this specification may also include verification information; the verification information can be used to extract the resources corresponding to the physical red envelope, which may have at least a first state that can be read and a second state that cannot be read.

[0143] Figure 6 This is a schematic diagram of a resource recharge page provided in an embodiment of this specification, such as Figure 6 As shown, the resource recharge page may include information 602 indicating the method for the recipient to receive the resources corresponding to the physical red envelope, wherein the receiving method may include at least a first receiving method for 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 receiving method for 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 user can select one of the receiving methods. In actual applications, a receiving method may also be displayed on the resource recharge page. If the user does not select this receiving method, it means that another receiving method needs to be used. For example, assuming that the first receiving method indicating that the recipient needs to input verification information is displayed on the resource recharge page, such as Figure 6 It shows "The other party needs to enter the password after scanning the code to receive the red envelope". If the user chooses this method, it means that the recipient needs to enter the verification information before receiving the red envelope resources; if the user does not choose this method, it can mean that the recipient does not need to enter the verification information, or it can mean that the recipient can receive the red envelope resources by scanning the code.

[0144] In the embodiments of this specification, after the user configures the claim method on the recharge page, the server may also establish a correspondence between the claim method, the code image, and the configured resource quantity parameter, so that when the recipient subsequently claims the red envelope resources, the resources corresponding to the configured resource quantity parameter are sent to the withdrawing party according to the claim method configured by the recharger. Optionally, the method in the embodiments of this specification may further include: obtaining the configured claim method information sent by the first terminal based on the resource recharge page;

[0145] A correspondence between the receiving method corresponding to the configured receiving method information and the configured recharge resource parameters is established.

[0146] It is understandable that the above Figure 4 as well as Figure 6 The page diagram provided is only for illustrating the examples given in the embodiments of this specification. In actual applications, specific page content can be displayed according to actual needs. For example, when the random filling method is used, the information area for configuring the identification information of the recharge red envelope can also be displayed. When the fixed amount filling method is used, the information area for configuring the number of recharge red envelopes can also be displayed, and so on.

[0147] Considering that in actual applications, users may send or receive physical red envelopes multiple times, and since each time may represent a social etiquette, users need to record it. Usually, users may need to use a physical notebook or electronic memo to record each red envelope receipt or sending situation. The problem that users may face is a large amount of manual accounting and reconciliation costs and the risk of data loss. To improve user convenience, the server in the embodiment of this specification can also generate record information corresponding to the physical red envelope for users to view. Optionally, the method in the embodiment of this specification can also include:

[0148] Get resource transfer record query instructions;

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

[0150] The record information is sent to the first terminal so that the first terminal displays a resource transfer record page.

[0151] The resource transfer record query instruction may specifically include:

[0152] Obtaining a resource transfer record query instruction generated by the first terminal based on a first operation of the user; the first operation includes an operation on a display page presented after the user scans a code image on a physical red envelope on the first terminal;

[0153] or,

[0154] Obtain a resource transfer record query instruction generated by the first terminal based on a search keyword provided by a user; the search keyword is related to the physical red envelope.

[0155] In the embodiment of this specification, after the recharge is completed, the terminal may display a page indicating that the recharge is completed, and the page may include a control for querying records, such as Figure 5 "View My Transaction Records" is shown. In actual applications, after a resource is claimed or after scanning the code image on a claimed physical red envelope, the terminal can also display a page indicating that the resource has been claimed. This page can also include controls for querying the record. When the user operates the above controls, the terminal can send a resource transfer record query instruction to the server, and the server can query the corresponding record information and feedback to the terminal.

[0156] In actual applications, users can receive or recharge physical red envelopes through the terminal application or mini-program in the terminal. The terminal application or mini-program may include a search area for searching records, and users can enter keywords related to physical red envelopes to view record information. For example, a user enters "cashless red envelope" in the search box of the terminal application to enter the corresponding mini-program. The mini-program page may include a control for user query records, and the user can view record information by operating the control. It can be understood that the above is only an example of the method provided in the embodiments of this specification for a clearer description. In actual applications, a specific search method can be set according to actual conditions, and no specific limitation is made here.

[0157] Figure 7 This is a schematic diagram of a resource transfer record page provided in an embodiment of this specification. Figure 7 As shown, the record page may include several resource transfer records 702. This information may include information about the sender or recipient, the specific resource quantity, and the time. The page may also include a control 704 that connects to the address for purchasing physical red envelopes, allowing users to easily purchase the physical red envelopes they need.

[0158] Based on the same idea, the example in this specification also provides a resource transfer method for receiving resources corresponding to the resource transfer method for recharging resources.

[0159] Figure 8This is a flow chart of a resource transfer method provided by an embodiment of this specification. From a program perspective, the execution subject of the process can be a program installed on an application server or an application client.

[0160] like Figure 8 As shown, the method may include:

[0161] Step 802: Obtain a resource claim trigger instruction sent by the second terminal based on scanning the code image on the physical red envelope.

[0162] Physical red envelopes can include: Figure 1 The physical red envelope shown after being recharged according to the above method may include a code image.

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

[0164] The resource collection trigger page may include resource quantity information, sender information, and may also include remarks provided by the sender, such as greetings.

[0165] Step 806: Obtain the resource claiming request sent by the second terminal based on the resource claiming triggering page.

[0166] The resource collection trigger page may include a control for collecting resources, such as a "collect now" control. When the user operates the control, the second terminal may send a resource collection request to the server.

[0167] Step 808: Based on the resource claiming 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 may include the resources transferred to the intermediate account by the above resource transfer method.

[0168] The code image may be the code image in a plurality of physical red envelopes recharged according to the above-mentioned resource transfer method; the second user account may be the user account logged in the second terminal, or the user account from which the user withdraws resources.

[0169] To ensure resource security, the physical red envelope in the embodiments of this specification may include verification information; the verification information is used to extract the resource corresponding to the physical red envelope, and has at least a first state in which it can be read and a second state in which it cannot be read. The method in the embodiments of this specification may also include:

[0170] Obtaining information to be verified sent by the second terminal based on the resource claim trigger page;

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

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

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

[0174] The verification information may have at least a first state in which it can be read and a second state in which it cannot be read. It may also be understood as hidden verification information, for example, it may be covered, or it may only be seen and read under certain lighting conditions, temperature conditions or viewing angles, and may not be read under normal conditions.

[0175] The verification information can be a string displayed on the physical red envelope, or it can be an image, such as a code image. Users can scan the code to obtain the corresponding verification information in the form of a string, or they can 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.

[0176] Figure 9 This is a schematic diagram of a resource collection trigger page provided in an embodiment of this specification, such as Figure 9 As shown, the page may include a verification information area 902 for entering the verification information. To facilitate the user to enter the corresponding verification information, the page may also include prompt information indicating how to obtain the verification information, such as "Please scratch off the coating and enter the password", etc. The specific content can be set according to actual needs and is not specifically limited here.

[0177] After the second terminal user completes filling in the verification information, the second terminal may send the resource claiming information in the resource claiming triggering page to the server, which may include the information to be verified filled in by the user.

[0178] The server can save the correspondence between the code image on the physical red envelope and the verification information carried on the physical red envelope. If the information to be verified filled in by the user is consistent with the verification information carried on the physical red envelope, it can be said that the information to be verified provided by the user is consistent with the verification information stored in the server, which can be said to have been verified, and the second terminal can collect the resources in the physical red envelope.

[0179] In the embodiments of this specification, when a user claims a resource in a physical red envelope, they can do so by entering verification information, ensuring the security of the resource. Furthermore, this verification information can be included in the physical red envelope, ensuring that only the user who owns the physical red envelope can claim the resource, effectively preventing the resource from being claimed by other users.

[0180] As described above regarding the embodiment of resource collection for resource sending, the resource sender can set whether the resource recipient needs to enter verification information when collecting the resource. During the collection process, the server can also determine the collection method corresponding to the code image. If the collection method is a collection method that requires verification information to be entered, the collection trigger page sent to the second terminal can include a verification information area for filling in the verification information; if the collection method is a collection method that does not require verification information to be entered, the collection trigger page sent to the second terminal may not include a verification information area for filling in the verification information. Optionally, the embodiments of this specification may also include:

[0181] Determining a resource claiming method corresponding to the code image based on the resource claiming trigger instruction;

[0182] The sending of the resource claim trigger page to the second terminal may specifically include:

[0183] If the resource collection method is a collection method that requires the recipient to enter the verification information on the physical red envelope to extract the resources in the code image, a resource collection trigger page containing a verification information area for providing verification information is sent to the second terminal.

[0184] In actual applications, the resources in the physical red envelope can only be claimed after it is recharged. Optionally, the method in the embodiment of this specification may further include:

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

[0186] The sending of the resource claim trigger page to the second terminal specifically includes:

[0187] If the code image is in the second state of having been recharged, a resource claim trigger page is sent to the first terminal.

[0188] If the code image is in the first state where it has not been recharged, a resource recharge page can be sent to the second terminal, or a page containing a prompt indicating that it has not been recharged can be sent to the second terminal. In actual applications, if the physical red envelope has been claimed, a page containing a prompt indicating that it has been claimed can also be sent to the second terminal. In actual applications, the page can also include a control for viewing the record of the claimed physical red envelope resources, so that the user can view the record information of the resources of the physical red envelopes of the same type that they have claimed or sent.

[0189] Similar to the resource transfer method for resource transmission described above, the second terminal user can also view his or her own resource records. Optionally, the method provided in the embodiment of this specification may further include:

[0190] Obtaining a resource transfer record query instruction sent by the second terminal;

[0191] Based on the query instruction, obtaining record information of a plurality of resource transfer records generated by scanning code images on a plurality of physical red envelopes; the record information includes records of the second terminal sending resources via the code images on the physical red envelopes and / or records of the second terminal receiving resources via the code images on the physical red envelopes;

[0192] The record information is sent to the second terminal so that the second terminal displays a resource transfer record page.

[0193] In actual applications, after the resource transfer is completed, a page indicating the resource transfer results may be sent to the second terminal. This page may include information about the resource quantity, the user account that transferred the resource, and so on. It may also include a control for viewing the resource transaction records generated in the form of physical red envelopes. The resource transfer record query instruction may be generated based on this control. Optionally, the method in the embodiment of this specification may further include:

[0194] Generate a resource claim result page; the resource claim result page includes a query control for querying records of resource transfer services based on physical red envelopes in which the second terminal has participated;

[0195] Sending the resource claim result page to the second terminal;

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

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

[0198] In actual applications, records can also be viewed in other ways, such as by searching for keywords in a terminal application, or by entering a record page through a preset path.

[0199] Based on the same idea, the present specification also provides the above Figure 3 The resource transfer method shown corresponds to the device. Figure 10 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this specification. Figure 10 As shown, the device may include:

[0200] A recharge instruction acquisition module 1002 is configured to acquire a resource recharge trigger instruction sent by the first terminal; the resource recharge trigger instruction is configured to transfer recharge resources corresponding to multiple physical red envelopes to intermediate accounts corresponding to the multiple physical red envelopes; the physical red envelopes have a code image on them, and the code image is configured to claim the resources corresponding to the physical red envelopes;

[0201] A page sending module 1004 is configured to send a resource recharge page to the first terminal based on the resource recharge trigger instruction; the resource recharge page includes recharge resource parameters that can be configured by the user;

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

[0203] The resource determination module 1008 is configured to determine the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters;

[0204] The resource transfer module 1010 is configured to transfer the total resources corresponding to the total amount of resources from the first user account of the first terminal to the intermediate account.

[0205] Based on the same idea, the present specification also provides the above Figure 8 The resource transfer method shown corresponds to the device. Figure 11 This is a schematic diagram of the structure of a resource transfer device provided in an embodiment of this specification. Figure 11 As shown, the device may include:

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

[0207] A page sending module 1104 is configured to send a resource claim triggering page to the second terminal based on the resource claim triggering instruction;

[0208] A request obtaining module 1106 is configured to obtain a resource claim request sent by the second terminal based on the resource claim triggering page;

[0209] The resource transfer module 1108 is configured 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 claim request; the resources include the resources transferred to the intermediate account according to the above method.

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

[0211] at least one processor 1210; and,

[0212] a memory 1230 communicatively connected to the at least one processor;

[0213] Among them, corresponding to Figure 3 In the resource transfer method, 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:

[0214] Obtaining a resource recharge trigger instruction sent by the first terminal; the resource recharge trigger instruction is used to transfer recharge resources corresponding to the multiple physical red envelopes to the intermediate accounts corresponding to the multiple physical red envelopes; the physical red envelopes have a code image, and the code image is used to collect the resources corresponding to the physical red envelopes;

[0215] Based on the resource recharge trigger instruction, sending a resource recharge page to the first terminal; the resource recharge page includes recharge resource parameters that can be configured by the user;

[0216] Obtaining configured recharge resource parameters sent by the first terminal based on the resource recharge page;

[0217] Determining the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters;

[0218] The total resources corresponding to the total amount of resources are transferred from the first user account of the first terminal to the intermediate account.

[0219] Among them, corresponding to Figure 8 In the resource transfer method, 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:

[0220] Obtaining a resource claim trigger instruction sent by the second terminal based on scanning a code image on the physical red envelope;

[0221] Based on the resource claim trigger instruction, sending a resource claim trigger page to the second terminal;

[0222] Obtaining a resource claim request sent by the second terminal based on the resource claim trigger page;

[0223] Based on the resource claiming 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 the resources transferred to the intermediate account according to the above method.

[0224] Based on the same idea, the embodiments of this specification also provide a computer-readable medium corresponding to the above method. The computer-readable medium stores computer-readable instructions, which can be executed by a processor to implement the above resource transfer method.

[0225] The various embodiments in this specification are described in a progressive manner. The same or similar parts between the various embodiments can be referred to each other. Each embodiment focuses on the differences from other embodiments. Figure 12 As for the device shown, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0226] In the 1990s, technological improvements could be clearly distinguished as either hardware improvements (for example, improvements to circuit structures like diodes, transistors, and switches) or software improvements (improvements to process flows). However, with the advancement of technology, many process flow improvements can now be considered direct improvements to hardware circuit structures. Designers almost always create the corresponding hardware circuit structure by programming the improved process flow into the hardware circuit. Therefore, it cannot be said that a process flow improvement cannot be implemented using physical hardware modules. For example, a programmable logic device (PLD), such as a field programmable gate array (FPGA), is an integrated circuit whose logical function is determined by user programming. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to hire a chip manufacturer to design and manufacture a dedicated integrated circuit chip. Moreover, nowadays, instead of manually fabricating integrated circuit chips, this programming is mostly performed using software called a "logic compiler." This is similar to the software compilers used during program development. Before compilation, the original code must be written in a specific programming language, called a Hardware Description Language (HDL). There are many types of HDL, including ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art will also understand that simply by programming a method flow in one of these hardware description languages ​​and then programming it into an integrated circuit, a hardware circuit that implements the logic method flow can be easily obtained.

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

[0228] The systems, devices, modules, or units described in the above embodiments may be implemented by computer chips or entities, or by products having certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, 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.

[0229] For the convenience of description, the above devices are described as being divided into various units according to their functions. Of course, when implementing this application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

[0230] Those skilled in the art will appreciate that embodiments of the present invention may be provided as methods, systems, or computer program products. Thus, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0231] The present invention is described with reference to flowcharts and / or block diagrams of methods, devices (systems), and computer program products according to embodiments of the present invention. It should be understood that each process and / or block in the flowcharts and / or block diagrams, as well as combinations of processes and / or blocks in the flowcharts and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowcharts and / or block diagrams. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0232] These computer program instructions may also be stored in a computer readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 a process or multiple processes and / or boxes Figure 1 The function specified in one or more boxes.

[0233] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

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

[0235] Memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. Memory is an example of a computer-readable medium.

[0236] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can be implemented using any method or technology for information storage. 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 RAM (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 cassettes, magnetic disk storage or other magnetic storage devices, or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include transitory computer-readable media such as modulated data signals and carrier waves.

[0237] It should also be noted that the terms "comprises," "includes," or any other variations thereof are intended to encompass non-exclusive inclusion, such that a process, method, commodity, or apparatus that includes a series of elements includes not only those elements but also other elements not explicitly listed, or includes elements inherent to such process, method, commodity, or apparatus. In the absence of further limitations, an element defined by the phrase "comprises a ..." does not exclude the presence of other identical elements in the process, method, commodity, or apparatus that includes the element.

[0238] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Furthermore, the present application may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

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

[0240] The foregoing is merely an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application should all be included within the scope of the claims of the present application.

Claims

1. A method for resource transfer, the method being applied to a physical red envelope combination comprising a plurality of physical red envelopes having an associated relationship; the method comprising: Obtaining a resource recharge trigger instruction sent by the first terminal; The resource recharge trigger instruction is sent by the first terminal scanning a code image on a physical red envelope in the physical red envelope combination, or the resource recharge trigger instruction is sent by the first terminal scanning a code image on the cover, packaging, or instructions of the physical red envelope combination; 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 envelopes have a code image, and the code image is used to claim the resources corresponding to the physical red envelopes; Based on the resource recharge trigger instruction, sending a resource recharge page to the first terminal; the resource recharge page includes recharge resource parameters that can be configured by the user; Obtaining the configured recharge resource parameters sent by the first terminal based on the resource recharge page; the first terminal does not need to provide the recipient's information; Determining the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters; The total resources corresponding to the total amount of resources are transferred from the first user account of the first terminal to the intermediate account.

2. According to the method according to claim 1, the recharge resource parameters include a red envelope quantity parameter representing the physical red envelope being recharged, a recharge method parameter, and a recharge resource quantity parameter.

3. The method according to claim 2, further comprising: Determine the target recharge methods corresponding to the multiple physical red envelopes according to the configured recharge method parameters; According to the target recharge method and the configured recharge resource quantity parameter, the target resource quantity corresponding to each of the multiple physical red envelopes is determined.

4. The method according to claim 3, wherein the target recharge method includes a first recharge method indicating a fixed amount of money configured by the user corresponding to each physical red envelope; and the recharge resource quantity parameter includes a first resource quantity configured by the user corresponding to each physical red envelope; The determining, according to the target recharge method and the configured recharge resource quantity parameter, the target resource quantity corresponding to each of the multiple physical red envelopes specifically includes: According to the first recharge method and the first resource quantity, the target resource quantity corresponding to each physical red envelope in the multiple physical red envelopes is determined.

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

6. The method according to claim 1, wherein obtaining the resource recharge trigger instruction sent by the first terminal specifically comprises: Obtain a resource recharge trigger instruction sent by the first terminal based on scanning a code image on a preset physical red envelope.

7. The method according to claim 6, wherein the preset physical red envelope is one of the multiple physical red envelopes; Alternatively, the preset physical red envelope is a physical red envelope in the red envelope combination to which the multiple physical red envelopes belong; and one of the red envelope combinations includes multiple physical red envelopes with associated relationships.

8. The method according to claim 6, wherein the preset physical red envelope is a physical red envelope in a red envelope combination to which the multiple physical red envelopes belong; a red envelope combination includes multiple physical red envelopes with associated relationships; and the recharge resource parameter includes a parameter indicating the number of physical red envelopes to be recharged; The method further comprises: Determining, based on the code identifier of the code image on the preset physical red envelope, a red envelope identifier set corresponding to the red envelope combination to which the preset physical red envelope belongs; A red envelope identifier in the red envelope identifier set corresponds to a physical red envelope in the red envelope combination; A red envelope identifier of the configured red envelope quantity is selected from the red envelope identifier set; wherein the selected red envelope identifier is used to represent the physical red envelope that is recharged.

9. The method according to claim 1, wherein the physical red envelope further includes identification information of a red envelope identifier; The method further comprises: Identification information for indicating a red envelope identification of the recharged physical red envelope is sent to the first terminal so that the first terminal displays the identification information of the recharged physical red envelope.

10. The method according to claim 1, 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 state in which it can be read and a second state in which it cannot be read; The resource recharge page also includes information indicating a method for the recipient to receive the resources corresponding to the physical red envelope; the method includes at least a first method for 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 for 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 comprises: Obtaining the configured collection method information sent by the first terminal based on the resource recharge page; A correspondence between the receiving method corresponding to the configured receiving method information and the configured recharge resource parameters is established.

11. A method for resource transfer, comprising: Obtaining a resource claim trigger instruction sent by the second terminal based on scanning a code image on the physical red envelope; Based on the resource claim trigger instruction, sending a resource claim trigger page to the second terminal; Obtaining a resource claim request sent by the second terminal based on the resource claim trigger page; Based on the resource claiming 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 the resources transferred to the intermediate account according to the method of claim 1.

12. The method according to claim 11, 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 in which it can be read and a second state in which it cannot be read; The method further comprises: Obtaining information to be verified sent by the second terminal based on the resource claim trigger page; Determine whether the information to be verified is consistent with the verification information, and obtain a determination result; The 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, the resources corresponding to the code image in the intermediate account are transferred to the second user account of the second terminal.

13. The method according to claim 12, further comprising: Determining a resource claiming method corresponding to the code image based on the resource claiming trigger instruction; The sending of the resource claim trigger page to the second terminal specifically includes: If the resource collection method is a collection method that requires the recipient to enter the verification information on the physical red envelope to extract the resources in the code image, a resource collection trigger page containing a verification information area for providing verification information is sent to the second terminal.

14. The method according to claim 11, further comprising: Obtaining a resource transfer record query instruction sent by the second terminal; Based on the query instruction, obtaining record information of a plurality of resource transfer records generated by scanning code images on a plurality of physical red envelopes; the record information includes records of the second terminal sending resources via the code images on the physical red envelopes and / or records of the second terminal receiving resources via the code images on the physical red envelopes; The record information is sent to the second terminal so that the second terminal displays a resource transfer record page.

15. The method according to claim 14, further comprising: Generate a resource claim result page; the resource claim result page includes a query control for querying records of resource transfer services based on physical red envelopes in which the second terminal has participated; Sending the resource claim result page to the second terminal; The obtaining of the resource transfer record query instruction generated by the second terminal specifically includes: A resource transfer record query instruction generated by the second terminal based on the query control is obtained.

16. A physical red envelope combination, comprising: at least one first code image carrier, and a plurality of physical cards; 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 method of claim 1; Any one of the physical cards carries a second code image, and the second code image is used to claim at least part of the resources.

17. The physical red envelope combination according to claim 16, wherein the first code image carrier is a physical card among the plurality of physical cards; And / or, the first code image and the second code image are the same code image.

18. The physical red envelope combination according to claim 16, wherein the physical card further includes red envelope identification information.

19. The physical red envelope combination according to claim 16, wherein the physical card further includes verification information; the verification information is used to extract resources corresponding to the physical card, and has at least a first state in which it can be read and a second state in which it cannot be read; in, The first state that can be read is specifically achieved in the following manner: removing a covering on the physical card that is used to cover the verification information, so that the verification information is displayed; Alternatively, the first state in which the card can be read is specifically achieved by placing the specific medium carrying the verification information contained on the physical card under first preset environmental conditions so that the verification information is in a display state; the first preset environmental conditions include at least one of a preset temperature, a preset humidity, a preset light type, and a preset reading angle; Alternatively, the second state that cannot be read is specifically achieved in the following manner: the physical card includes a covering for covering the verification information, and the covering makes the verification information hidden; Alternatively, the second state that cannot be read is specifically achieved in the following manner: the physical card includes a specific medium carrying the verification information, so that the verification information is hidden under natural conditions or normal viewing angles.

20. A resource transfer device, the device being applied to a physical red envelope combination including a plurality of physical red envelopes having an associated relationship, the device comprising: A recharge instruction acquisition module, configured to acquire a resource recharge trigger instruction sent by the first terminal; The resource recharge trigger instruction is sent by the first terminal scanning a code image on a physical red envelope in the physical red envelope combination, or the resource recharge trigger instruction is sent by the first terminal scanning a code image on the cover, packaging, or instructions of the physical red envelope combination; 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 envelopes have a code image, and the code image is used to claim the resources corresponding to the physical red envelopes; 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 includes recharge resource parameters that can be configured by the user; a parameter acquisition module, configured to acquire the configured recharge resource parameters sent by the first terminal based on the resource recharge page; the first terminal does not need to provide information about the recipient; A resource determination module, configured to determine the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters; The resource transfer module is configured to transfer the total resources corresponding to the total amount of resources from the first user account of the first terminal to the intermediate account.

21. A device for resource transfer, comprising: A collection instruction acquisition module is used to obtain a resource collection trigger instruction sent by the second terminal based on scanning the code image on the physical red envelope; a page sending module, configured to send a resource claim triggering page to the second terminal based on the resource claim triggering instruction; a request obtaining module, configured to obtain a resource claim request sent by the second terminal based on the resource claim triggering 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 collection request; the resources include the resources transferred to the intermediate account according to the method of claim 1.

22. A resource transfer device, the device being applied to a physical red envelope combination including a plurality of physical red envelopes having an associated relationship, the 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, the instructions being executed by the at least one processor to enable the at least one processor to: Obtaining a resource recharge trigger instruction sent by a first terminal; the resource recharge trigger instruction is sent by the first terminal by scanning a code image on a physical red envelope in the physical red envelope combination, or the resource recharge trigger instruction is sent by the first terminal by scanning a code image on the cover, packaging, or instruction manual of the physical red envelope combination; 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 envelopes have a code image on them, and the code image is used to claim the resources corresponding to the physical red envelopes; Based on the resource recharge trigger instruction, sending a resource recharge page to the first terminal; the resource recharge page includes recharge resource parameters that can be configured by the user; Obtaining the configured recharge resource parameters sent by the first terminal based on the resource recharge page; the first terminal does not need to provide the recipient's information; Determining the total amount of resources to be transferred corresponding to the multiple physical red envelopes according to the configured recharge resource parameters; The total resources corresponding to the total amount of resources are transferred from the first user account of the first terminal to the intermediate account.

23. A device for resource transfer, 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, the instructions being executed by the at least one processor to enable the at least one processor to: Obtaining a resource claim trigger instruction sent by the second terminal based on scanning a code image on the physical red envelope; Based on the resource claim trigger instruction, sending a resource claim trigger page to the second terminal; Obtaining a resource claim request sent by the second terminal based on the resource claim trigger page; Based on the resource claiming 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 the resources transferred to the intermediate account according to the method of claim 1.

24. A computer-readable medium having computer-readable instructions stored thereon, wherein the computer-readable instructions can be executed by a processor to implement the resource transfer method according to any one of claims 1 to 10 or the resource transfer method according to any one of claims 11 to 15.

Images