A method for sending and receiving red envelopes and electronic devices

Abstract

This application provides a method for sending and receiving red envelopes and an electronic device, offering a new way to send and receive red envelopes and improving the convenience of sending and receiving electronic red envelopes between users. In this method, when the first electronic device displays a red envelope sending interface, it can guide the user to send a red envelope to a second electronic device via short-range wireless communication. Furthermore, when the first and second electronic devices detect that they meet preset trigger conditions, a red envelope is sent to the second electronic device. Correspondingly, when the second electronic device detects that it meets the preset trigger conditions with the first electronic device, it directly displays a red envelope receiving interface. In this way, the first and second electronic devices can conveniently send and receive red envelopes through preset operation methods, reducing the operational complexity of sending and receiving red envelopes.

Description

Technical Field

[0001] This application relates to the field of electronic equipment technology, and in particular to a method for sending and receiving red envelopes and an electronic device. Background Technology

[0002] With the continuous development and innovation of electronic devices, they can provide increasingly rich functions in users' daily lives and work, bringing them a better user experience. The red envelope function is one such important function offered by electronic devices, facilitating communication and interaction between users and is widely used in various social media platforms.

[0003] How to innovate the red envelope function is of great research significance. Summary of the Invention

[0004] This application provides a method for sending and receiving red envelopes and an electronic device, which can provide a new way of sending and receiving red envelopes and enhance the fun and playability of sending and receiving electronic red envelopes between users.

[0005] Firstly, this application provides a method for sending and receiving red envelopes, which can be executed by a first electronic device. In this method, the first electronic device displays a first interface, which includes first guidance information and a red envelope illustration card. The first guidance information instructs a second electronic device to send a first red envelope corresponding to the red envelope illustration card using a first method, wherein the first method is implemented based on short-range wireless communication technology. In the first interface, in response to a first event that satisfies the triggering condition of the first method, the first red envelope is sent to the second electronic device.

[0006] In this method, the first electronic device sends a red envelope to the second electronic device via short-range wireless communication technology, based on the displayed red envelope sending interface, triggering the second electronic device to display a red envelope receiving interface. This method improves the convenience of sending and receiving red envelopes between electronic devices, enabling instant one-touch sending and reducing user operations. Furthermore, this method does not require the electronic devices to be connected through the user's address book, reducing the operational complexity of red envelope sending and receiving scenarios and making it easier for two users to send and receive red envelopes. Additionally, this method enhances the application scenarios and fun of using the red envelope function.

[0007] In one possible implementation, sending the first red envelope to the second electronic device includes: sending first data to the second electronic device, the first data including: a red envelope identifier and first information, the first information being used by the second electronic device to redirect to an interface for receiving the first red envelope. For example, the first information is a deep link, the deep link being used by the second electronic device to display the interface for receiving the first red envelope according to the link path, the link path being used to activate the red envelope function of the payment service. Optionally, the first data may also include: red envelope cover data, a greeting, etc. Alternatively, the red envelope cover data, greeting, etc., may also be carried in a deep link.

[0008] In this implementation, sending the first message from the first electronic device to the second electronic device allows the second electronic device to quickly activate the red envelope function of its payment service and directly display the red envelope receiving interface. This improves the convenience of sending and receiving red envelopes and reduces user operations.

[0009] In one possible implementation, before displaying the first interface, the method further includes: sending second data to a server, the second data including: a user identification (UID) of the first electronic device and second information, the second information being used to indicate the configuration of the red envelope; and receiving third data sent by the server, the third data including: a red envelope identifier. The UID of the first electronic device is used to verify the real-name information of the user sending the red envelope, thereby ensuring the security of the red envelope sending and receiving scenario.

[0010] In this implementation, by sending the configuration data of the red envelope to the server, the server can easily store the configuration information. This allows the server to respond to the red envelope receiving data from the second electronic device and allocate the red envelope to the second electronic device according to the configuration data. Furthermore, by generating a red envelope identifier, the server can easily associate and retrieve various red envelope-related data, such as red envelope configuration data, data used for sending red envelopes, and red envelope receiving data.

[0011] In one possible implementation, the UID of the first electronic device is determined based on the user account logged in on the first electronic device.

[0012] In this implementation, the first electronic device is typically logged into a user account. By reusing the user account logged into the first electronic device, the UID of the first electronic device can be easily obtained without additional account activation processing, simplifying the sending and receiving of red envelopes. For example, the user account logged into the first electronic device can be a Huawei account.

[0013] In one possible implementation, the red envelope icon corresponds to multiple sub-red envelopes; the number of red envelope icon cards included in the first interface corresponds one-to-one with the number of remaining sub-red envelopes; or, when the number of remaining sub-red envelopes is greater than a quantity threshold, the number of red envelope icon cards is the quantity threshold, and when the number of remaining sub-red envelopes is less than or equal to the quantity threshold, the number of red envelope icon cards corresponds one-to-one with the number of remaining sub-red envelopes.

[0014] In this implementation, by associating the red envelope icon displayed on the red envelope sending interface with the remaining number of red envelopes, the number of remaining red envelopes can be more realistically reflected, enhancing the experience and fun of sending and receiving red envelopes.

[0015] In one possible implementation, sending the first red envelope to the second electronic device in response to a first event that satisfies the triggering condition of the first method includes: displaying a second interface in response to the first event, the second interface including a first red envelope indicator card, the first red envelope indicator card being used to indicate the first red envelope; and sending the first red envelope to the second electronic device in response to a swipe operation on the first red envelope indicator card in the second interface.

[0016] In this implementation, the experience of sending red envelopes in real life can be simulated by sliding the swipe on the first electronic device, which can enhance the fun and experience of sending and receiving red envelopes.

[0017] In one possible implementation, the first method involves the first electronic device and the second electronic device touching each other. The first event is the touching of the first electronic device and the second electronic device, for example, the top of the first electronic device touching the top of the second electronic device, or the back of the first electronic device touching the back of the second electronic device. Alternatively, the first method is a preset air gesture method, where the first event is the first electronic device detecting a first air gesture, the first electronic device detecting a second air gesture, the first air gesture indicating sending the first red envelope, and the second air gesture indicating receiving the first red envelope.

[0018] In this implementation method, the sending and receiving of red envelopes between the first and second electronic devices can be conveniently achieved through a tap-to-tap or air gesture method, which can reduce user operations and improve the efficiency and user experience of sending and receiving red envelopes.

[0019] In one possible implementation, the first interface further includes second guidance information, which instructs the second method to send the first red envelope corresponding to the red envelope symbol card to the second electronic device; wherein the second method includes: a QR code method or a password red envelope method. For example, the method further includes: in response to a first operation, displaying a third interface, which displays a QR code or password red envelope corresponding to the first red envelope; wherein the first operation is a click operation on a first control, the first control being a control for flipping the red envelope symbol card, or a control for generating a QR code or password red envelope corresponding to the first red envelope.

[0020] This implementation method, by providing multiple methods for sending and receiving red envelopes, can meet the needs of various red envelope sending and receiving scenarios. For example, if the second electronic device supports short-range wireless communication methods such as tap-to-receive or air gestures to receive red envelopes, it can conveniently receive red envelopes through these methods. If the second electronic device does not support short-range wireless communication, it can still successfully receive red envelopes via QR code or password red envelopes. Furthermore, when the red envelope sent by the first electronic device includes multiple sub-red envelopes, providing multiple red envelope sending and receiving methods does not restrict whether the second electronic device supports short-range wireless communication, allowing users to easily choose a method to send and receive red envelopes, thereby improving the user experience of the red envelope function.

[0021] In one possible implementation, the method further includes: when it is detected that there are still remaining sub-red envelopes, displaying a fourth interface, the fourth interface including third guidance information and a red envelope illustration card; wherein, the third guidance information is used to instruct the sending of a second red envelope corresponding to the red envelope illustration card to a third electronic device using the first method, the second red envelope being one of the remaining sub-red envelopes. The third electronic device refers to an electronic device different from the second electronic device mentioned above, and can also be understood as another electronic device; the processing procedure between the first electronic device and the third electronic device can be referred to the processing procedure between the first electronic device and the second electronic device.

[0022] In this implementation, when the first electronic device detects that the red envelope includes multiple sub-red envelopes, it can improve the efficiency of sending red envelopes by continuing to display the red envelope sending interface, thus facilitating the sending of red envelopes from the first electronic device to multiple electronic devices.

[0023] In one possible implementation, before displaying the first interface, the method further includes: displaying a fifth interface in response to a second event; wherein the second event includes: triggering an operation on a second control in the negative one screen interface, or detecting a preset voice command, or triggering an operation on a third control in the first application, the second control, the preset voice command, and the third control being used to indicate sending a red envelope; the fifth interface being used for red envelope configuration; and a configuration operation on the fifth interface being detected.

[0024] This implementation method can provide multiple trigger entry points to access the red envelope sending and receiving interface, thereby making it easier for users to use the red envelope function.

[0025] In one possible implementation, before displaying the fifth interface, the method further includes: in response to a second event, when it is detected that a user account has not been activated, displaying a sixth interface, the sixth interface being used to guide the user to activate a user account.

[0026] In this implementation method, guiding users to open user accounts can improve the efficiency of users using the red envelope function.

[0027] In one possible implementation, the fifth interface includes a fourth control for opening a payment account.

[0028] In this implementation method, guiding users to open a payment account can improve the efficiency of users using the red envelope function.

[0029] In one possible implementation, the fifth interface includes a fifth control for launching the cashier. The method further includes: when an abnormal payment account status is detected, displaying a seventh interface, which guides the user to unfreeze the payment account using a preset verification method obtained by the first electronic device from the server.

[0030] In this implementation method, guiding users to unfreeze their payment accounts can improve the efficiency of users using the red envelope function.

[0031] In one possible implementation, the method further includes sending fourth data to the server, the fourth data including a red envelope identifier, the fourth data being used to query red envelope receipt details.

[0032] In this implementation, the server can maintain the record data of red envelopes. Through the red envelope identifier, the relevant details of the red envelope can be easily retrieved from the server, which makes it easier to display the red envelope management interface in a more real-time manner.

[0033] In one possible implementation, the method further includes: displaying an eighth interface in response to a second operation; wherein the second operation is used to view red envelope records, and the eighth interface includes at least one of the following: records of expired red envelopes, records of red envelopes to be received, records of red envelopes to be sent, records of red envelopes received, and records of red envelopes sent.

[0034] This implementation provides various red envelope management interfaces, making it convenient for users to manage red envelopes and meeting their needs in various management scenarios.

[0035] Secondly, this application provides another method for sending and receiving red envelopes, which can be executed by a second electronic device. The method includes: detecting a first event, the first event indicating that the second electronic device and the first electronic device meet the triggering conditions of a first mode, the first mode being implemented based on short-range wireless communication technology; and in response to the first event, displaying a first interface, the first interface including: a first red envelope indication card, the first red envelope indication card indicating a first red envelope sent by the first electronic device.

[0036] In this method, the second electronic device, responding to the first red envelope sent by the first electronic device, can directly display the red envelope receiving interface, enabling one-touch instant red envelope sending and reducing user operations. Furthermore, this method does not require the electronic devices to be contacts within the address book, reducing the operational complexity of red envelope sending and receiving scenarios and making it easier for two users to send and receive red envelopes. Additionally, this method can enhance the application scenarios and fun of using the red envelope function.

[0037] In one possible implementation, before displaying the first interface, the method further includes: receiving first data sent by the first electronic device, the first data including: a red envelope identifier and first information, the first information being used to display the first interface.

[0038] In one possible implementation, the first information is a deeplink, and the method further includes: launching a red envelope function for payment services based on the link path indicated by the deeplink.

[0039] In one possible implementation, the method further includes: sending second data to a server, the second data including: the UID of the second electronic device and a red envelope identifier; and receiving third data sent by the server, the third data including: the amount of the first red envelope.

[0040] In one possible implementation, the UID of the second electronic device is determined based on the user account logged in on the second electronic device.

[0041] In one possible implementation, the method further includes: displaying a second interface in response to a first operation; the first operation being used to instruct the user to receive the first red envelope; wherein, when the second electronic device detects that a payment account has been activated, the second interface is used to indicate the details of receiving the first red envelope; or, when the second electronic device detects that a payment account has not been activated, the second interface is used to indicate the details of receiving the first red envelope and first guidance information, the first guidance information being used to guide the user to activate a payment account.

[0042] In one possible implementation, before displaying the second interface, the method further includes: in response to a second event, when it is detected that a user account has not been activated, displaying a third interface, the third interface being used to guide the user to activate a user account.

[0043] In one possible implementation, the first method is a method in which the first electronic device and the second electronic device touch each other, and the first event is when the first electronic device touches the second electronic device; or, the first method is a preset air gesture method, and the first event is when the second electronic device detects a second air gesture, and the second air gesture is used to receive the first red envelope.

[0044] In one possible implementation, the method further includes sending fourth data to the server, the fourth data including a red envelope identifier, the fourth data being used to query red envelope receipt details.

[0045] In one possible implementation, the method further includes: displaying a fourth interface in response to a second operation; wherein the second operation is used to view red envelope records, and the fourth interface includes at least one of the following: records of expired red envelopes, records of red envelopes to be received, records of red envelopes to be sent, records of red envelopes received, and records of red envelopes sent.

[0046] Thirdly, this application provides a method for sending and receiving red envelopes, which can be executed by a server. The server receives first data sent by a first electronic device; the first data includes: the UID of the first electronic device and first information, the first information being used to indicate the configuration of the red envelope; based on the first data, a red envelope to be sent and second data are generated, the second data including a red envelope identifier for indicating the red envelope to be sent; the second data is sent to the first electronic device; a third data is received from a second electronic device, the third data including: the UID of the second electronic device and the red envelope identifier; the red envelope to be sent is queried based on the red envelope identifier; a fourth data is generated and sent to the second electronic device, the fourth data including: the amount of the first red envelope allocated to the second electronic device.

[0047] Fourthly, this application provides an electronic device comprising multiple functional modules; the multiple functional modules interact to implement the methods executed by the first electronic device in the first aspect and its embodiments, or to implement the methods executed by the second electronic device in the second aspect and its embodiments. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on specific implementations.

[0048] Fifthly, this application provides an electronic device including at least one processor and at least one memory, wherein the at least one memory stores computer program instructions. When the electronic device is running, the at least one processor executes the method executed by the first electronic device in the first aspect and its embodiments, or executes the method executed by the second electronic device in the second aspect and its embodiments.

[0049] Sixthly, this application provides a server comprising multiple functional modules; the multiple functional modules interact to implement the methods executed by the server in the third aspect and its various embodiments described above. The multiple functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules can be arbitrarily combined or divided based on specific implementations.

[0050] In a seventh aspect, this application provides a server, including at least one processor and at least one memory, wherein the at least one memory stores computer program instructions, and when the server is running, the at least one processor executes the methods executed by the server in the third aspect and its various embodiments described above.

[0051] Eighthly, this application also provides a red envelope sending and receiving system, which may include a first electronic device, M second electronic devices, and a server. The execution of the first electronic device can refer to the methods of the first electronic device described in the first aspect and its embodiments; the execution of the second electronic devices can refer to the methods of the second electronic devices described in the second aspect and its embodiments; and the execution of the server can refer to the methods of the server described in the third aspect and its embodiments. M can be determined based on the red envelope data configured on the first electronic device, and M can be less than or equal to the configured number of red envelopes. For example, if the first electronic device is configured with 10 red envelopes, then M is equal to or less than 10.

[0052] Ninthly, this application also provides a computer program product containing instructions that, when the computer program product is run on a computer, cause the computer to perform the method executed by the first electronic device in the first aspect and its embodiments, or to perform the method executed by the second electronic device in the second aspect and its embodiments.

[0053] In a tenth aspect, this application also provides a computer-readable storage medium storing a computer program that, when executed by a computer, causes the computer to perform the method executed by the first electronic device in the first aspect and its embodiments, or to perform the method executed by the second electronic device in the second aspect and its embodiments.

[0054] In the eleventh aspect, this application also provides a chip for reading a computer program stored in a memory and executing the method executed by the first electronic device in the first aspect and its embodiments, or executing the method executed by the second electronic device in the second aspect and its embodiments.

[0055] In a twelfth aspect, this application also provides a chip system including a processor for supporting a computer device in implementing the methods executed by a first electronic device according to the first aspect and its embodiments, or implementing the methods executed by a second electronic device according to the second aspect and its embodiments. In one possible design, the chip system further includes a memory for storing programs and data necessary for the computer device. The chip system may be composed of chips or may include chips and other discrete devices.

[0056] The beneficial effects of the second to twelfth aspects mentioned above can be found in the introduction of the first aspect, and will not be repeated here. Attached Figure Description

[0057] Figure 1 This is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application;

[0058] Figure 2 A software structure block diagram of an electronic device provided in an embodiment of this application;

[0059] Figure 3 A schematic diagram of a system architecture applicable to the red envelope sending and receiving method provided in the embodiments of this application;

[0060] Figure 4 A schematic diagram of the red envelope entry point for a red envelope sending and receiving method provided in this application embodiment;

[0061] Figure 5a One of the interface diagrams for the red envelope sending and receiving method provided in the embodiments of this application;

[0062] Figure 5b A second schematic diagram of the interface for sending and receiving red envelopes provided in this application embodiment;

[0063] Figure 5c The third schematic diagram of the interface for sending and receiving red envelopes provided in the embodiments of this application;

[0064] Figure 6 The fourth schematic diagram of the interface for sending and receiving red envelopes provided in the embodiments of this application;

[0065] Figure 7 This application provides a schematic diagram illustrating a scenario for selecting a red envelope cover.

[0066] Figure 8 One of the schematic diagrams of a guide interface for opening a Huawei account provided in this application embodiment;

[0067] Figure 9 A second schematic diagram of a guide interface for opening a payment account, provided as an embodiment of this application;

[0068] Figure 10 A schematic diagram of a guide interface for unfreezing a payment account provided in an embodiment of this application;

[0069] Figure 11a A second schematic diagram of a guide interface for opening a Huawei account, provided as an embodiment of this application;

[0070] Figure 11b A second schematic diagram of a guide interface for opening a payment account, provided as an embodiment of this application;

[0071] Figure 11c The third schematic diagram of a guide interface for opening a payment account provided in this application embodiment;

[0072] Figure 12a One of the schematic diagrams of a red envelope management interface provided in an embodiment of this application;

[0073] Figure 12b A second schematic diagram of a red envelope management interface provided in an embodiment of this application;

[0074] Figure 13 This is one of the flowcharts illustrating a method for sending and receiving red envelopes provided in an embodiment of this application;

[0075] Figure 14 A second schematic flowchart illustrating a method for sending and receiving red envelopes, provided as an embodiment of this application;

[0076] Figure 15 The third flowchart illustrating a method for sending and receiving red envelopes provided in this application embodiment;

[0077] Figure 16 The fourth flowchart illustrating a method for sending and receiving red envelopes provided in this application embodiment;

[0078] Figure 17 The fifth flowchart illustrating a method for sending and receiving red envelopes provided in this application embodiment;

[0079] Figure 18 This is the sixth flowchart illustrating a method for sending and receiving red envelopes, provided as an embodiment of this application. Detailed Implementation

[0080] The embodiments of this application will now be described in further detail with reference to the accompanying drawings.

[0081] The embodiments of this application involve at least one, including one or more; where "multiple" means two or more. Furthermore, it should be understood that in the description of this specification, terms such as "first" and "second" are used only for descriptive purposes and should not be construed as indicating relative importance or order. For example, "first electronic device" and "second electronic device" do not represent the degree of importance of the two or their order, but are merely for descriptive distinction. In the embodiments of this application, "and / or" merely describes an association relationship, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0082] References to "one embodiment" or "some embodiments" as used in this specification mean that one or more embodiments of this specification include a particular feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0083] This application provides a method for sending and receiving red envelopes (digital cash gifts), as well as an electronic device. This method is applicable to electronic devices and provides a new way to send and receive red envelopes. In this method, a first electronic device, based on a displayed red envelope sending interface, can send red envelopes to one or more second electronic devices using short-range wireless communication technology. Correspondingly, the second electronic devices can display a red envelope receiving interface based on short-range wireless communication technology to receive red envelopes sent by the first electronic device. Thus, this method eliminates the need for pre-established contact lists between electronic devices, improving the convenience of sending and receiving red envelopes.

[0084] Among these methods, the sending and receiving of red envelopes based on short-range wireless communication technology can include touch-to-pay or predefined air gestures. For example, when the first electronic device displays the red envelope sending interface, it can detect a touch with the second electronic device and send a red envelope to the second electronic device. Correspondingly, the second electronic device, in response to a touch with the first electronic device, can display the red envelope receiving interface.

[0085] In the above example, OneHop is a multi-terminal service collaboration solution technology. Relying on near-field communication (NFC) or short-range wireless communication protocols such as Bluetooth, it opens up multi-device touch interaction capabilities to applications on electronic devices such as mobile phones and third-party devices. This allows for the connection of devices across all scenarios, providing users with an efficient experience of seamless switching between various services across multiple devices. For example, OneHop can involve touching the top of a first electronic device and the top of a second electronic device, or it can involve touching the back of a first electronic device and the back of a second electronic device. It should be noted that the specific operation method of OneHop in this application embodiment is not limited; for example, touching the top of the first electronic device and the bottom of the second electronic device can be determined according to the hardware design of the electronic devices.

[0086] In some possible implementations of the "tap-to-win" feature, in a scenario where the first electronic device displays a red envelope sending interface, if the second electronic device detects that the ambient light data is less than a preset light intensity, it can trigger the second electronic device to send a broadcast signal so that other electronic devices that may be nearby, such as the first electronic device, can detect the broadcast signal. The second electronic device can detect ambient light data using an ambient light sensor.

[0087] Therefore, as long as the distance between the first and second electronic devices is less than a preset threshold and / or the magnetic data of the first and second electronic devices meets a preset correlation condition, the first electronic device can be triggered to send a red envelope. Then, the second electronic device can receive the red envelope. In this way, red envelope sending and receiving between the first and second electronic devices is realized, achieving one-touch instant red envelope sending based on both ends, which can improve the convenience of sending and receiving red envelopes.

[0088] In the above implementation, the preset threshold refers to a pre-set distance threshold, such as a distance threshold less than 0.5 mm. This application embodiment does not limit the setting of the preset threshold. It should be understood that if the distance between the first electronic device and the second electronic device is less than the preset threshold, it indicates that the positions of the first electronic device and the second electronic device are relatively close. If the distance between the first electronic device and the second electronic device is greater than or equal to the preset threshold, it indicates that the positions of the first electronic device and the second electronic device are not close. In some embodiments, the first electronic device, in response to receiving a broadcast signal from the second electronic device, determines the distance between the first electronic device and the second electronic device based on the broadcast signal. The process of determining the distance between the first electronic device and the second electronic device based on the broadcast signal can be: determining the transmission distance corresponding to the signal strength of the broadcast signal, and using this as the distance between the first electronic device and the second electronic device. For example, the first electronic device may pre-store the transmission distances corresponding to different signal strengths. It is worth noting that in other embodiments, the first electronic device can also use other methods to determine the distance between the first electronic device and the second electronic device, and this application embodiment does not limit this.

[0089] In the above implementation, the magnetic data of the first electronic device is used to characterize the magnetic field of the first electronic device, such as magnetic field strength and direction. It is understood that the location of the first electronic device can be determined based on its magnetic data. In some embodiments, the first electronic device may use a magnetometer sensor to acquire its magnetic data. It is worth noting that in other embodiments, the first electronic device may also use other methods to acquire magnetic data. This application does not limit this approach. The magnetic data of the second electronic device is similar to that of the first electronic device and will not be described again here. The preset correlation condition refers to a pre-set correlation condition, such as the magnetic data of the first electronic device being the same as that of the second electronic device, or the similarity between the magnetic data of the first electronic device and that of the second electronic device being greater than or equal to a preset similarity. This application does not limit the setting of the preset correlation condition.

[0090] The electronic devices in this application embodiment can be portable electronic devices such as mobile phones, tablets, and laptops, or wearable devices such as smartwatches, smart bracelets, smart headphones, and smart glasses; or, the electronic devices can be smart home devices such as large screens and smart speakers. This application embodiment does not impose any restrictions on the specific type of electronic device.

[0091] The electronic device in this application embodiment may be, but is not limited to, carrying... Or electronic devices with other operating systems.

[0092] Figure 1This is a schematic diagram of the structure of an electronic device 100 provided in an embodiment of this application. Figure 1 As shown, the electronic device 100 may include a processor 110, internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a sensor module 180, buttons 190, a motor 191, an indicator 192, a camera 193, a display screen 194, etc.

[0093] Processor 110 may include one or more processing units, such as an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). Different processing units may be independent devices or integrated into one or more processors. The controller may serve as the central nervous system and command center of the electronic device 100. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution. Processor 110 may also include memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that processor 110 has recently used or is repeatedly used. If processor 110 needs to reuse an instruction or data, it can directly retrieve it from the memory. This avoids repeated access, reduces the waiting time of processor 110, and thus improves system efficiency.

[0094] In one possible example, when electronic device 100 is a device for sending red envelopes, processor 110 can obtain basic configuration information of red envelopes from the server and generate relevant interfaces for sending red envelopes, such as red envelope configuration interface and red envelope sending interface; it can also perform information verification, thereby ensuring the security of red envelope sending.

[0095] In another possible example, when electronic device 100 is a device for receiving red envelopes, processor 110 can obtain the second red envelope sending data from the device that sent the red envelope, and generate a relevant interface for receiving red envelopes based on the second red envelope sending data, such as a red envelope receiving interface and a red envelope receiving details interface; it can also perform information verification, thereby ensuring the security of receiving red envelopes.

[0096] USB interface 130 is an interface that conforms to the USB standard specification, specifically it can be a Mini USB interface, Micro USB interface, USB Type C interface, etc. USB interface 130 can be used to connect a charger to charge electronic device 100, and it can also be used for data transfer between electronic device 100 and peripheral devices.

[0097] The charging management module 140 receives charging input from the charger. The power management module 141 connects to the battery 142, and the charging management module 140 connects to the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the processor 110, internal memory 121, external memory, display 194, camera 193, and wireless communication module 160, etc.

[0098] The wireless communication function of electronic device 100 can be implemented through antennas, wireless communication module 160, modem processor, and baseband processor. The antennas are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover one or more communication frequency bands. Different antennas can also be multiplexed to improve antenna utilization. For example, antennas can be multiplexed as diversity antennas for a wireless local area network. In some other embodiments, the antennas can be used in conjunction with tuning switches.

[0099] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), Zigbee, and satellite imagery. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via an antenna, modulates and filters the electromagnetic wave signal, and sends the processed signal to the processor 110. The wireless communication module 160 can also receive signals to be transmitted from the processor 110, modulate and amplify them, and then convert them into electromagnetic waves for radiation via the antenna. In this embodiment, the electronic device 100 can use NFC or Bluetooth and other short-range wireless communication technologies to send and receive red envelopes (digital cash gifts) by tapping them with other electronic devices.

[0100] In some embodiments, the antenna of the electronic device 100 is coupled to the wireless communication module 160, enabling the electronic device 100 to communicate with networks and other devices via wireless communication technologies. The wireless communication technologies may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies. The GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0101] The display screen 194 is used to display the display interface of an application, such as the display page of an application installed on the electronic device 100. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0102] In one possible example, when electronic device 100 is a device for sending red envelopes, display screen 194 can be used to display interfaces related to sending red envelopes, such as red envelope configuration interfaces and red envelope sending interfaces; it can also display interfaces related to information verification, such as real-name verification interfaces and payment verification interfaces; and it can also display interfaces related to red envelope management, such as red envelope record interfaces, red envelope record interfaces to be received interfaces, red envelope record interfaces sent interfaces, red envelope received interfaces, and red envelope receiving details interfaces. It can be understood that electronic device can not only send red envelopes but also receive them.

[0103] In another possible example, when the electronic device 100 is a device for receiving red envelopes, the display screen 194 can be used to display relevant interfaces for receiving red envelopes, such as a red envelope receiving interface and a red envelope receiving details interface; it can also display relevant interfaces for information verification, such as a real-name verification interface; and it can also display relevant interfaces for red envelope management, such as a red envelope record interface, a red envelope record to be received interface, a red envelope record sent interface, a red envelope received interface, and a red envelope receiving details interface.

[0104] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element through a lens to generate an optical image. In some embodiments, electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0105] The internal memory 121 can be used to store computer executable program code, which includes instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system and software code for at least one application. The data storage area may store data generated during the use of the electronic device 100 (e.g., captured images, recorded videos, etc.). Furthermore, the internal memory 121 may include high-speed random access memory and non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. In this embodiment, the internal memory 121 may store red envelope configuration data, red envelope details, etc., obtained from the server.

[0106] Electronic device 100 can implement audio functions such as music playback and recording through audio module 170, speaker 170A, receiver 170B, microphone 170C, and application processor.

[0107] The sensor module 180 may include, but is not limited to, an ambient light sensor 180A, a magnetic sensor 180B, and a touch sensor 180C. The ambient light sensor 180A is used to sense ambient light brightness. In this embodiment, the ambient light sensor 180C is used to detect ambient light data of the terminal device to determine whether the terminal device is obstructed. The touch sensor 180C is also called a "touch panel." The touch sensor 180C can be disposed on the display screen 194, and the touch sensor 180C and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180C is used to detect touch operations applied to or near it. The touch sensor 180C can transmit the detected touch operation to the application processor to determine the touch event type. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180C may also be disposed on the surface of the electronic device 100, in a different position than the display screen 194. In this embodiment, the magnetic sensor 180B can be a magnetometer sensor used to detect magnetic data of the terminal device.

[0108] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch buttons. Electronic device 100 can receive button input and generate key signal inputs related to user settings and function control of electronic device 100. Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, touch operations applied to different applications (such as taking photos, playing audio, etc.) can correspond to different vibration feedback effects. Touch vibration feedback effects can also be customized. Indicator 192 can be an indicator light, used to indicate charging status, battery level changes, or to indicate messages, missed calls, notifications, etc.

[0109] Understandable, Figure 1 The components shown do not constitute a specific limitation on the electronic device 100. The electronic device may also include more or fewer components than shown, or combine some components, or separate some components, or have different component arrangements. Furthermore, Figure 1 The combination / connection relationships between the components can also be adjusted and modified.

[0110] Figure 2 This is a software structure block diagram of an electronic device provided in an embodiment of this application. For example... Figure 2 As shown, the software architecture of an electronic device can be a layered architecture. For example, the software can be divided into several layers, each with a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the operating system is divided into five layers, from top to bottom: the application layer, the application framework layer (framework, FWK), the runtime and system libraries, the kernel layer, and the hardware layer.

[0111] The application layer can include a series of application packages. For example... Figure 2 As shown, the application layer can include camera, settings, skin modules, user interface (UI), third-party applications, etc. Third-party applications can include gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, SMS, etc.

[0112] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer can include some predefined functions. For example... Figure 2As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, and a notification manager. In this embodiment, the application framework layer may include sharekit capabilities and paymentkit capabilities.

[0113] The ShareKit capability can be used to send or receive red envelopes (digital cash gifts) between multiple electronic devices. For example, ShareKit can detect touch events such as touching the top or back of an electronic device to send or receive red envelopes across multiple devices. Furthermore, ShareKit can provide cross-application and cross-platform sharing capabilities for content such as text, images, and videos. For instance, a first electronic device can act as a sending terminal, and a second electronic device can act as a receiving terminal. Through the sharing service, the first electronic device can send text, images, and videos to the second electronic device.

[0114] Payment kit capabilities can be used to implement payment, marketing, and operational functions for electronic devices when sending and receiving red envelopes. For example, payment kit capabilities can be used to query basic configuration information on the red envelope generation interface, configure red envelopes on the red envelope configuration interface, request to launch the cashier, display the red envelope sending interface, generate second red envelope sending data, detect red envelope receiving operations, detect red envelope sending operations, detect red envelope management operations, and perform other red envelope-related processing.

[0115] The window manager is used to manage windowed applications. It can obtain the screen size, determine if a status bar is present, lock the screen, and capture screenshots. The content provider stores and retrieves data, making this data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0116] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0117] A phone manager is used to provide communication functions for electronic devices. For example, it manages call status (including connection and disconnection).

[0118] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0119] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0120] The runtime includes the core libraries and the virtual machine. The runtime is responsible for the scheduling and management of the operating system.

[0121] The core library consists of two parts: one part contains the functionalities that the Java language needs to call, and the other part contains the core libraries of the operating system. The application layer and application framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0122] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), image processing libraries, etc.

[0123] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0124] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, and AMR.

[0125] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0126] A 2D graphics engine is a graphics engine for 2D drawing.

[0127] The kernel layer is the layer between hardware and software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver.

[0128] The hardware layer can include various types of sensors, such as accelerometers, gyroscopes, and touch sensors.

[0129] It should be noted that, Figure 1 and Figure 2The structure shown is merely an example of an electronic device provided in this application embodiment and is not intended to limit the electronic device provided in this application embodiment in any way. In specific implementations, the electronic device may have more than Figure 1 or Figure 2 The structure shown may contain more or fewer devices or modules.

[0130] The following describes a method for sending and receiving red envelopes provided in an embodiment of this application.

[0131] Figure 3 This is a schematic diagram of a system architecture applicable to the red envelope sending and receiving method provided in this application embodiment. The system architecture may include a first electronic device and one or more second electronic devices. The first electronic device can be understood as an electronic device sending red envelopes, or a red envelope sending device; the second electronic devices can be understood as electronic devices receiving red envelopes, or red envelope receiving devices. Optionally, the number of second electronic devices can be determined based on the number of red envelopes sent by the first electronic device. For example, when the first electronic device sends one red envelope, such as a personalized red envelope, the system architecture may include one second electronic device. Or, for example, when the first electronic device sends a red envelope containing 10 sub-red envelopes, such as a lucky draw red envelope, the system architecture may include 10 second electronic devices.

[0132] For example, the sending and receiving of red envelopes can be achieved between the first electronic device and the second electronic device in one or more ways.

[0133] In some possible implementations, the first and second electronic devices can send and receive red envelopes by tapping each other.

[0134] In other possible implementations, the first and second electronic devices can send and receive red envelopes not only through a tap-to-pay interaction, but also through air gestures, QR codes, or password-based red envelopes. For example, in a scenario where the first electronic device sends 10 red envelopes, 5 second electronic devices can receive them via a tap-to-pay interaction, 1 second electronic device can receive them via air gestures, 2 second electronic devices can receive them via QR code scanning, and the remaining 2 second electronic devices can receive them via password-based red envelopes. The tap-to-pay interaction can be triggered by touching the top of the first and second electronic devices, or by touching the back of the first and second electronic devices; this application does not limit the specific operation method of the tap-to-pay interaction.

[0135] The air gesture method can be preset. For example, on the red envelope sending interface of the first electronic device, the user can send a red envelope by grabbing it in the air, and on the second electronic device, the user can receive the red envelope from the first electronic device by releasing it in the air.

[0136] For example, the QR code method could involve a first electronic device responding to a user's flipping of a red envelope icon card, triggering the display of a QR code corresponding to the red envelope. This QR code can be used to instruct the first electronic device to send red envelope data, such as a red envelope identifier, red envelope cover data, a greeting, or a deep link. Correspondingly, a second electronic device can scan the QR code displayed on the first electronic device to receive the red envelope sent by the first electronic device.

[0137] For example, in the password-protected red envelope method, the first electronic device may generate a password-protected red envelope in response to a user's action of generating such an envelope. Correspondingly, the second electronic device displays a red envelope receiving interface in response to the user's action of entering the password at a preset location. Alternatively, the password-protected red envelope method may also involve the first electronic device flipping a red envelope icon card in response to a user's action, triggering the flip to display the password corresponding to the red envelope. This password can be used by the second electronic device to receive the red envelope sent by the first electronic device. Correspondingly, the second electronic device displays a red envelope receiving interface in response to the user's action of entering the password at a preset location.

[0138] It should be noted that the specific operation method for sending and receiving red envelopes is not limited in the embodiments of this application. For example, in response to the user's flipping operation of the red envelope illustration card, the first electronic device can also be manually set to switch to displaying the QR code or the password corresponding to the red envelope. As another example, the first electronic device can also respond to the user's click operation on a preset control to determine whether to display the QR code or the password corresponding to the red envelope.

[0139] Furthermore, it can be understood that the first electronic device can support various payment methods, including tap-to-pay, air gesture, QR code, and password-based red envelopes. Correspondingly, the second electronic device can support at least one of these methods. When the second electronic device supports one method, it can receive red envelopes from the first electronic device through that supported method. When the second electronic device supports multiple methods, it can receive red envelopes from the first electronic device through a user-selected method.

[0140] In this way, by providing multiple methods for sending and receiving red envelopes, the needs of various red envelope sending and receiving scenarios can be met. For example, if the second electronic device supports short-range wireless communication methods such as tap-to-receive or air gestures to receive red envelopes, it can conveniently receive red envelopes through these methods. If the second electronic device does not support short-range wireless communication, red envelopes can still be successfully received via QR code or password red envelopes. Furthermore, when the red envelope sent by the first electronic device includes multiple sub-red envelopes, providing multiple methods for sending and receiving red envelopes does not restrict whether the second electronic device supports short-range wireless communication, allowing users to easily choose a method to send and receive red envelopes, thereby improving the user experience of the red envelope function.

[0141] based on Figure 3 The system architecture shown below will be used to illustrate various application scenarios that the method provided by the embodiments of this application can offer, facilitating understanding of the red envelope sending and receiving method provided by the embodiments of this application. The following embodiments use a tap-to-send red envelope method between a first electronic device and a second electronic device as an example; other red envelope sending and receiving methods will not be detailed. It is understood that the method provided by the embodiments of this application is not limited to implementing the following application scenarios.

[0142] (I) The trigger entry point for sending red envelopes

[0143] Figure 4 This is a schematic diagram of the red envelope entry point for a red envelope sending and receiving method provided in an embodiment of this application.

[0144] like Figure 4 As shown in interface 400A, the first electronic device can provide a trigger entry 401 for sending red envelopes on the negative one screen interface.

[0145] like Figure 4 As shown in interface 400B, the first electronic device can provide a trigger entry for sending red envelopes in the wallet application 402.

[0146] like Figure 4 As shown in interface 400C, the first electronic device can also provide a trigger entry for sending red envelopes through the smart assistant 403.

[0147] For example, the first electronic device responds to via Figure 4 The triggering of the trigger entry shown in interface 400A, or interface 400B, or interface 400C will display interface 400D. Interface 400D can be understood as the red envelope configuration interface before sending the red envelope, which is used to generate the red envelope to be sent.

[0148] It should be noted that the trigger entry point for sending red envelopes is not limited in this embodiment of the application, such as... Figure 4The trigger entry shown is just one example of a few possibilities; for example, a trigger entry could also be provided in the control center interface.

[0149] (II) The overall process of sending and receiving red envelopes

[0150] Figures 5a to 5c This is a schematic diagram of the interface for the method of sending and receiving red envelopes provided in an embodiment of this application. Figure 5a Interfaces 500A, 500B1, and 500C, and Figure 5c Interfaces 500F and 500B2 are the display interfaces of the first electronic device. Figure 5b Interfaces 500D and 500E are the display interfaces of the second electronic device.

[0151] like Figure 5a Interface 500A, as shown in the image, is an example of a configuration interface for sending red envelopes by a first electronic device. Interface 500A can be based on... Figure 4 The interface 400D is obtained from the interface. Interface 500A may include a first configuration area 501, a second configuration area 502, a third configuration area 503, and a confirmation control 504. Among these,

[0152] (1) The first configuration area 501 is used to select the type of red envelope. For example, the red envelope type may include ordinary red envelope, lucky red envelope, and lucky red envelope. Among them, ordinary red envelope may be a red envelope with the same amount for each sub-red envelope and the number of red envelopes can be configured; lucky red envelope may be a red envelope with random amount for each sub-red envelope and the number of red envelopes can be configured; lucky red envelope may be a single red envelope with a specific amount, such as ¥6.66, ¥8.88, etc. For example, the default red envelope type selected in interface 400D is ordinary red envelope, and the red envelope type selected in interface 500A is lucky red envelope.

[0153] It should be noted that the embodiments of this application do not limit the types of red envelopes included in the first configuration area or the number of red envelope types. For example, red envelope types may also include exclusive red envelopes, coupon red envelopes (that is, red envelopes may include electronic coupon information), and physical red envelopes (that is, red envelopes may include electronic physical information). Among them, exclusive red envelopes may be red envelopes with a target red envelope recipient user, and other users cannot receive the red envelope. For example, the number of red envelope types may include more or fewer, such as four types or one type.

[0154] (2) The second configuration area 502 is used to display the selected red envelope type. For example, when the selected red envelope type is a lucky red envelope, the second configuration area 502 may not need to include the number of red envelopes. As another example, when the selected red envelope type is a coupon red envelope, the second configuration area 502 may include selectable electronic coupons, etc.

[0155] like Figure 5a As shown in interface 500A, taking the selected red envelope type as a lucky draw red envelope as an example, the second configuration area 502 may include, but is not limited to: red envelope amount, number of red envelopes, and blessing message.

[0156] (3) The third configuration area 503 is used to select a red envelope cover. For example, when the user does not switch to another red envelope cover, a default red envelope cover can be used; the default red envelope cover can be the system default or a custom default. The process for switching the selected red envelope cover is as described below. Figure 7 As shown, details will not be elaborated here.

[0157] (4) A determination control 504 is used to generate a red envelope to be sent based on the configuration of the first configuration area 501, the second configuration area 502, and the third configuration area 503. For example, when the required fields in the first configuration area 501, the second configuration area 502, and the third configuration area 503 are not configured, the determination control 504 can be displayed as an inoperable state. The required fields may include, for example, the red envelope amount and the number of red envelopes. The blessing message and the red envelope cover can be optional fields, and when not selected, they can be determined as the default configuration.

[0158] like Figure 5a As shown in interface 500A, the confirmation control 504 can be displayed as inserting money into a red envelope. In some other possible examples, when the selected red envelope type is a physical red envelope, the confirmation control 504 can be displayed as inserting a gift into a red envelope.

[0159] In interface 500A, in response to a click on the confirmation control 504, the first electronic device can display interface 500B1 after information verification. Interface 500B1 is used to send red envelopes. The information verification process will be described later and will not be repeated here.

[0160] As shown in interface 500B1, it may include a first prompt area 505 and a second prompt area 5061. Among them,

[0161] (1) The first prompt area 505 is used to prompt the user on how to send and receive red envelopes. As shown in interface 500B1, the first prompt area 505 can use diagrams and text to prompt the user that red envelopes can be sent and received by tapping. The diagrams can be used to demonstrate how the first electronic device and the second electronic device can send and receive red envelopes by tapping. The text can include prompts such as "Tap to send red envelope" for the user facing the first electronic device and "Tap to receive red envelope" for the user facing the second electronic device.

[0162] It is understandable that the first prompt area 505 can also use illustrations and text to prompt users that they can send and receive red envelopes in other ways. For example, when prompting users that they can send and receive red envelopes via QR code, the illustration can be used to demonstrate that the user can click on any red envelope in the second prompt area 5061 on the first electronic device, thereby triggering the display of the QR code corresponding to the red envelope. The second electronic device can send and receive red envelopes by scanning the QR code displayed on the first electronic device; the text could be, for example, "Flip the red envelope cover to display the QR code".

[0163] It should be noted that the specific implementation of the first prompt area 505 in this embodiment is not limited. For example, when the first prompt area 505 is used to prompt multiple ways of sending and receiving red envelopes, it can be displayed in a tiled manner, or multiple cyclically switching window interfaces can be used to display multiple ways of sending and receiving red envelopes in turn.

[0164] (2) The second prompt area 5061 is used to prompt the user about the receiving status of the red envelope. For example, the second prompt area 5061 may include, but is not limited to: a text prompting the remaining amount of the red envelope, and a red envelope illustration card.

[0165] Optionally, the red envelope illustration cards displayed in the second prompt area 5061 can correspond one-to-one with the number of red envelopes obtained in the second configuration area 502 in interface 500A. Furthermore, after a red envelope is received, the second prompt area 5061 is refreshed. For example, the remaining red envelope quantity prompt text and the number of red envelope illustration cards are refreshed. See also Figure 5c As shown in the second prompt area 5062 of interface 500B2, compared to the second prompt area 5061 of interface 500B1, the remaining number of red envelopes prompt text is updated to 9 red envelopes remaining, and the number of red envelope illustration cards is updated to 9.

[0166] Alternatively, due to the display size of the second prompt area 5061, the maximum number of red envelope illustration cards that can be displayed can be set. For example, when the number of remaining red envelopes is greater than the maximum display number, the maximum number of red envelope illustration cards can be displayed; when the number of remaining red envelopes is less than or equal to the maximum display number, red envelope illustration cards corresponding one-to-one with the number of remaining red envelopes can be displayed. Figure 6 As shown in the examples, taking a maximum display quantity of 3 as an example, as shown in interface 600A, when the remaining number of red envelopes is 9, 3 red envelope illustration cards are displayed in the second prompt area 601; as shown in interface 600B, when the remaining number of red envelopes is 3, 3 red envelope illustration cards are still displayed in the second prompt area 602; as shown in interface 600C, when the remaining number of red envelopes is 2, 2 red envelope illustration cards are displayed in the second prompt area 603; and as shown in interface 600D, when the remaining number of red envelopes is 1, 1 red envelope illustration card is displayed in the second prompt area 604. It can be understood that the remaining red envelope quantity prompt text included in the second prompt area 5062 corresponds to the actual remaining quantity.

[0167] In this way, by associating the red envelope icon displayed on the red envelope sending interface with the number of remaining red envelopes, the number of remaining red envelopes can be more realistically reflected, enhancing the experience and fun of sending and receiving red envelopes.

[0168] During the process of displaying interface 500B1 on the first electronic device, the first electronic device can display interface 500C in response to a tap with the second electronic device. Interface 500C may include a tap display effect 507, a red envelope icon card, and a prompt control 508 for indicating to swipe up to send. For example, the first electronic device can send a red envelope in response to a swipe up operation on the red envelope icon card. In this way, on the first electronic device, the swipe operation can simulate the experience of sending red envelopes in real life, which can enhance the fun and user experience of sending and receiving red envelopes.

[0169] Correspondingly, the second electronic device, in response to a touch with the first electronic device, can display interface 500D. For easier understanding, please refer to... Figure 5bThe interface 500D shown is included. Interface 500D may include: a tap-to-display effect 509, a red envelope indicator card 510, a receive control 512A, and a reject control 512B. The red envelope indicator card 510 may also display prompt text indicating the user sending the red envelope, such as user A shown in interface 500D. For example, in interface 500D, in response to a click on the receive control 512A, the second electronic device may display interface 500E, which displays details of receiving the red envelope, such as prompt text indicating the user receiving the red envelope, such as user B shown in interface 500E.

[0170] It should be noted that the details interface for receiving red envelopes is not limited in this embodiment. For example, it may only display the details of the current user's red envelope receipts, or it may display the real-time details of the red envelope receipts.

[0171] In addition, it should be noted that in this application embodiment, the interface displayed by the second electronic device before the second electronic device touches the first electronic device is not limited. That is, this application does not limit the interface displayed by the second electronic device before the display interface 500D. For example, it can display a desktop interface or other application interfaces.

[0172] In one possible implementation, after the second electronic device receives the red envelope, the first electronic device can display something like this: Figure 5c Interface 500F is shown; then, after the display duration reaches the preset duration or in response to a click operation on the "Continue Sending Red Envelopes" control, interface 500B2 can be displayed. In interface 500B2, the first electronic device can refer to the processes shown in interfaces 500C and 500F to continue sending the remaining red envelopes to other second electronic devices until the remaining red envelopes are sent. Correspondingly, the other second electronic devices can refer to the processes shown in interfaces 500D and 500E to receive the red envelopes from the first electronic device. The processing flow between the first electronic device and the other second electronic devices will not be described in detail in this application. The preset duration can be, for example, 3 seconds (S) or 5 seconds.

[0173] pass Figures 5a to 5c The application scenario shown allows two electronic devices to conveniently send and receive red envelopes by tapping each other, based on a sharing service. Therefore, this method provides a new way to send and receive red envelopes, enhancing the fun and improving the user experience. Furthermore, this method eliminates the restriction of whether two electronic devices are contacts in each other's address books, facilitating easier interaction and improving the efficiency of the red envelope function.

[0174] (III) Choosing a Red Envelope Cover

[0175] Figure 7 This is a schematic diagram illustrating a scenario for selecting a red envelope cover, provided as an embodiment of this application. Based on Figure 5a As shown in interface 500A, the third configuration area 503 may include a jump control 5031. In interface 500A, in response to a click operation on the jump control 5031, the first electronic device can display interface 700A, which is used to display multiple different red envelope covers, such as red envelope cover 1, red envelope cover 2, ..., red envelope cover 6, etc. For example, in interface 700A, in response to a selection operation on red envelope cover 4 and a click operation on the use control, the first electronic device can display interface 700B. As can be seen from interface 700B, compared to interface 500A which defaults to using red envelope cover 1, it switches to using red envelope cover 4 as the red envelope cover to be sent.

[0176] (iv) Information verification process on the first electronic device

[0177] The first electronic device, acting as a red envelope sending device, can verify information including user real-name authentication and payment verification. For example, user real-name authentication can be obtained by guiding the user to upload identification information, or it can be obtained from an already verified user account. For example, payment methods can include bank card payment, account balance payment, etc. It is understood that when the first electronic device can obtain a secure bank card for payment, it can send red envelopes; or, when the first electronic device can obtain a secure account balance for payment, it can also send red envelopes. It should be noted that the specific implementation of the information verification process on the first electronic device is not limited in this embodiment.

[0178] In one possible implementation, when the first electronic device detects that a user account has not been activated, it can display a guided interface for activating a user account. For example, after detecting a trigger event for sending a red envelope, the interface for activating a user account can be displayed. Taking a Huawei account as an example... Figure 8 This is a schematic diagram of a guide interface for opening a Huawei account, provided as an embodiment of this application. Figure 4Taking the triggering of sending a red envelope in interface 400A as an example, if the first electronic device has not activated a Huawei account, it can display interface 900A, which is the login interface for a Huawei account and can also facilitate Huawei account registration. If the first electronic device already has an activated Huawei account, it can continue to display interface 400D. For example, the user's real-name information can be obtained from the Huawei account to determine the user to whom the red envelope will be sent. Another example is when the Huawei account is not associated with the user's real-name information, the user can be guided to upload identification information. For example, see the following text... Figure 11c As shown, details will not be elaborated here.

[0179] In another possible implementation, when the first electronic device detects that a payment account is not activated, it can display a guided interface to the user for activating a payment account. See also... Figure 9 This is a schematic diagram of a guide interface for opening a payment account provided in an embodiment of this application. Figure 9 The interface 900B, compared to Figure 4 In the red envelope sending interface shown in interface 400D, when the first electronic device detects that no payment account has been activated, it can display control 901 in interface 900B. Control 901 guides the user to activate the payment account by adding a bank card. In interface 900B, in response to a click on control 901, the first electronic device displays interface 900C, which is an example of adding a bank card. After the first electronic device detects that the bank card has been added successfully, it can continue to display interface 400D. From... Figure 9 As can be seen, not having a payment account does not affect the configuration of the red envelope. After configuring information such as the red envelope amount, number of red envelopes, blessing message, and red envelope cover, users can be guided to open a payment account.

[0180] In another possible implementation, if a payment account has already been activated, and an abnormal account status is detected during payment, the user can be guided to unfreeze their account. See also... Figure 10 This is a schematic diagram of a guide interface for unfreezing a payment account provided in an embodiment of this application. When making a payment as shown in interface 400D, if the first electronic device detects an abnormal payment account status, it can display interface 900D. Interface 900D is used to guide the user through facial recognition verification to unfreeze the account; wherein... Figure 10 The example used is a Huawei Pay account. It's understood that after successful verification, the 400D display interface can be restored.

[0181] It should be noted that the above Figures 8 to 10 This paper introduces several possible scenarios for the information verification process on a first electronic device. In actual implementation, other methods or entry points can also be used to guide users to verify information; this application does not limit the specific implementation method.

[0182] (v) Information verification process on the second electronic device

[0183] The second electronic device, acting as a red envelope receiving device, can verify user identity information, which may include real-name verification. For example, real-name verification can be performed by guiding the user to upload identification information, or it can be obtained from an already verified user account.

[0184] In one possible implementation, when the second electronic device detects that a user account has not been activated, it can display a guided interface for activating a user account. Taking a Huawei account as an example, the second electronic device can display an interface for activating a Huawei account after detecting a red envelope receiving operation. See also Figure 11a This is a schematic diagram of a guide interface for opening a Huawei account provided in an embodiment of this application. Figure 5b The click operation of the receiving control 512A in interface 500D is used as an example. If the second electronic device has not activated a Huawei account, it can display interface 1100A, which is the login interface for a Huawei account and can also be used for Huawei account registration. If the second electronic device has activated a Huawei account, it can continue to display interface 500E. For details, please refer to interface 1100A. Figure 8 The interface shown in 900A is not described in detail here.

[0185] In another possible implementation, when the second electronic device detects that a payment account has not been activated, it can first display a red envelope receiving details interface to the user. For example, the red envelope receiving details interface can display a guide interface for activating a payment account. See [link / reference] Figure 11b This is a schematic diagram of a guide interface for opening a payment account provided in an embodiment of this application. Figure 5b Using interface 500D as an example, when the second electronic device detects that no payment account has been activated, it can display interface 1100B. Interface 1100B may include guidance information 1101 and control 1102. Guidance information 1101 is used to prompt the user that the red envelope is about to be credited, and control 1102 is used to guide the user to activate the payment account by adding a bank card in order to receive the red envelope. The process of adding a bank card can be found in [reference needed]. Figure 9 As shown, it will not be elaborated further here.

[0186] In another possible implementation, the second electronic device can also display a guide interface for opening a payment account to the user within any interface using the red envelope function. See also Figure 11c This is a schematic diagram of another guide interface for opening a payment account provided in an embodiment of this application. Figure 11cAs can be seen in interface 1100C, when the second electronic device sends a red envelope, in the red envelope configuration interface, if the electronic device detects that the payment account is not activated, it can display a prompt area 1103. Prompt area 1103 can include prompt text guiding the user to activate a payment account and a control 1103A for uploading identification documents. In interface 1100C, in response to a click on control 1103A, the second electronic device can display interface 1100D, which can be used to guide the user to upload identification documents.

[0187] In another possible implementation, the handling of the second electronic device when it detects an abnormal payment account status can be found in [reference needed]. Figure 10 The processing procedure of the first electronic device described in the text will not be repeated here.

[0188] It should be noted that the above Figures 11a to 11c This paper introduces several possible scenarios for the information verification process on a second electronic device. In actual implementation, other methods or entry points can also be used to guide users to verify information; this application does not limit the specific implementation method.

[0189] (vi) Red Envelope Management

[0190] For example, the first electronic device and the second electronic device can provide a red envelope management interface. Optionally, the red envelope management interface may include any one or a combination of a red envelope record interface, a red envelope to be received interface, a red envelope to be sent interface, a red envelope sent interface, a red envelope received interface, and a red envelope receiving details interface.

[0191] For example, Figure 12a This is a schematic diagram of a red envelope management interface provided in an embodiment of this application. Figure 12a Interface 1200A shows a schematic diagram of the Huawei Pay interface, which may include a control 1201 for the red envelope function. Control 1201 can be used to view various possible red envelope management interfaces, such as interfaces 1200B, 1200C, and 1200D, which represent three different red envelope management interfaces. Interface 1200B shows the details of receiving a red envelope. Interface 1200C shows the red envelope record interface, which may include records of expired red envelopes, red envelopes to be received, and red envelopes to be sent. Interface 1200D shows the red envelope record interface, which may include all red envelope records to be received.

[0192] For example, Figure 12b This is another schematic diagram of a red envelope management interface provided in an embodiment of this application. Figure 5aThe interface 500A shown may include a control 1202 for viewing pending red envelopes. In interface 500A, the electronic device may display interface 1200C or interface 1200D, or other red envelope management interfaces, in response to a click operation on control 1202.

[0193] It should be noted that this application does not limit the specific form of the red envelope management interface, which can be customized as needed.

[0194] based on Figures 4 to 12b The following describes the interface display effect and the implementation process of the red envelope sending and receiving method provided in this application, to illustrate how the method provided in this application can achieve the aforementioned results. Figures 4 to 12b The interface effects shown enhance the fun and playability of sending and receiving electronic red envelopes between users.

[0195] To facilitate distinction, the terminology that may be used in the following embodiments will be explained first:

[0196] (1) The user identification (UID) on the first electronic device is used to indicate the user who sent the red envelope. Therefore, it can also be understood as the UID of the user who sent the red envelope, such as the UID of user A. For example, the UID on the first electronic device can be the Huawei account logged in on the first electronic device. For example, the server can query and verify the real-name information of the user who sent the red envelope based on the UID of the first electronic device.

[0197] (2) Device information of the first electronic device, used to indicate the electronic device used by the user sending the red envelope. Device information may include, but is not limited to: device model, device name, device identifier, network information, location information, etc. Device identifier may include, but is not limited to: universally unique identifier (UUID), international mobile equipment identity (IMEI) serial number (SN), electronic serial number (ESN), mobile equipment identity (MEI), etc. Network information may include, for example, cellular network, wireless network, etc.

[0198] For example, the server can make risk control decisions based on the device information of the first electronic device to ensure payment security. For instance, the server can use the device information of both the first and second electronic devices to perform location detection. When the first and second electronic devices use a tap-to-send method to send and receive red envelopes, they should be in close proximity. If they are not in close proximity, an anomaly can be identified to ensure payment security.

[0199] (3) The UID on the second electronic device is used to indicate the user who received the red envelope, and can therefore be understood as the UID of the user who received the red envelope, such as the UID of user B. For example, the UID on the second electronic device can be the Huawei account logged in on the second electronic device. For example, the server can query and verify the real-name information of the user who received the red envelope based on the UID of the second electronic device.

[0200] (4) Device information of the second electronic device, used to indicate the electronic device used by the user receiving the red envelope. Similar to the device information of the first electronic device, the device information of the second electronic device can be used by the server for risk control decisions.

[0201] (5) Red Packet Identification (ID): This is used to associate red packet configuration information, red packet details information, red packet record information, and other red packet-related information. For example, the server can store red packet-related information and interact with the first or second electronic device through the red packet ID, thereby facilitating the server to determine which red packet needs to be invoked or managed based on the red packet ID.

[0202] For example, Figure 13 This is a flowchart illustrating a method for sending and receiving red envelopes, provided in an embodiment of this application. The process can be implemented using a first electronic device, a second electronic device, and a server. The process may include the following steps:

[0203] Step 1301: The first electronic device detects the trigger event for sending a red envelope.

[0204] For example, the first electronic device can be Figure 4 The trigger entry shown in interfaces 400A, 400B, or 400C detects the trigger event for sending a red envelope. For details on the implementation process, please refer to [link / reference needed]. Figure 4 As shown.

[0205] like Figure 2 As shown, the first electronic device can use the payment kit capability to prepare for sending red envelopes, such as generating and configuring them.

[0206] Step 1302: In response to the trigger event for sending a red envelope, the first electronic device queries the server for basic red envelope configuration information. Correspondingly, the server receives the request from the first electronic device to query the basic red envelope configuration information.

[0207] The basic configuration information for red envelopes may include, but is not limited to: red envelope type, red envelope cover data, maximum red envelope amount data, maximum number of red envelopes data, and greeting template data.

[0208] For example, the server can be a cloud server or a server cluster; this embodiment of the application will be described using the server as an example.

[0209] Step 1303: The server returns the basic configuration information for the red envelope to the first electronic device. Correspondingly, the first electronic device receives the basic configuration information for the red envelope sent by the server.

[0210] For example, in response to a query request from the first electronic device, the server can obtain, but is not limited to, basic configuration information of the red envelope, such as the red envelope type, red envelope cover data, red envelope amount limit data, red envelope quantity limit data, and blessing template data.

[0211] Step 1304: The first electronic device displays the red envelope configuration interface.

[0212] For example, the red envelope configuration interface is as follows: Figure 4 The interface shown in 400D is shown in the image.

[0213] Step 1305: First electronic device acquires configuration.

[0214] For example, such as Figure 5a As shown in interface 500A, the configuration operation can include the following operations: select the red envelope type in the first configuration area 501, fill in the red envelope amount, number of sub-red envelopes and blessing message in the second configuration area 502, and select the red envelope cover in the third configuration area 503, etc.

[0215] Step 1306: In response to the configuration operation, the first electronic device sends red packet configuration data to the server. Correspondingly, the server receives the red packet configuration data sent by the first electronic device.

[0216] The configuration data for the red envelope includes, but is not limited to: the UID on the first electronic device, the red envelope amount, the red envelope type, the red envelope cover, the number of sub-red envelopes, and the greeting message. The UID on the first electronic device can be understood as the UID of the user sending the red envelope, such as user A's UID. Optionally, the server can query the real-name information of the user sending the red envelope using the UID on the first electronic device. If the real-name information of the user sending the red envelope is not found, the server can instruct the first electronic device to guide the user to upload identification information. Alternatively, the UID on the first electronic device can also be the user's real-name information.

[0217] In one possible scenario, a Huawei account is logged in on the first electronic device, so the Huawei account can be used as the UID on the first electronic device.

[0218] In another possible scenario, before sending the red envelope configuration data, the first electronic device detects that a user account, such as a Huawei account, has not been activated. In this case, the user can be guided to activate a user account in order to obtain the UID on the first electronic device. The specific implementation method is not limited.

[0219] In some possible implementations, the red envelope configuration data may also include first device information of the first electronic device. This first device information can be used for risk control decisions regarding red envelopes, thereby ensuring the security of user payments. The device information of the first electronic device in the red envelope configuration data can be understood as the device information of the first electronic device at the time the red envelope is created.

[0220] Step 1307: The server stores the red packet configuration data and generates the first red packet sending data.

[0221] The data sent in the first red packet may include, but is not limited to: red packet ID, prepay transaction session identifier (prepayID), and signature (sign). For example, the red packet ID can be used by the server to query stored red packet configuration data, facilitating the management of this data; the prepayID and signature can be used by the first electronic device to execute the payment processing procedure, the specific implementation of which is described below. Figure 14 As shown, details will not be elaborated here. For example, the server can associate the red packet ID with the UID of the user who sent the red packet, so that the server can manage the red packet record information.

[0222] In addition, the server verifies the greeting message. For example, if the greeting message does not comply with content risk control rules, the user can be prompted to modify it.

[0223] Step 1308: The server returns the first red packet sending data to the first electronic device. Correspondingly, the first electronic device receives the first red packet sending data sent by the server.

[0224] It is understood that through steps 1301 to 1308 above, the first electronic device can complete the configuration process of the red envelope and generate a red envelope to be sent. Optionally, the red envelope to be sent can be a single red envelope. Alternatively, the red envelope to be sent can also include multiple sub-red envelopes.

[0225] Step 1309: The first electronic device detects that the payment has been completed and displays the red envelope sending interface.

[0226] For example, the red envelope sending interface can be as follows: Figure 5a As shown in interface 500B1, it can also be as follows Figure 5c The interface shown in 500B2 is shown in the image.

[0227] Step 1310: During the process of displaying the red envelope sending interface, the first electronic device detects a touch with the second electronic device.

[0228] For example, the first electronic device and the second electronic device can touch each other by touching the top or the back. This application does not limit the specific operation method of touching.

[0229] In some possible implementations, in response to a tap with a second electronic device, the first electronic device can send its current device information to the server. Correspondingly, the server can store the device information of the first electronic device and set a cache duration based on the validity period of the red packet, such as 24 hours. Furthermore, the server can return a first device token to the first electronic device, which is used by the server to retrieve the device information of the first electronic device. It is understood that the device information of the first electronic device may change as the first electronic device moves or undergoes other changes. The device information of the first electronic device sent in this step can be understood as the device information of the first electronic device at the time the red packet is actually sent. For example, the server can make risk control decisions for the first electronic device based on the device information of the first electronic device at the time the red packet is created and the device information of the first electronic device at the time the red packet is actually sent.

[0230] Step 1311: The first electronic device generates the second red packet sending data.

[0231] The second red packet sending data may include, but is not limited to: red packet ID, first device token, red packet cover data, greeting message, deeplink, etc. The deeplink is used by the second electronic device to jump to the red packet receiving interface from any displayed interface, based on the red packet function provided by the target application or component. For example, the deeplink includes red packet functionality to initiate payment kit capabilities; for example, the link path could be: payment / redpacket. Optionally, the second electronic device can directly display the red packet receiving interface based on the link path indicated by the deeplink and the red packet cover data, greeting message, etc., included in the second red packet sending data. Alternatively, the red packet cover data and greeting message can also be encapsulated in the deeplink, so that the second electronic device can directly display the red packet receiving interface based on the link path indicated by the deeplink.

[0232] For example, such as Figure 5a As shown in interface 500D, the second electronic device can respond to a tap and directly display the red envelope receiving interface. This improves the convenience of sending and receiving red envelopes, reduces manual operation, and lowers operational complexity. Step 1312: The first electronic device sends the second red envelope sending data to the second electronic device. Correspondingly, the second electronic device receives the second red envelope sending data sent by the first electronic device.

[0233] For example, the first electronic device sends a second red packet to the second electronic device via the ShareKit capability. Correspondingly, the second electronic device can receive the second red packet from the first electronic device via the ShareKit capability.

[0234] Step 1313: The second electronic device sends red packet reception data to the server. Correspondingly, the server receives the red packet reception data sent by the second electronic device.

[0235] The data received in the red envelope transaction may include: the UID on the second electronic device and the red envelope ID. The UID on the second electronic device can be understood as the UID of the user receiving the red envelope, such as user B's UID. Optionally, the server can query the real-name information of the user receiving the red envelope using the UID on the second electronic device. If the real-name information is not found, the server can instruct the second electronic device to guide the user to upload identification information. Alternatively, the UID on the second electronic device can also be the user's real-name information.

[0236] In one possible scenario, a Huawei account is logged into the second electronic device, so the UID on the second electronic device can be obtained based on the Huawei account.

[0237] In another possible scenario, if the second electronic device detects that a user account such as a Huawei account has not been activated before sending the second red envelope data, it can guide the user to activate a user account in order to obtain the UID on the second electronic device. The specific implementation method is not limited.

[0238] In some possible implementations, the data received in the red envelope may also include device information of the second electronic device. This device information is used by the server to make risk control decisions, thereby ensuring the security of user payments. For example, the server can make risk control decisions based on the device information of the first and second electronic devices at the time the red envelope is actually sent. For instance, if the first and second electronic devices are far apart when sending and receiving red envelopes using a tap-to-pay method, it can be determined that there is a risk in the red envelope sending and receiving process, thus ensuring the security of user payments.

[0239] Step 1314: The server allocates the red envelope amount to the second electronic device.

[0240] For example, the server can obtain red packet configuration data based on the red packet ID, determine information such as red packet type, red packet amount, and number of sub-red packets based on the red packet configuration data, and then determine the red packet amount allocated to the second electronic device. For instance, when the red packet type is a "lucky red packet," the number of red packets can be determined to be 1, and the red packet amount allocated to the second electronic device is equal to the red packet configuration amount. As another example, when the red packet type is a "lucky draw red packet," the amount of the sub-red packets allocated to the second electronic device can be determined based on the red packet configuration amount and the number of sub-red packets.

[0241] For example, the server can associate the red packet ID with the UID of the red packet recipient, as well as the allocated red packet amount corresponding to the UID of the red packet recipient, so that the server can manage the red packet record information. It can be understood that the server updates the red packet receipt details information based on the red packet amount allocated to the second electronic device.

[0242] Step 1315: The server returns the red envelope receipt details to the second electronic device. Correspondingly, the second electronic device receives the red envelope receipt details sent by the server.

[0243] Optionally, the red packet receiving details may only include information about the red packet amount allocated by the server to the second electronic device. Alternatively, the red packet receiving details may also include all receiving details of the red packet corresponding to the red packet ID, such as information about the red packet amounts of other sub-red packets.

[0244] Step 1316: The second electronic device displays the red envelope receiving details interface based on the red envelope details information.

[0245] For example, the red envelope receiving interface is as follows: Figure 5b The interface shown in 500E is shown in the image.

[0246] It should be noted that when the first electronic device detects that the red envelope has not been completely sent, it can continue to send the remaining sub-red envelopes to other second electronic devices through steps 1310 to 1316 above. (See also...) Figure 5c As shown. It should be noted that other second electronic devices receiving red envelopes from the first electronic device can refer to the process described above, and will not be repeated here. In addition, in this embodiment of the application, it is not limited to other second electronic devices receiving red envelopes from the first electronic device by tapping; they can also receive red envelopes via QR codes. For example, the first electronic device displays a QR code associated with the red envelope, and the second electronic device receives the red envelope by scanning the QR code displayed on the first electronic device; or, they can receive red envelopes via password.

[0247] pass Figure 13 The illustrated process shows that after the first electronic device is configured to send a red envelope, it can send the red envelope to the second electronic device via a short-range wireless communication technology, such as a tap-to-send, based on the displayed red envelope sending interface. This allows the second electronic device to directly activate the target service's red envelope function and display the red envelope receiving interface. This method improves the convenience of sending and receiving red envelopes between electronic devices, enabling instant one-tap sending and reducing user operations. Furthermore, this method does not require the electronic devices to be contacts within the address book, reducing the operational complexity of red envelope sending and receiving scenarios and making it easier for two users to send and receive red envelopes. In addition, this method enhances the application scenarios and fun of using the red envelope function.

[0248] based on Figure 13 In step 1308, the first electronic device obtains the first red packet sending data, and the first electronic device can perform the red packet payment processing. For example, Figure 14 This is another flowchart illustrating a method for sending and receiving red envelopes provided in an embodiment of this application. This process can be used to implement the payment processing of red envelopes by a first electronic device. The process may include the following steps:

[0249] Step 1401: The first electronic device requests to activate the cash register based on the prepayment transaction session identifier and signature.

[0250] Step 1402: The first electronic device detects that it is a "tap to red envelope" scenario and requests pre-payment from the server. Correspondingly, the server receives the pre-payment request from the first electronic device.

[0251] Prepayment can be used to obtain payment methods, such as bank card payment or account balance payment.

[0252] Step 1403: The server returns the payment method to the first electronic device. Correspondingly, the first electronic device receives the payment method returned by the server.

[0253] Step 1404: The first electronic device displays the red envelope cashier according to the payment method.

[0254] For example, when the payment method returned by the server includes bank card payment and account balance payment, the red packet cashier may include one or more linked bank cards and account balances.

[0255] Step 1405: The first electronic device requests payment from the server; or, it binds a card and makes a payment. Correspondingly, the server receives the payment request or the card binding and payment request from the first electronic device.

[0256] For example, if the first electronic device detects the payment method selected by the user, it can request payment from the server according to the selected payment method.

[0257] In another example, if the first electronic device detects that the user has selected to add a bank card, it can request the server to bind the new bank card and make payments using the new bank card. For example, the first electronic device can... Figure 9 The interface shown shows how to add a bank card.

[0258] It is understandable that after receiving a payment request or a card-binding and payment request from the first electronic device, the server can make a risk control decision. For example, it can make a risk control decision based on the device information and the type of red envelope (digital cash gift) to ensure the user's payment security. Then, based on the risk control decision, the server returns the risk control result to the first electronic device. This risk control result can include: facial verification, verification code verification, fingerprint verification, or transaction failure, for example, through methods such as... Figure 10 The interface shown performs facial recognition verification. It's understandable that if the risk control decision indicates a successful transaction, a risk control result doesn't need to be returned.

[0259] Step 1406: The first electronic device queries the server for the red envelope payment result. Correspondingly, the server receives the red envelope payment result query request from the first electronic device.

[0260] Step 1407: The server returns the red envelope payment result to the first electronic device. Correspondingly, the first electronic device receives the red envelope payment result from the server.

[0261] Step 1408: The first electronic device displays the red envelope payment completion interface based on the red envelope payment result.

[0262] In one optional implementation, the first electronic device can set a display duration threshold for the red envelope payment completion interface, such as 1 second or 3 seconds. Then, after the first electronic device detects that the display duration threshold has been reached, it can redirect to... Figure 13 The red envelope sending interface is described in step 1309.

[0263] Step 1409: The server records the red envelope records for the "tap to red envelope" scenario.

[0264] For example, the server can store red envelope record data for users who sent the red envelopes, such as red envelope record data for user A.

[0265] pass Figure 14 The process shown can realize the payment processing when the first electronic device sends a red envelope, thereby ensuring the successful sending of the red envelope.

[0266] Based on the above text Figures 8 to 10 The introduction states that when an electronic device sends a red envelope, it needs to undergo an information verification process to support the above. Figure 13 and Figure 14 The implementation process of the first electronic device in the illustrated flow. For example, Figure 15 This is another schematic diagram illustrating the process of sending and receiving red envelopes, provided as an embodiment of this application. This process can be used to implement an information verification process for a first electronic device. This process can be applied to a first electronic device and may include the following steps:

[0267] Step 1501: The first electronic device checks whether a user account is activated. If yes, proceed to step 1502B; otherwise, proceed to step 1502A.

[0268] Step 1502A: Activate a user account. For example, the process of activating a user account can be found in [link to documentation]. Figure 8 As shown. The user account is, for example, a Huawei account.

[0269] It should be noted that, from Figure 8 As can be seen, after completing step 1502A, the red envelope configuration process can continue. Figure 15 The process shown can be compared with Figure 13 The introduced processes are integrated, for example, step 1302 is executed.

[0270] After completing step 1502A, proceed to step 1502B.

[0271] Step 1502B: The first electronic device checks whether a payment account is activated. If yes, proceed to step 1503B; otherwise, proceed to step 1503A.

[0272] Step 1503A: Activate a payment account. For example, the process of activating a payment account can be found in [link to documentation]. Figure 9 As shown.

[0273] After completing step 1503A, proceed to step 1503B.

[0274] Step 1503B: The first electronic device checks whether the payment account status is normal. If yes, proceed to step 1504B; otherwise, proceed to step 1504A.

[0275] Step 1504A: Unfreezing the payment account. For an example, the process of unfreezing a payment account can be found in [link to documentation]. Figure 10 As shown.

[0276] After completing step 1504A, proceed to step 1504B.

[0277] Step 1504B: The first electronic device checks whether the payment is made using the account balance. If yes, proceed to step 1505B; otherwise, proceed to step 1505A.

[0278] For example, the first electronic device can be via such Figure 14 The red envelope cashier shown in step 1404 detects the payment method selected by the user.

[0279] Step 1505A: The first electronic device checks whether a bank card has been added. If yes, proceed to step 1507; otherwise, proceed to step 1506.

[0280] Step 1505B: The first electronic device checks whether the account balance is sufficient. If yes, proceed to step 1507; otherwise, proceed to step 1505A.

[0281] It is understandable that when the first electronic device detects insufficient account balance, it can guide the user to switch to bank card payment; or, it can guide the user to recharge the account balance.

[0282] Step 1506: Add a bank card. For an example, the process of adding a bank card can be found in [link to documentation]. Figure 9 As shown.

[0283] Step 1507: Send a red envelope.

[0284] It should be noted that, from Figure 8 and Figure 9 As can be seen, steps 1502B to 1507 can be triggered after the red envelope configuration. Figure 15 The process shown can be compared with Figure 13 The introduced processes can be integrated, and can Figure 13It can be executed at any time after step 1304 and before step 1309.

[0285] It should be noted that, Figure 15 This application provides an example of information verification for the first electronic device described herein. The application does not limit the specific verification process and may be adjusted as needed.

[0286] pass Figure 15 As shown in the process, the first electronic device can ensure the security of user payments through the information verification process.

[0287] Based on the above text Figures 11a to 11c According to the introduction, the second electronic device also needs to undergo an information verification process when receiving red envelopes in order to support the above. Figure 13 The implementation process of the second electronic device in the illustrated flow. For example, Figure 16 This is another schematic diagram illustrating the process of sending and receiving red envelopes, provided as an embodiment of this application. This process can be used to implement information verification by a second electronic device. This process can be applied to a second electronic device and may include the following steps:

[0288] Step 1601: The second electronic device checks whether a user account is activated. If yes, proceed to step 1602B; otherwise, proceed to step 1602A.

[0289] Step 1602A: Activate a user account. For example, the process of activating a user account can be found in [link to documentation]. Figure 11a As shown. The user account is, for example, a Huawei account.

[0290] After completing step 1602A, proceed to step 1602B.

[0291] Step 1602B: The second electronic device checks whether a payment account is activated. If yes, proceed to step 1603; otherwise, proceed to step 1607.

[0292] Step 1603: Display the first red envelope receiving details interface. For example, the first red envelope receiving details interface looks like this: Figure 5b As shown in interface 500E, the red envelope has been deposited into the balance.

[0293] Step 1604: The second electronic device checks whether the payment account status is normal. If yes, proceed to step 1606; otherwise, proceed to step 1605.

[0294] Step 1605: Unfreeze the payment account. For an example, the process of unfreezing a payment account can be found in [link to documentation]. Figure 10 As shown.

[0295] After completing step 1605, proceed to step 1606.

[0296] Step 1606: The red envelope has been received.

[0297] Step 1607: The second electronic device displays the second red envelope receiving details interface. For example, the second red envelope receiving details interface is as follows: Figure 11b As shown in interface 1100B, the red envelope has not been deposited into the balance.

[0298] Step 1608: The second electronic device guides the opening of the payment account.

[0299] Step 1609: The second electronic device checks whether the document has been uploaded within the preset time period. If yes, proceed to step 1606; otherwise, proceed to step 1610. Figure 11b As shown, the preset duration can be, for example, 14 days.

[0300] Step 1610: The red envelope is returned to the original account. For example, the red envelope will be returned to user A's account.

[0301] It should be noted that, Figure 16 This application provides an example of information verification for the second electronic device described herein. The application does not limit the specific verification process and may be adjusted as needed.

[0302] pass Figure 16 As shown in the process, the second electronic device can ensure the security of user payments through the information verification process.

[0303] Based on the server's recording and management of red envelope records in the "tap-to-win" scenario, the first electronic device and / or the second electronic device can query the server for red envelope details. For example, Figure 17 This is a flowchart illustrating a method for sending and receiving red envelopes provided in an embodiment of this application. This process can be used to implement server maintenance of red envelope records for a "tap-to-receive" scenario. The process may include the following steps:

[0304] Step 1701: The server updates the red packet record associated with the first user identifier based on the red packet reception information. The first user identifier is the UID of the user who sent the red packet, such as the UID of user A.

[0305] It's understandable that the server maintains records of red envelopes so that users who sent or received red envelopes can easily query them.

[0306] Optionally, in step 1702, the first electronic device queries the details of the red envelope through the red envelope identifier.

[0307] Step 1703: The server returns the details of the red envelope to the first electronic device.

[0308] Alternatively, in step 1704, the second electronic device queries the details of the red envelope through the red envelope identifier.

[0309] Step 1705: The server returns the details of the red envelope to the second electronic device.

[0310] It should be noted that the timing of the first electronic device and the second electronic device querying the server is not limited in the embodiments of this application. For example, the query can be performed in response to user operation or periodically.

[0311] It should be noted that the first electronic device mentioned above can be used not only as a red envelope sending device but also as a red envelope receiving device. The processing flow of the first electronic device when it is used as a red envelope receiving device can be referred to the processing flow of the second electronic device mentioned above, and will not be repeated here.

[0312] pass Figure 17 The method shown involves the server maintaining red envelope records, which facilitates the querying of red envelope details by the first electronic device and / or the second electronic device, ensuring the timely updating of red envelope details.

[0313] Based on the same concept, this application also provides a method for sending and receiving red envelopes, which can be executed by a first electronic device. Figure 18 A flowchart of a method for sending and receiving red envelopes provided in this application embodiment is shown below. Figure 18 The method includes the following steps:

[0314] Step 1801: The first electronic device displays a first interface, which includes first guidance information and a red envelope symbol card. The first guidance information is used to instruct the second electronic device to send the first red envelope corresponding to the red envelope symbol card using a first method. The first method is implemented based on short-range wireless communication technology.

[0315] For example, the first interface is as follows Figure 5a In interface 500B1, the first guidance information is shown in the first prompt area 505, and the red envelope illustration card is shown in the second prompt area 5061. It can be understood that the red envelope illustration card in the first interface can be one or multiple cards. The first method can be, for example, a tap-to-win method.

[0316] Step 1802: In response to a first event that satisfies the triggering condition of the first method, the first electronic device sends a first red packet to the second electronic device. Accordingly, the second electronic device detects the first event.

[0317] For example, the first electronic device sending a first red packet to the second electronic device can be found in [reference needed]. Figure 13 Step 1312 is shown in the diagram.

[0318] Step 1803: The second electronic device responds to the first event and displays a second interface, which includes a first red envelope indication card, which is used to indicate the first red envelope sent by the first electronic device.

[0319] For example, the second interface is as follows Figure 5a As shown in interface 500D in b, the first red envelope illustration card is, for example, the red envelope illustration card 510 shown in interface 500D.

[0320] It should be noted that this application Figure 18 The methods for sending and receiving red envelopes shown can be referred to in the above embodiments of this application for specific implementation, and repeated details will not be repeated.

[0321] Based on the above embodiments, this application also provides an electronic device, which includes multiple functional modules; the multiple functional modules interact to realize the functions performed by the first electronic device or the second electronic device in the methods described in the embodiments of this application. For example, ... Figure 13 The steps performed by the first electronic device or the second electronic device in the illustrated embodiment, or the execution of... Figure 14 The steps performed by the first electronic device in the illustrated embodiment, or the execution of... Figure 15 The steps performed by the first electronic device in the illustrated embodiment, or the execution of... Figure 16 The steps performed by the first electronic device in the illustrated embodiment, or the steps performed by... Figure 17 The steps performed by the first or second electronic device in the illustrated embodiment, or the steps performed by... Figure 18 The steps performed by the first or second electronic device in the illustrated embodiment. The plurality of functional modules can be implemented based on software, hardware, or a combination of software and hardware, and the plurality of functional modules can be arbitrarily combined or divided based on specific implementation.

[0322] Based on the above embodiments, this application also provides an electronic device, which includes at least one processor and at least one memory, wherein the at least one memory stores computer program instructions. When the electronic device is running, the at least one processor performs the functions performed by the first or second electronic device in the methods described in the embodiments of this application. For example, when executing... Figure 13 The steps performed by the first electronic device or the second electronic device in the illustrated embodiment, or the execution of... Figure 14 The steps performed by the first electronic device in the illustrated embodiment, or the execution of... Figure 15 The steps performed by the first electronic device in the illustrated embodiment, or the execution of... Figure 16 The steps performed by the first electronic device in the illustrated embodiment, or the steps performed by... Figure 17 The steps performed by the first or second electronic device in the illustrated embodiment, or the steps performed by... Figure 18The steps performed by the first electronic device or the second electronic device in the illustrated embodiment

[0323] Based on the above embodiments, this application also provides a red envelope sending and receiving system, the system including a first electronic device, M second electronic devices, and a server. M can be determined according to the number of red envelopes configured on the first electronic device, and M can be less than or equal to the configured number of red envelopes. For example, if all sub-red envelopes of a red envelope sent by the first electronic device have been sent, then M can be equal to the number of red envelopes; otherwise, M can be less than the number of red envelopes.

[0324] Based on the above embodiments, this application also provides a computer program product containing instructions, which, when run on a computer, causes the computer to execute the methods described in the embodiments of this application.

[0325] Based on the above embodiments, this application also provides a computer-readable storage medium storing a computer program, which, when executed by a computer, causes the computer to perform the methods described in the embodiments of this application.

[0326] Based on the above embodiments, this application also provides a chip for reading computer programs stored in a memory to implement the methods described in the embodiments of this application.

[0327] Based on the above embodiments, this application provides a chip system including a processor for supporting a computer device in implementing the methods described in the embodiments of this application. In one possible design, the chip system further includes a memory for storing necessary programs and data of the computer device. This chip system may be composed of chips or may include chips and other discrete devices.

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

[0329] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. 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.

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

[0331] 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 the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0332] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the scope of protection of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.

Claims

1. A method for sending and receiving red envelopes, applied to a first electronic device, characterized in that, The method includes: The first interface displays a first guidance information and a red envelope icon card. The first guidance information is used to instruct the second electronic device to send a first red envelope corresponding to the red envelope icon card using a first method, which is implemented based on short-range wireless communication technology. The red envelope icon card corresponds to multiple sub-red envelopes. The number of red envelope icon cards included in the first interface corresponds one-to-one with the number of remaining sub-red envelopes. Alternatively, when the number of remaining sub-red envelopes is greater than a number threshold, the number of red envelope icon cards is the number threshold. When the number of remaining sub-red envelopes is less than or equal to the number threshold, the number of red envelope icon cards corresponds one-to-one with the number of remaining sub-red envelopes. In the first interface, in response to a first event that satisfies the triggering condition of the first method, the first red envelope is sent to the second electronic device; the first method is the method of the first electronic device and the second electronic device touching each other, the first event is the first electronic device touching the second electronic device, or the first method is a preset air gesture method, the first event is the first electronic device detecting a first air gesture, the first electronic device detecting the second electronic device detecting a second air gesture, the first air gesture being used to indicate sending the first red envelope, and the second air gesture being used to indicate receiving the first red envelope.

2. The method according to claim 1, characterized in that, Sending the first red packet to the second electronic device includes: Send first data to the second electronic device. The first data includes: a red envelope identifier and first information. The first information is used by the second electronic device to jump to an interface for receiving the first red envelope.

3. The method according to claim 2, characterized in that, The first information is a deep link, which is used by the second electronic device to display an interface for receiving the first red envelope based on the link path. The link path is used to activate the red envelope function of the payment service capability.

4. The method according to any one of claims 1 to 3, characterized in that, Before displaying the first interface, the method further includes: Send second data to the server, the second data including: the user identifier (UID) of the first electronic device and second information, the second information being used to indicate the configuration of the red packet; Receive third data sent by the server, the third data including: red envelope identifier.

5. The method according to claim 4, characterized in that, The UID of the first electronic device is determined based on the user account logged in on the first electronic device.

6. The method according to any one of claims 1 to 3, characterized in that, The step of sending the first red packet to the second electronic device in response to a first event that satisfies the triggering condition of the first method includes: In response to the first event, a second interface is displayed, the second interface including a first red envelope icon card, the first red envelope icon card being used to indicate the first red envelope; In the second interface, in response to a swipe operation on the first red envelope icon card, the first red envelope is sent to the second electronic device.

7. The method according to any one of claims 1 to 3, characterized in that, The first interface also includes second guidance information, which is used to instruct the second electronic device to send the first red packet corresponding to the red packet illustration card using a second method; The second method includes: QR code method or password red envelope method.

8. The method according to claim 7, characterized in that, The method further includes: In response to the first operation, a third interface is displayed, which is used to display the QR code or password-protected red envelope corresponding to the first red envelope; The first operation is a click operation on a first control, which is a control for flipping the red envelope illustration card, or a control for generating a QR code or password red envelope corresponding to the first red envelope.

9. The method according to any one of claims 1 to 3, characterized in that, The method further includes: When it is detected that there are still remaining sub-red envelopes, a fourth interface is displayed, which includes third guidance information and a second red envelope illustration card. The third guidance information is used to instruct the third electronic device to send the second red packet corresponding to the second red packet illustration card using the first method, and the second red packet is one of the remaining sub-red packets.

10. The method according to any one of claims 1 to 3, characterized in that, Before displaying the first interface, the method further includes: In response to a second event, a fifth interface is displayed; wherein the second event includes: triggering an operation on a second control in the negative one screen interface, or detecting a preset voice command, or triggering an operation on a third control in the first application, wherein the second control, the preset voice command, and the third control are used to indicate sending a red envelope; the fifth interface is used to configure the red envelope. A configuration operation was detected on the fifth interface.

11. The method according to claim 10, characterized in that, Before displaying the fifth interface, the method further includes: When an unactivated user account is detected, the sixth screen is displayed, which is used to guide the user to activate a user account.

12. The method according to claim 10, characterized in that, The fifth interface includes a fourth control, which is used to open a payment account.

13. The method according to claim 10, characterized in that, The fifth interface includes a fifth control, which is used to activate the cash register. The method further includes: When an abnormal payment account status is detected, a seventh interface is displayed. The seventh interface is used to guide the user to unfreeze the payment account using a preset verification method, which is obtained by the first electronic device from the server.

14. The method according to any one of claims 1 to 3, characterized in that, The method further includes: Send fourth data to the server, the fourth data including: red packet identifier, the fourth data being used to query red packet receipt details.

15. The method according to any one of claims 1 to 3, characterized in that, The method further includes: In response to the second operation, the eighth screen is displayed; The second operation is used to view the red envelope records, and the eighth interface includes at least one of the following: records of expired red envelopes, records of red envelopes to be received, records of red envelopes to be sent, records of red envelopes received, and records of red envelopes sent.

16. A method for sending and receiving red envelopes, applied to a second electronic device, characterized in that, The method includes: A first event is detected, which indicates that the second electronic device and the first electronic device meet the triggering conditions of a first method, the first method being implemented based on short-range wireless communication technology; wherein, in response to the first event, the first electronic device sends a first red envelope to the second electronic device in a first interface, the first interface including first guidance information and a first red envelope icon card, the first guidance information being used to indicate that the first red envelope corresponding to the first red envelope icon card is sent to the second electronic device using the first method; the first red envelope icon card corresponds to multiple sub-red envelopes; the number of the first red envelope icon cards included in the first interface corresponds one-to-one with the number of remaining sub-red envelopes; or, when the number of remaining sub-red envelopes is greater than a quantity threshold, the number of the first red envelope icon cards is the quantity threshold, and when the number of remaining sub-red envelopes is less than or equal to the quantity threshold, the number of the first red envelope icon cards corresponds one-to-one with the number of remaining red envelopes; In response to the first event, a second interface is displayed, the second interface including: a second red envelope indication card, the second red envelope indication card being used to indicate the first red envelope sent by the first electronic device; the first method being a touch between the first electronic device and the second electronic device, the first event being a touch between the first electronic device and the second electronic device; or, the first method being a preset air gesture method, the first event being the second electronic device detecting a second air gesture, the second air gesture being used to receive the first red envelope.

17. The method according to claim 16, characterized in that, Before displaying the second interface, the method further includes: The device receives first data sent by the first electronic device. The first data includes: a red envelope identifier and first information. The first information is used to display the second interface.

18. The method according to claim 17, characterized in that, The first information is a deep link, and the method further includes: The red envelope function of the payment service is activated based on the link path indicated by the deeplink.

19. The method according to any one of claims 16 to 18, characterized in that, The method further includes: Send second data to the server, the second data including: the user identifier (UID) of the second electronic device and the red packet identifier; The server sends third data, which includes the amount of the first red envelope.

20. The method according to claim 19, characterized in that, The UID of the second electronic device is determined based on the user account logged in on the second electronic device.

21. The method according to any one of claims 16 to 18, characterized in that, The method further includes: In response to the first operation, a third interface is displayed; the first operation is used to indicate receiving the first red envelope. Wherein, when the second electronic device detects that a payment account has been activated, the third interface is used to indicate the details of receiving the first red envelope; or, When the second electronic device detects that the payment account has not been activated, the third interface is used to indicate the receiving details of the first red envelope and the second guidance information, which is used to guide the user to activate the payment account.

22. The method according to claim 21, characterized in that, Before displaying the third interface, the method further includes: In response to the second event, when an unactivated user account is detected, a fourth interface is displayed, which is used to guide the user to activate a user account.

23. The method according to any one of claims 16 to 18, characterized in that, The method further includes: Send fourth data to the server, the fourth data including: red packet identifier, the fourth data being used to query red packet receipt details.

24. The method according to any one of claims 16 to 18, characterized in that, The method further includes: In response to the second action, the fifth interface is displayed; The second operation is used to view red envelope records, and the fifth interface includes at least one of the following: records of expired red envelopes, records of red envelopes to be received, records of red envelopes to be sent, records of red envelopes received, and records of red envelopes sent.

25. An electronic device, characterized in that, The method includes at least one processor coupled to at least one memory, the at least one processor being configured to read a computer program stored in the at least one memory to perform the method as described in any one of claims 1-15, or to perform the method as described in any one of claims 16-24.

26. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores instructions that, when executed on a computer, cause the computer to perform the method as described in any one of claims 1-15, or the method as described in any one of claims 16-24.

Images