Red envelope interaction processing methods and apparatuses, device and medium

Abstract

The embodiments of the present description disclose red envelope interaction processing methods and apparatuses, a device, and a medium. A solution comprises: establishing a short-range communication connection with a second terminal; by means of short-distance communication, acquiring tag information provided by the second terminal, the tag information being generated on the basis of red envelope information edited by a user on a red envelope editing page displayed by the second terminal, and the red envelope information at least comprising red envelope amount information; and, on the basis of the tag information, sending a red envelope acquisition request to a server, the server being used for transferring to a user account of the first terminal a number of resources represented by the red envelope amount information.

Description

A method, apparatus, device and medium for processing red envelope interactions

[0001] This application claims priority to Chinese Patent Application No. 2024115630229, filed on November 4, 2024, entitled "A Red Envelope Interaction Processing Method, Apparatus, Device and Medium", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of computer technology, and in particular to a method, apparatus, device and medium for processing red envelope interactions. Background Technology

[0003] Digital payments are becoming increasingly sophisticated and widely used, such as making payments by scanning QR codes. Similarly, the distribution of red envelopes and lucky money during Chinese New Year can be completed through online transfers.

[0004] In existing technologies, when sending red envelopes via online transfers, the recipient typically receives a notification message, clicks on it, or opens a mobile application to claim the red envelope. Even in face-to-face scenarios, users need to perform multiple steps to receive the red envelope.

[0005] Therefore, improving the convenience of red envelope interaction is a technical problem that urgently needs to be solved. Summary of the Invention

[0006] This specification provides a method, apparatus, device, and medium for processing red envelope interactions, in order to solve the problem of complex operation in existing red envelope interaction methods.

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

[0008] This specification provides an embodiment of a red envelope interaction processing method, applied to a first terminal, including:

[0009] Establish a short-range communication connection with the second terminal;

[0010] The tag information provided by the second terminal is obtained through short-range communication; the tag information is generated based on the red envelope information edited by the user on the red envelope editing page displayed on the second terminal; the red envelope information includes at least the red envelope amount information;

[0011] Based on the tag information, a request to obtain a red envelope is sent to the server; the server is used to transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal.

[0012] This specification provides an embodiment of a red envelope interaction processing method, applied to a second terminal, including:

[0013] Obtain the red envelope information edited by the user on the red envelope editing page; the red envelope information includes at least the red envelope amount information;

[0014] Based on the red envelope information, a red envelope generation request for generating short-range communication mode red envelopes is sent to the server;

[0015] Obtain the tag information returned by the server based on the red envelope generation request;

[0016] The tag information is provided to the first terminal via short-range communication; the first terminal is used to receive resources representing the amount of the red envelope based on the tag information.

[0017] This specification provides an embodiment of a red envelope interaction processing method, applied to a server, including:

[0018] The system receives a red envelope generation request sent by a second terminal for generating red envelopes in a short-range communication mode; the red envelope generation request is generated by the second terminal based on red envelope information edited by the user on the red envelope editing page; the red envelope information includes at least red envelope amount information;

[0019] Based on the aforementioned red envelope generation request, tag information is generated;

[0020] Send the tag information to the second terminal;

[0021] Obtain a red envelope retrieval request sent by the first terminal, which has established a short-range communication connection with the second terminal, based on the tag information;

[0022] Based on the request for the red envelope, the amount of resources represented by the red envelope amount information is transferred to the user account of the first terminal.

[0023] This specification provides an embodiment of a red envelope interaction processing device, applied to a first terminal, comprising:

[0024] A communication establishment module is used to establish a short-range communication connection with the second terminal;

[0025] The information acquisition module is used to acquire tag information provided by the second terminal through short-range communication; the tag information is generated based on the red envelope information edited by the user on the red envelope editing page displayed on the second terminal; the red envelope information includes at least the red envelope amount information;

[0026] The request sending module is used to send a red envelope acquisition request to the server based on the tag information; the server is used to transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal.

[0027] This specification provides an embodiment of a red envelope interaction processing device, applied to a second terminal, comprising:

[0028] The information acquisition module is used to acquire the red envelope information edited by the user on the red envelope editing page; the red envelope information includes at least the red envelope amount information;

[0029] The request sending module is used to send a red packet generation request to the server based on the red packet information, which is used to generate red packets in the short-range communication mode.

[0030] The tag information acquisition module is used to acquire the tag information fed back by the server based on the red envelope generation request;

[0031] The tag information sending module is used to provide the tag information to the first terminal via short-range communication; the first terminal is used to receive the amount of resources represented by the red envelope amount information based on the tag information.

[0032] This specification provides an embodiment of a red envelope interaction processing device, applied to a server, comprising:

[0033] The first request acquisition module is used to acquire a red envelope generation request sent by the second terminal for generating red envelopes in short-range communication mode; the red envelope generation request is generated by the second terminal based on the red envelope information edited by the user on the red envelope editing page; the red envelope information includes at least red envelope amount information;

[0034] The tag information generation module is used to generate tag information based on the red envelope generation request;

[0035] A tag information sending module is used to send the tag information to the second terminal;

[0036] The second request acquisition module is used to acquire the red envelope acquisition request sent by the first terminal that has established a short-range communication connection with the second terminal based on the tag information;

[0037] The resource transfer module is used to transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal based on the red envelope acquisition request.

[0038] This specification provides an embodiment of a red envelope interaction processing device, comprising:

[0039] At least one processor; and,

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

[0041] The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the above-described red envelope interaction processing method.

[0042] This specification provides an embodiment of a computer-readable medium storing computer-readable instructions that can be executed by a processor to implement at least one of the above-described red envelope interaction processing methods.

[0043] At least one embodiment of this specification can achieve the following beneficial effects:

[0044] The first terminal, acting as the receiver of the red envelope, can establish a short-range communication connection with the second terminal that sent it. Through this short-range communication, it obtains tag information provided by the second terminal. After obtaining the tag information, the first terminal can send a red envelope request to the server, thereby acquiring the red envelope resource. The process of the first terminal sending the red envelope request based on the tag information obtained through short-range communication only requires the user to bring the first and second terminals close together so that the first terminal can obtain the tag information via short-range communication to trigger the red envelope receiving process. This simplifies the user experience by requiring minimal user intervention. Attached Figure Description

[0045] 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.

[0046] Figure 1 is a schematic diagram of the overall scheme of a red envelope interaction processing method in an embodiment of this specification;

[0047] Figure 2 is a flowchart illustrating a red envelope interaction processing method provided in an embodiment of this specification;

[0048] Figure 3 is a flowchart illustrating a red envelope interaction processing method with a second terminal as the execution subject, as provided in an embodiment of this specification.

[0049] Figure 4 is a flowchart illustrating a method for processing red envelope interactions with a server as the execution entity, as provided in an embodiment of this specification.

[0050] Figure 5 is a swimlane diagram of a red envelope interaction processing method provided in the embodiments of this specification;

[0051] Figure 6 is a structural schematic diagram of a red envelope interaction processing device corresponding to Figure 2 provided in the embodiments of this specification;

[0052] Figure 7 is a structural schematic diagram of a red envelope interaction processing device corresponding to Figure 3 provided in the embodiments of this specification;

[0053] Figure 8 is a structural schematic diagram of a red envelope interaction processing device corresponding to Figure 4 provided in the embodiments of this specification;

[0054] Figure 9 is a schematic diagram of the structure of a red envelope interaction processing device provided in an embodiment of this specification. Detailed Implementation

[0055] 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.

[0056] To better understand the technical solutions provided in this manual, some terms will be explained below.

[0057] Digital payments refer to transactions made electronically. This includes making payments using mobile devices, computers, or other electronic devices instead of cash or traditional bank transfers.

[0058] Near Field Communication (NFC) is a short-range wireless communication technology that allows devices to exchange data in very close proximity (typically within 4 centimeters). NFC technology is based on Radio Frequency Identification (RFID) technology and can provide various functions such as data transmission, communication, and near-field payment.

[0059] Red envelopes are a traditional Chinese gift, typically given to relatives, friends, colleagues, or subordinates during festivals, celebrations, or special occasions to express blessings and good fortune. They usually contain cash and are wrapped in red paper, symbolizing good luck and happiness. In modern society, especially during festivals like the Spring Festival, red envelopes have gradually expanded to include electronic versions, such as virtual red envelopes sent through payment-enabled applications or mobile payment platforms.

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

[0061] To address the shortcomings of existing technologies, this solution provides the following embodiments:

[0062] Figure 1 is a schematic diagram of the overall scheme of a red envelope interaction processing method in an embodiment of this specification. As shown in Figure 1, the first terminal 1 is the device of the red envelope recipient, and the second terminal 2 is the device of the red envelope sender. The user of the second terminal 2 can edit information such as the red envelope amount to generate a virtual red envelope. The user of the first terminal 1 moves the first terminal 1 and the second terminal 2 close together, or the second terminal 2 and the first terminal 1 close together, or the two terminals move close to each other, so that the first terminal 1 is within the short-range communication range of the second terminal 2. In this way, the first terminal 1 can obtain the tag information in the second terminal 2. Then, based on the tag information, the first terminal 1 can send a red envelope acquisition request to the server. The server can transfer the red envelope resources represented by the red envelope information used to generate the tag information to the user account of the first terminal 1, so that the user of the first terminal 1 can obtain the red envelope.

[0063] In this configuration, the first terminal 1 and the second terminal 2 can be mobile terminals, such as smartphones, tablets, smartwatches, portable game consoles, etc. One of the terminals, first terminal 1 and second terminal 2, can also be a fixed terminal, such as a POS machine, cash register, advertising device, etc. The types of terminals for first terminal 1 and second terminal 2 can be the same or different, as long as they have short-range communication capabilities; no specific limitations are imposed here.

[0064] Next, a red envelope interaction processing method provided in the embodiments of the specification will be described in detail with reference to the accompanying drawings.

[0065] Figure 2 is a flowchart illustrating a red envelope interaction processing method provided in an embodiment of this specification. From a programming perspective, the entity executing the process may include a program mounted on a first terminal. This program may include a system program of the terminal system or an application client mounted on the terminal. From a hardware perspective, the entity executing the process may include the first terminal.

[0066] As shown in Figure 2, the process may include the following steps.

[0067] Step 202: Establish a short-range communication connection with the second terminal.

[0068] The first terminal acts as the recipient of the red envelope, and the second terminal acts as the sender. Both terminals have short-range communication capabilities; when they are within short-range communication range, they can establish a connection. Short-range communication can refer to communication that occurs only over a short distance, such as NFC or Bluetooth communication, or other forms of short-range communication.

[0069] Step 204: Obtain the tag information provided by the second terminal through short-range communication.

[0070] The tag information is generated based on the red envelope information edited by the user on the red envelope editing page displayed on the second terminal; the red envelope information includes at least the red envelope amount information.

[0071] The second terminal acts as a provider or sender of red envelopes. Users can view red envelope information, such as the amount, on the second terminal's red envelope editing page. The second terminal can generate tag information based on the user-edited red envelope information to trigger the red envelope claiming process. Alternatively, the second terminal can send the user-edited red envelope information to a server, which will then generate tag information and send it back to the second terminal, which can then save this tag information. After the first terminal establishes a short-range communication connection with the second terminal, the first terminal can obtain the tag information stored in the second terminal.

[0072] In practical applications, users of the second terminal can send red envelopes through terminal applications or mini-programs with red envelope sending functions. The red envelope editing page can be a page in the terminal application or mini-program, where users can edit the red envelope information.

[0073] In practical applications, if the first terminal is locked, the user can unlock it first, and then establish short-range communication between the first terminal and the second terminal, allowing the first terminal to obtain tag information. If the first terminal's short-range communication function can be used in the locked state, and the first terminal can parse tag information in the locked state, it is not necessary to unlock the first terminal. Whether or not the first terminal needs to be unlocked can be set according to actual needs, and no specific limitation is made here.

[0074] Step 206: Based on the tag information, send a red envelope retrieval request to the server.

[0075] The server is used to transfer resources representing the amount of the red envelope to the user account of the first terminal.

[0076] After the first terminal obtains the tag information, it triggers the red envelope acquisition process based on the tag information. Specifically, it can send a red envelope acquisition request to the server. The red envelope acquisition request can contain the identification information of the first terminal, and can also contain at least part of the information in the tag information, such as information used to identify the user account of the first terminal, so that the server can transfer red envelope resources to the user account of the first terminal after receiving the red envelope acquisition request sent by the first terminal.

[0077] 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.

[0078] In the method shown in Figure 2, the first terminal establishes a short-range communication connection with the second terminal. The first terminal obtains tag information provided by the second terminal through this short-range communication. After obtaining the tag information, the first terminal can send a request to the server to claim a red envelope, thereby obtaining the red envelope resource. The method of the first terminal sending the red envelope request to the server based on the tag information obtained through short-range communication only requires the user to bring the first and second terminals close together so that the first terminal can obtain the tag information through short-range communication to trigger the red envelope claiming process. This simplifies the user experience by eliminating the need for extensive user intervention.

[0079] On the other hand, the first terminal needs to obtain the tag information provided by the second terminal through short-range communication in order to receive the red envelope resources. In other words, the first terminal and the second terminal need to be close to each other, for example, by sticking or touching each other. The first terminal can obtain the red envelope resources. In the process of red envelope interaction, the user's sense of participation and ritual can also be improved, thus enhancing the user experience.

[0080] Based on the method in Figure 2, this specification also provides some specific implementation schemes, which are described below.

[0081] Optionally, the tag information in the embodiments of this specification may include link information for triggering the red envelope acquisition process. The aforementioned sending of a red envelope acquisition request to the server based on the tag information may specifically include: accessing the link address represented by the link information; and sending a red envelope acquisition request to the server based on the link address.

[0082] The tag information can be in the form of a link, or it can be tag information that contains links. For example, links starting with strings such as http or https.

[0083] After obtaining the tag information, the first terminal can parse its content to obtain the link information within the tag. The first terminal can then access the link address represented by this link information through its system browser or the built-in browser of its application. This link address enables the first terminal to interact with a server. The server can be the one corresponding to this link address and can handle the relevant business associated with that link address.

[0084] In practical applications, the process of sending and receiving red envelopes can be carried out in a terminal application or mini-program with red envelope interaction function. As one implementation, the tag information includes identification information of the target application used to receive the red envelope; if the target application is not launched on the first terminal, the method further includes: launching the target application based on the identification information.

[0085] Correspondingly, the aforementioned sending of a red envelope request to the server may specifically include: sending a red envelope request to the server based on the launched target application.

[0086] The first terminal may have a short-range communication module to acquire tag information, and the terminal system program can parse the content of the tag information. If the tag information contains the identification information of a target application, the terminal system can trigger the terminal to launch the target application. In this embodiment, the launched target application can send a red envelope request to the server. The server can be a server capable of handling the business related to the target application.

[0087] If the target application is already running on the first terminal, but in the background, a request to receive a red envelope can be sent to the server through the background application. Alternatively, the first terminal can switch the target application to the foreground and then send a request to receive a red envelope to the server.

[0088] In practical applications, if the target application is not installed on the first terminal, the first terminal can still display a prompt message prompting the user to install the target application upon obtaining the tag information. This prompt message can be generated by the server and sent back to the first terminal; alternatively, it can be provided locally on the first terminal or by the first terminal's system server according to the agreement between the first terminal provider and the target application provider.

[0089] To improve user experience, the first terminal can also display at least one of the following: information about receiving the red envelope and information about the result of receiving the red envelope. Optionally, after sending the red envelope request to the server in the embodiments of this specification, the process may further include:

[0090] Display a red envelope receiving page; the red envelope receiving page includes a prompt message indicating that a red envelope is being received; and / or, display a red envelope receiving result page; the red envelope receiving result page includes result information indicating the red envelope receiving result.

[0091] In practical applications, the first terminal can display either the red envelope receiving page or the red envelope receiving result page, or both pages.

[0092] For example, after the first terminal obtains the tag information provided by the second terminal to trigger the red envelope receiving process through short-range communication, the server can process the red envelope receiving request initiated by the first terminal. After the request is processed, the server sends the page information of the red envelope receiving result page to the first terminal, and the first terminal can display the red envelope receiving result page.

[0093] For example, after receiving a request for a red envelope from a first terminal, the first server can send back the red envelope receiving page information to the first terminal. The first terminal can then display a red envelope receiving page indicating that a red envelope is being received. While the red envelope receiving page is displayed on the first terminal, the server can execute the relevant process for processing the red envelope request sent by the first terminal. For example, based on the request, the server can determine the relevant information of the first terminal's user account and transfer the red envelope resources to the first terminal's user account.

[0094] For example, after the first terminal sends a request to the server to receive a red envelope using the tag information provided by the second terminal, the first terminal can first display the red envelope receiving page, and then display the red envelope receiving result page after the first terminal has finished receiving the red envelope.

[0095] In terms of page presentation, the red envelope receiving page and the red envelope receiving result page can be the same page or different pages. In the embodiments of this specification, the prompt information indicating that a red envelope is being received can be called the red envelope receiving page, and the result information indicating the red envelope receiving result can be called the red envelope receiving result page.

[0096] The red envelope receiving page can also include information representing the red envelope as a virtual image, such as text, characters, or images. For example, the red envelope receiving page can display an image or animated image of a red envelope cover with a red background; it can also display a static or dynamic virtual image in the shape of a gold ingot, a virtual image representing a currency symbol, or a cartoon image containing red envelope characteristics, etc.

[0097] The red envelope receiving page can display either a static or dynamic virtual image of the red envelope. For example, it can display a static red envelope cover or cartoon character; or it can display dynamic animation effects, such as showing the virtual image of the red envelope rotating, flying in, shaking, or growing in size.

[0098] The red envelope receiving page can be a page generated from the first terminal's local information after the first terminal obtains the tag information, or it can be a page fed back by the server. In one implementation, after the first terminal sends a red envelope receiving request to the server based on the tag information, the server can generate the red envelope receiving page information based on the request and feed it back to the first terminal, allowing the first terminal to display the red envelope receiving page. In another implementation, the first terminal can locally store the red envelope receiving page information. For example, when the first terminal installs a terminal application with red envelope receiving functionality, the application's installation package can contain the red envelope receiving page information. After obtaining the tag information, the first terminal can retrieve the red envelope receiving page information from its local data through the application, thus displaying the red envelope receiving page on the first terminal.

[0099] Optionally, the notification message indicating that a red envelope is being received may include at least one of the following: an animation effect of the red envelope being transferred to the first terminal, text information indicating that a red envelope is being received, or voice information indicating that a red envelope is being received.

[0100] Among them, the animation effect of transferring the red envelope to the first terminal can present users with a visual effect of the red envelope entering the first terminal, such as the visual effect of the red envelope flying in or jumping into the first terminal, or the visual effect of the red envelope gradually appearing on the first terminal from light to dark and from small to large, etc.

[0101] The text message indicating that a red envelope is being received can be a textual notification to the user that a red envelope is being received, such as the words "receiving red envelope" or "receiving red envelope". The text message can be static or dynamic.

[0102] The voice message indicating that a red envelope is being received can be a voice notification to the user that a red envelope is being received, such as "You are receiving a red envelope", "Red envelope being received", "Big red envelope coming", etc.

[0103] To further enhance the user experience and make digital red envelopes more ceremonial, as one implementation method, the animation effect of transferring the red envelope into the first terminal can specifically be: an animation effect of transferring the red envelope from a preset edge of the first terminal into the first terminal; the preset edge is any edge of the first terminal, an edge of the first terminal close to the second terminal, or any edge of the first terminal in the opposite direction to the edge of the second terminal from which the red envelope is transferred out.

[0104] In practical applications, the animation effect displayed on the first terminal can be determined based on the relative positions of the first and second terminals when establishing short-range communication. For example, assuming the first and second terminals are placed in the same direction, and the first terminal approaches the second terminal from the right side to establish short-range communication, the first terminal can display the visual effect of a red envelope being swiped in from the left side of the first terminal and moving to the right. Alternatively, if the top of the first terminal is located at the bottom of the second terminal, and the first terminal approaches the second terminal from the top to the bottom to establish short-range communication, the first terminal can display the visual effect of a red envelope being swiped in from the top of the first terminal.

[0105] If the first terminal and the second terminal are not placed in the same direction, such as the top of the first terminal being close to the top of the second terminal, the first terminal can also display the visual effect of the red envelope being swiped in from the top of the first terminal.

[0106] For example, if the second terminal displays an animation effect of the red envelope being drawn out from the right edge of the second terminal, the first terminal can display an animation effect of the red envelope being drawn in from the left edge of the first terminal.

[0107] It is understandable that the above are just a few examples. In actual applications, the visual effect can be determined based on the relative positions of the first and second terminals. There are no specific limitations here, as long as the visual effect of the red envelope being transferred to the first terminal can be displayed.

[0108] In practical applications, the animation effect of the red envelope being transferred in on the first terminal can also be a synchronized animation effect with the animation effect of the red envelope being transferred out on the second terminal. For example, the second terminal dynamically displays the visual effect of the red envelope being transferred out. At a certain moment, the second terminal displays a portion of the information, such as a part of the red envelope card or a part of the virtual avatar. The other part of the information has already been displayed on the second terminal, which can be understood as having been transferred out of the second terminal. At this time, the first terminal can display the other part of the information. In this way, the first and second terminals can display synchronized visual effects of sending and receiving red envelopes, making the user feel that the red envelope from the second terminal has been sent to the first terminal.

[0109] In practical applications, the animation effects displayed on the red envelope receiving page and the animation effects displayed on the red envelope sending page of the first terminal can be displayed synchronously or asynchronously, depending on the actual situation.

[0110] The red envelope receiving result page can be the page displayed after the first terminal has successfully received the red envelope. This page can contain information indicating that the red envelope has been successfully received. If the first terminal fails to receive the red envelope due to network instability or other reasons, the red envelope receiving result page can also display information indicating that the red envelope has not been successfully received.

[0111] Optionally, the result information indicating the receipt of the red envelope may include at least one of the following: an animation effect indicating that the red envelope has been received, text information indicating that the red envelope has been received, and voice information indicating that the red envelope has been received.

[0112] The animation effects indicating the receipt of a red envelope can be visual effects in animated form, such as a cartoon character, a red envelope image, or artistic font. Text messages indicating the receipt of a red envelope will be text-based, such as "You have received a new red envelope." Audio messages indicating the receipt of a red envelope will be voice-based, such as a voice announcement saying "You have received a new red envelope." Sound notifications such as "beep" or "ding" sounds can also be used.

[0113] In practical applications, the results can be dynamic or static. For example, results can be displayed as static text, or as an animation containing a virtual image of a red envelope.

[0114] In one implementation, at least one of the aforementioned voice messages indicating that a red envelope is being received and another indicating that a red envelope has been received may include information about the sender of the red envelope. This allows the user of the first terminal to know who sent them the red envelope.

[0115] In practical applications, the information of the red envelope sender may include the name information recorded by the user of the second terminal in the first terminal.

[0116] The user of the second terminal can be a friend or contact of the user of the first terminal. The user of the first terminal can make notes or set a name for the user of the second terminal in the first terminal, such as a title, name, nickname, etc.; or the first terminal can also record the name information set by the user of the second terminal.

[0117] If the first terminal does not record any information about the user of the second terminal, or if the user of the first terminal and the user of the second terminal have not previously communicated using the first terminal and the second terminal, or if there has been no communication between the user account of the first terminal and the user account of the second terminal, the voice information may also include the name information of the user of the second terminal, which can be the name information set by the user of the second terminal.

[0118] In practical applications, the text information, animation effects, and other information displayed on the page mentioned above may also include relevant information about the second-end user. It should be noted that all user-related information used in the embodiments of this specification is obtained and used with the user's authorization.

[0119] The red envelope receiving results page can also include a virtual image representing the red envelope. This image can be dynamic or static, as described above, and will not be repeated here.

[0120] In practical applications, the red envelope receiving result page can be generated by the server after it has executed the step of transferring the red envelope resources provided by the second terminal to the user account of the first terminal. For example, after the server transfers the amount of resources represented by the red envelope amount to the user account of the first terminal, it can generate a red envelope receiving result page and send it back to the first terminal; if some problems occur during the transfer process and the red envelope resources fail to be successfully transferred to the user account of the first terminal, the server can still generate a red envelope receiving result page and send it back to the first terminal.

[0121] The red envelope receiving result page can also be generated and displayed from the local data of the first terminal. As one implementation, the first terminal can locally store the page information for the red envelope receiving result page. For example, when the first terminal installs a terminal application with red envelope receiving functionality, the application's installation package can contain the page information for the red envelope receiving result page. After the first terminal obtains the tag information and sends a red envelope receiving request to the server, the server, after processing the relevant red envelope receiving or claiming process, sends information or instructions indicating completion and success to the first terminal. Upon receiving this information or instruction, the first terminal can retrieve the corresponding red envelope receiving result page information from its local data, and thus display the red envelope receiving result page on the first terminal.

[0122] Optionally, in the embodiments of this specification, the red envelope receiving page may also include at least one of the following controls: a first control for indicating that the red envelope is being opened, a second control for indicating that the red envelope is being received, and a third control for indicating that the red envelope is being refused.

[0123] In practical applications, the red envelope receiving page may not contain the above controls. For example, it may only display a virtual image of the red envelope or some prompt information, and the first terminal may passively receive or accept the red envelope.

[0124] The red envelope receiving page can also include one of the aforementioned controls. For example, the red envelope receiving page may only contain the first control. If the user performs an action on the first control, it can indicate that the user has confirmed receiving the red envelope. In practical applications, if no action is performed on the first control, one possibility is that the user has refused to receive the red envelope; another possibility is that the user has confirmed receiving the red envelope but has not yet viewed the specific amount. The server can also transfer the red envelope resources to the user's account on the first terminal. Similarly, the red envelope receiving page may only contain the second control. If the user performs an action on the third control, it can indicate that the user has confirmed receiving the red envelope, or that the user has confirmed receiving and opening the red envelope. Again, the red envelope receiving page may only contain the third control. If the user performs an action on the third control, the first terminal or server can determine that the user has refused to receive the red envelope; or, if the user does not perform an action on the third control within a preset time period, it can indicate that the user has confirmed receiving the red envelope, or that the user has confirmed receiving and opening the red envelope.

[0125] The red envelope receiving page can contain two of the controls mentioned above. For example, the red envelope receiving page can contain the first control and the third control, or the first control and the second control. The red envelope receiving page can also contain three of the controls mentioned above.

[0126] It is understandable that these are just some examples, and the specific content displayed on the red envelope receiving page can be set according to actual needs.

[0127] As one implementation method, the methods in the embodiments of this specification may further include:

[0128] If the user's first operation, indicating opening a red envelope, is detected on the red envelope receiving page, then the animation effect of opening the red envelope is displayed;

[0129] Alternatively, if a second operation indicating confirmation of receiving a red envelope is obtained from the user based on the red envelope receiving page, an animation effect of placing the red envelope into the first terminal is displayed.

[0130] Alternatively, if a third operation indicating that the user refuses to receive the red envelope is detected based on the red envelope receiving page, an animation effect of transferring the red envelope out of the first terminal is displayed.

[0131] The first operation can be an action performed by the user on the first control on the red envelope receiving page that indicates opening the red envelope, such as clicking the "open" control, performing a swipe operation in the first direction on the page, or tilting the first terminal in the first direction. The first operation can also be an operation on the aforementioned second control.

[0132] The animation effect for opening a red envelope is an animation effect that can represent the opening of a red envelope. For example, the red envelope receiving page first displays an unopened red envelope. After the first terminal obtains the user's first operation, the red envelope receiving page can display an animation effect of the unopened red envelope being opened.

[0133] The second operation can be an action performed by the user on a second control included on the red envelope receiving page, such as clicking the "Receive" control, performing a swipe operation in a second direction on the page, or tilting the first terminal in a second direction. The second operation can also be an operation on the aforementioned first control, or it can be an operation without the aforementioned third control.

[0134] The animation effect of placing the red envelope into the first terminal can be the effect of receiving the red envelope to a preset position, such as showing the visual effect of the red envelope being sucked into the lower right corner, or showing the visual effect of the red envelope jumping into the area marked by the red envelope clip on the red envelope receiving page, etc.

[0135] The virtual image of the red envelope displayed in the animation effect of the first terminal can represent either an unopened red envelope or an opened red envelope. This can be set according to actual needs.

[0136] The third operation can be the user's action on the third control included on the red envelope receiving page to indicate that they want to refuse to receive the red envelope, such as clicking the "Refuse" control, performing a third-party swipe operation on the page, or tilting the first terminal according to a third-party direction.

[0137] The animation effect for transferring the red envelope out of the first terminal can be an animation of breaking the red envelope, moving the red envelope out of the first terminal, or throwing the red envelope out of the first terminal, etc. The specific animation can be set according to actual needs, as long as it can represent transferring the red envelope out of the first terminal.

[0138] In practical applications, if the red envelope receiving page displays an animation of the red envelope being swiped into the first terminal, the red envelope leaving the first terminal can display an animation of the red envelope being swiped back along the path it was swiped into. For example, the red envelope receiving page first displays an animation of the red envelope being swiped into the first terminal from the left side; after the user refuses to accept the red envelope, the first terminal can display an animation of the red envelope being swiped back from the left side.

[0139] Based on the same approach, this specification also provides a method for processing red envelope interactions using a second terminal as the execution subject. Figure 3 is a flowchart illustrating a red envelope interaction processing method using a second terminal as the execution subject according to an embodiment of this specification. From a programming perspective, the execution subject of the process may include a program mounted on the second terminal. This program may include system programs of the terminal system or application client programs mounted on the terminal. From a hardware perspective, the execution subject of the process may include the second terminal.

[0140] As shown in Figure 3, the process may include the following steps.

[0141] Step 302: Obtain the red envelope information edited by the user on the red envelope editing page.

[0142] The red envelope information includes at least the amount. The red envelope editing page may contain an area for editing red envelope information, which users can edit by filling in or selecting data. The red envelope information is related to the red envelope itself, and may specifically include the amount. The specific amount included in the red envelope amount information can be edited by the user or be a default amount in the application.

[0143] The second terminal may have a display screen, or the second terminal may be connected to a display device. The red envelope editing page may be a page displayed on the second terminal, or it may be a page displayed on a display device associated with the second terminal.

[0144] In practical applications, users can send red envelopes through terminal applications or mini-programs installed on a second terminal. Sending red envelopes here refers to sending virtual red envelopes, a method of resource interaction that utilizes computer technology.

[0145] Step 304: Based on the red envelope information, send a red envelope generation request to the server for generating red envelopes in short-range communication mode.

[0146] The second terminal can send a red envelope generation request to the server based on the red envelope information. The red envelope generation request can be a request to the server to generate a red envelope that can be sent through short-range communication mode.

[0147] In practical applications, the red envelope editing page can include identification information for short-range communication, such as the word "NFC". Alternatively, the red envelope editing page can be the page displayed on the second terminal after the user selects short-range communication as the method for sending red envelopes.

[0148] The red envelope generation request can include red envelope information, such as the amount. It can also include a service identifier indicating that the red envelope is being sent via short-range communication, and information about the second terminal and / or the user logged into that terminal. Upon receiving the red envelope generation request, the server can trigger a red envelope processing flow using short-range communication. For example, the server can generate information to trigger the receipt of the red envelope and send it back to the second terminal, allowing the first terminal to trigger the receipt of the red envelope via short-range communication.

[0149] Step 306: Obtain the tag information fed back by the server based on the red envelope generation request.

[0150] The tag information can be used to trigger the receipt of red envelopes, specifically in the form of a pre-formatted string or a link. The tag information may include identifiers representing the red envelope resources corresponding to the red envelope generation request sent by the second terminal. For example, after receiving a red envelope generation request from the second terminal, the server can generate a token for that request. The server can then generate tag information based on this token, enabling subsequent execution of corresponding business processes.

[0151] Step 308: Provide the tag information to the first terminal via short-range communication.

[0152] The first terminal is used to receive resources representing the amount of the red envelope amount based on the tag information.

[0153] After receiving the tag information from the server, the second terminal can save the tag information locally on the terminal or in a secure and trusted environment to ensure information security.

[0154] In practical applications, the short-range communication function of the second terminal is enabled before executing step 308 above. Specifically, the short-range communication function of the second terminal can be enabled automatically before or during any of steps 302 to 306 above, or the user can manually enable the short-range communication function of the second terminal. For example, the short-range communication function of the second terminal can be enabled when displaying the red envelope editing page, or before displaying the red envelope editing page, such as after the second terminal launches the terminal application or mini-program where the red envelope editing page is located, or after the second terminal obtains the tag information fed back by the server.

[0155] The specific process of the first terminal receiving red envelope resources based on tag information can be found in the relevant content of the aforementioned embodiments, and will not be repeated here.

[0156] It should be understood that the order of some steps in the methods described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted. Furthermore, this embodiment and the above embodiments are based on the same technical concept, and similar or identical content included in this embodiment and the above embodiments can be referred to each other, and will not be repeated here.

[0157] In the method shown in Figure 3, the second terminal can send a red packet generation request to the server based on the red packet information edited by the user. After that, it can also send the tag information fed back by the server to the first terminal through short-range communication, so that the first terminal can obtain the red packet resources sent by the second terminal through short-range communication, which can simplify the user's operation in the red packet interaction process.

[0158] On the other hand, the second terminal sends red envelopes to the first terminal through short-range communication, so that the first terminal and the second terminal are relatively close to each other in order for the first terminal to receive the red envelope resources sent by the second terminal. This can also increase the user's sense of participation and ritual during the red envelope interaction process, thereby improving the user experience.

[0159] In the embodiments of this specification, the red envelope information edited by the user may or may not include the recipient's information.

[0160] In one implementation, the red envelope information edited by the user on the second terminal does not need to include the recipient's information. The first terminal, with short-range communication capabilities, can obtain the red envelope resource by simply touching or swiping it close to the second terminal. This allows the user on the second terminal to send red envelopes to the first terminal even without knowing the recipient's information, such as account details or phone number, used to distinguish different users. This improves the convenience of red envelope interaction. Furthermore, the second terminal user does not need to fill in the recipient's information, simplifying the user's operation.

[0161] As another implementation, the red envelope information edited by the user on the second terminal can include the recipient's information. This ensures that only the recipient can receive the red envelope from the second terminal and send a red envelope specifically for the first terminal. This allows red envelopes to be sent to a specific terminal even when multiple terminals are nearby. Furthermore, to simplify the operation of the second terminal, the user information of the first terminal can be obtained through short-range communication, automatically displaying the first terminal's user information on the red envelope editing page without requiring manual input from the user on the second terminal.

[0162] In practical applications, the red envelope editing page can also include a confirmation control. If the second terminal obtains the user's operation on the control, the second terminal can send a red envelope generation request to the server.

[0163] In the embodiments of this specification, short-range communication can refer to a communication method that enables data interaction within a relatively short distance, and may include communication methods such as Bluetooth and NFC.

[0164] As one implementation method, the short-range communication in the embodiments of this specification is NFC near-field communication; the method in the embodiments of this specification may also include:

[0165] The second terminal enables NFC card emulation mode;

[0166] The tag information is saved in the NFC card emulation mode so that the first terminal in NFC reader mode can read the tag information.

[0167] After receiving the tag information from the server, the second terminal can activate NFC card emulation mode and save the acquired tag information to itself, specifically in the NFC card emulation module. The first terminal can then operate in NFC reader mode, reading the tag information from the second terminal via NFC near-field communication.

[0168] In practical applications, the second terminal can also be in NFC card emulation mode before obtaining the tag information fed back by the server. For example, after the second terminal obtains the red envelope information edited by the user, or after displaying the red envelope editing page, or after sending a request to the server, the second terminal can process the NFC card emulation mode.

[0169] The second terminal can operate in any mode, including peer-to-peer, card emulation, and card reader modes, depending on actual needs. For details on the working principles of each mode, please refer to the relevant technical documentation; they will not be elaborated upon here.

[0170] In the embodiments of this specification, the second terminal sending the red envelope can be in card mode, and the first terminal receiving the red envelope can be in card reader mode. The first terminal can read the NFC tag information provided by the second terminal through NFC near-field communication and trigger the process of receiving the red envelope.

[0171] To improve user experience, the second terminal can also display information such as the red envelope sending details and the red envelope sending result. Optionally, the method in the embodiments of this specification may further include:

[0172] Displays a red envelope sending page; the red envelope sending page includes a prompt message indicating that a red envelope is being sent;

[0173] And / or, display a red envelope sending result page; the red envelope sending result page contains result information indicating the red envelope sending result.

[0174] In practical applications, the second terminal can display either the red envelope sending page or the red envelope sending result page, or both of these pages.

[0175] For example, after the second terminal sends tag information to the first terminal via short-range communication, the first terminal sends a request to the server to obtain a red envelope based on the tag information. After the server processes the request, it sends the red envelope sending result page information to the second terminal, which can then display the red envelope sending result page.

[0176] For example, after the second terminal sends a red envelope generation request to the server based on the red envelope information edited by the user, the server can send back the red envelope sending page information to the second terminal. The second terminal can then display the red envelope sending page indicating that a red envelope is being sent. While the red envelope sending page is being displayed on the second terminal, the server can execute the relevant processes for processing the red envelope generation request sent by the second terminal. For example, the process of generating tag information, and / or the process of determining the relevant information of the user account of the second terminal based on the red envelope generation request and deducting the corresponding red envelope resources from the user account of the second terminal, etc.

[0177] For example, after the second terminal sends a red envelope generation request to the server, the second terminal can first display the red envelope sending page, and then display the red envelope sending result page. For instance, after the second terminal finishes sending the red envelope, or after the server deducts the corresponding red envelope resources from the second terminal's user account, or after the first terminal obtains the second terminal's tag information, or after the second terminal executes the red envelope receiving process using the tag information, the second terminal can then display the red envelope sending result page.

[0178] In terms of page presentation, the red envelope sending page and the red envelope sending result page can be the same page or different pages. In the embodiments of this specification, the prompt information indicating that a red envelope is being sent can be called the red envelope sending page, and the result information indicating the red envelope sending result can be called the red envelope sending result page.

[0179] The red envelope sending page can also include information representing the red envelope as a virtual image, such as text, characters, or images. For example, the red envelope sending page can display an image or animated image of a red envelope cover with a red background; it can also display a static or dynamic virtual image in the shape of a gold ingot, a virtual image representing a currency symbol, or a cartoon image containing red envelope characteristics, etc.

[0180] The red envelope sending page can display either a static or dynamic virtual image of the red envelope. For example, it can display a static red envelope cover or cartoon character; or it can display dynamic animation effects, such as showing the virtual image of the red envelope rotating, flying out, shaking, or shrinking in size.

[0181] The red envelope sending page can be generated by the second terminal based on local information, or it can be a page fed back by the server. In one implementation, the server can generate the page information for the red envelope sending page based on the red envelope generation request sent by the second terminal and feed it back to the second terminal, allowing the second terminal to display the red envelope sending page. In another implementation, the second terminal can locally store the page information for the red envelope sending page. For example, when the second terminal installs a terminal application with red envelope sending functionality, the application's installation package can contain the page information for the red envelope sending page. After the first terminal obtains the red envelope information edited by the user, it can retrieve the page information for the red envelope sending page from local data through the terminal application, thus allowing the second terminal to display the red envelope sending page.

[0182] Optionally, the notification message indicating that a red envelope is being sent may include at least one of the following: an animation of the red envelope being transferred out of the second terminal, text information indicating that a red envelope is being sent, or voice information indicating that a red envelope is being sent.

[0183] Among them, the animation effect of transferring the red envelope out of the second terminal can present users with a visual effect of the red envelope moving out of the second terminal, such as the visual effect of the red envelope flying out and jumping out of the first terminal, or the visual effect of the red envelope gradually leaving the first terminal from dark to light and from large to small, etc.

[0184] The text message indicating that a red envelope is being sent can be a textual notification to the user, such as "Sending a red envelope." The text message can be static or dynamic.

[0185] The voice message indicating that a red envelope is being sent can be a voice prompt to the user that a red envelope is being sent, such as "You are sending a red envelope" or "Red envelope being sent".

[0186] To further enhance the user experience and make digital red envelopes more ceremonial, as one implementation method, the animation effect of the red envelope being transferred out of the second terminal can be: an animation effect of transferring the red envelope out of the second terminal from a preset edge of the second terminal; the preset edge is any edge of the second terminal, any edge of the second terminal that is close to the first terminal, or any edge of the second terminal that is in the opposite direction to the edge of the first terminal into which the red envelope is transferred.

[0187] In practical applications, the animation effect displayed on the second terminal can be determined based on the relative positions of the first and second terminals when establishing short-range communication. For example, assuming the first and second terminals are placed in the same direction, if the first terminal approaches the second terminal from its right side to establish short-range communication, the second terminal can display a visual effect of a red envelope swiping out from the right side of the second terminal and / or moving to the right. Similarly, if the top of the first terminal is located at the bottom of the second terminal, and the first terminal approaches the second terminal from its top to its bottom to establish short-range communication, the second terminal can display a visual effect of a red envelope swiping out from the bottom of the second terminal.

[0188] If the first terminal and the second terminal are not placed in the same direction, such as the top of the first terminal being close to the top of the second terminal, the second terminal can display the visual effect of the red envelope being swiped out from the top of the second terminal.

[0189] It is understandable that the above are just a few examples. In actual applications, the visual effect can be determined based on the relative positions of the first and second terminals. There are no specific limitations here, as long as the visual effect of the red envelope being transferred out of the second terminal can be displayed.

[0190] In practical applications, the animation effect of transferring the red envelope out of the second terminal is linked to the animation effect of transferring the red envelope into the first terminal.

[0191] For example, the second terminal can dynamically display the visual effect of a red envelope being transferred out. At a certain moment, the second terminal displays a portion of the information, such as a part of the red envelope card or a part of a virtual avatar. The remaining information has already been displayed on the second terminal, which can be interpreted as the red envelope having been transferred out. At this point, the first terminal can display the remaining information. In this way, the first and second terminals can display a linked visual effect of sending and receiving red envelopes, making the user feel as if the red envelope from the second terminal has been sent to the first terminal.

[0192] In practical applications, the animation effects displayed on the red envelope sending page on the second terminal and the animation effects displayed on the red envelope receiving page on the first terminal can be displayed synchronously or asynchronously, depending on the actual situation.

[0193] In the embodiments of this specification, the red envelope sending result page can represent the page displayed after the second terminal has completed sending the red envelope. This page can contain information indicating that the red envelope was successfully sent. If the second terminal fails to send the red envelope due to network instability or other reasons, the red envelope sending result page can display information indicating that the red envelope was not successfully sent.

[0194] Optionally, the result information indicating the red envelope sending result page includes at least one of the following: an animation effect indicating the end of red envelope sending, text information indicating the end of red envelope sending, and voice information indicating the end of red envelope sending.

[0195] The animation effect indicating the end of sending a red envelope can be a visual effect showing that the red envelope has been sent. For example, it can use a cartoon character, a red envelope image, or artistic font to indicate that the red envelope has been sent. The text message indicating the end of sending a red envelope is a text message indicating that the red envelope has been sent, such as "Red envelope sent". The voice message indicating the end of sending a red envelope is a voice message indicating that the red envelope has been sent, such as a voice broadcast message saying "Red envelope sent". It can also be a notification sound such as "beep" or "ding".

[0196] In practical applications, the results can be dynamic or static. For example, results can be displayed as static text, or as an animation containing a virtual image of a red envelope.

[0197] In one implementation, at least one of the aforementioned voice messages indicating that a red envelope is being sent and the voice message indicating that the red envelope sending has ended may include information about the recipient of the red envelope. This allows the user of the second terminal to easily ascertain who received the red envelope.

[0198] In practical applications, the information of the recipient of the red envelope may include the name information recorded by the user of the first terminal in the second terminal. For example, the second terminal may broadcast a voice prompt saying "Send a red envelope to Zhang San".

[0199] The user on the first terminal can be a friend or contact of the user on the second terminal. The user on the second terminal can add notes or set names for the user on the first terminal, such as titles, names, nicknames, etc.; or the second terminal can also record name information set by the user on the first terminal.

[0200] If the second terminal does not record any information about the user of the first terminal, or if the user of the second terminal and the user of the first terminal have not previously used the second terminal to contact each other, or if the user account of the second terminal and the user account of the first terminal have not sent any messages, the voice message may also include the name information of the user of the first terminal, which can be the name information set by the user of the first terminal.

[0201] In practical applications, the text information, animation effects, and other information displayed on the page mentioned above may also include relevant information about the first terminal user. It should be noted that all user-related information used in the embodiments of this specification is obtained and used with the user's authorization.

[0202] The red envelope sending results page can also include a virtual image representing the red envelope. This image can be dynamic or static, as described above, and will not be repeated here.

[0203] In practical applications, the red envelope sending result page can be generated by the server after transferring the red envelope resources provided by the second terminal out of the second terminal's user account, or it can be generated by the server after the first terminal receives the red envelope resources. For example, after the server transfers the amount of resources represented by the red envelope amount from the second terminal's user account or to the first terminal's user account, it can generate a red envelope sending result page and send it back to the second terminal. If some problems occur during the resource transfer process, and the red envelope resources are not successfully transferred out of the second terminal's user account or to the first terminal's user account, the server can also generate a red envelope sending result page and send it back to the second terminal.

[0204] The red envelope sending result page can also be generated and displayed from the local data of the second terminal. As one implementation, the second terminal can locally store the page information for the red envelope sending result page. For example, when the second terminal installs a terminal application with red envelope sending functionality, the application's installation package can contain the page information for the red envelope sending result page. After the server completes the relevant red envelope sending process, it sends information or instructions indicating whether the processing was completed successfully to the second terminal. Upon receiving this information or instruction, the second terminal can retrieve the corresponding page information for the red envelope sending result page from its local data, and thus display the red envelope sending result page on the second terminal.

[0205] To further enhance the user experience, this embodiment of the specification may also display an animation effect of sending red envelopes on the second terminal based on the user's operation on the page. Optionally, the red envelope sending page may include one or more red envelopes to be sent; the method further includes:

[0206] Obtain the user's actions regarding the target red envelope on the red envelope sending page;

[0207] Based on the operation direction indicated by the operation, an animation effect is displayed on the red envelope sending page, showing the target red envelope being drawn out of the second terminal along the operation direction;

[0208] Alternatively, based on the operation trajectory indicated by the operation, an animation effect can be displayed on the red envelope sending page to move the target red envelope out of the second terminal along the operation trajectory.

[0209] The red envelope sending page can display virtual images of one or more red envelopes to be sent, such as pictures, cartoon characters, etc.

[0210] In practical applications, the red envelope editing page can also include information about the number of red envelopes. Users can fill in or select the number of red envelopes to send, and this information can include details indicating the number of red envelopes. The number of red envelopes displayed on the red envelope sending page can be the same as the number of red envelopes included in the red envelope information. If the number of red envelopes in the red envelope information is large, such as 10 or 20, the number of red envelopes displayed on the red envelope sending page can be less than the number of red envelopes included in the red envelope information; the red envelope sending page can simply display multiple red envelopes.

[0211] The target red envelope represents the red envelope that the user selects from one or more red envelopes to be sent. The user can perform an operation in the area where the target red envelope is displayed, such as swiping in a certain direction. The second terminal can then display an animation effect showing the target red envelope moving out of the second terminal along the direction or trajectory of the user's operation.

[0212] For example, when a user swipes right on the red envelope sending page, the second terminal can display an animation of the red envelope moving to the right.

[0213] In practical applications, the red envelope sending page can also include operation prompts for users, such as text messages like "swipe right to send a red envelope," "swipe left to send a red envelope," or "swipe up to send a red envelope," or prompts in the form of arrows, etc.

[0214] To improve the accuracy of information processing, if the second terminal sends multiple red envelopes, the server can generate tag information for each red envelope for subsequent processing. Optionally, the red envelope information described in this embodiment may also include red envelope quantity information; if the quantity information indicates multiple red envelopes, the tag information includes multiple sub-tag information; one sub-tag information corresponds to one red envelope; providing the tag information to the first terminal via short-range communication specifically includes: providing each sub-tag information to at least one first terminal via short-range communication.

[0215] The sub-tag information can be a tag corresponding to a red envelope. The sub-tag information can be a string in a preset format or a link. The red envelope generation request sent by the second terminal can include red envelope amount information and red envelope quantity information. The server can generate multiple sub-tag information based on the red envelope generation request. The server can send all or part of the sub-tag information back to the second terminal at once, or it can send one sub-tag information at a time. The second terminal can first write one sub-tag information into the NFC card simulation module. If this sub-tag information is read by a first terminal, another sub-tag information can be written into the NFC card simulation module. Of course, the second terminal can also write multiple sub-tag information obtained at once into the NFC card simulation module. The specific processing method can be set according to actual needs or the actual short-range communication method used, as long as it can send each sub-tag information to one or more first terminals through short-range communication.

[0216] In practical applications, the red envelope editing page can also include options for setting the red envelope amount. For example, users can fill in the corresponding red envelope amount for each individual red envelope, or they can fill in the total amount and then choose a random amount or an average amount, thus eliminating the need for users to set an amount for each red envelope individually. The red envelope editing page can also include information about the red envelope mode, such as regular red envelopes, exclusive red envelopes, single red envelopes, and multiple red envelopes. Different editable information areas can be displayed on the red envelope editing page for different modes.

[0217] For scenarios where multiple red envelopes are sent from a second terminal, the red envelope sending page displayed on the second terminal can also show animation effects of sending multiple red envelopes. These animation effects can include a spray-style red envelope animation, a red envelope rain animation, a money tree animation, and so on.

[0218] In practical applications, the second terminal can also display corresponding animation effects based on the receipt status of each red envelope. For example, after the second terminal provides the first sub-tag information to a first terminal via short-range communication, an animation effect of sending the first red envelope is displayed on the red envelope sending page; the first red envelope is the red envelope corresponding to the first sub-tag information. If the first sub-tag information is provided to a first terminal, and then the second sub-tag information is provided to another first terminal via short-range communication, an animation effect of sending the second red envelope is displayed on the red envelope sending page; the second red envelope is the red envelope corresponding to the second sub-tag information.

[0219] For example, if a user on a second terminal sends three red envelopes (digital cash gifts), and multiple first terminals approach the second terminal simultaneously or at different times, each first terminal can establish a short-range communication connection with the second terminal simultaneously or sequentially. Suppose first terminal A receives a red envelope, the second terminal can display an animation of the red envelope being sent. Then, if another first terminal B receives a red envelope, the second terminal can display an animation of the red envelope being sent. Of course, the second terminal can also display an animation of red envelopes being sent consecutively.

[0220] It is understandable that the above are just examples of some animation effects, and there are other forms of animation effects, which will not be listed here.

[0221] It should be noted that the various pages or animation effects displayed in the first terminal and the various pages or animation effects displayed in the second terminal can be implemented independently of each other. For example, the first terminal can display the animation effect of receiving red envelopes, while the second terminal may not display the animation effect of sending red envelopes.

[0222] Based on the same approach, this specification also provides a method with a server as the execution subject. Figure 4 is a flowchart illustrating a method for processing red envelope interactions with a server as the execution subject, as provided in an embodiment of this specification. From a programming perspective, the execution subject of the process may include a program mounted on the server. From a hardware perspective, the execution subject of the process may include the server.

[0223] As shown in Figure 4, the process may include the following steps.

[0224] Step 402: Obtain the red packet generation request sent by the second terminal for generating red packets in short-range communication mode.

[0225] The red envelope generation request is generated by the second terminal based on the red envelope information edited by the user on the red envelope editing page; the red envelope information includes at least the red envelope amount information;

[0226] Step 404: Generate tag information based on the red envelope generation request.

[0227] The tag information may include identification information related to the red envelope business.

[0228] Step 406: Send the tag information to the second terminal.

[0229] The first terminal, which establishes a short-range communication connection with the second terminal, can send a request to receive a red envelope based on the tag information.

[0230] Step 408: Obtain the red envelope acquisition request sent by the first terminal that has established a short-range communication connection with the second terminal based on the tag information;

[0231] Step 410: Based on the red envelope acquisition request, transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal.

[0232] In practical applications, if there is no first terminal that establishes short-range communication with the second terminal, or if the first terminal does not obtain the tag information in the second terminal, or if the first terminal obtains the tag information but does not send a red envelope acquisition request to the server, or if the server does not obtain the red envelope acquisition request sent by the first terminal, the above steps 408 and 410 may not be executed.

[0233] In the embodiments described in this specification, the server can also generate corresponding page information based on each process in the red envelope interaction and feed it back to the first terminal and / or the second terminal. For example, the red envelope sending page, red envelope sending result page, red envelope receiving page, red envelope receiving result page, etc., described above. Furthermore, the relevant concepts and specific red envelope interaction processing flow involved in this embodiment can also be found in the content of the foregoing embodiments, and will not be repeated here.

[0234] To more clearly illustrate the red envelope interaction processing method provided in this embodiment, Figure 5 is a swimlane diagram of a red envelope interaction processing method provided in this embodiment. As shown in Figure 5, the process may include a red envelope sending stage and a red envelope receiving stage, and may specifically include the following steps.

[0235] Step 502: The second terminal displays the red envelope editing page.

[0236] The red envelope editing page may include an area for editing the red envelope amount. And / or, the red envelope editing page may also include a control indicating confirmation of sending the red envelope. Users edit red envelope information such as the amount on the red envelope editing page.

[0237] Step 504: Send a red envelope generation request to the server based on the red envelope information provided by the user.

[0238] The second terminal can also collect the user's biometric information and send it to the server. After the server verifies the user's identity based on the biometric information, it deducts the amount of resources represented by the red envelope from the user's account on the second terminal. The biometric information can include at least one of the following: face, fingerprint, iris, palm print, voice, etc.

[0239] In practical applications, if the user of the second terminal has already enabled the password-free payment function, the second terminal may not need to collect the user's biometric information.

[0240] Step 506: The server generates tag information based on the red envelope generation request and sends it back to the second terminal.

[0241] The tag information may include information used to trigger the red envelope claiming process.

[0242] To improve user experience, the second terminal can also display a red envelope sending page while the server is processing requests. This page can display information indicating that a red envelope is being sent. Alternatively, the second terminal can also display a red envelope generation page, which can show animations and / or text information such as inserting red envelope resources into the red envelope.

[0243] Step 508: The second terminal is in card emulation mode and saves the tag information.

[0244] The second terminal can activate card emulation mode to save the tag information after receiving it from the server. Alternatively, the second terminal can activate card emulation mode either before or after displaying the red envelope editing page, or before or after generating or sending a red envelope generation request to the server. There is no specific limitation on the timing of activating card emulation mode, as long as it allows the first terminal to obtain the tag information via short-range communication.

[0245] Step 510: The first terminal approaches the second terminal to obtain tag information.

[0246] When the first terminal and the second terminal are within short-range communication range, a short-range communication connection can be established. The first terminal can be in card reader mode and can obtain the tag information of the second terminal through short-range communication.

[0247] During the process of the first terminal obtaining the tag information of the second terminal, the red envelope sending page can also be displayed on the second terminal.

[0248] Step 512: The first terminal parses the tag information and sends a red envelope retrieval request to the server.

[0249] The tag information can be in the form of a link. The first terminal can launch a terminal application capable of receiving red envelopes based on the tag information. By accessing the link address contained in the tag information through the terminal application, a red envelope receiving request can be sent to the server. The red envelope receiving request can also contain the identification information of the first terminal and / or its user, allowing the server to determine the user receiving the red envelope. The red envelope receiving request can also contain business identification information, enabling the server to determine the user sending the red envelope and / or the quantity of red envelope resources corresponding to the request.

[0250] The first terminal can also execute step 514: display the red envelope receiving page.

[0251] After the first terminal obtains the tag information, it can display a red envelope receiving page, which can include an animation indicating the receipt of red envelopes.

[0252] After receiving the red envelope request sent by the first terminal, the server can execute step 516: transfer the red envelope resources to the user account of the first terminal.

[0253] The aforementioned red envelope receiving page can also be a response from the server to the first terminal after receiving the red envelope request. During the server's resource transfer process, the first terminal can display the red envelope receiving page.

[0254] The server can also perform step 518: send the red envelope processing result information to the first terminal and / or the second terminal.

[0255] In this way, the first terminal and / or the second terminal can display the result information. Specifically, the first terminal can execute step 520: display the red envelope receiving result page. The red envelope receiving result page can contain result information, and in addition, it can also contain at least one of the following: red envelope amount information, second terminal user information, and a blessing message.

[0256] The second terminal can execute step 522: display the red envelope sending result page.

[0257] In practical applications, the red envelope sending result page can also be displayed on the second terminal after the red envelope sending process is completed. Specifically, after the server deducts the red envelope resources from the user account of the second terminal, the second terminal can display the red envelope sending result page. For example, the red envelope sending result page can be displayed on the second terminal before the first terminal obtains the tag information, or it can be displayed on the second terminal after the first terminal completes the process of receiving the red envelope, such as after the first terminal successfully receives the red envelope resources. The red envelope sending result page can include result information, and in addition, it can also include at least one of the following: red envelope amount information and information about the first terminal user.

[0258] The above embodiment uses the example of a second terminal sending red envelopes as a card emulator and a first terminal receiving red envelopes as a card reader. In practical applications, the second terminal sending red envelopes can also be a card reader, and the first terminal receiving red envelopes can be a card emulator. As one implementation, the first terminal can have page tag information for triggering the display of a red envelope editing page. After the second terminal, acting as a card reader, reads this page tag information, it can display the red envelope editing page, thus simplifying the operation for the second terminal user to access the red envelope editing page. The page tag information can be generated and fed back by the server based on a request sent by the first terminal. For example, if the user of the first terminal performs an operation to trigger receiving a red envelope, such as a control displaying the words "Receive Red Envelope" on the page of the first terminal's application, after the user performs an operation on this control, the first terminal can send a tag generation request to the server. The server can generate page tag information for triggering the display of the red envelope editing page and feed it back to the first terminal. Thus, the second terminal, being close to the first terminal, can obtain this page tag information through short-range communication, and the red envelope editing page can then be displayed on the second terminal. Then, the second terminal can send a red envelope based on the red envelope information edited by the user on the red envelope editing page. The red envelope interaction process can be the red envelope interaction process described in the above embodiments.

[0259] In another implementation, the second terminal displays a red envelope editing page based on the page tag information provided by the first terminal. The second terminal sends a red envelope sending request to the server, and the server processes the red envelope business according to the request. It can deduct red envelope resources from the user account of the second terminal or add red envelope resources to the user account of the first terminal. The first terminal and / or the second terminal may also display the various red envelope receiving or sending related pages described in the above embodiments. A difference from the above embodiments may include: in this embodiment, the server does not need to send tag information to the second terminal to trigger the red envelope receiving process, and the first terminal does not need to trigger the red envelope receiving process through tag information; the server can automatically execute the relevant processes. In this implementation, the page tag information can correspond to the first terminal. For example, the page tag information can contain the identification information of the first terminal, or the server can store the correspondence between the page tag information and the first terminal. In this way, after the second terminal displays the red envelope editing page based on the page tag information provided by the first terminal, the red envelope sending request sent by the second terminal to the server can contain the identification information of the second terminal and / or some information from the page tag information, such as token information. The red envelope sending request can also contain information such as the red envelope amount. In this way, the server can determine the red envelope sender, the red envelope recipient, and the red envelope amount based on the red envelope sending request sent by the second terminal. Based on this information, the server can execute the relevant red envelope interaction process and complete the transfer of red envelope resources.

[0260] In the above embodiments, even if the user of the second terminal does not know how to send red envelopes or how to send red envelopes through short-range communication, the first terminal can trigger the red envelope editing page to be displayed directly on the second terminal, thereby simplifying the operation of the second terminal user.

[0261] Based on the same idea, embodiments of this specification also provide a device corresponding to the above method. Figure 6 is a structural schematic diagram of a red envelope interaction processing device corresponding to Figure 2 provided in an embodiment of this specification. As shown in Figure 6, the device may include:

[0262] The communication establishment module 602 is used to establish a short-range communication connection with the second terminal;

[0263] The information acquisition module 604 is used to acquire tag information provided by the second terminal through short-range communication; the tag information is generated based on the red envelope information edited by the user on the red envelope editing page displayed on the second terminal; the red envelope information includes at least red envelope amount information;

[0264] The request sending module 606 is used to send a red envelope acquisition request to the server based on the tag information; the server is used to transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal.

[0265] Based on the apparatus in Figure 6, this specification also provides some specific implementation schemes, which are described below.

[0266] Optionally, the tag information includes link information for triggering the red envelope acquisition process; the request sending module 606 can be specifically used to: access the link address represented by the link information; and send a red envelope acquisition request to the server based on the link address.

[0267] Optionally, the tag information includes identification information of the target application used to receive the red envelope; the device further includes an application launch module, specifically used to: launch the target application based on the identification information. The request sending module 606 can specifically be used to: send a red envelope acquisition request to the server based on the launched target application.

[0268] Optionally, the above device may further include a page display module, which can be used to: display a red envelope receiving page; the red envelope receiving page includes a prompt message indicating that a red envelope is being received; and / or, display a red envelope receiving result page; the red envelope receiving result page includes result information indicating the red envelope receiving result.

[0269] Optionally, the prompt information includes at least one of the following: an animation effect of the transfer process of the red envelope to the first terminal, text information indicating that a red envelope is being received, and voice information indicating that a red envelope is being received; the result information includes at least one of the following: an animation effect indicating that a red envelope has been received, text information indicating that a red envelope has been received, and voice information indicating that a red envelope has been received.

[0270] Optionally, the above-mentioned device is further configured to: if a first operation indicating that the user is opening a red envelope is obtained based on the red envelope receiving page, then display an animation effect of opening the red envelope; or, if a second operation indicating that the user is confirming receipt of the red envelope is obtained based on the red envelope receiving page, then display an animation effect of placing the red envelope into the first terminal; or, if a third operation indicating that the user is refusing to receive the red envelope is obtained based on the red envelope receiving page, then display an animation effect of transferring the red envelope out of the first terminal.

[0271] Optionally, the animation effect of transferring the red envelope into the first terminal can be: an animation effect of transferring the red envelope from a preset edge of the first terminal into the first terminal; the preset edge is any edge of the first terminal, an edge of the first terminal close to the second terminal, or any edge of the first terminal in the opposite direction to the edge of the second terminal from which the red envelope is transferred out.

[0272] Optionally, the voice information includes information about the sender of the red envelope; the information about the sender of the red envelope includes the name information recorded by the user of the second terminal in the first terminal.

[0273] Figure 7 is a structural schematic diagram of a red envelope interaction processing device corresponding to Figure 3 provided in an embodiment of this specification. As shown in Figure 7, the device may include:

[0274] The information acquisition module 702 is used to acquire red envelope information edited by the user on the red envelope editing page; the red envelope information includes at least red envelope amount information;

[0275] The request sending module 704 is used to send a red packet generation request for generating a short-range communication mode red packet to the server based on the red packet information;

[0276] The tag information acquisition module 706 is used to acquire the tag information fed back by the server based on the red envelope generation request;

[0277] The tag information sending module 708 is used to provide the tag information to the first terminal via short-range communication; the first terminal is used to receive the amount of resources represented by the red envelope amount information based on the tag information.

[0278] Based on the apparatus in Figure 7, this specification also provides some specific implementation schemes, which are described below.

[0279] Optionally, the short-range communication is NFC near-field communication; the device is further configured to: enable the second terminal to activate the NFC card emulation mode; and save the tag information in the NFC card emulation mode so that the first terminal in the NFC reader mode can read the tag information.

[0280] Optionally, the device may further include a page display module, specifically used for: displaying a red envelope sending page; the red envelope sending page containing prompt information indicating that a red envelope is being sent; and / or, displaying a red envelope sending result page; the red envelope sending result page containing result information indicating the red envelope sending result.

[0281] Optionally, the prompt information includes at least one of the following: an animation effect of the red envelope being transferred out of the second terminal, text information indicating that a red envelope is being sent, and voice information indicating that a red envelope is being sent; the result information includes at least one of the following: an animation effect indicating that the red envelope sending has ended, text information indicating that the red envelope sending has ended, and voice information indicating that the red envelope sending has ended.

[0282] Optionally, the animation effect of transferring the red envelope out of the second terminal is linked to the animation effect of transferring the red envelope into the first terminal.

[0283] Optionally, the red envelope sending page includes one or more red envelopes to be sent; the device can also be used to: acquire the user's operation on the red envelope sending page for the target red envelope; based on the operation direction indicated by the operation, display an animation effect on the red envelope sending page of drawing the target red envelope out of the second terminal along the operation direction; or, based on the operation trajectory indicated by the operation, display an animation effect on the red envelope sending page of moving the target red envelope out of the second terminal along the operation trajectory.

[0284] Optionally, the red envelope information also includes red envelope quantity information; if the red envelope quantity information represents a quantity of multiple red envelopes, the tag information includes multiple sub-tag information; one sub-tag information corresponds to one red envelope; the step of providing the tag information to the first terminal through short-range communication specifically includes: providing each of the sub-tag information to at least one first terminal through short-range communication.

[0285] Figure 8 is a structural schematic diagram of a red envelope interaction processing device corresponding to Figure 4 provided in an embodiment of this specification. As shown in Figure 8, the device may include:

[0286] The first request acquisition module 802 is used to acquire a red envelope generation request sent by the second terminal for generating a red envelope in short-range communication mode; the red envelope generation request is generated by the second terminal based on the red envelope information edited by the user in the red envelope editing page; the red envelope information includes at least red envelope amount information;

[0287] The tag information generation module 804 is used to generate tag information based on the red envelope generation request;

[0288] Tag information sending module 806 is used to send the tag information to the second terminal;

[0289] The second request acquisition module 808 is used to acquire a red envelope acquisition request sent by the first terminal that has established a short-range communication connection with the second terminal based on the tag information.

[0290] The resource transfer module 810 is used to transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal based on the red envelope acquisition request.

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

[0292] Figure 9 is a structural schematic diagram of a red envelope interaction processing device provided in an embodiment of this specification. As shown in Figure 9, the device 900 may include:

[0293] At least one processor 910; and,

[0294] Memory 930 communicatively connected to the at least one processor; wherein,

[0295] The memory 930 stores instructions 920 that can be executed by the at least one processor 910, which, when executed by the at least one processor 910, enables the at least one red envelope interaction processing method described above to be executed.

[0296] Based on the same approach, embodiments of this specification also provide a computer-readable medium corresponding to the above-described methods. The computer-readable medium stores computer-readable instructions, which can be executed by a processor to implement at least one of the above-described red envelope interaction processing methods.

[0297] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the device shown in FIG9 is basically similar to the method embodiment, so the description is relatively simple; relevant parts can be referred to the description of the method embodiment.

[0298] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use and processing of the relevant data must comply with the relevant laws, regulations and standards of the relevant regions, and corresponding operation portals are provided for users to choose to authorize or refuse.

[0299] 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 and "integrate" a digital system onto a PLD themselves, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, 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, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0300] 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: ARC 625D, 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, application-specific integrated circuits, 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.

[0301] 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, laptop computer, cellular phone, camera phone, smartphone, personal digital assistant, media player, navigation device, email device, game console, tablet computer, wearable device, or any combination of these devices.

[0302] 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.

[0303] 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.

[0304] 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, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.

[0305] 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 that implement the functions specified in one or more flowcharts and / or one or more block diagrams.

[0306] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.

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

[0308] 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.

[0309] 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 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.

[0310] 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.

[0311] 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.

[0312] 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.

[0313] 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 handling red envelope interactions, applied to a first terminal, comprising: Establish a short-range communication connection with the second terminal; The tag information provided by the second terminal is obtained through short-range communication. The tag information is generated based on the red envelope information edited by the user on the red envelope editing page displayed on the second terminal; the red envelope information includes at least the red envelope amount information; Based on the tag information, a request to receive a red envelope is sent to the server; The server is used to transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal.

2. The method according to claim 1, wherein the tag information includes link information for triggering the red envelope acquisition process; the step of sending a red envelope acquisition request to the server based on the tag information specifically includes: Access the link address represented by the link information; Based on the link address, a request to receive a red envelope is sent to the server.

3. The method according to claim 1, wherein the tag information includes identification information of the target application used to receive the red envelope; The method further includes: Based on the identification information, the target application is launched; The process of sending a red envelope request to the server specifically includes: Based on the launched target application, a request to receive a red envelope is sent to the server.

4. The method according to claim 1, further comprising, after sending the red envelope retrieval request to the server: The page for receiving red envelopes is displayed; the page includes a notification indicating that a red envelope is being received. And / or, display the red envelope receiving results page; The red envelope receiving results page contains result information indicating the red envelope receiving results.

5. The method according to claim 4, wherein the prompt information includes: The process of transferring the red envelope to the first terminal includes at least one of the following: animation effect indicating that the red envelope is being received, text information indicating that the red envelope is being received, and voice information indicating that the red envelope is being received; the result information includes at least one of the following: animation effect indicating that the red envelope has been received, text information indicating that the red envelope has been received, and voice information indicating that the red envelope has been received.

6. The method according to claim 5, further comprising: If the user's first operation, indicating opening a red envelope, is detected on the red envelope receiving page, then the animation effect of opening the red envelope is displayed; Alternatively, if a second operation indicating confirmation of receiving the red envelope is obtained from the user based on the red envelope receiving page, then an animation effect of putting the red envelope into the first terminal is displayed; Alternatively, if a third operation indicating that the user refuses to receive the red envelope is detected based on the red envelope receiving page, an animation effect of transferring the red envelope out of the first terminal is displayed.

7. The method according to claim 5, wherein the animation effect of the transfer process of transferring the red envelope to the first terminal specifically includes: An animation effect that transfers the red envelope from a preset edge of the first terminal into the first terminal; the preset edge is any edge of the first terminal, any edge of the first terminal that is close to the second terminal, or any edge of the first terminal that is in the opposite direction to the edge of the second terminal from which the red envelope is transferred out.

8. The method according to claim 5, wherein the voice information includes information of the sender of the red envelope; the information of the sender of the red envelope includes the name information recorded by the user of the second terminal in the first terminal.

9. A method for processing red envelope interactions, applied to a second terminal, comprising: Retrieve the red envelope information edited by the user on the red envelope editing page; The red envelope information includes at least the red envelope amount information; Based on the red envelope information, a red envelope generation request for generating short-range communication mode red envelopes is sent to the server; Obtain the tag information returned by the server based on the red envelope generation request; The tag information is provided to the first terminal via short-range communication. The first terminal is used to receive the amount of resources represented by the red envelope amount information based on the tag information.

10. The method according to claim 9, wherein the short-range communication is NFC near-field communication; the method further includes: The second terminal enables NFC card emulation mode; The tag information is saved in the NFC card emulation mode so that the first terminal in NFC reader mode can read the tag information.

11. The method according to claim 9, further comprising: Displays a red envelope sending page; the red envelope sending page includes a prompt message indicating that a red envelope is being sent; And / or, display the red envelope sending results page; The red envelope sending results page contains result information indicating the red envelope sending results.

12. The method according to claim 11, wherein the prompt information includes at least one of the following: an animation effect of the red envelope being transferred out of the second terminal, text information indicating that a red envelope is being sent, and voice information indicating that a red envelope is being sent; the result information includes: An animation effect indicating the end of sending a red envelope, a text message indicating the end of sending a red envelope, or a voice message indicating the end of sending a red envelope.

13. The method according to claim 12, wherein the animation effect of transferring the red envelope out of the second terminal and the animation effect of transferring the red envelope into the first terminal displayed in the first terminal are linked to the animation effect of transferring the red envelope.

14. The method according to claim 11, wherein the red envelope sending page includes one or more red envelopes to be sent; the method further includes: Obtain the user's actions regarding the target red envelope on the red envelope sending page; Based on the operation direction indicated by the operation, an animation effect is displayed on the red envelope sending page, showing the target red envelope being drawn out of the second terminal along the operation direction; Alternatively, based on the operation trajectory indicated by the operation, an animation effect can be displayed on the red envelope sending page to move the target red envelope out of the second terminal along the operation trajectory.

15. The method according to claim 9, wherein the red envelope information further includes red envelope quantity information; if the red envelope quantity information represents a quantity of multiple red envelopes, the tag information includes multiple sub-tag information; one sub-tag information corresponds to one red envelope; the step of providing the tag information to the first terminal via short-range communication specifically includes: The information of each sub-tag is provided to at least one first terminal via short-range communication.

16. A method for processing red envelope interactions, applied to a server, comprising: Obtain the red packet generation request sent by the second terminal for generating red packets in short-range communication mode; The red envelope generation request is generated by the second terminal based on the red envelope information edited by the user on the red envelope editing page; The red envelope information includes at least the red envelope amount information; Based on the aforementioned red envelope generation request, tag information is generated; Send the tag information to the second terminal; Obtain a red envelope retrieval request sent by the first terminal, which has established a short-range communication connection with the second terminal, based on the tag information; Based on the request for the red envelope, the amount of resources represented by the red envelope amount information is transferred to the user account of the first terminal.

17. A red envelope interaction processing device, applied to a first terminal, comprising: A communication establishment module is used to establish a short-range communication connection with the second terminal; The information acquisition module is used to acquire tag information provided by the second terminal through short-range communication; the tag information is generated based on the red envelope information edited by the user on the red envelope editing page displayed on the second terminal; the red envelope information includes at least the red envelope amount information; The request sending module is used to send a red envelope acquisition request to the server based on the tag information; The server is used to transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal.

18. A red envelope interaction processing device, applied to a second terminal, comprising: The information acquisition module is used to acquire the red envelope information edited by the user on the red envelope editing page; The red envelope information includes at least the red envelope amount information; The request sending module is used to send a red packet generation request to the server based on the red packet information, which is used to generate red packets in the short-range communication mode. The tag information acquisition module is used to acquire the tag information fed back by the server based on the red envelope generation request; The tag information sending module is used to provide the tag information to the first terminal via short-range communication. The first terminal is used to receive the amount of resources represented by the red envelope amount information based on the tag information.

19. A red envelope interaction processing device, applied to a server, comprising: The first request acquisition module is used to acquire the red packet generation request sent by the second terminal for generating red packets in the short-range communication mode; The red envelope generation request is generated by the second terminal based on the red envelope information edited by the user on the red envelope editing page; The red envelope information includes at least the red envelope amount information; The tag information generation module is used to generate tag information based on the red envelope generation request; A tag information sending module is used to send the tag information to the second terminal; The second request acquisition module is used to acquire the red envelope acquisition request sent by the first terminal that has established a short-range communication connection with the second terminal based on the tag information; The resource transfer module is used to transfer the amount of resources represented by the red envelope amount information to the user account of the first terminal based on the red envelope acquisition request.

20. A red envelope interaction processing device, comprising: At least one processor; as well as, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, which, when executed by the at least one processor, enables the at least one processor to perform the red envelope interaction processing method according to any one of claims 1 to 16.

21. A computer-readable medium having stored thereon computer-readable instructions that can be executed by a processor to implement the red envelope interaction processing method according to any one of claims 1 to 16.

Images