Red envelope receiving and sending method and electronic equipment

Abstract

The invention provides a red envelope receiving and transmitting method and electronic equipment, which are used for providing a new red envelope receiving and transmitting mode and can improve the convenience of receiving and transmitting electronic red envelopes between users. In the method, when a first electronic device displays a red envelope sending interface, a user can be guided to send a red envelope to a second electronic device based on a short-distance wireless communication mode; and when it is detected that the first electronic equipment and the second electronic equipment meet the triggering condition of the preset mode, triggering to send the red envelope to the second electronic equipment. Correspondingly, when the second electronic device detects that the first electronic device meets the triggering condition of the preset mode, the red envelope receiving interface is directly displayed. Thus, the first electronic device and the second electronic device can conveniently transmit and receive the red envelope through the preset operation mode, and the operation complexity of red envelope transmitting and receiving is reduced.

Description

Technical Field

[0001] The present application relates to the technical field of electronic equipment, and in particular to a method for sending and receiving red envelopes and an electronic device. Background Art

[0002] With the continuous development and innovation of electronic devices, they can provide more and more functions in users' daily lives and work, giving users a better user experience. Red envelope function is one of the important functions that electronic devices can provide. It can facilitate communication and interaction between users and is widely used in various social software.

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

[0004] The present application provides a red envelope sending and receiving method and an electronic device, which are used to provide a new way of sending and receiving red envelopes, which can enhance the fun and playability of sending and receiving electronic red envelopes between users.

[0005] In a first aspect, the present application provides a method for sending and receiving red envelopes, which can be performed by a first electronic device. In this method, the first electronic device displays a first interface, the first interface including first guidance information and a red envelope schematic card, the first guidance information being used to instruct a first red envelope corresponding to the red envelope schematic card to be sent to a second electronic device in a first manner, the first manner being implemented based on short-range wireless communication technology; in the first interface, in response to a first event that meets a trigger condition of the first manner, the first red envelope is sent to the second electronic device.

[0006] In this method, the first electronic device, based on the displayed red envelope sending interface, sends the red envelope to the second electronic device through a method based on short-range wireless communication technology, thereby triggering the second electronic device to display the red envelope receiving interface. In this way, the method can improve the convenience of sending and receiving red envelopes between electronic devices, realize one-touch instant sending of red envelopes, and reduce user operations. In addition, the method does not need to limit the relationship between electronic devices to contact book friends, which can reduce the operational complexity of the red envelope sending and receiving scenario, and can more conveniently realize the sending and receiving of red envelopes between two users. In addition, the method can also improve the application scenarios and fun of users 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, first information, and the first information is used for the second electronic device to jump to the interface for receiving the first red envelope. Exemplarily, the first information is a deep link (deeplink), and the deeplink is used for the second electronic device to display an interface for receiving the first red envelope according to a link path, and the link path is used to pull up the red envelope function of the payment service capability. Optionally, the first data may also include: red envelope cover data, greetings, etc. Another option is that red envelope cover data, greetings and other information may also be carried in the deeplink.

[0008] In this implementation, by sending the first information from the first electronic device to the second electronic device, the second electronic device can quickly activate the red envelope function of the payment service capability and directly display the red envelope receiving interface. This can improve the convenience of sending and receiving red envelopes and reduce 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 indicating the configuration of a red envelope; and receiving third data from 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 red envelope configuration data to the server, the server can store the red envelope configuration information, thereby enabling the server to respond to the red envelope reception data of the second electronic device and allocate the red envelope to the second electronic device based on the red envelope configuration data. Furthermore, by generating a red envelope identifier, the server can facilitate the association and retrieval of various red envelope-related data, such as the red envelope configuration data, the data used for red envelope sending, and the red envelope reception data.

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

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

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

[0014] In this implementation, by associating the red envelope schematic card displayed in the red envelope sending interface with the number of remaining red envelopes, the number of remaining red envelopes can be more realistically reflected, thereby improving the experience and fun of sending and receiving red envelopes.

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

[0016] In this implementation, on the first electronic device, a sliding operation can be used to simulate the experience of sending red envelopes in real life, thereby enhancing the fun and experience of sending and receiving red envelopes.

[0017] In one possible implementation, the first manner is a manner in which the first electronic device and the second electronic device touch each other, and the first event is a manner in which the first electronic device and the second electronic device touch each other, for example, the top of the first electronic device and the top of the second electronic device touch each other, or the back of the first electronic device and the back of the second electronic device touch each other, etc. Alternatively, the first manner is a preset air gesture manner, and the first event is the first electronic device detecting a first air gesture, the first electronic device detecting that the second electronic device detects a second air gesture, the first air gesture is used to indicate sending the first red envelope, and the second air gesture is used to indicate receiving the first red envelope.

[0018] In this implementation, red envelopes can be conveniently sent and received between the first electronic device and the second electronic device by touching them together or by making air gestures, which can reduce user operations and improve the efficiency of sending and receiving red envelopes and the user experience.

[0019] In one possible implementation, the first interface further includes second guidance information, the second guidance information being used to instruct a second method to be used 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. Exemplarily, the method further includes: in response to the first operation, displaying a third interface, the third interface being used to display a QR code corresponding to the first red envelope, or a password 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] In this implementation, by providing a variety of red envelope sending and receiving methods, the needs of a variety of red envelope sending and receiving scenarios can also be met. For example, when the second electronic device supports short-range wireless communication methods such as touch and air gestures to receive red envelopes, the red envelopes can be conveniently received through these short-range wireless communication methods. When the second electronic device does not support short-range wireless communication methods to receive red envelopes, it can also successfully receive red envelopes through QR code methods or password red envelope methods. It can also be understood that when the red envelope sent by the first electronic device is a type that includes multiple sub-red envelopes, by providing a variety of red envelope sending and receiving methods, it is not restricted whether the second electronic device supports short-range wireless communication methods, which can facilitate users to choose a method to send and receive red envelopes, thereby improving the user's experience of the red envelope function.

[0021] In one possible implementation, the method further includes: when detecting that there are still remaining sub-red envelopes, displaying a fourth interface, the fourth interface including third guidance information and a red envelope schematic card; wherein the third guidance information is used to indicate the use of the first method to send a second red envelope corresponding to the red envelope schematic card to a third electronic device, the second red envelope being one of the remaining sub-red envelopes. The third electronic device is used to indicate an electronic device different from the second electronic device mentioned above, and can also be understood as another electronic device. The processing process between the first electronic device and the third electronic device can refer to the processing process 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 red envelope sending by continuing to display the red envelope sending interface, and conveniently enable the first electronic device to send red envelopes 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 instruction, or triggering an operation on a third control in the first application, the second control, the preset voice instruction, and the third control are used to instruct the sending of a red envelope; the fifth interface is used to configure red envelopes; and a configuration operation on the fifth interface is detected.

[0024] In this implementation, multiple trigger entries can be provided to enter the red envelope sending and receiving interface, thereby making it easier for users to use the red envelope function.

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

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

[0027] In a possible implementation, the fifth interface includes a fourth control, and the fourth control is used to open a payment account.

[0028] In this implementation, by guiding users to open payment accounts, the efficiency of users in using the red envelope function can be improved.

[0029] In one possible implementation, the fifth interface includes a fifth control, which is used to pull up the cash register. The method also includes: when an abnormal payment account status is detected, displaying a seventh interface, and the seventh interface is used to guide the user to use a preset verification method to unfreeze the payment account, and the preset verification method is obtained by the first electronic device from the server.

[0030] In this implementation, by guiding users to unfreeze their payment accounts, the efficiency of users in using the red envelope function can be improved.

[0031] In a possible implementation, the method further includes: sending fourth data to the server, the fourth data including: a red envelope identifier, and the fourth data is used to query red envelope reception details.

[0032] In this implementation, the red envelope record data can be maintained based on the server. Through the red envelope identifier, the detailed information related to the red envelope can be easily queried from the server, thereby facilitating a more real-time display of the red envelope management interface.

[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 received red envelopes, and records of sent red envelopes.

[0034] In this implementation, by providing various red envelope management interfaces, users can easily manage red envelopes and meet the needs of users in various management scenarios.

[0035] In a second aspect, the present application provides another method for sending and receiving red envelopes, which can be performed by a second electronic device. The method includes: detecting a first event, where the first event is used to indicate that the second electronic device and the first electronic device meet a triggering condition of a first method, where the first method is implemented based on short-range wireless communication technology; in response to the first event, displaying a first interface, where the first interface includes: a first red envelope indication card, where the first red envelope indication card is used to indicate a first red envelope sent by the first electronic device.

[0036] In this method, the second electronic device can directly display a red envelope receiving interface in response to the first red envelope sent by the first electronic device, enabling one-touch instant red envelope sending, which can reduce user operations. Furthermore, this method does not require the electronic devices to be friends in the address book, which can reduce the operational complexity of red envelope sending and receiving scenarios and make red envelope sending and receiving between two users more convenient. Furthermore, this method can also enhance the application scenarios and fun of users using the red envelope function.

[0037] In a 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, and the first information is used to display the first interface.

[0038] In a possible implementation, the first information is a deeplink, and the method further includes: launching a red envelope function of the payment service capability according to a link path indicated by the deeplink.

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

[0040] In a possible implementation, the UID of the second electronic device is determined based on a user account logged in to 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 is used to indicate receipt of the first red envelope; wherein, when the second electronic device detects that a payment account has been opened, the second interface is used to indicate the receipt details of the first red envelope; or, when the second electronic device detects that a payment account has not been opened, the second interface is used to indicate the receipt details of the first red envelope and first guidance information, and the first guidance information is used to guide the user to open a payment account.

[0042] In a possible implementation, before displaying the second interface, the method further includes: in response to a second event, when it is detected that the user account has not been activated, displaying a third interface, wherein the third interface is 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 that the first electronic device and the second electronic device touch each other; or, the first method is a preset air gesture method, and the first event is that the second electronic device detects a second air gesture, and the second air gesture is used to receive the first red envelope.

[0044] In a possible implementation, the method further includes: sending fourth data to the server, the fourth data including: a red envelope identifier, and the fourth data is used to query red envelope reception 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 received red envelopes, and records of sent red envelopes.

[0046] In a third aspect, the present 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, generates a red envelope to be sent and second data, the second data including a red envelope identifier for indicating the red envelope to be sent; sends the second data to the first electronic device; receives third data from a second electronic device, the third data including: the UID of the second electronic device and the red envelope identifier; queries the red envelope to be sent based on the red envelope identifier; generates and sends fourth data to the second electronic device, the fourth data including: the amount of the first red envelope allocated to the second electronic device.

[0047] In a fourth aspect, the present application provides an electronic device comprising multiple functional modules; the multiple functional modules interact with each other to implement the method performed by the first electronic device in the first aspect and its respective embodiments, or to implement the method performed by the second electronic device in the second aspect and its respective embodiments. The multiple functional modules may be implemented based on software, hardware, or a combination of software and hardware, and the multiple functional modules may be arbitrarily combined or divided based on the specific implementation.

[0048] In a fifth aspect, the present application provides an electronic device comprising 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 above-mentioned first aspect and its various embodiments, or executes the method executed by the second electronic device in the above-mentioned second aspect and its various embodiments.

[0049] In a sixth aspect, the present application provides a server comprising multiple functional modules; the multiple functional modules interact with each other to implement the method performed by the server in the third aspect and its respective 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 the specific implementation.

[0050] In the seventh aspect, the present application provides a server comprising at least one processor and at least one memory, wherein the at least one memory stores computer program instructions. When the server is running, the at least one processor executes the method executed by the server in the above-mentioned third aspect and its various embodiments.

[0051] In an eighth aspect, the present 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 may refer to the method executed by the first electronic device in the above-mentioned first aspect and its various embodiments, the execution of the second electronic device may refer to the method executed by the second electronic device in the above-mentioned second aspect and its various embodiments, and the execution of the server may refer to the method executed by the server in the above-mentioned third aspect and its various embodiments. M may be determined based on the red envelope data configured by the first electronic device, and M may be less than or equal to the number of configured 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] In the ninth aspect, the present application also provides a computer program product comprising instructions, which, when run on a computer, enables the computer to execute the method executed by the first electronic device in the above-mentioned first aspect and its various embodiments, or to execute the method executed by the second electronic device in the above-mentioned second aspect and its various embodiments.

[0053] In the tenth aspect, the present application also provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a computer, the computer executes the method executed by the first electronic device in the above-mentioned first aspect and its various embodiments, or executes the method executed by the second electronic device in the above-mentioned second aspect and its various embodiments.

[0054] In the eleventh aspect, the present application also provides a chip, which is used to read the computer program stored in the memory, execute the method executed by the first electronic device in the above-mentioned first aspect and its various embodiments, or execute the method executed by the second electronic device in the above-mentioned second aspect and its various embodiments.

[0055] In a twelfth aspect, the present application further provides a chip system, which includes a processor for supporting a computer device to implement the method executed by the first electronic device in the above-mentioned first aspect and its various embodiments, or to implement the method executed by the second electronic device in the above-mentioned second aspect and its various embodiments. In one possible design, the chip system also includes a memory, which is used to store the necessary programs and data for the computer device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0056] Among them, 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. BRIEF DESCRIPTION OF THE DRAWINGS

[0057] Figure 1 A schematic structural diagram of an electronic device 100 provided in an embodiment of the present application;

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

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

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

[0061] Figure 5a This is one of the interface diagrams of the red envelope sending and receiving method provided in an embodiment of the present application;

[0062] Figure 5b This is the second interface diagram of the red envelope sending and receiving method provided in the embodiment of the present application;

[0063] Figure 5c This is the third interface diagram of the red envelope sending and receiving method provided in the embodiment of the present application;

[0064] Figure 6 This is the fourth interface diagram of the red envelope sending and receiving method provided in the embodiment of the present application;

[0065] Figure 7 A schematic diagram of a red envelope cover selection scenario provided in an embodiment of the present application;

[0066] Figure 8 This is one of the schematic diagrams of a guide interface for opening a Huawei account provided in an embodiment of the present application;

[0067] Figure 9 This is a second schematic diagram of a guide interface for opening a payment account provided in an embodiment of the present application;

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

[0069] Figure 11a This is a second schematic diagram of a guide interface for opening a Huawei account provided in an embodiment of the present application;

[0070] Figure 11b This is a second schematic diagram of a guide interface for opening a payment account provided in an embodiment of the present application;

[0071] Figure 11c This is a third schematic diagram of a guide interface for opening a payment account provided in an embodiment of the present application;

[0072] Figure 12a This is one of the schematic diagrams of a red envelope management interface provided in an embodiment of the present application;

[0073] Figure 12b This is a second schematic diagram of a red envelope management interface provided in an embodiment of the present application;

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

[0075] Figure 14 This is a second flow chart of a method for sending and receiving red envelopes provided in an embodiment of the present application;

[0076] Figure 15 This is a flowchart of a method for sending and receiving red envelopes provided in an embodiment of the present application;

[0077] Figure 16 This is a fourth flow chart of a method for sending and receiving red envelopes provided in an embodiment of the present application;

[0078] Figure 17 This is a fifth flow chart of a method for sending and receiving red envelopes provided in an embodiment of the present application;

[0079] Figure 18 This is the sixth flow chart of a method for sending and receiving red envelopes provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0081] The at least one involved in the embodiments of the present application includes one or more; wherein, more means greater than or equal to two. In addition, it should be understood that, in the description of this specification, words such as "first" and "second" are only used for the purpose of distinguishing the description, and cannot be understood as expressing or implying relative importance, nor can they be understood as expressing or implying an order. For example, the first electronic device and the second electronic device do not represent the importance of the two or the order of the two, but are only for distinguishing the description. In the embodiments of the present application, "and / or" is only a description of the association relationship, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the previous and next associated objects are in an "or" relationship.

[0082] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in connection with that embodiment is included in one or more embodiments of the specification. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in 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 "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0083] The embodiments of the present application provide a method for sending and receiving red envelopes and an electronic device. The method can be applied to electronic devices and provides a new way to send and receive red envelopes. In this method, a first electronic device can send a red envelope to one or more second electronic devices based on a displayed red envelope sending interface based on short-range wireless communication technology. Correspondingly, the second electronic device can display a red envelope receiving interface based on short-range wireless communication technology to receive the red envelope sent by the first electronic device. In this way, through this method, there is no need to pre-establish a contact book friend relationship between electronic devices, which can improve the convenience of the red envelope sending and receiving scenario.

[0084] Among them, the red envelope sending and receiving method based on short-range wireless communication technology can be, for example, a touch method, a pre-defined air gesture, etc. For example, when the first electronic device displays the red envelope sending interface, it detects a touch with the second electronic device and can send the red envelope to the second electronic device. Correspondingly, the second electronic device can display the red envelope receiving interface in response to the touch with the first electronic device.

[0085] In the above example, onehop is a solution technology for multi-terminal business collaboration. It relies on short-range wireless communication protocols such as near field communication (NFC) or Bluetooth to open multi-device touch interaction capabilities to electronic device applications such as mobile phones and third-party devices, so that all-scenario devices can be connected to provide users with an efficient experience of seamless switching of multiple services between multiple devices. Exemplarily, onehop can be a way of touching the top of the first electronic device and the top of the second electronic device, or a way of touching the back of the first electronic device and the back of the second electronic device. It should be noted that the specific operation method of onehop is not limited in the embodiment of the present application. For example, the method of 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 device.

[0086] In some possible implementations of the "touch and pay" feature, when a first electronic device displays a red envelope sending interface and a second electronic device detects that ambient light data is less than a preset light intensity, the second electronic device can be triggered to transmit a broadcast signal so that other electronic devices that may be close to the second electronic device, such as the first electronic device, can detect the broadcast signal. The second electronic device can detect the ambient light data using an ambient light sensor.

[0087] Furthermore, simply by ensuring that the distance between the first and second electronic devices is less than a preset threshold and / or that 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. Furthermore, the second electronic device can receive the red envelope. This enables the sending and receiving of red envelopes between the first and second electronic devices, and realizes the instant, one-touch sending of red envelopes 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. The embodiment of the present application 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 means 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 means that the positions of the first electronic device and the second electronic device are not close. In some embodiments, the first electronic device determines the distance between the first electronic device and the second electronic device based on the broadcast signal in response to receiving a broadcast signal from the second electronic device. The process of determining the distance between the first electronic device and the second electronic device based on the broadcast signal can be: according to the signal strength of the broadcast signal, determine the transmission distance corresponding to the signal strength as the distance between the first electronic device and the second electronic device. Exemplarily, the first electronic device can pre-store 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, which is not limited in the embodiment of the present application.

[0089] In the above implementation, the magnetic data of the first electronic device is used to characterize the magnetic field conditions of the first electronic device, such as magnetic field strength, magnetic field direction, etc. It is understandable that the orientation of the first electronic device can be located based on the magnetic data of the first electronic device. In some embodiments, the first electronic device may use a magnetometer sensor to obtain the magnetic data of the first electronic device. It is worth noting that in other embodiments, the first electronic device may also use other methods to obtain magnetic data. The embodiments of the present application do not limit this. The magnetic data of the second electronic device is similar to that of the first electronic device and will not be repeated here. Among them, the preset correlation condition refers to a pre-set correlation condition, such as the magnetic data of the first electronic device is the same as the magnetic data of the second electronic device, or the similarity between the magnetic data of the first electronic device and the magnetic data of the second electronic device is greater than or equal to the preset similarity. The embodiments of the present application do not limit the setting of the preset correlation condition.

[0090] The electronic device of the embodiments of the present application can be a portable electronic device such as a mobile phone, a tablet computer, a laptop computer, or a wearable device such as a smart watch, a smart bracelet, a smart headset, a smart glasses, etc.; or, the electronic device can also be a smart home device such as a large screen, a smart speaker, etc. The embodiments of the present application do not impose any restrictions on the specific type of electronic device.

[0091] The electronic device of the embodiment of the present application may include but is not limited to a device equipped with Or other electronic devices with operating systems.

[0092] Figure 1Schematic diagram of the structure of an electronic device 100 provided in an embodiment of the present application. Figure 1 As shown, the electronic device 100 may include a processor 110, an 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, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, etc.

[0093] The processor 110 may include one or more processing units. For example, the processor 110 may include 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). The different processing units may be independent devices or integrated into one or more processors. The controller may serve as the nerve center and command center of the electronic device 100. The controller may generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution. The processor 110 may also include memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a high-speed cache memory. This memory may store instructions or data that have just been used or are being recycled by the processor 110. If the processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids duplicate accesses, reduces the processor 110's waiting time, and thus improves system efficiency.

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

[0095] In another possible example, when the electronic device 100 is a device for receiving red envelopes, the processor 110 can obtain second red envelope sending data from the device that sends the red envelope, and generate relevant interfaces 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; information verification can also be performed to ensure the security of red envelope reception.

[0096] The USB interface 130 is an interface that complies with USB standards, and may be a Mini USB interface, a Micro USB interface, a USB Type C interface, etc. The USB interface 130 may be used to connect a charger to charge the electronic device 100, and may also be used to transfer data between the electronic device 100 and peripheral devices.

[0097] The charging management module 140 is configured to receive charging input from a charger. The power management module 141 is configured to connect the battery 142, the charging management module 140, and 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, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160.

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

[0099] The wireless communication module 160 can provide wireless communication solutions applied to 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 technology (IR), Zigbee, Star Flash, etc. 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, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna. In the embodiment of the present application, the electronic device 100 can realize the sending and receiving of red envelopes by touching other electronic devices based on short-range wireless communication technologies such as NFC technology or Bluetooth.

[0100] In some embodiments, the antenna of the electronic device 100 is coupled to the wireless communication module 160 so that the electronic device 100 can communicate with a network 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 technology. 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 system (SBAS).

[0101] The display screen 194 is used to display the display interface of the application, such as the display page of the 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 or 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 the electronic device 100 is a device for sending red envelopes, the display screen 194 can be used to display interfaces related to sending red envelopes, such as a red envelope configuration interface, a red envelope sending interface, etc.; it can also display interfaces related to information verification, such as a real-name verification interface, a payment verification interface, etc.; it can also display interfaces related to red envelope management, such as a red envelope record interface, a red envelope record interface to be received, a red envelope record interface that has been sent, a red envelope interface that has been received, a red envelope reception details interface, etc. It can be understood that the electronic device can not only send red envelopes, but also receive red envelopes.

[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, etc.; it can also display interfaces related to red envelope management, such as a red envelope record interface, a red envelope record interface to be received, a sent red envelope record interface, a received red envelope interface, a red envelope receiving details interface, etc.

[0104] Camera 193 is used to capture still images or videos. Objects are projected onto the photosensitive element through the 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 one.

[0105] The internal memory 121 can be used to store computer executable program codes, which include 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. Among them, the program storage area can store an operating system, and the software code of at least one application, etc. The data storage area can store data generated during the use of the electronic device 100 (such as captured images, recorded videos, etc.). In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. In an embodiment of the present application, the internal memory 121 may store red envelope configuration data, red envelope details information, etc. obtained from the server.

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

[0107] Among them, the sensor module 180 may include but is not limited to an ambient light sensor 180A, a magnetic sensor 180B, a touch sensor 180C, etc. The ambient light sensor 180A is used to sense the brightness of ambient light. In an embodiment of the present application, the ambient light sensor 380C is used to detect the ambient light data of the terminal device to determine whether the terminal device is blocked. The touch sensor 180C is also called a "touch panel". The touch sensor 180C can be set 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 acting on or near it. The touch sensor 180C can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180C can also be set on the surface of the electronic device 100, at a different position from the display screen 194. In an embodiment of the present application, the magnetic sensor 180B can be a magnetometer sensor for detecting magnetic data of the terminal device.

[0108] The buttons 190 include a power button, a volume button, etc. The button 190 can be a mechanical button. It can also be a touch button. The electronic device 100 can receive button input and generate key signal input related to the user settings and function control of the electronic device 100. The motor 191 can generate a vibration prompt. The motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization. The indicator 192 can be an indicator light, which can be used to indicate the charging status, power changes, and can also be used to indicate messages, missed calls, notifications, etc.

[0109] It is understandable that 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 arrange the components differently. Figure 1 The combination / connection relationship between the components can also be adjusted and modified.

[0110] Figure 2 This is a software structure diagram of an electronic device provided in an embodiment of the present application. Figure 2 As shown, the software structure of the 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. The 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 (runtime) and system library, the kernel layer, and the hardware layer.

[0111] The application layer can include a series of application packages. Figure 2 As shown, the application layer may include camera, settings, skin module, user interface (UI), third-party applications, etc. Among them, third-party applications may include gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

[0112] The application framework layer provides application programming interface (API) and programming framework for the application layer. The application framework layer may include some predefined functions. 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 the embodiment of the present application, the application framework layer may include a sharing service (sharekit) capability and a payment service (payment kit) capability.

[0113] The share kit capability can be used to enable the sending or receiving of red envelopes between multiple electronic devices. For example, the share kit capability can be used to enable the sending or receiving of red envelopes between multiple devices by detecting touch events such as the top touch or the back touch of the electronic device. Among them, the share kit capability can be used to provide cross-application and cross-terminal sharing capabilities of text, pictures, videos and other content. For example, the first electronic device can be used as a sending terminal, and the second electronic device can be used as a receiving terminal. Through the sharing service, the first electronic device can send text, pictures, videos, etc. to the second electronic device.

[0114] The payment kit capability can be used to implement payment, marketing, and operational functions when sending and receiving red envelopes on electronic devices. For example, the payment kit capability 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 other red envelope-related processes.

[0115] The window manager manages windowed applications. It can determine the display size, determine whether a status bar is present, lock the screen, and take screenshots. Content providers store and retrieve data and make it accessible to applications. This data can include video, images, audio, incoming and outgoing calls, browsing history and bookmarks, and phone books.

[0116] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.

[0117] The phone manager is used to provide communication functions for electronic devices, such as call status management (including answering, hanging up, etc.).

[0118] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0119] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically without user interaction. For example, the Notification Manager is used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include text messages in the status bar, beeps, vibrations on electronic devices, and flashing indicator lights.

[0120] The runtime includes the core library 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 containing the Java language's callable functions and the other containing the operating system's core libraries. The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

[0122] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), a 2D graphics engine (e.g., SGL), and an image processing library.

[0123] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.

[0124] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, etc.

[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 drawing engine for 2D drawings.

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

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

[0129] It should be noted that Figure 1 and Figure 2The structure shown is only an example of the electronic device provided by the embodiment of the present application, and does not limit the electronic device provided by the embodiment of the present application. In specific implementation, the electronic device may have more Figure 1 or Figure 2 More or fewer devices or modules may be included in the structures shown.

[0130] The following is an introduction to a method for sending and receiving red envelopes provided in an embodiment of the present application.

[0131] Figure 3 A schematic diagram of a system architecture applicable to the red envelope sending and receiving method provided in an embodiment of the present application. The system architecture may include a first electronic device and one or more second electronic devices. Among them, the first electronic device can be understood as an electronic device that sends red envelopes, and can also be understood as a red envelope sending device, and the second electronic device can be understood as an electronic device that receives red envelopes, and can also be understood as a red envelope receiving device. 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 an exclusive red envelope, the system architecture may include one second electronic device. For another example, when the first electronic device sends a red envelope such as a lucky red envelope that includes 10 sub-red envelopes, the system architecture may include 10 second electronic devices.

[0132] Illustratively, the first electronic device and the second electronic device may send and receive red envelopes in one or more ways.

[0133] In some possible implementations, the first electronic device and the second electronic device can send and receive red envelopes through a touch-to-pay method.

[0134] In some other possible implementations, the first electronic device and the second electronic device can send and receive red envelopes not only through the touch method, but also through air gestures, QR codes, and password red envelopes. For example, in a scenario where the first electronic device sends 10 red envelopes, 5 second electronic devices can receive red envelopes from the first electronic device through the touch method, 1 second electronic device can receive red envelopes from the first electronic device through air gestures, 2 second electronic devices can receive red envelopes from the first electronic device by scanning QR codes, and the remaining 2 second electronic devices can receive red envelopes from the first electronic device in the form of password red envelopes. Among them, the touch method can be, for example, triggered by touching the top of the first electronic device and the top of the second electronic device, or by touching the back of the first electronic device and the back of the second electronic device. This application does not limit the specific operation method of the touch.

[0135] The air gesture method can be pre-set. For example, the user can trigger the sending of a red envelope through an air grab gesture on the red envelope sending interface on the first electronic device, and trigger the receiving of the red envelope from the first electronic device through an air release gesture on the second electronic device.

[0136] For example, the QR code method can be that the first electronic device responds to the user's flipping operation on the red envelope symbol card, triggering the flipping and display of the QR code corresponding to the red envelope, where the QR code can be used to indicate the red envelope sending data generated by the first electronic device, for example, including the red envelope logo, red envelope cover data, greetings, deeplink, etc. Correspondingly, the 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] The password red envelope method can be, for example, a first electronic device that generates a password for receiving a red envelope in response to a user's operation of generating a password red envelope for sending a red envelope. Accordingly, the second electronic device displays a red envelope receiving interface in response to the operation of inputting the password red envelope at a preset location. Alternatively, the password red envelope method can also be, for example, a first electronic device that responds to a user's flipping operation of a red envelope indication card to trigger flipping and displaying a password corresponding to the red envelope, wherein the password can be used by the second electronic device to receive the red envelope sent by the first electronic device. Accordingly, the second electronic device displays a red envelope receiving interface in response to the operation of inputting the password red envelope at a preset location.

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

[0139] In addition, it is understood that the first electronic device may support a tap-to-pay method, an air gesture method, a QR code method, a password red envelope method, etc. Correspondingly, the second electronic device may support at least one of the tap-to-pay method, the air gesture method, the QR code method, and the password red envelope method. When the second electronic device supports one method, it can receive red envelopes from the first electronic device in the supported method. When the second electronic device supports multiple methods, it can receive red envelopes from the first electronic device in the method selected by the user.

[0140] In this way, by providing a variety of red envelope sending and receiving methods, the needs of a variety of red envelope sending and receiving scenarios can also be met. For example, when the second electronic device supports short-range wireless communication methods such as touch and air gestures to receive red envelopes, the red envelopes can be conveniently received through these short-range wireless communication methods. When the second electronic device does not support short-range wireless communication methods to receive red envelopes, it can also successfully receive red envelopes through QR code methods or password red envelope methods. It can also be understood that when the red envelope sent by the first electronic device is a type that includes multiple sub-red envelopes, by providing a variety of red envelope sending and receiving methods, it is not restricted whether the second electronic device supports short-range wireless communication methods, which can facilitate users to choose a method to send and receive red envelopes, thereby improving the user's experience of using the red envelope function.

[0141] based on Figure 3 The system architecture shown in the figure is described in several sections below to introduce various application scenarios that can be provided by the method provided in the embodiment of the present application, so as to facilitate understanding of a red envelope sending and receiving method provided in the embodiment of the present application. In the following embodiments, the sending and receiving of red envelopes between a first electronic device and a second electronic device by a bumping method is used as an example, and other red envelope sending and receiving methods are not described in detail. It can be understood that the method provided in the embodiment of the present application is not limited to realizing the following application scenarios.

[0142] (1) Trigger entry for sending red envelopes

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

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

[0145] like Figure 4 As shown in interface 400B in , the first electronic device can provide a trigger entry for sending a red envelope 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] Exemplarily, the first electronic device responds to Figure 4 The triggering entry shown in interface 400A, or interface 400B, or interface 400C is triggered to 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 triggering entry for sending red envelopes is not limited in the embodiment of the present application. Figure 4The trigger entrances shown are only several possible examples. For example, trigger entrances may also be provided in the control center interface.

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

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

[0151] like Figure 5a The interface 500A in FIG is an example of a configuration interface for sending a red envelope by a first electronic device. The interface 500A can be based on Figure 4 The interface 500A may include a first configuration area 501, a second configuration area 502, a third configuration area 503, and a confirmation control 504.

[0152] (1) The first configuration area 501 is used to select the red envelope type. For example, the red envelope type may include ordinary red envelopes, lucky red envelopes, and good luck red envelopes. Among them, ordinary red envelopes can be, for example, red envelopes with the same amount for each sub-red envelope and a configurable number of red envelopes; lucky red envelopes can be, for example, red envelopes with random amounts for each sub-red envelope and a configurable number of red envelopes; and good luck red envelopes can be, for example, 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 envelopes, and the red envelope type selected in interface 500A is lucky red envelopes.

[0153] It should be noted that the types of red envelopes and the number of red envelope types included in the first configuration area are not limited in the embodiments of the present application. For example, the red envelope types may also include exclusive red envelopes, card and coupon red envelopes (that is, the red envelopes may include electronic card and coupon information), and physical red envelopes (that is, the red envelopes may include electronic physical information). Among them, an exclusive red envelope may, for example, be a red envelope with a target red envelope receiving 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 or one.

[0154] (2) A second configuration area 502 is used to display information based on the selected red envelope type. For example, when the selected red envelope type is a good luck red envelope, the second configuration area 502 may not need to include the number of red envelopes. For another example, when the selected red envelope type is a card or coupon red envelope, the second configuration area 502 may include selectable electronic cards and coupons.

[0155] like Figure 5a As shown in the interface 500A, taking the selected red envelope type as the lucky 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 blessings.

[0156] (3) The third configuration area 503 is used to select the red envelope cover. For example, when the user does not switch to select other red envelope covers, the default red envelope cover can be used; wherein the default red envelope cover can be a system default or a custom default. The process of switching to select the red envelope cover can be as described below. Figure 7 As shown, no further details are given here.

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

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

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

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

[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 may use schematic diagrams and text to prompt the user that they can send and receive red envelopes by tapping. The schematic diagram may be used to demonstrate how the first electronic device and the second electronic device can send and receive red envelopes by tapping. The text may include prompts such as "tap to send red envelope" for a user facing the first electronic device and "tap to receive red envelope" for a user facing the second electronic device.

[0162] It is understood that a schematic diagram and text may be used in the first prompt area 505 to prompt the user that red envelopes can be sent and received in other ways. For example, when prompting the user that red envelopes can be sent and received via QR codes, the schematic diagram may 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, and the second electronic device can scan the QR code displayed on the first electronic device to send and receive the red envelope; the text may 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 is not limited in the embodiment of the present application. For example, when the first prompt area 505 is used to prompt multiple red envelope sending and receiving methods, it can be displayed in a tiled manner, or multiple circularly switched window interfaces can be used to display multiple red envelope sending and receiving methods in turn.

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

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

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

[0167] In this way, by associating the red envelope schematic card displayed in the red envelope sending interface with the remaining number of red envelopes, the number of remaining red envelopes can be more realistically reflected, thereby improving the experience and fun of sending and receiving red envelopes.

[0168] While the first electronic device is displaying interface 500B1, the first electronic device can display interface 500C in response to a tap with the second electronic device. Interface 500C can include a tap display effect 507, a red envelope symbol card, and a prompt control 508 for indicating a swipe-up action to send. For example, the first electronic device can send a red envelope in response to a swipe-up action on the red envelope symbol card. In this way, on the first electronic device, a swiping action can simulate the real-life experience of sending a red envelope, enhancing the fun and experience of sending and receiving red envelopes.

[0169] Correspondingly, the second electronic device may display interface 500D in response to the touch with the first electronic device. Figure 5bInterface 500D shown in . Interface 500D may include: a touch display effect 509, a red envelope indication card 510, a receiving control 512A and a reject control 512B. Among them, the red envelope indication card 510 may also display a prompt text, and the prompt text is used to indicate the user who sent the red envelope, such as the user who sent the red envelope shown in interface 500D is user A. Exemplarily, in interface 500D, in response to a click operation on the receiving control 512A, the second electronic device may display interface 500E, and interface 500E is used to display a detailed interface for receiving the red envelope, for example, a prompt text may be displayed to indicate the user who received the red envelope, such as the user who received the red envelope shown in interface 500E is user B.

[0170] It should be noted that the embodiment of the present application does not limit the details interface for receiving red envelopes. For example, only the red envelope receiving details of the current user can be displayed, or the real-time receiving details of the red envelope can be displayed.

[0171] In addition, it should be noted that in the embodiment of the present application, there is no limitation on the interface displayed by the second electronic device before the second electronic device is touched with the first electronic device. That is, the present application does not limit the interface displayed before the second electronic device displays interface 500D. For example, the desktop interface can be displayed, or other application interfaces can be displayed.

[0172] In a possible implementation, after the second electronic device receives the red envelope, the first electronic device may display the following information: Figure 5c Interface 500F shown; then, when the display time reaches the preset time or in response to a click operation on the control to continue sending red envelopes, interface 500B2 can be displayed. Moreover, in interface 500B2, the first electronic device can refer to the process shown in interface 500C and interface 500F to continue sending the remaining red envelopes to other second electronic devices until the remaining red envelopes are sent. Correspondingly, other second electronic devices can refer to the process shown in interface 500D and interface 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. Among them, the preset time length can be, for example, 3 seconds (S) or 5S.

[0173] pass Figures 5a to 5c In the application scenario shown, two electronic devices can conveniently send and receive red envelopes using a tap-to-tap method based on a sharing service. Therefore, this method can provide a new way to send and receive red envelopes, making it more interesting and enhancing the user experience. Furthermore, with this method, the sending and receiving of red envelopes between two electronic devices is not restricted by whether or not the two electronic devices are in the address book, allowing for more convenient interaction and improving the efficiency of the red envelope function.

[0174] (3) Choose the red envelope cover

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

[0176] (4) Information Verification Process on the First Electronic Device

[0177] The first electronic device serves as a red envelope sending device, and information verification may include user real-name verification and payment verification. Exemplarily, user real-name verification may be obtained by guiding the user to upload certificate information, or it may be obtained from a user account that has already been registered with real name. Exemplarily, payment methods may include: bank card payment, account balance payment, etc. It is understandable that when the first electronic device can obtain a secure bank card for payment, the sending of red envelopes can be achieved, or when the first electronic device can obtain a secure account balance for payment, the sending of red envelopes can also be achieved. It should be noted that the specific implementation of the information verification process on the first electronic device is not limited in the embodiments of the present application.

[0178] In one possible implementation, when the first electronic device detects that the user account is not activated, it can display a guidance interface for activating the user account to the user. For example, after detecting the trigger event of sending a red envelope, an interface for activating the user account can be displayed. Taking the user account as a Huawei account as an example, Figure 8 A schematic diagram of a guide interface for opening a Huawei account provided in an embodiment of the present application. Figure 4Taking the triggering of sending red envelopes in interface 400A as an example, the first electronic device can display interface 900A in response to not opening a Huawei account. Interface 900A is the login interface of the Huawei account, and can also realize the registration of a Huawei account. The first electronic device can continue to display interface 400D based on the scenario that the Huawei account has been opened. Exemplarily, the user's real-name information can be obtained from the Huawei account to facilitate the determination of the red envelope sending user. Another example is that when the user's real-name information is not associated with the Huawei account, the user can be guided to upload the certificate information. For example, please refer to the following Figure 11c As shown, no further details are given here.

[0179] In another possible implementation, when the first electronic device detects that the payment account has not been opened, it may display a guidance interface for opening a payment account to the user. Figure 9 , is a schematic diagram of a guide interface for opening a payment account provided in an embodiment of the present application. Figure 9 Interface 900B in the Figure 4 In the red envelope sending interface shown in interface 400D, when the first electronic device detects that the payment account has not been opened, it can display control 901 in interface 900B. Control 901 is used to guide the user to open a payment account by adding a bank card. In interface 900B, the first electronic device responds to a click operation on control 901 and displays interface 900C. Interface 900C is an example diagram of adding a bank card. After the first electronic device detects that the bank card has been added, it can continue to display interface 400D. Figure 9 It can be seen that not opening a payment account does not affect the configuration of red envelopes. After configuring the red envelope amount, number of red envelopes, blessings, red envelope cover and other information, users can be guided to open a payment account.

[0180] In another possible implementation, in a scenario where a payment account has been opened, if an abnormal payment account status is detected during payment, the user can be guided to unfreeze the account. Figure 10 , is a schematic diagram of a guide interface for unfreezing a payment account provided in an embodiment of the present application. When making a payment as shown in interface 400D, if the first electronic device detects an abnormality in the payment account status, it may display interface 900D, which is used to guide the user to unfreeze the account through facial recognition verification; wherein, Figure 10 In the example, the payment account is a Huawei payment account. It can be understood that after the verification is passed, the display interface 400D can be restored.

[0181] It should be noted that the above Figures 8 to 10 Several possible scenarios of the information verification process on the first electronic device are introduced. In actual implementation, other methods or other entrances can also be used to guide the user to verify the information, and this application does not limit the specific implementation method.

[0182] (5) Information Verification Process on the Second Electronic Device

[0183] The second electronic device serves as a red envelope receiving device, and information verification may include user real-name verification. For example, user real-name verification may be obtained by guiding the user to upload certificate information, or may be obtained from a user account that has already been verified.

[0184] In one possible implementation, when the second electronic device detects that the user account has not been activated, it can display a guidance interface for activating a user account to the user. Taking the user account as a Huawei account as an example, the second electronic device can display an interface for activating a Huawei account after detecting the receipt of a red envelope. Figure 11a , is a schematic diagram of a guide interface for opening a Huawei account provided in an embodiment of the present application. Figure 5b Taking the click operation of the receiving control 512A included in the interface 500D as an example, the second electronic device can display the interface 1100A in response to not opening a Huawei account. The interface 1100A is the login interface of the Huawei account and can also realize the registration of the Huawei account. The second electronic device can continue to display the interface 500E based on the scenario that the Huawei account has been opened. Among them, the interface 1100A can refer to Figure 8 The interface 900A is shown in FIG. , and will not be described in detail here.

[0185] In another possible implementation, when the second electronic device detects that the payment account has not been opened, it can first display the red envelope receiving details interface to the user. For example, in the red envelope receiving details interface, a guidance interface for opening a payment account can be displayed to the user. Figure 11b , is a schematic diagram of a guide interface for opening a payment account provided in an embodiment of the present application. Figure 5b Taking the interface 500D in the example, when the second electronic device detects that the payment account has not been opened, it can display the interface 1100B, which may include guidance information 1101 and control 1102. The guidance information 1101 is used to remind the user that the red envelope is waiting to be credited, and the control 1102 is used to guide the user to open a payment account by adding a bank card to receive the red envelope. Figure 9 As shown, no further details are given here.

[0186] In another possible implementation, the second electronic device may also display a guidance interface for opening a payment account to the user in any interface where the red envelope function is used. Figure 11c , is another guide interface diagram for opening a payment account provided in an embodiment of the present application. Figure 11cAs can be seen in interface 1100C, in the red envelope configuration interface displayed when the second electronic device sends a red envelope, if the electronic device detects that a payment account has not been opened, it can display prompt area 1103. Prompt area 1103 may include prompt text guiding the user to open a payment account and control 1103A for uploading 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 documents.

[0187] In another possible implementation, the second electronic device may process the payment account when it detects an abnormal state. Figure 10 The processing process of the first electronic device introduced in will not be repeated here.

[0188] It should be noted that the above Figures 11a to 11c The following are several possible scenarios of the information verification process on the second electronic device. In actual implementation, other methods or other entrances can also be used to guide the user to perform information verification. This application does not limit the specific implementation method.

[0189] (6) Red Envelope Management

[0190] For example, the first electronic device and the second electronic device may 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 to-be-received red envelope record interface, a to-be-sent red envelope record interface, a sent red envelope record interface, a received red envelope interface, and a red envelope reception details interface.

[0191] For example, Figure 12a This is a schematic diagram of a red envelope management interface provided by an embodiment of the present application. Figure 12a Interface 1200A in the figure 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 are three different red envelope management interfaces. Interface 1200B shows a red envelope receiving details interface. Interface 1200C shows a red envelope record interface, which may include records of expired red envelopes, records of red envelopes to be received, records of red envelopes to be sent, etc. Interface 1200D shows a red envelope record interface for red envelopes to be received, which may include all records of red envelopes to be received.

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

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

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

[0195] For ease of distinction, the terms that may be used in the following embodiments are first explained:

[0196] (1) A user identifier (UID) on the first electronic device, which is used to indicate the user who sent the red envelope, and can therefore 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 a Huawei account logged in on the first electronic device. Exemplarily, 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 red envelope sending user. The device information may include, but is not limited to, device model, device name, device identifier, network information, positioning information, etc. The device identifier may include, but is not limited to, a universally unique identifier (UUID), an international mobile equipment identity (IMEI), a serial number (SN), an electronic serial number (ESN), a mobile equipment identifier (MEI), etc. The network information may include, for example, a cellular network, a wireless network, etc.

[0198] Exemplarily, the server can make risk control decisions based on the device information of the first electronic device to ensure payment security. For example, the server can perform location detection based on the device information of the first electronic device and the device information of the second electronic device. When the first and second electronic devices use a touch-to-pay method to send and receive red envelopes, the first and second electronic devices must be in close proximity. If the first and second electronic devices are not in close proximity, the server can determine that the transaction is abnormal to ensure payment security.

[0199] (3) The UID on the second electronic device is used to indicate the red envelope recipient user, and can therefore also be understood as the UID of the red envelope recipient user, 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. Exemplarily, the server can query and verify the real-name information of the red envelope recipient user based on the UID of the second electronic device.

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

[0201] (5) Red envelope identification (ID), used to associate red envelope-related information such as red envelope configuration information, red envelope details, and red envelope record information. For example, the server can store red envelope-related information and interact with the first electronic device or the second electronic device through the red envelope ID, thereby facilitating the server to determine which red envelope to call or manage based on the red envelope ID.

[0202] For example, Figure 13 A flowchart of a method for sending and receiving red envelopes provided in an embodiment of the present application. The process can be implemented by 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 a triggering event for sending a red envelope.

[0204] For example, the first electronic device can Figure 4 The trigger entry shown in the middle interface 400A, interface 400B or interface 400C detects the trigger event of sending red envelope. For the specific implementation process, please refer to Figure 4 shown.

[0205] like Figure 2 As shown, the first electronic device can use the payment kit capability to complete the preparation work for sending red envelopes, such as red envelope generation and red envelope configuration.

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

[0207] The basic configuration information of the red envelope may include, but is not limited to, the red envelope type, red envelope cover data, red envelope amount limit data, red envelope quantity limit data, blessing template data, etc.

[0208] Exemplarily, the server may be a cloud server or a server cluster, and the embodiments of the present application are introduced using a server.

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

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

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

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

[0213] Step 1305: The first electronic device obtains a configuration operation.

[0214] For example, Figure 5a As shown in the interface 500A, the configuration operation may 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 blessings in the second configuration area 502, and select the red envelope cover in the third configuration area 503, etc.

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

[0216] Among them, the red envelope configuration data 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 blessing message. The UID on the first electronic device can be understood as the UID of the user sending the red envelope, such as the UID of user A. Optionally, the server can query the real-name information of the user sending the red envelope through the UID on the first electronic device. When the real-name information of the user sending the red envelope is not queried, the server can instruct the first electronic device to guide the user to upload the certificate information. Alternatively, the UID on the first electronic device can also be the real-name information of the user.

[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 the user account 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. The first device information may be used to make risk control decisions for the red envelope, thereby ensuring the security of user payments. The device information of the first electronic device in the red envelope configuration data may be understood as the device information of the first electronic device when the red envelope was created.

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

[0221] The first red envelope sending data may include but is not limited to: red envelope ID, prepayment transaction session identifier (prepayID), and signature (sign). For example, the red envelope ID can be used by the server to query the stored red envelope configuration data to facilitate the management of the red envelope configuration data; the prepayID and sign can be used by the first electronic device to execute the payment processing process, and the specific implementation process is as follows Figure 14 For example, the server may associate the red envelope ID with the UID of the user who sent the red envelope, so that the server can manage the red envelope record information.

[0222] In addition, the server verifies the greeting. For example, when the verified greeting does not meet the content risk control rules, the user may be prompted to modify the greeting.

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

[0224] It can be understood that through the above steps 1301 to 1308, the first electronic device can complete the red envelope configuration process and generate a red envelope to be sent. Optionally, the red envelope to be sent can be a single red envelope. Another option is that 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 a red envelope sending interface.

[0226] For example, the red envelope sending interface can be as follows Figure 5a As shown in the interface 500B1 in FIG. Figure 5c As shown in interface 500B2.

[0227] Step 1310: While displaying the red envelope sending interface, the first electronic device detects a bump with the second electronic device.

[0228] Illustratively, the first electronic device and the second electronic device can achieve a touch by touching the top, or can achieve a touch by touching the back. This application does not limit the specific operation method of the touch.

[0229] In some possible implementations, the first electronic device can send the current device information of the first electronic device to the server in response to a touch with the second electronic device. Correspondingly, the server can store the device information of the first electronic device and set the cache duration according to the validity period of the red envelope, such as 24 hours; and the server can return the first device token to the first electronic device, and the first device token is used by the server to retrieve the device information of the first electronic device. It can be understood that the device information of the first electronic device may change with changes such as the movement of the first electronic device. The device information of the first electronic device sent in this step can be understood as the device information of the first electronic device when the red envelope is actually sent. Exemplarily, the server can make a risk control decision for the first electronic device based on the device information of the first electronic device when the red envelope is created and the device information of the first electronic device when the red envelope is actually sent.

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

[0231] Among them, the second red envelope sending data may include but is not limited to: red envelope ID, first device token, red envelope cover data, blessings, deeplink, etc. Deeplink is used for the second electronic device to jump from displaying any interface to displaying the red envelope receiving interface based on the red envelope function provided by the target application or target component. For example, deeplink includes a red envelope function for pulling up the payment kit capability. For example, the link path that can be used is: payment / redpacket. Optionally, the second electronic device can directly display the red envelope receiving interface according to the link path indicated by deeplink, and with the red envelope cover data, blessings, etc. included in the second red envelope sending data. Another option is that the red envelope cover data and blessings can also be encapsulated in deeplink, so that the second electronic device can directly display the red envelope receiving interface according to the link path indicated by deeplink.

[0232] For example, Figure 5a As shown in interface 500D in the figure, the second electronic device can directly display the red envelope receiving interface in response to the touch. In this way, the convenience of sending and receiving red envelopes can be improved, the user's manual operation can be reduced, and the operation complexity can be reduced. 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 can send the second red envelope data to the second electronic device through the share kit capability. Correspondingly, the second electronic device can receive the second red envelope data from the first electronic device through the share kit capability.

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

[0235] The red envelope receiving data may include: the UID and red envelope ID on the second electronic device. The UID on the second electronic device can be understood as the UID of the user receiving the red envelope, such as the UID of user B. Optionally, the server can query the real-name information of the user receiving the red envelope through the UID on the second electronic device. When the real-name information of the user receiving the red envelope is not found, the server can instruct the second electronic device to guide the user to upload the ID 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 in on 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, before sending the second red envelope to send data, the second 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 the user account to obtain the UID on the second electronic device. The specific implementation method is not limited.

[0238] In some possible implementations, the red envelope reception data may further include device information of the second electronic device, and the device information is used by the server to make risk control decisions, thereby ensuring the security of the user's payment. For example, the server may make risk control decisions regarding the current red envelope transmission and reception based on the device information of the first electronic device and the device information of the second electronic device when the red envelope is actually sent. For example, when the first and second electronic devices use a tap-to-pay method to transmit and receive red envelopes, and the first and second electronic devices are far apart, the server may determine that there is a risk in the current red envelope transmission and reception, thereby ensuring the security of the user's payment.

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

[0240] For example, the server can obtain red envelope configuration data based on the red envelope ID, determine the red envelope type, red envelope amount, number of sub-red envelopes, and other information based on the red envelope configuration data, and then determine the red envelope amount allocated to the second electronic device. For example, when the red envelope type is a good luck red envelope, it can be determined that the number of red envelopes is 1, and the red envelope amount allocated to the second electronic device is equal to the amount configured for the red envelope. For another example, when the red envelope type is a lucky red envelope, the amount of the sub-red envelope allocated to the second electronic device can be determined based on the amount configured for the red envelope and the number of sub-red envelopes.

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

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

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

[0244] Step 1316: The second electronic device displays a 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 As shown in interface 500E.

[0246] It should be noted that when the first electronic device detects that the red envelope has not been sent out completely, it can continue to send the remaining sub-red envelopes to other second electronic devices through the above steps 1310 to 1316. Figure 5c As shown. It should be noted that, for other second electronic devices to receive red envelopes from the first electronic device, please refer to the process in the previous article, which will not be repeated here. In addition, the embodiment of the present application does not limit other second electronic devices to receiving red envelopes from the first electronic device by the touch method, but can also be in the form of a QR code, 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, it can also be in the form of a password red envelope.

[0247] pass Figure 13 In the process shown, after the first electronic device is configured to send the red envelope, it can send the red envelope to the second electronic device based on the displayed red envelope sending interface through a method based on short-range wireless communication technology such as a touch, so that the second electronic device can directly pull up the red envelope function of the target service to display the red envelope receiving interface. In this way, the method can improve the convenience of sending and receiving red envelopes between electronic devices, realize one-touch instant sending of red envelopes, and reduce user operations. Moreover, the method does not need to limit the electronic devices to the address book friend relationship, which can reduce the operational complexity of the red envelope sending and receiving scenario, and can more conveniently realize the sending and receiving of red envelopes between two users. In addition, the method can also improve the application scenarios and fun of users using the red envelope function.

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

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

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

[0251] Among them, prepayment can be used to obtain payment methods, such as bank card payment, account balance payment, etc.

[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 a red envelope cashier according to the payment method.

[0254] Exemplarily, when the payment methods returned by the server include bank card payment and account balance payment, the red envelope cashier may include one or more bound bank cards and account balances.

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

[0256] Exemplarily, the first electronic device detects the payment method selected by the user and may request payment from the server according to the selected payment method.

[0257] In another example, if the first electronic device detects that the user chooses to add a bank card, it can request the server to bind the new bank card and make payment through the new bank card. Figure 9 Add a bank card on the interface shown.

[0258] It is understandable that after the server receives the payment request from the first electronic device, or the card binding and payment request, it can make a risk control decision. For example, the risk control decision can be made based on the device information and red envelope type of the first electronic device 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. Among them, the risk control result may include: face verification, verification code verification, fingerprint verification, or transaction failure, etc., for example, it can be determined by Figure 10 The interface shown is used for face recognition verification. It is understood that when the risk control decision is that the transaction is successful, there is no need to return the risk control result.

[0259] Step 1406: The first electronic device queries the server for a 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 a red envelope payment completion interface based on the red envelope payment result.

[0262] In an optional implementation, the first electronic device can set a display time threshold for the red envelope payment completion interface, such as 1S or 3S. Then, after the first electronic device detects that the display of the red envelope payment completion interface reaches the display time threshold, it can jump to the following Figure 13 Continue to the red envelope sending interface introduced in step 1309.

[0263] Step 1409: The server records the red envelope as a bump-and-pay red envelope scenario.

[0264] Exemplarily, the server may store the red envelope record data of the user who sent the red envelope, for example, the red envelope record data of user A.

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

[0266] Based on the previous Figures 8 to 10 According to the introduction, when sending red envelopes, the first electronic device needs to perform information verification process to support the above Figure 13 and Figure 14 The implementation process of the first electronic device in the process shown. For example, Figure 15 This is another flowchart of a red envelope sending and receiving process provided in an embodiment of the present application. This process can be used to implement the information verification process of the first electronic device. This process can be applied to the first electronic device and may include the following steps:

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

[0268] Step 1502A: Open a user account. For example, the process of opening a user account can be found in Figure 8 The user account is, for example, a Huawei account.

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

[0270] After executing step 1502A, continue to execute step 1502B.

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

[0272] Step 1503A: Open a payment account. For example, the process of opening a payment account can be found in Figure 9 shown.

[0273] After executing step 1503A, continue to execute step 1503B.

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

[0275] Step 1504A: Unfreeze the payment account. For example, the process of unfreezing the payment account can be found in Figure 10 shown.

[0276] After executing step 1504A, continue to execute step 1504B.

[0277] Step 1504B: The first electronic device detects whether it is an account balance payment. If so, proceed to step 1505B; otherwise, proceed to step 1505A.

[0278] For example, the first electronic device may Figure 14 The red envelope cashier displayed in step 1404 detects the payment method selected by the user.

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

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

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

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

[0283] Step 1507: Send red envelope.

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

[0285] It should be noted that Figure 15 This is an example of information verification performed by the first electronic device introduced in this application. This application does not limit the specific verification process and can be adjusted as needed.

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

[0287] Based on the previous Figures 11a to 11c The second electronic device also needs to perform information verification when receiving the red envelope to support the above Figure 13 The implementation process of the second electronic device in the process shown. For example, Figure 16 This is another flow diagram of sending and receiving a red envelope provided in an embodiment of the present application. This flow can be used to implement the information verification process of a second electronic device. This flow can be applied to the second electronic device and may include the following steps:

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

[0289] Step 1602A: Open a user account. For example, the process of opening a user account can be found in Figure 11a The user account is, for example, a Huawei account.

[0290] After executing step 1602A, continue to execute step 1602B.

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

[0292] Step 1603: Display the first red packet receiving details interface. For example, the first red packet receiving details interface is as follows: Figure 5b As shown in the interface 500E in FIG. 500E, it can be seen that the red envelope has been deposited into the balance.

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

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

[0295] After executing step 1605 , continue to execute step 1606 .

[0296] Step 1606: The red envelope is 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 the interface 1100B in FIG. 1100B, it can be seen that the red envelope has not been deposited into the balance.

[0298] Step 1608: The second electronic device guides the user to open a payment account.

[0299] Step 1609: The second electronic device detects whether the certificate is uploaded within the preset time. If so, continue to step 1606; otherwise, execute step 1610. Figure 11b As shown, the preset duration may 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 is an example of information verification performed by a second electronic device introduced in this application. This application does not limit the specific verification process and can be adjusted as needed.

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

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

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

[0305] It can be understood that the server maintains red envelope records to facilitate inquiries by the red envelope sending user or the red envelope receiving user.

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

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

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

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

[0310] It should be noted that the embodiments of the present application do not limit the timing at which the first electronic device and the second electronic device query the server. For example, the query may be made in response to a user operation or periodically.

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

[0312] pass Figure 17 In the method shown, the server maintains the red envelope record, which can facilitate the first electronic device and / or the second electronic device to query the red envelope details information, ensuring the timeliness of the update of the red envelope details information.

[0313] Based on the same concept, an embodiment of the present application also provides a method for sending and receiving red envelopes, which can be executed by a first electronic device. Figure 18 This is a flowchart of a red envelope sending and receiving method provided in an embodiment of the present application, refer to Figure 18 , the method comprises the following steps:

[0314] Step 1801: The first electronic device displays a first interface, which includes first guidance information and a red envelope schematic card. The first guidance information is used to indicate that a first red envelope corresponding to the red envelope schematic card is sent to a second electronic device in a first manner, and the first manner is implemented based on short-range wireless communication technology.

[0315] For example, the first interface is as follows: Figure 5a In the interface 500B1, the first guidance information is shown in the first prompt area 505, and the red envelope indication card is shown in the second prompt area 5061. It can be understood that the red envelope indication card in the first interface can be one or more. The first method can be, for example, a touch-and-pay method.

[0316] Step 1802: The first electronic device sends a first red packet to the second electronic device in response to a first event that meets the triggering condition of the first mode. Accordingly, the second electronic device detects the first event.

[0317] For example, the first electronic device sends a first red packet to the second electronic device, for example, Figure 13 As shown in step 1312 in .

[0318] Step 1803: The second electronic device displays a second interface in response to the first event, where the second interface 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 schematic card is, for example, the red envelope schematic card 510 shown in interface 500D.

[0320] It should be noted that this application Figure 18 When implementing the red envelope sending and receiving method shown, please refer to the above embodiments of this application, and the repeated parts will not be repeated.

[0321] Based on the above embodiments, the present application further provides an electronic device, which includes multiple functional modules; the multiple functional modules interact with each other to implement the functions performed by the first electronic device or the second electronic device in each method described in the embodiments of the present application. Figure 13 In the embodiment shown, the first electronic device or the second electronic device performs the steps, or performs Figure 14 In the embodiment shown, the first electronic device performs the steps or performs Figure 15 In the embodiment shown, the first electronic device performs the steps or performs Figure 16 In the embodiment shown, the first electronic device performs the steps, or performs Figure 17 In the embodiment shown, the first electronic device or the second electronic device performs the steps, or performs Figure 18 The steps performed by the first electronic device or the second electronic device in the illustrated embodiment. 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.

[0322] Based on the above embodiments, the present 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, and when the electronic device is running, the at least one processor executes the functions executed by the first electronic device or the second electronic device in each method described in the embodiments of the present application. Figure 13 In the embodiment shown, the first electronic device or the second electronic device performs the steps, or performs Figure 14 In the embodiment shown, the first electronic device performs the steps or performs Figure 15 In the embodiment shown, the first electronic device performs the steps or performs Figure 16 In the embodiment shown, the first electronic device performs the steps, or performs Figure 17 In the embodiment shown, the first electronic device or the second electronic device performs the steps, or performs Figure 18Steps performed by the first electronic device or the second electronic device in the embodiment shown

[0323] Based on the above embodiments, the present application further provides a red envelope sending and receiving system, comprising a first electronic device, M second electronic devices, and a server. M can be determined based on the number of red envelopes configured for the first electronic device, and M can be less than or equal to the number of configured 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, the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute the methods described in the embodiments of the present application.

[0325] Based on the above embodiments, the present application further provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a computer, the computer executes the methods described in the embodiments of the present application.

[0326] Based on the above embodiments, the present application further provides a chip, which is used to read a computer program stored in a memory to implement the various methods described in the embodiments of the present application.

[0327] Based on the above embodiments, the present application provides a chip system, which includes a processor for supporting a computer device to implement the various methods described in the embodiments of the present application. In one possible design, the chip system also includes a memory for storing the necessary programs and data for the computer device. The chip system can be composed of a chip or can include a chip 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] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each process and / or block in the flowchart and / or block diagram, as well as the combination of processes and / or blocks in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 a process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[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 operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing the instructions executed on the computer or other programmable device for implementing the process. Figure 1 a process or multiple processes and / or boxes Figure 1 A step that specifies a function in one or more boxes.

[0332] Obviously, those skilled in the art may make various modifications and variations to this application without departing from the scope of protection of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A red envelope sending and receiving method, applied to a first electronic device, characterized in that: The method comprises: Displaying a first interface, the first interface including first guidance information and a red envelope schematic card, the first guidance information being used to instruct a first red envelope corresponding to the red envelope schematic card to be sent to a second electronic device in a first manner, the first manner being implemented based on a short-range wireless communication technology; In the first interface, in response to a first event that meets the triggering condition of the first method, the first red envelope is sent to the second electronic device.

2. The method according to claim 1, characterized in that The sending the first red packet 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 jump to an interface for displaying receiving the first red envelope.

3. The method according to claim 1, characterized in that The first information is a deep link deeplink, and the deeplink is used by the second electronic device to display an interface for receiving the first red envelope according to a link path, and the link path is used to pull up 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: Sending second data to the server, the second data comprising: a user identifier UID of the first electronic device and second information, the second information being used to indicate the configuration of the red envelope; Receive third data sent by the server, where the third data includes: a red envelope identifier.

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

6. The method according to any one of claims 1 to 5, characterized in that The red envelope schematic card corresponds to multiple sub-red envelopes; The number of the red packet schematic cards included in the first interface corresponds to the number of remaining sub-red packets; or, When the number of the remaining sub-red envelopes is greater than the quantity threshold, the number of the red envelope schematic cards is the quantity threshold; when the number of the remaining sub-red envelopes is less than or equal to the quantity threshold, the number of the red envelope schematic cards corresponds one-to-one to the number of the remaining sub-red envelopes.

7. The method according to any one of claims 1 to 6, characterized in that The sending the first red packet to the second electronic device in response to the first event satisfying the triggering condition of the first mode includes: In response to the first event, displaying a second interface, the second interface including a first red envelope schematic card, the first red envelope schematic card being used to indicate the first red envelope; In the second interface, in response to a sliding operation on the first red envelope indication card, the first red envelope is sent to the second electronic device.

8. The method according to any one of claims 1 to 7, characterized in that The first manner is a manner in which the first electronic device and the second electronic device touch each other, and the first event is a manner in which the first electronic device and the second electronic device touch each other; or, The first method is a preset air gesture method, the first event is that the first electronic device detects a first air gesture, the first electronic device detects that the second electronic device detects a second air gesture, the first air gesture is used to indicate sending the first red envelope, and the second air gesture is used to indicate receiving the first red envelope.

9. The method according to any one of claims 1 to 8, characterized in that The first interface further includes second guidance information, where the second guidance information is used to instruct to send the first red envelope corresponding to the red envelope schematic card to the second electronic device in a second manner; Among them, the second method includes: QR code method, or password red envelope method.

10. The method according to claim 9, characterized in that The method further comprises: In response to the first operation, displaying a third interface, the third interface being used to display a QR code corresponding to the first red envelope, or a password red envelope; Among them, the first operation is a click operation on the first control, and the first control is a control for flipping the red envelope schematic card, or a control for generating a QR code or password red envelope corresponding to the first red envelope.

11. The method according to any one of claims 1 to 10, characterized in that The method further comprises: When it is detected that there are still remaining sub-red envelopes, a fourth interface is displayed, wherein the fourth interface includes the third guide information and a red envelope schematic card; The third guidance information is used to instruct that the second red packet corresponding to the red packet schematic card is sent to the third electronic device in the first manner, and the second red packet is one of the remaining sub-red packets.

12. The method according to any one of claims 1 to 11, 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: a triggering operation on a second control in the negative one screen interface, or detecting a preset voice command, or a triggering operation on a third control in the first application, the second control, the preset voice command, and the third control are used to instruct sending a red envelope; the fifth interface is used to configure the red envelope; A configuration operation on the fifth interface is detected.

13. The method according to claim 12, characterized in that Before displaying the fifth interface, the method further includes: In response to the second event, when it is detected that the user account has not been opened, a sixth interface is displayed, wherein the sixth interface is used to guide the user to open a user account.

14. The method according to claim 12 or 13, characterized in that The fifth interface includes a fourth control, and the fourth control is used to open a payment account.

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

16. The method according to any one of claims 1 to 15, characterized in that The method further comprises: Send fourth data to the server, the fourth data including: a red envelope identifier, and the fourth data is used to query the red envelope receiving details.

17. The method according to any one of claims 1 to 16, characterized in that The method further comprises: In response to the second operation, displaying an eighth interface; Among them, 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 received red envelopes, and records of sent red envelopes.

18. A red envelope sending and receiving method, applied to a second electronic device, characterized in that: The method comprises: A first event is detected, where the first event is used to indicate that the second electronic device and the first electronic device meet a triggering condition of a first mode, where the first mode is implemented based on a short-range wireless communication technology; In response to the first event, a first interface is displayed, wherein the first interface includes: a first red envelope schematic card, wherein the first red envelope schematic card is used to indicate a first red envelope sent by the first electronic device.

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

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

21. The method according to any one of claims 18 to 20, characterized in that The method further comprises: Sending second data to the server, the second data including: a user identifier UID and a red envelope identifier of the second electronic device; Receive third data sent by the server, where the third data includes: the amount of the first red envelope.

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

23. The method according to any one of claims 18 to 22, characterized in that The method further comprises: In response to a first operation, displaying a second interface; the first operation is used to instruct receiving the first red packet; Wherein, when the second electronic device detects that the payment account has been opened, the second interface is used to indicate the receiving details of the first red envelope; or, When the second electronic device detects that the payment account has not been opened, the second interface is used to indicate the reception details of the first red envelope and the first guidance information, and the first guidance information is used to guide the user to open a payment account.

24. The method according to claim 23, characterized in that Before displaying the second interface, the method further includes: In response to the second event, when it is detected that the user account has not been opened, a third interface is displayed, wherein the third interface is used to guide the user to open a user account.

25. The method according to any one of claims 18 to 24, characterized in that The first manner is a manner in which the first electronic device and the second electronic device touch each other, and the first event is a manner in which the first electronic device and the second electronic device touch each other; or, The first method is a preset air gesture method, the first event is that the second electronic device detects a second air gesture, and the second air gesture is used to receive the first red envelope.

26. The method according to any one of claims 18 to 25, characterized in that The method further comprises: Send fourth data to the server, the fourth data including: a red envelope identifier, and the fourth data is used to query the red envelope receiving details.

27. The method according to any one of claims 18 to 26, characterized in that The method further comprises: In response to the second operation, displaying a fourth interface; Among them, 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 received red envelopes, and records of sent red envelopes.

28. A red envelope sending and receiving method, applied to a server, characterized in that: The method comprises: Receive first data sent by a first electronic device; the first data includes: a user identifier UID of the first electronic device and first information, the first information being used to indicate the configuration of the red envelope; Generate a red envelope to be sent and second data according to the first data, wherein the second data includes a red envelope identifier for indicating the red envelope to be sent; sending the second data to the first electronic device; receiving third data of the second electronic device, the third data including: the UID of the second electronic device and the red envelope identifier; Query the red envelope to be sent according to the red envelope identifier; Generate and send fourth data to the second electronic device, where the fourth data includes: the amount of the first red envelope allocated to the second electronic device.

29. An electronic device, characterized in that: The method comprises at least one processor coupled to at least one memory, wherein the at least one processor is used to read a computer program stored in the at least one memory to execute the method according to any one of claims 1 to 17, or to execute the method according to any one of claims 18 to 27.

30. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores instructions, which, when executed on a computer, enable the computer to execute the method described in any one of claims 1 to 17, or to execute the method described in any one of claims 18 to 27.

Images