Cross-device resource sharing method and electronic device

Abstract

A cross-device resource sharing method and an electronic device, which relate to the technical field of electronic devices and can improve the convenience and intelligence of cross-device resource sharing. The method comprises: when a first electronic device displays a first interface of a first application, sending an indication message to at least one electronic device in response to a detected resource sending gesture, wherein first content is displayed in the first interface, the resource sending gesture is used for instructing the first electronic device to share resources with other electronic devices, the resource sending gesture is a gesture not in contact with a display screen of the first electronic device, and the indication message is used for indicating that the first electronic device is about to share resources. On the basis of a communication connection with a second electronic device among the at least one electronic device, the first electronic device can send the first content to the second electronic device.

Description

Cross-device resource sharing methods and electronic devices

[0001] This application claims priority to Chinese patent application filed on November 15, 2024, with application number 202411642132.4 and entitled "Method and Electronic Device for Cross-Device Resource Sharing", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of electronic device technology, and in particular to cross-device resource sharing methods and electronic devices. Background Technology

[0003] With the rapid development of electronic device technology, electronic devices are becoming increasingly feature-rich, and users' needs for them are becoming more diverse. Currently, when using electronic devices, users may want to share resources (including but not limited to pictures, videos, news, and other resources) with friends so that they can have a better browsing experience. Therefore, improving the convenience and intelligence of cross-device resource sharing is crucial. Summary of the Invention

[0004] This application provides a cross-device resource sharing method and electronic device, which can improve the convenience and intelligence of cross-device resource sharing.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] In a first aspect, a cross-device resource sharing method is provided, applied to a first electronic device having a display screen. The method includes: when displaying a first interface of a first application, in response to a detected resource sending gesture, sending an instruction message to at least one electronic device, wherein the first interface displays first content, the resource sending gesture is used to instruct the first electronic device to share resources with other electronic devices, the resource sending gesture is a gesture that does not touch the display screen of the first electronic device, and the instruction message is used to instruct the first electronic device to share resources; and sending the first content to the second electronic device based on a communication connection with a second electronic device among the at least one electronic device.

[0007] Based on the above technical solution, when an electronic device displays an interface of an application, upon detecting a resource-sharing gesture that is not in contact with the screen, it can send an instruction message to other electronic devices indicating that it is about to share resources. Then, based on the communication connection with another electronic device, it can share content from the displayed interface with that device. Users do not need to perform any touch operations on the electronic device screen, and cross-device resource sharing can still be achieved even if the user's fingers are wet or otherwise unable to touch the screen. Furthermore, the resource sender and receiver do not need to be in contact, improving the convenience and intelligence of cross-device resource sharing.

[0008] In one possible design, the method further includes: when displaying a second interface of the first application, in response to a detected resource sending gesture, sending an instruction message to at least one electronic device, wherein the second interface is different from the first interface; and sending a screenshot of the second interface to the second electronic device based on a communication connection with the second electronic device among the at least one electronic device.

[0009] In this way, when a certain interface of an application does not support cross-device resource sharing, if the user performs a resource sending gesture on the resource sending end, the resource sending end can send an indication message to the outside world to indicate that it is about to send resources. The resource sending end can then send a screenshot of the resource from that interface of the application to the resource receiving end. This not only makes cross-device resource sharing more convenient and intelligent, but also ensures that even if a certain interface of an application does not support AirShare, cross-device resource sharing can still be achieved through screenshots, thus guaranteeing a good user experience.

[0010] In one possible design, the method further includes: when displaying the interface of a second application, in response to a detected resource sending gesture, sending an instruction message to at least one electronic device, the second application being different from the first application; and sending a screenshot of the interface to the second electronic device based on a communication connection with the second electronic device among the at least one electronic device.

[0011] In this way, even if an application doesn't support cross-device resource sharing, if the user performs a resource-sending gesture on the resource sender, the sender can send an indication message to the outside world to indicate that it is about to send the resource. The resource sender can then send a screenshot of the application's resource to the resource receiver. This not only makes cross-device resource sharing more convenient and intelligent, but also ensures that even if an application doesn't support cross-device resource sharing, it can still be achieved through screenshots, thus guaranteeing a good user experience.

[0012] In one possible design, sending the first content to the second electronic device based on the communication connection with the second electronic device among the at least one electronic device includes: sending the first content to the second electronic device based on the communication connection with the second electronic device among the at least one electronic device, and sending the first content to the third electronic device based on the communication connection with the third electronic device among the at least one electronic device. In this way, the resources of one electronic device can be received by multiple other electronic devices simultaneously, realizing the simultaneous sharing of resources with multiple other electronic devices.

[0013] In one possible design, sending the first content to the second electronic device based on the communication connection with the second electronic device among the at least one electronic device includes: establishing a communication connection with the second electronic device based on the indication message; and sending the first content to the second electronic device based on the communication connection. In this way, after sending the indication message, the resource sending end can establish a communication connection with the second electronic device based on the indication message, thereby determining which specific electronic device to share resources with when multiple other electronic devices are present.

[0014] In one possible design, the resource sending gesture includes a start gesture and an end gesture. The start gesture indicates the beginning of the resource sending gesture execution, and the end gesture indicates the end of the resource sending gesture execution. Before sending the first content to the second electronic device based on the communication connection, the method further includes: generating preview data of the first content when the start gesture is detected; and sending the preview data of the first content to the second electronic device based on the communication connection. In this way, the resource sending end generates preview data of the first content when it detects the start gesture in the resource sending gesture. Subsequently, after the first electronic device establishes a communication connection with the second electronic device, it is not necessary to perform the operation of generating preview data of the first content again; the preview data of the first content can be sent directly, which can reduce the perceived latency for the user and improve the user experience.

[0015] In one possible design, sending an indication message to at least one electronic device in response to a detected resource sending gesture includes: sending the indication message to the at least one electronic device in response to detecting the start gesture and the end gesture.

[0016] In one possible design, the method further includes: displaying a gesture icon corresponding to the start gesture when the start gesture is detected; or, displaying a gesture movement animation effect when the end gesture is detected to have moved out of front of the first electronic device, the gesture movement animation effect including a light and shadow movement animation effect on the display screen. Displaying a gesture icon corresponding to the start gesture when the start gesture is detected allows the user to confirm that the electronic device has begun to recognize the resource sending gesture based on the gesture icon. When the end gesture moves out of front of the electronic device, the electronic device can also display a light and shadow movement animation effect on the display screen; that is, the light and shadow can change according to the position of the end gesture in front of the electronic device, enhancing the technological feel of human-computer interaction.

[0017] The positions of the light and shadow 711 and 720 displayed on the screen of the electronic device 10 can change in real time according to the real-time changes in the position of the fist in the air-grabbing gesture in front of the electronic device 10. Thus, the electronic device 10 can give users the experience of the light and shadow 711 and 720 being controlled by the user's fist in the air, enhancing the technological feel of human-computer interaction and improving the user experience when using electronic devices to share resources across devices.

[0018] In one possible design, the direction in which the light and shadow move on the display screen is the same as the direction in which the ending gesture moves out in front of the first electronic device. In this way, the light and shadow in the gesture animation can move along the direction of the ending gesture, giving the user the experience of having the light and shadow manipulated remotely by the user's ending gesture, enhancing the technological feel of human-computer interaction and improving the user experience when sharing resources across devices.

[0019] In one possible design, after detecting a resource sending gesture, the method further includes: displaying a first pending animation effect, wherein the first pending animation effect includes at least one of a card generated based on the first content and light and shadow. In this way, after detecting a resource sending gesture, the electronic device displays the pending animation effect, making it easy for the user to know that the electronic device has responded to the user's request to share resources across devices.

[0020] In one possible design, during the process of sending the first content to the second electronic device, the method further includes: displaying a sending animation, the sending animation including at least one of preview data of the first content and lighting effects; and / or, displaying a target control, the target control being used to indicate the sending progress of the first content. In this way, when an electronic device shares resources with other electronic devices, it can also display sending animations including preview data of the shared resources and lighting effects, making it easier for users to know which resources are currently being shared. Presenting a target control to indicate the resource sending progress to the user can enhance the technological feel of human-computer interaction.

[0021] In one possible design, after detecting a resource sending gesture, the method further includes: displaying a second animation to be sent, the second animation including at least one of a screenshot of the second interface and light and shadow.

[0022] In one possible design, the first electronic device and the second electronic device are logged into different system accounts. Before sending the first content to the second electronic device, the method further includes: if the first electronic device and the second electronic device have not established a trust relationship, displaying a reminder message, the reminder message being used to confirm with the user whether to send the first content to the second electronic device or whether to establish a trust relationship with the second electronic device; or, if the first electronic device and the second electronic device have established a trust relationship, not displaying a reminder message, the reminder message being used to confirm with the user whether to send the first content to the second electronic device or whether to establish a trust relationship with the second electronic device. Thus, when the first electronic device and the second electronic device are logged into different system accounts, if they have not established a trust relationship, the system account can confirm with the user whether to send resources to the second electronic device or whether to establish a trust relationship with the second electronic device. This can improve the security of cross-device resource sharing. When they have established a trust relationship, the first electronic device no longer needs to output the aforementioned reminder message, and they can directly share resources across devices. This ensures the security of cross-device resource sharing without disturbing the user, providing a seamless sharing experience.

[0023] In one possible design, the first electronic device includes a AirShare service. This service provides an application registered with the AirShare service within the first electronic device with the ability to share its resources with other electronic devices. The first application is registered with the AirShare service, and its first interface is a preset interface that allows the use of the AirShare service, while its second interface is a preset interface that does not allow the use of the AirShare service. Alternatively, the second application may be an application not registered with the AirShare service. Thus, when an application is registered with the AirShare service, it can directly share resources across devices via the service, and the application can also specify which interface can use the service. Conversely, when an application is not registered with the AirShare service, it cannot directly share resources across devices via the service.

[0024] In one possible design, the resource sending gesture includes a gesture that changes from a palm to a fist.

[0025] In a second aspect, a cross-device resource sharing method is provided, applied to a second electronic device having a display screen. The method includes: receiving an indication message from a first electronic device, the indication message from the first electronic device indicating that the first electronic device is about to share resources; responding to the indication message from the first electronic device and a detected resource receiving gesture, receiving first content from the first electronic device based on a communication connection with the first electronic device, wherein the resource receiving gesture is a gesture that does not touch the display screen of the second electronic device, and the first content is content in a first interface of a first application displayed on the first electronic device.

[0026] In one possible design, the method further includes: in response to an instruction message from the first electronic device and the detected resource receiving gesture, receiving a screenshot of a second interface from the first electronic device based on a communication connection with the first electronic device, wherein the screenshot of the second interface is a screenshot of the second interface of the first application displayed on the first electronic device, and the second interface is different from the first interface.

[0027] In one possible design, the method further includes: in response to an instruction message from the first electronic device and the detected resource receiving gesture, receiving a screenshot of an interface from the first electronic device based on a communication connection with the first electronic device, wherein the screenshot is a screenshot of the interface of a second application displayed on the first electronic device, and the second application is different from the first application.

[0028] In one possible design, before receiving the first content from the first electronic device, the method further includes: receiving an indication message from a third electronic device, the indication message from the third electronic device indicating that the third electronic device is about to share resources; the step of receiving the first content from the first electronic device in response to the indication message from the first electronic device and a detected resource receiving gesture, based on the communication connection with the first electronic device, includes: in response to the indication message from the first electronic device, the indication message from the third electronic device, and the detected resource receiving gesture, receiving the first content from the first electronic device based on the communication connection with the first electronic device, wherein the system account logged in by the first electronic device and the second electronic device is the same; or, the system accounts logged in by the first electronic device and the second electronic device are different, and the first electronic device is an electronic device selected by the user.

[0029] In this way, when multiple resource senders exist, the resource receiver can choose to receive resources from the same system account, which can improve the security and privacy of cross-device resource sharing. Alternatively, the resource receiver can also receive resources from a specific resource sender based on user selection, thus meeting the user's actual needs.

[0030] In one possible design, before receiving the first content from the first electronic device, the method further includes: detecting the resource receiving gesture at a first frequency if no indication message is received from the first electronic device; and detecting the resource receiving gesture at a second frequency if the indication message is received from the first electronic device, wherein the second frequency is higher than the first frequency. In this way, the frequency at which the resource receiving gesture is detected before the indication from the resource receiving end to the resource sending end is lower than the frequency after receiving the indication message. That is, after receiving the indication message, the resource receiving end can increase the frequency of detecting the resource receiving gesture, enabling faster and more accurate identification of the gesture, improving the efficiency of cross-device resource sharing, and thus enhancing the intelligence of cross-device resource sharing.

[0031] In one possible design, the resource receiving gesture includes a start gesture and an end gesture. The start gesture indicates the beginning of the execution of the resource receiving gesture, and the end gesture indicates the end of the execution of the resource receiving gesture. Before receiving the first content from the first electronic device based on the communication connection with the first electronic device, the method further includes: establishing the communication connection with the first electronic device in response to the detected start gesture. In this way, the resource receiving end establishes a communication connection with the resource sending end when it detects the start gesture in the resource receiving gesture, i.e., establishing the connection in advance. Compared to the method of establishing a communication connection after receiving the end gesture, this can reduce the perceived latency for the user and improve the user experience.

[0032] In one possible design, the resource receiving gesture includes a start gesture and an end gesture, wherein the start gesture indicates the beginning of the execution of the resource receiving gesture, and the end gesture indicates the end of the execution of the resource receiving gesture; the method further includes: when the start gesture is detected, displaying a gesture icon corresponding to the start gesture; or, when the start gesture is detected to have moved in front of the second electronic device, displaying a gesture movement animation, wherein the gesture movement animation includes an animation of light and shadow moving on the display screen.

[0033] In one possible design, the direction in which the light and shadow move on the display screen is the same as the direction in which the start gesture moves in front of the second electronic device.

[0034] In one possible design, before receiving the first content from the first electronic device, the method further includes: in response to an instruction message from the first electronic device, upon detecting the end gesture, receiving preview data of the first content from the first electronic device based on the communication connection with the first electronic device;

[0035] In one possible design, the method further includes: displaying a receiving animation during the process of receiving the first content, the receiving animation including at least one of the preview data of the first content and lighting effects.

[0036] In one possible design, the system accounts logged into the first electronic device and the second electronic device are different. Before receiving the first content from the first electronic device, the method further includes: if the first electronic device and the second electronic device have not established a trust relationship, displaying a reminder message, the reminder message being used to confirm with the user whether to receive the first content from the first electronic device or whether to establish a trust relationship with the first electronic device; or, if the first electronic device and the second electronic device have established a trust relationship, not displaying a reminder message, the reminder message being used to confirm with the user whether to receive the first content from the first electronic device or whether to establish a trust relationship with the first electronic device.

[0037] In one possible design, the resource receiving gesture includes a gesture that changes from a clenched fist to a palm.

[0038] Thirdly, an electronic device is provided that has the function of implementing the method described in any of the designs of any of the preceding aspects. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the described function.

[0039] Fourthly, an electronic device is provided, comprising: a processor, a memory, a display screen, and a communication interface. The memory, the display screen, and the communication interface are coupled to the processor. The communication interface is used for communicating with other devices. The memory stores program code, including instructions. The processor reads the instructions from the memory to cause the electronic device to perform the method described in any of the designs of any of the preceding aspects. Optionally, the memory may be coupled to the processor or independent of the memory. Exemplarily, the communication interface may be a transceiver, an input / output interface, an interface circuit, an output circuit, an input circuit, a pin, or related circuitry, etc. The display screen can be used by the electronic device to perform display operations.

[0040] Fifthly, a computer-readable storage medium is provided, the computer-readable storage medium including a computer program that, when run on an electronic device, causes the electronic device to perform the method as described in any of the preceding aspects.

[0041] A sixth aspect provides a computer program product comprising: a computer program or instructions that, when executed on a computer, cause the computer to perform the method as designed in any of the preceding aspects.

[0042] A seventh aspect provides a chip system including at least one processor and at least one interface circuit, the at least one interface circuit being used to perform transceiver functions and send instructions to at least one processor, wherein when at least one processor executes instructions, at least one processor performs the method as described in any of the designs in any of the preceding aspects.

[0043] Eighthly, a communication system is provided, including a first electronic device and a second electronic device, wherein the first electronic device is configured to perform a method performed by the first electronic device as described in any of the preceding aspects, and the second electronic device is configured to perform a method performed by the second electronic device as described in any of the preceding aspects and any of the preceding aspects.

[0044] The technical effects of the aforementioned aspects can be referenced from each other, and will not be elaborated further here. Attached Figure Description

[0045] Figure 1 is a schematic diagram of a cross-device resource sharing scenario provided by an embodiment of this application;

[0046] Figure 2 is a schematic diagram of a scenario for a remotely operated electronic device provided in an embodiment of this application;

[0047] Figure 3 is a schematic diagram of another scenario of cross-device resource sharing provided by an embodiment of this application;

[0048] Figure 4 is a schematic diagram of the architecture of a communication system provided in an embodiment of this application;

[0049] Figure 5 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0050] Figure 6 is a schematic diagram of the structure of another electronic device provided in an embodiment of this application;

[0051] Figure 7 is a schematic diagram of the interface provided in an embodiment of this application;

[0052] Figure 8 is a schematic diagram of the interface provided in an embodiment of this application;

[0053] Figure 9 is a schematic diagram of the interface provided in the embodiment of this application;

[0054] Figure 10 is a schematic diagram of the interface provided in the embodiment of this application;

[0055] Figure 11 is a schematic diagram of the interface provided in the embodiment of this application;

[0056] Figure 12 is a schematic diagram of the interface provided in an embodiment of this application;

[0057] Figure 13 is a schematic diagram of the interface provided in an embodiment of this application;

[0058] Figure 14 is a schematic diagram of the interface provided in an embodiment of this application;

[0059] Figure 15 is a timing diagram of information reception of an electronic device provided in an embodiment of this application;

[0060] Figure 16 is a schematic diagram of the interface provided in an embodiment of this application;

[0061] Figure 17 is a flowchart illustrating a cross-device resource sharing method provided in an embodiment of this application;

[0062] Figure 18 is a schematic diagram showing the execution order of each step in a cross-device resource sharing method provided in an embodiment of this application;

[0063] Figure 19 is a flowchart illustrating another cross-device resource sharing method provided in an embodiment of this application;

[0064] Figure 20 is a schematic diagram of the structure of another electronic device provided in an embodiment of this application;

[0065] Figure 21 is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0066] In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between the related objects, indicating that there can be three relationships. For example, A and / or B can mean: A exists alone, A and B exist simultaneously, and B exists alone. A and B can be singular or plural.

[0067] In the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, a and b, a and c, b and c, a and b and c, where a, b, and c can be single or multiple.

[0068] Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and the terms "first" and "second" are not necessarily different.

[0069] Cross-device resource sharing (also known as cross-platform resource sharing) refers to sharing resources from one electronic device to another. In one possible scenario, as shown in Figure 1(1), electronic device 10 displays image 100. The user can perform a three-finger touch screen pinch operation on image 100 to share image 100 with other electronic devices. In response to this operation, as shown in Figure 1(2), electronic device 10 can display a copy button 110. At the same time, as shown in Figure 1(3), electronic device 20 displays desktop 120. Then, the user can perform a three-finger touch screen release operation on desktop 120. In response to this operation and the aforementioned three-finger touch screen pinch operation performed on electronic device 10, electronic device 10 can send image 100 to electronic device 20, and correspondingly, electronic device 20 can receive the image from electronic device 10. Subsequently, as shown in Figure 1(4), electronic device 20 can display image 100, thereby enabling the sharing of resources from electronic device 10 to electronic device 20.

[0070] This solution requires users to use three fingers to touch the screen of the electronic device to share resources. However, in some scenarios, such as when users are working in the kitchen with wet fingers, they may not be able to perform the three-finger touch operation, thus preventing cross-device resource sharing. Furthermore, when electronic device 20 displays an interface other than the desktop (such as a video interface), users need to perform various touch operations first for electronic device 20 to display the desktop, making the resource sharing process lengthy. Therefore, this solution currently only supports electronic devices 10 and 20 when logged into the same system account, resulting in low convenience and intelligence in cross-device resource sharing.

[0071] In another possible solution, the electronic device can support air gestures, such as air swiping and air grabbing. For example, as shown in Figure 2(1), the electronic device can display the gallery application interface 200. The user can face the electronic device with their palm facing up and their fingertips pointing upwards, and then wave their wrist downwards. In response to this operation, the electronic device can swipe the screen downwards. Alternatively, as shown in Figure 2(2), the electronic device can display the gallery application interface 210. The user can face the back of their hand with their fingertips pointing downwards and then wave their wrist upwards. In response to this operation, the electronic device can swipe the screen upwards. Or, as shown in Figure 2(3), the electronic device can display the gallery application interface 220. The user can face the screen with their palm facing up and then grab and clench their fist. In response to this operation, the electronic device can generate a screenshot of interface 220. Although this solution can achieve air gestures on the electronic device, it cannot achieve cross-device resource sharing.

[0072] In another possible solution, two electronic devices can share contact information by probing each other using near-field communication (NFC) technology. As shown in Figure 3, contact information can be shared by simply touching the heads of electronic device 10 and electronic device 20 together. In this solution, different electronic devices need to touch their heads to share resources; in other words, resource sharing cannot be completed when the electronic devices are a certain distance apart, resulting in weaker convenience and intelligence.

[0073] Based on this, embodiments of this application provide a cross-device resource sharing method, which can improve the convenience and intelligence of cross-device resource sharing. The technical solution provided by embodiments of this application can be applied to various resource sharing scenarios. For example, the resource may include, but is not limited to, various resources such as pictures, videos, and news information.

[0074] For example, Figure 4 shows a schematic diagram of the architecture of a communication system for a cross-device resource sharing method provided in an embodiment of this application. As shown in Figure 4, the communication system 400 may include a first electronic device 401 and a second electronic device 402.

[0075] In some embodiments, the first electronic device 401 can act as a resource sender, sending resources to the second electronic device 402. The second electronic device 402 can act as a resource receiver, receiving resources from the first electronic device 401. In other embodiments, the second electronic device 402 can act as a resource sender, sending resources to the first electronic device 401. The first electronic device 401 can act as a resource receiver, receiving resources from the second electronic device 402. That is, the first electronic device 401 and the second electronic device 402 can act as both resource senders and resource receivers.

[0076] For example, the first electronic device 401 or the second electronic device 402 may include, but is not limited to, mobile phones, tablets, desktop computers, laptops, handheld computers, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, and various electronic devices such as personal digital assistants (PDAs), augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, wearable devices, in-vehicle devices, smart home devices, and / or smart city devices. Optionally, the first electronic device 401 and the second electronic device 402 may be fixed devices or portable devices. The first electronic device 401 and the second electronic device 402 may be the same type of electronic device or different types of electronic devices.

[0077] Optionally, the operating system installed on the first electronic device 401 or the second electronic device 402 may include, but is not limited to, the following: Or other operating systems.

[0078] Optionally, the first electronic device 401 and the second electronic device 402 may establish a connection via wireless communication technology. For example, wireless communication technology may include, but is not limited to, Bluetooth (BT) (e.g., classic Bluetooth or Bluetooth Low Energy (BLE) Bluetooth), Sparklink (e.g., classic Sparklink or Sparklink Low Energy (SLE)), and wireless local area networks (WLAN) (e.g., wireless fidelity (Wi-Fi) networks).

[0079] For example, Figure 5 shows a schematic diagram of the structure of an electronic device provided in an embodiment of this application. This electronic device can be either the first electronic device 401 or the second electronic device 402 described above. As shown in Figure 5, the electronic device 500 may include a processor 110, a memory 120, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, antenna 1, antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a sensor module 180, buttons 190, a camera 191, a display screen 192, etc.

[0080] Processor 110 may include one or more processing units, such as application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0081] The controller can generate operation control signals based on the instruction opcode and timing signals to complete the control of instruction fetching and execution.

[0082] The processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory can store instructions or data that the processor 110 has just used or that are used repeatedly. If the processor 110 needs to use the instruction or data again, it can retrieve it directly from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0083] In some embodiments, processor 110 may include one or more interfaces, such as USB interface 130.

[0084] The charging management module 140 receives charging input from the charger. While charging the battery 142, the charging management module 140 can also supply power to the electronic device through the power management module 141.

[0085] The power management module 141 is used 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, memory 120, display 192, and wireless communication module 160, etc.

[0086] The wireless communication function of electronic device 500 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor, and baseband processor.

[0087] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 500 can be used to cover one or more communication frequency bands. Different antennas can also be reused to improve antenna utilization.

[0088] The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for use in electronic devices 500.

[0089] The wireless communication module 160 can provide solutions for wireless communication applications on electronic devices 500, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), Starflash, global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies.

[0090] In some embodiments, antenna 1 of electronic device 500 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 500 to communicate with networks and other devices via wireless communication technology. The wireless communication technology 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, Starflash, GNSS, WLAN, NFC, FM, and / or IR technologies, etc.

[0091] In some embodiments of this application, taking electronic device 500 as a first electronic device 401 as an example, when the first electronic device 401 is a resource sender, the wireless communication module 160 can be used by electronic device 500 to send resources to second electronic device 402. When the first electronic device 401 is a resource receiver, the wireless communication module 160 can be used by electronic device 500 to receive resources shared by the second electronic device 402. Similarly, taking electronic device 500 as a second electronic device 402 as an example, when the second electronic device 402 is a resource sender, the wireless communication module 160 can be used by electronic device 500 to send resources to first electronic device 401. When the second electronic device 402 is a resource receiver, the wireless communication module 160 can be used by electronic device 500 to receive resources shared by first electronic device 401.

[0092] Electronic device 500 implements display functions through a GPU, display screen 192, and application processor. The GPU is a microprocessor for image processing, connected to the display screen 192 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0093] Display screen 192 is used to display images, videos, etc. Display screen 192 includes a display panel. In some embodiments, electronic device 500 may include one or N displays screens 192, where N is a positive integer greater than 1. In some embodiments of this application, the display screen 192 can be used to present at least one of the following: resources to be shared, various animations during cross-device resource sharing, etc. A description of the various animations presented during cross-device resource sharing can be found below.

[0094] Electronic device 500 can achieve shooting function through ISP, camera 191, video codec, GPU, display 192 and application processor.

[0095] Camera 191 is used to capture still images or videos. In some embodiments, electronic device 500 may include one or N cameras 191, where N is a positive integer greater than 1. In some embodiments of this application, camera 191 can be used to acquire images of the surroundings of electronic device 500. These images may or may not contain specific gestures for triggering cross-device resource sharing. If present, these gestures may be resource sending or receiving gestures, as described later. Camera 191 can identify the content in the image to detect the presence of specific gestures for triggering cross-device resource sharing, such as resource sending or receiving gestures, as described later. In some implementations, camera 191 can run in the background in real time to acquire images of the surroundings of electronic device 500 in real time to detect the presence of specific gestures for triggering cross-device resource sharing, so that electronic device 500 can promptly send resources to other electronic devices and respond to users' resource sharing requests. For an introduction to broadcast messages, please refer to the relevant descriptions below.

[0096] In this embodiment, an electronic device can function as both a resource sender and a resource receiver. Therefore, the electronic device can perform operations required when acting as a resource sender, and also operations required when acting as a resource receiver, such as, but not limited to, the aforementioned operation of activating the camera in real-time for specific gesture recognition.

[0097] In some embodiments, to reduce the power consumption of electronic devices performing real-time gesture recognition based on cameras, low-power cameras can be used. The gesture recognition module can be recessed into the lower layers of the operating system or into hardware (such as a SensorHub) within the system architecture. The recognition result is only reported when a specific gesture is recognized, thus waking up higher-level operating system modules for cross-device resource sharing. This way, only the low-power operating system or hardware modules need to remain operational in real-time to trigger the corresponding cross-device resource sharing function upon detecting a specific gesture.

[0098] The memory 120 can be used to store computer executable program code, which includes instructions. The memory 120 may include a program storage area and a data storage area. The program storage area may store the operating system, applications required for at least one function, etc. The data storage area may store data created during the use of the electronic device 500, etc. Furthermore, the memory 120 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the electronic device 500 by running instructions stored in the memory 120 and / or instructions stored in memory disposed within the processor.

[0099] Electronic device 500 can implement audio functions through audio module 170 and application processor, such as music playback and recording.

[0100] The sensor module 180 may include one or more sensors.

[0101] Buttons 190 include a power button, volume buttons, etc. Buttons 190 can be mechanical buttons or touch-sensitive buttons. Electronic device 500 can receive button input and generate key signal inputs related to user settings and function control of electronic device 500.

[0102] In some embodiments, the system architecture of the electronic device 500 shown in FIG5 can also adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture, etc. Taking a layered architecture as an example, FIG6 shows a schematic diagram of the structure of another electronic device 500 provided in an embodiment of this application. The layered architecture can be divided into several layers, each with a clear role and division of labor, and the layers communicate with each other through interfaces. As shown in FIG6, the electronic device 500 may include an application layer, a system service layer, and a hardware layer.

[0103] The application layer can include a series of application packages, such as system applications and third-party applications. For example, system applications may include, but are not limited to, gallery applications, file management applications, and screenshot applications, while third-party applications may include, but are not limited to, video applications, social applications, and shopping applications. It is understood that the applications included in the application layer can be programs with visual icons displayed on the electronic device's screen, such as gallery applications. They can also be programs or functions that run internally on the electronic device and are not visible to the user, such as screenshot applications.

[0104] In some embodiments of this application, one or more applications located at the application layer may integrate a sharing tool (ShareKit), such as gallery applications, screenshot applications, and video applications that integrate ShareKit. Alternatively, one or more applications located at the application layer may not integrate ShareKit, such as file manager applications, social applications, and shopping applications. It is understood that the applications with and without ShareKit shown in Figure 6 are merely illustrative examples. ShareKit is a library file that provides an application programming interface (API) for sharing, which can be used by the application to implement cross-device resource sharing.

[0105] When an application integrates ShareKit, it can register with the remote sharing service provided by the system service layer by accessing the sharing API provided by the integrated ShareKit, thereby realizing the cross-device resource sharing scheme described in the following embodiments.

[0106] When an application does not integrate ShareKit, in some implementations, it may be unable to implement the cross-device resource sharing scheme described in the following embodiments because it cannot register with the AirShare service provided by the system service layer. In other implementations, other applications that integrate ShareKit can assist in implementing the cross-device resource sharing scheme described in the following embodiments. For example, taking a screenshot application as an example, the screenshot application can register with the AirShare service provided by the system service layer by accessing the sharing API provided by the integrated ShareKit, and then share the resources of other applications with other electronic devices through the AirShare service via screenshots.

[0107] The system service layer can include a series of system services, such as the AirShare service and a distributed architecture foundation. The AirShare service provides applications registered with it on electronic devices with the ability to share their resources with other electronic devices. The AirShare service can support one or more of the following functions: for example, it can acquire and manage application registration events at the application layer and perform cross-device resource sharing processing based on these events. It is understood that when an application registers with the AirShare service, its registration event exists. Conversely, when an application is not registered with the AirShare service, its registration event does not exist.

[0108] The AirShare service can also interface with a distributed architecture platform to perform operations such as discovering electronic devices and storing communication messages between electronic devices (including but not limited to Bluetooth broadcast messages described below). This allows for the rapid transmission of data frames to other electronic devices. For example, in the case of Wi-Fi communication between electronic devices, this data frame can be an action frame. Action frames can be used to establish peer-to-peer connections between electronic devices. The AirShare service can also parse the sharing service identifier carried in communication messages between electronic devices (including but not limited to broadcast messages and action frames). This sharing service identifier can be used to identify whether the message is for cross-device resource sharing, enabling rapid connections between electronic devices.

[0109] The air sharing service can also have connection scheduling capabilities, such as supporting connection to the hardware layer recognition module to play various animations during cross-device resource sharing. It supports notifying the hardware layer recognition module after receiving a broadcast message (also known as a broadcast packet or broadcast frame) from the resource sender, thereby increasing the frequency or frame rate of recognizing specific gestures used to trigger cross-device resource sharing.

[0110] The remote sharing service also features development and feedback exchange (DFX) capabilities and performance tuning. DFX capabilities provide a range of tools and functions for developing, testing, and maintaining applications.

[0111] A distributed architecture platform provides communication capabilities for interconnectivity between electronic devices, enabling them to quickly discover and connect to other electronic devices and achieve connectivity adaptation between different electronic devices.

[0112] The hardware layer may include an identification module, Bluetooth, and Wi-Fi. The identification module can be used to identify specific gestures used to trigger cross-device resource sharing. In some embodiments, the identification module may be specifically implemented as a camera, which can periodically capture images of the surroundings of the electronic device 500 to detect the presence of specific gestures that trigger cross-device resource sharing. Optionally, in some implementations, the identification module can also identify specific gestures that trigger cross-device resource sharing when it detects that the electronic device 500 has enabled the cross-device resource sharing function.

[0113] It is understood that the structure of the electronic device 500 shown in Figure 6 is merely illustrative. In practical applications, it may include more or fewer modules, and the layers to which each module belongs may also differ. Other ways of dividing the layers are also possible, and this application does not impose any limitations on them.

[0114] It is also understood that the structures illustrated in Figures 5 and 6 do not constitute a specific limitation on the first electronic device 401 or the second electronic device 402. In other embodiments of this application, the first electronic device 401 or the second electronic device 402 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The processing steps or functional characteristics of the illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0115] The technical solutions involved in the following embodiments can all be implemented in devices with the structures shown in Figures 5 and 6, and in systems with the architecture shown in Figure 4. The following description uses a first electronic device 401 as the first electronic device and a second electronic device 402 as the second electronic device, taking the first electronic device as a resource sender and the second electronic device as a resource receiver as an example to introduce the technical solutions of the embodiments of this application.

[0116] This application provides a cross-device resource sharing method. After recognizing a gesture to trigger resource sending (hereinafter referred to as a resource sending gesture), a first electronic device can send an indication message to at least one other electronic device, indicating that the first electronic device is about to send its own resources. Correspondingly, the at least one electronic device can receive the indication message from the first electronic device. Then, after recognizing a gesture to trigger resource receiving (hereinafter referred to as a resource receiving gesture), a second electronic device among the at least one electronic device triggers a connection with the first electronic device. Based on this connection, the first electronic device can send its own resources to the second electronic device, and correspondingly, the second electronic device can receive the resources from the first electronic device, thereby realizing cross-device resource sharing.

[0117] Optionally, in this embodiment, the resource sending and receiving gestures can be gestures that do not touch the electronic device's display screen, i.e., air gestures. This allows users to share resources across devices without touching the screen. Even in scenarios where users' fingers are wet or unable to touch the screen, cross-device resource sharing is still possible. This improves the convenience and intelligence of cross-device resource sharing.

[0118] The cross-device resource sharing method provided in this application will be described below in conjunction with different cross-device resource sharing scenarios. In all the following scenarios, the resources shared by the first electronic device to the second electronic device are those displayed on the display screen of the first electronic device. These resources can be resources from any application installed on the first electronic device. Of course, in other scenarios, the resources shared by the first electronic device to the second electronic device can also be resources not displayed on the display screen of the first electronic device.

[0119] In some scenarios, the resources sent from the first electronic device to the second electronic device can be resources from applications registered with the AirShare service shown in Figure 6. These are resources from applications that can use AirShare to share resources across devices. Taking the registered application as a gallery application, the resources sent from the first electronic device to the second electronic device as images from the gallery application, and the first electronic device as electronic device 10 and the second electronic device as electronic device 20 as an example, the process of the first electronic device sharing images with the second electronic device will be described.

[0120] For example, as shown in Figure 7(1), the electronic device 10 can present an interface 700 of a gallery application (which can be used as an example of a first interface of a first application). The interface 700 is an interface that displays images in a large format. An image 701 (which can be used as an example of first content) is displayed in the interface 700. In some embodiments, the gallery application can use the AirShare service to share resources in the current interface when presenting any interface on the electronic device 10. That is, when the electronic device 10 presents any interface of the gallery application, it can send the resources included in that interface to other electronic devices. In other embodiments, the gallery application can only use the AirShare service to share resources in the current interface when presenting a specific interface on the electronic device 10, such as, but not limited to, the interface 700 shown in Figure 7(1). That is, the electronic device 10 can only send the resources included in that interface to other electronic devices when presenting a specific interface of the gallery application. Optionally, the gallery application can pre-set which interface it can use the AirShare service for. For the implementation of other applications, refer to the similar implementation of the gallery application here.

[0121] Next, when the electronic device 10 displays the interface 700 shown in Figure 7(1), the user can trigger the electronic device 10 to send an image 701 to the electronic device 20 by performing a resource sending gesture. If the electronic device 10 detects that the user has performed various resource sending gestures such as a palm-to-fist grab gesture, in response to the user's operation, it will start the operation of sending the image 701 to other electronic devices.

[0122] In some embodiments, the electronic device 10 can periodically perform gesture recognition in the background using the recognition module shown in FIG6. Taking a camera as an example, the electronic device 10 can periodically acquire images of its surroundings using the camera to identify whether a specific gesture used to trigger cross-device resource sharing exists based on the acquired images. This enables rapid recognition of specific gestures used to trigger cross-device resource sharing.

[0123] In some embodiments, since the sharing process of cross-device resources takes a certain amount of time, in order to avoid the user mistakenly believing that the electronic device 10 is not responding after performing a resource sending gesture, the electronic device 10 can display some cross-device resource sharing animations when it detects the resource sending gesture, so as to give the user a more intelligent perception experience of cross-device resource sharing.

[0124] For example, as shown in Figure 7(2), when the electronic device 10 detects a palm in the air grab gesture (which can be an example of a start gesture included in a resource sending gesture, used to indicate the start of the execution of the resource sending gesture), the electronic device 10 can present a palm icon 702 on the interface 700 (i.e., present the gesture icon corresponding to the start gesture included in the resource sending gesture), so that the user can confirm that the electronic device 10 has recognized the resource sending gesture based on the presented palm icon 702. Then, when the electronic device 10 continues to detect a fist in the air grab gesture, the electronic device 10 can present a pending animation effect as shown in Figure 7(3) (which can be an example of a first pending animation effect). Optionally, the pending animation effect can be composed of a light and shadow 711 and a card 712 obtained based on the image 701. For example, the light and shadow 711 can be a ring with a light and shadow display effect, and the card 712 includes a scaled-down image 701.

[0125] In some implementations, when the electronic device 10 detects a fist in the air grab gesture, it can display a fist icon on the interface 700, other interfaces of the gallery application, or the interface of other applications. The fist icon can be displayed in the same position as the palm icon 702 and have the same UI style as the palm icon 702 (for example, it can be shown as the fist icon 901 in Figure 9 (2)), so that the user can confirm that the electronic device 10 has recognized the resource sending gesture based on the presented fist icon. For example, the electronic device 10 can display the palm icon 702 when it detects a palm in the air grab gesture; if the electronic device 10 detects a fist in the air grab gesture again in the following period of time, it can change to displaying a fist icon. The fist icon can be displayed simultaneously with the light and shadow 711 and the card 712 on the same interface of the gallery application, or it can be displayed sequentially on different interfaces of the gallery application or the interface of different applications.

[0126] Optionally, when the electronic device 10 detects that the fist in the air grab gesture (which can be used as an example of an end gesture included in the resource sending gesture, which is used to indicate the end of the execution of the resource sending gesture) moves away from the front of the electronic device 10, the electronic device 10 can also present the gesture movement animation effect shown in Figure 7 (4). Optionally, the gesture movement animation effect can be composed of light and shadow 720 and card 712 obtained based on image 701, etc. The difference between the animation effect to be sent shown in Figure 7 (3) and the gesture movement animation effect shown in Figure 7 (4) is that the position of the light and shadow displayed on the electronic device 10 is different. Optionally, the light and shadow in the animation effect to be sent can move along the direction in which the fist in the air grab gesture moves away from the front of the electronic device 10, thereby generating the gesture movement animation effect. Figure 7 (4) is an example of the fist in the air grab gesture moving away from the right side of the screen of the electronic device 10. Optionally, when the fist in the air grab gesture is completely removed from the front of the electronic device 10, that is, when the electronic device 10 can no longer detect the fist in the air grab gesture, the light and shadow in the animation to be sent can be completely removed from the display screen of the electronic device 10. For example, the electronic device 10 can present the gesture movement animation as shown in Figure 7 (5), in which the light and shadow 720 can no longer be presented. The positions of the light and shadow 711 and 720 on the display screen of the electronic device 10 can change in real time with the real-time change of the position of the fist in the air grab gesture in front of the electronic device 10. Thus, the electronic device 10 can give the user the experience of the light and shadow 711 and 720 being remotely controlled by the user's fist, enhancing the technological feel of human-computer interaction and improving the user experience when the user uses the electronic device to share resources across devices.

[0127] In some embodiments, electronic device 10 may perform the operation of sending images to other electronic devices while presenting the interfaces shown in FIG. 7(2) to FIG. 7(4). Specifically, when electronic device 10 recognizes a palm-to-fist air grab gesture (i.e., detects a start gesture and an end gesture), it may send an instruction message to at least one other electronic device to indicate that electronic device 10 is about to send its own resources. Accordingly, the at least one other electronic device may receive the instruction message from electronic device 10. Then, electronic device 20 of the at least one other electronic device performs the operation of recognizing resource receiving gestures to determine whether to receive resources from electronic device 10. For example, when electronic device 20 detects that the user has performed various resource receiving gestures such as a fist-to-palm air release gesture, in response to the operation performed by the user, electronic device 20 begins to perform the operation of receiving images from electronic device 10.

[0128] It is understood that in this embodiment of the application, the resource sending gesture is a grasping gesture from palm to fist and the resource receiving gesture is a release gesture from fist to palm. In other embodiments, the resource sending gesture and the resource receiving gesture can also be other air gestures, such as a gesture of waving the palm to the right side of the screen and a gesture of waving the fist to the left side of the screen. This embodiment of the application does not limit this.

[0129] Similarly, in some embodiments, to facilitate timely recognition of specific gestures performed by the user to trigger cross-device resource sharing, the electronic device 20 can also periodically perform gesture recognition in the background using the recognition module shown in Figure 6. Taking a camera as an example, the electronic device 20 can periodically acquire images of its surroundings using the camera to identify whether a specific gesture for triggering cross-device resource sharing exists based on the acquired images. This allows for rapid recognition of specific gestures used to trigger cross-device resource sharing.

[0130] In this embodiment, in some implementations, to facilitate faster recognition of resource receiving gestures by electronic device 20 and to expedite resource sharing with electronic device 10, electronic device 20 can increase the frequency at which its recognition module recognizes resource receiving gestures after receiving an instruction message from electronic device 10. That is, the recognition frequency used by electronic device 20's recognition module before receiving the instruction message from electronic device 10 (which can be described as a first frequency) is lower than the recognition frequency used after receiving the instruction message from electronic device 10 (which can be described as a second frequency). For example, taking a camera as the recognition module, the frequency at which electronic device 20's camera captures surrounding images before receiving the instruction message from electronic device 10 can be lower than the frequency after receiving the instruction message from electronic device 10. In other words, the frame rate of the surrounding images captured by electronic device 20's camera before receiving the instruction message from electronic device 10 can be lower than the frame rate of the surrounding images captured after receiving the instruction message from electronic device 10. This allows for faster and more accurate recognition of resource receiving gestures, improving the efficiency of cross-device resource sharing and thus enhancing the intelligence of cross-device resource sharing.

[0131] In some embodiments, an electronic device can function as both a resource sender and a resource receiver. Therefore, if electronic device 20 can function as both a resource sender and a resource receiver, its recognition module can continuously perform gesture recognition operations in the background to facilitate timely recognition of both resource sending and receiving gestures. In other words, the purpose of electronic device 20 recognizing gestures through its recognition module before receiving an instruction message from electronic device 10 is to enable timely identification of both resource sending and receiving gestures.

[0132] In some embodiments, after an electronic device (such as electronic device 10, electronic device 20, etc.) enables the cross-device resource sharing function, in response to the activation of the cross-device resource sharing function, the electronic device can perform a gesture recognition operation in the background in real time through the recognition module, so as to be able to promptly recognize resource sending gestures and / or resource receiving gestures. As one possible implementation, the cross-device resource sharing function can be enabled by default after the electronic device leaves the factory. As another possible implementation, the cross-device resource sharing function can be enabled manually, such as by the user enabling the cross-device resource sharing function of the electronic device through various button operations, gesture operations, voice operations, etc. Taking the user enabling the cross-device resource sharing function through the settings application installed in the electronic device as an example, as shown in Figure 8 (1), the electronic device can present the settings application interface 800, in which the air transfer button 801 is displayed, and the user can enable or disable the cross-device resource sharing function of the electronic device through the air transfer button 801.

[0133] Similarly, in some embodiments, to avoid the user mistakenly believing that the electronic device 20 is not responding after performing a resource receiving gesture, the electronic device 20 may also display some cross-device resource sharing animations when it detects a resource receiving gesture, so as to give the user a more intelligent perception experience of cross-device resource sharing.

[0134] For example, as shown in Figure 9(1), the electronic device 20 can display a main interface 900 (or desktop 900). Then, when the electronic device 20 detects a fist in the air release gesture (which can be an example of a start gesture included in a resource receiving gesture, indicating the start of the resource receiving gesture execution), as shown in Figure 9(2), the electronic device 20 can present a fist icon 901 on the main interface 900, that is, present a gesture icon corresponding to the start gesture included in the resource receiving gesture, so that the user can confirm that the electronic device 20 has recognized the resource receiving gesture based on the presented fist icon 901. Optionally, when the electronic device 20 detects a fist in the air release gesture moving in front of the electronic device 20, it can also present a gesture movement animation as shown in Figure 9(2). Optionally, in this example, the gesture movement animation can be composed of light and shadow 902 as shown in Figure 9(2). For example, light and shadow 902 can be a ring with light and shadow display effects. It is understood that the effects of light and shadow are not limited in this embodiment. Optionally, as shown in Figure 9(2), the light and shadow 902 can move in the direction of the fist in the air release gesture moving from the front of the electronic device 20, thereby generating the gesture movement animation shown in Figure 9(2). Figure 9(2) is an example of the fist in the air release gesture moving from the left side of the screen of the electronic device 20. Optionally, when the fist in the air release gesture moves completely from the front of the electronic device 20, that is, when the electronic device 20 can detect the complete fist in the air release gesture, the light and shadow 902 can be fully presented on the electronic device 20, as shown in Figure 9(3). The position of the light and shadow 902 on the display screen of the electronic device 20 can change in real time with the real-time change of the position of the fist in the air release gesture in front of the electronic device 20. Thus, the electronic device 20 can give users the experience of the light and shadow 902 being remotely controlled by the user's fist, enhancing the technological feel of human-computer interaction and improving the user experience when users use electronic devices to share resources across devices.

[0135] In some embodiments, when the electronic device 20 further detects the palm in the air release gesture (which can be an example of an end gesture included in the resource receiving gesture, which can be used to indicate the end of the execution of the resource receiving gesture), the electronic device 20 can also present a light and shadow animation on the main interface 900. The light and shadow animation can be a light and shadow that gradually increases and then disappears. As shown in Figure 9 (3), the light and shadow 902 can gradually increase and be displayed on the display screen until it disappears from the display screen. Figure 9 (4) shows a schematic diagram of the effect after the light and shadow 902 increases.

[0136] In some implementations, when the electronic device 20 detects a palm in a gesture of air release, it can display a palm icon on the main interface 900 or the interface of other applications. This palm icon can be displayed in the same position as the fist icon 901 and have the same UI style as the fist icon 901 (for example, it can be the palm icon 702 shown in Figure 7 (2)), so that the user can confirm that the electronic device 20 has recognized the resource receiving gesture based on the displayed palm icon. For example, the electronic device 20 can display the fist icon 902 when it detects a fist in a gesture of air release. If the electronic device 20 detects a palm in a gesture of air release again in the following period of time, it can change to displaying a palm icon. The above palm icon can be displayed simultaneously with the light and shadow 902 on the same interface of the desktop application, or it can be displayed sequentially on different interfaces of the desktop application (such as the main screen, secondary screen, etc.) or the interface of different applications.

[0137] In some embodiments, during the process of sending image 701 to electronic device 20, electronic device 10 may also present a sending animation effect and / or electronic device 20 may also present a receiving animation effect. For example, the sending animation effect presented by electronic device 10 may be as shown in Figure 10 (1), wherein the sending animation effect may consist of a preview image 1002 (which can serve as an example of preview data for the first content) and light and shadow 1001. The receiving animation effect presented by electronic device 20 may be as shown in Figure 11 (1), wherein the receiving animation effect may consist of a preview image 1102 (which can serve as an example of preview data for the first content) and light and shadow 1101. The aforementioned preview image 1002 and preview image 1102 may be preview images of image 701. Optionally, preview image 1102 may be sent by electronic device 10 to electronic device 20. Light and shadow 1001 and light and shadow 1101 can be circular; preview images 1002 and 1102 can be circular, or shapes that match the shapes of light and shadow 1001 and 1101 respectively; preview images 1002 and 1102 can be displayed within light and shadow 1001 and 1101 respectively; preview images 1002 and 1102 can be cropped from image 701 according to the shapes of light and shadow 1001 and 1101 respectively. It is understood that this example uses the same sending animation effect presented by electronic device 10 and the same receiving animation effect presented by electronic device 20. In other examples, the sending animation effect presented by electronic device 10 and the receiving animation effect presented by electronic device 20 can also be different.

[0138] Optionally, in the sending animation shown in Figure 10(1), the black area outside the light and shadow 1001 can be transparent, and the electronic device 10 displays the interface content (such as the gallery interface) before the sending animation. Similarly, in the receiving animation shown in Figure 11(1), the black area outside the light and shadow 1101 can be transparent, and the electronic device 20 displays the interface content (such as the desktop) before the receiving animation.

[0139] Optionally, the electronic device 10 externally displayed by light and shadow 1001 displays the interface content before the sending animation, which can be presented in a blurred form; the electronic device 20 externally displayed by light and shadow 1101 displays the interface content before the receiving animation, which can also be presented in a blurred form. In contrast, preview images 1002 and 1102 are not blurred. This allows the user's attention to focus on preview images 1002 and 1102, making the user aware that data transmission is in progress and preventing the user from interrupting the process by performing other operations.

[0140] Optionally, preview images 1002 and 1102 can be presented in a blurred form; while the interface content displayed on electronic device 10 outside of light and shadow 1001 before the sending animation effect and the interface content displayed on electronic device 20 outside of light and shadow 1101 before the receiving animation effect are not blurred. Thus, the blurred preview images 1002 and 1102 allow the user to perceive that their corresponding image 701 is being transmitted, without affecting the user's ability to continue viewing other parts of the display interface of electronic devices 10 and 20.

[0141] Optionally, during the process of electronic device 10 sending images to electronic device 20, in order to facilitate the user's awareness of the resource sharing progress and to facilitate the user's performance of other operations on electronic device 10, electronic device 10 may also use a live capsule (which can be used as an example of a target control presented by the first electronic device) to present the sending progress. For example, electronic device 10 may automatically switch from presenting the sending animation shown in Figure 10(1) to presenting the live capsule 1010 shown in Figure 10(2). Similarly, in order to facilitate the user's performance of other operations on electronic device 20, electronic device 20 may also use a live capsule to present the receiving progress. For example, electronic device 20 may automatically switch from presenting the receiving animation shown in Figure 11(1) to presenting the live capsule 1110 shown in Figure 11(2). Of course, electronic device 10 and / or electronic device 20 may also choose not to present the aforementioned sending and receiving animations, but instead directly present a live capsule.

[0142] Optionally, in other embodiments, electronic device 10 and / or electronic device 20 may also use other controls (such as a floating ball) to display the sending progress and receiving progress respectively.

[0143] Optionally, the sending animation, which includes light and shadow 1001 and preview image 1002, can also change in real time according to the real-time change of the position of the fist in the air grab gesture in front of the electronic device 10, as shown in Figure 7 (3) and Figure 7 (4); the receiving animation, which includes light and shadow 1101 and preview image 1102, can also change in real time according to the real-time change of the position of the palm in the air release gesture in front of the electronic device 10, as shown in Figure 9 (2) and Figure 9 (3).

[0144] Optionally, after sharing image 701 between electronic device 10 and electronic device 20, electronic device 10 can return to interface 700 as shown in Figure 7(1), that is, return to the interface presented when receiving the resource sending gesture. Optionally, electronic device 20 can present the received image 701. For example, taking the electronic device 20 saving the received image to the gallery application as an example, as shown in Figure 11(3), electronic device 20 can present the gallery application interface 1120 as shown in Figure 11(3) to present the received image 701. Alternatively, electronic device 20 can also present the received image in the form of a floating window, allowing the user to drag the floating window to a specified application. Alternatively, electronic device 20 can also pop up a prompt window to ask the user whether to save the received image to electronic device 20, and the user can choose to save the received image to a specified application or directory of electronic device 20; and / or, ask the user which application to view the received image, and the user can view the received image with a specified application.

[0145] The example shown in Figure 9 illustrates how electronic device 20 receives an image shared by electronic device 10 while its desktop is displayed. Optionally, when electronic device 20 displays different interfaces before receiving the image shared by electronic device 10, it can process the received image differently, such as saving the image (as shown in Figure 11). Alternatively, it can send the image to others. For example, if electronic device 20 displays a chat interface with a friend before receiving the image shared by electronic device 10, it can directly send the received image to that chat interface to send it to its friend.

[0146] Based on the solution described above, after a user performs a gesture to grab a resource from the sending device, the sending device can send an indication message to the outside world to indicate that it is about to send resources. Then, upon receiving this indication message and a gesture to release the resource from the receiving device, the receiving device can receive the resources. Users do not need to touch the screen of their electronic devices, and there is no need for physical contact between the devices, making cross-device resource sharing more convenient and intelligent.

[0147] In other scenarios, the resources sent from the first electronic device to the second electronic device may be resources from applications not registered in the AirShare service shown in Figure 6, i.e., resources from applications that cannot use the AirShare service to achieve cross-device resource sharing. Taking the application not registered in the AirShare service as a desktop application, the first electronic device as electronic device 10, and the second electronic device as electronic device 20 as an example, the process of the first electronic device sharing resources with the second electronic device will be described. It is understood that this example uses an application not registered in the AirShare service shown in Figure 6 as a desktop application. In practical applications, this application not registered in the AirShare service shown in Figure 6 can also be various system applications (such as the file management application shown in Figure 6), third-party applications (such as social applications, shopping applications), etc.

[0148] It is understandable that the solution described in this scenario is also applicable to situations where an application that has registered with the AirShare service presents an interface that does not support AirShare (such as the second interface of the first application), but still receives a resource sending gesture executed by the user.

[0149] For example, as shown in Figure 12(1), the electronic device 10 can display a desktop 1200 (which can serve as an example of the interface of a second application), on which various UI elements such as icons of one or more applications and time controls are displayed. Then, with the desktop 1200 as shown in Figure 12(1) displayed on the electronic device 10, the user can perform a resource sending gesture, such as a palm-to-fist grab gesture. In response to this user's operation, the electronic device 10 can generate a screenshot of the desktop 1200. Simultaneously, the electronic device 10 begins the operation of sending the screenshot to other electronic devices. Specifically, the electronic device 10 can send an instruction message to at least one other electronic device to indicate that the electronic device 10 is about to send its own resources. Correspondingly, this at least one other electronic device can receive the instruction message from the electronic device 10. Then, the electronic device 20 among these at least one other electronic device performs an operation to recognize the resource receiving gesture to determine whether to receive resources from the electronic device 10. For example, when electronic device 20 detects that the user has performed various resource receiving gestures such as a fist-to-palm release gesture, electronic device 20 starts to receive screenshots from electronic device 10 in response to the user's operation.

[0150] In this scenario, the implementation of the electronic device 10 recognizing resource sending gestures and the electronic device 20 recognizing resource receiving gestures can refer to the implementation in the previous scenario.

[0151] Similarly, in this scenario, when electronic device 10 detects a resource sending gesture, and / or when electronic device 20 detects a resource receiving gesture, it can also present animations of cross-device resource sharing, so as to bring users a more intelligent perception experience of cross-device resource sharing.

[0152] For example, as shown in Figure 12(2), when the electronic device 10 detects a palm in the air grab gesture, the electronic device 10 can display a palm icon 1211 on the desktop 1200. When the electronic device 10 continues to detect a fist in the air grab gesture, the electronic device 10 can display a pending animation effect as shown in Figure 12(3) (which can be used as an example of a second pending animation effect). Optionally, the pending animation effect can be an animation effect that generates and displays a screenshot 1220 of the desktop 1200. Optionally, the pending animation effect can also display the light and shadow shown in Figure 7(3) (not shown in Figure 12(3)).

[0153] In some implementations, when the electronic device 10 detects a fist in the air grab gesture, it can display a fist icon on the desktop 1200 or other interfaces. This fist icon can be displayed in the same position as the palm icon 1211 and have the same UI style as the palm icon 1211 (for example, it can be shown as the fist icon 901 in Figure 9 (2)). This allows the user to confirm that the electronic device 10 has recognized the resource sending gesture based on the displayed fist icon. For example, the electronic device 10 can display the palm icon 1211 when it detects a palm in the air grab gesture; if the electronic device 10 detects a fist in the air grab gesture again in the following period of time, it can change to displaying a fist icon. The fist icon can be displayed simultaneously with the screenshot 1220 shown in Figure 12 (3) on the same interface of the desktop application, or it can be displayed sequentially on different interfaces of the desktop application or on the interfaces of different applications.

[0154] For example, when the electronic device 10 detects that the fist in the air grab gesture has moved away from the front of the electronic device 10, the electronic device 10 can also present the gesture movement animation as shown in Figure 12 (4). Optionally, the gesture movement animation can be composed of light and shadow 1230. Figure 12 (4) is an example of the fist in the air grab gesture moving away from the right side of the screen of the electronic device 10. For an introduction to light and shadow 1230, please refer to the introduction of light and shadow in the gesture movement animation shown in Figure 7 (4). The position of light and shadow 1230 displayed on the screen of the electronic device 10 can change in real time with the real-time change of the position of the fist in the air grab gesture in front of the electronic device 10. Thus, the electronic device 10 can give the user the experience of light and shadow 1230 being controlled by the user's fist in the air, enhance the technological feel of human-computer interaction, and improve the user experience when the user uses the electronic device to share resources across devices.

[0155] For example, electronic device 20 can display the main interface 900 as shown in Figure 9(1). Then, when electronic device 20 detects the fist in the air release gesture, as shown in Figure 9(2), electronic device 20 can display the fist icon 901 on the main interface 900.

[0156] For example, when the electronic device 20 detects the fist in the air release gesture moving in front of the electronic device 20, it can also present the gesture movement effect shown in Figure 9 (2). For example, when the electronic device 20 further detects the palm in the air release gesture, the electronic device 20 can also present light and shadow effects on the main interface 900.

[0157] Similarly, in this scenario, during the process of electronic device 10 sending screenshot 1220 to electronic device 20, electronic device 10 can also display a sending animation effect and / or electronic device 20 can also display a receiving animation effect. For example, the sending animation effect displayed by electronic device 10 can be as shown in Figure 13 (1). The sending animation effect can be composed of preview image 1302 and light and shadow 1301. The receiving animation effect displayed by electronic device 20 is shown in Figure 13 (2), and the receiving animation effect can be composed of preview image 1312 and light and shadow 1311. Among them, preview image 1312 and preview image 1302 can be preview images of screenshot 1220. For the animation effects of the sending animation effect shown in Figure 13 (1) and the receiving animation effect shown in Figure 13 (2), please refer to the corresponding description of the sending animation effect shown in Figure 10 and the receiving animation effect shown in Figure 11.

[0158] Similarly, in this scenario, during the process of electronic device 10 sending screenshot 1220 to electronic device 20, electronic device 10 can also automatically switch from displaying the sending animation as shown in Figure 13(1) to displaying a live capsule, such as electronic device 10 displaying an interface as shown in Figure 11(2). Electronic device 20 can also automatically switch from displaying the receiving animation as shown in Figure 13(2) to displaying a live capsule, such as electronic device 20 displaying an interface as shown in Figure 11(2).

[0159] Similarly, in this scenario, after the screenshot 1220 is shared between electronic device 10 and electronic device 20, electronic device 10 can return to the desktop 1200 as shown in Figure 12(1). Optionally, electronic device 20 can display the received screenshot 1220. For example, as shown in Figure 13(3), electronic device 20 can display the gallery application interface 1320 to display the received screenshot 1220.

[0160] Based on the solution described in this scenario, when an application (including but not limited to system applications and third-party applications) lacks the capability to share resources across devices using the AirShare service, cross-device resource sharing can be achieved through screenshots. After a user performs an AirShare gesture on the resource sender, the resource sender can send an indication message to the outside world to indicate that it is about to send the resource. When the resource receiver receives the indication message and the AirShare gesture, the resource sender can send a screenshot of the resource (such as the application's interface) to the resource receiver. This not only makes cross-device resource sharing more convenient and intelligent, but also ensures a good user experience even when the application does not use the AirShare service provided in this solution.

[0161] Optionally, in the above scenario, the system accounts (such as Huawei accounts) logged into by electronic device 10 and electronic device 20 can be the same or different. In some embodiments, when the system accounts logged into by electronic device 10 and electronic device 20 are different, a trust relationship can also be established between electronic device 10 and electronic device 20 to improve the security of cross-device resource sharing.

[0162] For example, when electronic device 20 receives a resource receiving gesture such as a fist-to-palm release gesture, in response to this operation, before receiving the shared resources from electronic device 10, electronic device 20 may remind the user whether to receive resources from electronic device 10 or whether to establish a trust relationship with electronic device 10. Optionally, electronic device 20 may remind the user whether to receive resources from electronic device 10 or whether to establish a trust relationship with electronic device 10 before, after, or simultaneously with the aforementioned cross-device resource sharing animation. For example, in conjunction with the scenario shown in FIG9, electronic device 20 may present a reminder message 1400 as shown in FIG14 (1), which displays a Trust and Receive button 1401, a Receive button 1402, and a Reject button 1403. Among them, the Trust and Receive button 1401 can be used by electronic device 20 to receive shared resources from electronic device 10 and establish a trust relationship with electronic device 10. The receive button 1402 can be used by electronic device 20 to receive the shared resources from electronic device 10, but without establishing a trust relationship with electronic device 10. The reject button 1403 can be used by electronic device 20 to refuse to receive the shared resources from electronic device 10.

[0163] For example, assuming a user performs an operation such as clicking the Trust and Receive button 1401 shown in Figure 14(1), in response to this operation, the electronic device 10 can remind the user whether to send resources to the electronic device 20 or to establish a trust relationship with the electronic device 20. For example, in conjunction with the scenario shown in Figure 7, the electronic device 10 can present a reminder message 1410 as shown in Figure 14(2), which displays a Trust and Send button 1411, a Send button 1412, and a Cancel button 1413. The Trust and Send button 1411 can be used by the electronic device 10 to send resources to the electronic device 20 and establish a trust relationship with the electronic device 20. The Send button 1412 can be used by the electronic device 10 to send resources but not to establish a trust relationship with the electronic device 20. The Cancel button 1413 can be used by the electronic device 10 to cancel sending resources. It is understood that the electronic device 10 has received the resource sending gesture before presenting the reminder message 1410 shown in Figure 14(2). In this way, the electronic device 10 displays a reminder message 1410, which facilitates the establishment of a trust relationship with the electronic device 20.

[0164] In this example, if the user performs an operation such as clicking the Trust and Send button 1411 shown in Figure 14(2), a trust relationship is established between electronic device 10 and electronic device 20 in response to this operation. Subsequently, when electronic device 10 and electronic device 20 share resources across devices, they can share resources directly. Electronic device 10 will no longer display the reminder message shown in Figure 14(2), and electronic device 20 will no longer display the reminder message shown in Figure 14(1). This makes cross-device resource sharing faster and more convenient. Conversely, if the user does not perform an operation such as clicking the Trust and Send button 1411 shown in Figure 14(2), but instead performs an operation such as clicking the Send button 1412 shown in Figure 14(2), then electronic device 10 and electronic device 20 will only share the resource for this time in response to this operation, and a trust relationship will not be established. Subsequently, when electronic devices 10 and 20 share resources across devices, electronic device 20 will still display the reminder message shown in Figure 14(1), and electronic device 20 will also display the reminder message shown in Figure 14(2) or the reminder message shown in Figure 14(3). In this way, the security of cross-device resource sharing can be further guaranteed.

[0165] For another example, suppose a user performs an operation such as clicking the receive button 1402 shown in Figure 14(1). In response to this operation, electronic device 10 can remind the user whether to send resources to electronic device 20. For example, electronic device 10 can display a reminder message 1420 as shown in Figure 14(3). The reminder message 1420 no longer displays the trust and send button, but only the send button 1421 and the cancel button 1422. For a description of the send button 1421 and the cancel button 1422, please refer to the corresponding descriptions of the send button 1412 and the cancel button 1413 shown in Figure 14(2). In this example, the user can perform an operation such as clicking the send button 1421 shown in Figure 14(3) to realize the sharing of resources between electronic device 10 and electronic device 20, but no trust relationship is established between electronic device 10 and electronic device 20. Subsequently, when electronic device 10 and electronic device 20 share resources across devices, electronic device 20 will still display the reminder message shown in Figure 14(1), and electronic device 10 will still display the reminder message shown in Figure 14(2) or the reminder message shown in Figure 14(3).

[0166] In some embodiments, after an electronic device establishes a trust relationship with other electronic devices through the methods described above, the electronic device can also notify the user of the electronic devices that have established a trust relationship with it. As a possible example, as shown in FIG8 (1), the electronic device can simultaneously display the identifiers of the electronic devices that have established a trust relationship with it on the interface 800, such as device 1, device 2, etc. Of course, the electronic device can also display the identifiers of the electronic devices that have established a trust relationship with it on other interfaces, and this application embodiment does not limit this.

[0167] In some embodiments, the user can also change the trust relationship between electronic devices, such as canceling the trust relationship between electronic devices. It is understood that when the trust relationship between electronic devices is canceled, when the electronic devices share resources again, a reminder message as shown in Figure 14 can be displayed. As shown in Figure 8 (1), when the electronic device displays the identifier of the electronic device with which it has established a trust relationship, it can also display a delete button 802 so that the user can change the established trust relationship. If the user performs an operation such as clicking the delete button 802 corresponding to device 1, the electronic device can cancel the trust relationship established with device 1 in response to the operation. Optionally, before successfully canceling the trust relationship established with device 1, the electronic device can also remind the user to confirm whether to cancel the trust relationship with device 1. For example, the electronic device can display a reminder message 810 as shown in Figure 8 (2), in which a delete button 811 and a cancel button 812 can be displayed. When the electronic device detects an operation such as the user clicking the delete button 811, it determines to cancel the trust relationship established with device 1 in response to the operation. Conversely, if the electronic device detects an action such as a user clicking the cancel button 812, it responds to the action by not terminating the trust relationship established with device 1.

[0168] Of course, when electronic devices 10 and 20 are logged into different system accounts, electronic device 10 can directly remind the user whether to send the resource before sending it, and / or electronic device 20 can directly remind the user whether to receive the resource before receiving it. In other words, electronic devices 10 and 20 can choose not to execute the aforementioned reminder to establish a trust relationship, thus ensuring the security of cross-device resource sharing.

[0169] The above describes the process of cross-device resource sharing in different scenarios. The above description assumes that there is one resource sender and one resource receiver.

[0170] In other embodiments, there may be one resource sender and multiple resource receivers. That is, resources sent by one electronic device can be simultaneously received by multiple other electronic devices (such as a first electronic device and a third electronic device). In this embodiment, each resource receiver can receive resources from the resource sender using the scheme described above, and the resource sender can send resources using the scheme described above.

[0171] In some embodiments, there can be multiple resource senders and only one resource receiver. Taking electronic device 10 and electronic device 30 as resource senders and electronic device 20 as the resource receiver, in this embodiment, resource receiver 20 may receive an indication message from electronic device 10 and an indication message from electronic device 30 (which can be considered an example of an indication message from a third electronic device). It is understood that the indication messages from electronic device 10 and electronic device 30 may be received simultaneously by electronic device 20, or they may be received sequentially by electronic device 20. Regardless of the order in which they are received, these indication messages are received before the resource receiving gesture. For example, taking the sequential receipt of the indication messages from electronic device 10 and electronic device 30 by electronic device 20 as an example, Figure 15 shows a timing diagram of information received by electronic device 20 according to an embodiment of this application. As shown in Figure 15, the indication message from electronic device 10 is received at time t1; in other words, electronic device 10 receives the resource sending gesture at time t1. The indication message from electronic device 30 is received at time t2; in other words, electronic device 30 receives the resource sending gesture at time t2. The resource receiving gesture is received at time t3. Among them, the indication message of electronic device 10 is received earliest, and the resource receiving gesture is received latest.

[0172] When electronic device 20 receives a resource receiving gesture from the user, in response to the gesture, electronic device 20 can determine which electronic device to receive the resource from based on preset rules. As one possible implementation, the preset rules may include: by default, only receiving resources from electronic devices with the same system account as electronic device 20. For example, assuming that the system account of electronic device 10 is the same as that of electronic device 20, while the system account of electronic device 30 is different from that of electronic device 20, then electronic device 20 can determine to receive resources from electronic device 10, but not from electronic device 30. Optionally, in this implementation, there may be one or more electronic devices with the same system account as electronic device 20. When multiple electronic devices exist, electronic device 20 can simultaneously receive resources from these electronic devices with the same system account.

[0173] As another possible implementation, the preset rule may include: determining which electronic device's resources to receive based on the user's selection. For example, the electronic device may remind the user that multiple electronic devices are currently sending resources, and ask the user to select which specific electronic device's resources to receive. For instance, electronic device 20 may display a reminder message 1600 as shown in Figure 16 for the user to make a selection. If the user chooses to receive resources from electronic device 10, they can perform a selection operation on the selection button 1601 of electronic device 10. In response to this operation, electronic device 20 can determine to receive resources from electronic device 10. If the user chooses to receive resources from electronic device 30, they can perform a selection operation on the selection button 1602 of electronic device 30. In response to this operation, electronic device 20 can determine to receive resources from electronic device 30. Optionally, in this implementation, the user can select one or more electronic devices; this embodiment does not limit this. Optionally, in this implementation, there may be an electronic device with the same system account as electronic device 20, or there may be no electronic device with the same system account as electronic device 20.

[0174] Optionally, the two implementations described above can be used individually or in combination. As one possible combination, if an electronic device with the same system account as electronic device 20 exists, electronic device 20 can use the first implementation to receive resources. If only electronic devices with different system accounts exist, electronic device 20 can use the second implementation to receive resources.

[0175] Of course, the preset rules can also be implemented as other rules, such as determining which electronic device's resources to receive based on the order in which the instruction messages are received. For example, the electronic device that receives the earliest instruction message can receive the resources, or the electronic device that receives the latest instruction message can receive the resources.

[0176] For other implementations of this embodiment, please refer to the implementations in the above scenario.

[0177] The above embodiments describe the implementation of an electronic device sending and receiving resources. In other embodiments, an electronic device can simultaneously send and receive resources. This allows for resource sharing between electronic devices. Taking electronic devices 10 and 20 as examples, both may simultaneously recognize resource sending and receiving gestures. For instance, a user can simultaneously perform a hand gesture (like a palm-to-fist grab) on both devices, and both devices can recognize this gesture. The user can then choose to perform a resource receiving gesture on one of the devices first, such as releasing the fist from the hand gesture. For example, if the user releases the fist from the hand gesture on device 10, device 10 can recognize the resource receiving gesture first. In response to the resource sending gesture received by device 20 and the resource receiving gesture received by device 10, device 20 sends resources to device 10, and device 10 receives resources from device 20. Optionally, during this process, the electronic device 10 may remind the user that a resource has been received while displaying the pending-send animation as shown in Figure 7 (3). For example, the electronic device 10 may also display resource receiving animations, such as the card 712 being compressed downwards and then springing back as shown in Figure 7 (3), to remind the user that the electronic device 10 has received a resource.

[0178] Furthermore, after electronic device 20 continues to receive resource receiving gestures from the user, it can continue to recognize resource receiving gestures. In response to the resource sending gesture received by electronic device 10 and the resource receiving gesture received by electronic device 20, electronic device 10 sends resources to electronic device 20, and electronic device 20 receives the resources from electronic device 10. Optionally, in this example, after electronic device 10 finishes sending resources to electronic device 20, the electronic device can display the resources received from electronic device 20 without returning to the interface before sending the resources. The implementation is similar when the user first performs a resource receiving gesture on electronic device 20.

[0179] Of course, the user can also simultaneously perform a fist-to-palm resource receiving gesture on both electronic devices, and both electronic devices 10 and 20 can simultaneously recognize this gesture. In response to the aforementioned resource sending and receiving gestures, electronic device 10 sends resources to electronic device 20 and simultaneously receives resources sent by electronic device 20. Electronic device 20 receives resources sent by electronic device 10 and simultaneously sends resources to electronic device 10. Alternatively, in other embodiments, the user can perform resource sending gestures sequentially on both electronic devices, but simultaneously perform resource receiving gestures on both devices, thus also enabling mutual resource transfer between the two electronic devices.

[0180] In some embodiments, the indication message sent by the first electronic device can be a broadcast message, which can be a Bluetooth broadcast message, a Wi-Fi broadcast message, or a Starlight broadcast message. Of course, other message types can also be used, such as Wi-Fi, NFC, Zigbee, Universal Serial Bus (USB), and cellular messages. When the first electronic device sends resources to the second electronic device, it can do so based on the established connection between the two. That is, after receiving the indication message from the first electronic device, the second electronic device can establish a connection with the first electronic device. For example, this connection can be a Wi-Fi connection; however, when using other communication protocols, other connections can also be used, such as Bluetooth or cellular connections.

[0181] The following embodiments use the example of a Bluetooth broadcast message sent by a first electronic device and a Wi-Fi connection established between a second electronic device and the first electronic device to describe the cross-device resource sharing method provided in this application. For example, Figure 17 shows a flowchart of a cross-device resource sharing method provided in this application. As shown in Figure 17, the method includes the following steps:

[0182] S1701, The first electronic device detects a grasping gesture from palm to fist.

[0183] In some embodiments, before executing step S1701, the first electronic device may display an application interface, such as the desktop 1200 shown in FIG12, the gallery application interface 700 shown in FIG7, etc. The air grab gesture can be used to share the resources included in the application interface with other electronic devices.

[0184] Optionally, the first electronic device may also execute step S1701a during the execution of step S1701.

[0185] S1701a, The first electronic device displays at least one of a hand icon, a gesture movement animation, and a pending sending animation.

[0186] For information on the presentation of the hand icon, gesture movement animation, and pending animation in step S1701a, please refer to the relevant description of the presentation of the electronic device 10 shown in Figure 7.

[0187] S1702, In response to the air grab gesture, the first electronic device sends a Bluetooth broadcast message. Correspondingly, the second electronic device can receive the Bluetooth broadcast message from the first electronic device.

[0188] Understandably, other electronic devices besides the second electronic device can also receive Bluetooth broadcast messages from the first electronic device.

[0189] The Bluetooth broadcast message includes an indication message that can be used to indicate that the first electronic device is about to send its own resources.

[0190] In some embodiments, since other electronic devices may be simultaneously sending Bluetooth broadcast messages, and these different Bluetooth broadcast messages may have different purposes—for example, the Bluetooth broadcast message from the first electronic device may be for cross-device resource sharing, while the Bluetooth broadcast messages from other electronic devices may be for audio connection or other purposes—to facilitate the identification of Bluetooth broadcast messages with different purposes, the Bluetooth broadcast message may also carry a cross-device resource sharing service identifier. This service identifier can be used to characterize that the Bluetooth broadcast message is a broadcast message used to achieve cross-device resource sharing.

[0191] Optionally, in the embodiments of this application, the first electronic device may use a low-power mode, such as low-power Bluetooth mode or low-power star flash mode, when sending broadcast messages to the outside world, so as to reduce the power consumption of the first electronic device.

[0192] Optionally, the presentation of gesture movement animation and the animation to be sent can be executed simultaneously or sequentially with step S1702.

[0193] S1703, The second electronic device detects a release gesture from fist to palm.

[0194] Optionally, the second electronic device may display any application interface before executing step S1703, or it may display a screen-off interface, a screen-locked interface, etc.

[0195] Optionally, the second electronic device may also execute step S1703a during the execution of step S1703.

[0196] S1703a, The second electronic device displays at least one of the following: a fist icon, a gesture movement effect, and a light and shadow effect.

[0197] For information on the presentation of the fist icon, gesture movement animation, and light and shadow animation in step S1703a, please refer to the relevant introduction when the electronic device 20 is presented as shown in Figure 9.

[0198] S1704. In response to the air release gesture, the second electronic device sends a Wi-Fi action frame to the first electronic device based on a Bluetooth broadcast message.

[0199] The Wi-Fi action frame can be used to establish a Wi-Fi connection between the first electronic device and the second electronic device.

[0200] Similarly, in some embodiments, since different Wi-Fi action frames may have different purposes, in order to facilitate the identification of Wi-Fi action frames with different purposes, the Wi-Fi action frames may also carry the aforementioned cross-end resource sharing service identifier.

[0201] S1705, The first electronic device establishes a connection with the second electronic device based on the Wi-Fi action frame.

[0202] It is understood that in this embodiment of the application, the broadcast message sent by the first electronic device and the connection established between the first electronic device and the second electronic device are implemented based on different communication protocols. In other embodiments, the broadcast message sent by the first electronic device and the connection established between the first electronic device and the second electronic device can also be implemented based on the same communication protocol, such as Wi-Fi.

[0203] It is also understandable that steps S1704 and S1705 are based on the example of the second electronic device first sending a Wi-Fi action frame to the first electronic device, and then the first electronic device establishing a connection with the second electronic device based on the Wi-Fi action frame. In other implementations, the second electronic device can directly establish a connection with the first electronic device in response to a gesture, that is, it is not necessary to send a Wi-Fi action frame to the first electronic device again, so step S1704 can be an optional step. Accordingly, S1705 is changed to: the first electronic device establishes a connection with the second electronic device based on an instruction message.

[0204] S1706, The first electronic device sends resources to the second electronic device based on the established connection. Correspondingly, the second electronic device receives resources from the first electronic device based on the established connection.

[0205] Optionally, the resource can be the resource included in the application interface presented by the first electronic device before executing step S1701, such as the image in the scene shown in Figure 7, or the screenshot in the scene shown in Figure 12.

[0206] In some embodiments, during the execution of step S1706, the first electronic device may also display a sending animation, and the second electronic device may also display a receiving animation. Optionally, the receiving animation can be generated based on preview data of the resources sent by the first electronic device to the second electronic device. This preview data can be a preview image as described in the above scenario; of course, the preview data can also be other types of data. In this implementation, in order for the second electronic device to display the receiving animation, the first electronic device also needs to perform the operation of generating preview data and sending the preview data to the second electronic device.

[0207] In this embodiment, as one possible implementation, as shown in FIG18(1), the first electronic device may perform the operation of generating preview data after step S1704, and then perform step S1705. Optionally, as shown in FIG18(1), the process of establishing a connection in step S1705 may include the process of establishing a physical connection and the process of establishing a session connection. Then, after performing step S1705, the first electronic device may perform the operation of sending preview data to the second electronic device, and then perform step S1706. Correspondingly, the second electronic device may perform step S1705 after performing step S1704. After performing step S1705, it may perform the operation of receiving preview data, and then perform step S1706. Optionally, the first electronic device may also present the above-mentioned live capsule during the execution of step S1706. Similarly, the second electronic device may also present the above-mentioned live capsule during the execution of step S1706.

[0208] In the above implementation, after the second electronic device receives the air release gesture, the second electronic device sends a Wi-Fi action frame (i.e., step S1704), and the first electronic device performs operations such as generating preview data, establishing a connection (i.e., step S1705), and sending preview data. Among these operations, sending the Wi-Fi action frame to the first electronic device takes approximately 50 milliseconds (ms), generating the preview data takes approximately 510 ms, establishing the connection takes approximately 950 ms, and sending the preview data takes approximately 40 ms. Therefore, before the second electronic device receives the resources from the first electronic device, as shown in Figure 18 (1), the user-perceived latency is approximately 1.7 seconds (s). This relatively long latency is detrimental to the user experience.

[0209] Therefore, to address the aforementioned issue of delayed user perception, as another possible implementation, as shown in Figure 18(2), the first electronic device can perform the operation of generating preview data during the execution of step S1701, such as when detecting the start gesture in the resource sending gesture, i.e., perform the operation of generating preview data in advance. And / or, the second electronic device can also perform the process of establishing a connection with the first electronic device during the process of recognizing the air release gesture, i.e., perform the operation of establishing a connection in advance. As shown in Figure 18(2), the second electronic device can perform steps S1704 and S1705 when receiving the fist in the air release gesture, i.e., when detecting the start gesture in the resource receiving gesture, establish a communication connection with the first electronic device. After performing step S1705, and when the second electronic device receives the palm in the air release gesture, the first electronic device can perform the operation of sending preview data to the second electronic device, and then perform step S1706. Correspondingly, after performing step S1705, and when receiving the palm in the air release gesture, the second electronic device can perform the operation of receiving preview data based on the communication connection with the first electronic device, and then perform step S1706. Similarly, in this implementation, the first electronic device can also present the aforementioned live capsule during the execution of step S1706. Likewise, the second electronic device can also present the aforementioned live capsule during the execution of step S1706.

[0210] In this implementation, after receiving the air release gesture, the second electronic device only needs to perform the operation of sending preview data. Therefore, before the second electronic device receives the resources from the first electronic device, there is only a perceived delay in transmitting preview data, which can greatly reduce the perceived delay for users and improve the user experience.

[0211] Optionally, in this implementation, the operations of generating preview data in advance and establishing connections in advance can be used separately or simultaneously. However, regardless of which method is used, compared to the previous implementation, both can reduce the perceived latency for users and improve the user experience.

[0212] It is understandable that the descriptions of each step shown in Figure 18 can refer to the descriptions of the corresponding steps shown in Figure 17.

[0213] For example, combining the architecture shown in Figure 6 and the scenario of sharing images in a gallery application shown in Figure 7, etc., and still taking electronic device 10 as the resource sender and electronic device 20 as the resource receiver as an example, Figure 19 shows a flowchart of another cross-device resource sharing method provided in this application embodiment. It can be understood that, for ease of distinction, modules with the same function in different electronic devices are represented by different serial numbers in Figure 19, such as AirShare Service 1, AirShare Service 2, etc. It can also be understood that User 1 and User 2 can be users of electronic device 10 and electronic device 20, respectively. As shown in Figure 19, the method includes the following steps:

[0214] S1901, the gallery application 1 in the electronic device 10 senses the interface 700.

[0215] Among them, interface 700 is the interface shown in Figure 7(1).

[0216] S1902, Gallery Application 1 is connected to the sharing API of the sharing tool.

[0217] S1903, Gallery application 1 is registered to the remote sharing service 1 of electronic device 10.

[0218] In this case, Gallery Application 1 can perform the registration using the sharing API in step S1902.

[0219] It is understood that steps S1901 to S1903 are executed only when the gallery application 1 presents a specific interface (here, interface 700 shown in Figure 7(1)). In other words, when the gallery application 1 presents a non-specific interface, steps S1902 to S1903 may not be executed.

[0220] Based on steps S1901 to S1903, when the gallery application presents a certain interface, it performs the operation of registering with the AirShare service, that is, registering with the AirShare service in real time. This makes it easy for the gallery application to unregister from the AirShare service when it exits the presentation of the interface, so as to support cross-device sharing of resources in certain specific interfaces supported by the gallery application.

[0221] S1904. The remote sharing service 1 refreshes the registration status of the gallery application 1 in the recognition module 1.

[0222] Step S1904 can also be described as storing the registration event of the gallery application 1 to indicate that the gallery application 1 has registered with the AirShare service 1. Optionally, the registration event of the gallery application 1 can be stored in the AirShare service 1 or in the recognition module 1.

[0223] S1905, The recognition module 1 recognizes the palm and displays a palm icon.

[0224] For example, the hand icon can be the hand icon 702 shown in Figure 7 (2).

[0225] S1906. The remote sharing service 1 receives the event reported by the identification module 1 and generates at least one of the following: a motion effect to be sent and a sending motion effect.

[0226] This event can be used to notify the AirShare service 1 that a palm has been detected.

[0227] Based on step S1906, when a hand is detected, at least one of the following is generated: a motion effect to be sent and a motion effect to be sent. This data is prepared in advance, which makes it easier to play these motion effects in a timely manner and reduces the perceived latency for the user.

[0228] S1907, Recognition module 1 recognizes that the palm has become a fist.

[0229] In step S1907, the recognition module 1 can also report an event to the AirShare service 1. This event can be used to notify the AirShare service 1 that a palm has been recognized.

[0230] S1908, Remote sharing service 1 determines whether the gallery application 1 has been registered.

[0231] If not registered, proceed to steps S1909 to S1912. If already registered, proceed to step S1913.

[0232] S1909, Remote sharing service 1 reports information to screenshot application 1.

[0233] The reported information can be used to indicate that the gallery application 1 is not registered with the AirShare service 1. Optionally, the reported information can also be used to indicate whether the electronic device 10 has enabled cross-device resource sharing functionality.

[0234] S1910, Screenshot application 1 is integrated into the sharing API of the sharing tool.

[0235] S1911, Screenshot application 1 registers with AirShare service 1.

[0236] In this case, the screenshot application 1 can use the sharing API in step S1911 to perform the registration.

[0237] S1912. The remote sharing service 1 obtains and stores a uniform resource identifier (URI) from the screenshot application 1.

[0238] The URI can be the URI of the resource to be shared by the screenshot application 1, such as the URI of the screenshot generated by the screenshot application 1, like the URI of screenshot 1220 in the scenario shown in Figure 12. Of course, in this embodiment, the URI can also be other identifiers or information to facilitate the remote sharing service 1 in obtaining the resource to be shared.

[0239] It is understood that steps S1908 to S1911 are executed when the gallery application 1 is not registered with the air sharing service 1. In other embodiments, steps S1908 to S1911 can always be executed, that is, steps S1908 to S1911 can be executed regardless of whether the gallery application 1 is registered with the air sharing service 1. In this embodiment, the reporting information in step S1909 can also be used to indicate whether the gallery application 1 is registered with the air sharing service 1. Subsequently, the air sharing service 1 can determine where to obtain the URI based on whether the gallery application 1 has been registered. For example, if the air sharing service 1 determines that the gallery application 1 has been registered, the air sharing service 1 can execute step S1913. Conversely, if the air sharing service 1 determines that the gallery application 1 is not registered, the air sharing service 1 can execute step S1912.

[0240] S1913, Remote sharing service 1 obtains and stores the URI from gallery application 1.

[0241] The URI can be the URI of the resource to be shared by the gallery application 1. For example, in conjunction with step S1901, the URI can be the URI of image 701 as shown in Figure 7 (1).

[0242] S1914, Remote sharing service 1 presents a pending animation to user 1.

[0243] For example, when the screenshot application 1 has registered with the AirShare service, the pending send animation can be as shown in Figure 7 (3). When the screenshot application 1 has not registered with the AirShare service, the pending send animation can be as shown in Figure 12 (3).

[0244] Optionally, before presenting the animation to be sent, the remote sharing service 1 can also present the gesture movement animation shown in Figure 7 (4) or the gesture movement animation shown in Figure 12 (4).

[0245] S1915, AirShare service 1 obtains the Wi-Fi listening channel through the distributed architecture base 1, starts listening based on the Wi-Fi listening channel, and sends Bluetooth broadcast messages. Correspondingly, AirShare service 2 in electronic device 20 can receive Bluetooth broadcast messages based on the distributed architecture base 2.

[0246] The Wi-Fi listening channel can be used to listen for Wi-Fi action frames. A description of this Bluetooth broadcast message can be found in step S1704 shown in Figure 17.

[0247] S1916. AirShare Service 2 stores Bluetooth broadcast messages and notifies Identification Module 2 that it has received Bluetooth broadcast messages.

[0248] Optionally, since electronic device 2 may receive multiple Bluetooth broadcast messages at the same time, that is, there may be multiple resource senders at the same time, AirShare service 2 stores the Bluetooth broadcast messages to facilitate subsequent determination of which resource sender the resource was received from.

[0249] S1917, Identification module 2 increases the frequency of identifying resource receiving gestures.

[0250] For an introduction on how the recognition module 2 increases the frequency of receiving recognition resource gestures, please refer to the above description.

[0251] S1918, the recognition module 2 recognizes the fist and presents at least one of the fist icon and gesture movement animation through the air sharing service 2.

[0252] In this step, the fist icon can be the fist icon 901 shown in Figure 9 (2), and the gesture movement effect can be the gesture movement effect shown in Figure 9 (1).

[0253] S1919, the recognition module 2 recognizes that the fist has turned into a palm, and presents light and shadow effects through the air sharing service 2.

[0254] The lighting and shadow effects can be referenced from the lighting and shadow effects described above.

[0255] S1920, AirShare Service 2 sends a Wi-Fi action frame to AirShare Service 1 through Distributed Architecture Base 2. Correspondingly, AirShare Service 1 receives the Wi-Fi action frame through Distributed Architecture Base 1.

[0256] Optionally, AirShare 2 can immediately respond with a Wi-Fi action frame after receiving a Bluetooth broadcast message, enabling it to quickly establish a connection with electronic device 10.

[0257] In some scenarios, the AirShare service 2 may fail to send a Wi-Fi action frame to the AirShare service 1 via the distributed architecture base 2. In order to ensure the probability of a successful reply, the AirShare service 2 can reply with a Wi-Fi action frame again after receiving the next Bluetooth broadcast message, so as to establish a connection with the electronic device 10.

[0258] S1921. AirShare Service 1 and AirShare Service 2 establish a Wi-Fi connection.

[0259] S1922, AirShare Service 1 sends resources to AirShare Service 2 based on the URI of the Wi-Fi connection and storage. Correspondingly, AirShare Service 2 receives resources from AirShare Service 1.

[0260] Optionally, in conjunction with the scenario shown in Figure 11, the method shown in Figure 19 may also include step S1923.

[0261] S1923, Remote sharing service 2 presents resources through gallery application 2.

[0262] S1924, Gallery Application 1 detects exit interface 700.

[0263] S1925, Gallery app 1 is deregistered from AirShare service 1.

[0264] It is understandable that the process shown in Figure 19 is based on the example of not establishing a connection in advance. The same applies to the solution of establishing a connection in advance shown in Figure 17, as well as the presentation of various animation effects shown in Figure 17. The processes shown in Figure 19 and Figure 17 can be used for reference. To avoid redundancy, the solutions already introduced in the process shown in Figure 17, such as generating preview data in advance, will not be introduced in the process shown in Figure 19.

[0265] It is understood that the solution described in this application embodiment is based on a resource sharing scenario, and the solution provided in this application embodiment can be applied to various scenarios such as screen projection, cross-device copying, and cross-device collaboration.

[0266] The above primarily describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Based on the units and algorithm steps of the various examples described in the embodiments disclosed in this application, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by a computer driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solutions of the embodiments of this application.

[0267] This application provides embodiments for dividing an electronic device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into a single processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the unit division in this application embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0268] Figure 20 shows a schematic diagram of an electronic device provided in an embodiment of this application. The electronic device 2000 can be used to implement the methods executed by the electronic devices described in the above method embodiments. For example, the electronic device 2000 may include a processing unit 2001, a communication unit 2002, and a display unit 2003.

[0269] As a possible example, taking electronic device 2000 as the first electronic device, the processing unit 2001 is used to support electronic device 2000 in performing the processing function of the first electronic device as described in any one of Figures 1 to 19; the communication unit 2002 is used to support electronic device 2000 in performing the communication function of the first electronic device as described in any one of Figures 1 to 19; and the display unit 2003 is used to support electronic device 2000 in performing the display function of the first electronic device as described in any one of Figures 1 to 19.

[0270] As another possible example, taking electronic device 2000 as a second electronic device, the processing unit 2001 is used to support electronic device 2000 in performing the processing function of the second electronic device as described in any one of Figures 1 to 19; the communication unit 2002 is used to support electronic device 2000 in performing the communication function of the second electronic device as described in any one of Figures 1 to 19; and the display unit 2003 is used to support electronic device 2000 in performing the display function of the second electronic device as described in any one of Figures 1 to 19.

[0271] Optionally, the electronic device 2000 shown in FIG20 may further include a storage unit (not shown in FIG20) storing a program or instructions. When the processing unit 2001 executes the program or instructions, the electronic device 2000 shown in FIG20 can perform the method described in the above-described method embodiments.

[0272] The technical effects of the electronic device 2000 shown in Figure 20 can be referred to the technical effects described in the above method embodiments, and will not be repeated here. The processing unit 2001 involved in the electronic device 2000 shown in Figure 20 can be implemented by a processor or processor-related circuit components, and can be a processor or processing module. The communication unit 2002 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver module. The display unit 2003 can be implemented by display screen-related components.

[0273] This application also provides a chip system, as shown in FIG21, which includes at least one processor 2101 and at least one interface circuit 2102. The processor 2101 and the interface circuit 2102 are interconnected via lines. For example, the interface circuit 2102 can be used to receive signals from other devices. As another example, the interface circuit 2102 can be used to send signals to other devices (e.g., the processor 2101). Exemplarily, the interface circuit 2102 can read instructions stored in a memory and send the instructions to the processor 2101. When the instructions are executed by the processor 2101, the electronic device can perform the various steps performed by the electronic device in the above embodiments. Of course, the chip system may also include other discrete devices, which are not specifically limited in this application.

[0274] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0275] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0276] For example, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0277] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0278] This application also provides a computer storage medium storing computer instructions, which, when executed on an electronic device, cause the electronic device to perform the methods described in the above-described method embodiments.

[0279] This application provides a computer program product, which includes a computer program or instructions that, when run on a computer, cause the computer to perform the methods described in the above-described method embodiments.

[0280] In addition, this application also provides an apparatus, which may specifically be a chip, component or module. The apparatus may include a connected processor and a memory. The memory is used to store computer execution instructions. When the apparatus is running, the processor can execute the computer execution instructions stored in the memory to cause the apparatus to perform the methods in the above-described method embodiments.

[0281] In this embodiment, the electronic device, computer storage medium, computer program product or chip are all used to execute the corresponding method provided above. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding method provided above, and will not be repeated here.

[0282] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0283] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The embodiments can be combined with or referenced to each other without conflict. The apparatus embodiments described above are merely illustrative; for example, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0284] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0285] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0286] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, in essence, or the parts that contribute to the prior art, or all or part of the technical solutions, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0287] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

A cross-device resource sharing method, characterized in that, The method is applied to a first electronic device with a display screen, and the method comprises: In response to a detected resource sending gesture, sending an indication message to at least one electronic device while displaying a first interface of a first application, wherein the first interface displays first content, the resource sending gesture is used to indicate that the first electronic device shares resources with other electronic devices, the resource sending gesture is a gesture that is not in contact with the display screen of the first electronic device, and the indication message is used to indicate that the first electronic device is about to share resources; Based on a communication connection with a second electronic device of the at least one electronic device, sending the first content to the second electronic device. The method of claim 1, wherein The method further comprises: In response to a detected resource sending gesture, sending the indication message to at least one electronic device while displaying a second interface of the first application, wherein the second interface is different from the first interface; Based on a communication connection with a second electronic device of the at least one electronic device, sending a screenshot of the second interface to the second electronic device. The method according to claim 1 or 2, characterized in that The method further comprises: In response to a detected resource sending gesture, sending the indication message to at least one electronic device while displaying an interface of a second application, wherein the second application is different from the first application; Based on a communication connection with a second electronic device of the at least one electronic device, sending a screenshot of the interface to the second electronic device. The method according to any one of claims 1-3, characterized in that The sending of the first content to the second electronic device based on the communication connection with the second electronic device of the at least one electronic device comprises: Based on a communication connection with a second electronic device of the at least one electronic device, sending the first content to the second electronic device, and based on a communication connection with a third electronic device of the at least one electronic device, sending the first content to the third electronic device. The method according to any one of claims 1-4, characterized in that The sending of the first content to the second electronic device based on the communication connection with the second electronic device of the at least one electronic device comprises: Based on the indication message, establishing a communication connection with the second electronic device; Based on the communication connection, sending the first content to the second electronic device. The method according to claim 5, characterized in that The resource sending gesture comprises a start gesture and an end gesture, the start gesture indicates the start of the execution of the resource sending gesture, and the end gesture indicates the end of the execution of the resource sending gesture; Before the sending of the first content to the second electronic device based on the communication connection, the method further comprises: When the start gesture is detected, generating preview data of the first content; Based on the communication connection, sending the preview data of the first content to the second electronic device. The method according to claim 6, characterized in that The sending of the indication message to at least one electronic device in response to a detected resource sending gesture comprises: In response to the detection of the start gesture and the end gesture, sending the indication message to the at least one electronic device. The method according to claim 6 or 7, characterized in that The method further comprises: When the start gesture is detected, displaying a gesture icon corresponding to the start gesture; Or, when detecting that the end gesture moves out from the front of the first electronic device, display a gesture movement effect, the gesture movement effect comprising a light and shadow moving effect on the display screen. The method of claim 8, wherein The direction of the light and shadow moving on the display screen is the same as the direction of the end gesture moving out from the front of the first electronic device. The method according to any one of claims 1-9, characterized in that After detecting the resource sending gesture, the method further comprises: displaying a first to-be-sent effect, the first to-be-sent effect comprising at least one of a card and a light and shadow generated based on the first content. The method according to any one of claims 1-10, characterized in that During the process of sending the first content to the second electronic device, the method further comprises: displaying a sending effect, the sending effect comprising at least one of preview data of the first content and a light and shadow; And / or, displaying a target control for indicating the sending progress of the first content. The method according to any one of claims 2-11, characterized in that After detecting the resource sending gesture, the method further comprises: displaying a second to-be-sent effect, the second to-be-sent effect comprising at least one of a screenshot of the second interface and a light and shadow. The method according to any one of claims 1-12, characterized in that The first electronic device and the second electronic device log in to different system accounts, and before the first electronic device sends the first content to the second electronic device, the method further comprises: In the case that the first electronic device and the second electronic device have not established a trust relationship, displaying a prompt message for prompting the user to confirm at least one of whether to send the first content to the second electronic device or whether to establish a trust relationship with the second electronic device; Or, in the case that the first electronic device and the second electronic device have established a trust relationship, not displaying a prompt message for prompting the user to confirm at least one of whether to send the first content to the second electronic device or whether to establish a trust relationship with the second electronic device. The method according to claim 2 or 3, characterized in that The first electronic device comprises an air-sharing service, the air-sharing service being configured to provide a function of sharing resources of an application registered to the air-sharing service in the first electronic device to other electronic devices for the application; The first application is an application registered to the air-sharing service, a first interface of the first application is a preset interface capable of using the air-sharing service, and a second interface of the first application is a preset interface incapable of using the air-sharing service; or, the second application is an application not registered to the air-sharing service. The method according to any one of claims 1-14, characterized in that The resource sending gesture comprises a gesture of changing from a palm to a fist. A cross-device resource sharing method, characterized in that, Applied to a second electronic device with a display screen, the method comprises: receiving an indication message from a first electronic device, the indication message of the first electronic device being configured to indicate that the first electronic device is about to share resources; in response to the indication message of the first electronic device and a detected resource receiving gesture, receiving first content from the first electronic device based on a communication connection between the first electronic device and the second electronic device, wherein the resource receiving gesture is a gesture not in contact with the display screen of the second electronic device, and the first content is content in a first interface of a first application displayed by the first electronic device. The method of claim 16, wherein The method further comprises: In response to the indication message of the first electronic device and the detected resource receiving gesture, a screenshot of a second interface of the first electronic device is received based on the communication connection between the first electronic device, the screenshot of the second interface being a screenshot of a second interface of the first application displayed by the first electronic device, the second interface being different from the first interface. The method according to claim 16 or 17, characterized in that The method further includes: In response to the indication message of the first electronic device and the detected resource receiving gesture, a screenshot of an interface of the first electronic device is received based on the communication connection between the first electronic device, the screenshot of the interface being a screenshot of an interface of a second application displayed by the first electronic device, the second application being different from the first application. The method according to any one of claims 16-18, characterized in that Before the first content from the first electronic device is received, the method further includes: An indication message of a third electronic device is received, the indication message of the third electronic device being used to indicate that the third electronic device is about to share a resource; The response to the indication message of the first electronic device and the detected resource receiving gesture, the first content from the first electronic device is received based on the communication connection between the first electronic device, includes: In response to the indication message of the first electronic device, the indication message of the third electronic device and the detected resource receiving gesture, the first content from the first electronic device is received based on the communication connection between the first electronic device, wherein the first electronic device is the same as a system account logged in by the second electronic device; or, the first electronic device is different from the system account logged in by the second electronic device, and the first electronic device is an electronic device selected by a user. The method according to any one of claims 16-19, characterized in that Before the first content from the first electronic device is received, the method further includes: In the case where the indication message of the first electronic device is not received, the resource receiving gesture is detected at a first frequency; In the case where the indication message of the first electronic device is received, the resource receiving gesture is detected at a second frequency, wherein the second frequency is higher than the first frequency. The method according to any one of claims 16-20, characterized in that The resource receiving gesture includes a start gesture and an end gesture, the start gesture indicating the start of the execution of the resource receiving gesture, and the end gesture being used to indicate the end of the execution of the resource receiving gesture; Before the first content from the first electronic device is received based on the communication connection between the first electronic device, the method further includes: In response to the detected start gesture, the communication connection between the first electronic device is established. The method according to any one of claims 16-21, characterized in that The resource receiving gesture includes a start gesture and an end gesture, the start gesture indicating the start of the execution of the resource receiving gesture, and the end gesture being used to indicate the end of the execution of the resource receiving gesture; the method further includes: When the start gesture is detected, a gesture icon corresponding to the start gesture is displayed; Or, when the start gesture is detected to move in from the front of the second electronic device, a gesture movement animation is displayed, the gesture movement animation including an animation of light and shadow moving on the display screen. The method of claim 22, wherein The direction in which the light shadow moves on the display screen is the same as the direction in which the start gesture moves in front of the second electronic device. The method according to any one of claims 21-23, characterized in that Before receiving the first content from the first electronic device, the method further includes: In response to the indication message of the first electronic device, when the end gesture is detected, receiving preview data of the first content from the first electronic device based on the communication connection between the first electronic device. The method of claim 24, wherein The method further includes: During the process of receiving the first content, displaying a receiving animation, the receiving animation including at least one of the preview data of the first content and the light shadow. The method according to any one of claims 16-25, characterized in that The first electronic device and the second electronic device log in to different system accounts, and before receiving the first content from the first electronic device, the method further includes: In the case where the first electronic device and the second electronic device do not establish a trust relationship, displaying a prompt message, the prompt message being used to confirm with the user at least one of whether to receive the first content from the first electronic device or whether to establish a trust relationship with the first electronic device; Or, in the case where the first electronic device and the second electronic device have established a trust relationship, not displaying a prompt message, the prompt message being used to confirm with the user at least one of whether to receive the first content from the first electronic device or whether to establish a trust relationship with the first electronic device. The method according to any one of claims 16-26, characterized in that The resource receiving gesture includes a gesture from a fist to a palm. An electronic device, characterized by Including: A processor, a memory, a communication interface and a display screen, the memory, the display screen, the communication interface and the processor are coupled, the communication interface is used to communicate with other devices, the memory is used to store program code, the program code includes instructions, the processor reads the instructions from the memory to make the electronic device execute the method of any one of claims 1-15, or to make the electronic device execute the method of any one of claims 16-27. A computer-readable storage medium, characterized by, The computer readable storage medium includes a computer program, when the computer program runs on an electronic device, makes the electronic device execute the method of any one of claims 1-15, or makes the electronic device execute the method of any one of claims 16-27. A computer program product, characterized in that The computer program product includes: a computer program or instructions, when the computer program or instructions run on a computer, make the computer execute the method of any one of claims 1-15, or make the computer execute the method of any one of claims 16-27. A communication system characterized by Including a first electronic device and a second electronic device, the first electronic device is used to execute the method of any one of claims 1-15, and the second electronic device is used to execute the method of any one of claims 16-27.

Images