Bluetooth communication method, wearable device and system

Abstract

The application provides a Bluetooth communication method, a wearable device and a system, relates to the technical field of terminals, and can avoid keeping an HFP connection all the time, thereby causing unnecessary time delay or call errors when an electronic device processes voice messages. The Bluetooth communication system comprises an electronic device and a wearable device, and an HFP connection is established between the electronic device and the wearable device. When the electronic device meets a preset condition, the HFP connection is automatically disconnected. After receiving an incoming call, the electronic device sends a first notification to the wearable device, and then reestablishes the HFP connection. Therefore, the electronic device can answer the incoming call by using the wearable device.

Description

[0001] This application is a divisional application. The original application has the application number 202010808831.7 and the original application date is August 12, 2020. The entire contents of the original application are incorporated herein by reference. Technical Field

[0002] This application relates to the field of terminal technology, and in particular to a Bluetooth communication method, wearable device and system. Background Technology

[0003] With the development of wireless technology, Bluetooth technology is widely used in wearable devices such as headphones and watches, enabling Bluetooth calls and improving call convenience. Implementing Bluetooth calling requires pre-establishing a hands-free protocol (HFP) connection between the wearable device and the electronic device. Subsequently, when the electronic device receives a call request, it establishes an extended synchronous connection-oriented link (eSco) with the wearable device based on the HFP connection as an audio data transmission channel, thus enabling the wearable device to handle the call. After the call ends, the electronic device disconnects the eSco from the wearable device but maintains the HFP connection for handling the next call.

[0004] When an electronic device establishes an HFP connection with a wearable device, if the electronic device needs to handle call services, it will by default call the wearable device with which it has established an HFP connection to handle the audio data of the call, such as receiving or playing audio data. However, in some scenarios, if the call service is a short message voice chat or video call in an instant messaging application, using a wearable device (such as a smartwatch or smart bracelet) to handle it is inconvenient for the user. This is because the user needs to manually operate the electronic device, such as selecting a contact, clicking on an unread "voice message," or viewing the other party's image, while simultaneously using the wearable device to listen to the audio. Operating two devices at the same time results in a poor user experience.

[0005] Based on the above scenario, existing technologies propose a solution whereby, if an electronic device needs to handle a call, it sends an eSco establishment request to the wearable device, which then establishes an eSco with the electronic device. Subsequently, if the wearable device confirms that the current call is within an instant messaging application, it disconnects the eSco. This allows the electronic device to utilize its own audio module to handle the call, ensuring that the user can complete the call using only one device. However, this solution introduces a delay during the process of establishing and disconnecting the eSco. For example, if a user needs to record a short voice message, after clicking "start recording," they must wait until the electronic device can use its microphone to pick up sound before recording can begin, resulting in a poor user experience. Summary of the Invention

[0006] The Bluetooth communication method, wearable device, and system provided in this application can automatically disconnect the HFP connection when the electronic device meets preset conditions. Therefore, after the electronic device detects an operation to play a voice message, it will not use the wearable device to play the voice message, causing unnecessary delays. Furthermore, after receiving an incoming call, the electronic device can re-establish the HFP connection, ensuring that the electronic device can answer calls using the wearable device.

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

[0008] In a first aspect, this application provides a Bluetooth communication system, comprising an electronic device and a wearable device, wherein a Hands-free Protocol (HFP) connection is established between the electronic device and the wearable device. The electronic device is configured to automatically disconnect the HFP connection when preset conditions are met. The electronic device is also configured to send a first notification to the wearable device after receiving an incoming call. The wearable device is configured to establish an HFP connection with the electronic device based on the first notification. The electronic device is further configured to send first audio data of the incoming call to the wearable device and / or receive second audio data of the incoming call sent by the wearable device after detecting a user answering an incoming call.

[0009] Optionally, preset conditions include the electronic device not receiving an incoming call or detecting an outgoing call. Specifically, when the electronic device and wearable device maintain an HFP connection, the electronic device will send the corresponding call status to the wearable device when it receives an incoming call or detects an outgoing call. The wearable device can then determine whether the electronic device needs to handle the call based on the HFP connection; if not, it can disconnect the HFP connection.

[0010] In this way, by determining whether the electronic device meets preset conditions, the HFP connection can be automatically disconnected. This effectively avoids the latency caused by maintaining the HFP connection, which would otherwise require the electronic device to establish and then disconnect the eSCO link with the wearable device when receiving voice messages, video calls, audio calls, or other services.

[0011] Furthermore, when an electronic device receives an incoming call, it can notify the wearable device, thereby re-establishing the HFP connection. This ensures that the electronic device can answer calls using the wearable device without causing unnecessary latency, thus improving the user experience.

[0012] Optionally, an application, such as application A, can be installed on the electronic device to manage the wearable device. Application A can be a third-party application that can monitor whether the electronic device receives an incoming call and send an initial notification to the wearable device when an incoming call is received, thereby enabling the reconstruction of the HFP connection.

[0013] In one possible implementation, the electronic device is further configured to send a second notification to the wearable device after detecting an outgoing call by the user. The wearable device is further configured to establish an HFP connection with the electronic device based on the second notification. After the call connection is established, the electronic device is further configured to send third audio data of the outgoing call to the wearable device and / or receive fourth audio data of the outgoing call sent by the wearable device.

[0014] In other words, when an electronic device needs to handle the first call service of an incoming or outgoing call, it can send a notification to the wearable device to rebuild the HFP connection, ensuring that the wearable device can play the audio of the call and collect the user's audio during the call.

[0015] In one possible implementation, the wearable device is also configured to disconnect the HFP connection with the electronic device after detecting an operation to end the call or receiving an instruction to end the call from the electronic device.

[0016] In this system, users can hang up the phone by operating the wearable device after the call ends. Generally, after the call is ended, the electronic device no longer needs to handle the first call (incoming or outgoing). Therefore, if the wearable device determines that the current electronic device meets preset conditions, it will disconnect the HFP connection. This avoids unnecessary delays when the electronic device receives voice messages or other second call services. Alternatively, users can hang up the phone by operating the electronic device after the call ends. In this case, the electronic device will send an instruction to the wearable device after detecting the hang-up operation, or the wearable device will disconnect the HFP connection if it detects that the call has been disconnected.

[0017] In one possible implementation, the electronic device is further configured to play the first audio or record the second audio when an operation of playing the first audio of the first application or recording the second audio using the first application is detected.

[0018] The first application can be a third-party instant messaging application (e.g., WeChat, QQ, video conferencing applications, etc.). Voice messaging, audio calls, video calls, and telephone voice services within the first application can be described as the second call service. In other words, generally, call services can include both the first and second call services. The first call service includes functions such as answering and making calls within the call application. The second call service includes the call services within the first application.

[0019] Generally, electronic devices have a pre-installed application; similarly, wearable devices such as smartwatches have a watch version of that application installed. Of course, wearable devices may also not have a pre-installed application.

[0020] Therefore, when an electronic device detects the playback of audio from the first application or the recording of audio, it will not detect the disconnected HFP connection and can directly utilize its own audio modules, such as speakers and microphones, to process the audio. For example, it can directly play a voice message or start recording a message based on the corresponding operation. This avoids the delay caused by the electronic device detecting the HFP connection and then calling the wearable device to process the corresponding service.

[0021] In one possible implementation, the operation of playing the first audio includes any of the following: playing the first voice message, answering a video call, or answering an audio call.

[0022] In one possible implementation, the operation of recording the second audio using the first application includes the operation of recording the second voice message using the first application or the operation of recording audio using the first application.

[0023] In one possible implementation, the electronic device is also used to capture third audio after a video or audio call connection has been established.

[0024] In video and audio call scenarios, electronic devices can use their own audio modules to capture audio, eliminating the need to use wearable devices as audio capture modules.

[0025] Secondly, this application provides a Bluetooth communication method applied to a system including an electronic device and a wearable device, wherein a Hands-free Protocol (HFP) connection is established between the electronic device and the wearable device. The method includes: automatically disconnecting the HFP connection when the electronic device meets preset conditions; the electronic device sending a first notification to the wearable device after receiving an incoming call, so that the wearable device can establish an HFP connection with the electronic device according to the first notification; and the electronic device sending first audio data of the incoming call and / or receiving second audio data of the incoming call sent by the wearable device after detecting a user answering an incoming call.

[0026] In one possible implementation, before establishing an HFP connection between the electronic device and the wearable device, the method further includes: after detecting a user's outgoing call operation, the electronic device sends a second notification to the wearable device; so that the wearable device can establish an HFP connection with the electronic device based on the second notification. After the call connection is established, the electronic device sends third audio data of the outgoing call to the wearable device and / or receives fourth audio data of the outgoing call sent by the wearable device.

[0027] In one possible implementation, the method further includes: after the call ends, the electronic device disconnects the HFP connection with the wearable device.

[0028] In one possible implementation, the method further includes: when the electronic device detects an operation of playing a first audio file of a first application or recording a second audio file using the first application, it plays the first audio file or records the second audio file.

[0029] In one possible implementation, the operation of playing the first audio includes any of the following: playing the first voice message, answering a video call, or answering an audio call.

[0030] In one possible implementation, the operation of recording the second audio using the first application includes the operation of recording the second voice message using the first application or the operation of recording audio using the first application.

[0031] In one possible implementation, the method further includes: the electronic device acquiring third audio after the video call or audio call connection is established.

[0032] In one possible implementation, the preset conditions include the electronic device not receiving an incoming call or not detecting an outgoing call.

[0033] Furthermore, the technical effects of the Bluetooth communication method described in the second aspect can be referred to the technical effects of the Bluetooth communication system described in the first aspect, and will not be repeated here.

[0034] Thirdly, this application provides a Bluetooth communication method applied to a system including an electronic device and a wearable device, wherein a Hands-free Protocol (HFP) connection is established between the electronic device and the wearable device. The method includes: the wearable device automatically disconnecting the HFP connection when it determines that the electronic device meets preset conditions; the wearable device receiving a first notification and establishing an HFP connection with the electronic device according to the first notification; wherein the first notification is a notification sent to the wearable device by the electronic device after receiving an incoming call; and the wearable device receiving first audio data of the incoming call sent by the electronic device and / or second audio data of the incoming call sent to the electronic device.

[0035] In one possible implementation, the method further includes: the wearable device receiving a second notification and establishing an HFP connection with the electronic device based on the second notification; wherein the second notification is a notification sent to the wearable device by the electronic device after detecting the user's outgoing call operation. After the call connection is established, the wearable device receives third audio data of the outgoing call sent by the electronic device and / or sends fourth audio data of the outgoing call to the electronic device.

[0036] In one possible implementation, the method further includes: after the wearable device detects an operation to end the call, or receives an instruction to end the call from the electronic device, disconnecting the HFP connection with the electronic device.

[0037] In one possible implementation, the preset conditions include the electronic device not receiving an incoming call or not detecting an outgoing call.

[0038] Furthermore, the technical effects of the Bluetooth communication method described in the third aspect can be referred to the technical effects of the Bluetooth communication system described in the first aspect, and will not be repeated here.

[0039] Fourthly, this application provides an electronic device, including: a processor, a memory, and an audio module; the memory and audio module are coupled to the processor, the memory is used to store computer program code, the computer program code including computer instructions, and when the processor reads the computer instructions from the memory, the electronic device performs the following operations: automatically disconnecting the Hands-Free Protocol (HFP) connection with a wearable device when a preset condition is met; sending a first notification to the wearable device after receiving an incoming call, so that the wearable device can establish an HFP connection according to the first notification; and sending first audio data of the incoming call to the wearable device and / or receiving second audio data of the incoming call sent by the wearable device after detecting that the user has answered an incoming call.

[0040] In one possible implementation, when the processor reads computer instructions from memory, it also causes the electronic device to perform the following operations: after detecting a user's outgoing call, it sends a second notification to the wearable device; so that the wearable device can establish an HFP connection based on the second notification. After the call connection is established, it sends third audio data of the outgoing call to the wearable device and / or receives fourth audio data of the outgoing call sent by the wearable device.

[0041] In one possible implementation, when the processor reads computer instructions from memory, it also causes the electronic device to perform the following operation: disconnect the HFP connection with the wearable device after the call ends.

[0042] In one possible implementation, when the processor reads computer instructions from memory, it also causes the electronic device to perform the following operations: when an operation to play first audio from a first application or record second audio using the first application is detected, the first audio is played or the second audio is recorded.

[0043] In one possible implementation, the operation of playing the first audio includes any of the following: playing the first voice message, answering a video call, or answering an audio call.

[0044] In one possible implementation, the operation of recording the second audio using the first application includes the operation of recording the second voice message using the first application or the operation of recording audio using the first application.

[0045] In one possible implementation, when the processor reads computer instructions from memory, it also causes the electronic device to perform the following operation: after a video or audio call connection is established, it acquires a third audio signal.

[0046] In one possible implementation, the preset conditions include the electronic device not receiving an incoming call or not detecting an outgoing call.

[0047] Furthermore, the technical effects of the electronic device described in the fourth aspect can be referred to the technical effects of the Bluetooth communication system described in the first aspect, and will not be repeated here.

[0048] Fifthly, this application provides a wearable device, including: a processor, a memory, and an audio module. The memory and audio module are coupled to the processor. The memory stores computer program code, which includes computer instructions. When the processor reads the computer instructions from the memory, the wearable device performs the following operations: automatically disconnecting the hands-free protocol (HFP) connection with the electronic device when a preset condition is met; receiving a first notification and establishing an HFP connection with the electronic device based on the first notification; wherein the first notification is a notification sent by the electronic device after receiving an incoming call; and receiving first audio data of the incoming call sent by the electronic device and / or second audio data of the incoming call sent to the electronic device.

[0049] In one possible implementation, when the processor reads computer instructions from memory, it also causes the wearable device to perform the following operations: receive a second notification and establish an HFP connection with an electronic device based on the second notification; wherein the second notification is a notification sent by the electronic device after detecting that the user has made an outgoing call. After the call connection is established, the wearable device receives third audio data of the outgoing call sent by the electronic device and / or sends fourth audio data of the outgoing call to the electronic device.

[0050] In one possible implementation, when the processor reads computer instructions from memory, it also causes the wearable device to perform the following operation: disconnecting the HFP connection with the electronic device after detecting an operation to end the call, or receiving an instruction to end the call from the electronic device.

[0051] In one possible implementation, the preset conditions include the electronic device not receiving an incoming call or not detecting an outgoing call.

[0052] Furthermore, the technical effects of the wearable device described in the fifth aspect can be referred to the technical effects of the Bluetooth communication system described in the first aspect, and will not be repeated here.

[0053] Sixthly, this application provides an electronic device having the function of implementing the Bluetooth communication method as described in the second aspect above and any of its possible implementations. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0054] Seventhly, this application provides a wearable device that has the function of implementing the Bluetooth communication method as described in the third aspect and any of its possible implementations. This function can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-described function.

[0055] Eighthly, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the Bluetooth communication method as described in any one of the second aspects and any possible implementations thereof.

[0056] Ninthly, this application provides a computer-readable storage medium including computer instructions that, when executed on a wearable device, cause the wearable device to perform the Bluetooth communication method as described in any of the third aspects and any possible implementations thereof.

[0057] In a tenth aspect, this application provides a computer program product that, when run on an electronic device, causes the electronic device to execute the Bluetooth communication method as described in any one of the second aspects and any possible implementations thereof.

[0058] In the eleventh aspect, this application provides a computer program product that, when run on an electronic device, causes a wearable device to perform the Bluetooth communication method as described in any one of the third aspects and any possible implementations thereof.

[0059] In a twelfth aspect, a circuit system is provided, comprising processing circuitry configured to perform the Bluetooth communication method as described in the second aspect and any of its possible implementations. Alternatively, the processing circuitry is configured to perform the Bluetooth communication method as described in the third aspect and any of its possible implementations.

[0060] In a thirteenth aspect, embodiments of this application provide a chip system including at least one processor and at least one interface circuit. The at least one interface circuit is used to perform transceiver functions and send instructions to the at least one processor. When the at least one processor executes the instructions, the at least one processor executes the Bluetooth communication method as described in the second aspect above and any possible implementation thereof; or, the at least one processor executes the Bluetooth communication method as described in the third aspect above and any possible implementation thereof. Attached Figure Description

[0061] Figure 1 A system schematic diagram provided for an embodiment of this application;

[0062] Figure 2 This is a schematic diagram of the structure of a wearable device provided in an embodiment of this application;

[0063] Figure 3A This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application;

[0064] Figure 3B A schematic diagram of the software structure of an electronic device provided in an embodiment of this application;

[0065] Figure 4 A flowchart illustrating the Bluetooth communication method provided in the embodiments of this application. Figure 1 ;

[0066] Figure 5 A schematic diagram of the interface of the electronic device provided in the embodiments of this application. Figure 1 ;

[0067] Figure 6 A schematic diagram of the interface of the electronic device provided in the embodiments of this application. Figure 2 ;

[0068] Figure 7 A schematic diagram of the interface of the electronic device provided in this application embodiment is shown in Figure 3.

[0069] Figure 8 This is a schematic diagram of the process for establishing an HFP connection provided in an embodiment of this application;

[0070] Figure 9 This application scenario illustrates the use case of the Bluetooth communication method provided in the embodiments of this application. Figure 1 ;

[0071] Figure 10 A schematic diagram of the interface of the electronic device provided in the embodiments of this application. Figure 4 ;

[0072] Figure 11 A schematic diagram of the interface of the electronic device provided in the embodiments of this application. Figure 5 ;

[0073] Figure 12 This application provides an illustration of an application scenario for the Bluetooth communication method in the prior art. Figure 1 ;

[0074] Figure 13 This application provides an illustration of an application scenario for the Bluetooth communication method in the prior art. Figure 2 ;

[0075] Figure 14 This application scenario illustrates the use case of the Bluetooth communication method provided in the embodiments of this application. Figure 2 ;

[0076] Figure 15 Schematic diagram of the structure of the electronic device provided in the embodiments of this application Figure 2 ;

[0077] Figure 16 Schematic diagram of the structure of the wearable device provided in the embodiments of this application Figure 2 . Detailed Implementation

[0078] The Bluetooth communication method, wearable device, and system provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0079] The terms “comprising” and “having”, and any variations thereof, used in the description of this application are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the steps or units listed, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such process, method, product, or apparatus.

[0080] It should be noted that in the embodiments of this application, the words "exemplary" or "for example" are used to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the words "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0081] In the description of this application, unless otherwise stated, "multiple" means two or more. "And / or" in this document is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone.

[0082] like Figure 1 The diagram shown illustrates an application scenario of a Bluetooth communication method provided in this application. The system in which this Bluetooth communication method is applied includes a wearable device 100 and an electronic device 200.

[0083] For example, wearable device 100 can be a smartwatch, smart bracelet, wireless earphones, smart glasses, or smart helmet, etc. Electronic device 200 can be a mobile phone, tablet computer, laptop computer, ultra-mobile personal computer (UMPC), personal digital assistant (PDA), vehicle terminal, etc. The specific forms of wearable device 100 and electronic device 200 in this application embodiment are not limited in any way.

[0084] Wearable device 100 can establish a wireless connection with electronic device 200 through wireless communication technology. This wireless communication technology can include Bluetooth (BT), which can be traditional Bluetooth or Bluetooth Low Energy (BLE), wireless local area networks (WLAN) (such as Wireless Fidelity (Wi-Fi) networks), Zigbee, frequency modulation (FM), near field communication (NFC), infrared (IR), or general 2.4G / 5G frequency band wireless communication technologies, etc.

[0085] This application uses Bluetooth as the wireless communication technology for illustration. After the wearable device 100 and the electronic device 200 establish a Bluetooth connection, if the wearable device 100 supports HFP service, an HFP connection can be established between the wearable device 100 and the electronic device 200. Subsequently, based on the HFP connection, the wearable device 100 acts as the Bluetooth device of the electronic device 200, processing the call services received by the electronic device 200. The call services include a first call service and a second call service. The first call service includes services such as answering and making calls in a call application. The second call service includes services such as short voice message chat, audio calls, and video calls in third-party instant messaging applications (e.g., WeChat, QQ, video conferencing applications).

[0086] Generally, for a user, if the call is the first call, the user only needs to use wearable device 100 to handle it. If the call is the second call, the user needs to operate both wearable device 100 and electronic device 200 simultaneously to complete the second call. However, after receiving a call, electronic device 200 does not distinguish the call type, i.e., it does not differentiate between the first and second call. Instead, it defaults to calling wearable device 100, with which it has established an HFP connection, to handle the call. Therefore, if the call is the second call, it will result in a poor user experience.

[0087] Based on this, two solutions are proposed in the existing technology.

[0088] In Option 1, with an HFP connection, after receiving a call, electronic device 200 sends an eSco establishment request to wearable device 100. Wearable device 100 agrees to the eSco establishment request and establishes an eSco with electronic device 200. Then, wearable device 100 determines whether the call currently being processed by electronic device 200 is the first call. If not, it actively disconnects the eSco, allowing electronic device 200 to switch back to its own speaker or microphone to handle the second call. However, after establishing the eSco, electronic device 200 will either send audio data to wearable device 100 based on the eSco, or wait to receive audio data sent by wearable device 100, until the eSco is disconnected. During this process, if the user is not paying attention to wearable device 100, the audio data sent by electronic device 200 to wearable device 100 will be lost; or, the user will continue to wait until the eSco is disconnected, at which point electronic device 200 will receive the user's voice.

[0089] Option 2: In the case of HFP connection, after receiving a call service, electronic device 200 sends an eSco establishment request to wearable device 100. Based on the eSco establishment request, wearable device 100 determines whether the call service currently being processed by electronic device 200 is the first call service. If not, it refuses to establish eSco, allowing electronic device 200 to handle the second call service using its own speaker or microphone. However, the process of wearable device 100 determining the current call service type is time-consuming.

[0090] Therefore, in some embodiments of this application, if the wearable device 100 determines that the electronic device 200 does not need to handle the first call service, it actively disconnects the HFP connection with the electronic device 200. Then, when the electronic device 200 receives the second call service, it will not detect the disconnected HFP connection and will directly use its speaker, microphone, and other audio modules to handle the second call service. When the electronic device 200 receives the first call service, it notifies the wearable device 100 to re-establish the HFP connection. Afterwards, based on the HFP connection, the wearable device 100 handles the first call service. This ensures that the user can handle both the first and second call services relatively easily. Furthermore, the electronic device 200 will not cause unnecessary delays or call errors during the handling of the second call service.

[0091] Figure 2 A schematic diagram of a wearable device 100 is shown. The wearable device 100 may include at least one processor 101, at least one memory 102, a wireless communication module 103, an audio module 104, at least one speaker 105, at least one microphone 106, and a power module 107, etc.

[0092] The memory 102 can be used to store application code, such as application code for wireless pairing between the wearable device 100 and the electronic device 200, enabling the wearable device 100 and the electronic device 200 to establish a wireless connection; handle the call services of the electronic device 200; and charge the wearable device 100, etc.

[0093] The processor 101 can be used to execute the aforementioned application code and call relevant modules to implement the functions of the wearable device 100 in this embodiment. For example, it can implement functions such as wireless Bluetooth connection between the wearable device 100 and the electronic device 200, audio playback, and making / receiving phone calls. Another example is that the wearable device 100 can receive messages sent by the electronic device 200 to determine whether the call is the first call.

[0094] Processor 101 may include one or more processing units, which may be independent devices or integrated into one or more processors 101. Specifically, processor 101 may be an integrated control chip or may consist of circuitry including various active and / or passive components, and the circuitry is configured to perform the functions belonging to processor 101 as described in the embodiments of this application.

[0095] The wireless communication module 103 can be used to support data exchange between the wearable device 100 and its electronic device 200, including wireless communication technologies such as BT, WLAN (such as Wi-Fi), Zigbee, FM, NFC, IR, or general 2.4G / 5G wireless communication technologies.

[0096] In some embodiments, the wireless communication module 103 can be a Bluetooth chip. The wearable device 100 can pair with and establish a wireless connection with the Bluetooth chip of the electronic device 200 through this Bluetooth chip, enabling wireless communication and service processing between the wearable device 100 and the electronic device 200. Typically, the Bluetooth chip supports basic rate (BR) / enhanced data rate (EDR) Bluetooth and Bluetooth Low Energy (BLE), for example, it can send / receive page messages and BLE broadcast messages. Bluetooth 103 can also be a Bluetooth transceiver. The wearable device 100 can establish a wireless connection with the electronic device 200 through this Bluetooth transceiver to achieve short-range data exchange between the two. For example, exchanging audio data or control data.

[0097] In addition, the wireless communication module 103 may also include an antenna to receive electromagnetic wave signals, perform frequency modulation and filtering of the electromagnetic wave signals, and send the processed signal to the processor 101. The wireless communication module 103 may also receive signals to be transmitted from the processor 101, perform frequency modulation and amplification, and then convert them into electromagnetic waves for radiation via the antenna. For example, the wireless communication module 103 may receive notification messages sent by the electronic device 200, and based on these notification messages, determine the type of call service being processed by the electronic device 200, such as whether the call service being processed by the electronic device is a first call service or a second call service.

[0098] The audio module 104 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 104 may further include an encoder and a decoder for encoding and decoding the audio signals. In some embodiments, the audio module 104 may be located in the processor 101, or some functional modules of the audio module 104 may be located in the processor 101.

[0099] At least one speaker 105, also referred to as a "handpiece" or "receiver," can be used to convert audio electrical signals into sound signals and play them. For example, when the wearable device 100 is used as an audio output device of the electronic device 200, the speaker 105 can convert the received audio electrical signals into sound signals and play them.

[0100] At least one microphone 106, also referred to as a "microphone" or "voice transducer," is used to convert sound signals into audio electrical signals. For example, when the wearable device 100 is used as an audio input device for the electronic device 200, the microphone 106 can capture the user's sound signals and convert them into audio electrical signals while the user is speaking (such as making a call or sending a voice message).

[0101] The aforementioned audio electrical signals can also be described as audio data.

[0102] In some embodiments, the speaker 105 and microphone 106 may also be integrated into the audio module 104. For example, the audio module 104 may include a speaker assembly for outputting audio signals, and a microphone circuit that cooperates with the speaker for receiving audio signals. This application does not specifically limit the specific implementation of the audio module 104, speaker 105, and microphone 106.

[0103] The power module 107 can be used to provide system power to the wearable device 100, powering various modules of the wearable device 100; and supporting the wearable device 100 to receive charging input, etc. The power module 107 may include a power management unit (PMU) and a battery. The PMU can receive external charging input; transform the electrical signal input from the charging circuit and provide it to the battery for charging; it can also transform the electrical signal provided by the battery and provide it to other modules such as the wireless communication module 103 and the audio module 104; and prevent the battery from overcharging, over-discharging, short-circuiting, or experiencing overcurrent. In some embodiments, the power module 108 may also include a wireless charging coil for wirelessly charging the wearable device 100. Additionally, the power management unit can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance).

[0104] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the wearable device 100. It may have more than Figure 2 The wearable device 100 may include more or fewer components, combinations of two or more components, or different component configurations. For example, the wearable device 100 may also include components such as sensors, a display screen (which can display relevant information to the user), and motors. Figure 2 The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing or application-specific integrated circuits.

[0105] Figure 3A This application provides a schematic diagram of the structure of an electronic device 200.

[0106] Electronic device 200 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, a barometric pressure sensor 180C, a magnetic sensor 180D, an accelerometer sensor 180E, a distance sensor 180F, a proximity sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0107] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 200. In other embodiments of this application, the electronic device 200 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0108] Processor 110 may include one or more processing units, such as application processors (APs), modem processors, graphics processing units (GPUs), image signal processors (ISPs), controllers, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). These different processing units may be independent devices or integrated into one or more processors.

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

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

[0111] In some embodiments, the processor 110 may include one or more interfaces. Interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface, etc.

[0112] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C buses. The processor 110 can couple to the touch sensor 180K, charger, flash, camera 193, etc., through different I2C bus interfaces. For example, the processor 110 can couple to the touch sensor 180K through the I2C interface, enabling the processor 110 and the touch sensor 180K to communicate through the I2C bus interface, thereby realizing the touch function of the electronic device 200.

[0113] The I2S interface can be used for audio communication. In some embodiments, the processor 110 may include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface to enable the function of answering phone calls through the wearable device 100.

[0114] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via the PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering phone calls through the wearable device 100. Both the I2S interface and the PCM interface can be used for audio communication.

[0115] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface to enable music playback through the wearable device 100.

[0116] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. The MIPI interface includes a camera serial interface (CSI) and a display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to enable the electronic device 200 to capture images. The processor 110 and the display screen 194 communicate via the DSI interface to enable the electronic device 200 to display images.

[0117] The GPIO interface can be configured via software. It can be configured as a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to a camera 193, a display screen 194, a wireless communication module 160, an audio module 170, a sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0118] USB port 130 is a USB standard compliant interface, specifically a Mini USB port, Micro USB port, or USB Type-C port. USB port 130 can be used to connect a charger to charge electronic device 200, and can also be used for data transfer between electronic device 200 and peripheral devices. It can also be used to connect headphones for audio playback. This interface can also be used to connect other electronic devices, such as AR devices.

[0119] It is understood that the interface connection relationships between the modules illustrated in the embodiments of the present invention are merely illustrative and do not constitute a structural limitation on the electronic device 200. In other embodiments of this application, the electronic device 200 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0120] The charging management module 140 receives charging input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 receives charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 receives wireless charging input via the wireless charging coil of the electronic device 200. While charging the battery 142, the charging management module 140 can also supply power to the electronic device via the power management module 141.

[0121] The power management module 141 connects the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, providing power to the processor 110, internal memory 121, display screen 194, camera 193, and wireless communication module 160, etc. The power management module 141 can also monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 141 may also be located within the processor 110. In other embodiments, the power management module 141 and the charging management module 140 may be located in the same device.

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

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

[0124] The mobile communication module 150 can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to the electronic device 200. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves via antenna 1, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via antenna 1. In some embodiments, at least some functional modules of the mobile communication module 150 may be housed in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 may be housed in the same device.

[0125] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0126] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 200, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via antenna 2, performs frequency modulation and filtering of the electromagnetic wave signals, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0127] In some embodiments, antenna 1 of electronic device 200 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 200 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

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

[0129] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel may be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a miniature LED, a microLED, a quantum dot light-emitting diode (QLED), etc. In some embodiments, electronic device 200 may include one or N displays 194, where N is a positive integer greater than 1.

[0130] Electronic device 200 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0131] The ISP (Image Signal Processor) is used to process data fed back from the camera 193. For example, when taking a picture, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, and the camera's photosensitive element transmits the electrical signal to the ISP for processing, transforming it into an image visible to the naked eye. The ISP can also perform algorithmic optimization of image noise, brightness, and skin tone. The ISP can also optimize parameters such as exposure and color temperature of the shooting scene. In some embodiments, the ISP can be set in the camera 193.

[0132] Camera 193 is used to capture still images or videos. An object is projected onto a photosensitive element by generating an optical image through the lens. The photosensitive element can be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, which is then passed to an ISP for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP for processing. The DSP converts the digital image signal into image signals in standard RGB, YUV, or other formats. In some embodiments, the electronic device 200 may include one or N cameras 193, where N is a positive integer greater than 1.

[0133] Digital signal processors (DSPs) are used to process digital signals. Besides digital image signals, they can also process other digital signals. For example, when electronic device 200 selects a frequency, the DSP is used to perform Fourier transforms on the frequency energy.

[0134] Video codecs are used to compress or decompress digital video. Electronic device 200 may support one or more video codecs. Thus, electronic device 200 can play or record video in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

[0135] An NPU (Neural Processing Unit) is a neural network (NN) computing processor that, by borrowing the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, rapidly processes input information and can continuously learn on its own. NPUs enable intelligent cognitive applications in electronic devices, such as image recognition, facial recognition, speech recognition, and text understanding.

[0136] The external storage interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200. The external memory card communicates with the processor 110 through the external storage interface 120 to perform data storage functions. For example, music, video, and other files can be saved on the external memory card.

[0137] Internal memory 121 can be used to store computer executable program code, which includes instructions. Internal memory 121 may include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function (such as sound playback, image playback, etc.), etc. The data storage area may store data created during the use of electronic device 200 (such as audio data, phonebook, etc.). Furthermore, internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, universal flash storage (UFS), etc. Processor 110 executes various functional applications and data processing of electronic device 200 by running instructions stored in internal memory 121 and / or instructions stored in memory located in the processor.

[0138] Electronic device 200 can implement audio functions such as music playback and recording through audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, and application processor.

[0139] The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The audio module 170 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 170 may be located in the processor 110, or some functional modules of the audio module 170 may be located in the processor 110.

[0140] The speaker 170A, also known as a "loudspeaker," is used to convert audio electrical signals into sound signals. The electronic device 200 can listen to music or make hands-free calls through the speaker 170A.

[0141] The receiver 170B, also known as the "earpiece," is used to convert audio electrical signals into sound signals. When the electronic device 200 answers a telephone call or voice message, the receiver 170B can be brought close to the ear to listen to the voice.

[0142] Microphone 170C, also known as a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to microphone 170C, inputting the sound signal into microphone 170C. Electronic device 200 may have at least one microphone 170C. In some embodiments, electronic device 200 may have two microphones 170C, which, in addition to collecting sound signals, can also perform noise reduction. In other embodiments, electronic device 200 may have three, four, or more microphones 170C, which can collect sound signals, reduce noise, identify the sound source, and perform directional recording, etc.

[0143] The 170D headphone jack is used to connect wired headphones. The 170D headphone jack can be a USB 130 interface or a 3.5mm Open Mobile Terminal Platform (OMTP) standard interface, a CTIA (Cellular Telecommunications Industry Association of the USA) standard interface.

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

[0145] Motor 191 can generate vibration alerts. Motor 191 can be used for incoming call vibration alerts or for touch vibration feedback. For example, different vibration feedback effects can correspond to touch operations performed on different applications (such as taking photos, playing audio, etc.). Motor 191 can also correspond to different vibration feedback effects for touch operations performed on different areas of the display screen 194. Different application scenarios (such as time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also be customized.

[0146] Indicator 192 can be an indicator light, used to indicate charging status, power changes, or to indicate messages, missed calls, notifications, etc.

[0147] The SIM card interface 195 is used to connect a SIM card. The SIM card can be inserted into or removed from the SIM card interface 195 to make contact with and separate from the electronic device 200. The electronic device 200 can support one or N SIM card interfaces, where N is a positive integer greater than 1. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, etc. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 is also compatible with different types of SIM cards. The SIM card interface 195 is also compatible with external memory cards. The electronic device 200 interacts with the network through the SIM card to realize functions such as calls and data communication. In some embodiments, the electronic device 200 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the electronic device 200 and cannot be separated from the electronic device 200.

[0148] The software system of electronic device 200 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses the layered architecture Android system as an example to exemplify the software structure of electronic device 200.

[0149] Figure 3B This is a software structure block diagram of the electronic device 200 according to an embodiment of the present invention.

[0150] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0151] The application layer can include a series of application packages.

[0152] like Figure 3B As shown, the application package may include applications such as camera, calendar, map, navigation, WLAN, music, SMS, Bluetooth, calling, and video.

[0153] In some embodiments, the application may further include application A (e.g., a smartwatch application, a fitness and health application, etc.). Users can edit and manage one or more wearable devices 100 connected to electronic device 200 through application A. Application A may also support a notification service, sending notification messages to wearable device 100. These notification messages may, for example, include the call service type of electronic device 200. Wearable device 100 then learns the call service type of electronic device 200 based on the received notification message.

[0154] Optionally, the wearable device 100 can disconnect the HFP connection by receiving a notification message sent by application A, thereby avoiding delays in the second call service.

[0155] Optionally, users can use application A to configure wearable device 100, such as switching modes or adding new devices. The signaling for these settings typically uses a proprietary Bluetooth protocol.

[0156] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0157] like Figure 3B As shown, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, application manager, etc.

[0158] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0159] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

[0160] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build applications. A display interface can consist of one or more views. For example, a display interface including a text notification icon could include views for displaying text and views for displaying images.

[0161] The phone manager is used to provide communication functions for electronic devices 200. For example, it manages call status (including connection and disconnection).

[0162] In some embodiments, after the electronic device 200 receives the first call service, the phone manager will notify application A through broadcast messages or other means.

[0163] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0164] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0165] The application manager can manage the lifecycle of, for example, at least one application.

[0166] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for scheduling and managing the Android system.

[0167] The core library consists of two parts: one part is the functionalities that need to be called by the Java language, and the other part is the Android core library.

[0168] The application layer and application framework layer run in a virtual machine. The virtual machine executes the Java files of the application layer and application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, security and exception management, and garbage collection.

[0169] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0170] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0171] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

[0172] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

[0173] A 2D graphics engine is a graphics engine for 2D drawing.

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

[0175] In the following embodiments, a smartwatch is used as the wearable device 100 and a mobile phone is used as the electronic device 200 for illustration.

[0176] like Figure 4 The diagram shown is a flowchart of a Bluetooth communication method provided in an embodiment of this application. The method may include steps S401-S409.

[0177] S401, The mobile phone received the first operation.

[0178] The first operation instructs the phone to establish a Bluetooth connection with the smartwatch. Upon detecting the first operation, the phone initiates the Bluetooth pairing process with the smartwatch. The first operation can be, for example, triggering the Bluetooth pairing process. For instance, the first operation might include a series of actions detected by the phone during the connection establishment process with the smartwatch using application A, such as enabling Bluetooth and selecting the wearable device. Alternatively, the first operation could include selecting the wearable device during the Bluetooth connection process. Furthermore, if the smartwatch and phone have been paired before, the phone can accept user actions related to the smartwatch in the "My Devices" list within the Bluetooth "Settings" interface for pairing.

[0179] For example, such as Figure 5 As shown in (a), this is the main interface 501 displayed on the mobile phone. In response to the user clicking the icon 51 of application A (e.g., the Health app), the mobile phone opens the Health app and displays the following... Figure 5 Interface 502, shown in (b) above, displays the following in response to a user clicking the device icon 52: Figure 5 The device management interface 503 is shown in (c). Users can add or delete devices through the device management interface 503. In response to the user clicking the add device control 53, the mobile phone displays the following... Figure 5Interface 504 is shown in (d) above. In response to the user clicking icon 54, the mobile phone detects the device type of the wearable device to be connected and displays as shown below. Figure 5 Interface 505 is shown in (e) above. The phone responds to the user clicking icon 55 by displaying... Figure 5 The interface 506 shown in (f) is as follows. In response to the user clicking icon 56, the phone initiates the pairing process with the smartwatch.

[0180] If Bluetooth is not enabled on the phone when initiating the pairing process with the smartwatch, the phone will display the following: Figure 6 Interface 601, shown in (a), is used to receive the first operation. In response to the user clicking the OK icon 61, the phone turns on Bluetooth, searches for connectable smartwatches, and displays the following: Figure 6 Interface 602 is shown in (b) of the diagram. Icon 62 displayed in interface 602 indicates that Bluetooth is enabled on the phone. In response to the user clicking on a smartwatch's media access control (MAC) address in list 63, the phone can establish a Bluetooth connection with the selected smartwatch. That is, in the current scenario, the first operation includes clicking icon 61 and clicking on a smartwatch's MAC address in list 63.

[0181] If Bluetooth is enabled on the phone when the pairing process with the smartwatch begins, the phone will directly display the following: Figure 6 Interface 602 is shown in (b) of the diagram. The first operation is to click on the MAC address of a smartwatch in list 63.

[0182] In some embodiments, besides the first operation received by the mobile phone during the process of establishing a connection with the smartwatch using application A, the mobile phone can also enable Bluetooth and establish a Bluetooth connection with the smartwatch in various ways. For example, Bluetooth can be enabled via a shortcut key or through Bluetooth settings.

[0183] For example, the phone displays as follows Figure 7 The main interface 701 shown in (a) displays the following in response to the user clicking the settings icon 71: Figure 7 Interface 702 is shown in (b) above. The phone responds to the user's tap on icon 72 by displaying... Figure 7 The Bluetooth settings interface 703 is shown in (c) above. Currently, Bluetooth on the phone is off. In response to the user clicking icon 73, the phone turns on Bluetooth and displays the following: Figure 7Interface 704 is shown in (d) above. Icons 74 and 75 in interface 704 indicate that Bluetooth is enabled. Afterwards, in response to the user clicking the device name in list 76, the phone directly establishes a Bluetooth connection with the corresponding device. Therefore, in the current scenario, the first operation is clicking the device name in list 76.

[0184] In some embodiments, the mobile phone can also establish a connection by scanning a pairing QR code on the smartwatch. The first operation could then include scanning the pairing QR code, whereby the mobile phone reads the information contained in the QR code and initiates the pairing process with the smartwatch.

[0185] S402. The mobile phone and smartwatch establish a Bluetooth connection and an HFP connection.

[0186] Optionally, after detecting the first operation, the mobile phone confirms the smartwatch selected by the user and sends a Bluetooth connection establishment request to the smartwatch. After receiving a connection confirmation response from the smartwatch, the mobile phone can establish a Bluetooth connection with the smartwatch. In step S401 above, the mobile phone initiates the Bluetooth pairing process with the smartwatch through application A. After the mobile phone and smartwatch establish a Bluetooth connection, it indicates that the mobile phone has added the smartwatch to the connected devices list of application A. Subsequently, the mobile phone can edit the smartwatch and send notification messages to the smartwatch through application A.

[0187] In this embodiment, the HFP connection can be used to establish an eSCO link for transmitting voice data streams, or it can be used to establish an HFP service. Establishing a Bluetooth connection in this embodiment can be establishing a physical connection, such as an asynchronous connectionless (ACL) link.

[0188] For example, application A on the phone initiates the pairing process, displaying as follows: Figure 6 Interface 603, shown in (c) above, prompts the user to confirm on the smartwatch side. After receiving the confirmation response from the smartwatch, the phone displays the following... Figure 6 The device management interface 604 shown in (d) displays the smartwatches that have been added.

[0189] Optionally, after detecting the Bluetooth activation, the phone, based on the existing Bluetooth connection, initiates a hands-free protocol (HFP) connection establishment process with the smartwatch. For example... Figure 8 As shown, the process of establishing an HFP connection may include steps one through eight below.

[0190] Step 1: The mobile phone sends an HFP service query request to the smartwatch.

[0191] Step 2: The smartwatch sends the HFP service query results to the mobile phone.

[0192] Optionally, in steps one and two above, if the mobile phone needs to establish an HFP connection with the smartwatch, the mobile phone needs to send an HFP service query request to the smartwatch to confirm whether the smartwatch supports the HFP service. HFP service refers to the smartwatch's ability to support Bluetooth hands-free functionality, controlling phone calls such as answering, hanging up, and rejecting calls. After receiving the HFP service query request from the mobile phone, the smartwatch confirms whether it supports the HFP service.

[0193] If the smartwatch supports HFP service, basic HFP service information (profile information) will be sent to the phone. This profile information may include, for example, the protocol version number and the RFCOMM protocol channel number.

[0194] If the smartwatch does not support HFP service, the query result sent to the mobile phone will be empty. After receiving the query result, the mobile phone confirms that the smartwatch does not support HFP service and stops establishing an HFP connection.

[0195] In some embodiments, the mobile phone sends a capability query request to the smartwatch to query the services supported by the smartwatch. For example, the capability query request can be sent to the smartwatch via the Service Discovery Protocol (SDP). In response to the request, the smartwatch sends the capabilities it supports to the mobile phone, including but not limited to HFP, Advanced Audio Distribution Profile (A2DP), and other services.

[0196] Step 3: The mobile phone sends a communication link establishment request to the smartwatch.

[0197] Step 4: The smartwatch sends a communication link establishment response to the mobile phone.

[0198] Optionally, in steps three and four above, after the mobile phone receives the profile information and confirms that the smartwatch supports HFP service, it establishes a communication link with the smartwatch based on the profile information, such as a communication link based on the RFCOMM protocol.

[0199] Steps one through four above can also be described as the pairing process between the phone and the smartwatch. Once the phone and smartwatch are successfully paired, the smartwatch completes Service Level Connection (SLC) initialization through steps five through eight below to establish the HFP connection. During this process, the phone and smartwatch transmit interactive commands through the established communication link to complete the SLC initialization.

[0200] Step 5: The mobile phone and smartwatch confirm the functions supported by the HFP connection.

[0201] Optionally, the smartwatch sends an AT+BRSF command to the phone to inform the phone which functions the smartwatch supports when an HFP connection is established. After confirmation, the phone replies with the +BRSF command to the smartwatch, i.e., a confirmation response. Through AT command interaction, the phone and smartwatch confirm the functions that can be performed based on the HFP connection. These may include call status notifications, three-way calling, incoming call ringback notifications, and volume control.

[0202] Step 6: The mobile phone obtains the smartwatch's encoding and decoding capabilities and selects the corresponding codec when the call begins.

[0203] Optionally, the smartwatch can send AT+BAC= to the phone.<u1,u2,…> Commands are used to inform the phone of its encoding and decoding capabilities, such as wideband or narrowband encoding and decoding capabilities. Based on the smartwatch's encoding and decoding capabilities, the phone selects the appropriate codec at the start of a call to enable subsequent information exchange with the smartwatch.

[0204] Step 7: Confirm the notification metrics supported by your phone.

[0205] Optionally, the smartwatch sends the command AT+CIND=? to the phone to query the notification indicators supported by the phone. That is, it queries the notification functions supported by the phone and their corresponding indicators. The phone sends the +CIND command to the smartwatch to inform the smartwatch of the list of indicators currently supported by the phone.

[0206] For example, if a phone can send the status of a call to a smartwatch after receiving a call notification, the indicator list will contain the statuses of the calls that can be notified. Another example is the message notification service between the phone and smartwatch; the phone can send notification messages to the smartwatch, and the smartwatch, in turn, supports message notification services and can receive and parse notification messages sent by the phone.

[0207] Step 8: Confirm the current notification status of your phone.

[0208] Optionally, the smartwatch can send the command AT+CIND? to ​​the phone to query the current status of the phone's notification metrics. The phone will reply with the command smartwatch+CIND, which includes the current status of the phone's notification metrics.

[0209] For example, a smartwatch can use the +CIND command to confirm that the phone is processing a call, and the corresponding status for a call is dialing.

[0210] Steps one through eight above constitute the HFP connection establishment process initiated by the mobile phone. Similarly, the HFP connection establishment process can also be initiated by a smartwatch.

[0211] For example, when a smartwatch detects that Bluetooth has been enabled, it proactively sends profile information to the phone to establish a communication link. Then, the HFP connection establishment process is completed through steps five through eight described above. The specific HFP connection establishment process can be found in existing technologies and will not be elaborated upon here.

[0212] It's important to note that when the smartphone is powered on, the smartwatch initializes the HFP and message notification services. This means that the HFP and message notification service identifiers are added to the list of services supported by the smartwatch. Subsequently, by querying the service list, users can determine whether the smartwatch supports the HFP and message notification services.

[0213] Optionally, after a Bluetooth connection is established between the phone and the smartwatch, the phone can send notification messages to the smartwatch wirelessly via Bluetooth.

[0214] For example, application A on the phone used to connect to wearable devices supports message notification services, allowing the phone to send notification messages to the smartwatch via application A. Application A can provide... Figure 5 The sports and health app shown.

[0215] For example, such as Figure 9 As shown, the phone and smartwatch establish a wireless connection via Bluetooth. Specifically, an HFP connection is established between the phone and smartwatch. Application A on the phone sends notification messages to the smartwatch via Bluetooth. The smartwatch's processor processes the notification message, confirms its content, and executes the corresponding action.

[0216] Understandable Figure 9 The structure illustrated does not constitute a specific limitation on mobile phones and smartwatches. Mobile phones and smartwatches can have more than Figure 9 The more or fewer components shown can be combined into two or more components, or they can have different component configurations.

[0217] S403: The smartwatch determines whether the current phone needs to handle the first call. If not, it disconnects the HFP connection.

[0218] Optionally, the smartwatch, based on the HFP connection, determines whether the current mobile phone needs to handle the first call. If the current mobile phone does not need to handle the first call, the smartwatch sends a request to disconnect the HFP connection to the mobile phone. Upon receiving the disconnect request, the mobile phone disconnects the HFP connection and sends a response to the smartwatch. If the current mobile phone needs to handle the first call, the smartwatch sends a disconnect request to the mobile phone after the first call is completed, thereby terminating the HFP connection with the mobile phone.

[0219] For example, such as Figure 9 As shown, the smartwatch sends a request to disconnect the HFP connection to the phone's Bluetooth module. After disconnecting the HFP connection, the phone sends a disconnect response to the smartwatch. Furthermore, the phone's Bluetooth module notifies the audio management module that the audio channel between the phone and the smartwatch is now broken. Subsequently, based on the disconnected HFP connection status, the audio management module determines that the audio channel between the phone's Bluetooth module and the smartwatch's Bluetooth module is broken, and therefore will not send call tasks to the phone's Bluetooth module. In other words, the smartwatch will not be used to handle call services.

[0220] In one possible implementation, the smartwatch can determine whether the phone needs to handle the first call by querying the status of the call service. For example, if the phone receives a call, it will send the call status parameters to the smartwatch with which it has established an HFP connection, so that the smartwatch can determine the type of call service. Subsequently, the smartwatch can use AT commands to query the status parameters corresponding to the current phone call service to confirm the type of call service. For example, the AT command is AT+CLCC, which is used to list the current calls.

[0221] Table 1 below shows the query results and their meanings for the AT+CLCC command. The first call service corresponds to multiple states; if the call service is the first call service, the query result will be one or more of 1-6. The second call service, due to its faster status updates, is configured with a query result of 0. That is, if the call service is the second call service, the query result will be 0. Based on the query results, the smartwatch can determine whether the phone currently needs to handle the first call service. It can be understood that if the AT+CLCC command has no corresponding query result, it means that the phone currently has no call service. Therefore, the smartwatch can directly send a request to the phone to disconnect the HFP connection.

[0222] Table 1

[0223] 0 Active state 1 Keep (Held) 2 Dialing 3 Alerting 4 Incoming call 5 Waiting 6 Call held by response and hold

[0224] It should be noted that the call services provided by typical third-party instant messaging applications are secondary call services. When a mobile phone receives a call service triggered by a third-party instant messaging application, it will generate the Active state shown in Table 1 above. However, if the mobile phone generates multiple states during the processing of call services triggered by certain third-party instant messaging applications, then the call services provided by such third-party instant messaging applications also belong to the primary call services.

[0225] It should be noted that wearable devices capable of handling secondary call services, such as Bluetooth headsets, can be pre-configured to facilitate user calls. These wearable devices do not need to send a request to the phone to disconnect the HFP connection; that is, they do not need to actively disconnect the HFP connection.

[0226] For example, a user can wear a Bluetooth headset on their ear. During a second call, the user only needs to operate their phone to handle the call. Therefore, the Bluetooth headset can be pre-configured as a wearable device capable of handling second calls without actively disconnecting the HFP connection from the phone.

[0227] S404. After disconnecting the HFP connection, the mobile phone receives a call service and determines the current call service type. If it is the second call service, proceed to step S405; if it is the first call service, proceed to step S406.

[0228] The call service types include first-level call services and second-level call services. First-level call services include answering and making calls within call applications. Second-level call services include short voice message chat, audio calls, and video calls within third-party instant messaging applications (such as WeChat, QQ, and video conferencing applications).

[0229] Optionally, after receiving the first call service, the mobile phone will send a system broadcast message to notify all registered application modules that the mobile phone has received the first call service. Application A on the mobile phone needs to register to listen for this broadcast message to determine the type of call service currently being received. If application A receives the broadcast message, it determines that the call service currently being received by the mobile phone is the first call service.

[0230] Optionally, the mobile phone can also determine the call service type by detecting a second operation. This second operation is used to instruct the execution of a call service. For example, if the second operation is making or receiving a call, and the mobile phone detects this second operation, it confirms that it has received the first call service. Or, for example, if the second operation is playing or recording a short voice message, and the mobile phone detects this second operation, it confirms that it has received the second call service.

[0231] In some embodiments, the mobile phone can also determine the call service type through other means. For example, it can monitor the phone's hardware status to determine the type of call service received. For instance, it can monitor changes in the phone's user interface (UI), speaker status, microphone status, etc., to determine whether the current call service is the first call service or the second call service. For example, the UI interface for the first call service is the call function interface, such as the answer call page. If the phone's UI interface switches to displaying the answer call page, then the type of call service currently received by the phone is determined to be the first call service.

[0232] S405, Call service is the second call service, the mobile phone handles the second call service.

[0233] Optionally, as described in step S403 above, the smartwatch has disconnected its HFP connection from the phone. Then, as... Figure 9 As shown, when the phone receives a second call service generated by the first application, the audio management module detects whether a sound playback or recording module is currently available. If the audio management module determines that no Bluetooth connection is currently available, it will not invoke the Bluetooth module to handle the second call service. Instead, the audio management module will invoke the phone's own audio module to handle the call service. For example, the audio management module may invoke the speaker to play sound or invoke the microphone to record. If the first application is, for example, a third-party instant messaging application, then the second call service may include playing or recording audio from the first application, or video or audio calls.

[0234] For example, such as Figure 10 As shown in (a) on the main interface 1001, a third-party instant messaging application, such as a social networking app, receives a message on the mobile phone. In response to the user clicking the social networking app icon 101, the mobile phone opens the social networking app and displays... Figure 10 Interface 1002, shown in (b) above, displays the following in response to the user clicking the unread message icon 102: Figure 10 The chat interface 1003 is shown in (c). On the chat interface 1003, if the phone detects that the user clicks the short voice message icon 103, it indicates that the phone has received a second call service to play unread short voice messages, and the audio management module needs to select the module used for playing sound. At this time, as shown... Figure 9 As shown, based on the disconnected HFP connection, the audio management module determines that there is currently no Bluetooth-connected device. Figure 10 As shown in interface 1004 (d), the audio management module directly calls the phone's speaker to play the current short voice message. During this process, the phone can process the second call relatively quickly, without the user noticing.

[0235] Or, as Figure 11 As shown in (a) of the main interface 1101, after the phone detects the user's click on the social APP icon 111, it displays the following: Figure 11 Interface 1102, shown in (b) above, is displayed in response to a user clicking icon 112. Figure 11 Interface 1103 is shown in (c). On interface 1103, if the mobile phone detects that the user clicks icon 113, it means that the user needs to send a short voice message. That is, the mobile phone receives the second call service for recording short voice messages, and the audio management module needs to select the module used to receive sound. At this time, as shown in (c), Figure 9 As shown, based on the disconnected HFP connection, the audio management module determines that there is currently no Bluetooth-connected device. Figure 11 As shown in interface 1104 (d), the audio management module directly calls the phone's microphone to record short voice messages. Icon 114, displayed on interface 1104, indicates to the user that a short voice message is being recorded. During this process, the phone can handle the second call relatively quickly, eliminating the need for the user to wait and improving efficiency.

[0236] It should be noted that if the HFP connection between the mobile phone and the smartwatch is not disconnected in step S403 above, in one scenario, such as... Figure 12 As shown, if the HFP connection between the phone and the smartwatch is not disconnected, then, when the phone receives a second call, the phone's Bluetooth module will send an eSco establishment request to the smartwatch's Bluetooth module. In response to the eSco establishment request, the smartwatch and phone establish an eSco connection. After the eSco is established, the phone's Bluetooth module will notify the audio management module that an audio channel has been established between the phone and the smartwatch. Subsequently, if the smartwatch confirms that the call type currently being processed by the phone is a second call, it will disconnect the eSco connection with the phone. Correspondingly, the phone's Bluetooth module will notify the audio management module that the audio channel between the phone and the smartwatch has been disconnected. Only then can the phone process the second call through its own speaker or microphone.

[0237] For example, such as Figure 10 The short voice playback scenario shown in (c) responds to the user's click on the short voice message icon 103. After the smartwatch and phone establish an eSCO connection, the audio management module will, as shown in... Figure 12 Link 121, as shown, is the established audio channel that sends audio data to the smartwatch, where it is played by the smartwatch's speaker until the eSCO disconnects. During this process, if the user is not paying attention to the smartwatch, audio data will be lost. Furthermore, abnormalities may occur during the process of the phone switching the audio data to the phone's speaker for playback. For example... Figure 12As shown, if the switching is normal, the audio management module will send the audio data to the phone's speaker via link 122. If the switching is abnormal, the audio management module will send the audio data to the phone's earpiece via link 123. Figure 10 Interface 1005, shown in (e) above, is the interface displayed on the phone when a switching error occurs. The phone displays a prompt box 104 on interface 1005, informing the user that the phone is currently playing voice messages using the earpiece. At this time, the volume is low, resulting in a poor user experience. Furthermore, as... Figure 11 In the short voice recording scenario shown in (c), the process of establishing and disconnecting the eSco between the phone and the smartwatch takes time. Therefore, on interface 1103, the phone responds to the user's click on icon 113 by displaying the following... Figure 11 Interface 1105 is shown in (e). Interface 1105 displays icon 115, prompting the user to wait for recording. Recording only begins after the eSco is disconnected from the phone, resulting in a poor user experience.

[0238] In another scenario, such as Figure 13 As shown, if the HFP connection between the phone and the smartwatch is not broken, then after the phone receives a second call request, the phone's Bluetooth module will send an eSco establishment request to the smartwatch's Bluetooth module. Upon receiving this request, the smartwatch will not immediately establish an eSco connection with the phone. Instead, it will first confirm the type of call service being handled by the phone. If it is a second call service, it will send a response to the phone rejecting the eSco establishment request. After confirming that the smartwatch has rejected the eSco establishment request, the phone will send at least one eSco establishment request based on the eSco packet type. This process continues until all establishment requests corresponding to all eSco packet types have been rejected by the smartwatch, at which point the phone confirms that the eSco establishment has failed. The phone's Bluetooth module then notifies the audio management module that the audio channel between the phone and the smartwatch has failed to establish. Only then can the phone process the second call service through its own speaker or microphone.

[0239] For example, in such Figure 10 The short audio playback scenario shown in (c) above, or as... Figure 11 In the short voice recording scenario shown in (c), during the process of the smartwatch confirming the mobile phone call service type and the multiple requests between the mobile phone and the smartwatch to establish an eSCO, the mobile phone needs to wait continuously until it confirms that the eSCO establishment has failed. In other words, during this process, the user needs to wait for the short voice message to play or for it to be recorded, impacting the user experience.

[0240] As can be seen, compared to the two example scenarios mentioned above, through step S403, the smartwatch actively disconnects the HFP connection with the phone, ensuring that the phone does not detect the smartwatch when receiving a second call. Therefore, the phone can directly use its own audio module to handle the second call, reducing processing time and preventing audio data loss. Furthermore, the user can handle the second call using only one phone, reducing the difficulty of user operation.

[0241] S406, the call service is the first call service, and the mobile phone sends the first notification to the smartwatch.

[0242] The first notification is used to instruct the smartwatch to handle the first call. The first notification may, for example, include an incoming call notification message or an outgoing call notification message.

[0243] Optionally, as described in step S404 above, after receiving the system broadcast message, application A on the mobile phone determines that the current call is the first call and then sends a first notification to the smartwatch. Upon receiving the first notification, the smartwatch can then know that the mobile phone has received the first call. Alternatively, application A can use other pre-configured methods, such as monitoring the mobile phone's hardware status, to learn about the first call received by the mobile phone and send a first notification to the smartwatch.

[0244] Optionally, the first notification is a pre-configured formatted notification message between the mobile phone and the smartwatch. If the first notification is a fixed format message, after receiving the first notification, the smartwatch can directly parse the message or determine from the message identifier that the mobile phone has received the first call service.

[0245] For example, such as Figure 14 As shown, application A confirms that the mobile phone has received the first call service, such as a phone call. Application A sends the first notification to the smartwatch via Bluetooth using link 141. The smartwatch's processor receives and parses the first notification, recognizing that the mobile phone has received the first call service.

[0246] It should be noted that after receiving the first and second call notifications, the phone can send a notification message to the smartwatch. If the phone receives the second call notification, it will send a second notification to the smartwatch. Based on this second notification, the smartwatch will confirm that the phone has received the second call and will then not process the current call.

[0247] S407, smartwatch and mobile phone establish HFP connection.

[0248] Optionally, after receiving the first notification, the smartwatch determines that the current mobile phone has received the first call service based on the first notification, and then sends an HFP connection establishment request to the mobile phone. In response to the HFP connection establishment request, the mobile phone sends an HFP connection establishment response to the smartwatch, and establishes an HFP connection with the smartwatch through the steps in step S402 above.

[0249] For example, such as Figure 14 As shown, the smartwatch uses its Bluetooth module to send an HFP connection establishment request to the phone's Bluetooth module. Upon receiving the HFP connection establishment request, the phone agrees to establish the HFP connection and sends an HFP connection establishment response to the smartwatch. Based on the re-established HFP connection, the phone's Bluetooth module notifies the audio management module that the Bluetooth audio channel between the phone and the smartwatch has been established.

[0250] S408, based on HFP connection, the mobile phone handles the first call service.

[0251] Optionally, the phone determines that an HFP connection has been established with the smartwatch. Based on the HFP connection, the phone sends an eSCO connection request to the smartwatch. After the smartwatch agrees, the phone sends audio data to the smartwatch and / or receives audio data sent by the smartwatch to complete the processing of the first call. Thus, after receiving the first call, the phone notifies the smartwatch, causing the smartwatch to proactively establish an HFP connection with the phone. This enables convenient and quick processing of the first call using the smartwatch.

[0252] For example, such as Figure 14 As shown, after the HFP connection between the mobile phone and the smartwatch is successfully established, the audio management module determines that the available audio modules for processing audio include the Bluetooth module, speaker, and microphone. The audio management module selects the high-priority Bluetooth audio module as the audio data input / output module. That is, the mobile phone selects the device connected via HFP to handle the first call, using the smartwatch to answer or make calls. Figure 14 As shown, the phone uses the smartwatch's speaker to play audio data and the smartwatch's microphone to capture audio data. In other words, the phone sends audio data to the smartwatch and receives audio data from the smartwatch, thus completing the call. The priority of the audio data input / output modules is pre-configured in the phone. Generally, the phone's Bluetooth module has a higher priority than modules such as the speaker and microphone.

[0253] It's important to note that during the process of re-establishing the HFP connection between the smartwatch and the phone, the phone's audio management module may have already checked for the existence of an established audio channel. After the HFP connection is rebuilt, the audio management module checks the audio channel again. The HFP rebuilding process is extremely short, ensuring that the HFP connection is rebuilt without the user's awareness. Therefore, when the phone receives the user's action to initiate the first call, such as clicking the answer button, the audio channel has already been established. The audio management module then directly processes the audio data using Bluetooth based on this audio channel, without any audio data loss.

[0254] S409. After the first call ends, the smartwatch disconnects from the HFP connection.

[0255] Optionally, after completing the first call, the smartwatch will proactively release the HFP connection with the phone. This ensures that the phone can use the smartwatch to handle the first call, and also prevents the phone from sending an eSco establishment request to the smartwatch based on the HFP connection when it receives a second call, thus avoiding call anomalies. In other words, after the smartwatch proactively releases the HFP connection, steps S404-S409 are executed repeatedly.

[0256] Therefore, the Bluetooth communication method provided in this application allows the wearable device to actively release the HFP connection with the mobile phone when the phone is not engaged in the first call. This prevents audio data loss, abnormal sound switching, and waiting delays when the phone subsequently receives a second call. Furthermore, the wearable device is aware that the phone is currently processing the first call. The wearable device actively establishes an HFP connection with the phone, allowing the phone to utilize the wearable device to handle the first call based on this connection. This improves the efficiency of the phone in handling both the first and second calls, simplifies user operation, and enhances the user experience.

[0257] The above method applies not only to telephone voice message scenarios but also to voice messages from third-party applications. Typically, the phone has a first application installed, and correspondingly, the smartwatch has a watch version of that application installed, or the smartwatch may not have the first application installed. The phone and smartwatch establish an HFP service. When the phone doesn't need to handle calls, the HFP service is automatically disconnected. Therefore, when the phone detects the user clicking to play a voice message from the first application, it can directly play the voice message because the HFP service is disconnected, thus avoiding the latency caused by the phone detecting the HFP service.

[0258] In this embodiment, the mobile phone typically has a corresponding smartwatch app installed, usually developed by both the mobile phone manufacturer and the smartwatch manufacturer. Users can configure the smartwatch within the app, such as changing watch faces and adding new devices. The signaling used for these settings is typically a proprietary Bluetooth protocol. In this embodiment, the HFP service can be disconnected via the app to avoid latency.

[0259] like Figure 15 As shown in the embodiments of this application, an electronic device 1500 is disclosed, which can be used to implement the methods described in the above method embodiments. For example, the electronic device 1500 may specifically include: a processing unit 1501, a sending unit 1502, and a receiving unit 1503. The processing unit 1501 is used to support the electronic device 1500 in performing... Figure 4 Steps S404 and S405; the transmitting unit 1502 is used to support the electronic device 1500 in performing... Figure 4 Steps S406, S407, and S408 are described in the text; the receiving unit 1503 is used to support the electronic device 1500 in performing these steps. Figure 4 Steps S407 and S408 in the above method embodiment. All relevant content regarding each step in the above method embodiment can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0260] Optional, Figure 15 The illustrated electronic device 1500 may also include a storage unit ( Figure 15 (not shown in the image), this storage unit stores a program or instruction. When the processing unit executes the program or instruction, it causes... Figure 15 The electronic device 1500 shown can perform Figure 4 The Bluetooth communication method is shown.

[0261] Figure 15 The technical effects of the electronic device 1500 shown can be referenced. Figure 4 The technical effects of the Bluetooth communication method shown will not be elaborated here.

[0262] Figure 15 The processing unit involved in the illustrated electronic device 1500 can be implemented by a processor or processor-related circuit components, and can be a processor or processing module. The transmitting unit 1502 and the receiving unit 1503 can be combined into a transceiver unit, which can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver module.

[0263] like Figure 16As shown in the embodiments of this application, a wearable device 1600 is disclosed, which can be used to implement the methods described in the above method embodiments. For example, the wearable device 1600 may specifically include: a processing unit 1601, a receiving unit 1602, and a sending unit 1603. The processing unit 1601 is used to support the wearable device 1600 in executing... Figure 4 Steps S403 and S409; the receiving unit 1602 is used to support the wearable device 1600 in performing these steps. Figure 4 Steps S406, S407, and S408; the sending unit 1603 is used to support the wearable device 1600 in performing these steps. Figure 4 Steps S407 and S408 in the above method embodiment. All relevant content regarding each step in the above method embodiment can be referenced from the functional description of the corresponding functional module, and will not be repeated here.

[0264] Optional, Figure 16 The wearable device 1600 shown may also include a storage unit ( Figure 16 (not shown in the image), this storage unit stores a program or instruction. When the processing unit executes the program or instruction, it causes... Figure 16 The wearable device 1600 shown can perform Figure 4 The Bluetooth communication method is shown.

[0265] Figure 16 The technical effects of the wearable device 1600 shown can be referenced. Figure 4 The technical effects of the Bluetooth communication method shown will not be elaborated here.

[0266] Figure 16 The processing unit involved in the wearable device 1600 shown can be implemented by a processor or processor-related circuit components, and can be a processor or processing module. The receiving unit 1602 and the transmitting unit 1603 can be combined into a transceiver unit, which can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver module.

[0267] This application provides a Bluetooth communication system, which includes, as described above. Figure 15 The electronic devices shown and such Figure 16 The wearable device shown is connected via an HFP (Hardware-Plus Connection).

[0268] An electronic device used to automatically disconnect the HFP connection when the electronic device meets preset conditions.

[0269] Electronic devices are also used to send an initial notification to wearable devices after receiving an incoming call.

[0270] Wearable devices for establishing HFP connections with electronic devices based on a first notification.

[0271] The electronic device is also used to send first audio data of the incoming call to the wearable device and / or receive second audio data of the incoming call sent by the wearable device after detecting that the user has answered the call.

[0272] In one possible implementation, the electronic device is also used to send a second notification to the wearable device after detecting that the user has made a power outage.

[0273] Wearable devices are also used to establish HFP connections with electronic devices based on a second notification.

[0274] After the call connection is established, the electronic device is also used to send outgoing third audio data to the wearable device and / or receive outgoing fourth audio data sent by the wearable device.

[0275] In one possible implementation, the wearable device is also used to disconnect the HFP connection with the electronic device after detecting an operation to end the call or receiving an instruction to end the call from the electronic device.

[0276] In one possible implementation, the electronic device is further configured to play the first audio or record the second audio when an operation of playing the first audio of the first application or recording the second audio using the first application is detected.

[0277] In one possible implementation, the operation of playing the first audio includes any of the following: playing the first voice message, answering a video call, or answering an audio call.

[0278] In one possible implementation, the operation of recording the second audio using the first application includes the operation of recording the second voice message using the first application or the operation of recording audio using the first application.

[0279] In one possible implementation, the electronic device is also used to capture third audio after a video or audio call connection has been established.

[0280] In one possible implementation, the preset conditions include the electronic device not receiving an incoming call or not detecting an outgoing call.

[0281] The technical effects of this Bluetooth communication system can be referenced from the technical effects of the Bluetooth communication method described above, and will not be repeated here.

[0282] This application also provides a chip system including at least one processor and at least one interface circuit. The processor and the interface circuit are interconnected via lines. For example, the interface circuit can be used to receive signals from other devices. Or, for example, the interface circuit can be used to send signals to other devices. Exemplarily, the interface circuit can read instructions stored in memory and send those instructions to the processor. When the instructions are executed by the processor, an electronic device can perform the steps executed by the mobile phone in the above embodiments. Alternatively, a wearable device can perform the steps executed by the mobile phone in the above embodiments. Of course, the chip system may also include other discrete components, which are not specifically limited in this application.

[0283] This application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the aforementioned method steps to implement the Bluetooth communication method in the above embodiments.

[0284] This application also provides a computer-readable storage medium storing computer instructions. When the computer instructions are executed on a wearable device, the wearable device performs the aforementioned method steps to implement the Bluetooth communication method in the above embodiments.

[0285] This application also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned steps to implement the Bluetooth communication method described in the above embodiments.

[0286] In addition, embodiments of this application also provide an apparatus, which may specifically be a component or module. The apparatus may include a connected processor and a memory; wherein the memory is used to store computer execution instructions, and when the apparatus is running, the processor may execute the computer execution instructions stored in the memory to enable the apparatus to perform the Bluetooth communication methods in the above-described method embodiments.

[0287] In this application, the electronic devices, wearable devices, computer-readable storage media, computer program products or chips provided in the embodiments are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0288] Through the above description of the embodiments, those skilled in the art will clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. The specific working process of the system, device, and unit described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0289] In the several embodiments provided in this application, it should be understood that the disclosed methods can be implemented in other ways. For example, the terminal 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 of modules or units may be electrical, mechanical, or other forms.

[0290] 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.

[0291] 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.

[0292] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program instructions, such as flash memory, portable hard disk, read-only memory, random access memory, magnetic disk, or optical disk.

[0293] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication system, characterized in that, The communication system includes electronic devices and wearable devices; The electronic device is used to establish a Bluetooth connection and a hands-free protocol (HFP) connection with the wearable device, wherein the HFP connection is based on the Bluetooth connection; The wearable device is configured to automatically disconnect the HFP connection and maintain the Bluetooth connection when the electronic device does not need to process the first call service, wherein the first call service includes answering and making calls in the electronic device's call application. The electronic device is further configured to, after disconnecting the HFP connection, if it detects the operation of playing the first audio of the first application or recording the second audio using the first application, play the first audio or record the second audio using the audio module of the electronic device itself, wherein the first application includes an instant messaging application; The electronic device is further configured to send a first notification to the wearable device after receiving the first call service; The wearable device is also configured to, while maintaining the Bluetooth connection, re-establish the HFP connection based on the first notification and the electronic device.

2. The system according to claim 1, characterized in that, The wearable device is used to send a query request to the electronic device, the query request being used to query the status parameters corresponding to the call service of the electronic device; The electronic device is configured to send a query result to the wearable device, the query result including an indication of whether the electronic device currently needs to process the first call service; The wearable device is used to determine, based on the query result, that the electronic device does not need to process the first call service.

3. The system according to claim 2, characterized in that, The query request is an AT command.

4. The system according to any one of claims 1-3, characterized in that, The wearable device is further configured to disconnect the HFP connection with the electronic device after detecting an operation to terminate the first call service or receiving an instruction from the electronic device to terminate the first call service.

5. The system according to claim 1, characterized in that, The operation of playing the first audio includes any one of the following: playing the first voice message, answering a video call, or answering an audio call.

6. The system according to claim 1, characterized in that, The operation of recording the second audio using the first application includes recording the second voice message using the first application or recording audio using the first application.

7. The system according to claim 1, characterized in that, The electronic device is also used to acquire third audio after a video or audio call connection is established in the first application.

8. A communication method, characterized in that, Applied to systems including electronic devices and wearable devices, the method includes: The electronic device and the wearable device establish a Bluetooth connection and a hands-free protocol (HFP) connection, wherein the HFP connection is based on the Bluetooth connection; When the electronic device does not need to process the first call service, the wearable device automatically disconnects the HFP connection while maintaining the Bluetooth connection. The first call service includes answering and making calls in the electronic device's call application. After disconnecting the HFP connection, if the electronic device detects an operation of playing the first audio of the first application or recording the second audio using the first application, then the electronic device uses its own audio module to play the first audio or record the second audio, wherein the first application includes an instant messaging application; After receiving the first call service, the electronic device sends a first notification to the wearable device; While maintaining the Bluetooth connection, the wearable device re-establishes the HFP connection based on the first notification and the electronic device.

9. The method according to claim 8, characterized in that, The electronic device does not need to handle the first call service, including: The wearable device sends a query request to the electronic device, the query request being used to query the status parameters corresponding to the call service of the electronic device; The electronic device sends a query result to the wearable device, the query result including an indication of whether the electronic device currently needs to process the first call service; Based on the query results, the wearable device determines that the electronic device does not need to process the first call service.

10. The method according to claim 9, characterized in that, The query request is an AT command.

11. The method according to any one of claims 8-10, characterized in that, The method further includes: After detecting an operation to terminate the first call service, or receiving an instruction from the electronic device to terminate the first call service, the wearable device disconnects the HFP connection with the electronic device.

12. The method according to claim 8, characterized in that, The operation of playing the first audio includes any one of the following: playing the first voice message, answering a video call, or answering an audio call.

13. The method according to claim 8, characterized in that, The operation of recording the second audio using the first application includes recording the second voice message using the first application or recording audio using the first application.

14. The method according to claim 8, characterized in that, The method further includes: The electronic device acquires third audio after a video or audio call connection is established in the first application.

15. A communication method, characterized in that, Applied to wearable devices, the method includes: The wearable device and the electronic device establish a Bluetooth connection and a hands-free protocol (HFP) connection, wherein the HFP connection is based on the Bluetooth connection; When the electronic device does not need to process the first call service, the wearable device automatically disconnects the HFP connection while maintaining the Bluetooth connection. The first call service includes answering and making calls in the electronic device's call application. The wearable device receives a first notification sent by the electronic device, the first notification being sent by the electronic device after receiving the first call service; While maintaining the Bluetooth connection, the wearable device re-establishes the HFP connection based on the first notification and the electronic device.

16. The method according to claim 15, characterized in that, The electronic device does not need to handle the first call service, including: The wearable device sends a query request to the electronic device, the query request being used to query the status parameters corresponding to the call service of the electronic device; The wearable device receives a query result sent by the electronic device, the query result including an indication of whether the electronic device currently needs to process the first call service; Based on the query results, the wearable device determines that the electronic device does not need to process the first call service.

17. The method according to claim 16, characterized in that, The query request is an AT command.

18. The method according to any one of claims 15-17, characterized in that, The method further includes: After detecting an operation to terminate the first call service, or receiving an instruction from the electronic device to terminate the first call service, the wearable device disconnects the HFP connection with the electronic device.

19. A communication method, characterized in that, Applied to electronic devices, the method includes: Wearable devices and electronic devices establish Bluetooth connections and Hands-free Protocol (HFP) connections, wherein the HFP connection is based on the Bluetooth connection; When the electronic device does not need to process the first call service, the electronic device automatically disconnects the HFP connection while maintaining the Bluetooth connection. The first call service includes answering and making calls in the electronic device's call application. After disconnecting the HFP connection, if the electronic device detects an operation of playing the first audio of the first application or recording the second audio using the first application, then the electronic device uses its own audio module to play the first audio or record the second audio, wherein the first application includes an instant messaging application; After receiving the first call service, the electronic device sends a first notification to the wearable device so that the wearable device can establish the HFP connection according to the first notification. While maintaining the Bluetooth connection, the electronic device and the wearable device re-establish the HFP connection.

20. The method according to claim 19, characterized in that, When the electronic device needs to process the first call service, the re-establishment of the HFP connection between the electronic device and the wearable device includes: Upon detecting the user's action of making a phone call, a second notification is sent to the wearable device so that the wearable device can establish the HFP connection based on the second notification. The electronic device and the wearable device re-establish the HFP connection.

21. The method according to claim 19 or 20, characterized in that, The method further includes: After the call connection is established, the third audio data of the first call service is sent to the wearable device and / or the fourth audio data of the first call service is received from the wearable device.

22. The method according to any one of claims 19-21, characterized in that, The method further includes: After the call ends, disconnect the HFP connection with the wearable device.

23. The method according to claim 19, characterized in that, The operation of playing the first audio includes any one of the following: playing the first voice message, answering a video call, or answering an audio call.

24. The method according to claim 19, characterized in that, The operation of recording the second audio using the first application includes recording the second voice message using the first application or recording audio using the first application.

25. The method according to claim 19, characterized in that, The method further includes: The electronic device acquires third audio after a video or audio call connection is established in the first application.

26. A wearable device, characterized in that, include: The device includes a processor, a memory, and an audio module, wherein the memory and the audio module are coupled to the processor, the memory being used to store computer program code, the computer program code including computer instructions, and the wearable device performing the communication method as described in any one of claims 15-18 when the processor reads the computer instructions from the memory.

27. An electronic device, characterized in that, include: The electronic device includes a processor, a memory, and an audio module, wherein the memory and the audio module are coupled to the processor, the memory being used to store computer program code, the computer program code including computer instructions, and the electronic device performing the communication method as described in any one of claims 19-25 when the processor reads the computer instructions from the memory.

28. A computer-readable storage medium storing instructions, characterized in that, When the instructions are executed on a wearable device, the wearable device performs the communication method as described in any one of claims 15-18.

29. A computer-readable storage medium storing instructions, characterized in that, When the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the communication method as described in any one of claims 19-25.

Images