WO2022174746A1

WO2022174746A1 - Event notification method, bluetooth device and bluetooth system

Info

Publication number: WO2022174746A1
Application number: PCT/CN2022/075512
Authority: WO
Inventors: 李明旭; 朱珂; 崔晓青
Original assignee: 华为技术有限公司
Priority date: 2021-02-22
Filing date: 2022-02-08
Publication date: 2022-08-25
Also published as: CN114979352A

Abstract

The present application provides an event notification method, a Bluetooth device and a Bluetooth system. The Bluetooth system comprises a first Bluetooth device and a second Bluetooth device having no Bluetooth connection established therebetween, wherein the first Bluetooth device is configured to receive a first event, and in response to receiving the first event, send a first message to the second Bluetooth device by means of a Bluetooth broadcast channel, the first message being used to notify the second Bluetooth device of the first event; and the second Bluetooth device is configured to receive the first message on the Bluetooth broadcast channel, and perform a response action in response to the first message, the response action at least comprising an action for prompting the first event to a user. The present application avoids a user missing a first event.

Description

Event notification method, Bluetooth device, and Bluetooth system

This application claims the priority of the Chinese patent application filed on February 22, 2021 with the application number 202110198696.3 and the application title is "Event Notification Method, Bluetooth Device and Bluetooth System", the entire contents of which are incorporated by reference in in this application.

technical field

The present application relates to the technical field of Bluetooth communication, and in particular, to an event notification method, a Bluetooth device, a Bluetooth system, and a computer-readable storage medium.

Background technique

In 2000, the first Bluetooth-based phone headset (also known as "Bluetooth headset") appeared. Since the introduction of Bluetooth headsets, it has greatly facilitated people's daily life. For example, after the user connects the Bluetooth headset to the tablet, the user can play/pause the music on the tablet through the Bluetooth headset, or answer/hang up an incoming call on the tablet.

However, when a user is using a Bluetooth headset, the sound of the Bluetooth headset may cover other sounds in the environment, which may cause the user to miss some messages. For example, when a user is using a Bluetooth headset to listen to music on a tablet, if the user's mobile phone receives an incoming call, the ringtone on the mobile phone may be obscured by the sound in the Bluetooth headset, causing the user to miss the call.

SUMMARY OF THE INVENTION

Some embodiments of the present application provide an event notification method, a Bluetooth device, a Bluetooth system, and a computer-readable storage medium. The present application is described below from various aspects, and the embodiments and beneficial effects of the following aspects can be referred to each other.

In a first aspect, an embodiment of the present application provides a Bluetooth system, the Bluetooth system includes a first Bluetooth device and a second Bluetooth device that do not establish a Bluetooth connection with each other, wherein: the first Bluetooth device is configured to receive a first event. and, in response to receiving the first event, send a first message to the second Bluetooth device through the Bluetooth broadcast channel, where the first message is used to notify the second Bluetooth device of the first event; the second Bluetooth device is configured to broadcast on the Bluetooth The first message is received on the channel, and a response action in response to the first message is performed, wherein the response action at least includes an action for prompting the user of the first event.

According to the embodiment of the present application, when the first Bluetooth device receives the first event, the second Bluetooth device may notify the user of the first event, so as to prevent the user from missing the first event. In addition, the first bluetooth sends an event notification message to the second bluetooth device through the bluetooth broadcast channel, and there is no need to establish a bluetooth connection between the first bluetooth device and the second bluetooth device, so it can be applied to various bluetooth devices (for example, only one bluetooth connection is supported) channel equipment), with better adaptability.

In some embodiments, the first Bluetooth device sends an event notification message to a second Bluetooth device that meets a preset condition. The preset conditions may include specific conditions, for example, the preset conditions are: the second Bluetooth device has established a Bluetooth connection with other Bluetooth devices other than the first Bluetooth device; the preset conditions may also not include additional conditions, for example, the first Bluetooth device 2. The Bluetooth device is any device.

In some embodiments, sending the first message to the second Bluetooth device through the Bluetooth broadcast channel includes: the first Bluetooth device, based on determining that the second Bluetooth device has established a Bluetooth connection with other Bluetooth devices other than the first Bluetooth device, sending the first message to the second Bluetooth device. Two Bluetooth devices send the first message.

According to the embodiment of the present application, when the second Bluetooth device establishes a Bluetooth connection with other Bluetooth devices, it indicates that the user is currently using the second Bluetooth device, and therefore, it can be further ensured that the first message is notified to the user.

In some implementations, the prompt action includes playing prompt audio for the first event.

In some embodiments, the first message sent by the first Bluetooth device includes description information of the first event; and the prompt audio played by the second Bluetooth device includes the first audio, and the prompt audio carries the description information.

In some embodiments, playing the prompt audio by the second Bluetooth device includes: the second Bluetooth device determines the service type of its currently playing service; when the second Bluetooth device determines that the service type of its currently playing service is a call service, the second Bluetooth device determines The Bluetooth device plays the first audio after the current playback service ends; when the Bluetooth device determines that the service type of the current playback service is other than the call service, the second Bluetooth device plays the first audio at the current moment.

When the current audio playback service of the second Bluetooth device is a call service, it means that the user is using the second Bluetooth device to conduct a real-time call with other users. If the user's real-time call is interrupted, there will be a bad experience. Therefore, in the embodiment of the present application, the second Bluetooth device does not play the first audio for the time being, but plays the first audio after the call service ends.

In some embodiments, the prompt audio includes a second audio, and the duration of the second audio is shorter than that of the first audio; and, when the second Bluetooth device determines that the service type of its currently playing service is a call service, the second Bluetooth device is currently playing The second audio is played at all times, and the first audio is played after the current playing service ends.

According to the embodiments of the present application, it can not only play a certain prompting role, but also avoid affecting the normal conversation of the user.

In some embodiments, the description information of the first event includes device identification information of the first device, device type information of the first device, event type information of the first event, and/or time information when the first device receives the first event .

In some embodiments, performing the response action by the second Bluetooth device further comprises: sending a response message to the first message to the first Bluetooth device. In this way, it is beneficial for the first Bluetooth device to confirm that the second Bluetooth device has received the first message.

In some embodiments, the first Bluetooth device sends the first message to the second Bluetooth device, further comprising: if the first Bluetooth device does not receive a response message from the second Bluetooth device within a predetermined time after sending the first message , the first message is retransmitted successively according to the set time interval until a response message from the second Bluetooth device is received, or until the number of times of retransmission of the first message exceeds the set threshold.

The embodiments of the present application are beneficial to ensure that the second Bluetooth device does not miss the first message from the first Bluetooth device.

In some embodiments, the second Bluetooth device performing a response action in response to the first message includes: the second Bluetooth device performing a response action based on determining that it is a target receiving device of the first message.

According to the embodiment of the present application, the second Bluetooth device performs the response action only when it determines that it is the target receiving device of the first message; otherwise, the second Bluetooth device ignores the first message to avoid erroneously leaking user information.

In some embodiments, the first message carries the device identifier of the target receiving device of the first message; the second Bluetooth device determines that it is the target receiving device of the first message, including: the second Bluetooth device matches its own device identifier with the device identifier. The device identifier carried in the first message is matched to determine that it is the target receiving device of the first message.

In some implementations, the first Bluetooth device sends the first message to the second Bluetooth device, comprising: the first Bluetooth device sends the second Bluetooth device to the second Bluetooth device based on determining that the second Bluetooth device is a device that has completed Bluetooth pairing with the first Bluetooth device Send the first message.

According to the embodiments of the present application, unnecessary information leakage can be avoided, thereby improving the security of user information.

In some implementations, the first Bluetooth device sends the first message to the second Bluetooth device, comprising: the first Bluetooth device is based on determining that the second Bluetooth device is a device that has completed Bluetooth pairing with the first Bluetooth device, and determining that the second Bluetooth device is The device satisfies at least one of the following conditions, and sends the first message to the second Bluetooth device: in the historical communication process of the first Bluetooth device, the number of times that the second Bluetooth device establishes a Bluetooth connection with the first Bluetooth device exceeds the set threshold; The second Bluetooth device is designated by the user as a legitimate device to receive the first message.

When the number of times that the second Bluetooth device establishes a Bluetooth connection with the first Bluetooth device exceeds a certain number of times, it indicates that the second Bluetooth device is a device frequently used by the user, thereby indicating that the second Bluetooth device is a device trusted by the user. In addition, after the user specifies the validity of the second Bluetooth device, it means that the user confirms that the second Bluetooth device is a trusted device. Therefore, the embodiments of the present application can further ensure the security of information user information.

In some embodiments, the first event is an incoming call event.

In some embodiments, the second Bluetooth device is a Bluetooth headset, a Bluetooth speaker, or a wearable device.

In a second aspect, the embodiments of the present application provide an event notification method for a first Bluetooth device, the method includes: receiving a first event; in response to receiving the first event, sending a Bluetooth broadcast channel to the second Bluetooth device The first message is used to notify the second Bluetooth device of the first event, wherein the second Bluetooth device has not established a Bluetooth connection with the first Bluetooth device.

In some embodiments, sending the first message to the second Bluetooth device through a Bluetooth broadcast channel includes: based on determining that the second Bluetooth device has established a Bluetooth connection with other Bluetooth devices other than the first Bluetooth device, sending the first message to the second Bluetooth device First news.

In some embodiments, the first message includes descriptive information of the first event.

In some embodiments, the description information of the first event includes device identification information of the first Bluetooth device, device type information of the first Bluetooth device, event type information of the first event, and/or the first Bluetooth device receives the first event time information.

In some implementations, sending the first message to the second Bluetooth device through a Bluetooth broadcast channel further includes: if no response message is received from the second Bluetooth device within a predetermined time after sending the first message, according to the setting The first message is successively retransmitted at the time interval until a response message from the second Bluetooth device is received, or until the number of times of retransmission of the first message exceeds the set threshold.

In some embodiments, sending the first message to the second Bluetooth device through a Bluetooth broadcast channel includes: based on determining that the second Bluetooth device is a device that has completed Bluetooth pairing with the first Bluetooth device, sending the first message to the second Bluetooth device .

In some embodiments, sending the first message to the second Bluetooth device through the Bluetooth broadcast channel includes: based on determining that the second Bluetooth device is a device that has completed Bluetooth pairing with the first Bluetooth device, and determining that the second Bluetooth device satisfies the following At least one of the conditions is to send the first message to the second Bluetooth device: in the historical communication process of the first Bluetooth device, the number of times that the second Bluetooth device establishes a Bluetooth connection with the first Bluetooth device exceeds a set threshold; the second Bluetooth device is designated by the user as a legitimate device to receive the first message.

In some embodiments, the first event is an incoming call event.

In some embodiments, the first Bluetooth device sends an event notification message to a second Bluetooth device that meets a preset condition. The preset conditions may include specific conditions, for example, the preset conditions are: the second Bluetooth device has established a Bluetooth connection with other Bluetooth devices other than the first Bluetooth device, and/or, the second Bluetooth device has been connected to the first Bluetooth device. The Bluetooth device is a device that completes Bluetooth pairing; the preset condition may also not include additional conditions, for example, the second Bluetooth device is any device.

In a third aspect, the embodiments of the present application provide an event notification method for a second Bluetooth device, the method includes: receiving a first message from the first Bluetooth device on a Bluetooth broadcast channel, where the first message is used to notify the second Bluetooth device. The Bluetooth device notifies the first event received by the first Bluetooth device, wherein the second Bluetooth device has not established a Bluetooth connection with the first Bluetooth device; and executes a response action in response to the first message, wherein the response action at least includes an action for sending a message to the user. Action that prompts the first event.

In some embodiments, the second Bluetooth device establishes a Bluetooth connection with other devices than the first Bluetooth device.

In some embodiments, the first message includes description information of the first event; and the prompt audio played by the second Bluetooth device includes the first audio, and the prompt audio carries the description information.

In some embodiments, performing a response action in response to the first message further includes: sending a response message to the first message to the first Bluetooth device. In this way, it is beneficial for the first Bluetooth device to confirm that the second Bluetooth device has received the first message.

In some embodiments, performing the response action in response to the first message includes: the second Bluetooth device performing the response action based on determining that it is a target receiving device of the first message.

In some embodiments, the first event is an incoming call event.

In a fourth aspect, embodiments of the present application provide a Bluetooth device, including: a memory for storing instructions executed by one or more processors of the Bluetooth device; a processor, when the processor executes the memory When the instruction in , the Bluetooth device can be made to execute the event notification method provided by any one of the implementation manners of the second aspect of this application. For the beneficial effects that can be achieved in the fourth aspect, reference may be made to the beneficial effects of any implementation manner of the second aspect, which will not be repeated here.

In a fifth aspect, embodiments of the present application provide a Bluetooth device, including: a memory for storing instructions executed by one or more processors of the Bluetooth device; a processor, when the processor executes the memory When the instruction in , the Bluetooth device can be made to execute the event notification method provided by any one of the implementation manners of the third aspect of the present application. For the beneficial effects that can be achieved in the fifth aspect, reference may be made to the beneficial effects of any embodiment of the third aspect, which will not be repeated here.

In a sixth aspect, an embodiment of the present application provides a Bluetooth system, including a first Bluetooth device and a second Bluetooth device that do not establish a Bluetooth connection with each other, wherein the first Bluetooth device is used to perform any one of the second aspects of the present application. In the event notification method provided by the embodiment, the second Bluetooth device is configured to execute the event notification method provided by any embodiment of the third aspect of the present application. For the beneficial effects that can be achieved in the sixth aspect, reference may be made to the beneficial effects of any embodiment of the second aspect of the present application or the beneficial effects of any embodiment of the third aspect of the present application, which will not be repeated here.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, where an instruction is stored in the computer-readable storage medium, and when the instruction is executed on a computer, the computer can execute any one of the embodiments of the second aspect of the present application or The event notification method provided by any method of the third aspect of the present application. For the beneficial effects that can be achieved in the seventh aspect, reference may be made to the beneficial effects of any embodiment of the second aspect of the present application or the beneficial effects of any embodiment of the third aspect of the present application, which will not be repeated here.

Description of drawings

FIG. 1a is a schematic diagram of an application scenario of an event notification method provided by an embodiment of the present application;

1b is a schematic diagram of a terminal interface for enabling an event notification function provided by an embodiment of the present application;

2a is a schematic structural diagram of a Bluetooth device provided by an embodiment of the application;

FIG. 2b is a software architecture diagram of a Bluetooth device provided by an embodiment of the application;

3 is an exemplary structural diagram of a Bluetooth broadcast data packet provided by an embodiment of the present application;

FIG. 4 is an exemplary flowchart 1 of an event notification method provided by an embodiment of the present application;

FIG. 5 is an interface diagram 1 for specifying a user-trusted device provided by an embodiment of the present application;

FIG. 6 is an interface diagram 2 for specifying a user-trusted device provided by an embodiment of the present application;

7 is a schematic diagram of a broadcast packet sent by a first Bluetooth device according to an embodiment of the present application;

FIG. 8 is a schematic diagram of a broadcast packet replied by a second Bluetooth device according to an embodiment of the present application;

9 is a schematic flowchart of a second Bluetooth device playing a prompt audio provided by an embodiment of the present application;

FIG. 10 is an exemplary flowchart 2 of an event notification method provided by an embodiment of the present application;

11 is a schematic diagram of a module structure of a Bluetooth system provided by an embodiment of the application;

FIG. 12 shows a block diagram of an electronic device provided by an embodiment of the present application;

FIG. 13 shows a schematic structural diagram of a system on chip (System on Chip, SOC) provided by an embodiment of the present application.

Detailed ways

Specific embodiments of the present application will be described in detail below with reference to the accompanying drawings.

With the development of communication technology, for example, the development of voice over IP (Voice over Internet Protocol, VoIP) technology, more and more electronic devices currently have telephone functions. For example, in addition to traditional mobile phones, users can also make calls through tablets, laptops, etc. Theoretically, as long as the electronic device can access the Internet and has a microphone (Microphone, MIC) and an earpiece, the telephone function can be realized. Therefore, users can often have multiple electronic devices with telephone functions.

Referring to FIG. 1 a , a user has multiple electronic devices such as a mobile phone 100 , a tablet 110 , and a notebook computer 130 , and each electronic device is connected to the gateway 140 through its own WiFi module to form a local area network 150 . In addition, FIG. 1 a also includes a Bluetooth headset 120 , and the Bluetooth headset 120 is added to the local area network 150 through a Bluetooth connection with the tablet 110 . After the Bluetooth headset 120 and the tablet 110 are connected via Bluetooth, the user can listen to audio content (eg, music, answer voice calls, etc.) on the tablet 110 through the Bluetooth headset 120 . However, if the mobile phone 100 receives an incoming call at this time, the ringtone of the incoming call on the mobile phone 100 may be covered by the sound played by the Bluetooth headset 120 . Therefore, the user may not hear the incoming call on the mobile phone 100 , and thus may miss the call on the mobile phone 100 . call.

The embodiments of the present application are used to solve this technical problem. Specifically, the embodiments of the present application are used to provide an event notification method. When the mobile phone 100 (as the first Bluetooth device) receives an incoming call event (as the first event or the event to be notified), the mobile phone 100 (as the first event or the event to be notified) sends a notification to the Bluetooth headset 120 through the Bluetooth broadcast channel. (as the second Bluetooth device) sends an event notification message (as the first message), the event notification message is used to notify the Bluetooth headset 120 of an incoming call event. The Bluetooth headset 120 receives the event notification message sent by the mobile phone 100 on the Bluetooth broadcast channel, and executes a response action in response to the event notification message, wherein the response action includes an action for prompting the user of an incoming call event (eg, playing a prompt audio) .

Therefore, according to the embodiment of the present application, when the mobile phone 100 receives an incoming call event, the mobile phone 100 can notify the user of the incoming call event through the Bluetooth headset 120 to prevent the user from missing an incoming call.

In addition, limited by frequency resources and hardware configuration, the number of point-to-point Bluetooth connections supported by Bluetooth devices is often limited. Especially for a device with a relatively simple hardware configuration such as the Bluetooth headset 120, it may only support one point-to-point Bluetooth communication channel. In the embodiment of the present application, the first Bluetooth device sends an event notification message to the second Bluetooth device through the Bluetooth broadcast channel, and there is no need to establish a Bluetooth connection between the first Bluetooth device and the second Bluetooth device, so it can be applied to various Bluetooth devices. good adaptability.

In addition, although the mobile phone 100 is used as an example of the first Bluetooth device (or terminal device) in FIG. 1a, the present application is not limited to this. In other examples, the first Bluetooth device may be a tablet, a notebook computer, a smart screen, a smart home appliance (eg, a microwave oven, a smart door lock, an alarm clock), a car machine, etc., as long as it has a Bluetooth communication function.

Although FIG. 1a uses a Bluetooth headset as an example of the second Bluetooth device, the present application is not limited to this. In other examples, the second Bluetooth device may be a Bluetooth speaker, a wearable device (eg, a smart bracelet/watch, smart glasses, smart helmet, etc.), etc., as long as it has an audio playback function and a Bluetooth communication function.

Although the incoming electricity event is used as an example of the first event in FIG. 1a, the present application is not limited to this. In other examples, the first event may be an event to be notified other than an incoming call event, for example, a smart speaker playing schedule reminder event, a doorbell ringing event, a washing machine washing program completion event, a timer ending event, and the like.

Further, whether the first Bluetooth device enables the function of sending an event notification message to the outside may be set by the user. For example, referring to FIG. 1b, the pull-down menu of the first Bluetooth device (eg, mobile phone 100) includes an event notification switch 100a. If the user turns on the event notification switch 100a, when the first Bluetooth device receives the first event, it sends a notification to the second Bluetooth device. The device sends an event notification message; if the user turns off the event notification switch 100a, after the first Bluetooth device receives the first event, it does not send the event notification message to the outside. For another example, when the first Bluetooth device does not include a display screen (for example, a doorbell), the user can manage the device through a device management application (for example, Smart ^LifeTM ) installed on a smart terminal (for example, a mobile phone). ) to set whether to enable the device to send event notification messages to the outside world.

In addition, when the first Bluetooth device receives the first event, it can play a prompt tone associated with the first event. For example, when the mobile phone receives an incoming call event, it will play the incoming call ringtone; it may also not play the sound associated with the first event. For example, when the phone is set to silent mode, the phone will not play the ringtone even if it receives an incoming call event.

Specific embodiments of the present application are described below with reference to the scenario shown in FIG. 1a.

FIG. 2 a shows a schematic structural diagram of the mobile phone 100 . The mobile phone 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) connector 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an 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, buttons 190, motor 191, indicator 192, camera 193, display screen 194, and user Identity module (subscriber identification module, SIM) card interface 195 and so on. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the mobile phone 100 . In other embodiments of the present application, the mobile phone 100 may include more or less components than shown, or some components may be combined, or some components may be separated, or different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

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

The processor can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have just been used or recycled by the processor 110 . If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby increasing the efficiency of the system.

In some embodiments, the processor 110 may include one or more interfaces. The interface may include an integrated circuit (inter-integrated circuit, I2C) interface, an integrated circuit built-in audio (inter-integrated circuit sound, I2S) interface, a pulse code modulation (pulse code modulation, PCM) interface, a universal asynchronous transceiver (universal asynchronous transmitter) receiver/transmitter, UART) interface, mobile industry processor interface (mobile industry processor interface, MIPI), general-purpose input/output (GPIO) interface, subscriber identity module (subscriber identity module, SIM) interface.

The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may contain multiple sets of I2C buses. The processor 110 can be respectively coupled to the touch sensor 180K, the charger, the flash, the camera 193 and the like through different I2C bus interfaces. For example, the processor 110 may couple the touch sensor 180K through the I2C interface, so that the processor 110 communicates with the touch sensor 180K through the I2C bus interface, so as to realize the touch function of the mobile phone 100 .

The I2S interface can be used for audio communication. In some embodiments, the processor 110 may contain multiple sets of I2S buses. The processor 110 may be coupled with the audio module 170 through an I2S bus to implement 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 through the I2S interface, so as to realize the function of answering calls through a Bluetooth headset.

The PCM interface can also be used for audio communications, sampling, quantizing and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 may be coupled through a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 through the PCM interface, so as to realize the function of answering calls through the Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

The UART interface is a universal serial data bus used for asynchronous communication. The bus may be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication . In some embodiments, a UART interface is typically used to connect the processor 110 with the wireless communication module 160 . For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 through the UART interface to implement the Bluetooth function. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 through the UART interface, so as to realize the function of playing music through the Bluetooth headset.

The MIPI interface can be used to connect the processor 110 with peripheral devices such as the display screen 194 and the camera 193 . MIPI interfaces include camera serial interface (CSI), display serial interface (DSI), etc. In some embodiments, the processor 110 communicates with the camera 193 through a CSI interface, so as to realize the shooting function of the mobile phone 100 . The processor 110 communicates with the display screen 194 through the DSI interface to realize the display function of the mobile phone 100 .

The GPIO interface can be configured by software. The GPIO interface can be configured as a control signal or as a data signal. In some embodiments, the GPIO interface may be used to connect the processor 110 with the camera 193, the display screen 194, the wireless communication module 160, the audio module 170, the sensor module 180, and the like. The GPIO interface can also be configured as I2C interface, I2S interface, UART interface, MIPI interface, etc.

It can be understood that, the interface connection relationship between the modules illustrated in the embodiment of the present invention is only a schematic illustration, and does not constitute a structural limitation of the mobile phone 100 . In other embodiments of the present application, the mobile phone 100 may also adopt different interface connection manners in the foregoing embodiments, or a combination of multiple interface connection manners.

The wireless communication function of the mobile phone 100 may be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, the baseband processor, and the like.

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

The mobile communication module 150 can provide wireless communication solutions including 2G/3G/4G/5G etc. applied on the mobile phone 100 . The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA) and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and then turn it into an electromagnetic wave for radiation through the antenna 1 . In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the same device as at least part of the modules of the processor 110 .

The modem processor may include a modulator and a demodulator. Wherein, the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. Then the demodulator transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and passed to the application processor. The application processor outputs sound signals through audio devices (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or videos through the display screen 194 . In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be independent of the processor 110, and may be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide applications on the mobile phone 100 including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , perform frequency modulation on it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2 .

In some embodiments, the antenna 1 of the mobile phone 100 is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the mobile phone 100 can communicate with the network and other devices through 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), broadband 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 technology, etc. The GNSS may include global positioning system (global positioning system, GPS), global navigation satellite system (global navigation satellite system, GLONASS), Beidou navigation satellite system (beidou navigation satellite system, BDS), quasi-zenith satellite system (quasi -zenith satellite system, QZSS) and/or satellite based augmentation systems (SBAS).

The mobile phone 100 realizes the display function through the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is 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 that execute program instructions to generate or alter display information.

Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light). emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (quantum dot light emitting diodes, QLED) and so on. In some embodiments, the handset 100 may include 1 or N display screens 194, where N is a positive integer greater than 1.

The mobile phone 100 can realize the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194 and the application processor.

The ISP is used to process the data fed back by the camera 193 . For example, when taking a photo, the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin tone. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193 .

Camera 193 is used to capture still images or video. The object is projected through the lens to generate an optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals. In some embodiments, the mobile phone 100 may include one or N cameras 193 , where N is a positive integer greater than one.

A digital signal processor is used to process digital signals, in addition to processing digital image signals, it can also process other digital signals. For example, when the mobile phone 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the energy of the frequency point, and the like.

Video codecs are used to compress or decompress digital video. The handset 100 may support one or more video codecs. In this way, the mobile phone 100 can play or record videos in various encoding formats, such as: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4 and so on.

The NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process the input information, and can continuously learn by itself. Applications such as intelligent cognition of the mobile phone 100 can be implemented through the NPU, such as image recognition, face recognition, speech recognition, text understanding, and the like.

The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the mobile phone 100 . The external memory card communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example to save files like music, video etc in external memory card.

Internal memory 121 may be used to store computer executable program code, which includes instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area can store an operating system, an application program required for at least one function (such as a sound playback function, an image playback function, etc.), and the like. The storage data area can store data (such as audio data, phone book, etc.) created during the use of the mobile phone 100 and the like. In addition, the internal memory 121 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, universal flash storage (UFS), and the like. The processor 110 executes various functional applications and data processing of the mobile phone 100 by executing the instructions stored in the internal memory 121 and/or the instructions stored in the memory provided in the processor. The instructions stored in the memory 121 may include instructions that, when executed by at least one of the processors, cause the mobile phone 100 to perform the steps performed by the mobile phone in the event notification method provided in the embodiment of the present application.

The mobile phone 100 can implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, and an application processor. Such as music playback, recording, etc.

The audio module 170 is used for converting digital audio information into analog audio signal output, and also for converting analog audio input into digital audio signal. Audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110 , or some functional modules of the audio module 170 may be provided in the processor 110 .

Speaker 170A, also referred to as a "speaker", is used to convert audio electrical signals into sound signals. The mobile phone 100 can listen to music through the speaker 170A, or listen to a hands-free call.

The receiver 170B, also referred to as "earpiece", is used to convert audio electrical signals into sound signals. When the mobile phone 100 answers a call or a voice message, the voice can be answered by placing the receiver 170B close to the human ear.

The microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can make a sound by approaching the microphone 170C through a human mouth, and input the sound signal into the microphone 170C. The mobile phone 100 may be provided with at least one microphone 170C. In other embodiments, the mobile phone 100 may be provided with two microphones 170C, which can implement a noise reduction function in addition to collecting sound signals. In other embodiments, the mobile phone 100 may further be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

The earphone jack 170D is used to connect wired earphones. The earphone interface 170D may be a USB connector 130, or a 3.5mm open mobile terminal platform (OMTP) standard interface, a cellular telecommunications industry association of the USA (CTIA) standard interface.

The software system of the mobile phone 100 may adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. The embodiments of the present invention take an Android system with a layered architecture as an example to illustrate the software structure of the mobile phone 100 as an example.

FIG. 2b is a block diagram of the software structure of the mobile phone 100 according to the embodiment of the present invention.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. The communication between the layers is through the software interface. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and a system library, and a kernel layer.

The application layer can include a series of application packages.

As shown in Figure 2b, the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and so on.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 2b, the application framework layer may include a window manager, content provider, view system, telephony manager, resource manager, notification manager, etc.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc.

Content providers are used to store and retrieve data and make these data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone book, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. View systems can be used to build applications. A display interface can consist of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide the communication function of the mobile phone 100 . For example, the management of call status (including connecting, hanging up, etc.).

The resource manager provides various resources for the application, such as localization strings, icons, pictures, layout files, video files and so on.

The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages, and can disappear automatically after a brief pause without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications of applications running in the background, and notifications on the screen in the form of dialog windows. For example, text information is prompted in the status bar, a prompt sound is issued, the electronic device vibrates, and the indicator light flashes.

Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

The core library consists of two parts: one is the function functions that the java language needs to call, and the other is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, safety and exception management, and garbage collection.

A system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

The Surface Manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

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

2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.

In order to facilitate the understanding of the technical solutions of the embodiments of the present application, a brief introduction to the Bluetooth communication method is given first. There are two types of Bluetooth communication methods, one is point-to-point communication and the other is broadcast communication.

For point-to-point communication, both parties in the communication need to establish a Bluetooth connection before formal communication. The process of establishing a Bluetooth connection may include steps such as sending/confirming a connection request, and/or negotiating connection parameters (eg, connection interval). After the Bluetooth connection is established, the two communicating parties communicate on a dedicated physical channel (with dedicated communication time slot and communication frequency). Therefore, the physical channel is also called "point-to-point Bluetooth communication channel". Generally speaking, the number of Bluetooth connections (or peer-to-peer Bluetooth communication channels) supported by an electronic device is limited, for example, some Bluetooth headsets may only support one Bluetooth connection.

For the broadcast communication method, there is no dedicated physical channel between the two communicating parties, and the communicating party is on several fixed physical channels (the physical channel is the Bluetooth broadcast channel, and each physical channel has a fixed frequency, which is determined by The Bluetooth protocol stipulates that the data is sent over the Bluetooth broadcast channel, and the other party of the communication listens on the Bluetooth broadcast channel to receive the broadcast data. Among them, the party sending data is called "advertiser", and the party receiving data is called "observer". A pair of Bluetooth devices can communicate on a Bluetooth broadcast channel before establishing a Bluetooth connection. For example, in the process of establishing a Bluetooth connection, both parties of the communication can send/confirm a connection request on the Bluetooth broadcast channel, negotiate connection parameters, and so on.

When a Bluetooth device communicates in a broadcast communication manner, it performs data interaction with other Bluetooth devices by sending a Bluetooth broadcast data packet (hereinafter referred to as a broadcast packet) on a Bluetooth broadcast channel. Among them, the broadcast packet needs to conform to a certain format (specified by the Bluetooth protocol), so that the content in the broadcast packet can be recognized by other devices.

Figure 3 shows a schematic structural diagram of a broadcast packet. Referring to FIG. 3, the broadcast packet includes a type field, a broadcast device address field, and a data field.

Among them, the "type" field (Adv PDU Type) is used to write the type of the broadcast packet. The Bluetooth protocol specifies multiple types of broadcast packets, and different types of broadcast packets are identified by different type values. For example, when the type value is 0000, it means that the broadcast packet is a general type of broadcast packet (ADV_IND), and any Bluetooth device can use this type of data packet when sending broadcast data to the outside world; when the value of the type field is 0100 , indicating that the broadcast packet is a scan reply data packet (ADV_SCAN_RSP). When the scan device receives a broadcast message, it can use this type of data packet to send a reply message to the broadcast device.

The "Broadcasting device address" field (AdvA) is used to write the physical address of the broadcasting device, which can be either the public address of the broadcasting device or the random address of the broadcasting device;

The "Data" field (Data) is used to write business data. For example, when the mobile phone 100 sends an event notification message to the Bluetooth headset 120, the description information of the incoming call event may be written in the "data" field of the broadcast packet.

It should be noted that FIG. 3 only shows some fields in the broadcast packet, and other fields in the broadcast packet may refer to the provisions of the Bluetooth protocol, and will not be repeated.

Specific embodiments of the present application will be described below with reference to the scenario shown in FIG. 1a, but it can be understood that the present application is not limited thereto. In the scenario shown in FIG. 1 a , the Bluetooth headset 120 establishes a Bluetooth connection with the tablet 110 , and the terminal device (eg, mobile phone 100 ) does not establish a Bluetooth connection with the Bluetooth headset 120 . At this time, the terminal device receives the incoming call event E (the figure is 10086 incoming calls).

[Example 1]

This embodiment is used to provide an event notification method. The specific technical solution of this embodiment is described below with reference to the scene in FIG. 1a. Referring to FIG. 1a, when the user is listening to the audio content on the tablet 110 through the Bluetooth headset 120, the terminal device (eg, the mobile phone 100) receives the incoming call event E. In order to prevent the user from missing an incoming call, the terminal device notifies the user of the incoming call event E through the Bluetooth headset 120 .

Specifically, referring to FIG. 4 , the event notification method provided by this embodiment includes the following steps:

S110: The terminal device (as the first Bluetooth device) receives the incoming call event E (as the first event). The terminal device is a device with a telephone function (for example, the mobile phone 100 ). Exemplarily, the terminal device implements the phone function through a call application installed on the terminal device, and the call application may be a system phone application or a third-party application (for example, WeChat ^TM ).

In this embodiment, the "incoming call" can be a voice call or a video call; it can be an incoming call received by the system phone application, or an incoming call received by a third-party application (for example, WeChat ^TM , Facetime ^TM , etc.); It may be an incoming call received based on circuit switching (Circuit Switching, CS), or it may be an incoming call received based on VoIP.

When the terminal device receives the incoming call event, it will play the incoming call ringtone to prompt the user to answer the incoming call. However, referring to FIG. 1a, if the user is using the Bluetooth headset 120 to listen to the music on the tablet 110, the incoming call ringtone on the terminal device may be covered by the music sound played in the Bluetooth headset 120, so the user may not hear the incoming call ringtone, As a result, incoming calls on the terminal device will be missed.

To this end, in this embodiment, the terminal device pushes the incoming call event message to the Bluetooth headset 120 to remind the user of the incoming call event through the Bluetooth headset 120 to prevent the user from missing an incoming call on the terminal device. The following steps S120 to S150 will introduce the process in detail.

S120: In response to receiving the incoming call event E, the terminal device queries whether there is a Bluetooth headset in a Bluetooth connection state in the local area network 150 where the terminal device is located. If it exists, step S130 is executed to further judge whether the Bluetooth headset is a user-trusted device; if not, the method ends. When the Bluetooth headset is in the Bluetooth connection state, it means that the user is using the Bluetooth headset. Therefore, this step is beneficial to ensure that the incoming call event E is notified to the user through the Bluetooth headset.

Exemplarily, the terminal device can query whether there is a Bluetooth headset 120 in the Bluetooth connection state in the local area network 150 by any of the following methods:

Example 1: The terminal device sends a Bluetooth connection request to the Bluetooth headset 120. Since the Bluetooth headset 120 has already connected with the tablet 110, the Bluetooth headset 120 sends a reply rejecting the connection request to the mobile phone. The reply carries the reason for rejecting the connection request, such as information indicating that a connection has been established with other devices. In this way, the terminal device can know that the Bluetooth headset 120 is in the Bluetooth connection state.

Example 2: After the Bluetooth headset 120 establishes a Bluetooth connection with the tablet 110, it discloses its own communication status information in the form of Bluetooth broadcast, such as information indicating that the Bluetooth headset itself has established a Bluetooth connection with a specific device (eg, tablet 200). In this way, the terminal device can learn that the Bluetooth headset 120 is in the Bluetooth connection state by monitoring the Bluetooth broadcast.

Example 3: After the Bluetooth headset 120 establishes a Bluetooth connection with the tablet 110, the tablet 110 reports the connection event to the gateway 140, the hub device in the local area network 150, so that the gateway 140 can record the communication status information of the Bluetooth headset 120: "with Tablet 110 establishes a Bluetooth connection". After receiving the incoming call event E, the terminal device sends a query request to the gateway 140 to query whether the local area network 150 has a Bluetooth headset in a Bluetooth connection state. After receiving the query request, the gateway 140 replies to the terminal device the device identification of the Bluetooth headset 120 (for example, the device name of the Bluetooth headset 120, the MAC address, etc.) and the communication status information of the Bluetooth headset 120: "establish a Bluetooth connection with the tablet 110" , in this way, the terminal device can know that the Bluetooth headset 120 is in the Bluetooth connection state.

The terminal device may also query whether there is a Bluetooth headset in the Bluetooth connection state in the local area network 150 in other ways, which will not be described in detail.

S130: The terminal device determines whether the Bluetooth headset 120 is a device trusted by the user. If the Bluetooth headset 120 is a user-trusted device, step S140 is executed to notify the Bluetooth headset 120 that the terminal device has received a message of the incoming call event E (hereinafter referred to as "incoming call time notification message" or "notification message"); if the Bluetooth headset 120 If 120 is not a user trusted device, the terminal device will not send a notification message, and the method ends. Therefore, this embodiment can avoid unnecessary information leakage, thereby improving the security of user information.

The following exemplarily provides a method for the terminal device to determine whether the Bluetooth headset 120 is a device trusted by the user.

Example 1: When the Bluetooth headset 120 is a device that has completed Bluetooth pairing with the terminal device, the terminal device considers the Bluetooth headset 120 to be a user-trusted device; otherwise, the terminal device considers that the Bluetooth headset 120 is not a user-trusted device. In this embodiment, the terminal device determines the Bluetooth headset 120 by matching the device identifier of the Bluetooth headset 120 (for example, the MAC address of the Bluetooth headset 120 obtained in step S120 ) with the device list of paired devices stored in the terminal device. For the device that has completed Bluetooth pairing with the end device.

Example 2: When the Bluetooth headset 120 is a device that has completed Bluetooth pairing with the terminal device, and the Bluetooth headset 120 satisfies at least one of the following conditions, the terminal device considers the Bluetooth headset 120 to be a user-trusted device; otherwise, the terminal device considers the Bluetooth headset The 120 is not a device that users trust.

Condition A: During the historical communication process of the terminal device, the number of times that the Bluetooth headset 120 successfully establishes a Bluetooth connection with the terminal device exceeds the set threshold M1. When the number of times that the Bluetooth headset 120 establishes a Bluetooth connection with the terminal device exceeds a certain number of times, it indicates that the Bluetooth headset 120 is a device frequently used by the user, thus indicating that the Bluetooth headset 120 is a device trusted by the user. This embodiment does not limit the value of the set threshold M1, for example, the set threshold M1 may be 3 times, 10 times, or the like. It can be understood that the larger the value of the set threshold M1 is, the more beneficial it is to improve the security of information.

In this embodiment, in the historical communication process of the terminal device, after the terminal device establishes a Bluetooth connection with the Bluetooth headset 120 , the terminal device records the number of times that the terminal device establishes the Bluetooth connection with the Bluetooth headset 120 . By comparing the recorded times with the set threshold M1, the terminal device determines that the number of times it establishes a Bluetooth connection with the Bluetooth headset 120 is greater than the set threshold M1. Therefore, the Bluetooth headset 120 satisfies the condition A.

Condition B: The Bluetooth headset 120 is designated by the user as a legitimate device to receive the "incoming call event notification message". After the user specifies the validity of the Bluetooth headset 120, it means that the user confirms that the Bluetooth headset 120 is a trusted device. Figures 5 and 6 illustrate exemplary methods for a user to designate a device as a legitimate device to receive an "incoming call event notification message".

Refer to Figure 5. Figure 5(a) is the Bluetooth setting interface in the terminal device setting application. When the user opens the interface, area A of the interface displays the device list of paired Bluetooth devices, and area B displays the device list of available Bluetooth devices. When the user clicks on a certain device (device "HUAWEI FreeBuds Pro") in the area A, the terminal device pops up a selection box 160 as shown in Figure 5(b). When the user clicks the “Allow” button in the selection box 160, the terminal device adds the device identification (eg, MAC address) of the device to the trust list, so as to designate the device (device “HUAWEI FreeBuds Pro”) as receiving the “Incoming Call Event” Notify message" legitimate device.

Refer to Figure 6. FIG. 6( a ) is the same interface as FIG. 5( a ), that is, the meanings of area A and area B in FIG. 6( a ) are the same as those of FIG. 5( a ), and will not be repeated. When the user clicks on a certain device (device "S3") in the area B, the terminal device pops up a pairing prompt box 170 as shown in FIG. 6(b). After the user clicks the "pairing" button in the pairing prompt box 170, the terminal device pops up a selection box 180 as shown in Fig. 6(c). Same as FIG. 5(b), when the user clicks the “Allow” button in the selection box 180, the terminal device adds the device identification (eg, MAC address) of the device to the trust list, so as to add the device (device “S3”) to the trust list Designated as a legitimate device to receive Incoming Call Event Notification Messages.

In addition, when the user does not call up the interfaces shown in Fig. 5(b) and Fig. 6(c), or the user clicks the "Reject" or "Close" button on the prompt box 160 and the prompt box 180, the terminal device will not The corresponding device is added to the trusted list. That is to say, the default setting of the terminal device is not to designate the device as a legitimate device to receive "incoming call event notification messages", and to designate the device as a legitimate device to receive "incoming call event notification messages" only with the explicit permission of the user , so as to further ensure the security of information. In addition, the terminal device can also encrypt the trust list to further ensure the security of the information.

In this embodiment, the terminal device determines that the Bluetooth headset 120 is a legitimate device designated by the user to receive the "incoming call event notification message" by matching the device identifier of the Bluetooth headset 120 with the trust list. Therefore, the Bluetooth headset 120 satisfies the condition B.

In Example 2, the reason for adding judgment on condition A and condition B is: in some scenarios, the user may borrow other people's Bluetooth headset 120, at this time, the user needs to connect other people's Bluetooth headset with his own device (for example, terminal device) to pair. Therefore, if the Bluetooth headset 120 is determined to be a user-trusted device only based on the condition of "paired", it is still possible to send personal information to the Bluetooth headsets of other users. For this reason, in Example 2, the judgment of condition A and/or condition B is added to further ensure that the Bluetooth headset 120 is a device trusted by the user.

S140: The terminal device sends an incoming call event notification message (as the first message) on the Bluetooth broadcast channel to notify the Bluetooth headset 120 (as the second Bluetooth device) of the "incoming call event E".

Specifically, the terminal device sends the incoming call event notification message by sending the broadcast packet A on the Bluetooth broadcast channel. The description information of the incoming call event E is written in the broadcast packet A, so that when the Bluetooth headset 120 receives the broadcast packet A, the incoming call event E can be known.

In this embodiment, the description information of the event to be notified includes one or more of the following:

Device identification information of the first Bluetooth device: for example, the device name (for example, the most handsome boy), the MAC address of the device (for example, the MAC address of the Bluetooth chip of the mobile phone), and the serial number of the device in the local area network (for example, Node 001);

Device type information of the first Bluetooth device: for example, a mobile phone, a tablet, a car device, a smart speaker, a smart home appliance (eg, a washing machine, a microwave oven, a smart door lock, etc.), and a smart ornament (eg, an alarm clock, a thermometer, etc.).

Event time information: the time when the event to be notified occurs, for example, the time "12:08" when the terminal device receives the incoming call event E.

Event type information: for example, an incoming call event, a schedule reminder event, a doorbell time, a task completion event (for example, the washing program of the washing machine is completed, the timer is completed), and the like.

An example of broadcast packet A is given in FIG. 7 . Among them, the broadcast packet A is a general type of broadcast packet (ADV_IND), and the description information of the incoming call event E is written in the "data" field, which specifically includes: the device name of the terminal device "the most beautiful boy", the terminal device receives an incoming call Time "12:08" of event E and event type "Incoming call event". In other examples, the event description information in the broadcast packet A may be more or less than the above-mentioned information.

S150: The Bluetooth headset 120 receives the incoming call event notification message, and determines whether it is the target receiving device of the incoming call event notification message.

Specifically, the Bluetooth headset 120 scans the Bluetooth broadcast channel to receive an incoming call event notification message (ie, broadcast packet A) sent by the terminal device. After receiving the incoming call event notification message, the Bluetooth headset 120 further determines whether it is the target receiving device of the incoming call event notification message.

Referring to FIG. 7 , in the present embodiment, the device identifier of the Bluetooth headset 120 (specifically, the MAC address of the Bluetooth headset 120 ) is written in the “data” field of the broadcast packet A, which is the transmission carrier of the incoming call event notification message, and the Bluetooth headset 120 Determine whether it is the target receiving device of the incoming call event notification message according to the MAC address in the broadcast packet A. Specifically, when the MAC address of the Bluetooth headset 120 is the same as the MAC address in the broadcast packet A, the Bluetooth headset 120 determines that it is the target receiving device of the incoming call event notification message; otherwise, the Bluetooth headset 120 determines that it is not the target of the incoming call event notification message receiving device.

When the Bluetooth headset 120 determines that it is the target receiving device of the incoming call event notification message, step S160 is further performed to respond to the incoming call event notification message (for example, play the prompt audio for prompting the incoming call event E); otherwise, the Bluetooth headset 120 Ignore incoming call event notification messages to avoid false disclosure of user information.

In addition, if there are multiple second Bluetooth devices that meet the conditions described in steps S120 and S130 around the terminal device, the terminal device will prepare multiple broadcast packets A in this way, and the "data" field of each broadcast packet A is written in The MAC address of one of the second Bluetooth devices, and the multiple broadcast packets A are sent in sequence, but the present application is not limited to this. In other embodiments, the broadcast packet A may include multiple MAC addresses of the second Bluetooth device that meet the conditions described in steps S120 and S130 (that is, the "data" field of the broadcast packet A includes multiple MAC addresses). After the Bluetooth headset 120 receives the broadcast packet A, as long as its own MAC address is one of the multiple MAC addresses, step S160 can be executed.

In addition, if there are multiple Bluetooth devices (referred to as "available Bluetooth devices") that meet the conditions described in steps S120 and S130 around the terminal device, the terminal device can select one of them as the target receiving device of the broadcast packet A (as the second Bluetooth device) device), and write the MAC address of the target receiving device in the "Data" field of the broadcast packet A. This embodiment does not limit the method for the terminal device to select a target receiving device from a plurality of available Bluetooth devices, and several examples are given below.

Example 1: The terminal device selects the nearest device among multiple available Bluetooth devices as the target receiving device. Specifically, the terminal device can obtain the distance between the terminal device and multiple available Bluetooth devices through the Bluetooth proximity sensing technology, and select the device with the smallest distance among them as the target receiving device.

Example 2: The terminal device selects the device that has established the most Bluetooth connections with the terminal device from among multiple available Bluetooth devices as the target receiving device. It can be understood that the device that establishes the most Bluetooth connections with the terminal device should be the device most commonly used by the user. In this example, the device is used as the target receiving device, which is beneficial to ensure the user who is notified of the incoming call event E.

Example 3: The terminal device selects the device with the best compatibility with the terminal device among multiple available Bluetooth devices as the target receiving device. For example, the device belonging to the same brand (for example, HUAWEI ^TM ) as the terminal device is used as the target receiving device. equipment. Specifically, the terminal device may also store the usage priorities of multiple available Bluetooth devices (for example, the usage priorities determined according to the compatibility of each available Bluetooth device and the terminal device). When the terminal device receives the incoming call event E , and select the device with the highest priority from the multiple available second Bluetooth devices as the target receiving device.

S160: The terminal device performs a response action in response to the incoming call event notification message. Specifically, referring to FIG. 4 , the process of performing the response action by the Bluetooth headset 120 includes:

S161: The Bluetooth headset 120 sends a response message to the terminal device.

Specifically, the Bluetooth headset 120 sends a response message to the terminal device by sending a broadcast packet B to the terminal device on the Bluetooth broadcast channel. An example of broadcast packet B is given in FIG. 8 .

Referring to FIG. 8 , the Bluetooth headset 120 sends a response message to the terminal device by scanning the reply data packet. Therefore, the value of the “Type” field (Adv PDU Type) of the broadcast packet B is 0100; ) is the MAC address of the terminal device (the MAC address can be parsed from the broadcast packet A sent by the terminal device), so the broadcast packet B is the data packet replied to the terminal device; the "data" field of the broadcast packet B includes The acknowledgment message "NOTICE ACKNOWLEDGE", when the terminal device receives the broadcast packet B, can determine that the Bluetooth headset 120 has received the broadcast packet A.

FIG. 8 is an exemplary illustration of broadcast packet B, and other modifications may be made by those skilled in the art. For example, in other embodiments, the "Data" field of the broadcast packet B not only includes "NOTICE ACKNOWLEDGE", but may also include the content in the "Data" field of the broadcast packet A. In this way, the terminal device can more accurately confirm that the broadcast packet B is a reply to the broadcast packet A.

S162: The Bluetooth headset 120 plays a prompt audio, and the prompt audio is used to prompt the user of "call event E". Specifically, referring to FIG. 9 , the process of playing the prompt audio by the Bluetooth headset 120 includes the following steps:

S162a: The Bluetooth headset 120 determines whether its current audio playback service is a call service.

The Bluetooth protocol supports two types of audio playback services, namely call service and communication service. When the tablet 110 outputs audio to the Bluetooth headset 120, it will provide the Bluetooth headset 120 with the service identifier of the audio playback service. For example, the service identifier of the call service is MODE_IN_CALL, the service identifier of the communication service is MODE_IN_COMMUNICATION, and the Bluetooth headset 120 sends the service identifier according to the tablet 110. The service identifier of the current audio playback service can determine the service type of the current audio playback service.

When the current audio playback service of the Bluetooth headset 120 is a call service, it means that the user is using the Bluetooth headset 120 to make a real-time call with other users. If the user's real-time call is interrupted, there will be a bad experience. Therefore, in this scenario, the Bluetooth headset 120 does not play the prompt audio for the time being, but executes steps S162e to S162g to delay playing the prompt audio.

When the current audio playback service of the Bluetooth headset 120 is other than the call service (eg, communication service, no audio is played), the Bluetooth headset 120 performs steps S162b to S162d to play the prompt audio at the current moment.

S162b: The Bluetooth headset 120 sends a playback pause instruction to the tablet 110, so that the tablet 110 pauses the current audio playback service.

Specifically, the Bluetooth headset 120 sends a pause play instruction to the tablet 110 through the point-to-point Bluetooth communication channel between the Bluetooth headset 120 and the tablet 110 . After receiving the instruction, the tablet 110 suspends the currently running audio playback application (eg, Youku Video ^TM , Kuwo Music ^TM ) to suspend the output of audio signals to the Bluetooth headset 120 . In addition, when the Bluetooth headset 120 is not currently playing audio, the Bluetooth headset 120 may omit this step.

S162c: The Bluetooth headset 120 plays a prompt audio (as the first audio), and the prompt audio is used to prompt the user of "call event E".

After suspending the current audio playing service, the Bluetooth headset 120 starts playing the prompt audio. In this embodiment, the prompt audio carries one or more items of event description information.

In some examples, the prompt audio is audio preset in the Bluetooth headset 120 . For example, a plurality of prompt audios are preset in the Bluetooth headset 120, and different prompt audios correspond to different event types. After receiving the broadcast packet A, the Bluetooth headset 120 parses the broadcast packet A to determine the event type information carried in the data packet A. Furthermore, the Bluetooth headset 120 plays the prompt audio corresponding to the event type information carried by the data packet A.

In other examples, the Bluetooth headset 120 has a preset voice library. After receiving the broadcast packet A, the Bluetooth headset 120 parses and obtains the event description information contained in the broadcast packet A, and converts the text of the event description information into a prompt voice according to a preset voice library.

On this basis, the content of the prompt audio is not limited in this embodiment, and some examples are given below.

Example 1: The prompt audio carries event type information. For example, when the event type is an incoming call event, the prompt audio is the preset phone ringtone; when the event type is the timer task completion, the preset prompt audio is played, or the prompt tone including the voice content "timer is up" is played. ;

Example 2: The prompt audio carries device identification information and event type information. For example, referring to Figure 7, when the device is identified as "the most beautiful boy" and the event type is "incoming call event", the prompt audio includes the voice content "the most beautiful boy has received an incoming call, please deal with it in time";

Example 3: The prompt audio carries the device type information. For example, when the device type is "laptop", the prompt audio includes the voice content "new message on laptop, please check".

In this embodiment, the prompt audio carries one or more pieces of event description information, but the application is not limited to this. In other embodiments, the prompt audio may be formatted audio unrelated to the event description information (for example, the prompt audio is a formatted voice "please check the new message"); for another example, in order to improve user experience, the prompt audio may also have Interesting audio (eg, personality audio, funny audio), etc. In addition, the prompt audio played by the Bluetooth headset 120 may be audio downloaded from the terminal device side.

S162d: The Bluetooth headset 120 sends a playback resume instruction to the tablet 110, so that the tablet 110 resumes the audio playback service.

After playing the prompt audio, the Bluetooth headset 120 sends an instruction to resume playing to the tablet 110 . After the tablet 110 receives the instruction, the audio playback application on the tablet 110 (the application suspended in step S162b ) resumes outputting audio signals to the Bluetooth headset 120 .

S162e: The Bluetooth headset 120 adds a prompt audio playback task to the task queue, so as to play the prompt audio after the current call service is completed.

S162f: The Bluetooth headset 120 receives a signaling that the call ends.

After the call service on the tablet 110 ends (for example, after the user hangs up the current call on the tablet 110), the tablet 110 sends a call end signaling to the headset, so that the terminal device terminal device receives the call end signaling.

S162g: The Bluetooth headset 120 plays the prompt audio.

After receiving the signaling of the end of the call, the Bluetooth headset 120 starts to play the prompt audio. For the content of the prompt audio, reference may be made to the description in step S162c, and details are not repeated here.

In addition, in this step, since the prompt audio is played with a delay (that is, the prompt audio is played after the end of the call service), the time information of the incoming call event E can be added to the prompt audio, so that the user is informed of the incoming call event E. Time of occurrence. Exemplarily, the prompt audio includes a voice "the most beautiful boy received a call at 12:08, please deal with it in time".

The above steps S162a-S162g describe the process of playing the prompt audio by the Bluetooth headset 120, but the present application is not limited to this, and those skilled in the art can make other modifications on this basis.

For example, in step S162a, if the Bluetooth headset 120 judges that its current audio playback service is a call service, it can first play a shorter audio (as the second audio, shorter than the prompt audio in step S162c or step S162g), for example , "Di Di Di Di" sound to alert the user that there is a new event. After the current call service ends, the prompt audio determined in step S162g is played again. In this way, it can not only play a certain prompting role, but also avoid affecting the normal conversation of the user.

To sum up, this embodiment provides an event notification method. When an incoming call event E is received on the terminal device, an incoming call event notification message is sent to the Bluetooth headset 120 through a Bluetooth broadcast channel. After receiving the notification message, the Bluetooth headset 120 plays a prompt audio to prompt the user of "incoming call event E", so as to prevent the user from missing an incoming call.

In addition, the terminal device sends an incoming call event notification message to the Bluetooth headset 120 through the Bluetooth broadcast channel, so that a Bluetooth connection does not need to be established between the terminal device and the Bluetooth headset 120, so it can be applied to various Bluetooth devices (for example, only one Bluetooth connection is supported) channel Bluetooth headset), with better adaptability.

It should be noted that this embodiment is an exemplary illustration of the technical solution of the application, and those skilled in the art can make other modifications.

For example, in this embodiment, the terminal device sends an incoming call event notification message to the Bluetooth headset 120 that meets the preset condition, where the preset condition includes the conditions described in step S120 (that is, the Bluetooth headset 120 is a headset in a Bluetooth connection state), As well as the conditions described in step S130 (that is, the Bluetooth headset 120 is a device trusted by the user), the present application is not limited to this. In other embodiments, the preset condition may only include one of the conditions described in step S120 and the condition described in step S130; or, the preset condition may not include additional conditions, for example, the terminal device sends an incoming call event to any Bluetooth device notification message.

For example, in other embodiments, the Bluetooth headset 120 prompts the user "incoming call event E" by means other than "playing prompt audio". For example, the Bluetooth headset 120 is provided with a flashlight or a vibration motor. When the Bluetooth headset 120 receives the incoming call event notification message, it prompts the user "calling event E" by flashing the flashlight or vibrating the motor.

For example, in other embodiments, after the terminal device determines in step S130 that the Bluetooth headset 120 is a user-trusted device, it provides the Bluetooth headset 120 with a key B, where the key B matches the key A stored by the terminal device itself right key. When the terminal device sends the broadcast packet A to the Bluetooth headset 120, the key A is used to encrypt the MAC address of the Bluetooth headset 120 in the broadcast packet A and/or the description information of the incoming call event E. Since only the Bluetooth headset 120 has the key B paired with the key A, only the Bluetooth headset 120 can decrypt the valid information in the broadcast package A, and other devices cannot know the valid information in the broadcast package A, so that they can decrypt the valid information in the broadcast package A. To further ensure the security of information.

For example, in other embodiments, the execution order of some steps may be changed, for example, the execution order of steps S120 and S130 may be changed; or some steps may be omitted, for example, step S161 and the like may be omitted.

[Example 2]

On the basis of the first embodiment, this embodiment improves the actions on the side of the terminal device, specifically, adding a message retransmission mechanism of the terminal device. In this embodiment, after sending the incoming call event notification message, the terminal device resends the incoming call event notification message if it does not receive a response message from the Bluetooth headset 120 within the set time. This embodiment is beneficial to ensure that the Bluetooth headset 120 does not miss the notification message from the terminal device.

Specifically, referring to FIG. 10 , this embodiment includes the following steps:

S210: The terminal device receives the incoming call event E.

S220: In response to receiving the incoming call event E, the terminal device queries whether there is a Bluetooth headset 120 in a Bluetooth connection state in the local area network where the terminal device is located. If it exists, step S230 is executed to further judge whether the Bluetooth headset 120 is a user-trusted device; if not, the method ends.

S230: The terminal device determines whether the Bluetooth headset 120 is a device trusted by the user. If the Bluetooth headset 120 is a user-trusted device, step S240 is executed to notify the Bluetooth headset 120 that the terminal device has received the incoming call event E; if the Bluetooth headset 120 is not a user-trusted device, the terminal device will not send a notification message. method ends.

S240: The terminal device sends an incoming call event notification message on the Bluetooth broadcast channel to notify the Bluetooth headset 120 of the "incoming call event E". In addition, in this embodiment, the terminal device records the number of times i that the terminal device sends an incoming call event notification message, and the terminal device adds 1 to the number of times i after each sending an incoming call event notification message.

Steps S210 to S240 are substantially the same as steps S110 to S140 in the first embodiment. Therefore, the details not described in the steps may refer to the description in the first embodiment, and will not be repeated.

S250: The terminal device starts a timer. The terminal device starts a timer program after sending the broadcast message. This embodiment does not limit the time duration of the timer, for example, 3s, 7s, and the like.

S260: The terminal device determines whether it has received a response message from the Bluetooth headset 120 before the timer expires. If so, the terminal device executes step S270 to close the timer; if not, the terminal device executes step S280.

S270: The terminal device closes the timer. The terminal device terminates the timer program started in step S250, and the method ends.

S280: The terminal device determines whether the number of times the incoming call event notification message is sent reaches the set threshold M2. If it is reached, the terminal device does not re-send the notification message, and the method ends; if not, the terminal device returns to step S240 to re-send the notification message. This embodiment does not limit the specific value of the set threshold value M2. For example, the set threshold value M2 may be set to 2 times, 5 times, or the like.

That is, the terminal device performs a limited number of message retransmissions. When the number of times the terminal device sends the notification message reaches the set threshold M2, even if no response message from the Bluetooth headset 120 is received, the notification message will not be resent, thereby saving energy consumption of the terminal device.

To sum up, in this embodiment, after the terminal device sends an incoming call event notification message, if it does not receive a response message from the Bluetooth headset 120, it performs message retransmission. Therefore, this embodiment is beneficial to ensure that the Bluetooth headset 120 does not miss the notification message from the terminal device.

The following describes a structural diagram 200 of a Bluetooth system provided according to an embodiment of the present application with reference to FIG. 11 . The Bluetooth system 200 includes a Bluetooth device 210 (eg, a mobile phone) and a Bluetooth device 220 (eg, a Bluetooth headset).

Wherein, the Bluetooth device 210 includes:

System framework layer 211: for receiving incoming call events, and notifying the phone application 212 of the incoming incoming call events; and, determining that there is a Bluetooth device 220 in a Bluetooth connection state and paired with the Bluetooth device 210 in the local area network; and, generating an incoming call event notification message, and send the incoming call event notification message through the Bluetooth module 213 . The functions performed by the system framework layer 211 may correspond to steps S110 to S140 in FIG. 4 and steps S210 to S280 in FIG. 10 .

Phone application 212: used to generate an incoming call interface (eg, the interface displayed by the mobile phone 100 in FIG. 1a).

Bluetooth module 213: used to send an incoming call event notification message to the Bluetooth device 220 through a Bluetooth broadcast channel. The functions performed by the Bluetooth module 213 may correspond to step S140 in FIG. 4 and step S240 in FIG. 10 .

Bluetooth device 220 includes:

Bluetooth module 221: used for receiving incoming call event notification messages on the Bluetooth broadcast channel; and determining whether the Bluetooth device 220 is the target receiving device of the incoming call event notification message; and, sending a response message to the Bluetooth device 210 on the Bluetooth broadcast channel. The functions performed by the Bluetooth module 221 may correspond to steps S150 and S161 in FIG. 4 .

Audio playing module 222: used to play prompt audio. The functions performed by the audio playback module 222 may correspond to step S162 in FIG. 4 and steps S162a˜S162g in FIG. 9 .

Referring now to FIG. 12, shown is a block diagram of an electronic device 400 according to one embodiment of the present application. Electronic device 400 may include one or more processors 401 coupled to controller hub 403 . For at least one embodiment, the controller hub 403 is connected to 406 via a multidrop bus such as a Front Side Bus (FSB), a point-to-point interface such as a QuickPath Interconnect (QPI), or the like The processor 401 communicates. Processor 401 executes instructions that control general types of data processing operations. In one embodiment, the controller hub 403 includes, but is not limited to, a Graphics & Memory Controller Hub (GMCH) (not shown) and an Input/Output Hub (IOH) (which may be on a separate chip) (not shown), where the GMCH includes the memory and graphics controller and is coupled to the IOH.

Electronic device 400 may also include a coprocessor 402 and memory 404 coupled to controller hub 403 . Alternatively, one or both of the memory and GMCH may be integrated within the processor (as described in this application), with the memory 404 and coprocessor 402 coupled directly to the processor 401 and to the controller hub 403, the controller hub 403 and IOH are in a single chip.

The memory 404 may be, for example, Dynamic Random Access Memory (DRAM), Phase Change Memory (PCM), or a combination of the two. Memory 404 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions. The computer-readable storage medium stores instructions, in particular temporary and permanent copies of the instructions.

The electronic device 400 shown in FIG. 12 may be implemented as a first Bluetooth device and a second Bluetooth device, respectively. When the electronic device 400 is implemented as the first Bluetooth device, the instructions stored in the memory 404 may include: when executed by at least one of the processors, causing the first Bluetooth device to implement the methods shown in FIG. 4 , FIG. 9 , and FIG. 10 Instructions for the steps performed by the terminal device in . When the electronic device 400 is implemented as a second Bluetooth device, the instructions stored in the memory 404 may include: when executed by at least one of the processors, causing the second Bluetooth device to implement the methods shown in FIG. 4 , FIG. 9 , and FIG. 10 Instructions for the steps implemented by the Bluetooth headset.

In one embodiment, the coprocessor 402 is a special purpose processor, such as, for example, a high-throughput Many Integrated Core (MIC) processor, a network or communications processor, a compression engine, a graphics processor, a graphics processing unit General-purpose computing on graphics processing units (GPGPU), or embedded processors, etc. Optional properties of the coprocessor 402 are shown in Figure 12 with dashed lines.

In one embodiment, the electronic device 400 may further include a network interface (Network Interface Controller, NIC) 406 . The network interface 406 may include a transceiver for providing a radio interface for the electronic device 400 to communicate with any other suitable devices (eg, front-end modules, antennas, etc.). In various embodiments, network interface 406 may be integrated with other components of electronic device 400 . The network interface 406 can implement the functions of the communication unit in the above-mentioned embodiments.

The electronic device 400 may further include an input/output (I/O) device 405 . I/O 405 may include: a user interface designed to enable a user to interact with electronic device 400 ; a peripheral component interface designed to enable peripheral components to also interact with electronic device 400 ; and/or sensors designed to determine association with electronic device 400 environmental conditions and/or location information.

It is worth noting that Figure 12 is exemplary only. That is, although FIG. 12 shows that the electronic device 400 includes multiple devices such as the processor 401, the controller center 403, the memory 404, etc., in practical applications, the device using each method of the present application may only include the electronic device 400 Some of the devices, for example, may include only the processor 401 and the network interface 406 . The properties of the optional device in Figure 12 are shown in dashed lines.

Referring now to FIG. 13, shown is a block diagram of a System on Chip (SoC) 500 according to an embodiment of the present application. In Figure 13, similar components have the same reference numerals. Also, the dotted box is an optional feature of more advanced SoCs. In FIG. 13 , SoC 500 includes: interconnect unit 550 coupled to processor 510 ; system proxy unit 580 ; bus controller unit 590 ; integrated memory controller unit 540 ; , which may include integrated graphics logic, image processor, audio processor and video processor; Static Random Access Memory (SRAM) unit 530; Direct Memory Access (Direct Memory Access, DMA) unit 560. In one embodiment, coprocessor 520 comprises a special purpose processor, such as, for example, a network or communications processor, a compression engine, general-purpose computing on graphics processing units (GPGPU), a high-throughput MIC processor, or embedded processor, etc.

Static random access memory unit 530 may include one or more tangible, non-transitory computer-readable media for storing data and/or instructions. The computer-readable storage medium stores instructions, in particular temporary and permanent copies of the instructions.

The SoC shown in FIG. 13 may be provided in the first Bluetooth device and the second Bluetooth device, respectively. When the SoC is disposed in the first Bluetooth device, the static random access memory unit 530 stores instructions, the instructions may include: when executed by at least one of the processors, causing the first Bluetooth device to implement as shown in FIG. 4 and FIG. 9 . Instructions for steps implemented by the terminal device in the method shown in FIG. 10 . When the SoC is disposed in the second Bluetooth device, the static random access memory unit 530 stores instructions, the instructions may include: when executed by at least one of the processors, causing the second Bluetooth device to implement as shown in FIG. 4 and FIG. 9 . Instructions for steps implemented by the Bluetooth headset in the method shown in FIG. 10 .

The term "and/or" in this article is only an association relationship to describe the associated objects, indicating that there can be three kinds of relationships, for example, A and/or B, it can mean that A exists alone, A and B exist at the same time, and A and B exist independently B these three cases.

Each method implementation of the present application can be implemented by means of software, magnetic components, firmware, and the like.

Program code may be applied to input instructions to perform the functions described herein and to generate output information. The output information can be applied to one or more output devices in a known manner. For the purposes of this application, a processing system includes any system having a processor such as, for example, a Digital Signal Processor (DSP), a microcontroller, an application specific integrated circuit (ASIC), or a microprocessor.

The program code may be implemented in a high-level procedural language or an object-oriented programming language to communicate with the processing system. The program code may also be implemented in assembly or machine language, if desired. In fact, the mechanisms described herein are not limited to the scope of any particular programming language. In either case, the language may be a compiled language or an interpreted language.

One or more aspects of at least one embodiment may be implemented by representative instructions stored on a computer-readable storage medium, the instructions representing various logic in a processor, the instructions, when read by a machine, cause the machine to make Logic that implements the techniques described herein. These representations, known as "Intellectual Property (IP) cores," may be stored on tangible computer-readable storage media and provided to multiple customers or production facilities for loading into the actual manufacturing of the logic or processor in the manufacturing machine.

In some cases, an instruction converter may be used to convert instructions from a source instruction set to a target instruction set. For example, an instruction translator may transform (e.g., using static binary transform, dynamic binary transform including dynamic compilation), warp, emulate, or otherwise convert an instruction into one or more other instructions to be processed by the core. Instruction translators can be implemented in software, hardware, firmware, or a combination thereof. The instruction translator may be on-processor, off-processor, or partially on-processor and partially off-processor.

Claims

A Bluetooth system, characterized in that the Bluetooth system includes a first Bluetooth device and a second Bluetooth device that do not establish a Bluetooth connection with each other, wherein:

The first Bluetooth device is configured to receive a first event; and, in response to receiving the first event, send a first message to the second Bluetooth device through a Bluetooth broadcast channel, where the first message is used for notifying the second Bluetooth device of the first event;

The second Bluetooth device is configured to receive the first message on the Bluetooth broadcast channel, and perform a response action in response to the first message, wherein the response action at least includes prompting the user that the Describe the action of the first event.
The system according to claim 1, wherein the sending the first message to the second Bluetooth device through a Bluetooth broadcast channel comprises:

The first Bluetooth device sends the first message to the second Bluetooth device based on determining that the second Bluetooth device has established a Bluetooth connection with another Bluetooth device other than the first Bluetooth device.
The system of claim 1 or 2, the response action comprising playing a prompt audio for the first event.
The system according to claim 3, wherein the first message sent by the first Bluetooth device includes description information of the first event; and,

The prompt audio played by the second Bluetooth device includes the first audio, and the prompt audio carries the description information.
An event notification method for a first Bluetooth device, characterized in that the method includes:

received the first event;

In response to receiving the first event, a first message is sent to a second Bluetooth device through a Bluetooth broadcast channel, where the first message is used to notify the second Bluetooth device of the first event, wherein the first message is The second Bluetooth device has not established a Bluetooth connection with the first Bluetooth device.
The method according to claim 5, wherein the sending the first message to the second Bluetooth device through a Bluetooth broadcast channel comprises:

The first message is sent to the second Bluetooth device based on determining that the second Bluetooth device has established a Bluetooth connection with a Bluetooth device other than the first Bluetooth device.
The method according to claim 5 or 6, wherein the first message includes description information of the first event.
The method according to claim 7, wherein the description information of the first event comprises device identification information of the first Bluetooth device, device type information of the first Bluetooth device, and information of the first event. Event type information and/or time information when the first Bluetooth device receives the first event.
The method according to any one of claims 5 to 8, wherein the sending the first message to the second Bluetooth device through a Bluetooth broadcast channel further comprises:

If the response message from the second Bluetooth device is not received within a predetermined time after sending the first message, the first message will be retransmitted successively according to a set time interval until a response message from the second Bluetooth device is received. Two response messages from the Bluetooth device, or until the number of times of retransmitting the first message exceeds the set threshold.
The method according to any one of claims 5 to 9, wherein the sending the first message to the second Bluetooth device through a Bluetooth broadcast channel comprises:

The first message is sent to the second Bluetooth device based on determining that the second Bluetooth device is a device that has completed Bluetooth pairing with the first Bluetooth device.
The method according to any one of claims 5 to 9, wherein the sending the first message to the second Bluetooth device through a Bluetooth broadcast channel comprises:

Based on determining that the second Bluetooth device is a device that has completed Bluetooth pairing with the first Bluetooth device, and determining that the second Bluetooth device satisfies at least one of the following conditions, sending the second Bluetooth device the First message:

During the historical communication process of the first Bluetooth device, the number of times that the second Bluetooth device establishes a Bluetooth connection with the first Bluetooth device exceeds a set threshold;

The second Bluetooth device is designated by the user as a legitimate device to receive the first message.
The method according to any one of claims 5 to 11, wherein the first event is an incoming call event.
An event notification method for a second Bluetooth device, characterized in that the method includes:

A first message from a first Bluetooth device is received on a Bluetooth broadcast channel, the first message being used to notify the second Bluetooth device of a first event received by the first Bluetooth device, wherein the second Bluetooth device The Bluetooth device has not established a Bluetooth connection with the first Bluetooth device;

A response action is performed in response to the first message, wherein the response action includes at least an action for prompting the user of the first event.
14. The method of claim 13, wherein the response action comprises playing a prompt audio of the first event.
The method according to claim 14, wherein the first message includes description information of the first event; and,

The prompt audio played by the second Bluetooth device includes the first audio, and the prompt audio carries the description information.
The method according to claim 15, wherein the second Bluetooth device playing the prompt audio comprises:

The second Bluetooth device determines the service type of its current broadcast service;

When the second Bluetooth device determines that the service type of its current playback service is a call service, the second Bluetooth device plays the first audio after the current playback service ends; when the Bluetooth device determines that its current playback service is When the service type is other than the call service, the second Bluetooth device plays the first audio at the current moment.
The method of claim 16, wherein the prompt audio comprises a second audio, and the duration of the second audio is shorter than that of the first audio; and,

When the second Bluetooth device determines that the service type of its current playing service is a call service, the second Bluetooth device plays the second audio at the current moment, and plays the first audio after the current playing service ends.
The method according to any one of claims 13 to 17, wherein the response action further comprises:

A reply message to the first message is sent to the first Bluetooth device.
The method according to any one of claims 13 to 18, wherein the performing a response action in response to the first message comprises:

The second Bluetooth device performs the response action based on determining that it is a target recipient device of the first message.
The method according to claim 19, wherein the first message carries a device identifier of a target receiving device of the first message;

The second Bluetooth device determines that it is the target receiving device of the first message, including:

The second Bluetooth device matches its own device identification with the device identification carried in the first message to determine that it is the target receiving device of the first message.
The method according to any one of claims 13 to 20, wherein the second Bluetooth device is a Bluetooth headset, a Bluetooth speaker or a wearable device.
A Bluetooth device comprising:

memory for storing instructions executed by one or more processors of the Bluetooth device;

a processor, when the processor executes the instructions in the memory, it can cause the Bluetooth device to execute the event notification method according to any one of claims 5 to 12, or to execute any one of claims 13 to 21 The event notification method described in item.