Communication method, wearable device, and computer-readable storage medium

Abstract

The application relates to the technical field of smart wear, and provides a communication method, a wearable device and a computer readable storage medium. The communication method is applied to the wearable device, the wearable device is in communication connection with an electronic device, and the communication method comprises the following steps: receiving a first message sent by the electronic device, wherein the first message is used for representing an audio interaction event received by the electronic device; in response to the first message, identifying a head action event of a wearer of the wearable device; and sending an event identifier corresponding to the head action event to the electronic device, wherein the event identifier is used for instructing the electronic device to respond to the audio interaction event based on the head action event. Therefore, the user does not need to manually operate the wearable device or make any voice input, and can complete the response of the audio interaction event only by a head action, thereby liberating the hands, avoiding mis-touch, and improving the response timeliness of the audio interaction event.

Description

Technical Field

[0001] This application belongs to the field of smart wearable technology, and in particular relates to communication methods, wearable devices and computer-readable storage media. Background Technology

[0002] With the development of smart wearable technology, wearable devices (such as smart glasses and smartwatches) are gradually integrating communication functions, enabling them to establish communication connections with electronic devices (such as smartphones and tablets) and receive notifications of audio interaction events such as incoming calls and voice calls.

[0003] In existing technologies, wearable devices respond to audio interaction events based on user actions (such as clicks or swipes) after receiving notifications of such events. However, this is inconvenient in scenarios where hands are occupied, such as during exercise or driving, and is prone to accidental touches, thus affecting the user experience. Summary of the Invention

[0004] A first aspect of this application provides a communication method applied to a wearable device, wherein the wearable device is communicatively connected to an electronic device, the method comprising: Receive a first message sent by the electronic device, the first message being used to characterize an audio interaction event received by the electronic device; In response to the first message, head movement events of the wearer of the wearable device are identified; Send an event identifier corresponding to the head movement event to the electronic device, the event identifier being used to instruct the electronic device to respond to the audio interaction event based on the head movement event.

[0005] In one scenario, sending an event identifier corresponding to the head movement event to the electronic device includes: Send a first event identifier to the electronic device, the first event identifier being used to indicate whether the electronic device agrees to respond to the audio interaction event or refuses to respond to the audio interaction event.

[0006] In one case, the first event identifier is the event identifier of a nodding event or a head-shaking event.

[0007] In one scenario, sending an event identifier corresponding to the head movement event to the electronic device includes: Send a second event identifier to the electronic device, the second event identifier being used to instruct the electronic device to maintain a waiting state for the audio interaction event or to execute a preset default action.

[0008] In one scenario, in response to the first message, identifying head movement events of the wearable device wearer includes: In response to the first message, the posture recognition mode is activated, head movement data is collected through the sensors of the wearable device, and head movement events of the wearer are identified based on the head movement data. or, In response to the first message, a collection time window is opened to acquire head motion data within the collection time window, and head movement events of the wearable device wearer are identified based on the head motion data.

[0009] In one scenario, head movement events of the wearable device wearer are identified based on the head movement data, including: The head posture data at each moment is obtained based on the head movement data; The head's posture change data are determined based on the posture data at each time point; The head movement event is determined based on the posture change data and preset matching data.

[0010] In one scenario, head posture data at various moments is obtained based on the head motion data, including: The head motion data is then filtered. The posture data at each moment is obtained based on the filtered head motion data.

[0011] In one scenario, the audio interaction event is any one of a voice call request, a video call request, or a voice broadcast.

[0012] A second aspect of this application provides a communication device, including: A receiving module is configured to receive a first message sent by the electronic device, wherein the first message is used to characterize an audio interaction event received by the electronic device; The recognition module is used to recognize head movement events of the wearer of the wearable device in response to the first message; The sending module is used to send an event identifier corresponding to the head movement event to the electronic device, the event identifier being used to instruct the electronic device to respond to the audio interaction event based on the head movement event.

[0013] A third aspect of this application provides a wearable device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the communication method described in the first aspect above.

[0014] A fourth aspect of this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the communication method described in the first aspect above.

[0015] The fifth aspect of this application provides a computer program product that, when run on a wearable device, causes the wearable device to perform the communication method described in any one of the first aspects.

[0016] The beneficial effects of this application embodiment compared to the prior art are as follows: After the wearable device receives the first message representing an audio interaction event sent by the electronic device, it triggers the recognition of head movement events and sends the identifier of the recognized head movement event to the electronic device, instructing the electronic device to respond to the audio interaction event based on the head movement event. Therefore, the user does not need to manually operate the wearable device or perform any voice input; they can complete the response to the audio interaction event simply through head movements, freeing their hands, avoiding accidental touches, and improving the timeliness of response to audio interaction events. Attached Figure Description

[0017] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0018] Figure 1 This is a schematic diagram illustrating the implementation flow of a communication method provided in an embodiment of this application; Figure 2 This is a schematic diagram of a communication device provided in an embodiment of this application; Figure 3 This is a schematic diagram of the structure of the wearable device provided in the embodiments of this application. Detailed Implementation

[0019] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0020] It should be understood that, when used in this specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0021] It should also be understood that the terminology used in this specification is for the purpose of describing particular embodiments only and is not intended to limit the scope of the application. As used in this specification and the appended claims, the singular forms “a,” “an,” and “the” are intended to include the plural forms unless the context clearly indicates otherwise.

[0022] It should also be further understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0023] As used in this specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrases "if determined" or "if [described condition or event] is detected" may be interpreted, depending on the context, as "once determined," "in response to determination," "once [described condition or event] is detected," or "in response to detection of [described condition or event]."

[0024] Furthermore, in the description of this application, the terms "first," "second," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0025] The communication method provided in this application is described below by way of example.

[0026] The communication method provided in this application is applied to wearable devices (such as smart glasses, smart helmets, smart headphones, etc.). The wearable device is equipped with a wireless communication module (such as a Bluetooth module or a Wi-Fi module), a sensor, and a main control unit. The wearable device communicates with electronic devices (such as mobile phones) through the wireless communication module, collects head movement data of the wearer through the sensor, and executes the following communication method through the main control unit.

[0027] Please see the appendix Figure 1 The communication method provided in one embodiment of this application includes S101 to S103.

[0028] S101: Receive a first message sent by an electronic device, the first message being used to characterize an audio interaction event received by the electronic device.

[0029] Specifically, after receiving an audio interaction event, the electronic device generates a first message based on the audio interaction event and sends the first message to the wearable device. The audio interaction event can be any of the following types: voice call request, video call request, voice broadcast, etc., enabling the wearable device to respond to various communication scenarios.

[0030] In one scenario, the first message carries a type identifier for the audio interaction event. The wearable device can identify the type of the audio interaction event based on the type identifier, and record the audio interaction event or display the corresponding notification interface on the wearable device's screen.

[0031] S102: In response to the first message, identify head movement events of the wearer of the wearable device.

[0032] Specifically, wearable devices are equipped with sensors (such as inertial measurement units). After receiving the first message, the wearable device acquires head motion data (such as angular velocity, acceleration, etc.) collected by the sensors and identifies head movement events of the wearable device wearer based on the head motion data.

[0033] For example, after acquiring head motion data, the wearable device obtains the head's attitude data at various times, including pitch, yaw, and roll angles. For instance, for the current moment, the acceleration is normalized to obtain the observed gravity vector. The gravity prediction vector for the current moment is calculated based on the attitude data from the previous moment. The cross product of the observed gravity vector and the gravity prediction vector is calculated to obtain the attitude error vector. The attitude error vector is converted into an angular velocity compensation value, which is then superimposed on the current angular velocity to obtain the fused angular velocity. The product of the fused angular velocity and the sampling period is the angle change at the current moment. The attitude data from the previous moment is updated based on the angle change at the current moment to obtain the attitude data for the current moment.

[0034] After obtaining posture data at multiple time points, head posture changes can be determined based on posture data at adjacent time points. By analyzing the amplitude, direction, and duration of these head posture changes, head movement events can be identified. Specifically, head movement events can be nodding events, head shaking events, or invalid movement events. Feature parameters (i.e., amplitude, direction, or duration of posture changes) corresponding to different head movement events are pre-stored as matching data. For example, the feature parameters for a nodding event are a pitch angle change amplitude between 10 and 30 degrees and a duration between 0.5 and 2 seconds; the feature parameters for a head shaking event are a yaw angle change amplitude between 15 and 40 degrees and a duration between 1 and 3 seconds. The matching data can be obtained by pre-collecting head movement data of the wearable device wearer. For example, during wearable device initialization, the wearer is instructed to nod or shake their head, while simultaneously collecting the wearer's head movement data. Matching data is generated based on the collected head movement data, allowing the matching data to be adapted to the wearer. In subsequent use, the wearable device can also record the wearer's head movement data based on the first message, use the recorded head movement data as historical head movement data, and then update the matching data based on the historical head movement data to improve the accuracy of subsequent matching.

[0035] After obtaining head posture change data, feature parameters are calculated for those in the matching data whose similarity to the head posture change data is greater than a threshold (e.g., 0.8). The head movement events corresponding to these feature parameters are the head movement events of the wearable device wearer. Specifically, the Euclidean distance or cosine similarity between each matching data point and the head posture change data can be used as the similarity between the matching data and the head posture change data.

[0036] In one scenario, if a head movement event determined based on head motion data is deemed invalid, a voice prompt message such as "Please nod or shake your head to confirm" can be output. After outputting the prompt message, head motion data can be re-acquired, thereby avoiding the problem of failure to respond to audio interaction events due to the failure to collect head motion data in a timely manner.

[0037] In one scenario, wearable devices can also input head motion data into a preset motion recognition model to obtain head motion events output by the motion recognition model.

[0038] In one scenario, after obtaining head motion data, the data is preprocessed to remove abnormal sampling points. For example, for each sampling point, the data deviation between that sampling point and its adjacent sampling points (e.g., one or more sampling points before and after it) is determined. If the data deviation exceeds a preset threshold, the sampling point is identified as an abnormal sampling point and removed from the head motion data. Next, the preprocessed head motion data is filtered to remove sensor-induced noise and data drift. For example, Kalman filtering or low-pass filtering can be used to filter the head motion data, resulting in filtered head motion data. Then, the head posture data at various times is determined based on the filtered head motion data, and head action events are determined based on the head posture data at various times. This improves the data quality of the obtained head motion data and the accuracy of the obtained head action events.

[0039] In one scenario, upon receiving a first message, the wearable device, in response, activates a posture recognition mode. This mode collects head movement data using the device's sensors and identifies head motion events of the wearer based on this data. This allows for triggering head movement data collection based on audio interaction events, reducing active operation steps and improving response efficiency to audio interaction events. The posture recognition mode is deactivated if the identified head motion event (nodding or shaking) is deemed a valid event, or if a preset data collection duration has been reached. Activating the posture recognition mode can be an operation that starts the sensors, and deactivating it can be an operation that shuts down the sensors. Activating the posture recognition mode upon receiving the first message, compared to continuous head movement data collection by the sensors, saves the wearable device's energy consumption.

[0040] In another embodiment, upon receiving the first message, the wearable device responds by opening a data acquisition time window, acquiring head motion data within the time window, and identifying head movement events of the wearer based on the head motion data. Specifically, the duration of the acquisition time window is T0 (e.g., between 3 and 10 seconds). The wearable device receives the first message at time T1, begins acquiring head motion data from time T1, and performs real-time analysis on the head motion data. The time window closes when the head movement event identified based on the head motion data is a valid event, or when time T1+T0 is reached. The acquisition time window ensures that the user can complete head movements, improving the real-time performance of head movement event detection. Furthermore, analyzing only the head motion data within the acquisition time window to obtain head movement events avoids false triggering caused by misidentification of user intent.

[0041] In one scenario, the wearable device determines the type of audio interaction event based on the type identifier carried in the first message, and sets different acquisition time windows for different audio interaction event types. For example, for audio interaction events of voice call requests and video call requests, a shorter acquisition time window is set to improve the response efficiency of audio interaction events. For voice broadcasts, a longer acquisition time window can be set to avoid misidentification of head movements and reduce the probability of false triggering.

[0042] In one scenario, the wearable device analyzes head movement data in real time. After initially identifying a valid action event based on the head movement data, if the same action event is identified again within a preset time period (less than the data acquisition time window), the identified valid action event is considered a head action event. If the same action event is not identified again within the preset time period, it is determined that no valid action event was identified. For example, if the first head action event identified based on the real-time collected head movement data is a nodding event, and a nodding event is identified again within the preset time period, then the head action event is determined to be a nodding event. If the first identified head action event is a nodding event, and a head shaking event or an invalid action event is identified again within the preset time period, then the head action event is determined to be an invalid action event. By identifying multiple head action events, false triggers caused by accidental head movements can be avoided.

[0043] S103: Send an event identifier corresponding to the head movement event to the electronic device, the event identifier being used to instruct the electronic device to respond to the audio interaction event based on the head movement event.

[0044] Specifically, after the wearable device recognizes a head movement event (nodding event, shaking event, or invalid movement event), it generates an event identifier corresponding to the head movement event and sends the event identifier to the electronic device. The electronic device then calls the communication control interface to execute the corresponding response event based on the pre-set correspondence between the event identifier and the response event (such as answering a call, rejecting a call, or holding on).

[0045] In one scenario, the event identifier is designated as a first event identifier, which indicates whether the electronic device agrees to respond to an audio interaction event (e.g., answering a call) or refuses to respond to an audio interaction event (e.g., rejecting a call). For example, the first event identifier could be the event identifier for a nodding or head-shaking event. For instance, when a wearable device detects a nodding event, it sends the event identifier (e.g., x1) corresponding to the nodding event to the electronic device, which then agrees to respond to the audio interaction event based on the event identifier. Similarly, when a wearable device detects a head-shaking event, it sends the event identifier (e.g., x2) corresponding to the head-shaking event to the electronic device, which then refuses to respond to the audio interaction event based on the event identifier. Mapping nodding events to agreeing to respond to audio interaction events and mapping head-shaking events to refusing to respond to audio interaction events aligns with users' body language habits and improves the convenience of voice interaction.

[0046] In one scenario, the event identifier is a second event identifier, which is the event identifier for an invalid action event. This indicates that the wearer of the wearable device has not responded to the audio interaction event. It instructs the electronic device to maintain a waiting state for the audio interaction event until a set timeout period is reached or to execute a preset default action, thus allowing the electronic device to flexibly handle situations where the user is unresponsive. For example, if the wearable device identifies a head movement event as an invalid action event based on head motion data, it sends a second event identifier to the electronic device. The electronic device does not perform any action based on the second event identifier, maintaining a waiting state for the audio interaction event. Alternatively, the electronic device executes a default action based on the second event identifier (such as agreeing to respond to the audio interaction event, refusing to respond to the audio interaction event, or lowering the notification volume of the audio interaction event).

[0047] In one scenario, if the event identifier of a head movement event is used to indicate that the electronic device agrees to respond to an audio interaction event, the electronic device performs the action of agreeing to respond to the audio interaction event (e.g., answering a phone call) and simultaneously establishes an audio link with the wearable device. The wearable device receives and plays the audio of the audio interaction event through the audio link, while simultaneously capturing the wearer's voice and sending it to the electronic device through the audio link, thus enabling the wearable device to respond to the audio interaction event.

[0048] In another embodiment, the wearable device can also send a request to establish an audio link to the electronic device after detecting head movement data, thereby establishing an audio link request with the electronic device in advance. When the electronic device receives the event identifier corresponding to the head movement event and responds to the audio interaction event according to the event identifier, it can directly respond to the audio interaction event on the wearable device through the already established audio stream, improving the response efficiency of the audio interaction event.

[0049] In one scenario, when the wearable device is recognizing a head movement event of the wearer based on the first message, if it receives a notification message for another audio interaction event (a second message), it temporarily stores the second message in a message queue. Simultaneously, the wearable device continues to recognize head movement events corresponding to the first message until a head movement event is recognized. Then, it retrieves the second message from the message queue and recognizes the wearer's head movement event based on the second message.

[0050] In one scenario, while the wearable device is in a call, if a second message is received, the electronic device can be instructed to play a notification tone to inform the user. Simultaneously, head motion data is detected, and head movement events are identified based on this data. An event identifier for each head movement event is sent to the electronic device. If the head movement event identifier indicates agreement to respond to the audio interaction event, the audio interaction event corresponding to the first message ends, and the wearable device responds to the audio interaction event corresponding to the second message. If the head movement event identifier indicates refusal to respond to the audio interaction event, the audio interaction event corresponding to the second message either ends directly or remains in a waiting state.

[0051] In this embodiment, after receiving a first message representing an audio interaction event from an electronic device, the wearable device triggers the recognition of head movement events and sends the identifier of the recognized head movement event to the electronic device, instructing the electronic device to respond to the audio interaction event based on the head movement event. Therefore, the user does not need to manually operate the wearable device or perform any voice input; they can complete the response to the audio interaction event simply through head movements, improving the response efficiency of the audio interaction event and the convenience of the wearable device's interaction.

[0052] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0053] Corresponding to the communication method described in the above embodiments, Figure 2 A structural block diagram of a communication device provided in an embodiment of this application is shown. For ease of explanation, only the parts related to the embodiments of this application are shown.

[0054] like Figure 2 As shown, the communication device includes: Receiving module 21 is used to receive a first message sent by the electronic device, the first message being used to characterize an audio interaction event received by the electronic device; The identification module 22 is used to identify head movement events of the wearer of the wearable device in response to the first message; The sending module 23 is used to send an event identifier corresponding to the head movement event to the electronic device, the event identifier being used to instruct the electronic device to respond to the audio interaction event based on the head movement event.

[0055] In one case, the sending module 23 is specifically used for: A first event identifier is sent to the electronic device, the first event identifier being used to indicate whether the electronic device agrees to respond to the audio interaction event or refuses to respond to the audio interaction event.

[0056] In one case, the first event identifier is the event identifier of a nodding event or a head-shaking event.

[0057] In one case, the sending module 23 is specifically used for: Send a second event identifier to the electronic device, the second event identifier being used to instruct the electronic device to maintain a waiting state for the audio interaction event or to execute a preset default action.

[0058] In one case, the identification module 22 is specifically used for: In response to the first message, the posture recognition mode is activated, head movement data is collected through the sensors of the wearable device, and head movement events of the wearer are identified based on the head movement data.

[0059] or, In response to the first message, a collection time window is opened to acquire head motion data within the collection time window, and head movement events of the wearable device wearer are identified based on the head motion data.

[0060] In one case, the identification module 22 is specifically used for: The head posture data at each moment is obtained based on the head movement data; The head's posture change data are determined based on the posture data at each time point; The head movement event is determined based on the posture change data and preset matching data.

[0061] In one case, the identification module 22 is specifically used for: The head motion data is then filtered. The posture data at each moment is obtained based on the filtered head motion data.

[0062] In one scenario, the audio interaction event is any one of a voice call request, a video call request, or a voice broadcast.

[0063] It should be noted that the information interaction and execution process between the above-mentioned devices / units are based on the same concept as the method embodiments of this application. For details on their specific functions and technical effects, please refer to the method embodiments section, and they will not be repeated here.

[0064] Figure 3 This is a schematic diagram of the structure of the wearable device provided in the embodiments of this application.

[0065] like Figure 3 As shown, the wearable device in this embodiment includes: a processor 31, a memory 32, and a computer program 33 stored in the memory 32 and executable on the processor 31. When the processor 31 executes the computer program 33, it implements the steps described in the communication method embodiment above, for example... Figure 1 The steps S101 to S103 are shown. Alternatively, when the processor 31 executes the computer program 33, it implements the functions of each module / unit in the above-described device embodiments, for example... Figure 2 The functions of receiving module 21 to transmitting module 23 are shown.

[0066] For example, the computer program 33 may be divided into one or more modules / units, which are stored in the memory 32 and executed by the processor 31 to complete this application. The one or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program 33 in the wearable device.

[0067] Those skilled in the art will understand that Figure 3 This is merely an example of a wearable device and does not constitute a limitation on wearable devices. It may include more or fewer components than illustrated, or combine certain components, or different components. For example, the wearable device may also include input / output devices, network access devices, buses, etc.

[0068] The processor 31 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. The general-purpose processor can be a microprocessor or any conventional processor.

[0069] The memory 32 can be an internal storage unit of the wearable device, such as a hard drive or memory. The memory 32 can also be an external storage device of the wearable device, such as a plug-in hard drive, smart media card (SMC), secure digital (SD) card, flash card, etc. Furthermore, the memory 32 can include both internal and external storage units. The memory 32 is used to store the computer program and other programs and data required by the wearable device. The memory 32 can also be used to temporarily store data that has been output or will be output.

[0070] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the above-described division of functional units and modules is merely an example. In practical applications, the above functions can be assigned to different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above. The functional units and modules in the embodiments can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit. Furthermore, the specific names of the functional units and modules are only for easy differentiation and are not intended to limit the scope of protection of this application. The specific working process of the units and modules in the above system can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0071] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

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

[0073] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

[0075] If an integrated module / unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include: any entity or device capable of carrying the computer program code, a recording medium, a USB flash drive, a portable hard drive, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium, etc.

[0076] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0077] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A communication method, characterized in that, Applied to wearable devices, which are communicatively connected to electronic devices, the method includes: Receive a first message sent by the electronic device, the first message being used to characterize an audio interaction event received by the electronic device; In response to the first message, head movement events of the wearer of the wearable device are identified; Send an event identifier corresponding to the head movement event to the electronic device, the event identifier being used to instruct the electronic device to respond to the audio interaction event based on the head movement event.

2. The communication method according to claim 1, characterized in that, Sending an event identifier corresponding to the head movement event to the electronic device, including: Send a first event identifier to the electronic device, the first event identifier being used to indicate whether the electronic device agrees to respond to the audio interaction event or refuses to respond to the audio interaction event.

3. The communication method according to claim 2, characterized in that, The first event identifier is the event identifier of a nodding event or a head-shaking event.

4. The communication method according to claim 1, characterized in that, Sending an event identifier corresponding to the head movement event to the electronic device, including: Send a second event identifier to the electronic device, the second event identifier being used to instruct the electronic device to maintain a waiting state for the audio interaction event or to execute a preset default action.

5. The communication method according to claim 1, characterized in that, In response to the first message, identify head movement events of the wearer of the wearable device, including: In response to the first message, the posture recognition mode is activated, head movement data is collected through the sensors of the wearable device, and head movement events of the wearer are identified based on the head movement data. or, In response to the first message, a collection time window is opened to acquire head motion data within the collection time window, and head movement events of the wearable device wearer are identified based on the head motion data.

6. The communication method according to claim 5, characterized in that, Based on the head motion data, the wearer's head movement events are identified, including: The head posture data at each moment is obtained based on the head movement data; The head's posture change data are determined based on the posture data at each time point; The head movement event is determined based on the posture change data and preset matching data.

7. The communication method according to claim 6, characterized in that, Based on the head motion data, the head posture data at various times is obtained, including: The head motion data is then filtered. The posture data at each moment is obtained based on the filtered head motion data.

8. The communication method according to any one of claims 1 to 7, characterized in that, The audio interaction event is any one of the following: a voice call request, a video call request, or a voice broadcast.

9. A wearable device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the communication method as described in any one of claims 1 to 8.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the communication method as described in any one of claims 1 to 8.

Images