Equipment connection method and device, equipment and storage medium

Abstract

The invention relates to an equipment connection method and device, equipment and a storage medium. The device connection method comprises: receiving a connection request sent by a terminal device, the connection request comprising device information of the terminal device; in response to the connection request, judging whether equipment information is stored in a near field communication chip configured by the wearable equipment or not; under the condition that the device information is not stored in the near field communication chip, first connection information is obtained, and the first connection information reflects whether the wearable device can be connected with a new device or not; and under the condition that the first connection information is that the new equipment cannot be connected, sending a first connection result of equipment connection failure to the terminal equipment. According to the method provided by the invention, in the process of establishing the communication connection of the equipment, the safety of the equipment and the user experience are improved through storage of the equipment information and setting of the connection state.

Description

Technical Field

[0001] The present invention relates to the field of communication technologies, and in particular, to a device connection method, apparatus, device, and storage medium. Background Art

[0002] With the increasing richness of the functions of TWS (True Wireless Stereo) Bluetooth headsets, their prices have gradually risen. However, these wearable devices are extremely easy to lose due to user negligence during daily use. Due to the small size of TWS Bluetooth headsets, they are likely to fall or be forgotten when the user takes them off after carrying or using them, resulting in the loss of the device. More seriously, once the device is picked up by others, it can be directly used without the authorization of the original owner, increasing the risk of property loss for the user. Currently, there is a lack of effective anti-loss and anti-theft mechanisms in the market, and the property safety and privacy of users are not fully protected. Therefore, there is an urgent need for a security mechanism that can prevent the device from being used without authorization to improve the security of the device and enhance the user experience. Summary of the Invention

[0003] To solve the above technical problems, embodiments of the present disclosure provide a device connection method, apparatus, device, and storage medium.

[0004] In a first aspect, embodiments of the present disclosure provide a device connection method applied to a wearable device. The method includes:

[0005] Receiving a connection request sent by a terminal device, where the connection request includes device information of the terminal device;

[0006] In response to the connection request, determining whether the device information is stored in a near-field communication chip configured in the wearable device;

[0007] In the case where the device information is not stored in the near-field communication chip, obtaining first connection information, where the first connection information reflects whether the wearable device can connect to a new device;

[0008] In the case where the first connection information indicates that the wearable device cannot connect to a new device, sending a first connection result of device connection failure to the terminal device.

[0009] In a second aspect, embodiments of the present disclosure provide a device connection method applied to a terminal device. The method includes:

[0010] Sending a connection request to the wearable device, where the connection request includes device information of the terminal device;

[0011] Receive a first connection result of device connection failure sent by a wearable device, where the first connection result is generated by the wearable device in response to a connection request when the device information is not stored in the near-field communication chip configured by the wearable device and the obtained first connection information indicates that the wearable device cannot connect to a new device, and the first connection information reflects whether the wearable device can connect to a new device.

[0012] Thirdly, an embodiment of the present disclosure provides a device connection apparatus applied to a wearable device, including:

[0013] A first receiving unit, configured to receive a connection request sent by a terminal device, where the connection request includes device information of the terminal device;

[0014] A judging unit, configured to judge whether device information is stored in the near-field communication chip configured by the wearable device in response to the connection request;

[0015] An obtaining unit, configured to obtain first connection information when the device information is not stored in the near-field communication chip, where the first connection information reflects whether the wearable device can connect to a new device;

[0016] A first sending unit, configured to send a first connection result of device connection failure to the terminal device when the first connection information indicates that the wearable device cannot connect to a new device.

[0017] Fourthly, an embodiment of the present disclosure provides a device connection apparatus applied to a terminal device, including:

[0018] A second sending unit, configured to send a connection request to the wearable device, where the connection request includes device information of the terminal device;

[0019] A second receiving unit, configured to receive a first connection result of device connection failure sent by the wearable device, where the first connection result is generated by the wearable device in response to the connection request when the device information is not stored in the near-field communication chip configured by the wearable device and the obtained first connection information indicates that the wearable device cannot connect to a new device, and the first connection information reflects whether the wearable device can connect to a new device.

[0020] Fifthly, an embodiment of the present disclosure provides an electronic device, including:

[0021] A memory;

[0022] A processor; and

[0023] A computer program;

[0024] where the computer program is stored in the memory and is configured to be executed by the processor to implement the method according to the first aspect as described above.

[0025] In a sixth aspect, an embodiment of the present disclosure provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method according to the first aspect described above are implemented.

[0026] The present disclosure provides a device connection method, including: receiving a connection request sent by a terminal device, where the connection request includes device information of the terminal device; in response to the connection request, determining whether the device information is stored in a near-field communication chip configured in the wearable device; in a case where the device information is not stored in the near-field communication chip, obtaining first connection information, where the first connection information reflects whether the wearable device can connect to a new device; and in a case where the first connection information indicates that the wearable device cannot connect to a new device, sending a first connection result of device connection failure to the terminal device. The method provided in this application improves the security of the device and the user experience by storing device information and setting connection status during the process of establishing a device communication connection. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present disclosure and used together with the specification to explain the principles of the present disclosure.

[0028] To more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings required for use in the description of the embodiments or the prior art. Obviously, for those of ordinary skill in the art, other drawings can also be obtained based on these drawings without creative efforts.

[0029] Figure 1 It is a schematic flowchart of a device connection method provided by an embodiment of the present disclosure;

[0030] Figure 2 It is a schematic structural diagram of a near-field communication chip provided by an embodiment of the present disclosure;

[0031] Figure 3 It is a schematic diagram of an application scenario provided by an embodiment of the present disclosure;

[0032] Figure 4 It is a schematic processing diagram of a wearable device provided by an embodiment of the present disclosure;

[0033] Figure 5 It is a schematic processing diagram of a privileged instruction provided by an embodiment of the present disclosure;

[0034] Figure 6 It is a schematic flowchart of another device connection method provided by an embodiment of the present disclosure;

[0035] Figure 7Schematic diagram of the processing of a terminal device provided by an embodiment of the present disclosure;

[0036] Figure 8 Schematic diagram of the structure of a device connection device provided by an embodiment of the present disclosure;

[0037] Figure 9 Schematic diagram of the structure of another device connection device provided by an embodiment of the present disclosure;

[0038] Figure 10 Schematic diagram of the structure of an electronic device provided by an embodiment of the present disclosure. Detailed implementation manners

[0039] In order to more clearly understand the above objects, features and advantages of the present disclosure, the solutions of the present disclosure will be further described below. It should be noted that, without conflict, the embodiments of the present disclosure and the features in the embodiments may be combined with each other.

[0040] Many specific details are set forth in the following description in order to fully understand the present disclosure, but the present disclosure may be implemented in other ways different from those described herein; obviously, the embodiments in the specification are only a part of the embodiments of the present disclosure, rather than all the embodiments.

[0041] In view of the above technical problems, an embodiment of the present disclosure provides a device connection method. The following one or more embodiments are used for detailed description.

[0042] The device connection method provided by the embodiment of the present disclosure is applicable to the device connection scenario. This method can be executed by a device connection device, which can be implemented in software and / or hardware, and can be integrated in an electronic device. Among them, the electronic device may include, but is not limited to, mobile terminals such as smart phones, laptop computers, digital broadcast receivers, personal digital assistants (PDAs), tablet personal computers (Tablet PCs), portable multimedia players (PMPs), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), wearable devices, etc., and fixed terminals such as digital TVs, desktop computers, smart home devices, etc.

[0043] Figure 1 Schematic flowchart of a device connection method provided by an embodiment of the present disclosure, applied to a wearable device, specifically including as Figure 1 shown in the steps:

[0044] Exemplarily, refer to Figure 2 , Figure 2A schematic structural diagram of a near - field communication chip provided by an embodiment of the present disclosure. The near - field communication chip (Near Field Communication, NFC) supports short - range wireless communication and mainly includes a contactless front - end (Contactless Front - end, CLF chip), an embedded secure element (embedded Secure Element, eSE chip), and a first - type communication interface. Among them, the CLF chip is mainly responsible for parsing and processing radio - frequency communication instructions and communicating with the eSE chip through the first - type communication interface. Specifically, the CLF chip is mainly responsible for processing the instruction parsing and data transmission of radio - frequency communication to ensure that the device can smoothly perform contactless communication. The CLF chip also interacts with the eSE chip through the first - type communication interface to achieve secure data processing and storage. The eSE chip is a security chip, usually used in application scenarios that require high - security guarantees such as mobile payment, authentication, and digital rights management. Integrating the eSE chip in TWS Bluetooth headsets or other smart devices can enhance the security performance of the device, such as protecting device information. The first - type communication interface includes an IIC (Inter - Integrated Circuit, integrated circuit bus) interface, a UART (Universal Asynchronous Receiver - Transmitter, universal asynchronous transceiver) and / or an SPI (Serial Peripheral Interface, serial peripheral interface) interface.

[0045] In the following embodiments, taking the wearable device as a TWS Bluetooth headset (hereinafter referred to as Bluetooth headset) as an example, the device connection method between the Bluetooth headset and the terminal device will be described in detail. Specifically:

[0046] S101. Receive a connection request sent by the terminal device.

[0047] Among them, the connection request includes the device information of the terminal device.

[0048] It can be understood that a connection request refers to a request sent by a device when it hopes to establish communication with another device. For example, when the terminal device wants to connect to the Bluetooth headset via Bluetooth, it will send a connection request to the Bluetooth headset. Among them, the connection request contains necessary information (such as device information) to allow the receiving device to confirm the identity and permissions of the sending device and decide whether to accept the connection. The device information is used to identify the sending device, that is, the above - mentioned terminal device, including but not limited to the device name, Media Access Control (MAC) address, device type, etc.

[0049] Exemplarily, see Figure 3 , Figure 3A schematic diagram of an application scenario provided by an embodiment of the present disclosure actually refers to a connection and interaction scenario between a terminal device and a Bluetooth headset. The terminal device includes, for example, Figure 2 the NFC shown as Figure 2 and the Bluetooth headset also includes the NFC shown as

[0050] The terminal device and the Bluetooth headset perform radio frequency communication through CLF. Among them, the terminal device generally refers to a device that can be paired and communicate with the Bluetooth headset, and may be a smart device with Bluetooth function such as a mobile phone, a tablet, or a computer. A Bluetooth headset is a headset that can perform wireless communication with other devices through Bluetooth technology and is widely used in scenarios such as voice calls and listening to music. A Bluetooth headset usually has the characteristics of low power consumption and supports wireless pairing and communication with smart devices such as mobile phones and computers. CLF is a modular communication unit used to adjust the frequency, clock signal, or data transmission in wireless communication. Radio Frequency Communication is a communication method that transmits data through radio frequency signals of electromagnetic waves. In Bluetooth technology, radio frequency communication is used for wireless data exchange between devices. The Bluetooth headset and the terminal device transmit and receive signals in the 2.4 GHz frequency band through radio frequency signals.

[0050] S102. In response to a connection request, determine whether device information is stored in the near-field communication chip configured in the wearable device.

[0051] It can be understood that, based on S101 above, the Bluetooth headset determines whether device information is stored in the eSE chip in the near-field communication chip in response to the connection request sent by the terminal device.

[0052] Optionally, after determining whether device information is stored in the near-field communication chip configured in the wearable device, the method further includes:

[0053] When the device information is stored in the near-field communication chip, establish a communication connection between the terminal device and the wearable device, and send a second connection result indicating successful device connection to the terminal device.

[0054] Understandably, if the eSE chip stores device information, it means that the terminal device already has the configuration information or authentication data required for connection. The stored device information may include configuration information, authorization authentication, connection history, etc. Then, when the device information is valid and stored completely, the Bluetooth headset will allow the terminal device to establish a communication connection. At this time, the communication protocol is successfully activated, and data begins to be transmitted or exchanged. Subsequently, after the connection is successfully established, the Bluetooth headset sends a connection success feedback message to the terminal device, that is, the second connection result. The second connection result confirms that the connection between the terminal device and the Bluetooth headset has been established and data transmission or interaction operations can continue. This way of pre-storing device information ensures the security of the connection process and reduces the risk of unauthorized device connection.

[0055] Optionally, before determining whether the near-field communication chip configured in the wearable device stores device information, the method further includes:

[0056] Determine whether the near-field communication chip stores information of a first device, where the first device refers to a privileged device that has operation permissions for the wearable device, and the operation permissions include factory reset, device information editing, and / or connection information setting; when the near-field communication chip stores information of the first device, determine whether the near-field communication chip stores device information; or, when the near-field communication chip does not store information of the first device, send an authentication request to the terminal device, and when the connection authentication is successful, record the device information determined to be the information of the first device into the near-field communication chip.

[0057] Understandably, after the Bluetooth headset receives a connection request sent by the terminal device and before determining whether the eSE chip stores device information, it can first determine whether the eSE chip stores the device information of the first device (denoted as the first information). The first device refers to a privileged device that has operation rights for the Bluetooth headset. The operation rights include, but are not limited to, restoring the factory settings, editing device information, and setting connection information. The operation rights generally authorize the administrator device or the trusted device. The purpose is to ensure that only privileged devices can perform advanced / sensitive operations on the Bluetooth headset. If the eSE chip stores the first information, then it is determined whether the eSE chip stores device information. If the eSE chip does not store the first information, an authentication request is sent to the terminal device. The authentication request is to confirm whether the terminal device is a privileged device, that is, whether it has operation permissions. Usually, the terminal device first matched by the Bluetooth headset is determined as the first device. The authentication request usually includes the verification of the device identity, which can be completed through passwords, fingerprints, or other identity verification mechanisms. Generally, there is one privileged device for the Bluetooth headset. In the case of multiple privileged devices, the priorities of multiple privileged devices can be set by itself, such as setting the master and slave privileged devices, etc. In the case of a successful authentication request, the terminal device is determined as the first device, and then the information (device information) of the terminal device is recorded in the eSE chip for direct device management in subsequent operations, such as restoring the factory settings, editing device information, etc. This process of device identity authentication and device information storage ensures that only authenticated privileged devices can perform sensitive operations on the Bluetooth headset, further ensuring the security and manageability of the device, and realizing efficient and secure information interaction between specific devices.

[0058] Optionally, in the case where the near-field communication chip stores the information of the first device, the method further includes:

[0059] Obtain second connection information, where the second connection information reflects whether the wearable device can connect to the second device. The second device is different from the first device. The second device refers to an ordinary device that has no operation permissions for the wearable device; in the case where the second connection information indicates that the second device can be connected, it is determined whether the near-field communication chip stores device information; or, in the case where the second connection information indicates that the second device cannot be connected and the terminal device is not the first device, a first connection result is sent to the terminal device.

[0060] Understandably, after the first information is stored in the eSE chip and the first device is not a terminal device, before determining whether the device information is stored in the eSE chip, the second connection information is obtained. The second connection information indicates whether the wearable device allows a connection to the second device, that is, whether the Bluetooth headset can be connected to the second device. The second device refers to an ordinary device without operation permissions. The first device is a privileged device, and the second device is an ordinary device. The first device and the second device are different. The second device can only perform basic connection operations and has no permission to perform sensitive configurations and / or modifications on the Bluetooth, etc. In addition, the second connection information indicating whether the second device can be connected is set by the first device. If the second connection information indicates that the second device can be connected, it is determined whether the device information is stored in the eSE chip, that is, it is checked whether the device information has been stored. If it has been stored, it means that the Bluetooth headset is ready to connect to the terminal device. In this case, the terminal device is the second device. If the second connection information indicates that the second device cannot be connected and the terminal device is not the first device, a first connection result will be sent to the terminal device, and the first connection result indicates the result of the device connection failure.

[0061] S103. When the near-field communication chip does not store the device information, obtain the first connection information.

[0062] Among them, the first connection information reflects whether the wearable device can connect to a new device.

[0063] Understandably, on the basis of the above S102, if the eSE chip does not store the device information, that is, the terminal device is a new device that has never been connected or a new device whose device information has been deleted before, the first connection information is obtained. Among them, the first connection information indicates whether the Bluetooth device can connect to the new device through authentication or other pairing methods, that is, the first connection information refers to confirming whether a new device can be connected. The first connection information is also set by the privileged device. Specifically, it can be a status or identifier built into the Bluetooth headset to inform that it can be currently connected by other new devices.

[0064] Optionally, after obtaining the first connection information, the method further includes:

[0065] When the first connection information is that the new device can be connected, communicate and pair with the terminal device through the near-field communication chip; when the pairing is successful, establish a communication connection between the terminal device and the wearable device, and send a second connection result of the successful device connection to the terminal device; record the device information in the near-field communication chip.

[0066] It is understandable that if the first connection information indicates that the Bluetooth headset can be connected, the NFC chip will start pairing with the terminal device (such as a smartphone). Usually, this step includes preliminary authentication or key exchange between devices. Specifically, through NFC technology, the terminal device and the Bluetooth headset exchange data via wireless signals within a short distance to ensure that both devices can recognize each other and establish a temporary secure connection. If the pairing is successful between the two parties, it means that the devices can recognize each other and are ready for higher-level communication. That is, after successful pairing, the system will establish a continuous communication connection and data transmission can proceed smoothly between the two. After successful pairing and establishing a communication connection, the Bluetooth headset sends a second connection result of successful device connection to the terminal device via the near-field communication chip to notify the terminal device that the communication has been successfully established and the connection process ends. After successful connection and completion of pairing, the device information also needs to be recorded in the eSE chip, including device ID, pairing authentication data, connection history, etc., so that the connection can be quickly restored or used for security authentication in the future. This way of the Bluetooth headset recording device information by itself allows the device to quickly complete the pairing process by reading the stored device information during the next connection, improving the connection speed and security, reducing the time for users to perform manual operations, and at the same time avoiding unauthorized access and enhancing security. In addition, the second connection result fed back to the terminal device can also include the authorization status, connection quality, etc.

[0067] S104. In the case where the first connection information is that a new device cannot be connected, send a first connection result of device connection failure to the terminal device.

[0068] It is understandable that based on the above S103, if the device information is not stored in the eSE chip and the Bluetooth headset is in a state where a new device cannot be connected, that is, the current Bluetooth headset cannot connect to a new device with un-stored information, then directly send a first connection result of device connection failure to the terminal device to ensure that the device can clarify its identity and ensure communication security during the connection process.

[0069] Exemplarily, Figure 4A processing schematic diagram of a wearable device provided by an embodiment of the present disclosure. After the Bluetooth headset is connected to the terminal device, it is determined whether there is privileged user information in the eSE chip white list. If there is no privileged user information in the eSE chip, authentication information for NFC authentication of privileged users is sent to the terminal device. After the CLF of the Bluetooth headset receives the device information, the terminal device is determined as a privileged user and recorded in the eSE chip, indicating successful pairing. If there is privileged user information in the eSE chip and the terminal device is not a privileged device, it is determined whether other non-privileged users can be connected. If other non-privileged users cannot be connected, a connection result of pairing failure is sent to the terminal device. If other non-privileged users can be connected, it is determined whether the device information of the terminal device is stored in the eSE chip. If the device information is stored in the eSE chip, a direct connection is made and a connection result of pairing success is returned to the terminal device. If the device information is not stored in the eSE chip, it is determined whether a new device can be connected. If a new device is allowed to be connected, pairing is performed through the CLF, the device information is recorded in the eSE chip, and a connection result of pairing success is returned to the terminal device. If a new device is not allowed to be connected, a connection result of pairing failure is sent to the terminal device. For the specific implementation results of the above steps, please refer to the above embodiments and will not be elaborated here.

[0070] Optionally, the method further includes:

[0071] Receiving an operation instruction sent by the terminal device; in response to the operation instruction, determining whether the terminal device is a first device having an operation privilege for the wearable device; in the case where the terminal device is not the first device, not processing the operation instruction and sending a first processing result of processing failure to the terminal device; or, in the case where the terminal device is the first device, processing the operation instruction and sending a second processing result of processing success to the terminal device.

[0072] It is understandable that the Bluetooth headset receives an operation instruction sent by a terminal device. The operation instruction may involve control, data synchronization, or execution of certain tasks (such as editing device information, restoring factory settings, etc.). In response to the operation instruction, it is checked whether the terminal device has the operation authority, that is, whether the terminal device is a first device. The first device refers to a device that has passed authentication and obtained authorization. Specifically, it can be determined by identifying the identity information of the terminal device (such as device ID, pairing status, etc.). If the terminal device is not an authorized first device, the Bluetooth headset will not execute the operation instruction and send a first processing result of processing failure to the terminal device, informing that the operation instruction has not been executed because the terminal device does not have the permission to operate. If the terminal device is a first device and passes the permission verification, the Bluetooth headset will start to process the operation instruction. After the processing is completed, the Bluetooth headset will send a second processing result of processing success to the terminal device, indicating that the operation instruction has been successfully executed. This verification process ensures that only authenticated privileged devices (first devices) can operate the Bluetooth headset, and other unauthorized devices will be refused to execute the operation instruction, which can improve security and prevent unauthorized devices from controlling the Bluetooth headset.

[0073] Optionally, the operation instruction includes an editing instruction. The editing instruction is used to edit the device information stored in the near-field communication chip. The processing of the operation instruction can be specifically implemented through the following steps:

[0074] In the case where the operation instruction is an editing instruction, if the editing instruction is to delete the information of the first device, all the device information stored in the near-field communication chip will be deleted.

[0075] It is understandable that the operation instruction includes an editing instruction, a restoring factory settings instruction, and a connection settings instruction. Among them, the privileged device can set the Bluetooth headset to restore the factory state, delete any connected device information recorded in the eSE chip, set the device information that can receive or cannot receive new devices (when the device information that cannot receive new devices is set, a new device connecting to this Bluetooth headset will fail to connect), and set whether to connect or not connect to ordinary devices. In addition, if the editing instruction is to delete the information of the first device, that is, the privileged device deletes its own device information, all the recorded device information in the eSE chip will be deleted (directly restoring the factory state).

[0076] Exemplarily, Figure 5 FIG. is a schematic diagram of processing a privileged instruction provided by an embodiment of the present disclosure. After the Bluetooth headset receives the privileged instruction, it determines whether the terminal device sending the operation instruction is a connected privileged device. If the terminal device is not a connected privileged device, the privileged instruction will not be processed and a result of processing failure will be returned. If the terminal device is a connected privileged device, the privileged instruction will be processed and a result of processing success will be returned.

[0077] A device connection method provided by an embodiment of the present disclosure is applicable to the interaction between a wearable device and a terminal device. The processing flow of the wearable device is as follows: First, it receives a connection request from the terminal device and determines whether to connect to the terminal device according to the received device information. The judgment criteria include whether the terminal device is a privileged device, whether the wearable device allows connecting to ordinary devices, and whether the wearable device allows connecting to new devices. This method of multiple judgments through NFC and eSE encryption chips realizes the connection control of the wearable device, can reject the connection and use of non-privileged devices (ordinary devices and new devices), improves device security, and also avoids the problem that the device can be used without authorization after being lost. Furthermore, it also realizes the function of protecting the data of the device. In addition, it can also receive an operation instruction from the terminal device and determine whether the terminal device has the operation authority to ensure that only authorized privileged devices can control the functions of the wearable device. If the terminal device fails to pass the permission verification, the device will reject the operation instruction and send a feedback of processing failure; on the contrary, if the terminal device is a privileged device, it will execute the operation instruction and feedback the result of successful processing. This process ensures the security of data and that the control right of the device is not tampered with by unauthorized devices, reduces user losses to a certain extent, and improves the user experience.

[0078] Based on the above embodiment, Figure 6 is a schematic flowchart of another device connection method provided by an embodiment of the present disclosure, which is applied to a terminal device and specifically includes the following steps as Figure 6 shown:

[0079] S601. Send a connection request to the wearable device.

[0080] Among them, the connection request includes the device information of the terminal device.

[0081] It can be understood that the terminal device sends a connection request to the Bluetooth headset, and the connection request contains the device information of the terminal device, such as device ID, model, operating system version, Bluetooth address, etc. The device information is used for the wearable device to identify and verify the terminal device. Usually, the terminal device will connect to one wearable device. In the case where multiple wearable devices want to connect to the terminal device, the terminal device can select one wearable device to connect by itself, and then send a connection request to the wearable device.

[0082] S602. Receive the first connection result of device connection failure sent by the wearable device. Among them, the first connection result is generated by the wearable device in response to the connection request when the device information is not stored in the near-field communication chip configured by the wearable device and the obtained first connection information is that the new device cannot be connected, and the first connection information reflects whether the wearable device can connect to a new device.

[0083] Understandably, based on the above S601, after the Bluetooth headset receives a connection request, it will make at least one judgment on whether to connect to the terminal device. For the specific judgment process, refer to the above embodiments and will not be elaborated here. At the same time, the Bluetooth headset will also send a connection result of connection success or failure to the terminal device. After receiving the connection result, the terminal device can clarify the connection status and perform subsequent operations.

[0084] Optionally, after sending a connection request to the wearable device, the method further includes:

[0085] Receiving a second connection result of successful device connection sent by the wearable device, where the second connection result is generated by the wearable device without the need to perform connection authentication with the terminal device through the near-field communication chip, or the second connection result is generated by the wearable device after successful connection authentication with the terminal device through the near-field communication chip.

[0086] Understandably, the terminal device receiving the second connection result of successful connection may be generated by the Bluetooth headset when the device information is stored, or when the device information is not stored, the Bluetooth headset performs connection authentication to the terminal device through the CLF chip. For the specific description of the Bluetooth headset, refer to the above embodiments and will not be elaborated here.

[0087] Optionally, the method further includes:

[0088] Sending an operation instruction to the wearable device, where the operation instruction is used to instruct the wearable device to perform factory reset, device information editing, and / or connection information setting; receiving a processing result sent by the wearable device, where the processing result is a processing failure result generated by the wearable device when the terminal device is not the first device with operation authority; or the processing result is a processing success result generated by the wearable device when the terminal device is the first device.

[0089] It is understandable that the terminal device sends an operation instruction to the Bluetooth headset. This operation instruction is used to control the Bluetooth headset to perform specific operations, such as restoring the factory settings, editing device information, and setting connection information, etc. Restoring the factory settings means restoring the device to the factory default settings and clearing all user data and custom settings. Editing device information means allowing modification of the device information of the wearable device (such as name, version, etc.). Setting connection information means modifying connection settings, such as allowing connection to ordinary devices, new devices, etc. After receiving the operation instruction, the Bluetooth headset first determines whether the terminal device sending the instruction is a privileged device (the first device) with operation permissions. If the terminal device is the first device with operation permissions, and the operation instruction is legal and executed successfully, the Bluetooth headset will return a result indicating successful processing. If the terminal device is not the first device, that is, it has no operation permissions, the Bluetooth headset will return a result indicating failed processing, indicating that the instruction cannot be executed. Subsequently, after the terminal device receives the processing result from the Bluetooth headset, it can perform subsequent operations according to the result. If the result is "success", it indicates that the operation has been successfully executed; if the result is "failure", the terminal device needs to prompt the user or take other countermeasures. This step of determining whether there are operation permissions improves the security of device operations and avoids unauthorized device abuse or tampering.

[0090] Exemplarily, Figure 7 FIG. is a processing schematic diagram of a terminal device provided by an embodiment of the present disclosure. The terminal device connects to the Bluetooth headset and sends a connection request including device information. In the case where the Bluetooth headset does not allow connection to ordinary devices or new devices, and the terminal device is not a privileged device, a connection result of connection failure is obtained. In the case where the Bluetooth headset allows connection to ordinary devices or new devices, it is determined whether CLF connection authentication is required. If CLF connection authentication is not required, a direct connection can be made, and a connection result of successful pairing of the Bluetooth headset is obtained. If CLF connection authentication is required, CLF connection authentication is performed and a connection result of successful CLF connection authentication is obtained. Subsequently, a privileged instruction is sent to the Bluetooth headset. The Bluetooth headset will determine whether the privileged instruction is sent by a privileged device. If it is sent by a privileged device, an instruction result of successful sending will be obtained. If it is not sent by a privileged device, an instruction result of failed sending will be obtained.

[0091] A device connection method provided by an embodiment of the present disclosure is applied to a terminal device. By using near-field communication technology to control the connection of the Bluetooth headset, non-Bluetooth headset users cannot connect and use it normally, realizing the function of protecting the data of the Bluetooth headset.

[0092] Figure 8 FIG. is a structural schematic diagram of a device connection device provided by an embodiment of the present disclosure. The device connection device provided by an embodiment of the present disclosure can execute the processing flow provided by the device connection method embodiment, such as Figure 8As shown, the device connection apparatus 800 includes:

[0093] A first receiving unit 801, configured to receive a connection request sent by a terminal device, where the connection request includes device information of the terminal device;

[0094] A determining unit 802, configured to, in response to the connection request, determine whether device information is stored in a near field communication chip configured in the wearable device;

[0095] An obtaining unit 803, configured to obtain first connection information in the case where the near field communication chip does not store device information, where the first connection information reflects whether the wearable device can connect to a new device;

[0096] A first sending unit 804, configured to send a first connection result of device connection failure to the terminal device in the case where the first connection information indicates that the new device cannot be connected.

[0097] Optionally, the device connection apparatus 800 is further configured to:

[0098] In the case where the near field communication chip stores device information, establish a communication connection between the terminal device and the wearable device, and send a second connection result of successful device connection to the terminal device.

[0099] Optionally, the device connection apparatus 800 is further configured to:

[0100] In the case where the first connection information indicates that the new device can be connected, perform communication pairing with the terminal device through the near field communication chip;

[0101] In the case of successful pairing, establish a communication connection between the terminal device and the wearable device, and send a second connection result of successful device connection to the terminal device;

[0102] Record the device information into the near field communication chip.

[0103] Optionally, the device connection apparatus 800 is further configured to:

[0104] Determine whether information of a first device is stored in the near field communication chip, where the first device refers to a privileged device having an operation privilege for the wearable device, and the operation privilege includes factory reset, device information editing, and / or connection information setting;

[0105] In the case where the near field communication chip stores information of the first device, determine whether device information is stored in the near field communication chip; or,

[0106] In the case where the near field communication chip does not store information of the first device, send an authentication request to the terminal device, and in the case of successful connection authentication, record the device information determined to be the information of the first device into the near field communication chip.

[0107] Optionally, the device connection device 800 is further configured to:

[0108] Obtain second connection information, where the second connection information reflects whether the wearable device can be connected to a second device, the second device is different from the first device, and the second device refers to a general device that has no operation permission for the wearable device;

[0109] In the case that the second connection information indicates that the second device can be connected, determine whether device information is stored in the near-field communication chip; or,

[0110] In the case that the second connection information indicates that the second device cannot be connected and the terminal device is not the first device, send a first connection result to the terminal device.

[0111] Optionally, the device connection device 800 is further configured to:

[0112] Receive an operation instruction sent by the terminal device;

[0113] In response to the operation instruction, determine whether the terminal device is the first device that has operation permission for the wearable device;

[0114] In the case that the terminal device is not the first device, do not process the operation instruction and send a first processing result of processing failure to the terminal device; or,

[0115] In the case that the terminal device is the first device, process the operation instruction and send a second processing result of processing success to the terminal device.

[0116] Optionally, the operation instruction includes an editing instruction, and the editing instruction is used to edit the device information stored in the near-field communication chip.

[0117] Optionally, the device connection device 800 is further configured to:

[0118] In the case that the operation instruction is an editing instruction, if the editing instruction is to delete the information of the first device, delete all the device information stored in the near-field communication chip.

[0119] Figure 8 The device connection device in the illustrated embodiment can be used to execute the technical solutions of the above method embodiments, and its implementation principle and technical effects are similar, which will not be elaborated here.

[0120] Figure 9 This is a schematic structural diagram of a device connection device provided by an embodiment of the present disclosure. The device connection device provided by the embodiment of the present disclosure can execute the processing flow provided by the device connection method embodiment. As Figure 9 shown, the device connection device 900 includes:

[0121] A second sending unit 901, configured to send a connection request to the wearable device, where the connection request includes device information of the terminal device;

[0122] A second receiving unit 902, configured to receive a first connection result of device connection failure sent by the wearable device, where the first connection result is generated by the wearable device in response to the connection request when the near-field communication chip configured by the wearable device does not store the device information and the obtained first connection information indicates that the new device cannot be connected, and the first connection information reflects whether the wearable device can connect to a new device.

[0123] Optionally, the device connection device 900 is further configured to:

[0124] Receive a second connection result of successful device connection sent by the wearable device, where the second connection result is generated by the wearable device without the need to perform connection authentication with the terminal device through the near-field communication chip, or the second connection result is generated by the wearable device when the connection authentication with the terminal device through the near-field communication chip is successful.

[0125] Optionally, the device connection device 900 is further configured to:

[0126] Send an operation instruction to the wearable device, where the operation instruction is used to instruct the wearable device to perform a factory reset, device information editing, and / or connection information setting;

[0127] Receive a processing result sent by the wearable device, where the processing result is a processing failure result generated by the wearable device when the terminal device is not the first device with operation authority; or the processing result is a processing success result generated by the wearable device when the terminal device is the first device.

[0128] Figure 9 The device connection device in the illustrated embodiment can be used to execute the technical solutions of the above method embodiments, and its implementation principle and technical effects are similar, which will not be elaborated here.

[0129] Figure 10 The following is a schematic structural diagram of an electronic device provided by an embodiment of the present disclosure. Specifically, refer to Figure 10 , which shows a schematic structural diagram of an electronic device 100 suitable for implementing the present disclosure. The electronic device 100 in the embodiment of the present disclosure may include, but is not limited to, mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Tablet Computers), PMPs (Portable Multimedia Players), vehicle terminals (such as vehicle navigation terminals), wearable electronic devices, etc., and fixed terminals such as digital TVs, desktop computers, smart home devices, etc. Figure 7The electronic device shown is merely an example and should not impose any limitations on the functions and scope of use of the embodiments of the present disclosure.

[0130] As Figure 7 shown, the electronic device 100 may include a processing device 101 (such as a central processing unit, a graphics processing unit, etc.), which may perform various appropriate actions and processes according to a program stored in the read-only memory (ROM) 102 or a program loaded from the storage device 108 into the random access memory (RAM) 103 to implement the device connection method of the embodiments as described in the present disclosure. In the RAM 103, various programs and data required for the operation of the electronic device 100 are also stored. The processing device 101, the ROM 102, and the RAM 103 are connected to each other through a bus 104. The input / output (I / O) interface 105 is also connected to the bus 104.

[0131] Generally, the following devices may be connected to the I / O interface 105: an input device 106 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; an output device 107 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; a storage device 108 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 109. The communication device 109 may allow the electronic device 100 to communicate with other devices wirelessly or wiredly to exchange data. Although Figure 7 the electronic device 100 with various devices is shown, it should be understood that it is not required to implement or have all the shown devices. Instead, more or fewer devices may be implemented or had.

[0132] Specifically, according to the embodiments of the present disclosure, the process described above with reference to the flowchart may be implemented as a computer software program. For example, the embodiments of the present disclosure include a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program includes program codes for executing the method shown in the flowchart, so as to implement the device connection method as described above. In such an embodiment, the computer program may be downloaded and installed from the network through the communication device 109, or installed from the storage device 108, or installed from the ROM 102. When the computer program is executed by the processing device 101, the above-mentioned functions defined in the method of the embodiments of the present disclosure are executed.

[0133] It should be noted that the computer-readable medium described above in the present disclosure may be a computer-readable signal medium, a computer-readable storage medium, or any combination of the two. A computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples of a computer-readable storage medium may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, a computer-readable storage medium may be any tangible medium that contains or stores a program, and this program can be used by or in combination with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries computer-readable program code. Such a propagated data signal may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium, and this computer-readable signal medium can send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device. The program code contained on a computer-readable medium can be transmitted by any appropriate medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0134] In some embodiments, the client and the server can communicate using any currently known or future-developed network protocol such as HTTP (HyperText Transfer Protocol), and can be interconnected with digital data communication in any form or medium (e.g., a communication network). Examples of communication networks include local area networks (“LAN”), wide area networks (“WAN”), the Internet (e.g., the Internet), and end-to-end networks (e.g., ad hoc end-to-end networks), as well as any currently known or future-developed network.

[0135] The above computer-readable medium may be included in the above electronic device; or it may exist separately without being assembled into the electronic device.

[0136] Optionally, when the above one or more programs are executed by the electronic device, the electronic device may also perform the other steps described in the above embodiments.

[0137] Computer program code for performing the operations of this disclosure may be written in one or more programming languages or combinations thereof. The programming languages include, but are not limited to, object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program code may execute entirely on the device computer, partially on the device computer, execute as a stand-alone software package, execute partially on the device computer and partially on a remote computer, or execute entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the device computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or alternatively, may be connected to an external computer (e.g., through the Internet using an Internet service provider).

[0138] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in the flowchart or block diagram may represent a module, a segment of a program, or a part of code that contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order than marked in the accompanying drawings. For example, two consecutive blocks shown may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, and combinations of blocks in the block diagram and / or flowchart, may be implemented by a dedicated hardware-based system for performing the specified functions or operations, or may be implemented by a combination of dedicated hardware and computer instructions.

[0139] The units involved in the embodiments described in this disclosure may be implemented in software or in hardware. Among them, the name of the unit does not constitute a limitation on the unit itself in some cases.

[0140] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGA), application specific integrated circuits (ASIC), application specific standard products (ASSP), system on a chip (SOC), complex programmable logic devices (CPLD), and so on.

[0141] In the context of the present disclosure, a machine-readable medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0142] It should be noted that, in this document, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variation thereof is intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a series of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the statement "including a device connection" does not exclude the presence of additional identical elements in the process, method, article, or apparatus that includes the element.

[0143] The above are only specific embodiments of the present disclosure, enabling those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to the embodiments described herein, but rather to the broadest scope consistent with the principles and novel features disclosed herein.

Claims

1. A device connection method, characterized in that: Applied to a wearable device, the method comprises: Receiving a connection request sent by a terminal device, wherein the connection request includes device information of the terminal device; In response to the connection request, determining whether the device information is stored in a near field communication chip configured in the wearable device; In a case where the near field communication chip does not store the device information, obtaining first connection information, wherein the first connection information reflects whether the wearable device can connect to a new device; When the first connection information indicates that a new device cannot be connected, a first connection result indicating a device connection failure is sent to the terminal device.

2. The method according to claim 1, characterized in that After determining whether the device information is stored in the near field communication chip configured in the wearable device, the method further includes: In a case where the near field communication chip stores the device information, a communication connection between the terminal device and the wearable device is established, and a second connection result indicating a successful device connection is sent to the terminal device.

3. The method according to claim 1, characterized in that After obtaining the first connection information, the method further includes: When the first connection information indicates that a new device can be connected, performing communication pairing with the terminal device through the near field communication chip; If the pairing is successful, establishing a communication connection between the terminal device and the wearable device, and sending a second connection result indicating successful device connection to the terminal device; The device information is recorded in the near field communication chip.

4. The method according to claim 1, characterized in that: Before determining whether the device information is stored in the near field communication chip configured in the wearable device, the method further includes: Determine whether information of a first device is stored in the near field communication chip, wherein the first device refers to a privileged device having operation authority for the wearable device, and the operation authority includes restoring factory settings, editing device information, and / or setting connection information; In the case where the near field communication chip stores the information of the first device, determining whether the near field communication chip stores the device information; or, When the near field communication chip does not store the information of the first device, an authentication request is sent to the terminal device, and when the connection authentication is successful, the device information determined as the information of the first device is recorded in the near field communication chip.

5. The method according to claim 4, characterized in that In the case where the near field communication chip stores information of the first device, the method further includes: Acquire second connection information, wherein the second connection information reflects whether the wearable device can connect to a second device, the second device is different from the first device, and the second device refers to a common device that has no operation authority for the wearable device; In the case where the second connection information indicates that the second device can be connected, determining whether the device information is stored in the near field communication chip; or, When the second connection information indicates that the second device cannot be connected and the terminal device is not the first device, the first connection result is sent to the terminal device.

6. The method according to claim 1, characterized in that The method further comprises: Receiving an operation instruction sent by the terminal device; In response to the operation instruction, determining whether the terminal device is a first device having operation authority for the wearable device; In the case that the terminal device is not the first device, the operation instruction is not processed, and a first processing result of processing failure is sent to the terminal device; or In a case where the terminal device is the first device, the operation instruction is processed, and a second processing result indicating successful processing is sent to the terminal device.

7. The method according to claim 6, characterized in that The operation instruction includes an editing instruction, and the editing instruction is used to edit the device information stored in the near field communication chip. The processing of the operation instruction includes: In the case where the operation instruction is the editing instruction, if the editing instruction is to delete the information of the first device, then all device information stored in the near field communication chip is deleted.

8. A device connection method, characterized in that: Applied to a terminal device, the method comprises: Sending a connection request to the wearable device, wherein the connection request includes device information of the terminal device; Receive a first connection result of a device connection failure sent by the wearable device, wherein the first connection result is generated by the wearable device in response to the connection request when a near-field communication chip configured in the wearable device does not store the device information and the first connection information obtained is that a new device cannot be connected, wherein the first connection information reflects whether the wearable device can connect to a new device.

9. The method according to claim 8, characterized in that After sending the connection request to the wearable device, the method further includes: Receive a second connection result of successful device connection sent by the wearable device, wherein the second connection result is generated by the wearable device without the need to perform connection authentication with the terminal device through the near-field communication chip, or the second connection result is generated when the wearable device successfully performs connection authentication with the terminal device through the near-field communication chip.

10. The method according to claim 8, characterized in that The method further comprises: Sending an operation instruction to the wearable device, wherein the operation instruction is used to instruct the wearable device to restore factory settings, edit device information and / or set connection information; Receive a processing result sent by the wearable device, wherein the processing result is a processing failure result generated by the wearable device when the terminal device is not a first device with operation authority; or, the processing result is a processing success result generated by the wearable device when the terminal device is the first device.

11. A device connection device, characterized in that: Applied to wearable devices, including: A first receiving unit, configured to receive a connection request sent by a terminal device, wherein the connection request includes device information of the terminal device; a determination unit, configured to determine, in response to the connection request, whether the device information is stored in a near field communication chip configured in the wearable device; an acquiring unit, configured to acquire first connection information when the near field communication chip does not store the device information, wherein the first connection information reflects whether the wearable device can connect to a new device; The first sending unit is configured to send a first connection result indicating a device connection failure to the terminal device when the first connection information indicates that a new device cannot be connected.

12. A device connection device, characterized in that: Applied to terminal equipment, including: A second sending unit, configured to send a connection request to the wearable device, wherein the connection request includes device information of the terminal device; A second receiving unit is used to receive a first connection result of a device connection failure sent by the wearable device, wherein the first connection result is generated by the wearable device in response to the connection request when a near field communication chip configured in the wearable device does not store the device information and the acquired first connection information indicates that a new device cannot be connected, wherein the first connection information reflects whether the wearable device can connect to a new device.

13. An electronic device, characterized in that: include: Memory; processor; as well as Computer programs; The computer program is stored in the memory and is configured to be executed by the processor to implement the device connection method as claimed in any one of claims 1 to 10.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the device connection method according to any one of claims 1 to 10 are implemented.

Images