A red envelope distribution and collection method, device, equipment and readable medium

Abstract

Embodiments of the present specification disclose a red envelope sending and receiving method, device, equipment and readable medium. The scheme comprises: a server acquires red envelope receiving operation information sent by a first application; in response to the red envelope receiving operation information, the server feeds back red envelope receiving information of the red envelope to the first application; the red envelope receiving information is used to indicate that a red envelope in a locked state is allocated for an account corresponding to the first application; the server acquires purchase information of the account for a commodity corresponding to the red envelope receiving information; based on the purchase information, the server feeds back red envelope unsealing information of the red envelope to the first application; the red envelope unsealing information is used to indicate that an amount of money corresponding to the red envelope has been sent to an account of the account.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a method, apparatus, device, and readable medium for issuing and receiving red envelopes. Background Technology

[0002] With the popularization of e-commerce, various forms of electronic red envelopes have emerged. Electronic red envelopes have not only replaced physical red envelopes to a certain extent as a carrier of festival customs, but can also be used in daily scenarios such as social interaction and consumption, bringing convenience to people's lives.

[0003] In practical applications, for marketing purposes, businesses and payment platforms may distribute a large number of red envelopes for users to claim. Given the current rampant distribution of large amounts of red envelopes by various entities, and the fact that each red envelope claim consumes server resources, this leads to excessive consumption of server resources. Summary of the Invention

[0004] This specification provides a method, apparatus, device, and readable medium for issuing and receiving red envelopes, in order to solve the problem of excessive server resource consumption in existing red envelope distribution methods.

[0005] To solve the above-mentioned technical problems, the embodiments in this specification are implemented as follows:

[0006] This specification provides an embodiment of a method for distributing red envelopes, comprising: obtaining red envelope receiving operation information sent by a first application; responding to the red envelope receiving operation information, sending back red envelope receiving information to the first application; the red envelope receiving information indicating that a red envelope in a locked state has been allocated to the account corresponding to the first application; obtaining purchase information of the account for the product corresponding to the red envelope receiving information; based on the purchase information, sending back red envelope unpacking information to the first application; the red envelope unpacking information indicating that the amount corresponding to the red envelope has been distributed to the account.

[0007] This specification provides a method for receiving red envelopes, applied to a first application, comprising: obtaining a red envelope receiving operation triggered by a user; sending red envelope receiving operation information to a server based on the red envelope receiving operation; obtaining red envelope receiving information fed back by the server; the red envelope receiving information indicating that a red envelope in a locked state has been allocated to the account corresponding to the first application; generating a payment code based on a payment option trigger operation for scanning by a cash register; obtaining red envelope unpacking information fed back by the server; the red envelope unpacking information indicating that the amount corresponding to the red envelope has been distributed to the account.

[0008] This specification provides an embodiment of a method for receiving red envelopes, applied to a first application, comprising: obtaining a red envelope receiving operation triggered by a user; sending red envelope receiving operation information to a server based on the red envelope receiving operation; obtaining red envelope receiving information fed back by the server; the red envelope receiving information indicating that a red envelope in a locked state has been allocated to the account corresponding to the first application; generating identification scanning information based on a scanning operation of the identification on the inner packaging of the product corresponding to the red envelope receiving information; sending the identification scanning information to the server; obtaining red envelope unpacking information fed back by the server based on the identification scanning information; the red envelope unpacking information indicating that the amount corresponding to the red envelope has been distributed to the account.

[0009] This specification provides an embodiment of a red envelope distribution device, comprising: a red envelope receiving operation information acquisition module, used to acquire red envelope receiving operation information sent by a first application; a red envelope receiving information sending module, used to respond to the red envelope receiving operation information and send back red envelope receiving information to the first application; the red envelope receiving information indicates that a red envelope in a locked state has been allocated to the account corresponding to the first application; a purchase information acquisition module, used to acquire purchase information of the account for the goods corresponding to the red envelope receiving information; and a red envelope unpacking information sending module, used to send back red envelope unpacking information to the first application based on the purchase information; the red envelope unpacking information indicates that the amount corresponding to the red envelope has been distributed to the account.

[0010] This specification provides a red envelope receiving device, applied to a first application, comprising: a red envelope receiving operation acquisition module for acquiring a red envelope receiving operation triggered by a user; an information sending module for sending red envelope receiving operation information to a server based on the red envelope receiving operation; a red envelope receiving information acquisition module for acquiring red envelope receiving information fed back by the server; the red envelope receiving information indicates that a red envelope in a locked state has been allocated to the account corresponding to the first application; a payment code generation module for generating a payment code based on a payment option trigger operation for scanning by a cash register; and a red envelope unpacking information acquisition module for acquiring red envelope unpacking information fed back by the server; the red envelope unpacking information indicates that the amount corresponding to the red envelope has been distributed to the account.

[0011] This specification provides an embodiment of a red envelope receiving device, applied to a first application, comprising: a red envelope receiving operation acquisition module, used to acquire a red envelope receiving operation triggered by a user; a first information sending module, used to send red envelope receiving operation information to a server based on the red envelope receiving operation; a red envelope receiving information acquisition module, used to acquire red envelope receiving information fed back by the server; the red envelope receiving information indicates that a red envelope in a locked state has been allocated to the account corresponding to the first application; an identifier scanning information generation module, used to generate identifier scanning information based on a scanning operation of the identifier on the inner packaging of the product corresponding to the red envelope receiving information; a second information sending module, used to send the identifier scanning information to the server; and a red envelope unsealing information acquisition module, used to acquire red envelope unsealing information fed back by the server based on the identifier scanning information; the red envelope unsealing information indicates that the amount corresponding to the red envelope has been distributed to the account of the user.

[0012] An application server provided in the embodiments of this specification includes:

[0013] At least one processor; and,

[0014] A memory communicatively connected to the at least one processor; wherein,

[0015] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0016] Retrieve the red envelope claiming operation information sent by the first application; respond to the red envelope claiming operation information, send back the red envelope claiming information to the first application; the red envelope claiming information indicates that a red envelope in a locked state has been allocated to the account corresponding to the first application; obtain the purchase information of the account for the product corresponding to the red envelope claiming information; based on the purchase information, send back the red envelope unpacking information to the first application; the red envelope unpacking information indicates that the amount corresponding to the red envelope has been sent to the account.

[0017] This specification provides an embodiment of a user terminal, comprising:

[0018] At least one processor; and,

[0019] A memory communicatively connected to the at least one processor; wherein,

[0020] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0021] The system retrieves a user-triggered red envelope claiming operation; based on the red envelope claiming operation, it sends red envelope claiming operation information to the server; it retrieves red envelope claiming information returned by the server; the red envelope claiming information indicates that a red envelope in a locked state has been allocated to the account corresponding to the first application; it generates a payment code based on a payment option trigger operation for scanning by the cashier device; it retrieves red envelope unpacking information returned by the server; the red envelope unpacking information indicates that the amount corresponding to the red envelope has been distributed to the account.

[0022] This specification provides an embodiment of a user terminal, comprising:

[0023] At least one processor; and,

[0024] A memory communicatively connected to the at least one processor; wherein,

[0025] The memory stores instructions executable by the at least one processor, which, when executed by the at least one processor, enable the at least one processor to:

[0026] The system retrieves a user-triggered red envelope claiming operation; based on the red envelope claiming operation, it sends red envelope claiming operation information to the server; it retrieves red envelope claiming information returned by the server; the red envelope claiming information indicates that a red envelope in a locked state has been allocated to the account corresponding to the first application; based on a scanning operation of the identifier on the inner packaging of the product corresponding to the red envelope claiming information, it generates identifier scanning information; it sends the identifier scanning information to the server; it retrieves red envelope unpacking information returned by the server based on the identifier scanning information; the red envelope unpacking information indicates that the amount corresponding to the red envelope has been distributed to the account.

[0027] This specification provides an embodiment of a computer-readable medium storing computer-readable instructions that can be executed by a processor to implement a method for issuing or receiving red envelopes.

[0028] One embodiment of this specification can achieve the following beneficial effects: After the server obtains the user's red envelope receiving operation information, it first allocates a locked red envelope to the user's account without performing a transfer operation. When the server subsequently receives the user's account's consumption information, it then transfers the locked red envelope to the user's account. Since the red envelope distribution process is split into two stages, namely locking the red envelope and actual transfer, and the actual transfer to the user's account is only performed under certain conditions, the problem of excessive server resource consumption in the red envelope distribution process is solved to a certain extent. Attached Figure Description

[0029] To more clearly illustrate the technical solutions in the embodiments or prior art of this specification, the drawings used in the description of the embodiments or prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0030] Figure 1 A flowchart illustrating a method for distributing red envelopes, provided as an embodiment of this specification;

[0031] Figure 2 This is a schematic diagram illustrating the page information displayed by a first application after a user receives a red envelope, as provided in an embodiment of this specification.

[0032] Figure 3 This is a schematic diagram illustrating the page information displayed by a first application after a red envelope is opened, as provided in an embodiment of this specification.

[0033] Figure 4 A flowchart illustrating a method for receiving red envelopes provided in an embodiment of this specification;

[0034] Figure 5 A flowchart illustrating another method for receiving red envelopes provided in the embodiments of this specification;

[0035] Figure 6 A schematic diagram illustrating a method for receiving and distributing red envelopes in a practical application scenario, as provided in the embodiments of this specification.

[0036] Figure 7 This is a flowchart illustrating a method for receiving and distributing red envelopes in a practical application scenario, as provided in the embodiments of this specification.

[0037] Figure 8 A flowchart illustrating another practical application scenario for receiving and distributing red envelopes, as provided in the embodiments of this specification.

[0038] Figure 9 A flowchart illustrating another practical application scenario for receiving and distributing red envelopes, as provided in the embodiments of this specification;

[0039] Figure 10 The embodiments provided in this specification correspond to Figure 1 A schematic diagram of a red envelope distributing device;

[0040] Figure 11 The embodiments provided in this specification correspond to Figure 4 A schematic diagram of a red envelope receiving device;

[0041] Figure 12The embodiments provided in this specification correspond to Figure 5 A schematic diagram of a red envelope receiving device;

[0042] Figure 13 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this specification. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of one or more embodiments of this specification.

[0044] In practical applications, for marketing purposes, businesses and payment platforms may distribute a large number of red envelopes (digital cash gifts) for users to claim. These red envelopes are typically small in value, such as 0.01 yuan. Given the current rampant distribution of these small red envelopes by various entities, and the fact that each user claiming a small red envelope consumes server resources, this leads to excessive consumption of server resources.

[0045] To address the shortcomings of existing technologies, this solution provides the following implementation: After receiving a user's red envelope claiming information, the server first allocates a locked red envelope to the user's account without performing a transfer operation. Only after receiving subsequent consumption information from the user's account is the locked red envelope transferred to the user's account. By splitting the red envelope distribution process into two stages—locking the red envelope and the actual transfer—and only performing the actual transfer to the user's account under certain conditions, the problem of excessive server resource consumption during the red envelope distribution process is solved to some extent.

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

[0047] Figure 1 This is a flowchart illustrating a method for distributing red envelopes, as provided in an embodiment of this specification. From a programming perspective, the entity executing the process can be a program hosted on an application server.

[0048] The server described in this specification is from a functional perspective. In actual application, the server involved in the embodiments of this specification may include one or more groups of physical devices, and each group of physical devices may be used to implement different functions.

[0049] like Figure 1 As shown, the process may include the following steps:

[0050] Step 102: Obtain the red envelope receiving operation information sent by the first application.

[0051] The first application refers to the client corresponding to the application server. For example, if the first application is a payment application, then the application server is the payment application server corresponding to the payment application; if the first application is a social application, then the application server is the social application server corresponding to the social application.

[0052] Typically, the first application can be installed on a user terminal. The user terminal may include mobile terminals such as smartphones and tablets. When a user uses the first application installed on the user terminal, they can perform a red envelope claiming operation through the first application. In response to the user's red envelope claiming operation, the first application generates red envelope claiming operation information and sends the red envelope claiming operation information to the application server.

[0053] In the embodiments of this specification, the specific form of the red envelope may include electronic red envelopes, electronic vouchers, electronic coupons, etc. In this case, locking the red envelope may refer to storing the correspondence between user accounts and electronic red envelopes, electronic vouchers, electronic coupons, etc. in the platform server; opening the red envelope may refer to distributing the electronic red envelopes, electronic vouchers, electronic coupons, etc. to the user's account for the user's use.

[0054] In optional scenarios, the specific form of the red envelope may also include cash red envelopes, physical gift packages, etc. This application does not limit the specific form of the red envelope. In this case, locking the red envelope may refer to storing the correspondence between user identifiers and cash red envelopes, physical gift packages, etc., in the platform server; opening the red envelope may refer to delivering the cash red envelope, physical gift package, etc., to the user for the user's use.

[0055] In practical applications, the specific actions a user takes to claim a red envelope through the first application will result in different red envelope claiming information.

[0056] In an optional embodiment, a user can scan the barcode information corresponding to a product using a first application to perform a red envelope claim operation. The barcode information may include one-dimensional or two-dimensional barcode information (also known as a QR code). The barcode information can be located on the product's outer packaging, promotional posters, or direct mail magazine advertising (DM advertising), etc. This application does not specifically limit the carrier of the barcode information. In this embodiment, the platform server can pre-store the mapping relationship between barcode information and page information or link address information of the page containing red envelope claim information. Therefore, when the platform server obtains the barcode information, it can return the red envelope claim information corresponding to the obtained barcode information to the first application.

[0057] For example, in some specific embodiments, a user can perform a red envelope claim operation by scanning the barcode information on the outer packaging of a product using a first application. Specifically, the first application may call the information collection module of the user terminal to collect the barcode information on the outer packaging of the product. The acquisition of the red envelope claim operation information sent by the first application may specifically include: acquiring the barcode information of the outer packaging of the product sent by the first application; the barcode corresponding to the barcode information is used for scanning by the scanning device of the cashier system when settling the payment for the product.

[0058] The barcode information mentioned above refers to the product barcode located on the outer packaging of the product. The outer packaging can be anything a user can see before purchasing and using the product. Product barcode encoding follows the principle of uniqueness to ensure that product barcodes are not repeated worldwide; that is, one product item can only have one code, or one code can only identify one type of product item. Different specifications, packaging, varieties, prices, and colors of products can only use different product codes.

[0059] EAN product barcodes, also known as universal product barcodes, are developed by the International Article Numbering Association (IEA) and are used worldwide, making them the most widely used product barcode internationally. EAN product barcodes come in two versions: EAN-13 (standard version) and EAN-8 (shortened version). The EAN-13 universal product barcode typically consists of a prefix, manufacturer code, product code, and check digit. The prefix code identifies the country or region, and the authority to assign this code rests with the IEA. For example, 00-09 represents the United States and Canada, 45 and 49 represent Japan, 69 represents mainland China, 471 represents Taiwan, and 489 represents Hong Kong. The manufacturer code is assigned by the respective national or regional article numbering organization. The product code identifies the product itself, and the authority to assign this code rests with the product manufacturer, who decides which Arabic numerals to use as product codes for which products, according to established rules. Finally, a check digit verifies the correctness of the first 12 digits of the product barcode.

[0060] The product barcode can be used for scanning by a first scanning device during checkout. In embodiments of this specification, the first scanning device may include a barcode scanning device used in the POS system, such as a barcode scanner.

[0061] In this specification, barcode, or product barcode, refers to the barcode itself located on the product packaging. Barcode information, or product barcode information, refers to the string information parsed from the product barcode, such as "6902890884910".

[0062] In the embodiments of this specification, the barcode information of the outer packaging of the product sent by the first application can specifically be: a product barcode image captured by the user terminal, from which the application server parses the corresponding barcode information; or, barcode information obtained by the user terminal based on the captured product barcode image. That is, the barcode information of the outer packaging of the product sent by the first application can be the barcode information itself, or it can be other information containing barcode information, such as product barcode image information. The process of parsing the product barcode information from the product barcode image can be performed by the first application or by the application server.

[0063] In practical applications, the first application scans the barcode information on the outer packaging of the product. This can be done by directly scanning the barcode information on the physical product, or by scanning an image containing the barcode information of the physical product.

[0064] In an optional embodiment, a user can claim a red envelope by clicking a preset control or preset link on the page of the first application. Specifically, the red envelope claiming information may include the user's red envelope claiming operation information on the red envelope claiming page. The user can claim the red envelope through an activity link on the page. In this embodiment, the server can pre-store a mapping relationship between the preset control or preset link and the page information containing the red envelope claiming information. Therefore, when the platform server obtains the user's trigger operation information for the preset control or preset link, it can return the corresponding red envelope claiming information to the first application.

[0065] To make it more convenient for users to claim red envelopes, in some scenarios, users can claim red envelopes by taking a picture and recognizing the object. Specifically, the red envelope claiming operation information may include: the user's acquisition of image information of a product. Specifically, the user can use a first application to capture an image of a product and use image recognition technology to obtain the corresponding product information (i.e., identify the specific product from the image), and then send the obtained product information to the platform server. Optionally, the user can use the first application to capture an image of a product and send the image to the platform server, whereby the platform server uses image recognition technology to obtain the corresponding product information (i.e., identify the specific product from the image). In this embodiment, the platform server can pre-store a mapping relationship between product information and page information or link address information of a page containing red envelope claiming information. Therefore, when the platform server obtains product information, it can return the red envelope claiming information corresponding to the obtained product information to the first application.

[0066] Step 104: In response to the red envelope receiving operation information, send the red envelope receiving information to the first application; the red envelope receiving information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application.

[0067] After receiving the red envelope claiming operation information sent by the first application, the application server can allocate the target red envelope in a locked state to the account corresponding to the first application, and then send the red envelope claiming information of the target red envelope back to the first application.

[0068] In this embodiment of the specification, when the application server obtains the red envelope receiving operation information sent by the first application in step 102, the receiving operation information may carry the user's account information. Therefore, the application server allocates a target red envelope in a locked state to the account corresponding to the first application. Specifically, this may include allocating a target red envelope in a locked state to the account represented by the account information, based on the account information that may be carried in the receiving operation information.

[0069] In practical applications, feeding back the red envelope claiming information to the first application can specifically include: feeding back page information containing the red envelope claiming information to the first application, so that the first application can render the page based on the page information; or, feeding back the link address information of the page containing the red envelope claiming information to the first application, so that the first application can access the page containing the red envelope claiming information based on the link address information.

[0070] In the embodiments of this specification, the red envelope receiving information may include receiving result information for a target red envelope, and the receiving result information indicates that the target red envelope is in a locked state.

[0071] In an optional embodiment, responding to the red envelope claiming operation information, feeding back the red envelope claiming information to the first application may further include: responding to the red envelope claiming operation information, feeding back the red envelope pending claiming information to the first application; obtaining user claiming confirmation information for the red envelope sent by the first application; and responding to the claiming confirmation information, feeding back the red envelope claiming result information to the first application, wherein the claiming result information indicates that the red envelope is in a locked state.

[0072] Step 106: Obtain the purchase information of the account for the goods corresponding to the red envelope receiving information.

[0073] Specifically, the server can obtain the purchase information of the account for the goods corresponding to the red envelope receiving information from the first application or the POS device.

[0074] Optionally, obtaining the purchase information of the account for the goods corresponding to the red envelope receiving information may specifically include: obtaining the goods settlement information sent by the cash register; the goods settlement information includes the account information of the account and the goods information of the goods purchased by the account; and determining that the goods information of the goods purchased by the account includes the goods information of the goods corresponding to the red envelope receiving information.

[0075] Optionally, obtaining the purchase information of the account for the product corresponding to the red envelope redemption information may specifically include: obtaining identification scanning information sent by the first application; the identification scanning information is generated based on the scanning operation of the identification on the inner packaging of the product corresponding to the red envelope redemption information. Here, the identification on the inner packaging refers to the identification that the user cannot see or scan before purchasing and opening the outer packaging of the product. For example, if the product is bottled, the identification may be located inside the bottle cap. Similarly, if the product is bagged, the identification may be located inside the bag. Furthermore, if the product itself has a box that cannot be opened before purchase, the identification may be located inside that box. Therefore, if the user scans the identification on the inner packaging of the product, it indicates that the user has already purchased the product. Specifically, the identification may include a QR code.

[0076] Step 108: Based on the purchase information, send feedback to the first application regarding the opening information of the red envelope; the opening information indicates that the amount corresponding to the red envelope has been sent to the account of the user.

[0077] After the platform server obtains the purchase information of the product corresponding to the red envelope information for the account, it can determine whether there is a locked red envelope corresponding to the account and the product information. If there is, the locked red envelope is unsealed, that is, the amount corresponding to the locked red envelope is distributed to the account of the account.

[0078] In the embodiments of this specification, an account can be represented by account information, which can be information used to identify the account. For example, account information may include account ID, email address, mobile phone number, ID card number, etc. An account corresponds to a user account and has the function of fund transactions, which can be used for fund storage, expenditure, income, etc. In practical applications, fund transactions can be conducted between the user account and the account information.

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

[0080] Figure 1 The method described above involves the server, after receiving the user's red envelope claiming information, first allocating a locked red envelope to the user's account without performing a transfer operation. When the server subsequently receives the user's account's consumption information, it then transfers the locked red envelope to the user's account. By splitting the red envelope distribution process into two stages—locking the red envelope and the actual transfer—the actual transfer to the user's account is only performed under certain conditions. This approach, to some extent, solves the problem of excessive server resource consumption.

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

[0082] In an optional embodiment, after the platform server obtains the barcode information of the outer packaging of the product sent by the first application, it may further include: determining the red envelope information corresponding to the barcode information based on the barcode information; and then recording the account's red envelope claim information.

[0083] In another optional embodiment, after the platform server obtains the barcode information of the outer packaging of the product sent by the first application, it may further include: identifying the product information corresponding to the barcode information; determining the red envelope information corresponding to the product information based on the product information; and then recording the account's red envelope claiming information.

[0084] In the embodiments of this specification, the product barcode information can be a string, such as "6902890884910"; the product information can be product description information, such as "Mengniu Telunsu Pure Milk Slim Pack 250mL"; usually, the product barcode information and the product information are in one-to-one correspondence.

[0085] In practical applications, the platform server can pre-store the mapping relationship between various barcode information (or product information) and red envelope information. Thus, when the platform server receives or recognizes the barcode information (or product information corresponding to the barcode information) sent by the first application, it can determine the red envelope information corresponding to the account of the first application based on the mapping relationship and the barcode information (or product information).

[0086] Optionally, the platform server can pre-set various red envelope generation rules corresponding to barcode information (or product information). Thus, when the platform server receives or recognizes the barcode information (or product information corresponding to the barcode information) sent by the first application, it can determine the corresponding red envelope generation rules based on the barcode information (or product information), and then determine the red envelope information corresponding to the account of the first application.

[0087] In an optional embodiment, the page information received and displayed by the first application may include, for example: Figure 2 As shown. Figure 2 This is a schematic diagram of the page information displayed by the first application after a user receives a red envelope, as provided in the embodiments of this specification.

[0088] like Figure 2 The page information may include not only the red envelope receiving information 202, but may also include at least one of the following: the amount information corresponding to the red envelope 204, the red envelope opening time limit information 206, and the red envelope opening condition information 208.

[0089] like Figure 2 For example, the red envelope receiving information 202 is the message "Congratulations on locking the red envelope", which is used to inform the user that the locked red envelope has been received.

[0090] like Figure 2 The page displays the amount information 204 corresponding to the red envelope, allowing users to understand the specific amount of the red envelope before actually receiving it. As an example of the amount information 204, such as... Figure 2 The amount displayed is "XX yuan". Compared to the traditional method of sending red envelopes, where users need to open the envelope to know the amount, the solution based on the embodiments of this specification allows users to know the amount during the red envelope locking stage. This allows users to decide whether to continue with the subsequent red envelope opening operation, and also reduces the consumption of server resources to a certain extent.

[0091] The "red envelope unsealing time limit information 206" refers to the time limit for locking the red envelope and the user's account. If the server obtains purchase information for the product corresponding to the red envelope within the preset time limit, it will unseal the locked red envelope, that is, distribute the amount corresponding to the red envelope to the user's account. If the server does not obtain purchase information for the product corresponding to the red envelope within the preset time limit, it will unlock the red envelope. Figure 2 In this context, the red envelope opening time limit information 206 specifically refers to the information "Valid for opening within XX time period," for example, "Valid for opening within 24 hours." Optionally, corresponding to the red envelope opening time limit information 206, a countdown timer for the opening time limit can also be displayed on the page. Figure 2 (Not shown in the image).

[0092] The "red envelope opening condition information 208" refers to the conditions under which a user will open a locked red envelope. From the perspective of the first application, the red envelope opening conditions include: generating a payment code for scanning by the cashier to settle the payment for the goods corresponding to the red envelope redemption information; or, scanning the markings on the inner packaging of the goods corresponding to the red envelope redemption information. Figure 2 As shown, the user can be instructed on how to open the red envelope in text form, such as "XXX, go open it now." From the server's perspective, the conditions for opening the red envelope include: the server obtaining the user's account's purchase information for the product corresponding to the red envelope within a preset time period.

[0093] and Figure 2 Correspondingly, after the platform server sends the red envelope unpacking information to the first application in step 108, the first application can display the red envelope unpacking information to the user. For example... Figure 3 As shown, Figure 3 This is a schematic diagram of the page information displayed by the first application after the red envelope is unpacked, as provided in the embodiments of this specification.

[0094] like Figure 3 As shown, the message "Congratulations on opening the red envelope" (302) can be displayed. Additionally, the amount of the red envelope (304) can be displayed, along with a notification (306) to inform the user that the red envelope amount has been credited to their account.

[0095] exist Figure 2 and Figure 3 The examples provided here are merely illustrative of the embodiments described in this specification, illustrating the display of information regarding the receipt and opening of red envelopes in a first application. In practical applications, the content and format of the displayed information may not be limited to the examples above.

[0096] In an optional embodiment, after the platform server obtains the red envelope receiving operation information sent by the first application, it may further include: freezing the amount corresponding to the red envelope in the red envelope sending account to ensure that the red envelope in the locked state is valid. Here, the red envelope sending account refers to the source account of the red envelope amount. In practical applications, the red envelope sending account can be the account of a product manufacturer, a platform account, or a third-party account such as a supermarket, and can be set according to actual needs.

[0097] In an optional embodiment, after the platform server obtains the purchase information of the product corresponding to the red envelope receiving information for the account, it may further include: distributing the amount corresponding to the red envelope in the red envelope sending account to the account of the account.

[0098] It should be noted that, Figure 2 and Figure 3 This is just one specific example of a locking and opening scheme for electronic red envelopes; the implementation of this scheme is not limited to this. In practical applications, the specific implementation of other types of red envelopes can also be set according to actual needs.

[0099] The above describes a method for distributing red envelopes from the server's perspective. Based on this method, the process of distributing red envelopes is divided into two stages: receiving the locked red envelope and unlocking the locked red envelope. From the perspective of server resource consumption, since the actual transfer to the user's account is only executed after certain conditions are met (after the user actually makes a purchase), the consumption of server resources is reduced to some extent.

[0100] In addition, by allocating locked red envelopes to users before they actually make a purchase, the red envelope distribution process is revealed to users with minimal operational cost, increasing interaction between the red envelope distributor and the user, enhancing the user's sense of participation in the entire red envelope distribution process, and improving the user experience.

[0101] Furthermore, based on the solutions implemented in this specification, from the user's perspective, after the user performs the operation of receiving a red envelope, the server automatically records the correspondence between the user's account and the locked red envelope. Therefore, when the user actually makes a purchase, the server receives the user's purchase information from the POS device and can automatically determine and open the red envelope. In other words, although the red envelope distribution process is divided into two stages, the process of opening the red envelope (actual transfer) can be automatically executed by the server based on the received information, without requiring the user to actively trigger it. The entire red envelope distribution process does not increase the user's operational cost, resulting in a good user experience.

[0102] The following describes the solutions of the embodiments in this specification from the perspective of the client (i.e., the first application).

[0103] Figure 4 This is a flowchart illustrating a method for receiving red envelopes provided in an embodiment of this specification. From a programming perspective, the entity executing the process can be an application installed on the user's terminal.

[0104] like Figure 4 As shown, the process may include the following steps:

[0105] Step 402: Obtain the user-triggered red envelope claiming operation.

[0106] Optionally, obtaining the user-triggered red envelope claiming operation may specifically include: obtaining the user's barcode scanning operation on the outer packaging of the product corresponding to the red envelope claiming information; or, obtaining the user's red envelope claiming operation on the red envelope claiming page.

[0107] Step 404: Based on the red envelope receiving operation, send red envelope receiving operation information to the server.

[0108] Step 406: Obtain the red envelope claiming information fed back by the server; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application.

[0109] Step 408: Trigger an operation based on the payment option to generate a payment code for the cashier device to scan.

[0110] In practical applications, during the checkout process, the POS device can scan the barcode on the outer packaging of the purchased goods to obtain a list of product barcode information, i.e., the product settlement information. Furthermore, the POS device can scan the payment code, which may contain the user's account information. Then, the POS device can send the product settlement information corresponding to the payment code to the server; the product settlement information includes the product information of the item corresponding to the red envelope redemption information.

[0111] Once the server receives the payment code information and the product settlement information, if the product settlement information of the product purchased by the user's account contains the product information of the product corresponding to the red envelope redemption information, then the red envelope corresponding to the account that is in a locked state will be unsealed.

[0112] Step 410: Obtain the red packet unpacking information fed back by the server; the red packet unpacking information is used to indicate that the amount corresponding to the red packet has been sent to the account of the account.

[0113] Figure 5 This is a flowchart illustrating another method for receiving red envelopes provided in the embodiments of this specification. From a programming perspective, the entity executing the process can be an application installed on the user's terminal.

[0114] like Figure 5 As shown, the process may include the following steps:

[0115] Step 502: Obtain the user-triggered red envelope claiming operation.

[0116] Optionally, obtaining the user-triggered red envelope claiming operation may specifically include: obtaining the user's barcode scanning operation on the outer packaging of the product corresponding to the red envelope claiming information; or, obtaining the user's red envelope claiming operation on the red envelope claiming page.

[0117] Step 504: Based on the red envelope receiving operation, send red envelope receiving operation information to the server.

[0118] Step 506: Obtain the red envelope claiming information fed back by the server; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application.

[0119] Step 508: Based on the scanning operation of the identification on the inner packaging of the product corresponding to the red envelope redemption information, generate identification scanning information. Specifically, the identification may include a QR code.

[0120] Step 510: Send the identifier scanning information to the server.

[0121] Once the server receives the identifier scanning information sent by the first application, it can determine the product information corresponding to the identifier scanning information. If the account corresponding to the first application has a locked red envelope corresponding to the product information, then the locked red envelope corresponding to the account will be opened.

[0122] Step 512: Obtain the red packet unpacking information fed back by the server based on the identifier scanning information; the red packet unpacking information is used to indicate that the amount corresponding to the red packet has been sent to the account of the account.

[0123] According to the above explanation, such as Figure 6 As shown in the figure, this specification provides a scenario diagram illustrating a method for receiving and distributing red envelopes in a practical application scenario.

[0124] exist Figure 6 In this system, the platform server 602 can preset the correspondence between product 606 (product barcode 608) and red envelopes. When a user scans product barcode 608 using the client (first application) on user terminal 604 that corresponds to the platform server 602, the server can return a red envelope claim success message to user terminal 604, that is, a red envelope lock success message, and record the correspondence between the user account and the locked red envelope on the server.

[0125] Therefore, when the platform server 602 subsequently receives information from the cash register device 610 or the user terminal 604 indicating that the user account has purchased goods 606, it can unseal the locked red envelope, that is, transfer the amount corresponding to the locked red envelope to the user account.

[0126] It should be noted that, although Figure 6 The example shows scanning the barcode on a product as an entry point to claim a red envelope, but this is not the only practical application. For instance, the relevant page of the user's primary application can also be used as an entry point to claim the red envelope.

[0127] This specification also provides a flowchart illustrating a method for receiving and distributing red envelopes in a practical application scenario, as shown in the embodiments. Figure 7 As shown.

[0128] exist Figure 7 In step 702: The platform server pre-stores the mapping relationship between product barcode information and the page to be triggered and the red envelope contained in the page.

[0129] Step 704: The user scans the product barcode using the application on the user terminal that corresponds to the platform server.

[0130] Step 706: The user terminal sends barcode information to the platform server. In addition, the platform server can receive the user's account information simultaneously with the barcode information.

[0131] Step 708: After receiving the barcode information, the platform server determines the page corresponding to the received barcode information and the red envelope contained in the page based on the pre-stored mapping relationship between the barcode information and the page to be triggered and the red envelope contained in the page.

[0132] Step 710: The platform server sends the corresponding page to be triggered to the user terminal for the user terminal to display. Specifically, the page displays the red envelope information. The page to be triggered can be, for example, a mini-program page.

[0133] Step 712: Optionally, if step 710 sends information to the user terminal about a red envelope to be claimed, the user terminal can further obtain the user's claiming operation for the red envelope and determine the red envelope claimed by the user. If step 710 sends information to the user terminal about the result of claiming the red envelope, then step 712 does not need to be executed.

[0134] Step 714: The platform server records the correspondence between the received user account information and barcode information and the received red envelope. It should be noted that in the embodiments described in this specification, receiving a red envelope means that the user can see the red envelope, but cannot use it for payment yet. It can only be used for payment after the red envelope is opened.

[0135] In practical applications, if the platform server sends the red envelope claim result information to the user terminal, steps 710 and 714 can be executed simultaneously, or steps 714 can be executed first and then steps 710.

[0136] Step 716: Optionally, the user terminal may send a payment code display request to the platform server.

[0137] Step 718: Optionally, if step 716 is performed, the platform server may return a payment code to the user terminal.

[0138] Step 720: When a user purchases goods, the user's terminal can display a payment code to the cashier device.

[0139] Step 722: The POS device scans the product barcodes to record the purchased item list information and scans the payment code presented by the user terminal to obtain the payment code information. In practical applications, the first barcode scanner and the second barcode scanner can be the same or different.

[0140] It is understandable that the step of scanning the product barcode can be performed before or after the step of displaying the payment code on the user's terminal.

[0141] Step 724: The POS device sends the scanned product barcode information list (which may include product barcode information previously scanned by the user using the user terminal) and payment code information (e.g., user account information) to the platform server.

[0142] Step 726: The platform server determines whether the received list of product barcode information contains product barcode information previously scanned by the user's terminal. That is, it determines whether the platform server has recorded the locked red envelope corresponding to the product barcode information and user account information. If so, the locked red envelope is opened after settlement.

[0143] Step 728: The platform server sends payment deduction information to the user terminal.

[0144] Step 730: The platform server sends a message to the user terminal indicating that the red envelope has been successfully opened.

[0145] It is understandable that steps 728 and 730 can be executed simultaneously, or either one can be executed first.

[0146] This specification also provides a flowchart illustrating another practical application scenario for receiving and distributing red envelopes, such as... Figure 8 As shown.

[0147] exist Figure 8 In step 802: The platform server pre-generates the mapping relationship between the red envelope receiving operation information and the page to be triggered and the red envelope contained in the page, as well as the mapping relationship between product information (product barcode information) and red envelope.

[0148] Step 804: The user triggers the red envelope claiming operation for a specific product through any page of the application corresponding to the platform server on the user terminal.

[0149] Step 806: The user terminal sends a red envelope claiming operation message to the platform server. In addition, the platform server can receive the user's account information at the same time as receiving the red envelope claiming operation message.

[0150] Step 808: After receiving the red envelope claiming operation information, the platform server determines the page corresponding to the received barcode information and the red envelope contained in the page based on the pre-stored mapping relationship between barcode information, the page to be triggered, and the red envelope contained in the page; and can feed back the corresponding page to be triggered to the user terminal for the user terminal to display the page, specifically, display the red envelope information on the page. The page to be triggered can be, for example, a mini-program page.

[0151] Step 810: After receiving the user's red envelope claiming operation information, the platform server can determine the red envelope information corresponding to the user's account. Then, based on the pre-stored mapping relationship between product barcode information and red envelopes, it determines and records the correspondence between the received user account information, product barcode information, and the claimed red envelope. It should be noted that in the embodiments of this specification, claiming a red envelope means that the user can see the red envelope, but cannot yet use it for payment. It can only be used for payment after the red envelope is opened.

[0152] In practical applications, steps 808 and 810 can be executed simultaneously, or step 810 can be executed first and then step 808.

[0153] Step 812: Optionally, the user terminal may send a payment code display request to the platform server.

[0154] Step 814: Optionally, if step 812 is performed, the platform server may return a payment code to the user terminal.

[0155] Step 816: When a user purchases goods, the user's terminal can display a payment code to the cashier device.

[0156] Step 818: The POS device scans the product barcodes to record the purchased item list information and scans the payment code presented by the user terminal to obtain the payment code information. In practical applications, the first barcode scanner and the second barcode scanner can be the same or different.

[0157] It is understandable that the step of scanning the product barcode can be performed before or after the step of displaying the payment code on the user's terminal.

[0158] Step 820: The POS device sends the scanned product barcode information list (which may include product barcode information of products with pre-stored corresponding red envelopes) and payment code information (e.g., user account information) to the platform server.

[0159] Step 822: Based on the received list of product barcode information, the platform server determines whether it has recorded a locked red packet corresponding to the product barcode information and user account information. If so, the locked red packet is unsealed after settlement.

[0160] Step 824: The platform server sends payment deduction information to the user terminal.

[0161] Step 826: The platform server sends a message to the user terminal indicating that the red envelope has been successfully opened.

[0162] It is understandable that steps 824 and 826 can be executed simultaneously, or either one can be executed first.

[0163] This specification also provides a flowchart illustrating another practical application scenario for receiving and distributing red envelopes, such as... Figure 9 As shown.

[0164] exist Figure 9 In step 902: The platform server pre-stores the mapping relationship between product barcode information and the page to be triggered, as well as the red envelopes contained on the page; and correspondingly stores the identification information on the inner packaging of the product. In practical applications, the product barcode information and the identification information on the inner packaging of the product can have a one-to-one relationship. For example, for the same product (i.e., products with the same specifications, packaging, variety, color, etc.), there can be unified product barcode information and corresponding unified inner packaging identification information.

[0165] Step 904: The user scans the product barcode using the application on the user terminal that corresponds to the platform server.

[0166] Step 906: The user terminal sends barcode information to the platform server. In addition, the platform server can receive the user's account information simultaneously with the barcode information.

[0167] Step 908: After receiving the barcode information, the platform server determines the page corresponding to the received barcode information and the red envelope contained in the page based on the pre-stored mapping relationship between the barcode information and the page to be triggered and the red envelope contained in the page.

[0168] Step 910: The platform server sends the corresponding page to be triggered to the user terminal for the user terminal to display. Specifically, the page displays the red envelope information. The page to be triggered can be, for example, a mini-program page.

[0169] Step 912: Optionally, if step 910 sends information to the user terminal about a red envelope to be claimed, the user terminal can obtain the user's claiming operation for the red envelope and determine the red envelope claimed by the user. If step 910 sends information to the user terminal about the result of claiming the red envelope, then step 912 does not need to be executed.

[0170] Step 914: The platform server records the correspondence between the received user account information, product barcode information, identification information and the received red envelope.

[0171] It should be noted that, in the embodiments of this specification, receiving a red envelope means that the user can see the red envelope, but cannot use it for payment yet. It can only be used for payment after the red envelope is opened.

[0172] Step 916: After a user purchases a product, they can use their user terminal (e.g., the first application) to scan the markings on the product's inner packaging.

[0173] Step 918: The user terminal sends the identification scan information obtained by scanning the identification on the inner packaging of the product to the server. In practical applications, the identification on the inner packaging of a product can only be scanned after the user has purchased the product. Therefore, when the platform server receives the identification scan information corresponding to the target product sent by the user, it can determine that the user has purchased the target product.

[0174] Step 920: The platform server determines whether there is a locked red envelope corresponding to the user account and the identifier represented by the identifier scan information based on the received identifier scan information. If there is, the locked red envelope is opened.

[0175] Step 922: The platform server sends a message to the user terminal indicating that the red envelope has been successfully opened.

[0176] exist Figures 7 to 9 In some embodiments, the order of some steps can be interchanged according to actual needs, or some steps can be omitted or deleted.

[0177] exist Figures 7 to 9 In this embodiment, the operation steps of the user terminal, from a software perspective, can be considered as steps executed by an application installed on the user terminal. More specifically, they can be steps executed by an application corresponding to the platform server.

[0178] In the embodiments described in this specification, Figure 9 The steps for opening and unlocking the red envelope described in steps 916 to 922 can also be applied to... Figure 7 or Figure 8 In the proposed solution, specifically, it can replace... Figure 7 Steps 716 to 730 in the text can be replaced with... Figure 8 Steps 812 to 826 in the specification. Any combination of the solutions given in the embodiments of this specification should also fall within the protection scope of this application.

[0179] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods. Figure 10 The embodiments provided in this specification correspond to Figure 1 A schematic diagram of the structure of a red envelope distributing device. (See diagram below.) Figure 10 As shown, this device is applied to a server and may include:

[0180] The red envelope claiming information acquisition module 1002 is used to acquire the red envelope claiming information sent by the first application;

[0181] The red envelope receiving information sending module 1004 is used to respond to the red envelope receiving operation information and send the red envelope receiving information to the first application; the red envelope receiving information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application;

[0182] Purchase information acquisition module 1006 is used to acquire the purchase information of the account for the goods corresponding to the red envelope receiving information;

[0183] The red envelope unpacking information sending module 1008 is used to send red envelope unpacking information to the first application based on the purchase information; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the account.

[0184] based on Figure 10 The embodiments of this specification also provide some specific implementation schemes of the method, which are described below.

[0185] Optionally, the receiving operation information acquisition module 1002 can be specifically used to: acquire the barcode information of the outer packaging of the goods sent by the first application; the barcode corresponding to the barcode information is used for scanning by the barcode scanning device of the cashier system when settling the payment for the goods.

[0186] Optionally, the purchase information acquisition module 1006 can be specifically used to: acquire the product settlement information sent by the cash register; the product settlement information includes the account information of the account and the product information of the product purchased by the account; and determine that the product information of the product purchased by the account includes the product information of the product corresponding to the red envelope receiving information.

[0187] Optionally, the purchase information acquisition module 1006 can be specifically used to: acquire the identifier scanning information sent by the first application; the identifier scanning information is generated based on the scanning operation of the identifier on the inner packaging of the product corresponding to the red envelope redemption information.

[0188] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods. Figure 11 The embodiments provided in this specification correspond to Figure 4 A schematic diagram of a red envelope receiving device. Figure 11 As shown, the device, when applied to a first application, may include:

[0189] The red envelope receiving operation acquisition module 1102 is used to acquire the red envelope receiving operation triggered by the user;

[0190] The information sending module 1104 is used to send red envelope receiving operation information to the server based on the red envelope receiving operation;

[0191] The red envelope receiving information acquisition module 1106 is used to acquire the red envelope receiving information fed back by the server; the red envelope receiving information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application;

[0192] The payment code generation module 1108 is used to generate a payment code based on the payment option triggering operation, so that the cash register device can scan it;

[0193] The red envelope unpacking information acquisition module 1110 is used to acquire the red envelope unpacking information fed back by the server; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the account.

[0194] Optionally, the red envelope receiving operation acquisition module 1102 can be specifically used to: acquire the user's barcode scanning operation on the barcode information of the outer packaging of the product corresponding to the red envelope receiving information; or, acquire the user's red envelope receiving operation on the red envelope receiving page.

[0195] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods. Figure 12 The embodiments provided in this specification correspond to Figure 5 A schematic diagram of a red envelope receiving device. Figure 12 As shown, the device, when applied to a first application, may include:

[0196] The red envelope receiving operation acquisition module 1202 is used to acquire red envelope receiving operations triggered by users;

[0197] The first information sending module 1204 is used to send red envelope receiving operation information to the server based on the red envelope receiving operation;

[0198] The red envelope receiving information acquisition module 1206 is used to acquire the red envelope receiving information fed back by the server; the red envelope receiving information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application;

[0199] The identifier scanning information generation module 1208 is used to generate identifier scanning information based on the scanning operation of the identifier on the inner packaging of the product corresponding to the red envelope redemption information.

[0200] The second information sending module 1210 sends the identification scanning information to the server;

[0201] The red envelope unpacking information acquisition module 1212 is used to acquire the red envelope unpacking information fed back by the server based on the identifier scanning information; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the account.

[0202] Optionally, the red envelope receiving operation acquisition module 1202 can be specifically used to: acquire the user's barcode scanning operation on the outer packaging of the product corresponding to the red envelope receiving information; or, acquire the user's red envelope receiving operation on the red envelope receiving page.

[0203] Based on the same idea, this specification also provides devices corresponding to the above methods in its embodiments.

[0204] Figure 13 This is a schematic diagram of the structure of a terminal device provided in an embodiment of this specification.

[0205] like Figure 13 As shown, if the terminal device 1300 is an application server, it may include:

[0206] At least one processor 1310; and,

[0207] Memory 1330 communicatively connected to the at least one processor; wherein,

[0208] The memory 1330 stores instructions 1320 that can be executed by the at least one processor 1310, the instructions being executed by the at least one processor 1310 to enable the at least one processor 1310 to:

[0209] Get the red envelope claiming information sent by the first application;

[0210] In response to the red envelope claiming operation information, the red envelope claiming information is fed back to the first application; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application;

[0211] Obtain the purchase information of the account for the goods corresponding to the red envelope redemption information;

[0212] Based on the purchase information, the first application is fed back the red envelope unpacking information; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the user.

[0213] like Figure 13 As shown, if the terminal device 1300 is a user terminal, it may include:

[0214] At least one processor 1310; and,

[0215] Memory 1330 communicatively connected to the at least one processor; wherein,

[0216] The memory 1330 stores instructions 1320 that can be executed by the at least one processor 1310, the instructions being executed by the at least one processor 1310 to enable the at least one processor 1310 to:

[0217] Get the user's triggered red envelope claiming action;

[0218] Based on the aforementioned red envelope claiming operation, red envelope claiming operation information is sent to the server;

[0219] Obtain the red envelope claiming information fed back by the server; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application;

[0220] The payment option triggers an action to generate a payment code for the cashier device to scan.

[0221] Obtain the red packet unpacking information fed back by the server; the red packet unpacking information is used to indicate that the amount corresponding to the red packet has been sent to the account of the user.

[0222] Alternatively, to enable the at least one processor 1310 to:

[0223] Get the user's triggered red envelope claiming action;

[0224] Based on the aforementioned red envelope claiming operation, red envelope claiming operation information is sent to the server;

[0225] Obtain the red envelope claiming information fed back by the server; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application;

[0226] Based on the scanning operation of the identification on the inner packaging of the product corresponding to the red envelope redemption information, identification scanning information is generated;

[0227] Send the identifier scanning information to the server;

[0228] Obtain the red packet unpacking information fed back by the server based on the identifier scanning information; the red packet unpacking information is used to indicate that the amount corresponding to the red packet has been sent to the account of the account.

[0229] Based on the same approach, embodiments of this specification also provide a computer-readable medium corresponding to the above-described method. The computer-readable medium stores computer-readable instructions, which can be executed by a processor to implement the red envelope receiving or distributing method provided in the embodiments of this specification.

[0230] 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 describing the differences from other embodiments.

[0231] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to the methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Moreover, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software, which is similar to the software compiler used when writing program development code. The original code before compilation must also be written in a specific programming language, which is called a Hardware Description Language (HDL). There is not just one HDL, but many, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using the aforementioned hardware description languages ​​and programming it into an integrated circuit, the hardware circuit that implements the logic method flow can be easily obtained.

[0232] The controller can be implemented in any suitable manner. For example, it 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, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, ASICs, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0233] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can 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 any combination of these devices.

[0234] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

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

[0236] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations 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, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0237] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0238] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

[0240] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0241] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital character versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0242] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

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

[0244] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0245] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A method for distributing red envelopes, comprising: Get the red envelope claiming information sent by the first application; In response to the red envelope claiming operation information, the red envelope claiming information is fed back to the first application, specifically including: in response to the red envelope claiming operation information, feeding back the red envelope pending claiming information to the first application; obtaining user confirmation information for claiming the red envelope sent by the first application; in response to the confirmation information, feeding back the red envelope claiming information to the first application, wherein the red envelope claiming information indicates that the red envelope is in a locked state; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application; Obtain the purchase information of the account for the goods corresponding to the red envelope redemption information; Based on the purchase information, the first application is fed back the red envelope unpacking information; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the user.

2. The method according to claim 1, wherein obtaining the red envelope receiving operation information sent by the first application specifically includes: Obtain the barcode information of the outer packaging of the product sent by the first application; The barcode corresponding to the barcode information is used for scanning by the barcode scanning device of the cashier system when settling the payment for the goods; Alternatively, obtain the image information of the product sent by the first application.

3. The method according to claim 2, after obtaining the barcode information of the outer packaging of the goods sent by the first application, further comprising: Identify the product information corresponding to the barcode information; Based on the product information, determine the corresponding red envelope information; Record the account's information regarding receiving the red envelope.

4. The method according to claim 1 or 2, wherein obtaining the purchase information of the account for the goods corresponding to the red envelope receiving information specifically includes: Obtain the product settlement information sent by the POS device; The product settlement information includes the account information of the account and the product information of the products purchased by the account; It is determined that the product information of the goods purchased by the account includes the product information of the goods corresponding to the red envelope redemption information.

5. The method according to claim 1 or 2, wherein obtaining the purchase information of the account for the goods corresponding to the red envelope receiving information specifically includes: Obtain the identifier scanning information sent by the first application; The identification scanning information is generated based on the scanning operation of the identification on the inner packaging of the product corresponding to the red envelope redemption information.

6. The method according to claim 5, wherein the identifier specifically includes a QR code.

7. The method according to claim 1, wherein the red envelope receiving operation information specifically includes: User information regarding the red envelope claiming process on the red envelope claiming page.

8. The method according to claim 1, wherein the step of feeding back the red envelope receiving information to the first application specifically includes: The page information containing the red envelope claiming information is fed back to the first application; Alternatively, the application can be provided with a link to the page containing the information about claiming the red envelope.

9. The method according to claim 8, wherein the page information further includes at least one of the following: the amount information corresponding to the red envelope, the red envelope opening time limit information, and the red envelope opening condition information.

10. The method according to claim 1, further comprising, after obtaining the red envelope receiving operation information sent by the first application: Freeze the amount in the account that sent the red envelope corresponding to the red envelope to ensure that the red envelope in the locked state is valid.

11. The method according to claim 1, further comprising, after obtaining the purchase information of the account for the goods corresponding to the red envelope receiving information: The amount corresponding to the red envelope in the sending account will be sent to the account of the aforementioned account.

12. A method for receiving red envelopes, applied in the first application, comprising: Get the user's triggered red envelope claiming action; Based on the aforementioned red envelope claiming operation, red envelope claiming operation information is sent to the server; Obtaining the red envelope claiming information fed back by the server specifically includes: responding to the red envelope claiming operation information, sending feedback on the red envelope pending claiming information to the first application; obtaining user confirmation information for claiming the red envelope sent by the first application; responding to the confirmation information, sending feedback on the red envelope claiming information to the first application, wherein the red envelope claiming information indicates that the red envelope is in a locked state; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application; The payment option triggers an action to generate a payment code for the cashier device to scan. Obtain the red packet unpacking information fed back by the server; the red packet unpacking information is used to indicate that the amount corresponding to the red packet has been sent to the account of the user.

13. The method of claim 12, further comprising: The POS device sends the product settlement information corresponding to the payment code to the server; The product settlement information includes product information of the product corresponding to the red envelope redemption information.

14. The method according to claim 12, wherein obtaining the user-triggered red envelope receiving operation specifically includes: The user performs a barcode scanning operation to obtain the barcode information of the outer packaging of the product corresponding to the red envelope redemption information; Alternatively, it can retrieve the user's image information about the product.

15. The method according to claim 12, wherein obtaining the user-triggered red envelope receiving operation specifically includes: Get the user's actions regarding claiming red envelopes on the red envelope claiming page.

16. A method for receiving red envelopes, applied in a first application, comprising: Get the user's triggered red envelope claiming action; Based on the aforementioned red envelope claiming operation, red envelope claiming operation information is sent to the server; Obtaining the red envelope claiming information fed back by the server specifically includes: responding to the red envelope claiming operation information, sending feedback on the red envelope pending claiming information to the first application; obtaining user confirmation information for claiming the red envelope sent by the first application; responding to the confirmation information, sending feedback on the red envelope claiming information to the first application, wherein the red envelope claiming information indicates that the red envelope is in a locked state; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application; Based on the scanning operation of the identification on the inner packaging of the product corresponding to the red envelope redemption information, identification scanning information is generated; Send the identifier scanning information to the server; Obtain the red packet unpacking information fed back by the server based on the identifier scanning information; the red packet unpacking information is used to indicate that the amount corresponding to the red packet has been sent to the account of the account.

17. The method according to claim 16, wherein the identifier specifically includes: QR code.

18. The method according to claim 16, wherein obtaining the user-triggered red envelope receiving operation specifically includes: The user performs a barcode scanning operation to obtain the barcode information of the outer packaging of the product corresponding to the red envelope redemption information; Alternatively, it can retrieve the user's image information about the product.

19. The method according to claim 16, wherein obtaining the user-triggered red envelope receiving operation specifically includes: Get the user's actions regarding claiming red envelopes on the red envelope claiming page.

20. A red envelope dispensing device, comprising: The module for obtaining red envelope claiming information is used to obtain the red envelope claiming information sent by the first application. The red envelope receiving information sending module is used to respond to the red envelope receiving operation information and send back the red envelope receiving information to the first application. Specifically, it includes: responding to the red envelope receiving operation information and sending back the red envelope pending receiving information to the first application; obtaining user confirmation information for receiving the red envelope sent by the first application; responding to the confirmation information and sending back the red envelope receiving information to the first application, wherein the red envelope receiving information indicates that the red envelope is in a locked state; the red envelope receiving information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application. The purchase information acquisition module is used to acquire the purchase information of the account for the goods corresponding to the red envelope receiving information; The red envelope unpacking information sending module is used to send red envelope unpacking information to the first application based on the purchase information; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the account.

21. The apparatus according to claim 20, wherein the receiving operation information acquisition module is specifically used for: Obtain the barcode information of the outer packaging of the product sent by the first application; the barcode corresponding to the barcode information is used for scanning by the barcode scanning device of the cashier system when settling the payment for the product.

22. The apparatus according to claim 20 or 21, wherein the purchase information acquisition module is specifically used for: Obtain the product settlement information sent by the POS device; the product settlement information includes the account information of the account and the product information of the products purchased by the account; It is determined that the product information of the goods purchased by the account includes the product information of the goods corresponding to the red envelope redemption information.

23. The apparatus according to claim 20 or 21, wherein the purchase information acquisition module is specifically used for: Obtain the identifier scanning information sent by the first application; the identifier scanning information is generated based on the scanning operation of the identifier on the inner packaging of the product corresponding to the red envelope redemption information.

24. A red envelope receiving device, applied in a first application, comprising: The red envelope receiving operation acquisition module is used to acquire red envelope receiving operations triggered by users; The information sending module is used to send red envelope receiving operation information to the server based on the red envelope receiving operation; The red envelope receiving information acquisition module is used to acquire red envelope receiving information fed back by the server, specifically including: responding to the red envelope receiving operation information, feeding back the red envelope pending receiving information to the first application; acquiring the user's receiving confirmation information for the red envelope sent by the first application; responding to the receiving confirmation information, feeding back the red envelope receiving information to the first application, wherein the red envelope receiving information indicates that the red envelope is in a locked state; the red envelope receiving information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application; The payment code generation module is used to generate a payment code based on the payment option triggering the operation, so that the cash register can scan it; The red envelope unpacking information acquisition module is used to acquire the red envelope unpacking information fed back by the server; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the account.

25. The apparatus according to claim 24, wherein the red envelope receiving operation acquisition module is specifically used for: The user performs a barcode scanning operation to obtain the barcode information of the outer packaging of the product corresponding to the red envelope redemption information.

26. The apparatus according to claim 24, wherein the red envelope receiving operation acquisition module is specifically used for: Get the user's actions regarding claiming red envelopes on the red envelope claiming page.

27. A red envelope receiving device, applied in a first application, comprising: The red envelope receiving operation acquisition module is used to acquire red envelope receiving operations triggered by users; The first information sending module is used to send red envelope receiving operation information to the server based on the red envelope receiving operation; The red envelope receiving information acquisition module is used to acquire red envelope receiving information fed back by the server, specifically including: responding to the red envelope receiving operation information, feeding back the red envelope pending receiving information to the first application; acquiring the user's receiving confirmation information for the red envelope sent by the first application; responding to the receiving confirmation information, feeding back the red envelope receiving information to the first application, wherein the red envelope receiving information indicates that the red envelope is in a locked state; the red envelope receiving information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application; The identifier scanning information generation module is used to generate identifier scanning information based on the scanning operation of the identifier on the inner packaging of the product corresponding to the red envelope redemption information; The second information sending module sends the identifier scanning information to the server; The red envelope unpacking information acquisition module is used to acquire the red envelope unpacking information fed back by the server based on the identifier scanning information; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the account.

28. The apparatus according to claim 27, wherein the red envelope receiving operation acquisition module is specifically used for: The user performs a barcode scanning operation to obtain the barcode information of the outer packaging of the product corresponding to the red envelope redemption information.

29. The apparatus according to claim 27, wherein the red envelope receiving operation acquisition module is specifically used for: Get the user's actions regarding claiming red envelopes on the red envelope claiming page.

30. An application server, 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, which, when executed by the at least one processor, enable the at least one processor to: Get the red envelope claiming information sent by the first application; In response to the red envelope claiming operation information, the red envelope claiming information is fed back to the first application, specifically including: in response to the red envelope claiming operation information, feeding back the red envelope pending claiming information to the first application; obtaining user confirmation information for claiming the red envelope sent by the first application; in response to the confirmation information, feeding back the red envelope claiming information to the first application, wherein the red envelope claiming information indicates that the red envelope is in a locked state; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application; Obtain the purchase information of the account for the goods corresponding to the red envelope redemption information; Based on the purchase information, the first application is fed back the red envelope unpacking information; the red envelope unpacking information is used to indicate that the amount corresponding to the red envelope has been sent to the account of the user.

31. A user terminal, 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, which, when executed by the at least one processor, enable the at least one processor to: Get the user's triggered red envelope claiming action; Based on the aforementioned red envelope claiming operation, red envelope claiming operation information is sent to the server; Obtaining the red envelope claiming information fed back by the server specifically includes: responding to the red envelope claiming operation information, sending feedback on the red envelope pending claiming information to the first application; obtaining user confirmation information for claiming the red envelope sent by the first application; responding to the confirmation information, sending feedback on the red envelope claiming information to the first application, wherein the red envelope claiming information indicates that the red envelope is in a locked state; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application; The payment option triggers an action to generate a payment code for the cashier device to scan. Obtain the red packet unpacking information fed back by the server; the red packet unpacking information is used to indicate that the amount corresponding to the red packet has been sent to the account of the user.

32. A user terminal, 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, which, when executed by the at least one processor, enable the at least one processor to: Get the user's triggered red envelope claiming action; Based on the aforementioned red envelope claiming operation, red envelope claiming operation information is sent to the server; Obtaining the red envelope claiming information fed back by the server specifically includes: responding to the red envelope claiming operation information, sending feedback on the red envelope pending claiming information to the first application; obtaining user confirmation information for claiming the red envelope sent by the first application; responding to the confirmation information, sending feedback on the red envelope claiming information to the first application, wherein the red envelope claiming information indicates that the red envelope is in a locked state; the red envelope claiming information is used to indicate that a red envelope in a locked state has been allocated to the account corresponding to the first application; Based on the scanning operation of the identification on the inner packaging of the product corresponding to the red envelope redemption information, identification scanning information is generated; Send the identifier scanning information to the server; Obtain the red packet unpacking information fed back by the server based on the identifier scanning information; the red packet unpacking information is used to indicate that the amount corresponding to the red packet has been sent to the account of the account.

33. A computer-readable medium having stored thereon computer-readable instructions that can be executed by a processor to implement the method of any one of claims 1 to 19.

Images