A cross-device interaction method and device of a wearable device and the wearable device

Abstract

The application discloses a cross-device interaction method and device of a wearable device and the wearable device, and aims to solve the problem of poor user experience in the cross-device interaction method of the existing wearable device. The method comprises the following steps: the wearable device detects a first operation, wherein the first operation is used to instruct the wearable device to start cross-device interaction; in response to the first operation, the wearable device determines a target device which performs cross-device interaction with the wearable device; the wearable device determines the running state of the wearable device and the target device; wherein the running state is used to indicate whether the wearable device is running a first task, whether the target device can run the first task, whether the target device is running a second task, and whether the wearable device can run the second task; and the wearable device performs corresponding cross-device interaction according to the running state.

Description

Technical Field

[0001] This application relates to the field of terminal technology, and in particular to a cross-device interaction method, apparatus and wearable device for wearable devices. Background Technology

[0002] Smartwatches are a new type of wearable device that combines the latest internet technology (IT) with traditional watch functions, offering advantages such as portability, ease of use, and rich functionality. However, due to size limitations, smartwatches cannot have large screens, resulting in relatively poor display and touch functionality. Many complex tasks cannot be performed on smartwatches, and many cross-device interaction devices do not include smartwatches. In other words, smartwatches are merely accessories to other terminal devices, not independent devices for cross-device interaction. For example, smartwatches cannot directly add, modify, or delete contacts; the contacts must be added, modified, or deleted on the phone associated with the smartwatch, and then the updated data from the phone associated with the smartwatch will be synced to the smartwatch.

[0003] To achieve cross-device interaction, existing smartwatches generally employ two solutions. The first is that the smartwatch interacts with other terminal devices via near-field communication (NFC) tags. However, this solution requires the smartwatch to be aligned with the NFC tag for interaction, resulting in a strong reliance on NFC. The second solution involves online chat for interaction. However, this requires the smartwatch to first enter the chat application and then select contacts and pictures, leading to a deeper user interface. Furthermore, the small screen size of smartwatches can restrict operation.

[0004] It is evident that existing wearable devices (such as smartwatches) rely heavily on NFC tags or have deeply embedded operation interfaces when interacting with other terminal devices, resulting in poor user experience. Summary of the Invention

[0005] This application provides a cross-device interaction method, apparatus, and wearable device for wearable devices, in order to solve the technical problem of poor user experience in existing cross-device interaction methods for wearable devices.

[0006] In a first aspect, embodiments of this application provide a cross-device interaction method for wearable devices, including:

[0007] The wearable device detects a first operation; wherein the first operation is used to instruct the wearable device to initiate cross-device interaction;

[0008] In response to the first operation, the wearable device determines the target device with which it will interact across devices;

[0009] The wearable device determines the operating status of the wearable device and the target device; wherein, the operating status is used to indicate whether the wearable device is running a first task, whether the target device is able to run the first task, whether the target device is running a second task, and whether the wearable device is able to run the second task;

[0010] The wearable device performs corresponding cross-device interactions based on the operating status.

[0011] Based on the above technical solution, after detecting a first operation instructing the wearable device to initiate cross-device interaction, the wearable device, in response to the first operation, first determines the target device with which it will interact across devices, and then determines the operating states of both the wearable device and the target device. The operating states indicate whether the wearable device is running a first task, whether the target device is capable of running the first task, whether the target device is running a second task, and whether the wearable device is capable of running the second task. The wearable device then performs the corresponding cross-device interaction based on its operating states. This allows the wearable device to determine the target device with which it will interact across devices after detecting the first operation, and to predict user intent by determining the operating states of both devices, thus achieving cross-device interaction between the wearable device and the target device. This not only avoids reliance on NFC tags but also provides a shallower entry point, making operation less restrictive and improving the user experience.

[0012] In one possible design, the first operation includes a user performing a continuous tapping gesture on any spatial point; wherein the number of continuous taps is not less than a first preset threshold.

[0013] In one possible design, the wearable device detects a first operation, including:

[0014] The wearable device acquires acceleration data when detection conditions are met; wherein, the detection conditions are that the wearable device is in motion, or the wearable device is in a screen-on state, or the wearable device identifies an authorized device within a preset range, and the authorized device is a device associated with the wearable device or a device authorized by the wearable device.

[0015] The wearable device acquires the acceleration data within a preset time period and determines whether the acceleration data within the preset time period matches the preset acceleration data.

[0016] If the match is successful, the wearable device detects the first operation and stops acquiring the wearable device's acceleration data.

[0017] In one possible design, determining whether the acceleration data within the preset time period matches preset acceleration data includes:

[0018] The wearable device determines the preset sub-time periods included in the preset time period, and sorts the acceleration data corresponding to the preset sub-time periods in chronological order; wherein, the number of preset sub-time periods is twice the number of consecutive taps;

[0019] The wearable device determines whether the acceleration data within the preset sub-time period with an even-numbered sequence number matches the first preset acceleration data; wherein, the first preset acceleration data is the acceleration data corresponding to when the user performs a patting gesture operation on any spatial point;

[0020] If a match is successful, the wearable device determines whether the acceleration data within the preset sub-time period with an odd sequence number matches the second preset acceleration data; wherein, the second preset acceleration data is the acceleration data corresponding to the user's patting gesture operation on any spatial point before the user performs the patting gesture operation.

[0021] Based on the above technical solution, the wearable device can first divide a preset time period into multiple preset sub-time periods, and sort the acceleration data corresponding to the preset sub-time periods according to time sequence. The number of preset sub-time periods is twice the number of consecutive taps. Then, it determines whether the acceleration data in the even-numbered preset sub-time periods matches the first preset acceleration data, which is the acceleration data corresponding to the user's tapping gesture at any spatial point. If a match is found, it then determines whether the acceleration data in the odd-numbered preset sub-time periods matches the second preset acceleration data, which is the acceleration data corresponding to the user's tapping gesture before performing the tapping gesture. By first determining whether the acceleration data when the user performs a tapping gesture matches the first preset acceleration data, and then determining whether the acceleration data before the first tapping gesture and between two tapping gestures matches the second preset acceleration data, the wearable device can quickly detect the first operation, thereby quickly initiating cross-device interaction and improving the user experience.

[0022] In one possible design, determining whether the acceleration data within the preset sub-time period with an even-numbered sequence number matches the first preset acceleration data includes:

[0023] The wearable device determines whether the acceleration data within the first preset sub-time period with an even number matches the first preset acceleration data;

[0024] If a match is found, the wearable device activates its microphone to determine whether there is corresponding audio data for the acceleration data within the second preset sub-time period with an even-numbered sequence number.

[0025] If there is corresponding audio data, the wearable device acquires the audio data corresponding to the acceleration data within the preset sub-time period with an even number after the first preset sub-time period with an even number.

[0026] The wearable device determines whether the acceleration data within the preset sub-time period with an even number after the first preset sub-time period with an even number matches the first preset acceleration data, and whether the audio data matches the preset audio data.

[0027] Based on the above technical solution, when the wearable device determines whether the acceleration data in the even-numbered preset sub-time period matches the first preset acceleration data, it can determine whether the acceleration data in the even-numbered first preset sub-time period matches the first preset acceleration data. If they match, the wearable device's microphone is activated, and it is determined whether the acceleration data in the even-numbered second preset sub-time period has corresponding audio data. If there is corresponding audio data, the audio data corresponding to the acceleration data in the even-numbered preset sub-time period after the even-numbered first preset sub-time period is obtained. It is then determined whether the acceleration data in the even-numbered preset sub-time period after the even-numbered first preset sub-time period matches the first preset acceleration data, and whether the audio data matches the preset audio data. By activating the wearable device's microphone when the acceleration data within the first preset sub-time period with an even-numbered sequence matches the first preset acceleration data, the system can determine whether the acceleration data within the next preset sub-time period with an even-numbered sequence matches the first preset acceleration data, as well as whether the audio data matches the preset audio data. This allows the wearable device to combine its acceleration data and the audio data measured by its microphone to detect the first operation, improving the accuracy of the wearable device's detection. Furthermore, because the microphone is only activated when the user first performs a tapping gesture at any spatial point, the power consumption of the wearable device is reduced.

[0028] In one possible design, the wearable device identifies a target device with which it will interact across devices, including:

[0029] The wearable device sends a communication broadcast to the authorization device and determines the distance between the authorization device and the wearable device upon receiving the communication broadcast;

[0030] The wearable device determines whether the number of authorized devices whose distance meets the preset conditions is not less than a third preset threshold.

[0031] If the number is equal to the third preset threshold, then the wearable device determines the authorized device whose distance satisfies the preset condition as the target device;

[0032] If the number is greater than the third preset threshold, the wearable device determines the priority of the authorized device whose distance meets the preset condition based on the distance, and determines the authorized device with the highest priority whose distance meets the preset condition as the target device; or, displays a dialog box to select the target device from the authorized devices whose distance meets the preset condition, and determines the target device based on the information obtained from the dialog box.

[0033] In one possible design, if the operating status indicates that the wearable device is running the first task, after determining whether the number of authorized devices whose distance meets the preset condition is not less than a third preset threshold, the method further includes:

[0034] If the number is greater than the third preset threshold, the wearable device determines whether the authorized device whose distance meets the preset condition can run the first task;

[0035] The wearable device determines the priority of the authorized device whose distance meets the preset condition based on the judgment result and the distance, and determines the authorized device with the highest priority whose distance meets the preset condition as the target device.

[0036] In one possible design, the wearable device performs corresponding cross-device interactions based on the operating state, including:

[0037] The wearable device determines the cross-device interaction content based on the operating status; wherein, the cross-device interaction content includes any one of task continuation, data synchronization, capability assistance, and device control;

[0038] The task continuation is used to instruct the wearable device to control the target device to run the task that the wearable device is currently running, or the target device to control the wearable device to run the task that the target device is currently running; the data synchronization is used to instruct the wearable device to send relevant information about the task that the wearable device is currently running to the target device, or the target device to send relevant information about the task that the target device is currently running to the wearable device; the capability assistance is used to instruct the wearable device to display relevant information about the task that the target device is currently running, or the target device to display relevant information about the task that the wearable device is currently running; the device control is used to instruct the wearable device to display control information of the target device, or the target device to display control information of the wearable device.

[0039] The wearable device performs corresponding cross-device interactions with the target device based on the cross-device interaction content.

[0040] In one possible design, the wearable device determines the cross-device interaction content based on the operating state, including:

[0041] If the running status indicates that the wearable device is running the first task, and the target device is able to run the first task, then the wearable device determines that the cross-device interaction content is the task continuation or the data synchronization.

[0042] If the running status indicates that the wearable device is running the first task, the target device cannot run the first task, and the target device is running the second task, or the wearable device is not running the first task, and the target device is running the second task, then the wearable device determines that the cross-device interaction content is the capability assistance or the device control or the capability assistance and the device control.

[0043] If the operating status indicates that the wearable device is running the first task, the target device is unable to run the first task, and the target device is not running the second task, or if the wearable device is not running the first task and the target device is not running the second task, then the wearable device determines that the cross-device interaction content is device control.

[0044] Based on the above technical solution, when the wearable device indicates that it is running a first task and the target device is also capable of running the first task, the cross-device interaction content is determined to be task continuation or data synchronization. When the wearable device indicates that it is running a first task but the target device is not capable of running the first task and is running a second task, or when the wearable device is not running a first task but the target device is running a second task, the cross-device interaction content is determined to be capability assistance or device control, or both. When the wearable device indicates that it is running a first task but the target device is not capable of running the first task and is not running a second task, or when both the wearable device and the target device are not running a first task, the cross-device interaction content is determined to be device control. By determining whether the wearable device or the target device is running a task and whether the target device or the wearable device is capable of running the task being run by the other, user intent can be predicted, enabling cross-device interaction between the wearable device and the target device, thus improving the user experience.

[0045] Secondly, this application also provides a cross-device interaction device for wearable devices. This device has the function of implementing the first aspect or any possible design method described in the first aspect. The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described functions.

[0046] Thirdly, this application also provides a wearable device, the wearable device including at least one processor and a memory; the memory stores one or more computer programs; when the one or more computer programs stored in the memory are executed by the at least one processor, the wearable device performs the method described in the first aspect or any possible design of the first aspect.

[0047] Fourthly, this application also provides a computer storage medium comprising a computer program that, when run on a computer, causes the computer to perform the method described in the first aspect or any possible design of the first aspect.

[0048] Fifthly, this application also provides a program product that, when run on a computer, causes the computer to perform the method described in the first aspect or any possible design of the first aspect.

[0049] In a sixth aspect, this application also provides a chip that can be coupled to the memory of a wearable device for calling a computer program stored in the memory and executing the methods described in the first aspect and any possible design thereof. Attached Figure Description

[0050] Figure 1 This is a schematic diagram of the structure of a cross-device interaction system for wearable devices provided in an embodiment of this application;

[0051] Figure 2 A flowchart illustrating a cross-device interaction method for a wearable device provided in an embodiment of this application;

[0052] Figure 3a A schematic diagram of a preset sliding window provided in an embodiment of this application;

[0053] Figure 3b A schematic diagram illustrating cross-device interaction provided in an embodiment of this application;

[0054] Figure 3c A schematic diagram illustrating another cross-device interaction provided in an embodiment of this application;

[0055] Figure 3d A schematic diagram illustrating yet another type of cross-device interaction provided in an embodiment of this application;

[0056] Figure 4 This is a schematic diagram of the structure of a wearable device provided in an embodiment of this application. Detailed Implementation

[0057] In existing technologies, smartwatches generally employ two schemes to achieve cross-device interaction. The first scheme involves the smartwatch interacting with other terminal devices via NFC tags. For example, activating the smartwatch's one-touch transfer function and the phone's NFC function, selecting one or more images from the phone's gallery, and then placing the NFC area on the back of the phone against the smartwatch screen, the screen will display "Smart cropping in progress" and "Image transfer in progress," followed by the sequential display of the transferred images. However, in this scheme, the smartwatch must be aligned with the NFC tag for cross-device interaction, resulting in a strong reliance on the NFC tag. The second scheme involves cross-device interaction via online chat. For example, if the smartwatch has a chat function, images from the smartwatch's gallery can be sent to contacts in the smartwatch's contact list via a chat application. However, in this scheme, the smartwatch must first enter the chat application and then select contacts and images, resulting in a deeper entry point for the operation. Furthermore, due to the small screen size of smartwatches, operation can be easily limited. It is evident that existing wearable devices (such as smartwatches) rely heavily on NFC tags or have deeply embedded operation interfaces when interacting with other terminal devices, resulting in poor user experience.

[0058] In view of this, embodiments of this application provide a cross-device interaction method for wearable devices. Without adding new hardware, the wearable device detects user operations by acquiring acceleration data measured by an inertial measurement unit (IMU). After detecting the user operation, in response to the user operation, it determines the target device with which the wearable device will interact across devices, and predicts the user's intention by determining the operating states of the wearable device and the target device, thereby realizing cross-device interaction between the wearable device and the target device. This not only avoids dependence on NFC tags, but also has a shallow operation entry point, making the operation less restricted and improving the user experience.

[0059] It should be understood that the technical solutions of the embodiments of this application can be applied to various communication systems, such as: Global System for Mobile Communications (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, LTE Frequency Division Duplex (FDD) system, LTE Time Division Duplex (TDD) system, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) communication system, 5th Generation (5G) system or New Radio (NR) system, and subsequent evolution communication systems, etc.

[0060] It should be understood that the terminal equipment in the embodiments of this application may also be referred to as user equipment (UE), mobile station (MS), mobile terminal (MT), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user device, etc.

[0061] Terminal devices can be devices that provide voice / data connectivity to users, such as handheld devices with wireless connectivity, in-vehicle devices, etc. Currently, examples of terminals include: mobile phones, tablets, laptops, PDAs, mobile internet devices (MIDs), wearable devices, virtual reality (VR) devices, augmented reality (AR) devices, wireless terminals in industrial control, wireless terminals in self-driving vehicles, wireless terminals in remote medical surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminal devices in 5G networks, or future public land mobile communication networks. Terminal devices in a network (PLMN), etc., are not limited to this in the embodiments of this application.

[0062] As an example and not a limitation, in this application embodiment, wearable devices can also be called wearable smart devices. This is a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those that are feature-rich, large in size, and can achieve complete or partial functionality without relying on a smartphone, such as smartwatches or smart glasses, as well as those that focus on a specific application function and require use with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0063] Furthermore, in this embodiment of the application, the terminal device can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of the future development of information technology. Its main technical feature is to connect objects to the network through communication technology, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection.

[0064] The various terminal devices described above, if located in a vehicle (e.g., placed inside or installed inside a vehicle), can be considered as vehicle-mounted terminal devices, also known as on-board units (OBUs).

[0065] It should be understood that the technical solutions of the embodiments of this application can be applied to a cross-device interaction system for wearable devices. The following uses a smartwatch as an example to briefly describe the structure of the cross-device interaction system for wearable devices to which the embodiments of this application can be applied, to facilitate understanding of the technical solutions by those skilled in the art. For example, as shown below... Figure 1 The diagram shown is a structural schematic of a cross-device interaction system for wearable devices provided in an embodiment of this application. This system includes a smartwatch 110, a mobile phone 120, a smart lamp 130, and a smart speaker 140. The mobile phone 120, smart lamp 130, and smart speaker 140 are authorized devices of the smartwatch 110; that is, they are devices associated with or authorized by the smartwatch 110. Association can occur through user login with the same account, or through different accounts that are associated, such as those corresponding to the same identity verification information, or those accounts being mutually bound. Alternatively, users can log in with different accounts that are within the same wireless local area network, the same Bluetooth network, or unassociated accounts connected directly via WiFi.

[0066] It should be noted that, in the embodiments of this application, Figure 1 The cross-device interaction system of the wearable device shown can also include more or fewer nodes, such as other terminal devices. Figure 1 The terminal devices included in the application scenarios shown can be the various forms of terminal devices described above. The embodiments of this application... Figure 1 They will not be shown one by one in the text.

[0067] The above describes a cross-device interaction system for wearable devices provided by embodiments of this application. Next, with reference to the accompanying drawings, a cross-device interaction method for wearable devices provided by embodiments of this application will be described.

[0068] It should be understood that the terms "first" and "second" in the embodiments of this application are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. "At least one" refers to one or more, and "more" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships may exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, or a and b and c.

[0069] like Figure 2 The diagram shown is a flowchart illustrating a cross-device interaction method for wearable devices provided in an embodiment of this application. This cross-device interaction method for wearable devices can be applied to... Figure 1 The shown or the Figure 1 This application does not impose specific limitations on cross-device interaction systems for wearable devices with similar functional structures. The specific flow of the cross-device interaction method for wearable devices is described below. It should be understood that in this application embodiment, the method is described using a wearable device as the execution subject as an example. As an example and not a limitation, the execution subject of the method can also be a chip, chip system, or processor applied to the wearable device.

[0070] S201, The wearable device detects a first operation; wherein the first operation is used to instruct the wearable device to initiate cross-device interaction.

[0071] In some embodiments, when detection conditions are met, the wearable device can first acquire acceleration data measured by its IMU and then filter the acceleration data. The detection conditions include the wearable device being in motion, the wearable device having its screen on, or the wearable device identifying an authorized device within a preset range. The authorized device is a device associated with or authorized by the wearable device; for example, the authorized devices for the smartwatch 110 could be a mobile phone 120, a smart lamp 130, and a smart speaker 140. Then, the filtered acceleration data within a preset time period is acquired, and it is determined whether the filtered acceleration data within the preset time period matches preset acceleration data. Specifically, the filtered acceleration data is captured through a preset sliding window, and the match between the filtered acceleration data within the preset sliding window and the preset acceleration data is determined. The preset sliding window is a window that slides across the filtered acceleration data within a preset time period to obtain filtered acceleration data for different time periods. If a match is successful, a first operation is detected. The first operation is used to instruct the wearable device to initiate cross-device interaction.

[0072] It should be noted that, in the embodiments of this application, the first operation can be a user wearing a wearable device performing a continuous tapping gesture on any spatial point, wherein the number of continuous taps is not less than a first preset threshold, for example, the first preset threshold is 2.

[0073] For example, if the first preset threshold is 2, the first operation is that the user wears the smartwatch 110 and performs a continuous tapping gesture on any spatial point; wherein, the number of continuous taps can be two (one tap), three (one tap one tap), or four (one tap one tap one tap), and the direction of the continuous taps can be downward, upward, or leftward. This application embodiment does not limit this, but for ease of explanation, we take two downward continuous taps as an example.

[0074] It should be noted that, in this embodiment, the IMU of the wearable device includes three single-axis accelerometers and three single-axis gyroscopes. The gyroscopes measure the angular velocity data of the wearable device relative to the navigation coordinate system, and the accelerometers measure the acceleration data of the wearable device along three independent axes in the carrier coordinate system, such as the acceleration data a along the x-axis. x y-axis acceleration data a y acceleration data along the z-axis a z This allows us to obtain angular velocity and acceleration data of wearable devices in three-dimensional space, such as acceleration data of wearable devices in three-dimensional space. This allows us to calculate the posture of the wearable device.

[0075] For example, the smartwatch 110 acquires acceleration data 'a' measured by its IMU and filters the acceleration data 'a', such as by using a high-pass or band-pass filter to remove noise, resulting in filtered acceleration data 'a'. A preset sliding window is used to extract the filtered acceleration data 'a', i.e., a preset time period is used as the window to slide across the filtered acceleration data 'a', resulting in filtered acceleration data 'a″' for different time periods. The size of the time period can be adjusted empirically. Machine learning methods are used to identify the filtered acceleration data 'a″ within the preset sliding window, determining whether it corresponds to the acceleration data of the first operation. This identification process includes, but is not limited to, traditional classification models, deep learning, and threshold judgment, such as comparing the filtered acceleration data 'a″ within the preset sliding window with the preset acceleration data 'a'. * Whether it matches; if it is determined that the filtered acceleration data a″ in the preset sliding window is the acceleration data corresponding to the first operation, then the smartwatch 110 detects the first operation, that is, it detects that the user is wearing the smartwatch 110 and performs a continuous patting gesture operation on any spatial point twice, thereby starting the cross-device interaction of the smartwatch 110.

[0076] Specifically, when a wearable device determines whether the filtered acceleration data within a preset time period (such as a preset sliding window) matches preset acceleration data, it first needs to determine the preset sub-time periods included in the preset time period, and then sort the acceleration data corresponding to the preset sub-time periods according to time sequence. The number of preset sub-time periods is twice the number of consecutive taps. Next, it determines whether the filtered acceleration data within the even-numbered preset sub-time periods matches the first preset acceleration data, where the first preset acceleration data is the acceleration data corresponding to the user's tapping gesture at any spatial point. If the filtered acceleration data within a preset sub-time period with an even-numbered sequence number successfully matches the first preset acceleration data, then it is determined whether the filtered acceleration data within a preset sub-time period with an odd-numbered sequence number matches the second preset acceleration data. The second preset acceleration data is the acceleration data corresponding to the user's slapping gesture operation at any spatial point before the slapping gesture, and includes two sub-acceleration data. One sub-acceleration data represents the acceleration data corresponding to the user's first slapping gesture operation at any spatial point, and the other represents the acceleration data corresponding to the time between two slapping gesture operations at any spatial point. If the filtered acceleration data within a preset sub-time period with an odd-numbered sequence number successfully matches any of the sub-acceleration data included in the second preset acceleration data, the wearable device determines that the filtered acceleration data within the preset time period successfully matches the preset acceleration data, and thus determines that the first operation has been detected.

[0077] For example, such as Figure 3a The diagram shown is a schematic representation of a preset sliding window provided in an embodiment of this application. Figure 3a The preset sliding window includes four preset sliding sub-windows: preset sliding sub-window ①, preset sliding sub-window ②, preset sliding sub-window ③, and preset sliding sub-window ④. The smartwatch 110 compares the filtered acceleration data a″ within the preset sliding window with the preset acceleration data a. * When checking for a match, first determine whether the filtered acceleration data a″2 in the preset sliding sub-window ② and the filtered acceleration data a″4 in the preset sliding sub-window ④ match the first preset acceleration data. If they match, then the filtered acceleration data a″2 in the preset sliding sub-window ② is determined to be the acceleration data corresponding to the user's first tapping gesture operation at any spatial point, and the filtered acceleration data a″4 in the preset sliding sub-window ④ is the acceleration data corresponding to the user's second tapping gesture operation at any spatial point. Since it is subjectively considered that there is a pause between the two tapping gesture operations (preset sliding sub-window ② and preset sliding sub-window ④), and the first tapping gesture operation (preset sliding sub-window ②) is relatively smooth, the filtered acceleration data a″1 in the preset sliding sub-window ① and the filtered acceleration data a″3 in the preset sliding sub-window ③ are then compared with the second preset acceleration data. If any of the included sub-accelerometer data matches, the smartwatch detects the first operation, that is, it detects that the user is wearing the smartwatch 110 and performs a continuous tapping gesture on any spatial point twice, thereby initiating the cross-device interaction of the smartwatch 110.

[0078] It should be noted that, in this embodiment, since the wearable device cannot accurately detect the first operation solely based on the acceleration data measured by its IMU, the first operation can be detected by combining the audio data measured by the wearable device's microphone, thereby improving the detection accuracy or detecting the material of the object being struck. Specifically, when determining whether the filtered acceleration data within an even-numbered preset sub-time period (such as a preset sliding sub-window) matches the first preset acceleration data, it can be determined whether the filtered acceleration data within an even-numbered first preset sub-time period matches the first preset acceleration data. If they match, the wearable device's microphone is activated, and it is determined whether there is corresponding audio data for the filtered acceleration data within an even-numbered second preset sub-time period. If there is corresponding audio data, the audio data corresponding to the filtered acceleration data within an even-numbered preset sub-time period after the even-numbered first preset sub-time period is obtained. It is then determined whether the filtered acceleration data within an even-numbered preset sub-time period after the even-numbered first preset sub-time period matches the first preset acceleration data, and whether the audio data matches the preset audio data. The preset acceleration data and preset audio data are data collected in advance through multiple experiments or calculated through data models.

[0079] For example, the smartwatch 110 determines the filtered acceleration data a″2 in the preset sliding sub-window ② and the filtered acceleration data a″4 in the preset sliding sub-window ④, and compares them with the first preset acceleration data. When checking for a match, you can first determine whether the filtered acceleration data a″2 within the preset sliding sub-window ② matches the first preset acceleration data. If a match is found, the microphone of the smartwatch 110 is activated. It is then checked whether the filtered acceleration data a″4 within the preset sliding sub-window ④ has a corresponding audio data b. If so, the audio data b corresponding to the filtered acceleration data a″4 within the preset sliding sub-window ④ is obtained. Finally, the filtered acceleration data a″4 within the preset sliding sub-window ④ is compared with the first preset acceleration data... Whether they match, and the audio data b corresponding to the filtered acceleration data a″4 within the preset sliding sub-window ④ and the preset audio data b. * Does it match?

[0080] S202, In response to the first operation, the wearable device determines the target device with which it will interact across devices.

[0081] In some embodiments, after detecting the first operation, the wearable device can, in response to the first operation, determine the target device with which it will interact across devices. Specifically, in response to the first operation, the wearable device first sends a communication broadcast to the authorized device and determines the distance between the authorized device receiving the communication broadcast and the wearable device. For example, the distance between the authorized device receiving the communication broadcast and the wearable device can be determined via Bluetooth, ultra-wideband (UWB), or ultrasound. Then, it is determined whether the number of authorized devices whose distance meets a preset condition is not less than a third preset threshold. The preset condition can be a distance not greater than a fourth preset threshold or a minimum distance; this embodiment is not limited to this, but for ease of explanation, a distance not greater than the fourth preset threshold is used as an example. If the number of authorized devices that meet the preset conditions is less than the third preset threshold, a dialog box will be displayed indicating that there is currently no suitable target device. If the number of authorized devices that meet the preset conditions is equal to the third preset threshold, then the authorized devices that meet the preset conditions will be identified as target devices. If the number of authorized devices that meet the preset conditions is greater than the third preset threshold, then the priority of the authorized devices that meet the preset conditions will be determined based on the distance, and the authorized device with the highest priority and that meets the preset conditions will be identified as the target device. Alternatively, a dialog box will be displayed to select a target device from the authorized devices that meet the preset conditions, and the target device will be identified based on the information obtained from the dialog box.

[0082] For example, in response to the first operation, the smartwatch 110 sends a communication broadcast to the mobile phone 120, the smart lamp 130, and the smart speaker 140. The mobile phone 120 and the smart lamp 130 receive the communication broadcast, while the smart speaker 140 does not. The smartwatch 110 determines via Bluetooth that the distances between the mobile phone 120 and the smart lamp 130 that received the communication broadcast and the smartwatch 110 are 80cm and 90cm, respectively.

[0083] If the third preset threshold is 1 and the fourth preset threshold is 85cm, and the distance between the mobile phone 120 and the smartwatch 110 is greater than 85cm, then the number of authorized devices whose distance meets the preset conditions is 1, and the mobile phone 120 can be identified as the target device.

[0084] If the third preset threshold is 1 and the fourth preset threshold is 100cm, and the distance between the mobile phone 120 and the smart lamp 130 and the smartwatch 110 is no more than 100cm, then the number of authorized devices that meet the preset conditions is 2. The priority of the mobile phone 120 and the smart lamp 130 can be determined as the first priority and the second priority respectively based on the distance between the mobile phone 120 and the smart lamp 130 and the smartwatch 110, and then the mobile phone 120 can be determined as the target device. Alternatively, a dialog box can be displayed to select the target device from the mobile phone 120 and the smart lamp 130, and the mobile phone 120 or the smart lamp 130 can be determined as the target device based on the information obtained from the dialog box.

[0085] It should be noted that, in the embodiments of this application, if the wearable device is running the first task and the number of trusted devices that meet the preset conditions is greater than the third preset threshold, the wearable device can determine whether the trusted devices that meet the preset conditions can run the first task, and determine the priority of the trusted devices that meet the preset conditions based on the judgment result and the distance, and determine the trusted device with the highest priority and the distance that meets the preset conditions as the target device.

[0086] For example, if the smartwatch 110 is running the first task, the third preset threshold is 1, the fourth preset threshold is 100cm, and the distance between the mobile phone 120 and the smart lamp 130 and the smartwatch 110 is no more than 100cm, then the number of authorized devices whose distance meets the preset conditions is 2. It can be determined whether the mobile phone 120 and the smart lamp 130 can run the first task. If both the mobile phone 120 and the smart lamp 130 can run the first task, then based on the distance between the mobile phone 120 and the smart lamp 130 and the smartwatch 110, the priorities of the mobile phone 120 and the smart lamp 130 are determined to be the first priority and the second priority, respectively, thus determining the mobile phone 120 as the target device. If the mobile phone 120 can run the first task, but the smart lamp 130 cannot run the first task, then the priorities of the mobile phone 120 and the smart lamp 130 are determined to be the first priority and the second priority, respectively, thus determining the mobile phone 120 as the target device.

[0087] S203. The wearable device determines the operating status of the wearable device and the target device.

[0088] In some embodiments, in response to a first operation, after determining a target device with which the wearable device will interact across devices, the wearable device can determine the operating state of both the wearable device and the target device. The operating state indicates whether the wearable device is running a task (such as a first task), whether the target device is capable of running the first task, whether the target device is running a task (such as a second task), and whether the wearable device is capable of running the second task.

[0089] S204. Wearable devices perform corresponding cross-device interactions based on their operating status.

[0090] In some embodiments, after determining the operating states of the wearable device and the target device, the wearable device can determine the cross-device interaction content based on the operating states of the wearable device and the target device, and perform corresponding cross-device interactions with the target device based on the cross-device interaction content. The cross-device interaction content is used to indicate the tasks performed and / or the information displayed when the wearable device interacts with the target device in different operating states.

[0091] It should be noted that, in this embodiment, cross-device interaction includes any one of task continuation, data synchronization, capability assistance, and device control. Task continuation is used to instruct the wearable device to control the target device to run a task currently being run by the wearable device, or the target device to control the wearable device to run a task currently being run by the target device. For example, the wearable device can control a smart speaker to play a song currently being played by the wearable device. Data synchronization is used to instruct the wearable device to send information about the task currently being run by the wearable device to the target device, or the target device to send information about the task currently being run by the target device to the wearable device. For example, the wearable device can send an image currently displayed by the wearable device to a mobile phone. Capability assistance is used to instruct the wearable device to display information about the task currently being run by the target device, or the target device to display information about the task currently being run by the wearable device. For example, the wearable device can display the lyrics of a song currently being played by the smart speaker, and then control the progress of the song being played by the smart speaker when a user performs a swipe gesture on the lyrics. Device control is used to instruct the wearable device to display control information from the target device, or the target device to display control information from the wearable device. For example, the wearable device can display the control panel of a smart desk lamp, and then, when it detects a user's click gesture on a control option in the control panel, it controls the smart desk lamp to execute that control option. The executor and the executed party in task continuation, data synchronization, capability cooperation, and device control can be determined based on the priority of the wearable device and the target device, or the user's selection. For ease of explanation, the following example uses the wearable device as the executor and the target device as the executed party.

[0092] Specifically, if the operating status of the wearable device and the target device indicates that the wearable device is running a first task, and the target device is capable of running the first task, then the cross-device interaction content is determined to be task continuation or data synchronization. For example, if the target device is a mobile phone 120, and the smartwatch 110 is playing a song, and the mobile phone 120 is also capable of playing a song, then the cross-device interaction content can be determined to be that the smartwatch 110 controls the mobile phone 120 to play the song that the smartwatch 110 is playing, i.e., task continuation. Or, if the target device is a mobile phone 120, and the smartwatch 110 is displaying an image or call log, and the mobile phone 120 is also capable of displaying an image or call log, then the cross-device interaction content can be determined to be that the smartwatch 110 sends the displayed image or call log to the mobile phone 120, i.e., data synchronization. For example, such as... Figure 3b The diagram illustrates a cross-device interaction provided in this application embodiment. The smartwatch 110 is displaying the call log of an incoming call from "186……5212" in Qingdao, Shandong. Specifically, it displays the caller information, including the caller number ("186……5212"), the location of the number (Qingdao, Shandong), and the call time (18:33). The smartphone sends this call log to the mobile phone 120, so that the call log of the incoming call from "186……5212" in Qingdao, Shandong is also stored in the call log of the mobile phone 120, including the caller number (186……5212), the location of the number (Qingdao, Shandong), and the call time (18:33).

[0093] If the operating status of the wearable device and the target device indicates that the wearable device is running a first task, the target device cannot run the first task, and the target device is running a second task; or, the wearable device is not running a first task (i.e., the wearable device has no running task), and the target device is running a second task, then the cross-device interaction content is determined to be capability assistance, device control, or both. For example, if the target device is a smart speaker 140, and the smartwatch 110 is displaying an image, the smart speaker 140 cannot display an image, and the smart speaker 140 is playing a song; or, the smartwatch 110 has no running task, and the smart speaker 140 is playing a song, then the cross-device interaction content can be determined to be that the smartwatch 110 displays the lyrics of the song played by the smart speaker 140, and then when the smartwatch 110 detects a user swiping gesture on the lyrics, it controls the progress of the song played by the smart speaker 140, i.e., capability assistance. Alternatively, the smartwatch 110 can display the control panel of the smart speaker 140. When the smartwatch 110 detects a preset gesture (such as a tap) performed by the user on a control option within the control panel, it controls the smart speaker 140 to execute that control option, i.e., device control. Alternatively, the smartwatch 110 can display the lyrics of the song being played by the smart speaker 140 and the control panel of the smart speaker 140. When the smartwatch 110 detects a preset gesture (such as a swipe) performed by the user on the lyrics, it controls the progress of the song being played by the smart speaker 140. Similarly, when the smartwatch 110 detects a preset gesture (such as a tap) performed by the user on a control option within the control panel, it controls the smart speaker 140 to execute that control option, i.e., capability assistance and device control.

[0094] For example, such as Figure 3c The diagram illustrates another cross-device interaction method provided in this application embodiment. The smartwatch 110 displays information about the song being played on the smart speaker 140 on the first-level page, including the song title, artist, lyrics, and other relevant information, as well as the Bluetooth and song control panel of the smart speaker 140, specifically displaying the speaker's Bluetooth button and song playback control button. When the smartwatch 110 detects a user's click gesture on the speaker's Bluetooth button, it displays the smart speaker 140's Bluetooth control panel on the second-level page, specifically displaying Bluetooth control options such as the Bluetooth button (which prevents Bluetooth from being switched on / off via the app after the speaker is disconnected from the network) and the Bluetooth connection prompt button (which provides a prompt when Bluetooth is connected).

[0095] If the operating status of the wearable device and the target device indicates that the wearable device is running a first task, the target device cannot run the first task, and the target device is not running a second task, or the wearable device is not running a first task and the target device is not running a second task, then the cross-device interaction content is determined to be device control. For example, if the target device is a smart lamp 130, and the smart watch 110 is playing a song, but the smart lamp 130 cannot play a song, and the smart lamp 130 is not running a task, or the smart watch 110 is not running a task and the smart lamp 130 is not running a task, then the cross-device interaction content can be determined to be that the smart watch 110 displays the control panel of the smart lamp 130, such as adjusting the color temperature of the smart lamp.

[0096] For example, such as Figure 3d The diagram shown is a schematic representation of another type of cross-device interaction provided in an embodiment of this application. Figure 3dAfter the smartwatch 110 detects that the user is wearing the smartwatch 110 and performs a double-tapping gesture at any spatial point, it sends a communication broadcast to an authorized device (such as a mobile phone 120, a smart lamp 130, or a smart speaker 140). Upon receiving the communication broadcast, the authorized device (such as a mobile phone 120, a smart lamp 130, or a smart speaker 140) determines the distance between itself and the smartwatch 110, and then determines whether a target device exists for cross-device interaction with the smartwatch 110. If no target device exists for cross-device interaction, the smartwatch 110 displays a "No target device found" dialog box. If a target device exists for cross-device interaction, the smartwatch 110 determines whether it is currently running a first task. If the smartwatch 110 is running the first task, it determines whether the target device (such as the mobile phone 120, smart lamp 130, or smart speaker 140) can run the first task. If the target device (such as the mobile phone 120) can run the first task, the cross-device interaction between the smartwatch 110 and the target device (such as the mobile phone 120) is task continuation or data synchronization. If the smartwatch 110 is not running the first task, or if the smartwatch 110 is running the first task but the target device (such as the mobile phone 120, smart lamp 130, or smart speaker 140) cannot run the first task, it determines whether the target device (such as the mobile phone 120, smart lamp 130, or smart speaker 140) is running a second task. If the target device (such as the smart lamp 130) is running the second task, the cross-device interaction between the smartwatch 110 and the target device (such as the smart lamp 130) running the second task is capability assistance or device control, or capability assistance and device control. If the target device (such as smart speaker 140) is not running a second task, the cross-device interaction between smartwatch 110 and the target device (such as smart speaker 140) that is not running a second task is device control.

[0097] The above technical solution allows the wearable device to, upon detecting a first operation instructing it to initiate cross-device interaction, first determine the target device for cross-device interaction, and then determine the operating states of both the wearable and target devices. The operating states indicate whether the wearable device is running a first task, whether the target device is capable of running the first task, whether the target device is running a second task, and whether the wearable device is capable of running the second task. The wearable device then performs the corresponding cross-device interaction based on these operating states. This allows the wearable device to determine the target device for cross-device interaction after detecting the first operation, and predict user intent by determining the operating states of both devices, thus achieving cross-device interaction between the wearable and target devices. This not only avoids reliance on NFC tags but also provides a shallower entry point, making operation less restrictive and improving the user experience. The above embodiments can be used individually or in combination to achieve different technical effects.

[0098] The methods provided in the embodiments of this application above are described from the perspective of wearable devices as the executing entity. To implement the functions of the methods provided in the embodiments of this application above, the wearable device may include hardware structures and / or software modules, implementing the above functions in the form of hardware structures, software modules, or a combination of hardware structures and software modules. Whether a particular function is implemented in the form of hardware structures, software modules, or a combination of hardware structures and software modules depends on the specific application and design constraints of the technical solution.

[0099] Based on the same technical concept, embodiments of this application also provide a wearable device. For example, as shown... Figure 4 As shown, the wearable device 400 may include:

[0100] At least one processor 401; and a communication interface 403 communicatively connected to the at least one processor 401;

[0101] The at least one processor 401 causes the wearable device 400 to perform operations by executing instructions stored in the memory 402. Figure 2 , Figures 3a-3d The method shown.

[0102] Optionally, the memory 402 is located outside the wearable device 400.

[0103] Optionally, the wearable device 400 includes the memory 402, which is connected to the at least one processor 401, and stores instructions executable by the at least one processor 401. (Appendix) Figure 4The dashed line indicates that memory 402 is optional for wearable device 400.

[0104] The processor 401 and the memory 402 can be coupled through an interface circuit or integrated together; no restriction is imposed here.

[0105] This application embodiment does not limit the specific connection medium between the processor 401, memory 402, and communication interface 403. This application embodiment... Figure 4 The processor 401, memory 402, and communication interface 403 are connected via a bus 404. Figure 4 The connections between other components are shown in bold and are for illustrative purposes only, not as limiting information. The bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, Figure 4 The bus is represented by a single thick line, but this does not mean that there is only one bus or one type of bus.

[0106] It should be understood that the processor mentioned in the embodiments of this application can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0107] For example, the processor can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor can be a microprocessor or any conventional processor.

[0108] It should be understood that the memory mentioned in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0109] It should be noted that, in the embodiments of this application, when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, or discrete hardware component, the memory (storage module) can be integrated into the processor.

[0110] It should be noted that the memories described herein are intended to include, but are not limited to, these and any other suitable types of memories.

[0111] Based on the same technical concept, embodiments of this application also provide a computer storage medium, including computer instructions, which, when executed on a computer, cause... Figure 2 , Figures 3a-3d The method shown was executed.

[0112] Based on the same technical concept, embodiments of this application also provide a chip, said chip being coupled to a memory for reading and executing program instructions stored in the memory, such that... Figure 2 , Figures 3a-3d The method shown was executed.

[0113] Based on the same technical concept, embodiments of this application also provide a computer program product, which, when run on a computer, enables such... Figure 2 , Figures 3a-3d The method shown was executed.

[0114] It should be understood that all relevant content of each step involved in the above method embodiments can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0115] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0116] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to this application. It should be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0117] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0118] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

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

Claims

1. A cross-device interaction method for wearable devices, characterized in that, include: The wearable device detects a first operation; wherein the first operation is used to instruct the wearable device to initiate cross-device interaction; In response to the first operation, the wearable device determines the target device with which it will interact across devices; The wearable device determines the operating status of the wearable device and the target device; wherein, the operating status is used to indicate whether the wearable device is running a first task, whether the target device is able to run the first task, whether the target device is running a second task, and whether the wearable device is able to run the second task; The wearable device determines the cross-device interaction content based on the operating state, and performs corresponding cross-device interactions with the target device based on the cross-device interaction content; wherein, the cross-device interaction content includes any one of data synchronization, capability assistance, and device control.

2. The method as described in claim 1, characterized in that, The first operation includes a user performing a continuous tapping gesture on any spatial point; wherein the number of continuous taps is not less than a first preset threshold.

3. The method as described in claim 2, characterized in that, The wearable device detects a first operation, including: The wearable device acquires acceleration data when detection conditions are met; wherein, the detection conditions are that the wearable device is in motion, or the wearable device is in a screen-on state, or the wearable device identifies an authorized device within a preset range, and the authorized device is a device associated with the wearable device or a device authorized by the wearable device. The wearable device acquires the acceleration data within a preset time period and determines whether the acceleration data within the preset time period matches the preset acceleration data. If the match is successful, the wearable device detects the first operation and stops acquiring the wearable device's acceleration data.

4. The method as described in claim 3, characterized in that, The step of determining whether the acceleration data within the preset time period matches preset acceleration data includes: The wearable device determines the preset sub-time periods included in the preset time period, and sorts the acceleration data corresponding to the preset sub-time periods in chronological order; wherein, the number of preset sub-time periods is twice the number of consecutive taps; The wearable device determines whether the acceleration data within the preset sub-time period with an even-numbered sequence number matches the first preset acceleration data; wherein, the first preset acceleration data is the acceleration data corresponding to when the user performs a patting gesture operation on any spatial point; If a match is successful, the wearable device determines whether the acceleration data within the preset sub-time period with an odd sequence number matches the second preset acceleration data; wherein, the second preset acceleration data is the acceleration data corresponding to the user's patting gesture operation on any spatial point before the user performs the patting gesture operation.

5. The method as described in claim 4, characterized in that, The determination of whether the acceleration data within the preset sub-time period with an even sequence number matches the first preset acceleration data includes: The wearable device determines whether the acceleration data within the first preset sub-time period with an even number matches the first preset acceleration data; If a match is found, the wearable device activates its microphone to determine whether there is corresponding audio data for the acceleration data within the second preset sub-time period with an even-numbered sequence number. If there is corresponding audio data, the wearable device acquires the audio data corresponding to the acceleration data within the preset sub-time period with an even number after the first preset sub-time period with an even number. The wearable device determines whether the acceleration data within the preset sub-time period with an even number after the first preset sub-time period with an even number matches the first preset acceleration data, and whether the audio data matches the preset audio data.

6. The method according to any one of claims 3-5, characterized in that, The wearable device identifies target devices with which it interacts across devices, including: The wearable device sends a communication broadcast to the authorization device and determines the distance between the authorization device and the wearable device upon receiving the communication broadcast; The wearable device determines whether the number of authorized devices whose distance meets the preset conditions is not less than a third preset threshold. If the number is equal to the third preset threshold, then the wearable device determines the authorized device whose distance satisfies the preset condition as the target device; If the number is greater than the third preset threshold, the wearable device determines the priority of the authorized device whose distance meets the preset condition based on the distance, and determines the authorized device with the highest priority whose distance meets the preset condition as the target device; or, displays a dialog box to select the target device from the authorized devices whose distance meets the preset condition, and determines the target device based on the information obtained from the dialog box.

7. The method as described in claim 6, characterized in that, If the operating status indicates that the wearable device is running the first task, after determining whether the number of authorized devices whose distance meets the preset condition is not less than a third preset threshold, the method further includes: If the number is greater than the third preset threshold, the wearable device determines whether the authorized device whose distance meets the preset condition can run the first task; The wearable device determines the priority of the authorized device whose distance meets the preset condition based on the judgment result and the distance, and determines the authorized device with the highest priority whose distance meets the preset condition as the target device.

8. The method as described in claim 7, characterized in that, The data synchronization is used to instruct the wearable device to send relevant information about the task it is running to the target device, or the target device to send relevant information about the task it is running to the wearable device; the capability assistance is used to instruct the wearable device to display relevant information about the task it is running to the target device, or the target device to display relevant information about the task it is running to the wearable device. The device control is used to instruct the wearable device to display the control information of the target device, or for the target device to display the control information of the wearable device.

9. The method as described in claim 8, characterized in that, The wearable device determines the cross-device interaction content based on the operating state, including: If the running status indicates that the wearable device is running the first task, and the target device is capable of running the first task, then the wearable device determines that the cross-device interaction content is the data synchronization; If the running status indicates that the wearable device is running the first task, the target device cannot run the first task, and the target device is running the second task, or the wearable device is not running the first task, and the target device is running the second task, then the wearable device determines that the cross-device interaction content is the capability assistance or the device control or the capability assistance and the device control. If the operating status indicates that the wearable device is running the first task, the target device is unable to run the first task, and the target device is not running the second task, or if the wearable device is not running the first task and the target device is not running the second task, then the wearable device determines that the cross-device interaction content is device control.

10. A wearable device, characterized in that, include: At least one processor and memory; The memory stores one or more computer programs; When one or more computer programs stored in the memory are executed by the at least one processor, the wearable device performs the method as described in any one of claims 1-9.

11. A computer storage medium, characterized in that, The computer storage medium includes a computer program that, when run on a computer, causes the computer to perform the method as described in any one of claims 1-9.

Images