Bluetooth connection method and related device

Abstract

The invention provides a Bluetooth connection method and a related device, and relates to the technical field of communication. In the method, when a first device is in a first mode, the first device can receive identification information of a second device sent by the second device; the first equipment in the first mode agrees to establish Bluetooth connection with trusted equipment indicated by a storage area of the first equipment; and then the first device determines that the identification information of the second device is the same as the identification information of the trusted device stored in the storage area of the first device, and the first device can establish a Bluetooth connection with the second device. Therefore, the first device establishes the Bluetooth connection with the second device under the condition that the first device determines that the identity of the second device is the trusted device, so that the security of establishing the Bluetooth connection between the first device and the second device can be improved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a Bluetooth connection method and related devices. Background Art

[0002] Bluetooth technology is a short-range wireless radio frequency communication technology. With the rapid development of Bluetooth technology, the application of electronic devices that support Bluetooth technology has become more common. Taking the electronic devices such as Bluetooth headsets and mobile phones as an example, after the Bluetooth headset establishes a Bluetooth connection with the mobile phone, the Bluetooth headset can receive audio data transmitted by the mobile phone, and users can answer calls, listen to music, etc. through the Bluetooth headset.

[0003] However, when any two electronic devices such as Bluetooth headsets and mobile phones establish a Bluetooth connection, there is a problem of indiscriminate Bluetooth connection. Summary of the invention

[0004] In order to solve the above problems, the present application provides a Bluetooth connection method and related devices, the purpose of which is to solve the problem of indiscriminate Bluetooth connection when two electronic devices establish a Bluetooth connection and improve the security of establishing a Bluetooth connection between two electronic devices.

[0005] In the first aspect, the present application provides a Bluetooth connection method, which can be applied to a first device. For example, the first device can be an electronic device such as a Bluetooth headset, a Bluetooth speaker, a smart watch, and smart glasses. In this method, the first device in the first mode can agree to establish a Bluetooth connection with a trusted device indicated by a storage area of ​​the first device. For example, the storage area of ​​the first device may include a storage list of the first device, and the storage list may store identification information of a trusted device for indicating a trusted device. The second device can send its own identification information to the first device. When the first device is in the first mode, the first device can receive the identification information of the second device sent by the second device. For example, the identification information of the second device may include the device identification information of the second device, the account identification information of the second user account logged in by the second device, etc.; then, the first device determines that the identification information of the second device is the same as the identification information of the trusted device stored in its own storage area, indicating that the second device is a trusted device of the first device, and the first device can establish a Bluetooth connection with the second device. For example, the second device can be an electronic device such as a mobile phone and a tablet computer.

[0006] In this way, the first device no longer establishes a Bluetooth connection with any electronic device indiscriminately. The first device can verify the identity of the second device. That is, when the first device determines that the second device is its trusted device, the first device establishes a Bluetooth connection with the second device. This can avoid the problem of affecting the communication security between the two due to the insecure identity of the second device, thereby improving the security of establishing a Bluetooth connection between the first device and the second device.

[0007] In a possible implementation, before the first device receives the identification information of the second device sent by the second device, the Bluetooth connection method may further include the following steps: the first device may receive the first indication information sent by the third device, the first indication information being used to instruct the first device to switch to the first mode; the first device may switch to the first mode in response to receiving the first indication information, indicating that the first device may switch to the first mode based on the received first indication information when it is not in the first mode; then, the first device may receive the identification information of the trusted device sent by the third device, for example, the identification information of the trusted device may include at least one of the device identification information of the trusted device, the account identification information of the user account logged in by the trusted device, the contact information of the trusted device, etc.; when the first device is in the first mode, the first device may store the identification information of the trusted device in the storage area. Exemplarily, the third device may be an electronic device such as a mobile phone or a tablet computer.

[0008] In this way, the third device can control the first device to switch to the first mode, so that the first device in the first mode can verify the identity of the second device that subsequently requests to establish a Bluetooth connection with the first device. At the same time, the third device controls the first device to switch to the first mode, and the first device can store the identification information of the trusted device sent by it to the storage area, so as to facilitate the subsequent verification of the identity of the second device, thereby improving the security of the Bluetooth connection established between the first device and the second device.

[0009] In a possible implementation, the first device receives the identification information of the trusted device sent by the third device, which may include: the first device receives the account identification information of the first user account sent by the third device, for example, the account identification information of the first user account may be the mobile phone number, email address, etc. associated with the first user account registered by the user, and the third device has logged in to the first user account. In this way, the account identification information of the first user account can be stored in the storage area as the identification information of the trusted device, indicating that the first device can use the electronic device that has logged in to the same user account as the first user account as a trusted device.

[0010] In one possible implementation, the first device determines that the identification information of the second device is the same as the identification information of the trusted device stored in the storage area, and the first device establishes a Bluetooth connection with the second device, which may include: the first device determines that the identification information of the second device is the same as the account identification information of the first user account stored in the storage area, indicating that the identification information of the second user account logged in by the second device is the same as the account identification information of the first user account, and the second device and the first device are logged in to the same user account, and the first device can establish a Bluetooth connection with the second device. In this way, when the second device is logged in to the same user account as the first user account, it can pass the identity authentication of the first device, which can improve the security of establishing a Bluetooth connection between the two. In addition, the second device logged in to the same user account can directly pass the identity authentication of the first device without user operation, which can improve the user experience.

[0011] In a possible implementation, the first device receives the identification information of the trusted device sent by the third device, which may include: the first device receives the device identification information of the second device sent by the third device, for example, the device identification information of the second device may be the MAC address of the second device, the device name of the second device, etc., and the device identification information of the second device may be sent by the third device to the first device in response to the operation of the third device inputting the device identification information of the second device, for example, the user may input the device identification information of the second device in the third device, and then the third device sends it to the first device. In this way, the device identification information of the second device may be stored in the storage area as the identification information of the trusted device, indicating that the third device can control the first device to add the identification information for indicating the trusted device, that is, the third device can control the first device to add a new trusted device, and the user can operate to add a trusted device on the basis of improving the security of the Bluetooth connection between the first device and the second device, which can improve the user experience.

[0012] In one possible implementation, the Bluetooth connection method may also include: the first device determines that the identification information of the second device is different from the identification information of the trusted device stored in the storage area, and the first device can send a prompt message to the third device, and the prompt message is used to prompt the second device to request to establish a Bluetooth connection with the first device. For example, the third device can display a pop-up window, and the pop-up window displays the prompt message that the second device requests to establish a Bluetooth connection with the first device; then the first device determines that it has received the second indication information sent by the third device, and establishes a Bluetooth connection with the second device, and the second indication information is used to indicate consent to the first device to establish a Bluetooth connection with the second device. For example, the pop-up window displayed by the third device includes a consent control, and the user triggers the consent control, indicating that the user agrees to the first device to establish a Bluetooth connection with the second device, and the third device can send the second indication information to the second device.

[0013] In this way, when the third device is still establishing a Bluetooth connection with the first device, and the first device determines that the identification information of the second device is different from the identification information of the trusted device stored in itself, the first device can request the third device to determine whether the second device can establish a Bluetooth connection with the first device. After the third device agrees, it indicates that the second device is a trusted device of the first device. The second device passes the identity authentication of the first device, which can improve the security of the Bluetooth connection established between the first device and the second device.

[0014] In a possible implementation, the Bluetooth connection method may also include: the first device determines that the second indication information sent by the third device is received, and stores the identification information of the second device in the storage area of ​​the first device. In this way, when the second device passes the identity authentication of the first device, it indicates that the second device is a trusted device of the first device, and the first device can store its identification information in the storage area to facilitate the subsequent establishment of a Bluetooth connection with the second device, that is, the two do not need the consent of the third device to reconnect, which can reduce user operations and improve user experience.

[0015] In a possible implementation, the Bluetooth connection method may also include: the first device determines that the third indication information sent by the third device is received, and the first device may send information to the second device to indicate that the first device refuses to establish a Bluetooth connection with the second device. For example, the first device may send a connection error message to the second device. The third indication information is used to indicate that the Bluetooth connection between the first device and the second device is refused. For example, the pop-up window displayed by the third device includes a rejection control. The user triggers the rejection control, indicating that the user refuses to establish a Bluetooth connection between the first device and the second device. The third device may send the third indication information to the second device. In this way, the third device refuses to establish a Bluetooth connection between the first device and the second device, indicating that the second device is not a trusted device of the first device and the second device has not passed the identity authentication of the first device, which can avoid communication security issues caused by the insecure identity of the second device.

[0016] In a possible implementation, the Bluetooth connection method may also include: the first device determines that the identification information of the second device is different from the identification information of the trusted device stored in the storage area, the first device may send information to the second device to indicate that the first device refuses to establish a Bluetooth connection with the second device, and send the contact information of the trusted device to the second device, for example, the trusted device may be a third device, the contact information of the trusted device may be the mobile phone number of the third device, etc., and the contact information of the trusted device is stored in the storage area of ​​the first device. In this way, when the first device and the second device are held by different users, and the first device is found by the user holding the second device, the user holding the second device can obtain the contact information of the trusted device of the first device, thereby increasing the possibility of the first device being recovered.

[0017] In a possible implementation, the Bluetooth connection method may also include: when the first device is in the second mode, the first device may receive the first communication connection request information sent by the third device, and the first device in the second mode agrees to establish a Bluetooth connection with the electronic device that sends the communication connection request information to the first device, indicating that the first device in the second mode can establish an indiscriminate Bluetooth connection with any electronic device; then the first device responds to receiving the first communication connection request information sent by the first device, and the first device can establish a Bluetooth connection with the third device. In this way, the first device in the second mode can still establish an indiscriminate Bluetooth connection with any electronic device, indicating that the user can use the first device in the first mode or the first device in the second mode, which can improve the user experience.

[0018] In a possible implementation, the Bluetooth connection method may also include: the first communication connection request information sent by the third device to the first device includes the identification information of the third device, for example, the first communication connection request information may include the device identification information of the third device, the account identification information of the first user account logged in by the third device, and the contact information of the third device. When the third device sends the first indication information to the first device to instruct the first device to switch to the first mode, the first device may store the identification information of the third device in the storage area of ​​the first device. In this way, when the third device controls the first device to switch to the first mode, the first device can determine that the third device is a trusted device to avoid the situation where the third device cannot connect back to the first device in the first mode.

[0019] In one possible implementation, the first device receives the identification information of the second device sent by the second device, which may include: the first device receives the second communication connection request information sent by the second device, the second communication connection request information includes the identification information of the second device, for example, the second device scans the device identification information of the first device broadcast by the first device, the second device can display the device identification information of the first device, the user can trigger the device identification information of the first device, and the second device can send the second communication connection request information to the first device in response to the user's triggering operation. In this way, the Bluetooth connection method provided by the present application can be implemented in the scenario where the second device requests to establish a Bluetooth connection with the first device, which can improve the security of the first device and the second device to establish a Bluetooth connection.

[0020] In a possible implementation, the first device receiving identification information of the second device sent by the second device may include: the first device may receive identification information of the second device broadcast by the second device, where the identification information of the second device includes account identification information of a second user account logged in by the second device;

[0021] Accordingly, the first device determines that the identification information of the second device is the same as the identification information of the trusted device stored in the storage area, and the first device establishes a Bluetooth connection with the second device, which may include: the first device determines that the account identification information of the second user account is the same as the identification information of the trusted device stored in the storage area, and the first device can send a third communication connection request message to the second device; then the first device can receive information sent by the second device to indicate that the second device agrees to establish a Bluetooth connection with the first device, indicating that the two have established a Bluetooth connection. In this way, the Bluetooth connection method provided by the present application can be implemented in the scenario where the first device automatically requests to establish a Bluetooth connection with the second device, which can improve the security of the Bluetooth connection between the first device and the second device, and can also reduce user operations and improve user experience.

[0022] In a second aspect, the present application provides an electronic device, which may be a first device, comprising a memory and a processor; the memory stores computer program code, the computer program code comprising computer instructions; one or more processors call computer instructions to enable the electronic device to execute the Bluetooth connection method of the first aspect mentioned above.

[0023] In a third aspect, the present application provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the Bluetooth connection method of the first aspect is implemented.

[0024] In a fourth aspect, the present application provides a computer program product, which includes a computer program code. When the computer program code is executed by an electronic device, the Bluetooth connection method of the first aspect is implemented. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 A signaling interaction diagram of a traditional Bluetooth connection method provided in an embodiment of the present application;

[0026] Figure 2 An application scenario of a Bluetooth connection method provided in an embodiment of the present application;

[0027] Figure 3 A signaling interaction diagram for establishing a Bluetooth connection by a Bluetooth device in normal mode provided in an embodiment of the present application;

[0028] Figure 4 A signaling interaction diagram of a mode switching phase of a Bluetooth device provided in an embodiment of the present application;

[0029] Figure 5 A signaling interaction diagram of a Bluetooth device in a strong binding mode during a Bluetooth connection phase provided in an embodiment of the present application;

[0030] Figure 6A signaling interaction diagram of a Bluetooth connection phase of a Bluetooth device in another strong binding mode provided in an embodiment of the present application;

[0031] Figure 7 A signaling interaction diagram of a Bluetooth connection phase of a Bluetooth device in a strong binding mode provided in another embodiment of the present application;

[0032] Figure 8 A signaling interaction diagram of a Bluetooth connection phase of a Bluetooth device in a strong binding mode provided in another embodiment of the present application;

[0033] Fig. 9 A signaling interaction diagram of the Bluetooth connection phase of a Bluetooth device in strong binding mode is also provided in an embodiment of the present application. DETAILED DESCRIPTION

[0034] First, the vocabulary involved in the embodiments of the present application is explained. It can be understood that this explanation is for a clearer understanding of the embodiments of the present application, and does not necessarily constitute a limitation on the embodiments of the present application.

[0035] Bluetooth device: In the embodiments of the present application, Bluetooth headsets, Bluetooth speakers, smart glasses, smart watches, etc. may be referred to as Bluetooth devices.

[0036] Electronic device: In the embodiments of the present application, terminal devices such as mobile phones, tablet computers, wearable devices, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA) and the like may be referred to as electronic devices.

[0037] The traditional Bluetooth connection method is: Figure 1 As shown, the electronic device is a mobile phone 110, the Bluetooth device is a Bluetooth headset 120, and the Bluetooth headset 120 and the mobile phone 110 establish a Bluetooth connection for the first time. The Bluetooth headset 120 acts as an advertiser to send a non-directional broadcast data frame ADV_IND (which can be called broadcast information) to the surroundings. For example, the Bluetooth headset 120 can send ADV_IND through any broadcast channel among broadcast channels 37-39. Figure 1Taking the Bluetooth headset 120 sending ADV_IND through the broadcast channel 37 as an example, the ADV_IND may include the device identification information of the Bluetooth headset 120, such as the Media Access Control Address (MAC address) of the Bluetooth headset 120, the device name of the Bluetooth headset 120, etc.

[0038] Combination Figure 1 As shown, the mobile phone 110 as the connector observer can scan ADV_IND and find the Bluetooth headset 120 through the device identification information of the Bluetooth headset 120 contained in ADV_IND. The mobile phone 110 can then send a connection request data frame CONNECT_REQ (which can be called a connection request) to the Bluetooth headset 120. For example, the mobile phone 110 can send the CONNECT_REQ through any data channel from data channel 0 to data channel 36. Figure 1 Take the mobile phone 110 sending the CONNECT_REQ through the data channel 36 as an example.

[0039] CONNECT_REQ may include the device identification information of the mobile phone 110 and the device identification information of the Bluetooth headset 120, for example, the MAC address of the mobile phone 110 and the MAC address of the Bluetooth headset 120. After the Bluetooth headset 120 receives the CONNECT_REQ, the Bluetooth headset 120 and the mobile phone 110 will enter the Bluetooth pairing stage, during which the Bluetooth headset 120 and the mobile phone 110 will jointly generate a communication key link key. Subsequently, the Bluetooth headset 120 will bind and store the generated link key with the device identification information of the mobile phone 110, and the mobile phone 110 will bind and store the link key with the device identification information of the Bluetooth headset 120. The Bluetooth headset 120 and the mobile phone 110 can encrypt the data communicated with each other through the link key, indicating that a Bluetooth connection has been established between the two.

[0040] Combination Figure 1As shown, when the Bluetooth headset 120 and the mobile phone 110 disconnect the Bluetooth connection and reconnect later, the Bluetooth headset 120 can send a directional broadcast data frame ADV_DIRECT_IND (which can be called broadcast information) to the mobile phone 110 through the broadcast channel 37. The ADV_DIRECT_IND includes the device identification information of the Bluetooth headset 120 and the device identification information of the mobile phone 110, such as the MAC address of the Bluetooth headset 120 and the MAC address of the mobile phone 110. The mobile phone 110 receives the ADV_DIRECT_IND sent by the Bluetooth headset 120 and can send CONNECT_REQ to the Bluetooth headset 120 through the data channel 36. The Bluetooth headset 120 and the mobile phone 110 can check whether the link key of the other party is stored based on the received identification information of the other party. If the link key of the other party is stored, the data communicated with each other can be encrypted based on the link key. If there is no link key of the other party, the Bluetooth pairing stage described above can be entered again.

[0041] Research has found that when both electronic devices and Bluetooth devices support Bluetooth technology, users can manually trigger their own electronic devices to establish a Bluetooth connection with the Bluetooth device. In response to the user's triggering operation, the electronic device will send a CONNECT_REQ to the Bluetooth device. However, when the Bluetooth device receives a CONNECT_REQ from any electronic device, it will agree to the CONNECT_REQ, indicating that the Bluetooth device has no requirements for the identity of the electronic device and can establish a Bluetooth connection with any electronic device without distinction. Assuming that user A holds a Bluetooth headset 120, a Bluetooth device, and user B holds a mobile phone 110, an electronic device, user B can operate to trigger the mobile phone 110 to establish a Bluetooth connection with the Bluetooth headset 120. This is likely to cause the problem of affecting the communication security between the two due to the insecurity of the identity of the electronic device.

[0042] Based on the above problems, there is an urgent need to explore a Bluetooth connection method that increases the identity authentication of electronic devices, so that Bluetooth devices can establish Bluetooth connections with electronic devices that have passed identity authentication, thereby improving the security of Bluetooth connections between Bluetooth devices and electronic devices.

[0043] Therefore, an embodiment of the present application provides a Bluetooth connection method, in which, during the process of establishing a Bluetooth connection between a first electronic device and a Bluetooth device, a user can trigger an operation on a communication management application of the first electronic device (also referred to as a third device), and the communication management application logs in to a user account (also referred to as a first user account). In response to the user's triggering operation, the first electronic device can control the Bluetooth device (also referred to as the first device) to switch from a normal mode (also referred to as a second mode) to a strong binding mode (also referred to as the first mode); then, when the Bluetooth device in the strong binding mode establishes a Bluetooth connection with a second electronic device (also referred to as the second device) for the first time, the Bluetooth device in the strong binding mode can verify the identity of the second electronic device, for example, determining whether the user account (also referred to as the second user account) logged in by the communication management application of the second electronic device is the same as the user account logged in by the communication management of the first electronic device, or determining whether the second electronic device is a trusted device authorized by the first electronic device; after the Bluetooth device determines that the second electronic device has passed the identity authentication, the Bluetooth device can establish a Bluetooth connection with the second electronic device.

[0044] In this way, when the Bluetooth device is in strong binding mode, it can authenticate the second device that may establish a Bluetooth connection with itself, avoiding the problem of the Bluetooth device indiscriminately establishing a Bluetooth connection with any electronic device, and improving the security of establishing a Bluetooth connection between the Bluetooth device and electronic devices.

[0045] The electronic device may establish a Bluetooth connection with the Bluetooth device using the standard Bluetooth protocol. When the electronic device uses the standard Bluetooth protocol, the broadcast information such as ADV_IND and the connection request such as CONNECT_REQ sent by the electronic device may include the device identification information of the electronic device itself.

[0046] The embodiment of the present application provides a private Bluetooth protocol, and the electronic device can also use the private Bluetooth protocol to establish a Bluetooth connection with the Bluetooth device. When the electronic device uses the private Bluetooth protocol, the broadcast information and connection request sent by it include the identification information of the electronic device, and the identification information of the electronic device can also include the account identification information of the user account logged in by the electronic device on the basis of including the device identification information.

[0047] Exemplarily, the device identification information of an electronic device may include the MAC address of the electronic device, the device name of the electronic device, and other information that identifies the electronic device; the account identification information of a user account may include the mobile phone number, email address, or account name used to register the user account, and other information that identifies the user account.

[0048] In a possible implementation, the user account may be a user account that can be logged in by both the system application and the third-party application of the electronic device. For example, the system application may be a setting application of the electronic device, and the third-party application may be a communication management application. For such electronic devices that support logging in the same user account in both the system application and the third-party application, it is called that the electronic device itself uses a private Bluetooth communication protocol to establish a Bluetooth connection with the Bluetooth device, and the system application and the third-party application of the electronic device both support using the private Bluetooth communication protocol to establish a Bluetooth connection with the Bluetooth device.

[0049] In another possible implementation, the user account may also be a user account that can be logged in by a third-party application of the electronic device, but the same user account cannot be logged in by the system application of the electronic device. For such electronic devices that do not support logging in the same user account in both the system application and the third-party application, it is called that the electronic device itself uses the standard Bluetooth communication protocol to establish a Bluetooth connection with the Bluetooth device, the system application of the electronic device supports the use of the standard Bluetooth communication protocol to establish a Bluetooth connection with the Bluetooth device, and the third-party application of the electronic device supports the use of a private Bluetooth communication protocol to establish a Bluetooth connection with the Bluetooth device.

[0050] It should be emphasized that the user accounts introduced in the embodiments of the present application are user accounts under the same operating system. For instance, in the example of an electronic device that does not support logging in the same user account to both system applications and third-party applications, the third-party application supports logging in to the user account of operating system A. It may be that the system application does not support logging in to the user account, or it may be that the system application does not support logging in to the user account of operating system A, but the system application can log in to the user account of operating system B.

[0051] Next, the application scenario of the technical solution of the present application is exemplified. The Bluetooth connection method provided by the technical solution of the present application may include three stages: a Bluetooth connection stage of a Bluetooth device in normal mode, a mode switching stage of a Bluetooth device, and a Bluetooth connection stage of a Bluetooth device in strong binding mode.

[0052] Combination Figure 2 As shown, taking the Bluetooth device (also referred to as the first device) as the Bluetooth headset 120, the electronic device (also referred to as the third device) as the mobile phone 110, and the electronic device (also referred to as the second device) as the mobile phone 130 as an example, in the Bluetooth connection stage of the Bluetooth device in normal mode, the mobile phone 110 establishes a Bluetooth connection with the Bluetooth headset 120 in normal mode (also referred to as the second mode); in the mode switching stage of the Bluetooth device, the mobile phone 110 controls the Bluetooth headset 120 to switch from normal mode to strong binding mode; in the Bluetooth connection stage of the Bluetooth device in strong binding mode (also referred to as the first mode), the mobile phone 130 establishes a Bluetooth connection with the Bluetooth headset 120 in strong binding mode.

[0053] The following embodiments are combined Figure 2 The three stages of the Bluetooth connection method provided in the embodiment of the present application described above are introduced respectively.

[0054] First enter the Bluetooth connection stage of the Bluetooth device in normal mode.

[0055] In some embodiments, the mobile phone 110 may be installed with a communication management application, and the communication management application of the mobile phone 110 may use a private Bluetooth communication protocol to establish a Bluetooth connection with the Bluetooth headset 120 in normal mode.

[0056] The Bluetooth headset can send ADV_IND, and after the mobile phone 110 scans the ADV_IND sent by the Bluetooth headset 120, the mobile phone 110 can then send CONNECT_REQ to the Bluetooth headset 120. The ADV_IND can include the device identification information of the Bluetooth headset 120, and the CONNECT_REQ can include the device identification information of the mobile phone 110 and the account identification information of the user account logged in by the communication management application (also referred to as the first user account). Then, the Bluetooth headset 120 can agree to the CONNECT_REQ and store the device identification information of the mobile phone 110 and the account identification information of the user account.

[0057] When the Bluetooth headset 120 in normal mode sends ADV_IND, it will agree to receive CONNECT_REQ sent by any electronic device, indicating that the Bluetooth headset 120 in normal mode can establish a Bluetooth connection with any electronic device without distinction.

[0058] It should be noted that the implementation method of the Bluetooth connection stage of the Bluetooth device in normal mode can be seen below Figure 3 A detailed description of the illustrated embodiment will not be expanded here.

[0059] After that, the mode switching phase of the Bluetooth device may be entered.

[0060] In some embodiments, the mobile phone 110 may be installed with a communication management application, which logs into a user account and controls the Bluetooth headset 120 to switch from a normal mode to a strong binding mode.

[0061] For example, the user interface of the communication management application of the mobile phone 110 may display a strong binding mode switching control. After the user triggers the strong binding mode switching control, the mobile phone 110 may send a mode switching indication message (also referred to as the first indication message) to the Bluetooth headset 120. After receiving the mode switching indication message, the Bluetooth headset may switch its normal mode to the strong binding mode.

[0062] It should be noted that the strong binding mode switching control displayed in the user interface of the communication management application is only an example. This application does not limit the content displayed in the user interface of the communication management application. After the user operation triggers the user interface, the mobile phone 110 can control the Bluetooth headset 120 to switch to the strong binding mode.

[0063] The Bluetooth headset 120 in strong binding mode can authenticate other electronic devices such as the mobile phone 130 that request to establish a Bluetooth connection, indicating that the Bluetooth headset 120 in strong binding mode no longer establishes a Bluetooth connection with any electronic device indiscriminately, but establishes a Bluetooth connection with electronic devices that have passed authentication.

[0064] It should be noted that the communication management application installed in the mobile phone 110 and the functions of the communication management application are only examples. The mobile phone can also be installed with a system application that can log in to the user account, and the system application can also support the same functions as the communication management application. In addition, the communication management application can include more functions than the above examples, which can be seen in Figure 4 The present application does not limit the related introduction of the illustrated embodiments.

[0065] The implementation of the mode switching phase of the Bluetooth device can be seen below Figure 4 A detailed description of the illustrated embodiment will not be expanded here.

[0066] After that, you can enter the Bluetooth connection stage of the Bluetooth device in strong binding mode.

[0067] Combination Figure 2 As shown, when the mobile phone 130 requests to establish a Bluetooth connection with the Bluetooth headset 120, the Bluetooth headset 120 in strong binding mode can verify the identity of the mobile phone 130. If the identity authentication of the mobile phone 130 is passed, the mobile phone 130 and the Bluetooth headset 120 can establish a Bluetooth connection. If the identity authentication of the mobile phone is not passed, the mobile phone 130 cannot establish a Bluetooth connection with the Bluetooth headset 120.

[0068] In some embodiments, after the mobile phone 130 scans the ADV_IND sent by the Bluetooth headset, the mobile phone 130 can send a CONNECT_REQ to the Bluetooth headset 120. The Bluetooth headset 120 determines that the CONNECT_REQ includes the account identification information of the user account of the mobile phone 110 stored in the trust list of the Bluetooth headset 120 (taking the storage area of ​​the first device as an example that can be the trust list of the Bluetooth headset 120) (that is, the identification information of the trusted device includes the account identification information of the user account logged in by the mobile phone 110), or the Bluetooth headset 120 determines that the CONNECT_REQ includes the device identification information of the electronic device stored in the trust list (that is, the identification information of the trusted device includes the device identification information of the electronic device), indicating that the Bluetooth headset 120 determines that the electronic device sending the CONNECT_REQ is a trusted device, the mobile phone 130 passes the identity authentication, and the Bluetooth headset 120 can establish a Bluetooth connection with the mobile phone 130.

[0069] In some embodiments, after the Bluetooth headset 120 receives the CONNECT_REQ sent by the mobile phone 130, the Bluetooth headset 120 determines that the CONNECT_REQ does not include the account identification information of the user account of the mobile phone 110 and the device identification information of the electronic device stored in the trust list, and the Bluetooth headset 120 can refuse to establish a Bluetooth connection with the mobile phone 130.

[0070] In some embodiments, after the Bluetooth headset 120 receives the CONNECT_REQ sent by the mobile phone 130, the Bluetooth headset 120 determines that the CONNECT_REQ does not include the account identification information of the user account of the mobile phone 110 and the device identification information of the electronic device stored in the trust list. However, when the mobile phone 110 and the Bluetooth headset 120 are still establishing a Bluetooth connection, the Bluetooth headset 120 can send a connection request prompt message (also referred to as prompt message) to the mobile phone 110. The connection request prompt message is used to prompt the user holding the mobile phone 110 that the mobile phone 130 wants to establish a Bluetooth connection with the Bluetooth headset 120.

[0071] Then, if the user agrees to the request connection prompt information, the Bluetooth headset 120 can establish a Bluetooth connection with the mobile phone 130. If the user refuses the request connection prompt information, the Bluetooth headset 120 can refuse to establish a Bluetooth connection with the mobile phone 130.

[0072] It should be noted that the process of verifying the identity of the mobile phone 130 by the Bluetooth device in the strong binding mode described above is only an example. The Bluetooth connection stage of the Bluetooth device in the strong binding mode may include more identity authentication methods, which can be seen below. Figure 5-Figure 9 A detailed description of the illustrated embodiment will not be expanded here.

[0073] It can be seen from this that the Bluetooth headset 120 that switches from normal mode to strong binding mode can no longer establish a Bluetooth connection with any electronic device indiscriminately, but will establish a Bluetooth connection with electronic devices that have passed identity authentication, thereby ensuring the security of the identity of the electronic device that establishes a Bluetooth connection with the Bluetooth headset 120, thereby improving the security of data communication between the Bluetooth headset 120 and the mobile phone 130.

[0074] Next, combine Figure 3 The Bluetooth connection stage of the Bluetooth device in the normal mode mentioned above is introduced in detail. In this embodiment, the electronic device is a mobile phone 110 and the Bluetooth device is a Bluetooth headset 120 as an example.

[0075] like Figure 3 As shown, the process of establishing a Bluetooth connection between the mobile phone 110 and the Bluetooth headset 120 in the normal mode may include the following steps:

[0076] S301: The Bluetooth headset 120 sends ADV_IND to the surroundings.

[0077] It can be said that the Bluetooth headset 120 broadcasts ADV_IND to the surroundings.

[0078] In some embodiments, ADV_IND may include device identification information of the Bluetooth headset 120 device.

[0079] Exemplarily, the device identification information of the Bluetooth headset 120 device may include the MAC address of the Bluetooth headset 120 , the device name of the Bluetooth headset 120 , or user-defined data, etc., which may uniquely identify the Bluetooth headset 120 .

[0080] The present application does not limit the information type and information quantity of the device identification information of the Bluetooth headset 120 device, and other electronic devices can uniquely identify the Bluetooth headset 120 based on the device identification information of the Bluetooth headset 120 device.

[0081] S302 : The mobile phone 110 scans the ADV_IND sent by the Bluetooth headset 120 , and sends a CONNECT_REQ to the Bluetooth headset 120 .

[0082] In some embodiments, the mobile phone 110 itself may use a standard Bluetooth protocol to send a CONNECT_REQ (also referred to as a first communication connection request message) to the Bluetooth headset 120 , and the CONNECT_REQ may include device identification information of the mobile phone 110 .

[0083] Exemplarily, the device identification information of the mobile phone 110 may include the MAC address of the mobile phone 110 , the device name of the mobile phone 110 , or user-defined data.

[0084] The present application does not limit the information type and information quantity of the device identification information of the mobile phone 110 , and other electronic devices or Bluetooth devices can uniquely identify the mobile phone 110 based on the device identification information of the mobile phone 110 .

[0085] In some embodiments, the mobile phone 110 itself can use a private Bluetooth protocol to send a CONNECT_REQ to the Bluetooth headset 120. The CONNECT_REQ may include the device identification information of the mobile phone 110. The device identification information of the mobile phone 110 may include the device identification information of the mobile phone 110 and the account identification information of the user account A logged in by the mobile phone 110.

[0086] Exemplarily, the account identification information of user account A may include identification information of user account A itself, such as the mobile phone number or email address associated with user account A when the user registered user account A, or the account name set by the user when registering the account, etc., which can be distinguished from information of other user accounts.

[0087] As another example, the account identification information of user account A may include the account identification information of the family account to which the user account A belongs, such as the account name of the family account, the identification code of the family account, and other information that can be distinguished from other family accounts.

[0088] Next, taking the mobile phone 110 installed with the communication management application as an example, the implementation method of the mobile phone 110 scanning the ADV_IND sent by the Bluetooth headset 120 and sending the CONNECT_REQ to the Bluetooth headset 120 is introduced.

[0089] In a possible implementation, after the communication management application of the mobile phone 110 logs in to the user account A, the communication management application can scan the ADV_IND sent by the Bluetooth headset 120 , and the communication management application can send a CONNECT_REQ to the Bluetooth headset 120 .

[0090] In some embodiments, the mobile phone 110 includes a communication management application and a communication module, and the communication module includes a Bluetooth chip. The user interface of the communication management application may include a device scanning control. After the user triggers the device scanning control, the communication management application may control the Bluetooth chip to scan ADV_IND sent by other surrounding electronic devices or Bluetooth devices. After the Bluetooth chip scans the ADV_IND of the Bluetooth headset 120, it reports it to the communication management application. Then, the user interface of the communication management application may display the device identification information of the Bluetooth headset 120 included in the ADV_IND, such as the device name of the Bluetooth headset 120. The user interface of the communication management application may also display a device connection control, and the user may trigger the device connection control. In response to the user's triggering operation, the communication management application may control the Bluetooth chip to send CONNECT_REQ to the Bluetooth headset 120 that sent ADV_IND.

[0091] It should be noted that the device scanning controls and device connection controls displayed in the user interface of the communication management application in the above example are only examples, and this application does not limit this. It can enable the mobile phone 110 to scan the surrounding electronic devices and Bluetooth devices after being triggered by the user's operation, and realize the function of the mobile phone 110 sending CONNECT_REQ to the Bluetooth headset 120.

[0092] S303: The Bluetooth headset 120 sends a connection confirmation message to the mobile phone 110 in response to CONNECT_REQ.

[0093] The Bluetooth headset 120 is in normal mode and can establish a Bluetooth connection with any electronic device without distinction.

[0094] In some embodiments, after the Bluetooth headset 120 receives CONNECT_REQ, the Bluetooth headset 120 can send a connection confirmation message to the mobile phone 110. The connection confirmation message is used to prompt the mobile phone 110 that the Bluetooth headset 120 agrees to the connection request CONNECT_REQ, indicating that a Bluetooth connection has been successfully established between the Bluetooth headset 120 and the mobile phone 110, and the two can communicate data.

[0095] Next, combine Figure 4 The mode switching phase of the aforementioned Bluetooth device is introduced in detail.

[0096] In this embodiment, the electronic device is a mobile phone 110, the Bluetooth device is a Bluetooth headset 120, the mobile phone 110 has adopted a private Bluetooth protocol to establish a Bluetooth connection with the Bluetooth headset 120 in normal mode, and the mobile phone 110 has a communication management application installed, and the communication management application has logged in to user account A.

[0097] It should be noted that the communication management application installed on the mobile phone 110 logged in with user account A is only an example. Other third-party applications of the mobile phone 110 may also log in to the user account A, or system applications such as the settings application of the mobile phone 110 may log in to the user account A. The functions of any other third-party application and any system application are the same as the functions of the communication management application described in the following embodiments.

[0098] like Figure 4 As shown, the mode switching phase of the Bluetooth device may include the following steps:

[0099] S401: The mobile phone 110 sends mode switching instruction information to the Bluetooth headset 120.

[0100] In some embodiments, the mode switching indication information (also referred to as first indication information) is used to instruct the Bluetooth headset 120 to switch from the normal mode to the strong binding mode.

[0101] It should be noted that the first indication information can also be used to instruct the Bluetooth headset 120 to switch from other modes to the strong binding mode, which is not limited in this application.

[0102] In the example where the mobile phone 110 includes a communication management application and a Bluetooth chip, the user interface of the communication management application of the mobile phone 110 can display a strong binding mode switching control. When a user triggers the strong binding mode switching control, the communication management application can control the Bluetooth chip to send mode switching indication information to the Bluetooth headset 120 in response to the user's triggering operation, so as to control the Bluetooth headset 120 to switch from normal mode to strong binding mode.

[0103] In addition, in some embodiments, the user interface of the communication management application of the mobile phone 110 can also display a normal mode switching control. When the user triggers the normal mode switching control, the communication management application can control the Bluetooth chip to send another mode switching indication information to the Bluetooth headset 120 in response to the user's triggering operation to control the Bluetooth headset 120 to switch from the strong binding mode to the normal mode.

[0104] It should be noted that another mode switching indication information can also be used to instruct the Bluetooth headset 120 to switch from other modes to the normal mode, and this application does not limit this.

[0105] It should be further explained that the normal mode switching control and the strong binding mode switching control displayed in the user interface of the communication management application are only examples. This application does not limit the content displayed in the user interface of the communication management application. It can trigger the control of the Bluetooth headset 120 to switch modes.

[0106] S402: The Bluetooth headset 120 switches from the normal mode to the strong binding mode in response to the mode switching instruction information.

[0107] After receiving the mode switching instruction information sent by the mobile phone 110, the Bluetooth headset 120 can switch its normal mode to the strong binding mode.

[0108] The Bluetooth headset 120 in normal mode can establish a Bluetooth connection with any electronic device indiscriminately. For example, when the Bluetooth headset 120 in normal mode receives a CONNECT_REQ sent by any electronic device, it can directly agree to the connection request CONNECT_REQ, and the Bluetooth headset 120 in normal mode will establish a Bluetooth connection with any electronic device.

[0109] After receiving the CONNECT_REQ sent by the electronic device, the Bluetooth headset 120 in the strong binding mode will authenticate the electronic device, and if the electronic device passes the authentication, the Bluetooth headset 120 will agree to the connection request of CONNECT_REQ.

[0110] S403: The mobile phone 110 sets the owner information.

[0111] In some embodiments, the user interface of the communication management application of the mobile phone 110 may also display an owner information setting control. After the user triggers the owner information setting control, the user may enter the owner information in the user interface, and the owner information may be used to contact the user holding the mobile phone 110. For example, the owner information may be the user's mobile phone number, email address, etc.

[0112] It should be noted that the user interface of the communication management application displays the owner information setting control only as an example. This application does not limit the content displayed in the user interface of the communication management application. It can be used for users to enter the owner information (also known as the contact information of the mobile phone 110. The device identifier of the trusted device may include the contact information of the mobile phone 110).

[0113] S404: The mobile phone 110 sends the owner information to the Bluetooth headset 120.

[0114] After the mobile phone 110 recognizes the owner information input by the user, it can send it to the Bluetooth headset 120.

[0115] In the example where the mobile phone 110 includes a communication management application and a Bluetooth chip, after the communication management application recognizes that the user inputs the owner information, the communication management application can control the Bluetooth chip to send the owner information to the Bluetooth headset 120 .

[0116] It should be noted that the present application does not limit the execution steps of S403-S404. The user may first trigger the operation to input the owner information, and may first execute S403, and then execute S404 and S302 at the same time. The mobile phone 110 sends a CONNECT_REQ to the Bluetooth headset 120. The CONNECT_REQ may include the owner information in addition to the device identification information of the mobile phone 110 and the account identification information of the user account A.

[0117] S405: The Bluetooth headset 120 stores the device identification information of the mobile phone 110, the account identification information of the user account A, and the owner information in the trust list.

[0118] In the embodiment of the present application, the trust list is used to store the identification information of the trusted devices of the Bluetooth headset 120. Exemplarily, the device identification information of the trusted device, the account identification information of the user account logged in by the trusted device, and the owner information of the trusted device can be stored.

[0119] The mobile phone 110 controls the Bluetooth headset 120 to switch from normal mode to strong binding mode, indicating that the mobile phone 110 is a trusted device of the Bluetooth headset 120. The Bluetooth headset 120 can add the device identification information of the mobile phone 110, the account identification information of user account A, and the owner information to the trust list.

[0120] In some embodiments, in the process of establishing a Bluetooth connection between the above-mentioned Bluetooth headset 120 and the mobile phone 110, the Bluetooth headset 120 can jointly generate a link key with the mobile phone 110, and the Bluetooth headset 120 can bind the link key with the device identification information of the mobile phone 110, the account identification information of the user account A, and the owner information and store them in a trusted list.

[0121] In addition, in some embodiments, when the Bluetooth headset 120 is in the strong binding mode, the mobile phone 110 can add the identification information of the electronic device to the trust list of the Bluetooth device 120. This indicates that the mobile phone 110 can add a trusted device for the Bluetooth headset 120.

[0122] Exemplarily, the user interface of the communication management application of the mobile phone 110 may also display a trusted device adding control. After the user operation triggers the trusted device adding control, the user may enter the identification information of the electronic device in the user interface, such as the device identification information of the electronic device, the account identification information of the user account logged in by the electronic device, etc. The identification information of the electronic device may indicate a trusted device of the Bluetooth headset 120, which may pass the identity authentication of the Bluetooth headset 120 in the strong binding mode.

[0123] It should be noted that the trusted device adding control displayed in the user interface of the communication management application is only an example. This application does not limit the content displayed in the user interface of the communication management application, and it can be used for users to enter the identification information of the electronic device.

[0124] In addition, in some embodiments, the Bluetooth headset 120 may further include a common list for storing identification information of electronic devices that establish a Bluetooth connection with the common mode Bluetooth headset 120. The identification information of the electronic devices stored in the trusted list may be synchronized to the common list.

[0125] As can be seen from the above, the mobile phone 110 can control the Bluetooth headset 120 to switch to the strong binding mode, adding a step for the Bluetooth headset 120 to authenticate the electronic device requesting a Bluetooth connection, which can avoid the problem of the Bluetooth headset 120 indiscriminately establishing a Bluetooth connection with any electronic device, and ensure the security of the identity of the electronic device that successfully establishes a Bluetooth connection with the Bluetooth headset 120.

[0126] Next, combine Figures 5 to 9 The Bluetooth connection phase of the Bluetooth device in the aforementioned strong binding mode is introduced in detail. Figures 5 to 9 These correspond to Embodiment 1 to Embodiment 5 respectively, and each embodiment takes the mobile phone 130 requesting to establish a Bluetooth connection with the Bluetooth headset 120 as an example.

[0127] It should be noted that in the embodiment of the present application, when the mobile phone 110 logs in to the user account, the user account logged in can be called the first user account (for example, user account A introduced later), and when the mobile phone 130 logs in to the user account, the user account logged in can be called the second user account (for example, user account A or user account B introduced later).

[0128] Embodiment 1:

[0129] In the first embodiment, the mobile phone 110 and the Bluetooth headset 120 still establish a Bluetooth connection, and the mobile phone 110 uses Figure 4 The steps shown have controlled the Bluetooth headset 120 to switch from the normal mode to the strong binding mode, and the mobile phone 130 itself uses the standard Bluetooth communication protocol to request to establish a Bluetooth connection with the Bluetooth headset 120.

[0130] like Figure 5 As shown, the Bluetooth connection phase of the Bluetooth device in the strong binding mode may include the following steps:

[0131] S501: The Bluetooth headset 120 sends ADV_IND to the surroundings.

[0132] In some embodiments, when the mobile phone 110 and the Bluetooth headset 120 are still connected to a Bluetooth connection, the Bluetooth headset 120 can stop sending ADV_IND to the surroundings. The user can operate to trigger the Bluetooth headset to enter the Bluetooth pairing state again, and can continue to send ADV_IND to the surroundings.

[0133] Exemplarily, the earphone compartment of the Bluetooth headset includes a button, and the user can long press the button to trigger the Bluetooth headset to send ADV_IND again to establish a Bluetooth connection with other electronic devices, indicating that the Bluetooth headset 120 can establish Bluetooth connections with two or more electronic devices at the same time.

[0134] It should be noted that the above-mentioned user operation triggering the Bluetooth headset to send ADV_IND again is only an example. The body of the Bluetooth headset may also include a button, and the user can double-click the button to trigger the Bluetooth headset to send ADV_IND again. This application does not limit the position of the button or the triggering method of the button.

[0135] It should be noted that other implementations of S501 can refer to the introduction of S301 and will not be described in detail here.

[0136] S502: The mobile phone 130 scans the ADV_IND sent by the Bluetooth headset 120, and sends a CONNECT_REQ to the Bluetooth headset 120 using the standard Bluetooth communication protocol.

[0137] The mobile phone 130 itself adopts the standard Bluetooth communication protocol, indicating that the system application of the mobile phone 130 has not logged into the user account, and the CONNECT_REQ (also referred to as the second communication connection request information) sent by the system application of the mobile phone 130 includes the device identification information of the mobile phone 130.

[0138] In some embodiments, the mobile phone 110 includes a system application and a communication module, and the communication module includes a Bluetooth chip.

[0139] The user interface of the system application may include a device scanning control. After the user triggers the device scanning control, the system application may control the Bluetooth chip to scan ADV_IND sent by other surrounding electronic devices or Bluetooth devices. After the Bluetooth chip scans the ADV_IND of the Bluetooth headset 120, it reports it to the system application. Then, the user interface of the system application may display the device identification information of the Bluetooth headset 120 device included in the ADV_IND, such as the device name of the Bluetooth headset 120. The user interface of the system application may also display a device connection control, which the user may trigger. In response to the user's triggering operation, the system application may control the Bluetooth chip to send CONNECT_REQ to the Bluetooth headset 120 that sent the ADV_IND.

[0140] It should be noted that the content displayed on the user interface of the system application in the above example is only an example, and this application does not limit this. It can enable the mobile phone 110 to scan the surrounding electronic devices and Bluetooth devices after being triggered by the user's operation, and realize the function of the mobile phone 110 sending CONNECT_REQ to the Bluetooth headset 120.

[0141] In addition, in some embodiments, the following step 1 may be used to replace S502:

[0142] Step 1: The mobile phone 130 scans the ADV_IND sent by the Bluetooth headset 120 and sends a CONNECT_REQ to the Bluetooth headset 120 using a private Bluetooth communication protocol.

[0143] In some embodiments, the mobile phone 130 has installed a communication management application, which has logged in a user account B, which is different from the user account A logged in by the communication management application of the mobile phone 110 .

[0144] The communication management application of the mobile phone 130 can use a private Bluetooth communication protocol to send a CONNECT_REQ to the Bluetooth headset 120, and the CONNECT_REQ includes the device identification information of the mobile phone 130 and the account identification information of the user account B. The implementation method can refer to the introduction of the embodiment of the mobile phone 110 including the communication management application and the communication module in S302, which will not be repeated here.

[0145] Based on the above, it can be seen that when the system application of mobile phone 130 uses the standard Bluetooth communication protocol to establish a Bluetooth connection with the Bluetooth headset 120, after the communication management application of mobile phone 130 logs in to user account B, the communication management application of mobile phone 130 can use a private Bluetooth communication protocol to request to establish a Bluetooth connection with the Bluetooth headset 120.

[0146] S503: The Bluetooth headset 120 responds to CONNECT_REQ and determines that the mobile phone 130 adopts the standard Bluetooth communication protocol.

[0147] In some embodiments, CONNECT_REQ may include a flag bit, where the flag bit is used to indicate the Bluetooth communication protocol adopted by the electronic device sending the CONNECT_REQ.

[0148] Exemplarily, the value of the flag bit of CONNECT_REQ is 1, indicating that the electronic device sends CONNECT_REQ using a private Bluetooth communication protocol. The CONNECT_REQ may include device identification information of the electronic device and account identification information of the logged-in user account.

[0149] The value of the flag bit of CONNECT_REQ is 0, indicating that the electronic device uses the standard Bluetooth communication protocol to send CONNECT_REQ, and the CONNECT_REQ may include device identification information of the electronic device.

[0150] The Bluetooth headset 120 determines that the flag bit of the received CONNECT_REQ indicates that the mobile phone 130 uses the standard Bluetooth communication protocol. The Bluetooth headset 120 can determine that the CONNECT_REQ does not include the account identification information of the user account logged in by the mobile phone 130.

[0151] In addition, when step 1 is used to replace S502, the following step 2 may also be used to replace S503:

[0152] Step 2: In response to CONNECT_REQ, the Bluetooth headset 120 determines that the mobile phone 130 uses a private Bluetooth communication protocol.

[0153] The Bluetooth headset 120 determines that the flag bit of the received CONNECT_REQ indicates that the mobile phone 130 uses a private Bluetooth communication protocol. The Bluetooth headset 120 can determine that the CONNECT_REQ includes the device identification information of the mobile phone 130 and the account identification information of the logged-in user account B.

[0154] S504: The Bluetooth headset 120 determines that the device identification information of the mobile phone 130 is not in the trusted list.

[0155] Based on the above introduction, the trust list can store the identification information of the trusted device of the Bluetooth headset 120. The Bluetooth headset 120 determines that the trust list does not store the device identification information of the mobile phone 130, indicating that the mobile phone 130 is not yet a trusted device of the Bluetooth headset 120.

[0156] In addition, when step 1 is used to replace S502 and step 2 is used to replace S503, the following step 3 may be used to replace S504:

[0157] Step 3: The Bluetooth headset 120 determines that the device identification information of the mobile phone 130 and the account identification information of the user account B are not in the trusted list.

[0158] The Bluetooth headset 120 determines that the flag bit of the received CONNECT_REQ indicates that the mobile phone 130 uses a private Bluetooth communication protocol. The Bluetooth headset 120 can determine that the CONNECT_REQ includes the device identification information of the mobile phone 130 and the account identification information of the logged-in user account B. The Bluetooth headset 120 can determine whether it is stored in the trust list.

[0159] The Bluetooth headset 120 can determine that the account identification information of user account B is different from the account identification information of user account A stored in itself, and the device identification information of the mobile phone 130 is not stored in the trust list, indicating that the mobile phone 130 is not yet a trusted device of the Bluetooth headset 120.

[0160] S505: The Bluetooth headset 120 sends a connection request prompt message of the mobile phone 130 to the mobile phone 110.

[0161] The mobile phone 110 and the Bluetooth headset 120 still maintain a Bluetooth connection. When the Bluetooth headset determines that the mobile phone 130 is not a trusted device, the Bluetooth headset 120 can send a connection request prompt message of the mobile phone 130 to the mobile phone 110 to further authenticate the identity of the mobile phone 130.

[0162] In some embodiments, the connection request prompt information is used to prompt the user holding the mobile phone 110 that the mobile phone 130 requests to establish a Bluetooth connection with the Bluetooth headset 120 .

[0163] Exemplarily, it may be a pop-up window of a communication management application of the mobile phone 110, which displays a prompt message requesting a connection. The present application does not limit the display method of the prompt message requesting a connection.

[0164] S506: In response to the user's consent operation to the connection prompt information request, the mobile phone 110 sends verification consent indication information to the Bluetooth headset 120.

[0165] In some embodiments, the consent operation for requesting the connection prompt information refers to the user's operation of consenting to the establishment of a Bluetooth connection between the Bluetooth headset 120 and the mobile phone 130 .

[0166] The verification consent indication information (also referred to as second indication information) is used to indicate that the Bluetooth headset 120 agrees to the CONNECT_REQ sent by the mobile phone 130 , indicating that the mobile phone 110 agrees to establish a Bluetooth connection between the Bluetooth headset 120 and the mobile phone 130 .

[0167] In the example of a communication management application pop-up window of the mobile phone 110, and the mobile phone 110 including a communication management application and a Bluetooth chip, the window may also include a consent control, which the user can operate to trigger the consent control, and then the communication management application can control the Bluetooth chip to send verification consent indication information to the Bluetooth headset 120.

[0168] It should be noted that the present application does not limit the content displayed on the user interface of the communication management application, and can be used for the user to trigger an operation to agree to establish a Bluetooth connection between the Bluetooth headset 120 and the mobile phone 130.

[0169] S507: The Bluetooth headset 120 adds the identification information of the mobile phone 130 to the trust list in response to the verification consent indication information.

[0170] When S502 - S504 are executed, the identification information of the mobile phone 130 includes its device identification information.

[0171] When executing steps 1 to 3, the identification information of the mobile phone 130 includes its device identification information and the account identification information of the user account B logged in.

[0172] S508: The Bluetooth headset 120 sends a connection confirmation message to the mobile phone 130 in response to the verification approval indication message.

[0173] In some embodiments, the Bluetooth headset 120 receives the verification consent indication information, and the Bluetooth headset 120 can send a connection confirmation message to the mobile phone 130. The connection confirmation message is used to prompt the mobile phone 130 that the Bluetooth headset 120 agrees to the CONNECT_REQ connection request, indicating that a Bluetooth connection has been successfully established between the Bluetooth headset 120 and the mobile phone 130, and the two can communicate data.

[0174] It should be noted that the present application does not limit the execution order of S507 and S508, and S508 may be executed first and then S507.

[0175] S509: In response to the user's consent operation to the request for connection prompt information, the mobile phone 110 uploads the device identification information of the mobile phone 130 to the cloud server.

[0176] In some embodiments, the connection request prompt information sent by the Bluetooth headset 120 to the mobile phone 110 may include the device identification information of the mobile phone 130. After the user agrees to the connection request prompt information, the communication management application of the mobile phone 110 can upload the device identification information of the mobile phone 130 to the cloud server, that is, upload it to the cloud account of the user account A of the communication management application.

[0177] In this way, a user of an electronic device logged in with user account A can be prompted that the mobile phone 130 is a trusted device of the Bluetooth headset 120 , and the mobile phone 130 can establish a Bluetooth connection with the Bluetooth headset 120 .

[0178] It should be noted that S509 is an optional execution step. The present application does not limit the execution order of S506 and S509, and the two can be executed simultaneously or successively.

[0179] In addition, in some embodiments, there may be a case where the user performs a rejection operation on the connection request prompt information, and the following step 4 may be used to replace S506, and the following step 5 may be used to replace S508. This indicates that in this embodiment 1, after executing S501-S505, steps 4 and 5 may continue to be executed, and S507 and S509 are no longer executed.

[0180] Step 4: In response to the user's rejection operation of the connection request prompt information, the mobile phone 110 sends a verification rejection indication message to the Bluetooth headset 120 .

[0181] In some embodiments, the rejection operation of requesting the connection prompt information refers to a user operation rejecting the establishment of a Bluetooth connection between the Bluetooth headset 120 and the mobile phone 130 .

[0182] The verification rejection indication information (also referred to as the third indication information) is used to instruct the Bluetooth headset 120 to reject the CONNECT_REQ sent by the mobile phone 130 , indicating that the mobile phone 110 rejects the Bluetooth headset 120 to establish a Bluetooth connection with the mobile phone 130 .

[0183] In the example of a communication management application pop-up window of the mobile phone 110, and the mobile phone 110 including a communication management application and a Bluetooth chip, the window may also include a rejection control, which the user can operate to trigger, and then the communication management application can control the Bluetooth chip to send a verification rejection indication message to the Bluetooth headset 120.

[0184] It should be noted that the present application does not limit the content displayed on the user interface of the communication management application, and can be used for the user to trigger an operation to refuse the Bluetooth headset 120 from establishing a Bluetooth connection with the mobile phone 130.

[0185] Step 5: The Bluetooth headset 120 sends a connection error message to the mobile phone 130 in response to the verification rejection indication message.

[0186] In some embodiments, when the Bluetooth headset 120 receives the verification rejection indication information, the Bluetooth headset 120 may send a connection error message to the mobile phone 130 (the connection error information is information used to indicate that the Bluetooth headset 120 refuses to establish a Bluetooth connection with the mobile phone 130). The connection error message is used to prompt the mobile phone 130 that the Bluetooth headset 120 rejects the CONNECT_REQ connection request, indicating that the Bluetooth connection between the Bluetooth headset 120 and the mobile phone 130 failed to be established.

[0187] As can be seen from the above, after the Bluetooth headset 120 switches to the strong binding mode, during the process of the Bluetooth headset 120 verifying the identity of the electronic device (the mobile phone 130 mentioned above) requesting a Bluetooth connection, another electronic device (the mobile phone 110 mentioned above) can be used to assist in the verification, thereby ensuring the security of the identity of the electronic device that successfully establishes a Bluetooth connection with the Bluetooth headset 120.

[0188] Embodiment 2:

[0189] In the second embodiment, the mobile phone 110 disconnects the Bluetooth connection with the Bluetooth headset 120, and the mobile phone 110 uses Figure 4The steps shown have controlled the Bluetooth headset 120 to switch from normal mode to strong binding mode. The system application of the mobile phone 130 has not logged in to the user account, nor has the communication management application been installed. The mobile phone 130 itself uses the standard Bluetooth communication protocol to request to establish a Bluetooth connection with the Bluetooth headset 120.

[0190] like Figure 6 As shown, the Bluetooth connection phase of the Bluetooth device in the strong binding mode may include the following steps:

[0191] S601: The Bluetooth headset 120 sends ADV_IND to the surroundings.

[0192] It should be noted that the implementation method of S601 can refer to the introduction of S301, which will not be repeated here.

[0193] S602: The mobile phone 130 scans the ADV_IND sent by the Bluetooth headset 120, and sends a CONNECT_REQ to the Bluetooth headset 120 using the standard Bluetooth communication protocol.

[0194] S603: The Bluetooth headset 120 responds to CONNECT_REQ and determines that the mobile phone 130 adopts the standard Bluetooth communication protocol.

[0195] S604: The Bluetooth headset 120 determines that the device identification information of the mobile phone 130 is not in the trusted list.

[0196] It should be noted that the implementation method of S602-S604 can refer to the introduction of S502-S504, which will not be repeated here.

[0197] S605: The Bluetooth headset 120 sends a connection error message to the mobile phone 130.

[0198] In some embodiments, when the Bluetooth headset 120 determines that the mobile phone 130 adopts the standard Bluetooth communication protocol and the device identification information of the mobile phone 130 is not in the trusted list, it indicates that the mobile phone 130 is not a trusted device of the Bluetooth headset 120, and because the Bluetooth headset 120 does not maintain a Bluetooth connection with the mobile phone 110, the Bluetooth headset 120 cannot communicate data with the mobile phone 110, and the Bluetooth headset 120 cannot further authenticate the mobile phone 130. It can be determined that it has failed the authentication, and the Bluetooth headset 120 can reject the CONNECT_REQ connection request sent by the mobile phone 130.

[0199] It should be noted that other implementations of S605 can refer to the introduction of step 5 in the first embodiment, which will not be described in detail.

[0200] As can be seen from the above, after the Bluetooth headset 120 switches to the strong binding mode, electronic devices that have not passed the identity authentication cannot establish a Bluetooth connection with the Bluetooth headset 120, which can avoid the communication security issues between the two caused by the insecure identity of the electronic device.

[0201] Embodiment three:

[0202] In the third embodiment, the mobile phone 110 disconnects the Bluetooth connection with the Bluetooth headset 120, and the mobile phone 110 uses Figure 4 The steps shown have controlled the Bluetooth headset 120 to switch from the normal mode to the strong binding mode. The mobile phone 130 installs a communication management application, and the user account B logged in by the communication management application is different from the user account A logged in by the mobile phone 110.

[0203] like Figure 7 As shown, the Bluetooth connection phase of the Bluetooth device in the strong binding mode may include the following steps:

[0204] S701: The Bluetooth headset 120 sends ADV_IND to the surroundings.

[0205] It should be noted that the implementation method of S701 can refer to the introduction of S301, which will not be repeated here.

[0206] S702: The mobile phone 130 scans the ADV_IND sent by the Bluetooth headset 120, and sends a CONNECT_REQ to the Bluetooth headset 120 using a private Bluetooth communication protocol.

[0207] In some embodiments, the mobile phone 130 itself adopts a private Bluetooth communication protocol, the system application of the mobile phone 130 logs in to the user account B, and the installed communication management application also logs in to the user account B. The system application or the communication management application can use the private Bluetooth communication protocol to request to establish a Bluetooth connection with the Bluetooth headset 120, and CONNECT_REQ includes the device identification information of the mobile phone 130 and the account identification information of the user account B.

[0208] In some embodiments, the mobile phone 130 itself adopts the standard Bluetooth communication protocol, and the communication management application installed in the mobile phone 130 logs in to the user account B. The communication management application can use a private Bluetooth communication protocol to establish a Bluetooth connection with the Bluetooth headset 120, and CONNECT_REQ includes the device identification information of the mobile phone 130 and the account identification information of the user account B.

[0209] It should be noted that for other implementations of S702, reference may be made to the introduction of step 1 in the first embodiment.

[0210] S703: The Bluetooth headset 120 responds to CONNECT_REQ and determines that the mobile phone 130 uses a private Bluetooth communication protocol.

[0211] S704: The Bluetooth headset 120 determines that the device identification information of the mobile phone 130 and the account identification information of the user account B are not in the trusted list.

[0212] It should be noted that the implementation of S703-S704 can refer to the introduction of step 2 and step 3 in embodiment 1, and will not be repeated here.

[0213] S705: The Bluetooth headset 120 sends a connection error message including the owner information to the mobile phone 130.

[0214] In some embodiments, the connection error information may include machine owner information.

[0215] It should be noted that for other implementations of S705, reference may be made to the introduction of step 5 in the first embodiment.

[0216] S706: The mobile phone 130 displays the owner information.

[0217] In some embodiments, it may be a pop-up window of the user interface of the communication management application of the mobile phone 130, which displays the owner information so that the user holding the mobile phone 130 can contact the user holding the mobile phone 110 through the owner information. This application does not limit the display method of the owner information.

[0218] As can be seen from the above, in the event that the Bluetooth headset 120 is lost or picked up, the possibility of the Bluetooth headset 120 being found can be increased by sending the owner information of the Bluetooth headset 120 to the electronic device that cannot establish a Bluetooth connection.

[0219] Embodiment 4:

[0220] In this fourth embodiment, the mobile phone 110 can disconnect the Bluetooth connection with the Bluetooth headset 120, or the mobile phone 110 can still maintain the Bluetooth connection with the Bluetooth headset 120, which is not limited in this application.

[0221] In the fourth embodiment, the mobile phone 110 adopts Figure 4 The steps shown have controlled the Bluetooth headset 120 to switch from the normal mode to the strong binding mode. The mobile phone 130 itself uses the standard Bluetooth communication protocol to request to establish a Bluetooth connection with the Bluetooth headset 120. The mobile phone 130 installs a communication management application, and the communication management application logs in to the user account A, which is the same as the user account A logged in by the communication management application of the mobile phone 110.

[0222] like Figure 8 As shown, the Bluetooth connection phase of the Bluetooth device in the strong binding mode may include the following steps:

[0223] S801: The Bluetooth headset 120 sends ADV_IND to the surroundings.

[0224] It should be noted that the implementation of S801 can refer to the introduction of S501, which will not be repeated here.

[0225] S802: The mobile phone 130 scans the ADV_IND sent by the Bluetooth headset 120, and sends a CONNECT_REQ to the Bluetooth headset 120 using a private Bluetooth communication protocol.

[0226] In some embodiments, CONNECT_REQ includes device identification information of the mobile phone 130 and account information of the user account A logged in by the communication management application of the mobile phone 130 .

[0227] S803: The Bluetooth headset 120 responds to CONNECT_REQ and determines that the mobile phone 130 uses a private Bluetooth communication protocol.

[0228] It should be noted that the implementation of S802-S803 can refer to the introduction of step 1-step 2 in embodiment 1, and will not be repeated here.

[0229] S804: The Bluetooth headset 120 determines that the account identification information of the user account A included in the CONNECT_REQ is the same as the account identification information of the user account A stored in the trust list of the Bluetooth headset 120.

[0230] S805: The Bluetooth headset 120 adds the device identification information of the mobile phone 130 to the trust list.

[0231] Exemplarily, the Bluetooth headset may bind and store the account identification information of the user account A, the device identification information of the mobile phone 110 , and the device identification information of the mobile phone 130 into a trust list.

[0232] S806: The Bluetooth headset 120 sends a connection confirmation message to the mobile phone 130.

[0233] It should be noted that the implementation method of S806 can refer to the introduction of S508, which will not be repeated here.

[0234] S807: In response to the connection confirmation information, the mobile phone 130 uploads the device identification information of the mobile phone 130 to the cloud server.

[0235] In some embodiments, after the mobile phone 130 successfully establishes a Bluetooth connection with the Bluetooth headset 120, the communication management application of the mobile phone 130 can upload the device identification information of the mobile phone 130 to the cloud server, that is, to the cloud account of the user account A of the communication management application. The user of the electronic device logged in with the user account A can be prompted that the mobile phone 130 is a trusted device of the Bluetooth headset 120 and the mobile phone 130 can establish a Bluetooth connection with the Bluetooth headset 120.

[0236] It should be noted that S807 is an optional execution step.

[0237] As can be seen from the above, after the Bluetooth headset 120 switches to the strong binding mode, the identity of the electronic device (i.e., the mobile phone 130 described above) can be verified through the logged-in user account. Electronic devices logged in to the same user account can pass the identity authentication of the Bluetooth headset 120, thereby ensuring the security of the identity of the electronic device that successfully establishes a Bluetooth connection with the Bluetooth headset 120.

[0238] It should be understood that when the Bluetooth of an electronic device is in an activated state, it can send ADV_IND to the surroundings, and can also scan ADV_IND sent by other surrounding electronic devices or Bluetooth devices. The same applies to Bluetooth devices.

[0239] The above embodiments 1 to 4 introduce the process of the mobile phone 130 requesting to establish a Bluetooth connection with the Bluetooth headset 120 , and the following embodiment 5 introduces the process of the Bluetooth headset 120 requesting to establish a Bluetooth connection with the mobile phone 130 .

[0240] Embodiment five:

[0241] In the fifth embodiment, the mobile phone 110 may disconnect the Bluetooth connection with the Bluetooth headset 120, or the mobile phone 110 may still maintain the Bluetooth connection with the Bluetooth headset 120, which is not limited in the present application.

[0242] In the fifth embodiment, the mobile phone 110 adopts Figure 4 The steps shown have switched the Bluetooth headset 120 from normal mode to strong binding mode. The mobile phone 130 itself uses a private Bluetooth communication protocol, and the mobile phone 130 installs a communication management application, and the communication management application logs in to user account A, which is the same as the user account A logged in by the communication management application of the mobile phone 110.

[0243] like Fig. 9 As shown, the Bluetooth connection phase of the Bluetooth device in the strong binding mode may include the following steps:

[0244] S901: The mobile phone 130 sends ADV_IND to the surroundings.

[0245] It can also be said that the mobile phone 130 broadcasts ADV_IND to the surroundings.

[0246] In some embodiments, the mobile phone 130 includes a system application and a Bluetooth chip. The system application of the mobile phone 130 also logs in to the user account A. When the Bluetooth function of the system application is activated, the system application of the mobile phone 130 can control the Bluetooth chip to send ADV_IND to the surrounding area. The ADV_IND includes the device identification information of the mobile phone 130 and the account identification information of the user account A.

[0247] In some embodiments, the mobile phone 130 also includes a communication management application and a Bluetooth chip. The communication management application of the mobile phone 130 also logs in to the user account A. When the Bluetooth function of the communication management application is activated, the communication management application of the mobile phone 130 can control the Bluetooth chip to send ADV_IND to the surrounding area. The ADV_IND includes the device identification information of the mobile phone 130 and the account identification information of the user account A.

[0248] Exemplarily, the device identification information of the mobile phone 130 may include the MAC address of the mobile phone 130, the device name of the mobile phone 130, or user-defined data. The present application does not limit the information type and amount of the device identification information of the mobile phone 130, and other electronic devices can uniquely identify the mobile phone 130 based on the device identification information of the mobile phone 130.

[0249] S902: The Bluetooth headset 120 scans the ADV_IND sent by the mobile phone 130 and determines that the mobile phone 130 adopts a private Bluetooth communication protocol.

[0250] In some embodiments, ADV_IND may include a flag bit, where the flag bit is used to indicate the Bluetooth communication protocol adopted by the electronic device sending ADV_IND.

[0251] It should be noted that, for the introduction of the flag bit of ADV_IND, reference may be made to the description of the flag bit of CONNECT_REQ in S503, which will not be repeated here.

[0252] The Bluetooth headset 120 determines that the flag bit of the received ADV_IND indicates that the mobile phone 130 uses a private Bluetooth communication protocol. The Bluetooth headset 120 can determine that the ADV_IND includes the account identification information of the user account A logged in by the mobile phone 130, and the Bluetooth headset 120 can continue to execute S903.

[0253] S903: The Bluetooth headset 120 determines that the account identification information of the user account A included in ADV_IND is the same as the account identification information of the user account A stored in the trust list of the Bluetooth headset 120.

[0254] S904: The Bluetooth headset 120 sends a CONNECT_REQ to the mobile phone 130.

[0255] In some embodiments, the Bluetooth headset 120 determines that the mobile phone 130 has logged into the same user account A as the trusted device mobile phone 110 , and the Bluetooth headset 120 can automatically send a CONNECT_REQ (also referred to as a third communication connection request message) to the mobile phone 130 .

[0256] In some embodiments, the CONNECT_REQ may include the account identification information of the user account A logged in by the mobile phone 110 and the device identification information of the Bluetooth headset 120 stored in the Bluetooth headset 120 .

[0257] S905: The mobile phone 130 sends a connection confirmation message to the Bluetooth headset 120 in response to CONNECT_REQ.

[0258] In some embodiments, the mobile phone 130 determines that the account identification information of the user account A included in CONNECT_REQ is the same as the account identification information of the user account A logged in by the mobile phone 130 itself. The mobile phone 130 can automatically send a connection confirmation message to the Bluetooth headset 120 based on the device identification information of the Bluetooth headset 120. The connection confirmation information is information used to indicate that the mobile phone 130 agrees to establish a Bluetooth connection with the Bluetooth headset 120.

[0259] This connection confirmation message is used for the Bluetooth headset 120. The mobile phone 130 agrees to the CONNECT_REQ connection request, indicating that the Bluetooth headset 120 and the mobile phone 130 have successfully established a Bluetooth connection and can communicate data between them.

[0260] S906: The mobile phone 130 uploads the device identification information of the mobile phone 130 to the cloud server.

[0261] It should be noted that the implementation of S906 may refer to the introduction of S807, and S906 is an optional execution step.

[0262] As can be seen from the above, after the Bluetooth headset 120 switches to the strong binding mode, the Bluetooth headset 120 can automatically establish a Bluetooth connection with an electronic device that is logged in to the same user account. On the basis of ensuring the security of the identity of the electronic device that successfully establishes a Bluetooth connection with the Bluetooth headset 120, user operations are further reduced, which can improve the user experience.

[0263] The embodiment of the present application also provides a computer-readable storage medium storing a computer program, and when the computer program is executed by a computer, one or more steps in any of the above-mentioned Bluetooth connection methods can be implemented.

[0264] The computer-readable storage medium may be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium may be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.

[0265] Another embodiment of the present application further provides a computer program product including instructions. When the computer program product is executed by a computer, one or more steps in any of the above-mentioned Bluetooth connection methods can be implemented.

[0266] The electronic device, computer-readable storage medium, and computer program product provided in this embodiment are all used to execute the corresponding Bluetooth connection method provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding Bluetooth connection method provided above, and will not be repeated here.

[0267] The terms "first", "second", "third", etc. in the specification, claims and drawings of this application are used to distinguish different objects rather than to limit a specific order.

[0268] In the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a specific way.

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

Claims

1. A Bluetooth connection method, characterized in that: Applied to a first device, comprising: When the first device is in the first mode, receiving identification information of the second device sent by the second device; the first device in the first mode agrees to establish a Bluetooth connection with the trusted device indicated by the storage area of ​​the first device; It is determined that the identification information of the second device is the same as the identification information of the trusted device stored in the storage area, and a Bluetooth connection is established with the second device.

2. The method according to claim 1, characterized in that Before the receiving the identification information of the second device sent by the second device, the method further includes: receiving first indication information sent by a third device, wherein the first indication information is used to instruct the first device to switch to the first mode; In response to receiving the first indication information, switching to the first mode; Receiving identification information of a trusted device sent by the third device; When the first device is in the first mode, the identification information of the trusted device is stored in the storage area.

3. The method according to claim 2, characterized in that The receiving the identification information of the trusted device sent by the third device includes: Receive account identification information of a first user account sent by the third device; the third device has logged in to the first user account.

4. The method according to claim 3, characterized in that The determining that the identification information of the second device is the same as the identification information of the trusted device stored in the storage area, and establishing a Bluetooth connection with the second device includes: Determine that the identification information of the second device is the same as the account identification information of the first user account stored in the storage area, and establish a Bluetooth connection with the second device; the identification information of the second device is the account identification information of the second user account logged in to the second device.

5. The method according to claim 2, characterized in that: The receiving the identification information of the trusted device sent by the third device includes: Receive the device identification information of the second device sent by the third device; the device identification information of the second device is sent by the third device to the first device after the third device responds to the operation of inputting the device identification information of the second device.

6. The method according to claim 1, characterized in that Also includes: determining that the identification information of the second device is different from the identification information of the trusted device stored in the storage area, and sending a prompt message to the third device; The prompt information is used to prompt the second device to request to establish a Bluetooth connection with the first device; Determine that second indication information sent by the third device is received, and establish a Bluetooth connection with the second device; the second indication information is used to indicate consent to establish a Bluetooth connection between the first device and the second device.

7. The method according to claim 6, characterized in that Also includes: Determine that second indication information sent by the third device is received, and store identification information of the second device in a storage area of ​​the first device.

8. The method according to claim 6, characterized in that Also includes: Determine that third indication information sent by the third device is received, and send, to the second device, information for instructing the first device to refuse to establish a Bluetooth connection with the second device; The third indication information is used to indicate that the establishment of a Bluetooth connection between the first device and the second device is rejected.

9. The method according to claim 1, characterized in that: Also includes: Determine that the identification information of the second device is different from the identification information of the trusted device stored in the storage area, send to the second device information for instructing the first device to refuse to establish a Bluetooth connection with the second device, and send the contact information of the trusted device to the second device; the contact information of the trusted device is stored in the storage area of ​​the first device.

10. The method according to any one of claims 1 to 8, characterized in that: Also includes: When the first device is in the second mode, receiving first communication connection request information sent by a third device; The first device in the second mode agrees to establish a Bluetooth connection with the electronic device that sends the communication connection request information to the first device; In response to receiving the first communication connection request information sent by the first device, establishing a Bluetooth connection with the third device.

11. The method according to claim 10, characterized in that The first communication connection request information includes identification information of the third device, and further includes: When the first device is in the first mode, the identification information of the third device is stored in the storage area; and the first device switches to the first mode in response to receiving the first indication information sent by the third device.

12. The method according to any one of claims 1 to 11, characterized in that: The receiving identification information of the second device sent by the second device includes: Second communication connection request information sent by the second device is received; the second communication connection request information includes identification information of the second device.

13. The method according to claim 1, characterized in that The receiving identification information of the second device sent by the second device includes: receiving identification information of the second device broadcast by the second device; the identification information of the second device including account identification information of a second user account logged in by the second device; The determining that the identification information of the second device is the same as the identification information of the trusted device stored in the storage area, and establishing a Bluetooth connection with the second device includes: Determining that the account identification information of the second user account is the same as the identification information of the trusted device stored in the storage area, and sending third communication connection request information to the second device; Receive information sent by the second device to indicate that the second device agrees to establish a Bluetooth connection with the first device.

14. An electronic device, characterized in that: The electronic device is a first device, comprising a memory and a processor; The memory is coupled to the processor, and the memory is used to store computer program code, wherein the computer program code includes computer instructions, and one or more of the processors call the computer instructions to enable the electronic device to execute the Bluetooth connection method as described in any one of claims 1-13.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by the processor, the Bluetooth connection method according to any one of claims 1 to 13 is implemented.

16. A computer program product, characterized in that The invention comprises computer program codes, which, when executed by an electronic device, implement the steps of the Bluetooth connection method according to any one of claims 1 to 13.

Images