Red envelope interaction processing method and device, equipment and medium

Abstract

The embodiment of the invention discloses a red envelope interaction processing method and device, equipment and a medium. The scheme comprises: establishing a short-distance communication connection with a second terminal; obtaining label information provided by the second terminal through a short-distance communication mode; the label information is generated based on red envelope information edited by a user in a red envelope editing page displayed by the second terminal; the red envelope information at least comprises red envelope amount information; based on the label information, sending a red envelope acquisition request to a server; and the server is used for transferring the resource of the quantity represented by the red envelope amount information to a user account of the first terminal.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a red envelope interactive processing method, device, equipment and medium. Background Art

[0002] Digital payments are becoming more and more developed and widely used. For example, payment can be made by scanning a QR code. Another example is the distribution of red envelopes and lucky money during the Chinese New Year, which can be completed through online transfers.

[0003] In the prior art, when sending a red envelope through online transfer, the recipient usually receives the red envelope prompt information, clicks on the information or opens the terminal application, and clicks to receive the red envelope. Even in a face-to-face scenario, the user needs to perform multiple steps to obtain the red envelope.

[0004] Therefore, how to improve the convenience of red envelope interaction is a technical problem that needs to be solved urgently. Summary of the invention

[0005] The embodiments of this specification provide a red envelope interaction processing method, device, equipment and medium to solve the problem of complex operation in existing red envelope interaction methods.

[0006] To solve the above technical problems, the embodiments of this specification are implemented as follows: A red envelope interaction processing method provided in an embodiment of the present specification is applied to a first terminal, including: establishing a short-range communication connection with a second terminal; Acquiring tag information provided by the second terminal by means of short-distance communication; the tag information is generated based on the red envelope information edited by the user in the red envelope editing page displayed by the second terminal; the red envelope information at least includes red envelope amount information; Based on the tag information, a red envelope acquisition request is sent to a server; the server is used to transfer resources of a quantity indicated by the red envelope amount information to a user account of the first terminal.

[0007] A red envelope interaction processing method provided in an embodiment of the present specification is applied to a second terminal, including: Obtain the red envelope information edited by the user in the red envelope editing page; the red envelope information at least includes the red envelope amount information; Based on the red envelope information, sending a red envelope generation request for generating a short-distance communication mode red envelope to a server; Obtaining label information of the server based on the red envelope generation request feedback; The tag information is provided to a first terminal by means of short-distance communication; the first terminal is used to collect resources of a quantity indicated by the red envelope amount information based on the tag information.

[0008] A red envelope interaction processing method provided in an embodiment of the present specification is applied to a server, including: Obtaining a red envelope generation request for generating a short-distance communication mode red envelope sent by the second terminal; 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 at least includes red envelope amount information; Generate label information based on the red envelope generation request; Sending the tag information to the second terminal; Obtaining a red envelope obtaining request sent by the first terminal that establishes a short-distance communication connection with the second terminal based on the tag information; Based on the red envelope acquisition request, resources of a quantity indicated by the red envelope amount information are transferred to a user account of the first terminal.

[0009] The embodiment of this specification provides a red envelope interaction processing device, which is applied to a first terminal and includes: A communication establishing module, used to establish a short-distance communication connection with a second terminal; an information acquisition module, configured to acquire tag information provided by the second terminal by means of short-distance communication; the tag information is generated based on the red envelope information edited by the user in the red envelope editing page displayed by the second terminal; the red envelope information at least includes red envelope amount information; A request sending module is used to send a red envelope acquisition request to a 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.

[0010] The embodiment of this specification provides a red envelope interaction processing device, which is applied to a second terminal, including: An information acquisition module, used to acquire the red envelope information edited by the user in the red envelope editing page; the red envelope information at least includes the red envelope amount information; A request sending module, used for sending a red envelope generation request for generating a short-distance communication mode red envelope to a server based on the red envelope information; A tag information acquisition module, used to acquire 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 through short-distance communication; the first terminal is used to collect the resources of the quantity indicated by the red envelope amount information based on the tag information.

[0011] The embodiment of this specification provides a red envelope interaction processing device, which is applied to a server and includes: A first request acquisition module is used to acquire a red envelope generation request for generating a short-distance communication mode red envelope sent by a second terminal; 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 at least includes red envelope amount information; A label information generating module, used for generating label information based on the red envelope generating request; A label information sending module, used for sending the label information to the second terminal; A second request acquisition module, used to acquire a red envelope acquisition request sent by the first terminal that establishes a short-distance communication connection with the second terminal based on the tag information; A 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.

[0012] A red envelope interaction processing device provided in an embodiment of the present specification includes: at least one processor; and, 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, and the instructions are executed by the at least one processor so that the at least one processor can execute the at least one red envelope interaction processing method mentioned above.

[0013] An embodiment of the present specification provides a computer-readable medium on which computer-readable instructions are stored. The computer-readable instructions can be executed by a processor to implement at least one of the above-mentioned red envelope interaction processing methods.

[0014] At least one embodiment of this specification can achieve the following beneficial effects: As a terminal for receiving red envelopes, the first terminal can establish a short-distance communication connection with the second terminal that sends red envelopes, and obtain the tag information provided by the second terminal through short-distance communication. After obtaining the tag information, the first terminal can send a red envelope acquisition request to the server based on the tag information, and then the first terminal can obtain the red envelope resources. Among them, the first terminal sends a red envelope acquisition request to the server based on the tag information obtained by the short-distance communication method. The user only needs to bring the first terminal and the second terminal close together so that the first terminal can obtain the tag information through short-distance communication to trigger the red envelope collection process. The red envelope resources can be obtained without the user performing too many operations, which can simplify user operations. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0016] Figure 1 This is a schematic diagram of the overall solution of a red envelope interaction processing method in an embodiment of this specification; Figure 2 A flowchart of a red envelope interaction processing method provided in an embodiment of this specification; Figure 3 A flowchart of a red envelope interaction processing method with a second terminal as the execution subject provided in an embodiment of this specification; Figure 4 A flowchart of a method for red envelope interaction processing with a server as the execution subject provided in an embodiment of this specification; Figure 5 A swimlane diagram of a red envelope interactive process provided in an embodiment of this specification; Figure 6 The embodiments of this specification provide corresponding to Figure 2 A structural schematic diagram of a red envelope interactive processing device; Figure 7 The embodiments of this specification provide corresponding to Figure 3 A structural schematic diagram of a red envelope interactive processing device; Figure 8 The embodiments of this specification provide corresponding to Figure 4 A structural schematic diagram of a red envelope interactive processing device; Fig. 9 A structural schematic diagram of a red envelope interaction processing device provided in an embodiment of this specification. DETAILED DESCRIPTION

[0017] In order to make the purpose, 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 combination with the specific embodiments of this specification and the corresponding drawings. Obviously, the described embodiments are only part of the embodiments of this specification, not all of the embodiments. Based on the embodiments in this specification, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of one or more embodiments of this specification.

[0018] In order to more clearly understand the technical solution provided in this specification, some terms are explained below.

[0019] Digital payments refer to payment methods for transactions that are made electronically. It involves using a mobile device, computer or other electronic device to make payments, rather than using cash or traditional bank transfers.

[0020] Near Field Communication (NFC) is a short-range wireless communication technology that allows devices to exchange data when they are very close (usually within 4 cm). NFC technology is based on Radio Frequency Identification (RFID) technology and can provide multiple functions such as data transmission, communication and near-field payment.

[0021] Red envelopes are a form of gift in traditional Chinese culture, usually given to relatives, friends, colleagues or subordinates during festivals, celebrations or special occasions to express blessings and auspiciousness. Red envelopes usually contain cash and are wrapped in red paper, symbolizing good luck and happiness. In modern society, especially during festivals such as the Spring Festival, the form of red envelopes has gradually expanded to electronic red envelopes, such as virtual red envelopes sent through terminal applications with payment functions or mobile payment platforms.

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

[0023] In order to solve the defects in the prior art, this solution provides the following embodiments: Figure 1 Schematic diagram of the overall solution of a red envelope interaction processing method in the embodiment of this specification. Figure 1 As shown, the first terminal 1 is the device of the red envelope acquirer, and the second terminal 2 is the device of the red envelope sender. The user of the second terminal 2 can edit the red envelope amount and other information to generate a virtual red envelope. The user of the first terminal 1 brings 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 close together, so that the first terminal 1 is within the short-distance communication range of the second terminal 2, so that the first terminal 1 can obtain the tag information in the second terminal 2, and then the first terminal 1 can send a red envelope acquisition request to the server based on the tag information, and 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.

[0024] The first terminal 1 and the second terminal 2 may be mobile terminals, such as smart phones, tablet computers, smart watches, portable game consoles, and the like. One of the first terminal 1 and the second terminal 2 may also be a fixed terminal, such as a POS machine, a cash register, an advertising device, and the like. The first terminal 1 and the second terminal 2 may be of the same or different types, as long as they have a short-distance communication function, and are not specifically limited here.

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

[0026] Figure 2 A flowchart of a red envelope interaction processing method provided in an embodiment of this specification. From a program perspective, the execution subject of the process may include a program installed on the first terminal. Among them, the program may include a system program of the terminal system, and may also include an application client installed in the terminal. From a hardware perspective, the execution subject of the process may include the first terminal.

[0027] like Figure 2 As shown, the process may include the following steps.

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

[0029] The first terminal is the terminal of the red envelope recipient, and the second terminal is the terminal of the red envelope sender. The first terminal and the second terminal have a short-distance communication function. When the first terminal and the second terminal are within the range of short-distance communication, the two can establish a short-distance communication connection. Among them, short-distance communication can refer to communication that can only be generated within a shorter distance, such as NFC communication, Bluetooth communication, etc., or other forms of short-distance communication.

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

[0031] Among them, the label information is generated based on the red envelope information edited by the user in the red envelope editing page displayed on the second terminal; the red envelope information at least includes red envelope amount information.

[0032] The second terminal is used as a terminal for providing or sending red envelopes, and the user can edit the red envelope information such as the red envelope amount on the red envelope editing page of the second terminal. The second terminal can generate tag information for triggering the red envelope collection process based on the red envelope information edited by the user, or the second terminal can send the red envelope information edited by the user to the server, and the server generates the tag information and then feeds it back to the second terminal, and then the second terminal can save the tag information. After the first terminal establishes a short-distance communication connection with the second terminal, the first terminal can obtain the tag information in the second terminal.

[0033] In actual applications, the user of the second terminal can send red envelopes through a terminal application or mini-program with a red envelope sending function. The red envelope editing page can be a page in the terminal application or mini-program, and the user edits the red envelope information in the page.

[0034] In actual applications, if the first terminal is in a locked state, the user can first unlock the first terminal, and then establish short-distance communication between the first terminal and the second terminal, so that the first terminal can obtain the tag information. If the short-distance communication function of the first terminal can be used in a locked state, and the first terminal can parse the tag information in a locked state, it is also unnecessary to unlock the first terminal. Whether the first terminal needs to be unlocked can be set according to actual needs, and is not specifically limited here.

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

[0036] The server is used to transfer the amount of resources indicated by the red envelope amount information to the user account of the first terminal.

[0037] After the first terminal obtains the tag information, the red envelope acquisition process is triggered based on the tag information. Specifically, a red envelope acquisition request can be sent to the server. The red envelope acquisition request can include the identification information of the first terminal and can also include at least part of the information in the tag information, for example, it can include information used to determine 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 obtaining the red envelope acquisition request sent by the first terminal.

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

[0039] Figure 2 In the method, a first terminal establishes a short-distance communication connection with a second terminal, obtains tag information provided by the second terminal by means of short-distance communication, and after obtaining the tag information, the first terminal can send a red envelope acquisition request to a server based on the tag information, and then the first terminal can obtain red envelope resources. Among them, the first terminal sends a red envelope acquisition request to a server based on the tag information obtained by means of short-distance communication. The user only needs to bring the first terminal and the second terminal close together so that the first terminal can obtain the tag information by means of short-distance communication to trigger the red envelope collection process. The red envelope resources can be obtained without the user performing too many operations, thereby simplifying user operations.

[0040] On the other hand, the first terminal needs to obtain the label information provided by the second terminal through short-distance communication, so as to receive the red envelope resources. That is, the distance between the first terminal and the second terminal needs to be relatively close. For example, the first terminal can obtain the red envelope resources by sticking or touching. In the process of red envelope interaction, it can also enhance the user's sense of participation and ritual, thereby improving the user experience.

[0041] based on Figure 2 The present specification also provides some specific implementation plans in the examples, which are described below.

[0042] Optionally, in the embodiment of this specification, the tag information may include link information for triggering the red envelope acquisition process. The above-mentioned sending 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.

[0043] The tag information may be information in a link form, or tag information containing information in a link form, such as information in a link form starting with a string such as http or https.

[0044] After the first terminal obtains the tag information, it can parse the content of the tag information to obtain the link information in the tag information. The first terminal can access the link address represented by the link information through the system browser or the built-in browser of the terminal application, and the link address enables the first terminal to interact with the server. The server can be a server corresponding to the link address and can process the related business corresponding to the link address.

[0045] In actual applications, the red envelope interaction process such as sending a red envelope, receiving a red envelope, etc. can be performed in a terminal application or applet with a red envelope interaction function. As an implementation method, the tag information includes identification information of a target application for receiving a red envelope; if the target application is not started in the first terminal, the method further includes: starting the target application based on the identification information.

[0046] Correspondingly, the sending of the red envelope acquisition request to the server may specifically include: based on the started target application, sending the red envelope acquisition request to the server.

[0047] Among them, the first terminal may have a short-distance communication module, and the tag information is obtained through the short-distance communication module, and the terminal system program can parse the content in the tag information. If the tag information contains the identification information of the target application, the terminal system can trigger the terminal to start the target application. In the embodiment of this specification, a red envelope acquisition request can be sent to the server through the started target application. The server can be a server that can handle the services related to the target application.

[0048] If the target application has been started in the first terminal but is in the background, the target application running in the background can also send a red envelope acquisition request to the server. The first terminal can also switch the target application to the foreground and then send a red envelope acquisition request to the server.

[0049] In actual applications, if the target application is not installed in the first terminal, the first terminal may also display a prompt message prompting the user to install the target application in the acquired tag information. The prompt message may be generated by the server and fed back to the first terminal; or it may be provided by the first terminal locally or by the system server of the first terminal according to the agreement between the provider of the first terminal and the provider of the target application.

[0050] To improve user experience, the first terminal may also display at least one of the information about the red envelope received and the information about the result of the red envelope received. Optionally, after sending the red envelope acquisition request to the server in the embodiment of this specification, the following may also be included: Display a red envelope collection page; the red envelope collection page includes prompt information indicating that the red envelope is being collected; and / or, display a red envelope collection result page; the red envelope collection result page includes result information indicating the red envelope collection result.

[0051] In actual applications, the first terminal may display one of the red envelope receiving page and the red envelope receiving result page, or may display both pages.

[0052] For example, after the first terminal obtains the tag information provided by the second terminal for triggering the red envelope collection process through short-distance communication, the server can process the red envelope acquisition request initiated by the first terminal. After the request is processed, the page information of the red envelope collection result page is sent to the first terminal, and the first terminal can display the red envelope collection result page.

[0053] For another example, after obtaining the red envelope acquisition request sent by the first terminal, the first server can feedback the page information of the red envelope receiving page to the first terminal, and the first terminal can display the red envelope receiving page indicating that the red envelope is being received. During the process of displaying the red envelope receiving page on the first terminal, the server can execute relevant processes for processing the red envelope acquisition request sent by the first terminal, for example, determine the relevant information of the user account of the first terminal based on the request, and transfer the red envelope resources to the user account of the first terminal.

[0054] For another example, after the first terminal sends a red envelope acquisition request to the server through the tag information provided by the second terminal, the first terminal may first display a red envelope collection page, and then display a red envelope collection result page after the first terminal finishes collecting the red envelope.

[0055] 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 embodiment of this specification, the prompt information indicating that the 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.

[0056] The red envelope receiving page may also include information representing a virtual image of the red envelope, such as text, characters, pictures, etc. For example, the red envelope receiving page may display an image or animated image of a red envelope cover with a red background; the red envelope receiving page may also display a static or dynamic virtual image in the form of a gold ingot, a virtual image representing a currency symbol, or some cartoon images containing red envelope features.

[0057] The red envelope receiving page can display a static virtual image of the red envelope, or a dynamic virtual image of the red envelope, such as a static red envelope cover, cartoon image, etc.; or a dynamic animation effect, such as a virtual image of the red envelope that displays dynamic information in the form of rotation, flying in, shaking, changing from small to large, etc.

[0058] The red envelope receiving page can be a page generated by the local information of the first terminal after the first terminal obtains the tag information, or it can be a page fed back by the server. As an implementation method, after the first terminal sends a red envelope obtaining request to the server based on the tag information, the server can generate page information of the red envelope receiving page based on the red envelope obtaining request and feed it back to the first terminal, so that the first terminal can display the red envelope receiving page. As another implementation method, the page information of the red envelope receiving page can be locally stored in the first terminal. For example, when the first terminal installs a terminal application with a red envelope receiving function, the installation package of the terminal application can include the page information of the red envelope receiving page. After the first terminal obtains the tag information, it can obtain the page information of the red envelope receiving page from the local data through the terminal application, and then the red envelope receiving page can be displayed in the first terminal.

[0059] Optionally, the prompt information indicating that the red envelope is being received may include at least one of an animation effect of the transfer process of transferring the red envelope to the first terminal, a text message indicating that the red envelope is being received, and a voice message indicating that the red envelope is being received.

[0060] Among them, the animation effect of the transfer process of the red envelope into the first terminal can present to the user 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 changing from light to dark, from small to large and being displayed on the first terminal, etc.

[0061] The text information indicating that the red envelope is being received may be information in the form of text that prompts the user that the red envelope is being received, such as the words "receiving red envelope" and "receiving red envelope". The text information may be static or dynamic.

[0062] The voice message indicating that a red envelope is being collected may be information in the form of voice that prompts the user that a red envelope is being collected, such as voice broadcast messages such as "You are collecting a red envelope", "Red envelope being collected", "Big red envelope coming", etc.

[0063] In order to further improve the user experience and make the digital red envelope more ceremonial, as an implementation method, the animation effect of the transfer process of transferring the red envelope to the first terminal can be specifically: the animation effect of transferring the red envelope from a preset edge of the first terminal to the first terminal; the preset edge is any edge of the first terminal, the edge of the first terminal close to the second terminal, and any edge of the first terminal in the opposite direction of the edge of the second terminal from which the red envelope is transferred.

[0064] In actual applications, the animation effect displayed in the first terminal can be determined according to the relative position of the first terminal and the second terminal when the first terminal establishes short-distance communication with the second terminal. For example, assuming that the first terminal and the second terminal are placed in the same direction, the first terminal approaches the second terminal from the right side of the second terminal to establish short-distance communication with the second terminal, and the first terminal can display a visual effect of a red envelope sliding in from the left side of the first terminal and moving to the right. For another example, if the top of the first terminal is located at the bottom of the second terminal, the first terminal approaches the second terminal by bringing the top close to the bottom of the second terminal to establish short-distance communication with the second terminal, and the first terminal displays a visual effect of a red envelope sliding in from the top of the first terminal.

[0065] If the placement directions of the first terminal and the second terminal are inconsistent, such as the top of the first terminal is close to the top of the second terminal, the first terminal may also display a visual effect of a red envelope being swiped in from the top of the first terminal.

[0066] For another example, if the second terminal displays an animation effect of a red envelope being swiped out from the right edge of the second terminal, the first terminal may display an animation effect of a red envelope being swiped in from the left side of the first terminal.

[0067] It can be understood that the above are only a few examples. In actual applications, the visual effect of the display can be determined according to the relative positions of the first terminal and the second terminal. There is no specific limitation here, as long as the visual effect of showing that the red envelope is transferred to the first terminal can be displayed.

[0068] In actual applications, the animation effect of the red envelope transfer displayed in the first terminal can also be an animation effect displayed in linkage with the animation effect of the red envelope transfer displayed in the second terminal. For example, the second terminal dynamically displays the visual effect of the red envelope transfer out of the second terminal. At a certain moment, the second terminal displays a part of the information contained, such as a part of the red envelope card, or a part of the virtual image. The other part of the information has been displayed in 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 visual effect of sending and receiving red envelopes in linkage can be displayed in the first terminal and the second terminal, so that the user can feel that the red envelope in the second terminal is sent to the first terminal.

[0069] In actual applications, the animation effects displayed on the red envelope receiving page in the first terminal and the animation effects displayed on the red envelope sending page in the first terminal can be displayed synchronously or asynchronously, which can be set according to actual conditions.

[0070] The red envelope collection result page may indicate the page displayed after the first terminal completes the collection of the red envelope, and the page may include information indicating that the red envelope has been successfully received; if the first terminal fails to successfully obtain the red envelope due to network instability or other reasons, the red envelope collection result page may also display information indicating that the red envelope has not been successfully received.

[0071] Optionally, the result information indicating the result of receiving the red envelope may include at least one of: 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.

[0072] Among them, the animation effect indicating that a red envelope has been received can be a visual effect indicating that a red envelope has been received in the form of animation. For example, the receipt of a red envelope is indicated in the form of a cartoon image, a red envelope picture, or an artistic font. The text information indicating that a red envelope has been received is information indicating that a red envelope has been received in the form of text. For example, text information such as "You have received a new red envelope". The voice information indicating that a red envelope has been received is information indicating that a red envelope has been received in the form of voice. For example, information in the form of voice broadcasts such as "You have received a new red envelope". It can also be information prompt sounds such as "beep" and "ding".

[0073] In practical applications, the result information may be dynamic information or static information, for example, the result information may be displayed in the form of static text, or in the form of an animation including a virtual image of a red envelope, and so on.

[0074] As an implementation mode, at least one of the voice message indicating that a red envelope is being received and the voice message indicating that a red envelope has been received may include information about the sender of the red envelope, so that the user of the first terminal can know who sent the red envelope to him / her.

[0075] In the implementation application, the information of the red envelope sender may include the name information of the user of the second terminal recorded in the first terminal.

[0076] The user of the second terminal may be a friend, contact, etc. of the user of the first terminal. The user of the first terminal may note 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 may also record the name information set by the user of the second terminal himself.

[0077] If the first terminal does not record relevant information of the user of the second terminal, or the user of the first terminal and the user of the second terminal have not previously used the first terminal to contact the second terminal, or there has been no contact 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, and the name information may be the name information set by the user of the second terminal himself.

[0078] In actual applications, the above-mentioned text information, animation effects, etc. displayed on the page may also include relevant information of the second terminal user. It should be noted that the user-related information used in the embodiments of this specification is obtained and used based on user authorization.

[0079] The red envelope collection result page may also include a virtual image representing the red envelope, which may be a dynamic image or a static image, such as the relevant content introduced above, which will not be repeated here.

[0080] In actual applications, the red envelope collection result page can be a page generated after the server executes the steps 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 information to the user account of the first terminal, it can generate a red envelope collection result page and feedback to the first terminal; if some problems occur during the process of transferring resources and the red envelope resources cannot be successfully transferred to the user account of the first terminal, the server can also generate a red envelope collection result page and feedback to the first terminal.

[0081] The red envelope collection result page can also be generated and displayed by the local data of the first terminal. As an implementation method, the first terminal can store the page information of the red envelope collection result page locally. For example, when the first terminal installs a terminal application with the function of receiving red envelopes, the installation package of the terminal application can include the page information of the red envelope collection result page. After the first terminal obtains the tag information and sends a red envelope acquisition request to the server, the server sends information or instructions indicating the completion of the processing and whether the processing is successful to the first terminal after completing the relevant process of obtaining or receiving the red envelope. After the first terminal obtains the information or instruction, it can obtain the corresponding page information of the red envelope collection result page from the local data, and then the red envelope collection result page can be displayed in the first terminal.

[0082] Optionally, the red envelope receiving page in the embodiment of this specification may also include at least one of a first control for indicating opening a red envelope, a second control for indicating receiving a red envelope, and a third control for indicating refusing to receive a red envelope.

[0083] In actual applications, the red envelope receiving page may not include the above controls, such as only displaying a virtual image of the red envelope or some prompt information, and the first terminal may passively receive or accept the red envelope.

[0084] The red envelope receiving page may also include one of the above controls. For example, the red envelope receiving page may only include the first control. If the user performs an operation on the first control, it may also indicate that the user is determined to receive the red envelope. In actual applications, if the first control is not operated, one case may indicate that the user refuses to receive the red envelope, and another case may indicate that the user is determined to receive the red envelope, but has not checked the specific red envelope amount. The server may also transfer the red envelope resource to the user account of the first terminal. For another example, the red envelope receiving page may only include the second control. If the user performs an operation on the third control, it may indicate that the user is determined to receive the red envelope, or it may indicate that the user is determined to receive and open the red envelope. For another example, the red envelope receiving page may only include the third control. If the user performs an operation on the third control, the first terminal or the server may determine that the user refuses to receive the red envelope, or if the user does not perform an operation on the third control within a preset time period, it may indicate that the user is determined to receive the red envelope, or it may indicate that the user is determined to receive and open the red envelope.

[0085] The red envelope receiving page may include two of the above controls. For example, the red envelope receiving page may include the first control and the third control, or the red envelope receiving page may include the first control and the third control, or the red envelope receiving page may include the first control and the second control. The red envelope receiving page may also include three of the above controls.

[0086] It is understandable that these are just some examples provided here, and the specific content displayed in the red envelope collection page can be set according to actual needs.

[0087] As an implementation manner, the method in the embodiments of this specification may also include: If a first operation of opening a red envelope performed by the user based on the red envelope receiving page is obtained, an animation effect of opening the red envelope is displayed; Alternatively, if a second operation indicating confirmation of receiving the red envelope performed by the user based on the red envelope receiving page is obtained, an animation effect of placing the red envelope into the first terminal is displayed.

[0088] Alternatively, if a third operation indicating refusal to receive the red envelope performed by the user based on the red envelope receiving page is obtained, an animation effect of transferring the red envelope out of the first terminal is displayed.

[0089] The first operation may be an operation of the user on a first control included in the red envelope receiving page indicating opening the red envelope, such as clicking an "open" control, performing a swiping operation in a first direction on the page, tilting the first terminal in a first direction, etc. The first operation may also be an operation on the second control.

[0090] The animation effect of opening a red envelope is an animation effect that can indicate that a red envelope is opened. For example, an unopened red envelope is first displayed on the red envelope receiving page. After the first terminal obtains the user's first operation, the animation effect of the unopened red envelope being opened can be displayed on the red envelope receiving page.

[0091] The second operation may be an operation performed by the user on the second control for receiving the red envelope contained in the red envelope receiving page, such as clicking the "receive" control, performing a swiping operation in the second direction on the page, tilting the first terminal in the second direction, etc. The second operation may also be an operation on the first control, or may not be an operation on the third control.

[0092] The animation effect of placing the red envelope into the first terminal may be the effect of receiving the red envelope into a preset position, for example, showing the visual effect of the red envelope being sucked into the lower right corner, showing the visual effect of the red envelope jumping into the area marked with the red envelope clip displayed in the red envelope receiving page, and so on.

[0093] The virtual image of the red envelope displayed in the animation effect of placing the red envelope into the first terminal may be a virtual image representing an unopened red envelope, or may be a virtual image representing an opened red envelope, which may be set according to actual needs.

[0094] The third operation may be an operation by the user on a third control included in the red envelope receiving page that indicates refusal to receive the red envelope, such as clicking a "reject" control, swiping in a third direction on the page, tilting the first terminal in a third direction, etc.

[0095] The animation effect of transferring the red envelope out of the first terminal may be an animation effect of breaking the red envelope, moving the red envelope out of the first terminal, throwing the red envelope out of the first terminal, etc. The specific setting may be based on actual needs as long as it can indicate that the red envelope is transferred out of the first terminal.

[0096] In actual applications, if the red envelope receiving page displays an animation effect of the red envelope being swiped into the first terminal, the animation effect of the red envelope being transferred out of the first terminal may display an animation effect of swiping the red envelope back along the path the red envelope was swiped in. For example, the red envelope receiving page first displays an animation effect of the red envelope being swiped in from the left side of the first terminal, and after the user refuses to receive the red envelope, the first terminal may display an animation effect of swiping the red envelope out from the left side.

[0097] Based on the same idea, this specification also provides a method for red envelope interaction processing with the second terminal as the execution subject. Figure 3 A flowchart of a red envelope interaction processing method with a second terminal as the execution subject provided in an embodiment of this specification. From a program perspective, the execution subject of the process may include a program installed in the second terminal. Among them, the program may include a system program of the terminal system, and may also include a program of an application client installed in the terminal. From a hardware perspective, the execution subject of the process may include the second terminal.

[0098] like Figure 3 As shown, the process may include the following steps.

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

[0100] The red envelope information at least includes the red envelope amount information. The red envelope editing page may include an area for editing the red envelope information, and the user may edit the red envelope information by filling in, selecting, etc. The red envelope information is information related to the red envelope, and may specifically include the red envelope amount information. The specific amount amount included in the red envelope amount information may be editable by the user, or may be the default amount amount in the application.

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

[0102] In actual applications, users can send red envelopes through terminal applications or small programs installed in the second terminal. Sending red envelopes here can mean sending virtual red envelopes, sending red envelopes with the help of computer technology, and a way of resource interaction.

[0103] Step 304: Based on the red envelope information, a red envelope generation request for generating a short-distance communication mode red envelope is sent to the server.

[0104] The second terminal may send a red envelope generation request to the server based on the red envelope information, wherein the red envelope generation request may be a generation request requesting the server to generate a red envelope that can be sent via a short-distance communication mode.

[0105] In actual applications, the red envelope editing page may include identification information of short-distance communication, such as information of NFC, etc. Alternatively, the red envelope editing page may be a page displayed in the second terminal after the user selects the red envelope sending method of sending a red envelope via short-distance communication in the second terminal.

[0106] The red envelope generation request may include red envelope information, such as red envelope amount information, etc. The red envelope generation request may also include service identification information indicating that the red envelope is sent by short-distance communication, and may also include relevant information of the second terminal and / or the user logged in to the second terminal. After obtaining the red envelope generation request, the server may trigger the execution of the red envelope processing flow in the short-distance communication mode. For example, the server may generate information for triggering the collection of the red envelope and feed it back to the second terminal, so that the first terminal can trigger the collection of the red envelope by short-distance communication.

[0107] Step 306: Obtain tag information generated by the server based on the red envelope request feedback.

[0108] The tag information may be information for triggering the red envelope collection, and may specifically be a character string in a preset format, or information in the form of a link, etc. The tag information may include identification information indicating the red envelope resource corresponding to the red envelope generation request sent by the second terminal for collecting the red envelope. For example, after obtaining the red envelope generation request sent by the second terminal, the server may generate a token for the request, and the server may generate tag information based on the token so that the corresponding business processing flow can be executed based on the token later.

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

[0110] Among them, the first terminal is used to collect resources of the quantity indicated by the red envelope amount information based on the tag information.

[0111] After the second terminal obtains the tag information fed back by the server, the tag information can be stored locally in the terminal or in a secure and trusted environment to ensure the security of the information.

[0112] In actual applications, before executing the above step 308, the short-distance communication function of the second terminal is in the processing-on state, and specifically, before or during the execution of any of the above steps 302 to 306, the second terminal automatically turns on the short-distance communication function, or the user manually starts the short-distance communication function of the second terminal. For example, when the second terminal displays the red envelope editing page, or before displaying the red envelope editing page, such as after the second terminal starts the terminal application or applet where the red envelope editing page is located, or after the second terminal obtains the tag information fed back by the server, the short-distance communication function of the second terminal can be in the on state.

[0113] The specific process of the first terminal receiving the red envelope resource based on the tag information can be found in the relevant content of the aforementioned embodiment, which will not be repeated here.

[0114] It should be understood that the order of some steps in the method described in one or more embodiments of this specification can be interchanged according to actual needs, or some steps can be omitted or deleted. In addition, this embodiment and the above embodiment are embodiments based on the same technical concept, and the similar or identical contents contained in this embodiment and the above embodiment can be referenced to each other, and will not be repeated here.

[0115] Figure 3 In the method, the second terminal can send a red envelope generation request for generating a short-distance communication mode red envelope to the server based on the red envelope information edited by the user, and then can send the tag information fed back by the server to the first terminal through short-distance communication, so that the first terminal can obtain the red envelope resources sent by the second terminal through short-distance communication, which can simplify the user's operations during the red envelope interaction process.

[0116] On the other hand, the second terminal sends the red envelope to the first terminal via short-distance communication, so that the first terminal and the second terminal are relatively close to each other to receive the red envelope resources sent by the second terminal. In the process of red envelope interaction, it can also enhance the user's sense of participation and ritual, and improve the user experience.

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

[0118] As an implementation method, the red envelope information edited by the user of the second terminal does not need to include the recipient's information. The first terminal with short-range communication can obtain the red envelope resource by sticking or touching the second terminal, so that when the user of the second terminal does not know the recipient's information, such as account, mobile phone number and other information used to distinguish different users, the user of the second terminal can also send a red envelope to the first terminal, which can improve the convenience of red envelope interaction. On the other hand, the user of the second terminal does not need to fill in the recipient's information, and can also simplify the operation steps of the user of the second terminal.

[0119] As another implementation, the red envelope information edited by the user of the second terminal may include the recipient's information, so that only the recipient can obtain the red envelope provided by the second terminal, and can send a red envelope dedicated to the first terminal to the first terminal, so that even if there are multiple terminals near the second terminal, the red envelope can be sent to a specific terminal. In order to simplify the operation of the second terminal, the user information of the first terminal can also be obtained through short-distance communication, so that the user information of the first terminal can be automatically displayed in the red envelope editing page, without the need for the user of the second terminal to fill it out manually.

[0120] In actual applications, the red envelope editing page may further include a confirmation control. If the second terminal obtains the user's operation on the control, the second terminal may send a red envelope generation request to the server.

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

[0122] As an implementation manner, the short-distance communication in the embodiment of this specification is NFC near-field communication; the method in the embodiment of this specification may also include: The second terminal turns on the NFC card emulation mode; The tag information is saved in the NFC card emulation mode so that the first terminal in the NFC card reader mode reads the tag information.

[0123] After obtaining the tag information fed back by the server, the second terminal can turn on the NFC card simulation mode and save the obtained tag information to the second terminal, specifically, the tag information can be saved to the NFC card simulation module. The first terminal can be in NFC reader mode and read the tag information in the second terminal through NFC near field communication.

[0124] In actual applications, the second terminal may also be in NFC card simulation 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 simulation mode.

[0125] The second terminal can be in any mode of point-to-point mode, card emulation mode, and card reader mode according to actual needs. The working principle of the specific mode can be found in the relevant technical introduction, which will not be repeated here.

[0126] In the embodiment 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.

[0127] To improve user experience, the second terminal may also display information about the red envelope being sent, information about the result of the red envelope being sent, etc. Optionally, the method in the embodiment of this specification may further include: Displaying a red envelope sending page; the red envelope sending page includes prompt information indicating that the red envelope is being sent; And / or, display a red envelope sending result page; the red envelope sending result page contains result information indicating the red envelope sending result.

[0128] In actual application, the second terminal may display one of the red envelope sending page and the red envelope sending result page, or may display both pages.

[0129] For example, after the second terminal sends tag information to the first terminal via short-distance communication, the first terminal sends a red envelope acquisition request to the server based on the tag information. After the request is processed, the server sends the page information of the red envelope sending result to the second terminal, and the second terminal can display the red envelope sending result page.

[0130] For another 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 feedback the page information of the red envelope sending page to the second terminal, and the second terminal can display a red envelope sending page indicating that the red envelope is being sent. During the process of displaying the red envelope sending page on the second terminal, the server can execute relevant processes for processing the red envelope generation request sent by the second terminal, for example, the process of generating tag information, and / or, it can also be a process of determining relevant information of the user account of the second terminal based on the red envelope generation request, deducting corresponding red envelope resources from the user account of the second terminal, and so on.

[0131] For another example, after the second terminal sends a red envelope generation request to the server, the second terminal may first display the red envelope sending page, and then display the red envelope sending result page. For example, after the second terminal finishes sending the red envelope, or after the server deducts the corresponding red envelope resource from the user account of the second terminal, or after the first terminal obtains the tag information of the second terminal, or after the second terminal executes the red envelope receiving process through the tag information, the second terminal may display the red envelope sending result page.

[0132] 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 embodiment of this specification, the prompt information indicating that the 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.

[0133] The red envelope sending page may also include information representing a virtual image of the red envelope, such as text, characters, pictures, etc. For example, the red envelope sending page may display an image or animated image of a red envelope cover with a red background; the red envelope sending page may also display a static or dynamic virtual image in the form of a gold ingot, a virtual image representing a currency symbol, or some cartoon images containing red envelope features.

[0134] The red envelope sending page can display a static virtual image of the red envelope, or a dynamic virtual image of the red envelope, such as a static red envelope cover, cartoon image, etc.; or a dynamic animation effect, such as a virtual image of the red envelope that displays dynamic information in the form of rotation, flying, shaking, changing from large to small, etc.

[0135] The red envelope sending page can be a page generated by the second terminal based on local information, or it can be a page fed back by the server. As an implementation method, the server can generate the page information of 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, so that the second terminal can display the red envelope sending page. As another implementation method, the page information of the red envelope sending page can be stored locally in the second terminal. For example, when the second terminal installs a terminal application with a red envelope sending function, the installation package of the terminal application can include the page information of the red envelope sending page. After the first terminal obtains the red envelope information edited by the user, it can obtain the page information of the red envelope sending page from the local data through the terminal application, and then the red envelope sending page can be displayed in the second terminal.

[0136] Optionally, the prompt information indicating that the red envelope is being sent may include at least one of an animation effect of the transfer process of transferring the red envelope out of the second terminal, text information indicating that the red envelope is being sent, and voice information indicating that the red envelope is being sent.

[0137] Among them, the animation effect of the transfer process of the red envelope out of the second terminal can present to the user a visual effect of the red envelope being moved out to 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 exiting the first terminal from dark to light, from large to small, etc.

[0138] The text information indicating that a red envelope is being sent may be information in the form of text that prompts the user that a red envelope is being sent, such as information with the words "red envelope is being sent". The text information may be static or dynamic.

[0139] The voice message indicating that a red envelope is being sent may be a message in the form of voice prompting the user that a red envelope is being sent, such as a voice broadcast message of “You are sending a red envelope”, “Red envelope being sent”, etc.

[0140] In order to further improve the user experience and make the digital red envelope more ceremonial, as an implementation method, the animation effect of the above-mentioned transfer process of transferring the red envelope out of the second terminal can be specifically: the 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, the edge of the second terminal close to the first terminal, and any edge of the second terminal in the opposite direction of the edge of the first terminal that is drawn into the red envelope.

[0141] In actual applications, the animation effect displayed in the second terminal can be determined based on the relative position of the first terminal and the second terminal when the first terminal and the second terminal establish short-distance communication. For example, assuming that the placement directions of the first terminal and the second terminal are consistent, the first terminal approaches the second terminal from the right side of the second terminal to establish short-distance communication with the second terminal, and the visual effect of a red envelope being drawn out from the right side of the second terminal and / or moving to the right can be displayed in the second terminal. For another example, if the top of the first terminal is located at the bottom of the second terminal, the first terminal approaches the second terminal by bringing the top close to the bottom of the second terminal to establish short-distance communication with the second terminal, and the visual effect of a red envelope being drawn out from the bottom of the second terminal can be displayed in the second terminal.

[0142] If the placement directions of the first terminal and the second terminal are inconsistent, such as the top of the first terminal is close to the top of the second terminal, the second terminal may display a visual effect of a red envelope being drawn out from the top of the second terminal.

[0143] It can be understood that the above are only a few examples. In actual applications, the visual effect of display can be determined according to the relative positions of the first terminal and the second terminal. There is no specific limitation here, as long as the visual effect of displaying the red envelope is displayed as being transferred from the second terminal.

[0144] In actual application, the animation effect of the transfer process 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 the animation effects of linked transfer of the red envelope.

[0145] For example, the second terminal dynamically displays the visual effect of the red envelope being transferred out of the second terminal. At a certain moment, the second terminal displays a portion of the information contained therein, such as a portion of the red envelope card or a portion of the virtual image. The other portion of the information has been displayed in 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 portion of the information. In this way, the first terminal and the second terminal can display the visual effect of linked sending and receiving red envelopes, so that the user can feel that the red envelope in the second terminal is sent to the first terminal.

[0146] In actual applications, the animation effects displayed on the red envelope sending page in the second terminal and the animation effects displayed on the red envelope receiving page in the first terminal can be displayed synchronously or asynchronously, which can be set according to actual conditions.

[0147] In the embodiment of the present specification, the red envelope sending result page may represent the page displayed after the second terminal completes the red envelope sending, and the page may include 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 may display information indicating that the red envelope was not successfully sent.

[0148] Optionally, the result information indicating the red envelope sending result contained in the red envelope sending result page includes at least one of: an animation effect indicating the completion of the red envelope sending, text information indicating the completion of the red envelope sending, and voice information indicating the completion of the red envelope sending.

[0149] Among them, the animation effect indicating the completion of sending the red envelope can be a visual effect indicating that the red envelope has been sent in the form of animation. For example, the sending of the red envelope is indicated in the form of a cartoon image, a red envelope picture, or an artistic font. The text information indicating the completion of sending the red envelope is information indicating that the red envelope has been sent in the form of text. For example, text information such as "the red envelope has been sent". The voice information indicating the completion of sending the red envelope is information indicating that the red envelope has been sent in the form of voice. For example, information in the form of voice broadcasts such as "the red envelope has been sent". It can also be information prompt sounds such as "beep" and "ding".

[0150] In practical applications, the result information may be dynamic information or static information, for example, the result information may be displayed in the form of static text, or in the form of an animation including a virtual image of a red envelope, and so on.

[0151] As an implementation mode, at least one of the voice message indicating that the red envelope is being sent and the voice message indicating that the red envelope sending is finished may include the information of the red envelope recipient, so that the user of the second terminal can know who has received the red envelope.

[0152] In the implementation application, the information of the red envelope recipient 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 message of "send a red envelope to Zhang San".

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

[0154] If the second terminal does not record relevant information of the user of the first terminal, or the user of the second terminal and the user of the first terminal have not previously used the second terminal to contact the first terminal, or no contact has been sent between the user account of the second terminal and the user account of the first terminal, the voice information may also include the name information of the user of the first terminal, and the name information may be the name information set by the user of the first terminal himself.

[0155] In actual applications, the above-mentioned text information, animation effects, etc. displayed on the page may also include relevant information of the first terminal user. It should be noted that the user-related information used in the embodiments of this specification is obtained and used based on user authorization.

[0156] The red envelope sending result page may also include a virtual image representing the red envelope, which may be a dynamic image or a static image, such as the relevant content introduced above, which will not be repeated here.

[0157] In actual applications, the red envelope sending result page can be a page generated by the server after the server transfers the red envelope resources provided by the second terminal out of the user account of the second terminal, or it can be a page 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 information out of the user account of the second terminal or transfers the resources to the user account of the first terminal, it can generate a red envelope sending result page and feedback to the second terminal; if some problems occur during the process of transferring resources, and the red envelope resources cannot be successfully transferred out of the user account of the second terminal or cannot be successfully transferred into the user account of the first terminal, the server can also generate a red envelope sending result page and feedback to the second terminal.

[0158] The red envelope sending result page can also be generated and displayed by the local data of the second terminal. As an implementation method, the second terminal can store the page information of the red envelope sending result page locally. For example, when the second terminal installs a terminal application with the function of sending red envelopes, the installation package of the terminal application can include the page information of the red envelope sending result page. After the server completes the relevant process of processing the red envelope sending, it sends information or instructions indicating that the processing is completed and whether the processing is successfully completed to the second terminal. After the second terminal obtains the information or instructions, it can obtain the corresponding page information of the red envelope sending result page from the local data, and then the red envelope sending result page can be displayed in the second terminal.

[0159] To further improve the user experience, in the embodiments of this specification, an animation effect of sending a red envelope can also be displayed in the second terminal according to the user's operation on the page. Optionally, the page showing the sending of a red envelope may include one or more red envelopes to be sent; the method further includes: Obtaining the user's operation on the target red envelope on the red envelope sending page; Based on the operation direction represented by the operation, displaying an animation effect of sliding the target red envelope out of the second terminal along the operation direction in the red envelope sending page; Alternatively, based on the operation track represented by the operation, an animation effect of moving the target red envelope along the operation track out of the second terminal is displayed in the red envelope sending page.

[0160] Among them, the red envelope sending page can display one or more virtual images of the red envelopes to be sent, such as pictures, cartoon images, etc.

[0161] In actual applications, the red envelope editing page may also include information about the number of red envelopes. Users can fill in or select the number of red envelopes to be sent, and the red envelope information may include information indicating the number of red envelopes. The number of red envelopes displayed on the red envelope sending page may be consistent with the number of red envelopes contained in the red envelope information. If the number of red envelopes in the red envelope information is large, such as 10, 20, etc., the number of red envelopes displayed on the red envelope sending page may also be less than the number of red envelopes contained in the red envelope information, and the red envelope sending page may only display multiple red envelopes.

[0162] The target red envelope represents the red envelope that the user wants to send from one or more red envelopes to be sent. The user can perform an operation in the area displaying the target red envelope, such as swiping in a certain direction, and the second terminal can display an animation effect of the target red envelope moving out of the second terminal along the operation direction or trajectory based on the direction or trajectory of the user's operation.

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

[0164] In actual applications, the red envelope sending page may also include operation prompt information to prompt users to operate, such as text information such as swipe right to send red envelope, swipe left to send red envelope, swipe up to send red envelope, etc., or prompt information in the form of an indicating arrow, etc.

[0165] To improve the accuracy of information processing, if the second terminal sends multiple red envelopes, the server can generate label information for each red envelope so as to process each red envelope later. Optionally, the red envelope information described in the embodiment of this specification may also include red envelope quantity information; if the red envelope quantity information indicates a number of multiple red envelopes, the label information includes multiple sub-label information; one sub-label information corresponds to one red envelope; providing the label information to the first terminal by short-distance communication specifically includes: providing each sub-label information to at least one first terminal by short-distance communication.

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

[0167] In actual applications, the red envelope editing page may also include options for setting the red envelope amount. For example, the user can fill in the corresponding red envelope amount for each red envelope, or the user can fill in the total amount of the red envelope and then select a random amount or an average amount, so that the user does not need to set the amount for each red envelope. The red envelope editing page may also include information on the red envelope mode, such as ordinary red envelopes, exclusive red envelopes, single red envelopes, multiple red envelopes, and other modes. For different modes, different editable information editing areas may be displayed in the red envelope editing page.

[0168] For the scenario where the second terminal sends multiple red envelopes, the red envelope sending page displayed by the second terminal can also display an animation effect of sending multiple red envelopes. The animation effect of sending multiple red envelopes can include an animation effect of jet-like red envelopes, red envelope rain, a money tree animation effect, and the like.

[0169] In actual applications, the second terminal can also display corresponding animation effects according to the receipt of each red envelope. For example, after the second terminal provides the first sub-tag information to a first terminal through short-distance communication, the animation effect of sending the first red envelope is displayed in 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 the second sub-tag information is provided to another first terminal through short-distance communication, the animation effect of sending the second red envelope is displayed in the red envelope sending page; the second red envelope is the red envelope corresponding to the second sub-tag information.

[0170] For example, the user of the second terminal sends three red envelopes, and multiple first terminals are close to the second terminal at the same time or at different times. Each first terminal can establish a short-distance communication connection with the second terminal at the same time or one by one. If the first terminal A receives a red envelope, the second terminal can display an animation effect of a red envelope being transferred out, and then another first terminal B receives another red envelope, and the second terminal can display another animation effect of a red envelope being transferred out. Of course, the second terminal can also display an animation effect of continuously sending red envelopes.

[0171] It is understandable that the above are only examples of some animation effects, and there may be other forms of animation effects, which are not listed here one by one.

[0172] It should be noted that the various pages or animation effects displayed in the first terminal described above and the various pages or animation effects displayed in the second terminal can be implemented independently of each other. For example, the animation effect of receiving a red envelope can be displayed in the first terminal, but the animation effect of sending a red envelope may not be displayed in the second terminal.

[0173] Based on the same idea, this specification also provides a method using a server as the execution subject. Figure 4 The present invention provides a flowchart of a method for interactive processing of red envelopes with a server as the execution subject. From the perspective of the program, the execution subject of the process may include a program installed on the server. From the perspective of hardware, the execution subject of the process may include a server.

[0174] like Figure 4 As shown, the process may include the following steps.

[0175] Step 402: Obtain a red envelope generation request sent by the second terminal for generating a short-distance communication mode red envelope.

[0176] 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 at least includes red envelope amount information; Step 404: Generate tag information based on the red envelope generation request.

[0177] Among them, the tag information may include identification information related to the red envelope business.

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

[0179] The first terminal that establishes a short-distance communication connection with the second terminal can send a red envelope acquisition request based on the tag information.

[0180] Step 408: obtaining a red envelope obtaining request sent by the first terminal that establishes a short-distance communication connection with the second terminal based on the tag information; 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.

[0181] In actual applications, if the first terminal does not establish short-range communication with the second terminal, or the first terminal does not obtain the tag information in the second terminal, or the first terminal does not send a red envelope acquisition request to the server after obtaining the tag information, or 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.

[0182] In the embodiments of 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, the red envelope sending result page, the red envelope receiving page, the red envelope receiving result page, etc. introduced above. And the relevant concepts involved in this embodiment and the specific red envelope interaction processing flow can also be referred to the contents of the aforementioned embodiments, which will not be repeated here.

[0183] For a clearer description, a red envelope interaction processing method is provided in the embodiments of this specification. Figure 5 This is a swimlane diagram of a red envelope interactive process provided in the embodiments of this specification. Figure 5 As shown, the process may include a red envelope sending stage and a red envelope receiving stage, and may specifically include the following steps.

[0184] Step 502: The second terminal displays a red envelope editing page.

[0185] 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. The user edits the red envelope information such as the amount in the red envelope editing page.

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

[0187] The second terminal may also collect the user's biometric information and send it to the server, so that after the server verifies the user's identity based on the biometric information, it deducts the amount of resources represented by the red envelope amount from the user account of the second terminal. The biometric information may include at least one of face, fingerprint, iris, palm print, voice and other biometric information.

[0188] In actual applications, if the user of the second terminal has enabled the password-free payment function, the second terminal may not collect the user's biometric information.

[0189] Step 506: The server generates label information based on the red envelope generation request and feeds it back to the second terminal.

[0190] Among them, the tag information may include information used to trigger the red envelope collection process.

[0191] To improve the user experience, during the process of the server processing the request, the second terminal may also display a red envelope sending page, which may display information indicating that the red envelope is being sent. Alternatively, the second terminal may also display a red envelope generation page, which may display an animation and / or text information of stuffing the red envelope resource into the red envelope.

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

[0193] After the second terminal obtains the tag information sent by the server, it can start the card simulation mode to save the tag information. Alternatively, the second terminal can also start the card simulation mode after or before displaying the red envelope editing page, or after or before the second terminal generates or sends a red envelope generation request to the server. The timing of starting the card simulation mode is not specifically limited here, as long as the first terminal can obtain the tag information through short-distance communication.

[0194] Step 510: The first terminal approaches the second terminal and obtains tag information.

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

[0196] During the process in which the first terminal obtains the tag information of the second terminal, the second terminal may also display a red envelope sending page.

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

[0198] Among them, the tag information can be information in the form of a link. The first terminal can start a terminal application that can obtain red envelopes based on the tag information. Accessing the link address contained in the tag information through the terminal application can represent sending a red envelope acquisition request to the server. The red envelope acquisition request can also include identification information of the first terminal and / or the user of the first terminal, and the server can determine the user who receives the red envelope based on the identification information. The red envelope acquisition request can also include business identification information so that the server can determine information such as the red envelope sending user and / or the number of red envelope resources corresponding to the request.

[0199] The first terminal may further execute step 514: displaying a red envelope receiving page.

[0200] After acquiring the tag information, the first terminal may display a red envelope receiving page, and the page may include an animation indicating receiving the red envelope.

[0201] After obtaining the red envelope obtaining request sent by the first terminal, the server may execute step 516: transferring the red envelope resource to the user account of the first terminal.

[0202] Among them, the above-mentioned red envelope receiving page can also be fed back to the first terminal after the server obtains the red envelope obtaining request. During the process of resource transfer by the server, the first terminal can display the red envelope receiving page.

[0203] The server may also execute step 518: feedback red envelope processing result information to the first terminal and / or the second terminal.

[0204] In this way, the first terminal and / or the second terminal can display the result information, and the first terminal can specifically perform step 520: display the red envelope receiving result page. The red envelope receiving result page can include the result information, and on this basis, can also include at least one of the following information: the red envelope amount information, the second terminal user information, and the blessing message.

[0205] The second terminal may execute step 522: displaying a red envelope sending result page.

[0206] In actual applications, the red envelope sending result page can also be a page displayed after the second terminal completes the red envelope sending process. 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 in the second terminal before the first terminal obtains the tag information, or it can be the first terminal after the red envelope receiving process is completed, such as after the first terminal successfully receives the red envelope resources, the red envelope sending result page is displayed in the second terminal. Among them, the red envelope sending result page can include result information, and on this basis, it can also include at least one of the red envelope amount information and the information of the first terminal user.

[0207] The above embodiment is described by taking the second terminal for sending red envelopes as a card simulation terminal and the first terminal for receiving red envelopes as a card reader terminal as an example. In actual applications, the second terminal for sending red envelopes may also be a card reader terminal, and the first terminal for receiving red envelopes may be a card simulation terminal. As an implementation method, the first terminal may have page tag information for triggering the display of a red envelope editing page. After the second terminal reads the page tag information as a card reader, the red envelope editing page may be displayed, which can simplify the operation of the second terminal user entering the red envelope compilation page. Among them, the page tag information can be generated and fed back by the server based on the request sent by the first terminal. For example, the user of the first terminal can perform an operation to trigger the collection of red envelopes in the first terminal. For example, the page of the terminal application of the first terminal has a control for triggering the process of receiving red envelopes, such as a control that displays the words "receive red envelopes". After the user performs an operation on the control, the first terminal can send a tag generation request to the server, and 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. In this way, the second terminal and the first terminal are close to each other and can obtain the page tag information through short-distance communication, and then the red envelope editing page can be displayed in the second terminal. Then, the second terminal may send a red envelope based on the red envelope information edited by the user in the red envelope editing page, wherein the red envelope interaction process may be the red envelope interaction process described in the above embodiments.

[0208] As another implementation, the second terminal displays a red envelope editing page based on the page tag information provided by the first terminal, and the second terminal sends a red envelope sending request to the server. The server performs red envelope business processing according to the red envelope sending request, and can deduct red envelope resources from the user account of the second terminal, and can also add red envelope resources to the user account of the first terminal. Among them, the first terminal and / or the second terminal can also display the relevant pages for collecting or sending each red envelope introduced in the above embodiments. The differences from the above embodiments may include: In this embodiment, the server does not need to send tag information for triggering the red envelope collection process to the second terminal, and the first terminal does not need to trigger the execution of the red envelope collection process through tag information, and the server can automatically execute the relevant process. The page tag information in this implementation may have a corresponding relationship with the first terminal, such as the page tag information may include the identification information of the first terminal, or the server may store the corresponding relationship 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 may include the identification information of the second terminal and / or part of the information in the page tag information, such as token information, etc. The red envelope sending request may also include information such as the red envelope amount. In this way, the server can determine the red envelope sender, the red envelope recipient, the red envelope amount and other information based on the red envelope sending request sent by the second terminal. Based on this information, the server can execute relevant processes for red envelope interaction and complete the transfer of red envelope resources.

[0209] In the above embodiment, even if the user of the second terminal does not know how to send a red envelope or how to send a red envelope through short-distance communication, it can be triggered by the first terminal, and the red envelope editing page can be directly displayed in the second terminal, thereby simplifying the operation of the second terminal user.

[0210] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method. Figure 6 The embodiments of this specification provide corresponding to Figure 2 A schematic diagram of the structure of a red envelope interactive processing device. Figure 6 As shown, the device may include: The communication establishing module 602 is used to establish a short-distance communication connection with the second terminal; The information acquisition module 604 is used to acquire the tag information provided by the second terminal by means of short-distance communication; the tag information is generated based on the red envelope information edited by the user in the red envelope editing page displayed by the second terminal; the red envelope information at least includes the red envelope amount information; 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.

[0211] based on Figure 6 The present specification also provides some specific implementation plans, which are described below.

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

[0213] Optionally, the tag information includes identification information of a target application for receiving a red envelope; the device further includes an application startup module, specifically configured to: start the target application based on the identification information. The request sending module 606 can be specifically configured to: send a red envelope acquisition request to a server based on the started target application.

[0214] Optionally, the above-mentioned device may also include a page display module, which can be used to: display a red envelope collection page; the red envelope collection page includes prompt information indicating that the red envelope is being collected; and / or, display a red envelope collection result page; the red envelope collection result page includes result information indicating the red envelope collection result.

[0215] Optionally, the prompt information includes: at least one of an animation effect of the transfer process of transferring the red envelope to the first terminal, 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 an animation effect indicating that the red envelope is received, text information indicating that the red envelope is received, and voice information indicating that the red envelope is received.

[0216] Optionally, the above-mentioned device is also used for: if a first operation indicating opening of a red envelope performed by a user based on the red envelope receiving page is obtained, then an animation effect of opening the red envelope is displayed; or, if a second operation indicating confirmation of receiving the red envelope performed by a user based on the red envelope receiving page is obtained, then an animation effect of placing the red envelope into the first terminal is displayed; or, if a third operation indicating refusal to receive the red envelope is obtained, then an animation effect of transferring the red envelope out of the first terminal is displayed.

[0217] Optionally, the animation effect of the transfer process of transferring the red envelope to the first terminal can specifically be: the animation effect of transferring the red envelope from a preset edge of the first terminal to 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 of the edge of the second terminal from which the red envelope is transferred.

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

[0219] Figure 7 The embodiments of this specification provide corresponding to Figure 3 A schematic diagram of the structure of a red envelope interactive processing device. Figure 7 As shown, the device may include: The information acquisition module 702 is used to acquire the red envelope information edited by the user in the red envelope editing page; the red envelope information at least includes the red envelope amount information; A request sending module 704 is used to send a red envelope generation request for generating a short-distance communication mode red envelope to a server based on the red envelope information; 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; The tag information sending module 708 is used to provide the tag information to the first terminal through short-distance communication; the first terminal is used to collect the resources of the quantity indicated by the red envelope amount information based on the tag information.

[0220] based on Figure 7 The present specification also provides some specific implementation plans, which are described below.

[0221] Optionally, the short-distance communication is NFC near-field communication; the device is further used for: the second terminal turning on an NFC card emulation mode; and saving the tag information in the NFC card emulation mode so that the first terminal in an NFC card reader mode can read the tag information.

[0222] Optionally, the device may further include a page display module, which may be specifically used to: display 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 a red envelope sending result page; the red envelope sending result page includes result information indicating the red envelope sending result.

[0223] Optionally, the prompt information includes at least one of an animation effect of the transfer process of transferring the red envelope out of the second terminal, text information indicating that the red envelope is being sent, and voice information indicating that the red envelope is being sent; the result information includes: at least one of an animation effect indicating the completion of the red envelope sending, text information indicating the completion of the red envelope sending, and voice information indicating the completion of the red envelope sending.

[0224] Optionally, the animation effect of the process 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 animation effects of linked transfer of the red envelope.

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

[0226] Optionally, the red envelope information also includes red envelope quantity information; if the red envelope quantity information indicates a multiple quantity, the label information includes multiple sub-label information; one sub-label information corresponds to one red envelope; providing the label information to the first terminal via short-distance communication specifically includes: providing each sub-label information to at least one first terminal via short-distance communication.

[0227] Figure 8 The embodiments of this specification provide corresponding to Figure 4 A schematic diagram of the structure of a red envelope interactive processing device. Figure 8 As shown, the device may include: A first request acquisition module 802 is used to acquire a red envelope generation request for generating a short-distance communication mode red envelope sent by a second terminal; 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 at least includes red envelope amount information; A label information generating module 804, configured to generate label information based on the red envelope generating request; The tag information sending module 806 is used to send the tag information to the second terminal; A second request acquisition module 808, configured to acquire a red envelope acquisition request sent by the first terminal that establishes a short-distance communication connection with the second terminal based on the tag information; 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.

[0228] Based on the same idea, the embodiments of this specification also provide a device corresponding to the above method.

[0229] Fig. 9 This is a schematic diagram of the structure of a red envelope interactive processing device provided in an embodiment of this specification. Fig. 9 As shown, the device 900 may include: at least one processor 910; and, A memory 930 in communication with the at least one processor; wherein, The memory 930 stores instructions 920 that can be executed by the at least one processor 910, and the instructions are executed by the at least one processor 910 so that the at least one processor 910 can execute the above-mentioned at least one red envelope interaction processing method.

[0230] Based on the same idea, the embodiment of this specification also provides a computer-readable medium corresponding to the above method. The computer-readable medium stores computer-readable instructions, which can be executed by a processor to implement at least one red envelope interaction processing method.

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

[0232] 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, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards in the relevant regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0233] In the 1990s, it was very clear whether the improvement of a technology was hardware improvement (for example, improvement of the circuit structure of diodes, transistors, switches, etc.) or software improvement (improvement of the method flow). However, with the development of technology, many improvements of the method flow today can be regarded as direct improvements of the hardware circuit structure. Designers almost always obtain the corresponding hardware circuit structure by programming the improved method flow into the hardware circuit. Therefore, it cannot be said that the improvement of a method flow cannot be implemented with hardware entity modules. For example, a programmable logic device (PLD) (such as a field programmable gate array (FPGA)) is such an integrated circuit whose logical function is determined by the user's programming of the device. Designers can "integrate" a digital system on a PLD by programming it themselves, without having to ask chip manufacturers to design and make dedicated integrated circuit chips. Moreover, nowadays, instead of manually making integrated circuit chips, this kind of programming is mostly implemented by "logic compiler" software, which is similar to the software compiler used when developing and writing programs, and the original code before compilation must also be written in a specific programming language, which is called hardware description language (HDL). There is not only one kind of HDL, but many kinds, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, RHDL (Ruby Hardware Description Language), etc. The most commonly used ones are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also know that it is only necessary to program the method flow slightly in the above-mentioned hardware description languages ​​and program it into the integrated circuit, and then it is easy to obtain the hardware circuit that implements the logic method flow.

[0234] The controller may be implemented in any suitable manner, for example, the controller may take the form of a microprocessor or processor and a computer-readable medium storing a computer-readable program code (e.g., software or firmware) executable by the (micro)processor, a logic gate, a switch, an application-specific integrated circuit (ASIC), a programmable logic controller, and an embedded microcontroller, examples of which include but are not limited to the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicone Labs C8051F320, and the memory controller may also be implemented as part of the control logic of the memory. It is also known to those skilled in the art that, in addition to implementing the controller in a purely computer-readable program code manner, the controller may be implemented in the form of a logic gate, a switch, an application-specific integrated circuit, a programmable logic controller, and an embedded microcontroller by logically programming the method steps. Therefore, such a controller may be considered as a hardware component, and the devices for implementing various functions included therein may also be considered as structures within the hardware component. Or even, the devices for implementing various functions may be considered as both software modules for implementing the method and structures within the hardware component.

[0235] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, the computer may be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0236] For the convenience of description, the above device is described in various units according to their functions. Of course, when implementing the present application, the functions of each unit can be implemented in the same or multiple software and / or hardware.

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

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

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

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

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

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

[0243] Computer readable media include permanent and non-permanent, removable and non-removable media that can be implemented by any method or technology to store information. Information can be computer readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic disk storage or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined in this article, computer readable media does not include temporary computer readable media (transitory media), such as modulated data signals and carrier waves.

[0244] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

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

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

[0247] The above is only an embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various changes and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application should be included in the scope of the claims of the present application.

Claims

1. A red envelope interaction processing method, applied to a first terminal, comprising: establishing a short-range communication connection with a second terminal; Acquire tag information provided by the second terminal by means of short-range communication; The tag information is generated based on the red envelope information edited by the user in the red envelope editing page displayed on the second terminal; the red envelope information at least includes red envelope amount information; Based on the tag information, a red envelope acquisition request 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. According to the method of claim 1, the tag information includes link information for triggering the red envelope acquisition process; the sending of the 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 red envelope acquisition request is sent to the server.

3. The method according to claim 1, wherein the tag information includes identification information of a target application for receiving a red envelope; The method further comprises: Based on the identification information, starting the target application; The sending of the red envelope acquisition request to the server specifically includes: Based on the started target application, a red envelope acquisition request is sent to the server.

4. The method according to claim 1, after sending the red envelope acquisition request to the server, further comprising: Displaying a red envelope receiving page; the red envelope receiving page includes prompt information indicating that the red envelope is being received; And / or, displaying the red envelope receiving result page; The red envelope receiving result page contains result information indicating the red envelope receiving result.

5. The method according to claim 4, wherein the prompt information comprises: The result information includes: at least one of an animation effect indicating that the red envelope is received, a text message indicating that the red envelope is received, and a voice message indicating that the red envelope is received.

6. The method according to claim 5, further comprising: If a first operation of opening a red envelope performed by the user based on the red envelope receiving page is obtained, an animation effect of opening the red envelope is displayed; Alternatively, if a second operation indicating confirmation of receiving the red envelope performed by the user based on the red envelope receiving page is obtained, an animation effect of placing the red envelope into the first terminal is displayed; Alternatively, if a third operation indicating refusal to receive the red envelope performed by the user based on the red envelope receiving page is obtained, an animation effect of transferring the red envelope out of the first terminal is displayed.

7. According to the method of claim 5, the animation effect of the process of transferring the red envelope to the first terminal specifically includes: The animation effect of transferring the red envelope from the preset edge of the first terminal to the first terminal; the preset edge is any edge of the first terminal, an edge of the first terminal close to the second terminal, and any edge of the first terminal in the opposite direction to the edge of the second terminal from which the red envelope is transferred.

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

9. A red envelope interaction processing method, applied to a second terminal, comprising: Get the red envelope information edited by the user on the red envelope editing page; The red envelope information at least includes red envelope amount information; Based on the red envelope information, sending a red envelope generation request for generating a short-distance communication mode red envelope to a server; Obtaining label information of the server based on the red envelope generation request feedback; Providing the tag information to the first terminal by means of short-distance communication; The first terminal is used to collect resources of a quantity indicated by the red envelope amount information based on the tag information.

10. The method according to claim 9, wherein the short-distance communication is NFC near field communication; the method further comprises: The second terminal turns on the NFC card emulation mode; The tag information is saved in the NFC card emulation mode so that the first terminal in the NFC card reader mode reads the tag information.

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

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

13. According to the method of claim 12, the animation effect of the transfer process 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 the animation effects of linked transfer of 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 comprises: Obtaining the user's operation on the target red envelope on the red envelope sending page; Based on the operation direction represented by the operation, displaying an animation effect of sliding the target red envelope out of the second terminal along the operation direction in the red envelope sending page; Alternatively, based on the operation track represented by the operation, an animation effect of moving the target red envelope along the operation track out of the second terminal is displayed in the red envelope sending page.

15. The method according to claim 9, wherein the red envelope information further includes red envelope quantity information; if the red envelope quantity information indicates a plurality of quantities, the tag information includes a plurality of sub-tag information; one sub-tag information corresponds to one red envelope; and providing the tag information to the first terminal by means of short-distance communication specifically comprises: The information of each sub-tag is provided to at least one first terminal by means of short-distance communication.

16. A red envelope interactive processing method, applied to a server, comprising: Obtaining a red envelope generation request for generating a short-distance communication mode red envelope sent by the second terminal; 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 at least includes red envelope amount information; Generate label information based on the red envelope generation request; Sending the tag information to the second terminal; Obtaining a red envelope obtaining request sent by the first terminal that establishes a short-distance communication connection with the second terminal based on the tag information; Based on the red envelope acquisition request, resources of a quantity indicated by the red envelope amount information are transferred to a user account of the first terminal.

17. A red envelope interaction processing device, applied to a first terminal, comprising: A communication establishing module, used to establish a short-distance communication connection with a second terminal; an information acquisition module, configured to acquire tag information provided by the second terminal by means of short-distance communication; the tag information is generated based on the red envelope information edited by the user in the red envelope editing page displayed by the second terminal; the red envelope information at least includes red envelope amount information; A request sending module, used for sending a red envelope acquisition request to a 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 obtain the red envelope information edited by the user in the red envelope editing page; The red envelope information at least includes red envelope amount information; A request sending module, used for sending a red envelope generation request for generating a short-distance communication mode red envelope to a server based on the red envelope information; A tag information acquisition module, used to acquire tag information fed back by the server based on the red envelope generation request; A tag information sending module, used for providing the tag information to the first terminal by means of short-distance communication; The first terminal is used to collect resources of a quantity indicated by the red envelope amount information based on the tag information.

19. A red envelope interactive processing device, applied to a server, comprising: A first request acquisition module, used to acquire a red envelope generation request for generating a short-distance communication mode red envelope sent by the second terminal; 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 at least includes red envelope amount information; A label information generating module, used for generating label information based on the red envelope generating request; A label information sending module, used for sending the label information to the second terminal; A second request acquisition module, used to acquire a red envelope acquisition request sent by the first terminal that establishes a short-distance communication connection with the second terminal based on the tag information; A 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 interactive 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, and the instructions are executed by the at least one processor so that the at least one processor can execute the red envelope interaction processing method described in any one of claims 1 to 16.

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

Images