Equipment interaction method, related device and communication system

Abstract

The invention provides an equipment interaction method, a related device and a communication system. When the first device determines that the first device is close to and touches other objects, the first device may broadcast a first message. When the second device receives the first message, the second device detects whether the distance between the first device and the second device is less than the first distance. If the distance between the first device and the second device is smaller than the first distance, the second device detects whether a device touch screen event exists or not according to the screen data. And if the device touch screen event exists, the second device sends a second message to the first device. And according to the second message, the first equipment and the second equipment can perform data circulation. According to the method, the user operation of data circulation between the devices can be simplified, the two devices which touch each other in the event that the devices touch the screen can be accurately recognized, and the situation that data circulation objects make mistakes is reduced.

Description

Technical Field

[0001] The present application relates to the field of terminal technology, and in particular to a device interaction method, related apparatus and communication system. Background Art

[0002] With the rapid development of electronic devices such as mobile phones, tablets, laptops, and in-car devices, many users now own multiple devices and frequently need to transfer data between them. For example, they might need to send documents from their phone to their laptop for editing, send navigation information from their phone to their in-car device for navigation, or stream videos from their phone to their tablet. Improving the interactive experience of transferring data between devices is a pressing issue. Summary of the Invention

[0003] This application provides a device interaction method, related apparatus, and communication system. This method enables data transfer between a first device and a second device by identifying an event in which a first device touches the screen of a second device. This simplifies user operations for transferring data between devices and accurately identifies the two devices that are touching each other during a device touch event, reducing errors in data transfer objects.

[0004] In a first aspect, the present application provides a device interaction method. The method is applied to a system including a first device and a second device, wherein the second device includes a first screen. When device motion data of the first device satisfies a first condition, the first device broadcasts a first message; the second device receives the first message and determines, based on the first message, that the distance between the first device and the second device is less than a first distance; the second device determines, based on the distance between the first device and the second device being less than the first distance and first screen data of the first screen, that the first device has touched the first screen, and sends a second message to the first device; the first device sends first content on the first device to the second device, and / or the second device sends second content on the second device to the first device.

[0005] The first message may be used to indicate that the first device has touched another object, and the second message may be used to indicate that a device touch screen event has occurred on the second device.

[0006] In some embodiments, the first content may include content displayed on a first device. The second device may include content displayed on a second device.

[0007] As can be seen, when a first device touches the screen of a second device, both the first and second devices perform detection on their own devices and confirm with the peer device to determine whether the devices touching each other in the device touch event are the first and second devices. This method of mutual verification of device touch events between two devices accurately identifies the two devices touching each other in a device touch event, reducing the possibility of data transfer errors. Furthermore, the second device can determine, based on the first message from the first device and the detected screen data, that a touch event occurred, and that the touch event is a device touch event, rather than a touch event caused by a user's finger, stylus, or other conductor. This avoids incorrect responses from the second device due to incorrect identification of the touch event type. Furthermore, the second device only begins detecting device touch events after receiving the first message from the first device. This allows for more accurate determination of the user's intent to transfer data between the first and second devices. For example, if the first device accidentally touches the second device, the first device's device motion data may not match the characteristics of the first device being near and touching another object. The first device will not send the first message to the second device. Then, the second device will not determine the device touch screen event based on its screen data, and will not request data flow with the first device. This reduces the situation where unnecessary data flow between devices is caused by the first device accidentally touching the screen of the second device.

[0008] In combination with the first aspect, in some embodiments, the detection threshold in the second device for determining that a touch screen event occurs on the first screen is a second threshold. After determining, according to the first message, that the distance between the first device and the second device is less than the first distance, the second device lowers the detection threshold for determining that a touch screen event occurs on the first screen to the first threshold; the second device determines that the first device touches the first screen based on the detection result that the distance between the first device and the second device is less than the first distance and the first screen data is detected using the first threshold.

[0009] Among them, the second device can use the first threshold to detect the first screen data to determine whether there is a touch screen event on the first screen. If there is data greater than or equal to the first threshold in the first screen data, the area corresponding to the data greater than or equal to the first threshold in the first screen is the touch area. The presence of a touch area touched by a conductor on the first screen can indicate that there is a touch screen event on the first screen. Furthermore, the second device can determine whether the touch screen event on the first screen is a device touch screen event based on whether the shape of the touch area conforms to a preset shape and / or whether the screen data in the touch area matches the preset screen data features.

[0010] As can be seen, the second device can lower the screen's touch event detection threshold when detecting a device touch event. This allows accurate detection of the slight capacitance change caused by the first device touching the screen, reducing the chance of missed touch events. Furthermore, based on detecting the shape of the touched area, the second device can also distinguish whether the touch event was triggered by the device itself or by another conductor, such as a user's finger or stylus, thereby improving the accuracy of device touch event detection.

[0011] In combination with the first aspect, in some embodiments, the first area of ​​the first screen includes the touch area of ​​the first device on the first screen. After determining that the first device touches the first screen, the second device restores the detection threshold used to determine whether there is a touch screen event in the area outside the first area on the first screen to the second threshold.

[0012] It is understandable that a low touch screen event detection threshold may affect the second device's ability to accurately identify the touch screen operation of the user's finger on the screen. For example, due to the low touch screen event detection threshold, when the user performs a two-finger operation on the screen, the second device may identify the touch area of ​​the two fingers as a connected touch area, and then identify the two-finger operation on the screen as a single-finger operation or an operation of another device touching the screen. The second device restores the touch screen event detection threshold in the non-touch area to the second threshold, and can accurately identify the user's touch screen operation on the non-touch area of ​​the screen while the first device touches the screen of the second device, and execute the instructions corresponding to the touch screen operation. In other words, while the user uses the first device to touch the screen of the second device for data transfer, he can also perform other user operations in the area outside the device touch area on the screen of the second device.

[0013] In combination with the first aspect, in some embodiments, when the first device leaves the first screen, the second device restores the detection threshold for determining whether a touch screen event occurs in the first area to the second threshold.

[0014] As can be seen, the second device lowers the touch screen event detection threshold in the first area to the first threshold only while the first device is touching the screen of the second device. This allows for accurate detection of device touch screen events and prevents frequent false touches on the second device's screen due to the low touch screen event detection threshold when the screen is not being touched by another device.

[0015] In combination with the first aspect, in some embodiments, the first area of ​​the first screen includes the touch area of ​​the first device on the first screen, and the second device determines that after the first device touches the first screen and before the first device leaves the first screen based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, the second device receives one or more touch screen operations acting on the first area; the second device does not respond to the one or more touch screen operations.

[0016] In particular, during the period from when the first device is determined to have touched the first screen to when the first device leaves the first screen, the second device may set the first area as a restricted area. When the first area is a restricted area, the first screen of the second device will not generate touch screen events corresponding to other touch screen operations (such as finger touch screen operations, stylus touch screen operations, etc.) acting on the first area. Alternatively, the second screen of the second device will generate touch screen events corresponding to other touch screen operations acting on the first area but will not report the touch screen events. By setting the first area as a restricted area, the second device may not respond to other touch screen operations acting on the first area.

[0017] Optionally, the second device may impose rule constraints on touch screen events. In the time period after determining that the first device touches the first screen and before the first device leaves the first screen, the second device may restrict other touch screen events detected in the first area. Among them, the second device may include a multi-mode input subsystem. The multi-mode input subsystem can be used to receive touch screen events reported by the first screen and distribute the touch screen events to upper-level applications. When receiving the device touch screen event reported by the first screen, the multi-mode input subsystem can start to impose rule constraints on the touch screen event. Among them, before receiving the device leaving the screen event reported by the first screen, the multi-mode input subsystem can detect whether the touch area corresponding to the other touch screen events is partially the same as or completely the same as the device touch area (such as the first area) corresponding to the device touch screen event when receiving other touch screen events (such as finger touch screen events, stylus touch screen events). If the touch area corresponding to the other touch screen events is partially the same as or completely the same as the device touch area corresponding to the device touch screen event, the multi-mode input subsystem may not distribute the other touch screen events to the upper-level application. In this way, while the first device is touching the screen of the second device, the second device may not respond to other touch operations on the first area. This method of applying rule constraints to touch events can improve the accuracy of touch event detection, avoid illogical touch events, and reduce the possibility of data transfer errors caused by accidental touches on the touch area of ​​the device in scenarios where the device touches the screen to transfer data.

[0018] In combination with the first aspect, in some embodiments, after the first device leaves the first screen, the second device receives a first touch screen operation acting on the first area; and the second device executes an instruction corresponding to the first touch screen operation.

[0019] Before the first device leaves the first screen, the first area is set as a restricted area. After the first device leaves the first screen, the second device can remove the restrictions on the first area. In other words, after the first device leaves the first screen, the second device can resume responding to touch screen operations on the first area.

[0020] In combination with the first aspect, in some embodiments, the second device detects that the second screen data of the first screen does not meet the second condition; if there is third screen data that meets the second condition within the first time period, the second device determines that the first device has not left the first screen; if there is no screen data that meets the second condition within the first time period, the second device determines that the first device has left the first screen; wherein, the first time period is the time period after the second device detects the second screen data.

[0021] Among them, the second condition may include the presence of data greater than or equal to a touch screen event detection threshold (e.g., a first threshold) in the screen data, and the shape of the touch area corresponding to the first screen of the data greater than or equal to the touch screen event detection threshold conforms to a preset shape (e.g., a rectangle). The second screen data of the first screen does not meet the second condition, which may indicate that there is currently no device touch screen event on the first screen. The presence of third screen data within the first time that meets the second condition may indicate that the second device detects a device touch screen event on the first screen again soon after detecting that there is no device touch screen event on the first screen.

[0022] It can be seen that the above-mentioned method of delaying confirmation of the device leaving the screen event can reduce the situation of misjudging the first device leaving the screen of the second device and more accurately determine the time when the first device leaves the screen of the second device. In addition, before determining that the device has left the screen event, the second device can maintain its determined touch area as an unrestricted area. This can avoid premature confirmation of the device leaving the screen event, which may lead to the sliding or partial lifting of the first device being determined as a touch operation and giving an unnecessary response. In other words, delaying confirmation of the device leaving the screen event can also reduce false touches caused by the first device touching the screen, thereby improving the user experience.

[0023] In combination with the first aspect, in some embodiments, the second device detects a first touch area based on the first screen data, and the shape of the first touch area conforms to the first shape; the second device determines that the first device touches the first screen based on the distance between the first device and the second device being less than the first distance and the shape of the first touch area conforming to the first shape.

[0024] Herein, the first shape may include a rectangle.

[0025] As can be seen, the second device can determine whether a touch on its screen is a device touch event based on the shape of the touched area. This allows for more accurate identification of whether the second device's screen has been touched by the first device, avoiding the identification of a touch event on the second device's screen by a conductor such as a user's finger or stylus as a touch event of the first device touching the second device's screen.

[0026] In combination with the first aspect, in some embodiments, the device motion data of the first device satisfies the first condition, including: the device motion data of the first device matches the device motion data corresponding to the first device approaching the first object and touching the first object.

[0027] In a second aspect, the present application provides a device interaction method. The method is applied to a second device, the second device including a first screen. The second device receives a first message from the first device and determines, based on the first message, that the distance between the first device and the second device is less than a first distance; the second device determines, based on the distance between the first device and the second device being less than the first distance and first screen data of the first screen, that the first device has touched the first screen, and sends a second message to the first device; the second device receives first content on the first device, and / or the second device sends second content on the second device to the first device.

[0028] The first device may broadcast a first message when the device motion data of the first device satisfies a first condition. The first message may be used to indicate that the first device has touched another object. The second message may be used to indicate that a device touch screen event has occurred on the second device.

[0029] In some embodiments, the first content may include content displayed on a first device. The second device may include content displayed on a second device.

[0030] As can be seen, when a first device touches the screen of a second device, both the first and second devices perform detection on their own devices and confirm with the peer device to determine whether the devices touching each other in the device touch event are the first and second devices. This method of mutual verification of device touch events between two devices accurately identifies the two devices touching each other in a device touch event, reducing the possibility of data transfer errors. Furthermore, the second device can determine, based on the first message from the first device and the detected screen data, that a touch event occurred, and that the touch event is a device touch event, rather than a touch event caused by a user's finger, stylus, or other conductor. This avoids incorrect responses from the second device due to incorrect identification of the touch event type. Furthermore, the second device only begins detecting device touch events after receiving the first message from the first device. This allows for more accurate determination of the user's intent to transfer data between the first and second devices. For example, if the first device accidentally touches the second device, the first device's device motion data may not match the characteristics of the first device being near and touching another object. The first device will not send the first message to the second device. Then, the second device will not determine the device touch screen event based on its screen data, and will not request data flow with the first device. This reduces the situation where unnecessary data flow between devices is caused by the first device accidentally touching the screen of the second device.

[0031] In combination with the second aspect, in some embodiments, the detection threshold in the second device for determining whether a touch screen event occurs on the first screen is a second threshold. After determining, based on the first message, that the distance between the first device and the second device is less than the first distance, the second device lowers the detection threshold for determining whether a touch screen event occurs on the first screen to the first threshold; the second device determines that the first device touches the first screen based on the detection result of detecting the first screen data using the first threshold when the distance between the first device and the second device is less than the first distance.

[0032] As can be seen, the second device can lower the screen's touch event detection threshold when detecting a device touch event. This allows accurate detection of the slight capacitance change caused by the first device touching the screen, reducing the chance of missed touch events. Furthermore, based on detecting the shape of the touched area, the second device can also distinguish whether the touch event was triggered by the device itself or by another conductor, such as a user's finger or stylus, thereby improving the accuracy of device touch event detection.

[0033] In combination with the second aspect, in some embodiments, the first area of ​​the first screen includes the touch area of ​​the first device on the first screen. After determining that the first device touches the first screen, the second device restores the detection threshold used to determine whether there is a touch screen event in the area outside the first area on the first screen to the second threshold.

[0034] It is understandable that a low touch screen event detection threshold may affect the second device's ability to accurately identify the touch screen operation of the user's finger on the screen. For example, due to the low touch screen event detection threshold, when the user performs a two-finger operation on the screen, the second device may identify the touch area of ​​the two fingers as a connected touch area, and then identify the two-finger operation on the screen as a single-finger operation or an operation of another device touching the screen. The second device restores the touch screen event detection threshold in the non-touch area to the second threshold, and can accurately identify the user's touch screen operation on the non-touch area of ​​the screen while the first device touches the screen of the second device, and execute the instructions corresponding to the touch screen operation. In other words, while the user uses the first device to touch the screen of the second device for data transfer, he can also perform other user operations in the area outside the device touch area on the screen of the second device.

[0035] In combination with the second aspect, in some embodiments, when it is determined that the first device leaves the first screen, the second device restores the detection threshold for determining whether a touch screen event occurs in the first area to the second threshold.

[0036] As can be seen, the second device lowers the touch screen event detection threshold in the first area to the first threshold only while the first device is touching the screen of the second device. This allows for accurate detection of device touch screen events and prevents frequent false touches on the second device's screen due to the low touch screen event detection threshold when the screen is not being touched by another device.

[0037] In combination with the second aspect, in some embodiments, the first area of ​​the first screen includes the touch area of ​​the first device on the first screen, and the second device receives one or more touch screen operations acting on the first area before determining that the first device leaves the first screen after determining that the distance between the first device and the second device is less than the first distance and the first screen data of the first screen; the second device does not respond to the one or more touch screen operations.

[0038] In particular, during the period from when the first device is determined to have touched the first screen to when the first device leaves the first screen, the second device may set the first area as a restricted area. When the first area is a restricted area, the first screen of the second device will not generate touch screen events corresponding to other touch screen operations (such as finger touch screen operations, stylus touch screen operations, etc.) acting on the first area. Alternatively, the second screen of the second device will generate touch screen events corresponding to other touch screen operations acting on the first area but will not report the touch screen events. By setting the first area as a restricted area, the second device may not respond to other touch screen operations acting on the first area.

[0039] Optionally, the second device may impose rule constraints on touch screen events. In the time period after determining that the first device touches the first screen and before the first device leaves the first screen, the second device may restrict other touch screen events detected in the first area. Among them, the second device may include a multi-mode input subsystem. The multi-mode input subsystem can be used to receive touch screen events reported by the first screen and distribute the touch screen events to upper-level applications. When receiving the device touch screen event reported by the first screen, the multi-mode input subsystem can start to impose rule constraints on the touch screen event. Among them, before receiving the device leaving the screen event reported by the first screen, the multi-mode input subsystem can detect whether the touch area corresponding to the other touch screen events is partially the same as or completely the same as the device touch area (such as the first area) corresponding to the device touch screen event when receiving other touch screen events (such as finger touch screen events, stylus touch screen events). If the touch area corresponding to the other touch screen events is partially the same as or completely the same as the device touch area corresponding to the device touch screen event, the multi-mode input subsystem may not distribute the other touch screen events to the upper-level application. In this way, while the first device is touching the screen of the second device, the second device may not respond to other touch operations on the first area. This method of applying rule constraints to touch events can improve the accuracy of touch event detection, avoid illogical touch events, and reduce the possibility of data transfer errors caused by accidental touches on the touch area of ​​the device in scenarios where the device touches the screen to transfer data.

[0040] In combination with the second aspect, in some embodiments, after determining that the first device leaves the first screen, the second device receives a first touch screen operation acting on the first area; and the second device executes an instruction corresponding to the first touch screen operation.

[0041] Before the first device leaves the first screen, the first area is set as a restricted area. After the first device leaves the first screen, the second device can remove the restrictions on the first area. In other words, after the first device leaves the first screen, the second device can resume responding to touch screen operations on the first area.

[0042] In combination with the second aspect, in some embodiments, the second device detects that the second screen data of the first screen does not meet the second condition; if there is third screen data that meets the second condition within the first time period, the second device determines that the first device has not left the first screen; if there is no screen data that meets the second condition within the first time period, the second device determines that the first device has left the first screen; wherein, the first time period is the time period after the second device detects the second screen data.

[0043] It can be seen that the above-mentioned method of delaying confirmation of the device leaving the screen event can reduce the situation of misjudging the first device leaving the screen of the second device and more accurately determine the time when the first device leaves the screen of the second device. In addition, before determining that the device has left the screen event, the second device can maintain its determined touch area as an unrestricted area. This can avoid premature confirmation of the device leaving the screen event, which may lead to the sliding or partial lifting of the first device being determined as a touch operation and giving an unnecessary response. In other words, delaying confirmation of the device leaving the screen event can also reduce false touches caused by the first device touching the screen, thereby improving the user experience.

[0044] In combination with the second aspect, in some embodiments, the second device detects a first touch area based on the first screen data, and the shape of the first touch area conforms to the first shape; the second device determines that the first device touches the first screen based on the distance between the first device and the second device being less than the first distance and the shape of the first touch area conforming to the first shape.

[0045] Herein, the first shape may include a rectangle.

[0046] As can be seen, the second device can determine whether a touch on its screen is a device touch event based on the shape of the touched area. This allows for more accurate identification of whether the second device's screen has been touched by the first device, avoiding the identification of a touch event on the second device's screen by a conductor such as a user's finger or stylus as a touch event of the first device touching the second device's screen.

[0047] In a third aspect, the present application provides an electronic device. The electronic device may include a first screen, a memory, and a processor. The first screen may be configured to display a user interface and receive touchscreen operations. The memory may be configured to store a computer program. The processor may be configured to invoke the computer program to execute any possible implementation method described in the second aspect.

[0048] In a fourth aspect, the present application provides a computer-readable storage medium storing instructions, which can be executed by a processor to implement any possible implementation method in the second aspect.

[0049] In a fifth aspect, the present application provides a computer program product, which may include computer instructions. When the computer instructions are run on a processor, any possible implementation method in the second aspect can be implemented.

[0050] In a sixth aspect, the present application provides a chip, which is applied to an electronic device. The chip includes one or more processors, which are used to call computer instructions to enable the electronic device to execute or any possible implementation method in the second aspect.

[0051] In the seventh aspect, the present application provides a communication system, which may include a first device and a second device, the first device being used to execute the method executed by the first device of any design in any of the above aspects, and the second device being used to execute the method executed by the second device of any design in any of the above aspects.

[0052] It is understandable that the electronic device provided in the third aspect, the computer-readable storage medium provided in the fourth aspect, the computer program product provided in the fifth aspect, the chip provided in the sixth aspect, and the communication system provided in the seventh aspect are all used to perform the methods provided in the embodiments of the present application. Therefore, the beneficial effects that can be achieved can be referred to the beneficial effects of the corresponding methods and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0053] Figure 1 is a schematic diagram of a communication system 10 provided in an embodiment of the present application;

[0054] Figure 2A 1 is a schematic diagram of triggering electronic device 100 and electronic device 200 to perform data transfer provided by an embodiment of the present application;

[0055] Figure 2B is a schematic diagram of a capacitive screen provided in an embodiment of the present application;

[0056] Figures 3A to 3H This is a schematic diagram of some data flow scenarios provided by the embodiments of the present application;

[0057] Figures 4A to 4C Schematic diagrams of other data flow scenarios provided in embodiments of the present application;

[0058] Figures 5A to 5G Schematic diagrams of some postures of the electronic device 100 provided in an embodiment of the present application;

[0059] Figure 6 This is a flow chart of a device interaction method provided by an embodiment of the present application;

[0060] Figure 7A and Figure 7B is a flowchart of other device interaction methods provided by embodiments of the present application;

[0061] Figure 8A This is a schematic diagram of a method for detecting a touch screen event of a device provided in an embodiment of the present application;

[0062] Figure 8B This is a schematic diagram of setting a restricted area provided in an embodiment of the present application;

[0063] Figure 8C and Figure 8D2 is a schematic diagram of a delayed confirmation of a device leaving the screen event provided by an embodiment of the present application;

[0064] Figure 9A This is a schematic diagram of the device software structure provided by an embodiment of the present application;

[0065] Figure 9B is a schematic diagram of a device interaction method provided in an embodiment of the present application;

[0066] Figure 10 This is a schematic diagram of the device software structure provided by an embodiment of the present application;

[0067] Figure 11 This is a schematic diagram of the hardware structure of a device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0068] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and claims of the present application, the singular expressions "a", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two). The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0069] References to "one embodiment" or "some embodiments" etc. described in this specification mean that the specific features, structures or characteristics described in conjunction with the embodiment are included in one or more embodiments of the present application. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. appearing in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in another way. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in another way. The term "connected" includes direct and indirect connections, unless otherwise stated. "First" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0070] In the embodiments of this application, words such as "exemplarily" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of this application should not be interpreted as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplarily" or "for example" is intended to present the relevant concepts in a concrete manner.

[0071] Figure 1 A schematic diagram of a communication system 10 provided in an embodiment of the present application is exemplarily shown.

[0072] like Figure 1 As shown, the communication system 10 may include an electronic device 100 and an electronic device 200. The device types of the electronic device 100 and the electronic device 200 may include, but are not limited to, mobile phones, tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, ultra-mobile personal computers (UMPCs), netbooks, and various electronic devices equipped with screens, such as personal digital assistants (PDAs), augmented reality (AR) devices, virtual reality (VR) devices, artificial intelligence (AI) devices, wearable devices, vehicle-mounted devices, smart home devices and / or smart city devices. The device types of the electronic device 100 and the electronic device 200 may be the same or different. The embodiment of the present application is for the electronic device 100 and the electronic device 200. The embodiment of the present application does not limit the device types of the electronic device 100 and the electronic device 200.

[0073] The electronic device 100 and the electronic device 200 may be connected via a wired communication technology or a wireless communication technology. For example, the wireless communication technology may include, but is not limited to, Bluetooth (e.g., traditional Bluetooth or Bluetooth low energy (BLE)), SparkLink (e.g., traditional SparkLink or SparkLink low energy (SLE)), Near Field Communication (NFC), Wireless Local Area Networks (WLAN) (e.g., Wireless Fidelity (Wi-Fi) networks), Zigbee, Frequency Modulation (FM), Infrared (IR), etc.

[0074] The electronic device 100 can send the content in the electronic device 100 (for example, pictures, documents, video playback information, navigation information, a user interface displayed by the electronic device 100 , etc.) to the electronic device 200 .

[0075] In some embodiments, the electronic device 200 can store content 1 from the electronic device 100. In this way, the user can perform operations such as editing on the content 1 separately on the electronic device 200 without affecting the content 1 in the electronic device 100. Optionally, if the electronic device 200 is running an application (APP) 1 when receiving the content 1, the electronic device 200 can also apply the content 1 to the APP1. For example, the electronic device 200 has opened the document 1, and when it receives the picture 1 from the electronic device 100, the electronic device 200 can insert the picture 1 into the document 1. For another example, the electronic device 200 has opened the instant messaging application, and when it receives the picture 1 from the electronic device 100, the electronic device 200 can send the picture 1 to one or more contacts in the instant messaging application.

[0076] In some embodiments, electronic device 200 can display content 2 from electronic device 100 without storing content 2. A user can perform corresponding operations on content 2 on electronic device 100 on electronic device 200. For example, content 2 can be the desktop of electronic device 100. Content 2 can include app icons on the desktop of electronic device 100. After electronic device 100 projects the desktop to electronic device 200, the user can use one or more apps on electronic device 100 on electronic device 200.

[0077] The electronic device 200 may also send content (e.g., pictures, documents, video playback information, navigation information, a user interface displayed by the electronic device 200, etc.) in the electronic device 200 to the electronic device 100. For details, please refer to the above description of the electronic device 100 sending content of the electronic device 100 to the electronic device 200.

[0078] The above embodiments of data transfer between the electronic device 100 and the electronic device 200 are merely exemplary introductions to the present application and should not be construed as limiting the present application. The electronic device 100 and the electronic device 200 may also provide more other data transfer experiences.

[0079] Figure 2A A schematic diagram of triggering data transfer between the electronic device 100 and the electronic device 200 provided in an embodiment of the present application is exemplarily shown.

[0080] like Figure 2A As shown, when electronic device 100 touches the screen of electronic device 200, data can be transferred between electronic device 100 and electronic device 200. The data transfer may include electronic device 100 sending content on electronic device 100 to electronic device 200, and / or electronic device 200 sending content on electronic device 200 to electronic device 100. The content of the data transfer between electronic device 100 and electronic device 200 may include content displayed on the screen of electronic device 100 and / or electronic device 200.

[0081] That is, when a user wants to transfer content on electronic device 100 to electronic device 200 and / or transfer content on electronic device 200 to electronic device 100, the user can use electronic device 100 to touch the screen of electronic device 200. Optionally, electronic device 200 touching the screen of electronic device 100 can also trigger data transfer between electronic devices 100 and 200. In the subsequent embodiments of this application, the example of electronic device 100 touching the screen of electronic device 200 to trigger data transfer between devices is specifically described.

[0082] In some embodiments, when electronic device 100 touches the screen of electronic device 200, the screen data on the screen of electronic device 200 changes. Electronic device 200 can detect a corresponding touch screen event based on the change in screen data. As a specific implementation, the process of electronic device 200 detecting a touch screen event is described below, taking the case where the screen of electronic device 200 is a capacitive screen and the screen data on the screen is capacitance.

[0083] The capacitive screen may include one or more capacitive modules. When the electronic device 100 or a conductor such as a finger or a stylus touches the screen of the electronic device 200, the capacitance value of one or more capacitive modules on the screen will change (for example, the capacitance becomes larger or smaller). The electronic device 200 can determine that the screen of the electronic device 200 is touched based on the change in capacitance on the screen. Among them, the capacitive modules can be distributed in different areas of the screen. When the electronic device 100 or a conductor such as a finger or a stylus touches a certain area of ​​the screen of the electronic device 200, the capacitance of the capacitive modules distributed in the corresponding area of ​​the screen will change. In this way, the electronic device 200 can determine in which area of ​​the screen a touch screen event occurs.

[0084] In some embodiments, one or more capacitive modules on the screen may be composed of a horizontally arranged electrode array and a vertically arranged electrode array.

[0085] Figure 2B A schematic diagram of a capacitive screen is shown as an example.

[0086] like Figure 2B As shown, two groups of electrodes (such as horizontal electrodes 201 and vertical electrodes 202) form a capacitor 203 at the intersection. That is, a horizontally arranged electrode and the vertically arranged electrode that crosses it constitute two stages of a capacitor, that is, a capacitor module. When the electronic device 100 or a conductor such as a finger or a stylus touches the screen of the electronic device 200, it will affect the coupling between the two electrodes near the touch position, thereby changing the capacitance between the two electrodes, causing the capacitance to change. The horizontally arranged electrodes can be transmitting electrodes. The vertically arranged electrodes can be receiving electrodes. When detecting the capacitance on the screen, the horizontally arranged electrodes can send excitation signals in sequence, and the vertically arranged electrodes can receive signals. In this way, the capacitance of the capacitors at the intersection of all transmitting electrodes and receiving electrodes on the screen (such as capacitor 203) can be obtained, that is, the capacitance value of each capacitor module is obtained.

[0087] Figure 2B The capacitive screen shown is only an exemplary introduction to the present application and should not be construed as limiting the present application. In other implementations, the capacitive modules on the screen can be set in other ways or have other arrangements.

[0088] It should be noted that in the scenario where data transfer is triggered by electronic device 100 touching the screen of electronic device 200, both electronic device 100 and electronic device 200 need to determine that electronic device 100 has touched the screen of electronic device 200. This ensures accurate identification of whether the user intends to use electronic device 100 and electronic device 200 for data transfer, and reduces the situation where accidental touches cause electronic device 100 and electronic device 200 to transfer data without the user's intention to interact. The method for a dual-end device to determine whether electronic device 100 has touched the screen of electronic device 200 will be described in subsequent embodiments. It will not be expanded here.

[0089] based on Figure 2A The triggering method for the electronic device 100 and the electronic device 200 to perform data flow is shown. The following introduces some scenarios in which the electronic device 100 and the electronic device 200 perform data flow.

[0090] Figures 3A to 3H The following schematic diagrams illustrate some data flow scenarios.

[0091] like Figure 3A As shown in (1), different areas of the screen of the electronic device 200 may display different contents, for example, content A, content B, and content C. The electronic device 100 may select the corresponding content on the screen of the electronic device 200 by touching different areas of the screen of the electronic device 200. For example, the electronic device 100 touches the position where content B is displayed on the screen of the electronic device 200. The electronic device 200 may send indication information of content B to the electronic device 100. Figure 3A As shown in (2) in FIG, the electronic device 100 can display the options of the content B according to the indication information of the content B. Further, as shown in FIG. Figure 3A As shown in (3) in , the user can perform preset operations on the options of content B, such as pull-down operations. Figure 3A As shown in (4), in response to a user's preset operation on content B, the electronic device 200 may send content B to the electronic device 100. The electronic device 100 may display content B on the screen.

[0092] In some embodiments, Figure 3A The preset operation for the option of content B shown in (3) is optional. For example, in response to the operation of electronic device 100 touching the position of content B on the screen of electronic device 200, electronic device 200 can send content B to electronic device 100. Electronic device 100 can display content B from electronic device 200.

[0093] The following uses the above-mentioned content A, content B, content C and other contents as different files on the electronic device 200 as an example to introduce the process of the electronic device 100 obtaining the content on the electronic device 200 by touching the screen of the electronic device 200.

[0094] like Figure 3B As shown, multiple file icons may be displayed on the screen of the electronic device 200, for example, file icon 311, file icon 312, file icon 313, and file icon 314. The file icons can be used to open the corresponding files. Among them, file icon 311 may correspond to a txt file named "TXT1". File icon 312 may correspond to a ppt file named "PPT1". File icon 313 may correspond to a pdf file named "PDF1". File icon 314 may correspond to an excel file named "EXCEL1". The above file icons are only exemplary descriptions of the present application and should not constitute a limitation on the present application. The electronic device 200 may also display more or fewer file icons.

[0095] The electronic device 100 may display a user interface 320. The user interface 320 may be a user interface of an instant messaging app in the electronic device 100. For example, the user interface 320 may be a chat interface with a contact "Zhang San" in the instant messaging app.

[0096] like Figure 3B As shown, the electronic device 100 touches the position where the file icon 312 is displayed on the screen of the electronic device 200. The electronic device 200 can send the indication information corresponding to the file icon 312 to the electronic device 100. For example, the indication information corresponding to the file icon 312 may include one or more information such as the name of the file corresponding to the file icon 312, the file type, etc. The embodiment of the present application does not limit the indication information corresponding to the file icon 312. The electronic device 100 can display option 331 on the screen according to the indication information corresponding to the file icon 312. Optionally, the electronic device 100 can also display a thumbnail of the interface displayed before receiving the indication information corresponding to the file icon 312 on the screen. As shown in FIG. Figure 3C As shown, the electronic device 100 may display a thumbnail 332 below the option 331 on the screen. The thumbnail 332 may be Figure 3B A thumbnail of user interface 320 is shown.

[0097] like Figure 3DAs shown, when the area of ​​the electronic device 100 touching the screen changes to the position where the file icon 313 is displayed on the screen of the electronic device 200, the electronic device 200 can send the indication information corresponding to the file icon 313 to the electronic device 100. The electronic device 100 can display option 333 according to the indication information corresponding to the file icon 313. In response to the sliding operation on option 333, the electronic device 100 can open the file corresponding to option 333 and display Figure 3E The user interface 340 shown. Among them, the file corresponding to option 333 can be the file corresponding to the file icon 313 in the electronic device 200, that is, the PDF file named "PDF1". The user interface 340 can include the file content of the PDF file named "PDF1". It should be noted that the file corresponding to option 333 can be sent by the electronic device 200 to the electronic device 100 before or after the user slides down the option 333 on the electronic device 100. The embodiment of the present application does not limit the timing when the electronic device 200 sends the file corresponding to option 333 to the electronic device 100.

[0098] In this way, the user can quickly send the file on the electronic device 200 to the electronic device 100 by touching the screen of the electronic device 200 through the electronic device 100, so that the user can read and edit the file on the electronic device 100.

[0099] like Figure 3F , the electronic device 100 may display option 333. Option 333 may refer to the introduction of the aforementioned embodiment.

[0100] like Figure 3F and Figure 3G As shown, in response to the operation of pulling down option 333 and hovering over the position of thumbnail 332, electronic device 100 can send the file corresponding to option 333 to the corresponding contact in the instant messaging APP and display Figure 3H User interface 350 is shown.

[0101] like Figure 3H As shown, user interface 350 may be the interface corresponding to thumbnail 332, that is, the chat interface with contact "Zhang San" in the instant messaging app. User interface 350 may include message 351. Message 351 may be a message sent to contact "Zhang San". The content of message 351 may be the file corresponding to option 333, that is, the PDF file named "PDF1".

[0102] In this way, based on the electronic device 100 touching the screen of the electronic device 200, the user can use the electronic device 100 to quickly retrieve the target file from the electronic device 200, and send the target file to the corresponding contact through the instant messaging APP in the electronic device 100.

[0103] The above data flow scenarios are merely exemplary descriptions of this application and should not be construed as limiting this application. In addition to acquiring files and opening files after acquiring them, or sending acquired files to contacts in an instant messaging app, electronic device 100 can also acquire other types of data on electronic device 200 by touching the screen of electronic device 200, and use the acquired data to perform other operations.

[0104] As can be seen from the above scenario, data can be transferred between two electronic devices simply by bringing the screen of one electronic device close to another. This does not require a complex interface jump to call up the data transfer function, nor does it require selecting the data receiving end from a list of electronic devices. This simplifies the operations required for data transfer between devices, making it more convenient and quick to implement. Furthermore, the above operation of triggering data transfer between devices can give users a "picking something up from the screen" experience, which is highly technological and interesting.

[0105] Figures 4A to 4C Schematic diagrams of other data flow scenarios are shown as examples.

[0106] like Figure 4A As shown in (1) in FIG, content D may be displayed on the screen of the electronic device 100. Figure 4A As shown in (2), when the electronic device 100 touches the screen of the electronic device 200 and detects a preset operation on the content D, such as a sliding operation, the electronic device 100 can send the content D to the electronic device 200. Figure 4A As shown in (3), the electronic device 200 can display content D on the screen.

[0107] In some embodiments, Figure 4A The preset operation on the content D shown in (2) is optional. For example, in response to the electronic device 100 touching the screen of the electronic device 200, the electronic device 100 can send the content D to the electronic device 200.

[0108] The following takes the above-mentioned content D as music playback content as an example to introduce the process of the electronic device 100 sending data to the electronic device 200 by touching the screen of the electronic device 200.

[0109] like Figure 4B As shown, the electronic device 100 may display a music playback interface 410. For example, the music playback interface 410 may be a playback interface for music named "Music 1". The electronic device 200 may display a homepage 420. The homepage 420 may include one or more APP icons in the electronic device 200.

[0110] In some embodiments, when the electronic device 100 displays the music playback interface 410 and the electronic device 200 displays the home page 420, when the electronic device 100 touches any area on the screen of the electronic device 200, the electronic device 100 can send the music playback information of the music playback interface 410 to the electronic device 200, so that the electronic device 200 plays the corresponding music. The above-mentioned music playback information may include one or more information such as the name of the music being played in the music playback interface 410 (for example, "Music1"), the playback progress of the music, etc.

[0111] like Figure 4C As shown, the electronic device 200 can open the music APP in the electronic device 200 according to the music playing information from the electronic device 100 and display the music playing interface 430. For example, the music playing interface 430 can be a playing interface of music named "Music1".

[0112] In some embodiments, the electronic device 200 can continue to play the corresponding music from the playback progress of the electronic device 100 based on the music playback information of the electronic device 100. For example, the music playback information indicates that the electronic device 100 is currently playing "Music1" for 50 seconds. The electronic device 200 can continue to play "Music1" from the 50th second of "Music1". Optionally, after sending the music playback information to the electronic device 200, the electronic device 100 can stop playing the corresponding music (such as "Music1"). In other words, the user can quickly transfer the audio played on the electronic device 100 to the electronic device 200 for playback by touching the screen of the electronic device 200 with the electronic device 100, and the electronic device 200 can seamlessly connect the audio played by the electronic device 100.

[0113] The above data flow scenarios are only exemplary introductions to this application and should not be construed as limiting this application. In addition to sending relevant information of the current display interface, electronic device 100 can also send other types of data in electronic device 100 to electronic device 200 by touching the screen of electronic device 200. For example, when electronic device 100 displays a gallery interface, when electronic device 100 touches the screen of electronic device 200, electronic device 100 can send one or more images in the gallery interface to electronic device 200.

[0114] From the above scenario, it can be seen that data flow between two electronic devices can be achieved by bringing one electronic device close to the screen of another electronic device. This does not require complex interface jumps to call up the data flow function, nor does it require selecting the data receiving end from the electronic device list. It can simplify the operations required for data flow between devices, making data flow between devices more convenient and quick to achieve.

[0115] In some embodiments, the electronic device 100 can achieve data flow by touching the screen of the electronic device 200 with the top of the electronic device 100. Optionally, and not limited to the top of the electronic device 100, the electronic device 100 can also achieve data flow by touching the screen of the electronic device 200 with other parts of the electronic device 100. For example, the left side, or the right side, or the back of the electronic device 100 touching the screen of the electronic device 200 can trigger data flow between the electronic device 100 and the electronic device 200. The back of the electronic device 100 can be the side opposite to the screen of the electronic device 100. The subsequent embodiments of this application are introduced by taking the top of the electronic device 100 touching the screen of the electronic device 200 as an example.

[0116] When the top of electronic device 100 touches the screen of electronic device 200, if the posture of electronic device 100 is different, the size and / or position of the touch area on the screen of electronic device 200 will be different. Some postures of electronic device 100 touching electronic device 200 are introduced below.

[0117] Figures 5A to 5G Some posture diagrams of the electronic device 100 are exemplarily shown.

[0118] like Figure 5A As shown, in the device coordinate system of the electronic device 100, the x-axis is parallel to the top or bottom edge of the electronic device 100 and points to the right side of the screen, the y-axis is perpendicular to the x-axis and points to the top of the electronic device 100, and the z-axis is perpendicular to the screen and points in the direction of the screen. The x-axis and y-axis may be located in the plane where the screen of the electronic device 100 is located. The data collected by the accelerometer and gyroscope sensor in the electronic device 100 may include three-axis components in the above-mentioned device coordinate system. The above-mentioned device coordinate system will change as the posture of the electronic device 100 changes.

[0119] The electronic device 100 can rotate around the x-axis of the device coordinate system and can also rotate around the y-axis of the device coordinate system.

[0120] like Figure 5B As shown, the top of the electronic device 100 touches the screen of the electronic device 200. The angle between the plane where the screen of the electronic device 100 is located and the plane where the screen of the electronic device 200 is located is α1.

[0121] like Figure 5C As shown, the top of the electronic device 100 touches the screen of the electronic device 200. The angle between the plane where the screen of the electronic device 100 is located and the plane where the screen of the electronic device 200 is located is α2.

[0122] like Figure 5DAs shown, the top of the electronic device 100 touches the screen of the electronic device 200. The angle between the plane where the screen of the electronic device 100 is located and the plane where the screen of the electronic device 200 is located is α3.

[0123] When the top of electronic device 100 touches the screen of electronic device 200, electronic device 100 rotates around the x-axis of the device coordinate system, which may cause the angle between the plane where the screen of electronic device 100 is located and the plane where the screen of electronic device 200 is located to change.

[0124] The angle between the plane where the screen of electronic device 100 is located and the plane where the screen of electronic device 200 is located may be in a range of greater than or equal to 0° and less than or equal to 180°.

[0125] In some embodiments, when the angle between the plane where the screen of electronic device 100 lies and the plane where the screen of electronic device 200 lies is 90°, the contact area between the top of electronic device 100 and the screen of electronic device 200 is the largest, that is, the touch area of ​​electronic device 100 on the screen of electronic device 200 is the largest. As the angle between the plane where the screen of electronic device 100 lies and the plane where the screen of electronic device 200 lies deviates further from 90°, the contact area between the top of electronic device 100 and the screen of electronic device 200 decreases, that is, the touch area of ​​electronic device 100 on the screen of electronic device 200 decreases.

[0126] For example, the side frame of the top of the electronic device 100 is rectangular. Figure 5C The angle α2 shown is 90°. At this time, the side frame of the top of the electronic device 100 is completely attached to the screen of the electronic device 200, so the touch area is relatively large. The angle between the plane where the screen of the electronic device 100 is located and the plane where the screen of the electronic device 200 is located is Figure 5B α1 shown or Figure 5D In the case of position α3 shown, only one edge line of the top side frame of the electronic device 100 may be attached to the screen of the electronic device 200, so the touch area is relatively small.

[0127] like Figure 5E As shown, the top of the electronic device 100 touches the screen of the electronic device 200. The angle between the straight line where the top edge of the electronic device 100 is located and the straight line where the left edge of the screen of the electronic device 200 is located is 90°. The touch area of ​​the electronic device 100 on the screen of the electronic device 200 can be Figure 5E The area 511 shown. It can be seen that the area 511 is a rectangle with a long side perpendicular to the left side of the screen of the electronic device 200.

[0128] like Figure 5FAs shown, the top of the electronic device 100 touches the screen of the electronic device 200. The angle between the straight line where the top edge of the electronic device 100 is located and the straight line where the left edge of the screen of the electronic device 200 is located is 45°. The touch area of ​​the electronic device 100 on the screen of the electronic device 200 can be Figure 5F As shown in FIG. 512 , it can be seen that the area 512 is a rectangle whose long side is aligned at a 45° angle to the left side of the screen of the electronic device 200 .

[0129] like Figure 5G As shown, the top of the electronic device 100 touches the screen of the electronic device 200. The straight line where the top edge of the electronic device 100 is located is parallel to the straight line where the left edge of the screen of the electronic device 200 is located. The touch area of ​​the electronic device 100 on the screen of the electronic device 200 can be Figure 5G As shown in FIG. 513 , it can be seen that the area 513 is a rectangle whose long side is parallel to the left side of the screen of the electronic device 200 .

[0130] When the top of the electronic device 100 touches the screen of the electronic device 200, the electronic device 100 rotates around the y-axis of the device coordinate system, which may cause the angle between the straight line where the top edge of the electronic device 100 is located and the straight line where the left edge of the screen of the electronic device 200 is located to change.

[0131] The electronic device 100 Figures 5B to 5G In the posture shown, data flow between the electronic device 100 and the electronic device 200 can be triggered by touching the screen of the electronic device 200 with the top.

[0132] As can be seen from the aforementioned embodiments, when electronic device 100 touches the screen of electronic device 200 to trigger data transfer between devices, electronic device 100 needs to confirm that it is electronic device 200's screen that is being touched, and electronic device 200 needs to confirm that its screen is being touched by electronic device 100. In other words, accurate data transfer between two devices requires double-end verification to confirm that both devices are touching each other in the event of one device touching the screen of the other.

[0133] In some embodiments, if electronic device 100 and electronic device 200 do not perform double-ended verification, electronic device 100 or electronic device 200 may not transfer data with the correct device. For example, if electronic device 100 only determines that it has touched the screen of a device but does not confirm that the screen touched is the screen of electronic device 200, electronic device 100 may transfer data with a nearby device other than electronic device 200. Alternatively, if electronic device 200 only determines that its screen has been touched by a device but does not confirm that the device that touched its screen is electronic device 100, electronic device 200 may transfer data with a nearby device other than electronic device 100. For example, a user owns four devices: device a, device b, device c, and device d. If the user uses device a to touch the screen of device b and also uses device c to touch the screen of device d, if the touching devices do not perform double-ended verification, data may flow between device a and device d, and between device c and device b. It can be seen that the two devices need to confirm that they are the devices that touch each other in the event that one device touches the screen of the other device. Otherwise, the objects of the data flow between the devices may be wrong, thereby affecting the user experience.

[0134] In addition, in addition to the electronic device 100, the user's finger / stylus or other conductor touching the screen of the electronic device 200 will also cause the screen data of the electronic device 200 to change. When the electronic device 100 touches the screen of the electronic device 200, the electronic device 200 may recognize the event of the electronic device 100 touching the screen as the event of the user's finger touching the screen, and thus give an incorrect response. For example, referring to the aforementioned Figure 3B , a file icon is displayed on the screen of electronic device 200. A user's finger clicking on the file icon can be used to trigger electronic device 200 to open the file corresponding to the file icon. Electronic device 100 touching the location of the file icon on the screen of electronic device 200 can be used to trigger electronic device 200 to send the file corresponding to the file icon to electronic device 100. If electronic device 200 recognizes the event of electronic device 100 touching the screen as an event of the user's finger clicking the screen, electronic device 200 will mistakenly open the corresponding file, and the user's need for data transfer between devices cannot be met.

[0135] In some embodiments, a user may accidentally touch the screen of electronic device 200 with electronic device 100 while using electronic device 100. Electronic device 100 does not detect that it has touched the screen of other devices, but electronic device 200 detects that its screen has been touched by other devices based on screen data. Electronic device 200 may request electronic device 100 to transfer data. In the above scenario, the user does not actually have the need for data transfer between devices. Electronic device 200 requests data transfer with electronic device 100 based on unilateral detection results, which not only causes unnecessary disturbances to the systems of electronic device 200 and electronic device 100, but also affects the user's experience of using electronic device 100 and electronic device 200.

[0136] An embodiment of the present application provides a device interaction method that can accurately identify the two devices touching each other in the event of the device touching the screen and whether the user intends to use the two devices to transfer data through double-end device verification, thereby improving the accuracy of data transfer between devices.

[0137] Figure 6 A flow chart of a device interaction method is exemplarily shown.

[0138] S611 : The electronic device 100 determines, based on the device motion data of the electronic device 100 , that the electronic device 100 is close to and in contact with another object.

[0139] The electronic device 100 may include a sensor such as an inertial measurement unit (IMU) for detecting device motion data. The IMU may include an acceleration sensor and a gyroscope sensor. The device motion data of the electronic device 100 may include one or more items of data such as acceleration data and angular velocity data. The electronic device 100 may determine the motion of the electronic device 100 based on the device motion data of the electronic device 100.

[0140] When electronic device 100 touches the screen of electronic device 200, the movement of electronic device 100 may include: electronic device 100 moves toward the location of the screen of electronic device 200 and stops moving after touching the screen of electronic device 200. During this movement and stopping process, the acceleration data of electronic device 100 typically changes significantly, for example, the acceleration data may decrease sharply from a positive value to a negative value. Therefore, electronic device 100 can determine whether electronic device 100 is close to and in contact with another object by analyzing its device motion data.

[0141] In some embodiments, the electronic device 100 may store a touch detection model. The electronic device 100 may input device motion data into the touch detection model and use the output of the touch detection model to determine whether the electronic device 100 is in proximity with and in contact with another object. The touch detection model may be a neural network model. The embodiments of the present application do not limit the type of touch detection model or the training method.

[0142] S612: The electronic device 100 broadcasts message 1, where the message 1 is used to indicate that the electronic device 100 has touched another object.

[0143] Based on the device motion data, electronic device 100 can only determine whether it has touched an object, but cannot directly determine whether the object it has touched is the screen of electronic device 200. Therefore, electronic device 100 can broadcast message 1 to inform surrounding devices that it has touched an object, requiring the surrounding devices to detect whether their screens have been touched by the electronic device.

[0144] In some embodiments, the electronic device 100 may broadcast the message 1 via Bluetooth communication. Not limited to Bluetooth communication, the electronic device 100 may also broadcast the message 1 via other wireless communication methods, such as star flash.

[0145] In some embodiments, the message 1 may include one or more pieces of information such as the device identification of the electronic device 100, the time when the electronic device 100 touches the other object, etc. The embodiment of the present application does not limit the content of the message 1.

[0146] S613 : The electronic device 200 receives the message 1 , and determines according to the message 1 that the distance between the electronic device 100 and the electronic device 200 is less than the distance 1 .

[0147] In some embodiments, the electronic device 200 may calculate the distance between the electronic device 100 and the electronic device 200 based on the signal strength of the message 1. It is understandable that the closer the distance between the electronic device 100 and the electronic device 200, the stronger the signal strength of the message 1 received by the electronic device 200.

[0148] In some embodiments, after receiving message 1, electronic device 200 may send a ranging request to electronic device 100. Electronic device 100 may send a ranging signal for ranging in response to the ranging request. Electronic device 200 may receive the ranging signal and calculate the distance between electronic device 100 and electronic device 200 based on the signal strength of the ranging signal.

[0149] If the distance between electronic device 100 and electronic device 200 is less than distance 1, it can indicate that electronic device 100 and electronic device 200 are very close to each other. This embodiment of the application does not limit the size of distance 1. For example, distance 1 can be a smaller value such as 5 cm or 10 cm.

[0150] If the distance between the electronic device 100 and the electronic device 200 is greater than or equal to distance 1, the object touched by the electronic device 100 cannot be the electronic device 200. Therefore, the electronic device 200 does not need to perform the following step S614.

[0151] If the distance between electronic device 100 and electronic device 200 is less than distance 1, the object touched by electronic device 100 may be electronic device 200. Then, electronic device 200 may perform the following step S614 to further determine whether its screen is touched by another device.

[0152] S614: The electronic device 200 determines, based on the screen data of the electronic device 200, that the screen of the electronic device 200 is touched by another electronic device.

[0153] Electronic device 200 can obtain screen data of electronic device 200. For example, if the screen of electronic device 200 is a capacitive screen, the screen data of electronic device 200 may include the capacitance of the screen. As can be seen from the aforementioned embodiments, when the screen of electronic device 200 is touched by a conductor, the capacitance of the screen of electronic device 200 will change. Based on the screen data, electronic device 200 can detect whether there is an area on the screen where the capacitance has changed.

[0154] The shape of the touch area when the electronic device 100 touches the screen of the electronic device 200 is different from the shape of the touch area when the user's finger or stylus touches the screen of the electronic device 200. Figures 5B to 5G It can be seen that when the electronic device 100 touches the screen of the electronic device 200, the shape of the touch area is usually rectangular. When the user's finger or stylus touches the screen of the electronic device 200, the shape of the touch area is usually circular. Therefore, the electronic device 200 can determine the touch area based on the area where the capacitance changes. The touch area can represent the area on the screen of the electronic device 200 that is touched by the conductor. The electronic device 200 can detect whether the shape of the touch area conforms to the shape of the device touching the screen. When the shape of the touch area is rectangular, or approximately rectangular, the electronic device 200 can determine that the shape of the touch area conforms to the shape of the device touching the screen.

[0155] If there is a touch area on the screen of the electronic device 200 and the touch area conforms to the shape of the device touching the screen, the electronic device 200 may execute the following step S615.

[0156] If there is no touch area on the screen of the electronic device 200 or the touch area does not conform to the shape of the device touch screen, the electronic device 200 may not execute the following step S615.

[0157] S615 : The electronic device 200 sends a message 2 to the electronic device 100 , where the message 2 is used to indicate that a device touch screen event occurs on the electronic device 200 .

[0158] The distance between electronic device 200 and electronic device 100 is less than distance 1, and there is a device touch screen event on electronic device 200, which may indicate that the device touching the screen of electronic device 200 is electronic device 100. Therefore, electronic device 200 may send message 2 to electronic device 100.

[0159] Message 2 may be a reply message to Message 1. Message 2 may include information such as the device identifier of electronic device 200 and an indicator indicating a device touch screen event. The presence of a device touch screen event on electronic device 200 may indicate that the screen of electronic device 200 has been touched by another electronic device. The present embodiment of the application does not limit the content of Message 2.

[0160] In some embodiments, when the electronic device 100 touches the screen of the electronic device 200, the electronic device 200 may also move accordingly. For example, when the electronic device 100 touches the screen of the electronic device 200, the screen of the electronic device 200 may vibrate slightly. Alternatively, while the electronic device 100 moves toward the location of the electronic device 200, the electronic device 200 also moves toward the location of the electronic device 100, that is, the electronic device 100 and the electronic device 200 approach each other, and after approaching each other, the electronic device 100 touches the screen of the electronic device 200. The electronic device 200 can obtain data collected by sensors such as the IMU in the electronic device 200, and then determine the device motion data of the electronic device 200. The electronic device 200 can detect whether the device motion data of the electronic device 200 meets the preset conditions. If the device motion data of electronic device 200 meets the preset conditions, the distance between electronic device 200 and electronic device 100 is less than distance 1 (see step S613), and the screen data determines that the screen of electronic device 200 is touched by another electronic device (see step S614), then electronic device 200 can determine that electronic device 100 is touching the screen of electronic device 200, and then execute step S615. This can more accurately identify the two devices that are touching each other in the event of a device touching the screen.

[0161] Among them, the device motion data of the electronic device 200 meets the preset conditions, which may include: the device motion data of the electronic device 200 meets the characteristics of the electronic device 200 touching other objects, and / or, the motion data of the electronic device 200 indicates that the time when the electronic device 200 touches other objects is the same or similar to the time when the electronic device 100 touches other objects (it should be understood that two times are similar can mean that the time difference between the two times is less than a preset threshold), and / or, the motion data of the electronic device 200 and the motion data of the electronic device 100 meet the characteristics of the two devices touching each other, etc.

[0162] S616: Data is transferred between the electronic device 100 and the electronic device 200.

[0163] When receiving message 2, electronic device 100 can determine that the object it has touched is the screen of electronic device 200. In this way, electronic device 100 can determine that it has touched the screen of electronic device 200, and electronic device 200 can determine that its screen has been touched by electronic device 100. Therefore, data can be transferred between electronic devices 100 and 200. The process of data transfer between devices can refer to the above Figures 3A to 3H 、 Figures 4A to 4C Introduction.

[0164] As can be seen from the above method, after the electronic device 100 detects that it has touched an object, it can determine whether it has touched the screen of an electronic device and which electronic device's screen it is by broadcasting message 1 and waiting for a reply from other electronic devices. The electronic device (such as electronic device 200) that receives message 1 can determine whether its screen has been touched by the electronic device 100 by detecting the distance between itself and the electronic device 100 and whether there is a device touch screen event, and send a reply message to message 1 to the electronic device 200 if it is determined that the screen has been touched by the electronic device 100. In this way, when the electronic device 100 touches the screen of the electronic device 200, both the electronic device 100 and the electronic device 200 will perform detection on their own devices and confirm with the other device to determine that the devices that touch each other in the event of the device touching the screen are the electronic device 100 and the electronic device 200. The above method of mutual verification of the device touching the screen event by two-end devices can accurately identify the two devices that touch each other in the event of the device touching the screen, reducing the situation of errors in data flow objects.

[0165] Furthermore, electronic device 200 can determine, based on message 1 from electronic device 100 and the shape of the detected touch area, that the touch screen event is a device touch screen event, rather than a touch screen event caused by a user's finger / stylus or other conductor. In this way, electronic device 200 can avoid giving an erroneous response due to incorrect recognition of the touch screen event type.

[0166] In addition, the electronic device 200 starts detecting the device touch screen event only after receiving the message 1 from the electronic device 100. This can more accurately determine whether the user has the intention to use the electronic device 100 and the electronic device 200 for data flow. For example, in the case where the electronic device 100 accidentally touches the electronic device 200, the device motion data of the electronic device 100 may not meet the characteristics of the electronic device 100 approaching and touching other objects in the aforementioned step S611. The electronic device 100 will not send message 1 to the electronic device 200. Then, the electronic device 200 will not determine the device touch screen event based on its screen data, and will not request data flow with the electronic device 100. This reduces the situation where unnecessary data flow between devices is caused by the electronic device 100 accidentally touching the screen of the electronic device 200.

[0167] Figure 7A and Figure 7B The flowcharts of other device interaction methods provided by the embodiments of the present application are exemplified.

[0168] In the scenario where the electronic device 100 touches the screen of the electronic device 200 to realize data flow between the electronic device 100 and the electronic device 200, the electronic device 100 can Figure 7A The method shown in the figure is used to transfer data with the electronic device 200. The electronic device 200 can Figure 7B The method shown performs data flow with the electronic device 100.

[0169] like Figure 7A As shown:

[0170] S711 : The electronic device 100 determines whether the electronic device 100 is close to and in contact with another object based on the device motion data of the electronic device 100 .

[0171] S712: The electronic device 100 broadcasts message 1, where the message 1 is used to indicate that the electronic device 100 has touched another object.

[0172] Step S711 and step S712 may refer to the aforementioned Figure 6 Steps S611 and S612 are shown in the figure. They will not be described in detail here.

[0173] If it is determined based on the device motion data that the electronic device 100 is not close to and in contact with other objects, the electronic device 100 may continue to obtain newly detected device motion data and execute step S711 again.

[0174] S713: Whether the electronic device 100 receives a reply message to message 1.

[0175] After broadcasting message 1 , electronic device 100 may wait for reply messages to message 1 from other electronic devices.

[0176] If electronic device 100 receives a reply message from another electronic device to message 1, the object touched by electronic device 100 is the screen of the electronic device that sent the reply message to electronic device 100. Electronic device 100 can exchange data with the electronic device that sent the reply message to electronic device 100.

[0177] If the electronic device 100 does not receive a reply message from the other electronic device to the message 1, then the object touched by the electronic device 100 is not the screen of the other electronic device. Figure 7A After the process ends, the electronic device 100 can continue to acquire newly detected device motion data and execute step S711 again.

[0178] In some embodiments, the electronic device 100 may wait for a reply message to message 1 from other electronic devices within a preset time period (e.g., 3 seconds, or 5 seconds, etc.). If a reply message to message 1 is received within the preset time period, the electronic device 100 may execute the following step S714. If no reply message to message 1 is received within the preset time period, the electronic device 100 may no longer wait and execute step S711 again. That is to say, after the waiting timeout, even if the electronic device 100 receives a reply message to message 1, it may no longer respond to the reply message and perform data flow with the device that sent the reply message.

[0179] S714 , after receiving the reply message from the electronic device 200 to the message 1 , the electronic device 100 transfers data with the electronic device 200 based on the communication connection 1 .

[0180] The reply message of the electronic device 200 to the message 1 may be the aforementioned Figure 6 Message 2 is shown.

[0181] The communication connection 1 may be a Bluetooth communication connection, a Wi-Fi communication connection, or a StarFlash communication connection, etc. The embodiment of the present application does not limit the type of the communication connection 1.

[0182] In some embodiments, after receiving a reply message from the electronic device 200 to the message 1 , the electronic device 100 may establish a communication connection 1 with the electronic device 200 , and then transfer data through the communication connection 1 .

[0183] Alternatively, before electronic device 100 receives a reply message from electronic device 200 to message 1, communication connection 1 has already been established between electronic device 100 and electronic device 200. Upon receiving a reply message from electronic device 200 to message 1, electronic device 100 can transfer data with electronic device 200 via communication connection 1 without having to re-establish communication connection 1.

[0184] like Figure 7B As shown:

[0185] S721 , the electronic device 200 receives the message 1 broadcast by the electronic device 100 .

[0186] For message 1, reference may be made to the introduction of the aforementioned embodiment.

[0187] S722 : The electronic device 200 detects the distance between the electronic device 100 and the electronic device 200 according to the message 1 .

[0188] Step S722 can refer to the above Figure 6 Step S613 shown.

[0189] S723: Is the distance between the electronic device 100 and the electronic device 200 less than distance 1?

[0190] If the distance between the electronic device 100 and the electronic device 200 is less than the distance 1, the electronic device 200 may execute the following step S724.

[0191] If the distance between electronic device 100 and electronic device 200 is greater than or equal to distance 1, then Figure 7B The process shown ends. It is understandable that when the distance between electronic device 100 and electronic device 200 is greater than or equal to distance 1, the screen of electronic device 200 will not be touched by electronic device 100. Therefore, electronic device 200 does not need to reply to the message to electronic device 100 and exchange data with electronic device 100.

[0192] S724: The electronic device 200 lowers the touch screen event detection threshold of the entire screen to detection threshold 1.

[0193] Compared to the user's finger / stylus touching the screen, the screen data (such as capacitance) changes caused by the electronic device 100 touching the screen are weaker. In addition, the electronic device 100 may be covered with a protective case (such as a mobile phone case). When the electronic device 100 touches the screen of the electronic device 200, it is actually the protective case on the electronic device 100 that touches the screen of the electronic device 200. The above protective case may be made of plastic, and the screen data changes caused by touching the screen are weaker. Figure 5B or Figure 5DWhen the screen of the electronic device 100 is touched in the tilted posture shown, the area of ​​the touched area is small, which may also make it difficult for the electronic device 200 to detect the device touch screen event.

[0194] To improve the accuracy of device touch screen event detection and avoid missing device touch screen events, the electronic device 200 can lower the detection threshold for determining touch screen events, for example, to detection threshold 1. The embodiment of the present application does not limit the value of detection threshold 1.

[0195] Before the touch screen event detection threshold is lowered, the touch screen event detection threshold is detection threshold 2. Detection threshold 2 is greater than detection threshold 1. In the case that the screen of the electronic device 200 is a capacitive screen, before the touch screen event detection threshold is lowered, the electronic device 200 requires the capacitance change of one or more capacitance modules on the screen to be greater than or equal to detection threshold 2 before determining that a touch screen event exists. The capacitance change caused when the electronic device 100 touches the touch screen is weak and may not meet the requirement of detection threshold 2. Then, when the electronic device 100 touches the screen of the electronic device 200, the electronic device 200 may not determine that there is a touch screen event on the screen. After the touch screen event detection threshold is lowered, the capacitance change of one or more capacitance modules on the screen of the electronic device 200 reaches detection threshold 1 to determine that there is a touch screen event. In this way, the touch screen event can be accurately identified when the device touches the screen.

[0196] The capacitance change of a capacitance module can refer to the difference between the reference signal and the raw signal (RawData). The reference signal can be the capacitance signal detected by the screen without a finger or other conductor input. The raw signal can be the capacitance signal formed by the coupling of the transmitting electrode and the receiving electrode detected by the capacitance module. The capacitance change can be referred to as Diff or DiffData.

[0197] S725 : The electronic device 200 detects a device touch screen event based on the detection threshold 1 .

[0198] In some embodiments, the electronic device 200 may determine the touch area based on a detection threshold of 1 and detect whether the shape of the touch area conforms to a preset shape. For example, the preset shape is a rectangle. When a touch screen event is determined to have occurred based on the detection threshold of 1 and the shape of the touch area conforms to the preset shape, the electronic device 200 may determine that a device touch screen event has occurred and then execute steps S727 and S729 described below.

[0199] If it is determined according to the detection threshold 1 that there is no touch screen event, or if there is a touch screen event but the shape of the touch area does not conform to the preset shape, the electronic device 200 may execute the following step S726.

[0200] It should be noted that the embodiments of the present application do not limit the method for determining whether a touch screen event on the screen is a device touch screen event. In addition to the shape of the touch area, the electronic device 200 can also determine whether a touch screen event is a device touch screen event based on data such as the change in capacitance of the touch area. For example, the electronic device 200 may include a device touch screen event detection model. The electronic device 200 can input the change in capacitance of the touch area into the device touch screen event detection model and determine whether the touch screen event is a device touch screen event based on the output of the device touch screen event detection model.

[0201] In some embodiments, the electronic device 200 can determine the touch area in combination with multiple frames (for example, 4 frames or 5 frames, etc.) of screen data. One frame of screen data may include the capacitance change of all capacitive modules on the screen at a certain moment. For example, the electronic device 200 can obtain 5 consecutive frames of screen data and determine the touch area corresponding to each frame of screen data respectively. The electronic device 200 can use the touch area corresponding to 4 frames of screen data to correct the touch area corresponding to another frame of screen data, and then determine the corrected touch area as the area where the electronic device 100 touches the screen on the screen of the electronic device 200. Alternatively, the electronic device 200 can take the union of the touch areas corresponding to the 5 frames of screen data, and determine the touch area obtained by taking the union as the area where the electronic device 100 touches the screen on the screen of the electronic device 200. This can improve the accuracy of touch area detection. The embodiments of the present application do not limit the specific method for determining the touch area.

[0202] S726 . The electronic device 200 increases the touch screen event detection threshold of the entire screen to detection threshold 2 .

[0203] If there is no touch screen event on the screen of the electronic device 200, or if there is a touch screen event but the touch screen event is not a device touch screen event (for example, it may be a user's finger touching the screen), the electronic device 200 may increase the touch screen event detection threshold for the entire screen to detection threshold 2. The embodiment of the present application does not limit the value of detection threshold 2.

[0204] If no device touch screen event is detected, the electronic device 200 will not send a reply message to the electronic device 100 for the message 1. Figure 7B The shown process ends.

[0205] S727 . The electronic device 200 sends a message 2 to the electronic device 100 . The message 2 is a reply message to the message 1 .

[0206] Step S727 can refer to the above Figure 6 Step S615 is shown.

[0207] S728 . The electronic device 200 transfers data with the electronic device 100 based on the communication connection 1 .

[0208] Communication connection 1 can refer to the aforementioned Figure 7A The following is an introduction to step S714.

[0209] S729. The electronic device 200 sets area 1 as a restricted area, where the restricted area is an area that does not respond to touch screen operations.

[0210] In some embodiments, when the electronic device 200 detects a device touch screen event, for example, a device touch screen event occurs in area 1 of the screen of the electronic device 200, the electronic device 200 may set area 1 as a restricted area. Area 1 may include the touched area on the screen of the electronic device 200 that was touched by the electronic device 100.

[0211] Among them, the electronic device 200 setting area 1 as a restricted area can indicate that the screen of the electronic device 200 will not generate touch screen events corresponding to other touch screen operations acting on area 1, or the electronic device 200 generates touch screen events corresponding to other touch screen operations acting on area 1 but will not report the touch screen events.

[0212] That is to say, when area 1 is a restricted area, the electronic device 200 may no longer respond to other touch screen operations acting in area 1 (for example, finger click operations, finger sliding operations, stylus click operations, etc.).

[0213] It can be understood that referring to the above Figures 3A to 3H 、 Figures 4A to 4C In the data flow scenario shown, when the electronic device 100 displays different interfaces or the electronic device 200 displays different interfaces, the content of the data flow between the electronic device 100 and the electronic device 200 may be different. For example, when content 1 is displayed in area 1 of the screen of the electronic device 200, the user can touch area 1 of the screen of the electronic device 200 with the electronic device 100 to enable the electronic device 100 to obtain content 1. However, if, during the period when the electronic device 100 touches the screen of the electronic device 200, the user's finger accidentally touches area 1 so that the content of area 1 changes, for example, from content 1 to content 2, then the electronic device 200 may not be able to send the data that the user needs to flow, such as content 1, to the electronic device 100.

[0214] Therefore, the electronic device 200 sets area 1 as a restricted area to reduce data transfer errors caused by accidental touches.

[0215] The present embodiment of the present application does not limit the order in which steps S727 and S729 are executed. For example, if a device touch screen event occurs in area 1 of the screen, the electronic device 200 may execute steps S727 and S729 simultaneously, or the electronic device 200 may execute step S727 first and then step S729, or the electronic device 200 may execute step S729 first and then step S727.

[0216] S730: The electronic device 200 increases the touch screen event detection threshold for areas other than area 1 on the screen to detection threshold 2.

[0217] In some embodiments, before the electronic device 100 leaves the screen of the electronic device 200 , the electronic device 200 may increase the touch screen event detection threshold for areas outside the area 1 on the screen to the detection threshold 2 .

[0218] It is understandable that a low touch screen event detection threshold may affect the electronic device 200's ability to accurately identify the touch screen operation of the user's finger on the screen. For example, due to the low touch screen event detection threshold, when the user performs a two-finger operation on the screen, the electronic device 200 may identify the touch area of ​​the two fingers as a connected touch area, and then identify the two-finger operation on the screen as a single-finger operation or an operation of another device touching the screen. Based on step S730, the electronic device 200 can accurately identify the user's touch screen operation on an area other than area 1 on the screen while the electronic device 100 is touching the screen of the electronic device 200, and execute the instructions corresponding to the touch screen operation. In other words, while the user is using the electronic device 100 to touch the screen of the electronic device 200 for data transfer, he can also perform other user operations on the area outside the device touch area on the screen of the electronic device 200.

[0219] The present embodiment of the present application does not limit the order in which steps S729 and S730 are executed. For example, if a device touch screen event occurs in area 1 of the screen, the electronic device 200 may execute steps S729 and S730 simultaneously, or the electronic device 200 may execute step S729 first and then step S730, or the electronic device 200 may execute step S730 first and then step S729.

[0220] S731: Whether the electronic device 200 detects an event of the device leaving the screen.

[0221] After determining that a device touches the screen, the electronic device 200 can detect in real time whether the device has left the screen. The electronic device 200 can determine whether the device has left the screen by detecting whether the screen data still meets the characteristics of the device touching the screen. The screen data meeting the characteristics of the device touching the screen may include: the presence of an area on the screen with a capacitance change greater than or equal to a detection threshold of 1 (i.e., a touch area), and the shape of the touch area meeting a preset shape.

[0222] In some embodiments, when it is detected that the screen data changes from satisfying the characteristics of the device touching the screen to not satisfying the characteristics of the device touching the screen, the electronic device 200 waits for a preset time period and detects whether the screen data satisfies the characteristics of the device touching the screen again within the preset time period. The embodiment of the present application does not limit the value of the above-mentioned preset time period. For example, the preset time period can be a value such as 100 milliseconds or 200 milliseconds. If within the preset time period, the electronic device 200 detects again that the screen data satisfies the characteristics of the device touching the screen, the electronic device 200 can determine that the electronic device 100 has not left the screen, that is, the device leaving the screen event has not been detected yet. If the waiting timeout occurs and the electronic device 200 does not detect that the screen data satisfies the characteristics of the device touching the screen again, the electronic device 200 can determine that the electronic device 100 has left the screen, that is, the device leaving the screen event is detected.

[0223] It is understandable that in the process of the electronic device 100 touching the screen of the electronic device 200, the user holding the electronic device 100 may slide or partially lift it for a short time, but this does not mean that the electronic device 100 has left the screen of the electronic device 200. The above-mentioned method of delaying the confirmation of the device leaving the screen event can reduce the situation of misjudging the electronic device 100 leaving the screen of the electronic device 200, and more accurately determine the time when the electronic device 100 leaves the screen of the electronic device 200. In addition, before confirming the device leaving the screen event, the area 1 including the touch area is a restricted area, which can avoid premature confirmation of the device leaving the screen event, which may result in the sliding or partial lifting of the electronic device 100 being determined as a touch operation and giving an unnecessary response. That is, delaying the confirmation of the device leaving the screen event can also reduce the false touch caused by the electronic device 100 touching the screen, thereby improving the user experience.

[0224] It should be noted that the above-mentioned waiting of the electronic device 200 for the preset time period is an optional step. In some embodiments, when the screen data is detected to change from meeting the characteristics of the device touching the screen to not meeting the characteristics of the device touching the screen, the electronic device 200 can determine that the electronic device 100 has left the screen without waiting for the preset time period.

[0225] S732: The electronic device 200 removes restrictions on area 1 and increases the touch screen event detection threshold of area 1 to detection threshold 2.

[0226] S733: The electronic device 200 maintains area 1 as a restricted area.

[0227] It should be noted that, during the process of the electronic device 100 touching the screen of the electronic device 200, the electronic device 100 may slide, causing the touch area of ​​the device to change. Figure 3C and Figure 3D , the electronic device 100 can Figure 3C The position of the touch file icon 312 is slid to the right, and changes to Figure 3D The position of the touch file icon 313 is shown. The electronic device 200 can obtain screen data in real time and detect the device touch area of ​​the electronic device 100 on the screen. When the device touch area changes, the electronic device 200 can change the restricted area on the screen accordingly.

[0228] In some embodiments, the above S730 is optional. After detecting the device leaving the screen event, the electronic device 200 may increase the touch screen event detection threshold of the entire screen to detection threshold 2.

[0229] Electronic device 200 lowers the touch screen event detection threshold for area 1 to detection threshold 1 only when electronic device 100 touches the screen of electronic device 200. This allows accurate detection of device touch screen events and prevents frequent false touches on the screen of electronic device 200 due to the low touch screen event detection threshold when the screen is not touched by other devices.

[0230] In some embodiments, one or more of steps S724, S726, S729, S730, S732, and S733 are optional. For example, S724, S726, and S730 are optional. This means that the electronic device 200 does not need to adjust the touch event detection threshold of the screen. For another example, S729, S732, and S733 are optional. This means that the electronic device 200 does not need to set area 1 containing the touch area as a restricted area.

[0231] From the above Figure 7A and Figure 7BAs can be seen from the illustrated method, when electronic device 100 touches the screen of electronic device 200, both electronic device 100 and electronic device 200 perform detection on their own devices and confirm with the peer device to determine that the devices touching each other in the device-to-screen event are electronic device 100 and electronic device 200. This allows accurate identification of the two devices touching each other in the device-to-screen event, reducing the possibility of errors in data transfer objects. Furthermore, electronic device 200 can determine, based on message 1 from electronic device 100 and the shape of the detected touch area, that the touch screen event is a device touch screen event, rather than a touch screen event caused by a user's finger / stylus or other conductor. This avoids the situation where electronic device 200 issues an erroneous response due to incorrect identification of the touch screen event type. Furthermore, electronic device 200 only begins detecting the device touch screen event after receiving message 1 from electronic device 100. This allows a more accurate determination of whether the user intends to use electronic devices 100 and 200 for data transfer. For example, if electronic device 100 accidentally touches electronic device 200, the device motion data of electronic device 100 may not meet the characteristics of electronic device 100 approaching and touching another object in step S611. Electronic device 100 will not send message 1 to electronic device 200. Therefore, electronic device 200 will not determine the device touch screen event based on its screen data and will not request data transfer with electronic device 100. This reduces the possibility of unnecessary data transfer between devices due to electronic device 100 accidentally touching the screen of electronic device 200.

[0232] Figure 8A A schematic diagram of a method for detecting a touch screen event of a device provided in an embodiment of the present application is exemplarily shown.

[0233] S811: The electronic device 200 lowers the touch screen event detection threshold of the entire screen to detection threshold 1.

[0234] Step S811 can refer to the above Figure 7B Step S724 is shown.

[0235] S812 . The electronic device 200 detects position points on the screen where the screen data meets the detection threshold 1 , and determines a connected area based on the position points where the screen data meets the detection threshold 1 .

[0236] In some embodiments, the electronic device 200 may obtain the most recent screen data detected on the screen of the electronic device 200 and detect a portion of the screen data that satisfies the detection threshold 1. The most recent screen data detected by the electronic device 200 may be detected after the electronic device 200 receives the message 1 or after the electronic device 200 detects that the distance between the electronic device 100 and the electronic device 200 is less than the distance 1.

[0237] For example, the screen data may include the capacitance change of multiple capacitance modules on the screen. The electronic device 200 can detect whether the capacitance change of each capacitance module is greater than or equal to the detection threshold 1. If the capacitance change of a capacitance module is greater than or equal to the detection threshold 1, the corresponding position of this capacitance module on the screen is the position point on the screen where the screen data meets the detection threshold 1. The electronic device 100 can find all the position points where the screen data meets the detection threshold 1 and determine the connected area. Among them, the position points on the boundary of the connected area are all position points where the screen data meets the detection threshold 1. The embodiment of the present application does not limit the method for determining the connected area. For example, the electronic device 200 can use a breadth-first search (BFS) algorithm and other methods to determine the connected area.

[0238] In some embodiments, message 1 broadcast by electronic device 100 may include information such as time 1 when electronic device 100 touched another object. Electronic device 200 may obtain historical screen data on the screen based on message 1. The historical screen data may include screen data detected by electronic device 200 at time 1. Electronic device 200 may detect portions of the historical screen data that meet detection threshold 1, thereby determining a connected area.

[0239] It is understandable that if the electronic device 200 uses the most recently detected screen data, the user is required to keep the electronic device 100 touching the screen of the electronic device 200 at least until the electronic device 200 receives the message 1. If the electronic device 200 uses the above-mentioned historical screen data, the user can remove the electronic device 100 from the screen of the electronic device 200 after the electronic device 100 sends the message 1. This can shorten the time that the electronic device 100 touches the screen of the electronic device 200 and improve the user experience. When transferring data between devices, the user does not need to keep the electronic device 100 attached to the screen of the electronic device 200 for a long time.

[0240] The connected area determined by the electronic device 200 is the touched area where the screen of the electronic device 200 is touched by the electronic device 100 .

[0241] S813: If the shape of the connected area meets the preset shape, the electronic device 200 determines that a device touch screen event occurs.

[0242] The preset shape may represent the shape of the device touching the screen.

[0243] By the aforementioned Figure 5E to Figure 5G It can be seen that when the electronic device 100 touches the screen of the electronic device 200, the shape of the touched area is usually rectangular. Therefore, the above-mentioned preset shape can be a rectangle.

[0244] The electronic device 200 can extract the geometric features of the connected area and determine whether the geometric features conform to the preset shape. If the geometric features of the connected area conform to the preset shape, the electronic device 200 can determine that there is a device touch screen event in the connected area. Figure 7B Steps S727 to S733 are shown.

[0245] If the electronic device 200 does not detect a position point where the screen data meets the detection threshold 1, or the geometric features of the connected area do not meet the preset shape, the electronic device 200 may perform Figure 7B Step S726 is shown.

[0246] As can be seen, electronic device 200 can lower the screen's touch event detection threshold when detecting whether a device touch event has occurred. This allows accurate detection of the slight capacitance change caused by electronic device 100 touching the screen, reducing the likelihood of missed touch event detections. Furthermore, based on detecting the shape of the touched area, electronic device 200 can also distinguish whether a touch event was triggered by the device or by another conductor, such as a user's finger or stylus, thereby improving the accuracy of device touch event detection.

[0247] Figure 8B A schematic diagram of setting a restricted area provided in an embodiment of the present application is exemplarily shown.

[0248] like Figure 8B As shown, the screen of the electronic device 200 may include multiple capacitor modules. The screen data of the electronic device 200 may include the capacitance change of all capacitor modules on the screen. The electronic device 200 may determine the connected area based on the screen data. The specific method can refer to the aforementioned Figure 8A Introduction. Figure 8B The data in a small rectangle shown can represent the capacitance change of a capacitor module. Among them, the value of the small rectangle in the gray area is larger and greater than the touch event detection threshold (for example, detection threshold 1). Figure 8B The gray area shown may be a connected area determined by the electronic device 200 .

[0249] In some embodiments, the electronic device 200 may determine location point 821, location point 822, location point 823, and location point 824 based on the connected area. Location point 821 may be the intersection of the top and left sides of the connected area. Location point 822 may be the intersection of the top and right sides of the connected area. Location point 823 may be the intersection of the bottom and left sides of the connected area. Location point 824 may be the intersection of the bottom and right sides of the connected area. The electronic device 200 may set the area formed by connecting location point 821, location point 822, location point 823, and location point 824 as a restricted area. It can be seen that the restricted area includes the above-mentioned connected area.

[0250] In some embodiments, because the electronic device 200 lowers the touch screen event detection threshold of the entire screen to the detection threshold before detecting a device touch screen event, after determining that a touch screen event has occurred, the electronic device 200 can set the corresponding area as a restricted area and increase the touch screen event detection threshold of the area outside the restricted area on the screen to detection threshold 2. Furthermore, after detecting an event in which the device leaves the screen, the electronic device 200 can remove the restriction on the corresponding area and restore the touch screen event detection threshold.

[0251] The above method of setting the touch area as a restricted area can reduce data flow errors caused by accidental touches.

[0252] Figure 8C and Figure 8D A schematic diagram illustrating the delayed confirmation of a device leaving the screen event provided by an embodiment of the present application is exemplified.

[0253] In some embodiments, when the electronic device 100 touches the screen of the electronic device 200 , the user may slide or partially lift the electronic device 100 for a short time, but this does not mean that the electronic device 100 has left the screen of the electronic device 200 .

[0254] like Figure 8C As shown in (1) in FIG, the top of the electronic device 100 touches the screen of the electronic device 200. Figure 8C As shown in (2), due to factors such as user hand shaking, a portion of the top of the electronic device 100 leaves the screen of the electronic device 200. The touch area of ​​the electronic device 100 on the screen of the electronic device 200 may change from a rectangular area to a circular area. In other words, Figure 8C In the state shown in (2), the screen data detected by the electronic device 200 does not meet the characteristics of the device touching the screen. Figure 8C As shown in (3), after the top of the electronic device 100 partially leaves the screen of the electronic device 200 for a short time, it immediately returns to the state where the top completely touches the screen of the electronic device 200. Furthermore, after the electronic device 100 and the electronic device 200 complete the data flow, the user can separate the electronic device 100 and the electronic device 200. Figure 8C As shown in (4), the top of the electronic device 100 completely leaves the screen of the electronic device 200 and does not quickly return to the state of touching the screen of the electronic device 200.

[0255] It can be seen that in Figure 8CIn the process shown in (1), (2), and (3), although the electronic device 200 detects that the screen data does not meet the characteristics of the device touching the screen, it soon detects that the screen data meets the characteristics of the device touching the screen again. That is, the electronic device 100 does not actually leave the screen of the electronic device 200. If the electronic device 200 Figure 8C In the state shown in (2), if it is directly confirmed that the device leaves the screen, the electronic device 200 will mistakenly determine the screen leaving event, and may determine that part of the electronic device 100 is lifted or slid as a touch operation, and give an unnecessary response.

[0256] refer to Figure 8D The method shown here delays confirmation of the device leaving the screen event.

[0257] S831: The electronic device 200 detects that the screen data does not meet the characteristics of the device touching the screen.

[0258] After determining that a device touch event has occurred on the screen, the electronic device 200 can obtain the latest screen data in real time and detect whether the screen data still meets the characteristics of a device touch screen. The screen data meeting the characteristics of a device touch screen may include: there is an area on the screen with a capacitance change greater than or equal to a detection threshold of 1 (i.e., a touch area), and the shape of the touch area meets a preset shape.

[0259] S832: Whether the electronic device 200 detects screen data that meets the device touch screen feature again before the duration 1 times out.

[0260] When it is detected that the screen data does not meet the characteristics of the device touching the screen, the electronic device 200 can start timing and continue to detect whether the latest screen data meets the characteristics of the device touching the screen. In particular, the electronic device 200 can maintain the touch area determined before the screen data is detected to not meet the characteristics of the device touching the screen as the restricted area.

[0261] S833: The electronic device 200 determines that no device-leaving-screen event occurs.

[0262] If the electronic device 200 detects that the screen data meets the characteristics of the device touching the screen again before the timer duration exceeds duration 1, the electronic device 200 can determine that the device has not left the screen event. The electronic device 200 can set the touched area on the screen touched by other devices as a restricted area.

[0263] S834: The electronic device 200 determines that a device-leaves-screen event occurs.

[0264] If the timed duration exceeds duration 1 and the electronic device 200 does not detect screen data that meets the characteristics of the device touching the screen within duration 1, the electronic device 200 can determine that a device leaves the screen event has occurred. The electronic device 200 can remove the restrictions on the area on the screen that was set as the restricted area and restore the touch screen event detection threshold (for example, to detection threshold 2).

[0265] It can be seen that the above-mentioned method of delaying the confirmation of the device leaving the screen event can reduce the situation of misjudging the electronic device 100 leaving the screen of the electronic device 200, and more accurately determine the time when the electronic device 100 leaves the screen of the electronic device 200. In addition, before determining that the device has left the screen event, the electronic device 200 can keep its determined touch area as an unrestricted area. This can avoid premature confirmation of the device leaving the screen event, which may result in the sliding or partial lifting of the electronic device 100 being determined as a touch operation, giving an unnecessary response. That is, delaying the confirmation of the device leaving the screen event can also reduce false touches caused by the electronic device 100 touching the screen, thereby improving the user experience.

[0266] In some embodiments, the types of touch screen events on the screen may include, but are not limited to, device touch screen events, finger touch screen events, stylus touch screen events, and the like. Among them, when an object touches the screen, the object will inevitably leave the screen. For example, if the electronic device 200 detects a device touch screen event, the electronic device 200 will subsequently detect a device leave the screen event. If the electronic device 200 detects a finger touch screen event, the electronic device 200 will subsequently detect a finger leave the screen event. If the electronic device 200 detects a stylus touch screen event, the electronic device 200 will subsequently detect a stylus leave the screen event. Moreover, after a device touch screen event occurs in a certain area of ​​the screen and before a device leave the screen event is detected, the area where the device touch screen event occurs generally does not generate touch screen events (such as finger touch screen events, stylus touch screen events) of other objects and leave the screen events (such as finger leave the screen event, stylus leave the screen event).

[0267] The electronic device 200 can impose rule constraints on touch screen events and screen leaving events. When the electronic device 200 detects a device touch screen event on the screen, before detecting a device screen leaving event, the electronic device 200 can restrict touch screen events and screen leaving events of other objects detected in the device touch area on the screen. That is to say, during the period from the occurrence of a device touch screen event on the screen to the detection of a device screen leaving event, the electronic device 200 may not respond to touch screen events (such as finger touch screen events, stylus touch screen events) and screen leaving events (such as finger screen leaving events, stylus screen leaving events) of other objects in the device touch area on the screen.

[0268] In some embodiments, the electronic device 200 may include a multi-mode input subsystem. The multi-mode input subsystem may be used to receive input events such as touch screen events on the screen and distribute the input events to upper-layer applications. The electronic device 200 may implement rule constraints on touch screen events through the multi-mode input subsystem. For example, when receiving a device touch screen event reported by the screen, the multi-mode input subsystem may begin to implement rule constraints on the touch screen event. Among them, before receiving a device leave screen event reported by the screen, the multi-mode input subsystem may detect whether the touch area corresponding to the touch screen event of other objects or the leave area corresponding to the leave screen event of other objects is partially the same as or completely the same as the device touch area corresponding to the device touch screen event when receiving a touch screen event (e.g., a finger touch screen event, a stylus touch screen event) or a leave screen event (e.g., a finger leave screen event, a stylus leave screen event) of other objects. If the touch area corresponding to the touch screen event of other objects or the leave area corresponding to the leave screen event of other objects is partially the same as or completely the same as the device touch area corresponding to the device touch screen event, the multi-mode input subsystem may not distribute the touch screen event of other objects to the upper-layer application. This can prevent accidental touches on the device touch area while electronic device 100 is touching the screen of electronic device 200. If the touch area corresponding to a touch event of another object or the leave area corresponding to a leave event of another object is completely different from the device touch area corresponding to the device touch event, the multi-mode input subsystem can distribute the touch event of the other object or the leave event to the upper-layer application. In this way, while the user is using electronic device 100 to touch the screen of electronic device 200 to transfer data, he or she can also perform other user operations in areas outside the device touch area on the screen of electronic device 200.

[0269] It can be seen that the above method of rule-based constraints on touch screen events can improve the accuracy of touch screen event detection, avoid illogical touch screen events, and reduce the situation where the device touch area is accidentally touched in the scenario where the device touches the screen for data flow, resulting in data flow errors.

[0270] Figure 9A A schematic diagram of the device software structure provided in an embodiment of the present application is exemplified.

[0271] The software structures of the electronic device 100 and the electronic device 200 in the embodiments of the present application can be referred to Figure 9A The software structure shown.

[0272] like Figure 9AAs shown, electronic device 100 / electronic device 200 may include a mobile sensing development platform (MSDP), a multi-mode input subsystem, a soft bus, and applications. For example, the applications may include one or more apps such as a gallery, file management, maps, and music.

[0273] MSDP can provide distributed fusion perception capabilities and distributed device virtualization capabilities. Distributed fusion perception capabilities can include aggregating and integrating multiple perception sources from multiple devices to accurately perceive the user's spatial state, mobility, gestures, sports health, and other conditions, thereby building ubiquitous basic perception capabilities for all scenarios. Distributed device virtualization capabilities can include building a device virtualization platform to virtualize various components of external devices (such as cameras, displays, microphones, speakers, etc.) as extended components of local devices, while also sharing the local components with other devices.

[0274] The multi-mode input subsystem can be used to receive input events such as touch events on the screen and distribute the input events to upper-layer applications.

[0275] The soft bus provides communication-related capabilities for seamless interconnection between multiple devices, including: WLAN service capabilities, Bluetooth service capabilities, soft bus, inter-process communication RPC (Remote Procedure Call) and other communication capabilities.

[0276] The device collaboration module can be used to determine the status of the local device and one or more other devices (for example, the applications running on the device, the capabilities of the device, the operations received by the device, etc.) based on information such as information perceived by MSDP and input events obtained by the multi-mode input subsystem. Based on the status of the local device and one or more other devices, the device collaboration module can determine what kind of collaborative services are currently needed, and then control the local device and other devices to provide corresponding collaborative services. Collaborative services may include but are not limited to data sharing, application continuity, etc. Data sharing can refer to the rapid transmission and sharing of information such as files and data between different devices. Application continuity can mean that users can seamlessly switch between different devices and continue to use applications and work previously on other devices.

[0277] based on Figure 9A The device software structure shown is as follows. A device interaction method provided by this application is introduced below.

[0278] Figure 9B A schematic diagram exemplarily shows a device interaction method provided in an embodiment of the present application.

[0279] S911. The device collaboration module in the electronic device 100 may declare support for the screen touch event to the mobile perception platform.

[0280] The device collaboration module in the electronic device 100 declares that it supports the touch screen event, which may indicate that the electronic device 100 can exchange data with other electronic devices by touching the screen of the other electronic device. The touch screen event may refer to the event that the electronic device 100 touches the screen of another electronic device.

[0281] When the device collaboration module can declare support for the screen touch event to the mobile perception platform, the mobile perception platform can report the screen touch event to the device collaboration module after detecting the screen touch event.

[0282] S912. The device collaboration module in the electronic device 200 may subscribe to the device touch screen event from the mobile perception platform.

[0283] The device collaboration module in the electronic device 200 subscribes to the device touch screen event, which may indicate that the electronic device 200 can exchange data with other electronic devices when the other electronic devices touch the screen of the electronic device 200.

[0284] When the device collaboration module can subscribe to the device touch screen event from the mobile perception platform, the mobile perception platform can report the device touch screen event to the device collaboration module after detecting the device touch screen event.

[0285] S913: The motion sensing platform in the electronic device 100 determines that the electronic device 100 is close to and in contact with another object.

[0286] In some embodiments, the mobile sensing platform in the electronic device 100 can obtain the device motion data of the electronic device 100 and determine whether the electronic device 100 is close to and in contact with other objects based on the device motion data. For details, please refer to the aforementioned Figure 6 Step S611 is shown.

[0287] The electronic device 100 may include a multi-mode input subsystem. The multi-mode input subsystem may receive data collected by sensors such as an IMU and transmit the data collected by the IMU to the mobile sensing platform.

[0288] S914. The mobile perception platform in the electronic device 100 requests the soft bus to broadcast message 1.

[0289] Message 1 may be used to indicate that the electronic device 100 has touched another object.

[0290] S915 , the soft bus in the electronic device 100 broadcasts message 1 .

[0291] S916. The soft bus in the electronic device 200 sends message 1 to the mobile perception platform.

[0292] The electronic device 200 may receive the message 1 via the soft bus and send the message 1 to the mobile sensing platform in the electronic device 200 .

[0293] S917 . The mobility perception platform in the electronic device 200 determines, based on the message 1 , that the distance between the electronic device 100 and the electronic device 200 is less than the distance 1 .

[0294] S918. The motion sensing platform in the electronic device 200 determines, based on the screen data of the electronic device 200, that the screen of the electronic device 200 is touched by another electronic device.

[0295] Step S917 and step S918 may refer to the aforementioned Figure 6 Steps S613 and S614 are shown.

[0296] S919. The mobile sensing platform in the electronic device 200 plays a touch screen animation.

[0297] In some embodiments, after detecting a device touch screen event, the mobile sensing platform in the electronic device 200 can start playing a touch screen animation. For example, the touch screen animation can be a water ripple animation. The embodiments of this application do not limit the type of touch screen animation. The above touch screen animation can be used to prompt the user on the user interface that the electronic device 200 has recognized a device touch screen event and is about to start data flow.

[0298] The motion sensing platform in the electronic device 200 can call the motion effect playing application in the electronic device 200 to play the touch screen motion effect. The embodiment of the present application does not limit the playing method of the touch screen motion effect.

[0299] S920. The mobile perception platform in the electronic device 200 reports the device touch screen event to the device collaboration module.

[0300] In some embodiments, the device touch screen event may include information about the device that touched the screen of the electronic device 200, such as the electronic device 100. In this way, the device collaboration module in the electronic device 200 can determine with which device data will be transferred and the specific content of the data transfer based on the device touch screen event.

[0301] S921. The mobile perception platform in the electronic device 200 sends message 2 to the electronic device 100 through the soft bus.

[0302] Message 2 may be used to indicate the presence of a device touch screen event on the electronic device 200 .

[0303] S922: The mobile sensing platform in the electronic device 100 plays a touch screen animation.

[0304] The soft bus in the electronic device 100 can receive the message 2 and send the message 2 to the mobile perception platform in the electronic device 100 .

[0305] According to message 2, the mobile sensing platform in electronic device 100 can play touch screen animation. For details, please refer to the above step S919 for the introduction of the mobile sensing platform playing touch screen animation in electronic device 200. The touch screen animation played by electronic device 100 and electronic device 200 can be the same or different.

[0306] S923: The mobile perception platform in the electronic device 100 reports the screen touch event to the device collaboration module.

[0307] In some embodiments, the screen touch event may include information about the device to which the screen touched by the electronic device 100 belongs, such as the electronic device 200. In this way, the device collaboration module in the electronic device 100 can determine which device to transfer data to and the specific content of the data transfer based on the screen touch event.

[0308] S924 . The device collaboration module in the electronic device 100 and the device collaboration module in the electronic device 200 perform data transfer.

[0309] When the device collaboration module in the electronic device 100 receives a screen touch event, and the device collaboration module in the electronic device 200 receives a device touch screen event, the electronic device 100 and the electronic device 200 can transfer data through their respective device collaboration modules. For example, the device collaboration module in the electronic device 100 and the device collaboration module in the electronic device 200 can determine the content currently displayed by the electronic device 100 and the electronic device 200, and then determine the specific content of the data flow according to the device touch area. When the electronic device 100 transmits data to the electronic device 200, the device collaboration module in the electronic device 100 can obtain the content that needs to be transferred from the corresponding upper-layer application and send it to the electronic device 200 via the soft bus. The soft bus in the electronic device 200 can receive content from the electronic device 100 and send it to the device collaboration module in the electronic device 200. Furthermore, the device collaboration module in the electronic device 200 can send content from the electronic device 100 to the corresponding upper-layer application in the electronic device 200. The process of the electronic device 200 transmitting data to the electronic device 100 can refer to the above-mentioned process of the electronic device 100 transmitting data to the electronic device 200, and will not be repeated here. The scenario of data transfer between electronic device 100 and electronic device 200 can refer to the aforementioned Figures 3A to 3H 、 Figures 4A to 4C Introduction.

[0310] As can be seen from the above method, when electronic device 100 touches the screen of electronic device 200, both electronic device 100 and electronic device 200 will perform detection on their own devices and confirm with the other device to determine that the devices touching each other in the device touch screen event are electronic device 100 and electronic device 200. This can accurately identify the two devices touching each other in the device touch screen event, reducing the possibility of errors in data transfer objects. Furthermore, electronic device 200 can determine that the touch screen event is a device touch screen event based on message 1 from electronic device 100 and the shape of the detected touch area, rather than a touch screen event caused by other conductors such as a user's finger / stylus. In this way, electronic device 200 can avoid giving an erroneous response due to incorrect recognition of the touch screen event type. In addition, electronic device 200 only begins detecting the device touch screen event after receiving message 1 from electronic device 100. This can more accurately determine whether the user intends to use electronic devices 100 and 200 for data transfer. For example, if electronic device 100 accidentally touches electronic device 200, the device motion data of electronic device 100 may not meet the characteristics of electronic device 100 approaching and touching another object in step S611. Electronic device 100 will not send message 1 to electronic device 200. Therefore, electronic device 200 will not determine the device touch screen event based on its screen data and will not request data transfer with electronic device 100. This reduces the possibility of unnecessary data transfer between devices due to electronic device 100 accidentally touching the screen of electronic device 200.

[0311] Figure 10 A schematic diagram of the device software structure provided in an embodiment of the present application is exemplified.

[0312] An operating system may be run in the electronic device 100. The operating system may be various operating systems currently used in the industry, including but not limited to: an operating system developed based on OpenHarmony, such as HarmonyOS; or other operating systems such as Mobile operating systems can also be various open source operating systems or their derivatives, such as Linux OS and other embedded operating systems; or they can be new operating systems of the future, such as artificial intelligence (AI) operating systems. An operating system is a set of interconnected system software programs that manage and control the operation of electronic devices, utilize and run hardware and software resources, and provide public services to organize user interactions. The operating system plays a connecting role in electronic devices, connecting to the physical hardware layer and providing an operating environment for application software.

[0313] The following uses HarmonyOS as an example to illustrate the software structure of the electronic device 100. Based on this, those skilled in the art can deduce the implementation of the embodiments of the present application under other specific operating systems.

[0314] like Figure 10 As shown, the software architecture of electronic device 100 can be divided into several layers. In some embodiments, these layers, from bottom to top, are: kernel layer, system service layer, framework layer, and application layer. Layers communicate with each other via software interfaces. System functions can be tailored, added, or combined at the subsystem level in different device deployment scenarios. Within each subsystem, functions can be tailored, added, or combined at the functional level.

[0315] The Kernel Abstraction Layer (KAL) shields multi-kernel differences and provides basic kernel capabilities to the upper layer, including but not limited to process / thread management, memory management, file system, network management, and peripheral management.

[0316] Kernel subsystem: supports the selection of suitable OS kernels for different resource-constrained devices, including but not limited to Linux kernel, Hongmeng kernel, LiteOS, etc.

[0317] Driver subsystem: The driver framework is the foundation for the system's hardware ecosystem to be open, providing unified peripheral access capabilities and a driver development and management framework. The driver framework includes: display drivers, camera drivers, audio drivers, Bluetooth drivers, sensor drivers, etc.

[0318] The system service layer includes the core capabilities of the system and provides services to applications through the framework layer. This layer includes a set of subsystems, but is not limited to the following:

[0319] System basic capability subsystem set: provides basic capabilities for the operation, scheduling, migration and other operations of distributed applications on multiple devices; for example, it can include soft bus, distributed data management, distributed task scheduling, compiler / runner; it also includes multi-mode input subsystem, graphics subsystem, security subsystem, AI business subsystem, etc. Among them, the multi-mode input subsystem can integrate inputs of multiple dimensions. Specifically, the multi-mode input subsystem receives device input events based on the kernel subsystem and driver framework, such as input events from keyboards, mice, touch screens, touchpads and other devices. The multi-mode input subsystem can normalize and standardize the input events and distribute them to the UI framework. The UI framework encapsulates the events and forwards them to the application, or distributes the events to the application through other interfaces.

[0320] Basic software service subsystem set: provides public and general software services; for example, event notification subsystem, telephone service subsystem, multimedia subsystem, mobile perception platform subsystem, etc. The mobile perception platform subsystem can refer to the above Figure 9A and Figure 9B Introduction to the mobile sensing platform.

[0321] Enhanced software service subsystem set: provides differentiated capability-enhanced software services for different devices; for example, it may include smart screen-specific business subsystems, wearable-specific business subsystems, IoT-specific business subsystems, etc.

[0322] Hardware service subsystem set: provides hardware services; for example, it can include location service subsystem, user IAM (Identity and Access Management) subsystem, wearable proprietary hardware service subsystem, biometric recognition, IoT proprietary hardware service subsystem, etc.

[0323] Distributed task scheduling can realize distributed service management (discovery, synchronization, registration, and calling), and support operations such as remote startup, remote calling, remote connection, and migration of applications across devices.

[0324] Distributed data management can realize data synchronization, data storage, data sharing and data access functions across all scenarios and devices.

[0325] The soft bus provides communication-related capabilities for seamless interconnection between multiple devices.

[0326] The compiler / runner is a unified compilation and runtime platform designed to support the joint compilation and execution of multiple programming languages ​​and multiple chip platforms. For example, the compiler / runner can be the Ark Compiler.

[0327] The framework layer provides application programming interfaces (APIs) and programming frameworks for applications in the application layer. Examples include the UI framework module (which provides a complete infrastructure for UI development for system applications, including UI features such as components, layouts, animations, interactive events, and real-time interface preview tools), the user program framework, and the Ability framework (an Ability is a lightweight application that schedules and manages its operation and lifecycle). Different devices may run different operating systems, and the APIs they support may also vary.

[0328] The HarmonyOS API provides a series of open capabilities to support HarmonyOS application development. HarmonyOS APIs can be set up at the framework level or independently of the framework level. Examples include the Audio API (audio service), the Push API (push service), and the Account API (account service).

[0329] Applications can include system applications and extension applications / third-party applications. System applications include desktop applications, control bar applications, settings applications, contacts applications, phone applications, camera applications, gallery applications, file management applications, etc. Extension applications / third-party applications include social applications, map applications, music applications, etc.

[0330] Figure 11 A schematic diagram of the hardware structure of a device provided in an embodiment of the present application is exemplified.

[0331] like Figure 11 As shown, the electronic device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc.

[0332] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device 100. In other embodiments of the present application, the electronic device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0333] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0334] The controller may be the nerve center and command center of the electronic device 100. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0335] Processor 110 may also include a memory for storing instructions and data. In some examples, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces processor 110 latency, and thus improves system efficiency.

[0336] USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. USB interface 130 can be used to connect a charger to charge electronic device 100, transfer data between electronic device 100 and peripheral devices, or connect headphones to play audio.

[0337] The charging management module 140 is used to receive charging input from a charger. The charger can be a wireless charger or a wired charger. While charging the battery 142, the charging management module 140 can also power the electronic device through the power management module 141.

[0338] 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 provide power to the processor 110, the internal memory 121, the external memory, the display 194, the camera 193, and the wireless communication module 160.

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

[0340] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in electronic device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0341] The mobile communication module 150 can provide wireless communication solutions, including 2G / 3G / 4G / 5G, for the electronic device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low-noise amplifier (LNA), and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modem processor for demodulation. The mobile communication module 150 can also amplify the signals modulated by the modem processor and convert them into electromagnetic waves for radiation via the antenna 1.

[0342] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), NFC, infrared technology (IR), etc. applied to the electronic device 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0343] The electronic device 100 implements display functions through a GPU, a display screen 194, and an application processor. The GPU is a microprocessor for image processing that connects the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering.

[0344] The display screen 194 is used to display images, videos, etc. In some embodiments, the electronic device 100 may include 1 or N display screens 194 , where N is a positive integer greater than 1.

[0345] The electronic device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

[0346] The ISP is used to process data fed back by the camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then transmitted to the ISP for processing and converted into an image visible to the naked eye.

[0347] The camera 193 is used to capture still images or videos. In some embodiments, the electronic device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0348] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0349] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in electronic device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0350] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 100. The external memory card communicates with the processor 110 via the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be stored on the external memory card.

[0351] The internal memory 121 can be used to store computer executable program codes, which include instructions. The processor 110 executes various functional applications and data processing of the electronic device 100 by running the instructions stored in the internal memory 121. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area can store data created during the use of the electronic device 100 (such as audio data, a phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

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

[0353] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0354] The speaker 170A, also called a "speaker", is used to convert audio electrical signals into sound signals. The electronic device 100 can listen to music or listen to hands-free calls through the speaker 170A.

[0355] The receiver 170B, also called a "handset", is used to convert audio electrical signals into sound signals. When the electronic device 100 receives a call or a voice message, the user can place the receiver 170B close to the ear to listen to the voice.

[0356] Microphone 170C, also known as a "microphone" or "speaker," is used to convert sound signals into electrical signals. When making a call or sending a voice message, a user can speak by approaching microphone 170C with their mouth to input the sound signal into microphone 170C.

[0357] The headphone jack 170D is used to connect a wired headphone.

[0358] The sensor module 180 may include a pressure sensor, a gyro sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a gravity sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, a bone conduction sensor, an angle sensor, and the like.

[0359] Buttons 190 include a power button, a volume button, etc. Motor 191 can generate vibration prompts. Indicator 192 can be an indicator light that can be used to indicate charging status, power changes, messages, missed calls, notifications, etc.

[0360] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and disconnected from the electronic device 100 by inserting or removing the SIM card into or from the SIM card interface 195. The electronic device 100 interacts with the network through the SIM card to implement functions such as calls and data communications.

[0361] The hardware and software structure of the electronic device 200 can refer to the aforementioned Figure 10 、 Figure 11 The structure of the electronic device 100 is shown.

[0362] An embodiment of the present application further provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments can be implemented.

[0363] An embodiment of the present application further provides a computer program product, including a computer program. When the computer program runs on a processor, the steps in the above-mentioned various method embodiments can be implemented.

[0364] The present application also provides a chip system, comprising a processing circuit and an interface circuit, wherein the interface circuit is configured to receive code instructions and transmit them to the processing circuit, and the processing circuit is configured to execute the code instructions so that the chip system implements the steps of any method embodiment of the present application. The chip system can be a single chip or a chip module composed of multiple chips.

[0365] It is understood that the various user interfaces described in the embodiments of this application are merely exemplary interfaces and do not limit the scope of this application. In other embodiments, the user interface may adopt a different interface layout, include more or fewer controls, and add or remove other functional options. As long as they are based on the same concept provided by this application, they are all within the scope of protection of this application.

[0366] It should be noted that, without causing any contradiction or conflict, any feature in any embodiment of the present application, or any part of any feature, can be combined, and the combined technical solution is also within the scope of the embodiments of the present application.

[0367] As described above, the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the above embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the above embodiments, or make equivalent replacements for some of the technical features therein. However, these modifications or replacements do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A device interaction method, characterized in that: The method is applied to a system including a first device and a second device, where the second device includes a first screen, and the method includes: When the device motion data of the first device meets a first condition, the first device broadcasts a first message; The second device receives the first message, and determines, according to the first message, that the distance between the first device and the second device is less than a first distance; The second device determines, based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, that the first device touches the first screen, and sends a second message to the first device; The first device sends first content on the first device to the second device, and / or the second device sends second content on the second device to the first device.

2. The method according to claim 1, characterized in that A detection threshold for determining in the second device that a touch screen event occurs on the first screen is a second threshold, and after determining, according to the first message, that the distance between the first device and the second device is less than the first distance, the method further includes: The second device lowers a detection threshold for determining whether a touch screen event occurs on the first screen to a first threshold; The second device determines, based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, that the first device touches the first screen, specifically including: The second device determines that the first device touches the first screen based on a detection result that the distance between the first device and the second device is less than the first distance and the first screen data is detected using the first threshold.

3. The method according to claim 2, characterized in that The first area of ​​the first screen includes a touch area of ​​the first device on the first screen. After determining that the first device touches the first screen, the method further includes: The second device restores the detection threshold for determining that a touch screen event occurs in an area outside the first area on the first screen to the second threshold.

4. The method according to claim 3, characterized in that The method further comprises: When the first device leaves the first screen, the second device restores the detection threshold for determining whether a touch screen event occurs in the first area to the second threshold.

5. The method according to any one of claims 1 to 4, characterized in that The first area of ​​the first screen includes a touch area of ​​the first screen by the first device, and after the second device determines that the first device touches the first screen based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, the method further includes: Before the first device leaves the first screen, the second device receives one or more touch screen operations acting on the first area; The second device does not respond to the one or more touch screen operations.

6. The method according to claim 5, characterized in that The method further comprises: After the first device leaves the first screen, the second device receives a first touch screen operation acting on the first area; The second device executes an instruction corresponding to the first touch screen operation.

7. The method according to any one of claims 1 to 6, characterized in that The method further comprises: The second device detects that the second screen data of the first screen does not meet a second condition; If the third screen data exists within the first time period and satisfies the second condition, the second device determines that the first device has not left the first screen; If there is no screen data meeting the second condition within the first time period, the second device determines that the first device has left the first screen; The first time period is a time period after the second device detects the second screen data.

8. The method according to any one of claims 1 to 7, characterized in that The second device determines, based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, that the first device touches the first screen, specifically including: The second device detects a first touch area according to the first screen data, and a shape of the first touch area conforms to a first shape; The second device determines that the first device touches the first screen according to that the distance between the first device and the second device is less than the first distance and the shape of the first touch area conforms to the first shape.

9. The method according to any one of claims 1 to 8, characterized in that The device motion data of the first device satisfies a first condition, including: the device motion data of the first device matches device motion data corresponding to the first device approaching a first object and touching the first object.

10. A device interaction method, characterized in that: The method is applied to a second device, where the second device includes a first screen, and the method includes: The second device receives the first message from the first device, and determines, according to the first message, that the distance between the first device and the second device is less than a first distance; The second device determines, based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, that the first device touches the first screen, and sends a second message to the first device; The second device receives the first content on the first device, and / or the second device sends the second content on the second device to the first device.

11. The method according to claim 10, characterized in that A detection threshold for determining in the second device that a touch screen event occurs on the first screen is a second threshold, and after determining, according to the first message, that the distance between the first device and the second device is less than the first distance, the method further includes: The second device lowers a detection threshold for determining whether a touch screen event occurs on the first screen to a first threshold; The second device determines, based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, that the first device touches the first screen, specifically including: The second device determines that the first device touches the first screen based on a detection result of detecting the first screen data using the first threshold value, based on a distance between the first device and the second device being less than the first distance.

12. The method according to claim 11, characterized in that The first area of ​​the first screen includes a touch area of ​​the first device on the first screen. After determining that the first device touches the first screen, the method further includes: The second device restores the detection threshold for determining that a touch screen event occurs in an area outside the first area on the first screen to the second threshold.

13. The method according to claim 12, characterized in that The method further comprises: When it is determined that the first device leaves the first screen, the second device restores the detection threshold for determining whether a touch screen event occurs in the first area to the second threshold.

14. The method according to any one of claims 10 to 13, characterized in that The first area of ​​the first screen includes a touch area of ​​the first screen by the first device, and after the second device determines that the first device touches the first screen based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, the method further includes: Before determining that the first device leaves the first screen, the second device receives one or more touch screen operations acting on the first area; The second device does not respond to the one or more touch screen operations.

15. The method according to claim 14, characterized in that The method further comprises: After determining that the first device leaves the first screen, the second device receives a first touch screen operation acting on the first area; The second device executes an instruction corresponding to the first touch screen operation.

16. The method according to any one of claims 10 to 15, characterized in that The method further comprises: The second device detects that the second screen data of the first screen does not meet a second condition; If the third screen data exists within the first time period and satisfies the second condition, the second device determines that the first device has not left the first screen; If there is no screen data meeting the second condition within the first time period, the second device determines that the first device has left the first screen; The first time period is a time period after the second device detects the second screen data.

17. The method according to any one of claims 10 to 16, characterized in that The second device determines, based on the distance between the first device and the second device being less than the first distance and the first screen data of the first screen, that the first device touches the first screen, specifically including: The second device detects a first touch area according to the first screen data, and a shape of the first touch area conforms to a first shape; The second device determines that the first device touches the first screen according to that the distance between the first device and the second device is less than the first distance and the shape of the first touch area conforms to the first shape.

18. An electronic device, characterized in that: The electronic device includes a first screen, a memory and a processor, wherein the first screen is used to display a user interface and receive touch screen operations; the memory is used to store a computer program; and the processor executes the computer program to implement the method described in any one of claims 10-17.

19. A computer-readable storage medium storing instructions, characterized in that: When the instructions are executed by a processor, the method according to any one of claims 10 to 17 is implemented.

20. A computer program product, characterized in that The computer program product comprises computer instructions, which implement the method according to any one of claims 10 to 17 when executed by a processor.

Images