Wearable device connection method and device

The method allows wearable devices to seamlessly switch connections between terminal devices using notification and broadcast messages, enhancing user experience by simplifying operations and ensuring security.

CN119071788APending Publication Date: 2024-12-03HONOR DEVICE CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202310647974.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2023-05-31
Publication Date
2024-12-03

AI Technical Summary

Technical Problem

Wearable devices require cumbersome operations to switch connections between different terminal devices, such as disconnecting from one device and reconnecting to another, which degrades user experience.

Method used

A method for wearable devices to establish connections with multiple terminal devices by sending notification messages and broadcast messages, allowing seamless switching without user intervention, using short-range wireless communication protocols like Bluetooth, Zigbee, Wi-Fi, or Mesh, and displaying interfaces for user interaction.

Benefits of technology

Simplifies user operations by enabling wearable devices to connect to multiple terminal devices securely and efficiently, saving power and resources while maintaining user information security.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119071788A_ABST
    Figure CN119071788A_ABST
Patent Text Reader

Abstract

The embodiment of the invention provides a connection method and device of a wearable device, the method is executed by the wearable device, the wearable device establishes a first connection with a first terminal device, and the method comprises the following steps: receiving notification information sent by the first terminal device, the notification information is used for indicating that a second terminal device having a trust relationship with the first terminal device exists around, and the notification information is received after the wearable device enters a preset geographic area; in response to the notification information, sending a first broadcast message to surrounding equipment; according to the notification information, a first interface is displayed, the first interface comprises a first control, in response to a connection instruction input by the user by clicking the first control, a second connection is established with a second terminal device, and the second connection is a short-distance wireless communication connection based on a second communication protocol; or, in response to a first request message sent by the second terminal device, establishing a third connection with the second terminal device. The method can simplify user operation and improve user experience.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of electronic technology, and in particular to a connection method and device for a wearable device. Background Art

[0002] With the advancement of technology, wearable devices (such as smart watches, sports bracelets, etc.) are being used more and more widely and their functions are becoming more and more abundant. For example, wearable devices can be connected to terminal devices for somatosensory fitness. Specifically, wearable devices can be connected to terminal devices such as mobile phones, large-screen devices or tablets. Wearable devices collect user motion data and transmit it to terminal devices. Terminal devices display or give feedback on user actions based on the motion data.

[0003] Generally, a wearable device can only establish a connection with one terminal device. To achieve the connection between the wearable device and other terminal devices, the user needs to perform more complicated operations. Take a smart watch as an example. When the smart watch is connected to a mobile phone, if the user needs to connect the smart watch to a large-screen device (such as a smart TV), it is necessary to first disconnect the smart watch from the mobile phone and unbind the two so that the smart watch can be paired. After that, the user controls the large-screen device to search for the smart watch, and inputs the connection command through the large-screen device to instruct the large-screen device to establish a connection with the smart watch. This process is rather cumbersome and the user experience is not good. Summary of the invention

[0004] The present application provides a wearable device connection method and device, which can simplify user operations and improve user experience.

[0005] In a first aspect, the present application provides a connection method for a wearable device, which is executed by the wearable device, wherein the wearable device has established a first connection with a first terminal device, and the first connection is a short-range wireless communication connection based on a first communication protocol. The method includes: receiving a notification message sent by the first terminal device, the notification message is used to indicate that there is a second terminal device with a trust relationship with the first terminal device in the surrounding area, and the notification message is received after the wearable device enters a preset geographical area; in response to the notification message, sending a first broadcast message to surrounding devices, and the first broadcast message is used for surrounding devices to discover the wearable device; according to the notification message, displaying a first interface, the first interface includes a first control, and in response to a connection instruction input by the user by clicking the first control, establishing a second connection with the second terminal device, and the second connection is a short-range wireless communication connection based on the second communication protocol; or, in response to a first request message sent by the second terminal device, establishing a third connection with the second terminal device, and the third connection is a short-range wireless communication connection based on a third communication protocol.

[0006] Optionally, the first terminal device may be, for example, a mobile phone, a tablet computer, etc. The second terminal device may be, for example, a large-screen device. The wearable device may be, for example, a smart watch, a sports bracelet, etc.

[0007] Optionally, the first communication protocol, the second communication protocol and the third wireless communication protocol may be one of short-range wireless communication protocols such as Bluetooth protocol, Matter protocol, Zigbee protocol, wireless fidelity (Wi-Fi) protocol, Thread protocol or Mesh protocol. The first communication protocol and the second communication protocol may be the same protocol or different protocols. Optionally, the first communication protocol and the third communication protocol may be the same protocol or different protocols.

[0008] Optionally, the notification information may carry the device information of the second terminal device. The device information of the second terminal device includes, but is not limited to, the media access control (MAC) address. The wearable device may display the first interface based on the device information of the second terminal device in the notification information. The first interface may include the device information of the second terminal device. In addition, when the notification information carries the device information of the second terminal device, the wearable device may send a discoverable broadcast to the second terminal device based on the device information of the second terminal device, that is, the device information (such as the MAC address) of the second terminal device may be carried in the discoverable broadcast. The smart watch sends a discoverable broadcast to the second terminal device. After other devices receive the discoverable broadcast and determine that the MAC address carried in the broadcast message is inconsistent with their own MAC address, they will discard the discoverable broadcast message and will not continue to parse it. In this way, the disturbance of the wearable device to other surrounding devices can be reduced, the power consumption of surrounding devices can be saved, and the user experience can be improved.

[0009] Optionally, the first request message is used to request to establish a connection with the wearable device. When the third communication protocol is a Bluetooth protocol, the first request message may be a pairing request.

[0010] In general, when a wearable device has established a connection with a terminal device, the wearable device is in a paired state. Considering the security of user information, the wearable device no longer sends discoverable broadcasts to the surroundings. Only when the user disconnects the connection and releases the binding relationship between the two, will the wearable device be triggered to send discoverable broadcasts to the surroundings again. The method provided in the first aspect of the present application, when a Bluetooth connection has been established between a first terminal device and a wearable device, receives a notification message sent by the first terminal device to obtain information about the existence of a second terminal device with a trust relationship with the first terminal device in the current scene. In this scenario, if the wearable device does not release the binding relationship with the first terminal device, re-establishing a connection with the second terminal device will not affect the security of user information. Therefore, the wearable device sends a discoverable broadcast to surrounding devices, so that the wearable device can be scanned and discovered by the wearable device. Afterwards, the user operates on the second terminal device, or on the wearable device side, so that the second terminal device establishes a short-range wireless communication connection with the wearable device. That is to say, in this embodiment, when the wearable device has established a first connection with the first terminal device, the wearable device can send a discoverable broadcast to the surrounding without the user performing the disconnection and unbinding operations, so as to establish a second connection or a third connection with the second terminal device, simplifying user operations and improving user experience. Moreover, the second connection or the third connection established between the wearable device and the second terminal device is highly secure. In addition, in this embodiment, the first interface is displayed according to the notification information, so that the user can trigger the connection with the second terminal device based on the first interface input instruction, without the user performing the operation of scanning and discovering the second terminal device on the wearable device side, further simplifying user operations and improving user experience.

[0011] In a possible implementation, the method further includes: before establishing a connection with the second terminal device, automatically disconnecting a physical link with the first terminal device.

[0012] That is, before "establishing a second connection with the second terminal device", the method further includes: in response to a connection instruction input by the user by clicking the first control, automatically disconnecting the physical link with the first terminal device (i.e., the physical link in the first connection). Or, before "establishing a third connection with the second terminal device", the method further includes: in response to a first request message sent by the second terminal device, automatically disconnecting the physical link with the first terminal device.

[0013] In this implementation, the wearable device receives the notification information sent by the first terminal device, so it can be determined that the current application scenario is: the wearable device is connected to the first terminal device, and there is a trusted device in the current surrounding environment, and the trusted device is the second terminal device. In this scenario, if the wearable device receives a connection instruction from the user to establish a connection with the second terminal device, or receives a first request message (such as a pairing request) from the second terminal device, it can be confirmed that the connection between the wearable device and the second terminal device will not affect the security of the user information. Therefore, the wearable device can automatically disconnect the connection with the first terminal device and then establish a connection with the second terminal device without displaying an interface to inquire the user or manually operating the user. In this way, not only is the short-range wireless communication connection of the wearable device switched from the first terminal device to the second terminal device, but the user does not need to perform the related operations of disconnection and unbinding, which simplifies the user operation and further improves the user experience. On the other hand, in this scenario, the wearable device can confirm that even if the wearable device does not unbind the binding relationship with the first terminal device, it will not affect the security of the user information. Therefore, the wearable device can only disconnect the physical link with the first terminal device. In this way, when the wearable device is subsequently reconnected with the first terminal device, there is no need to enter the logical link establishment stage (such as the pairing stage), and the user does not need to perform related operations to establish the logical link (such as the pairing confirmation operation), which saves the execution programs of the wearable device and the first terminal device, simplifies user operations, and improves user experience.

[0014] In a possible implementation, establishing a connection with the second terminal device includes: maintaining a first connection with the first terminal device; establishing a connection with the second terminal device, and the connection between the wearable device and the second terminal device only includes a data transmission channel.

[0015] That is to say, the wearable device does not disconnect the first connection with the first terminal device. In this case, the second connection or the third connection established between the wearable device and the second terminal device only includes the data transmission channel.

[0016] In this implementation, after the wearable device learns the current application scenario based on the notification information, it determines that the connection with the second terminal device is highly secure, so the wearable device can directly establish a second short-range wireless communication connection with the second terminal device without disconnecting the connection with the first terminal device, thereby facilitating the user to interact with both the first terminal device and the second terminal device through the wearable device at the same time, thereby improving the user experience. Moreover, after determining the current application scenario, the wearable device only establishes a data transmission channel with the second terminal device. This can simplify the process of establishing a connection between the wearable device and the second terminal device, save channels, and save power consumption and resources of both.

[0017] In a possible implementation, the first communication protocol is a Bluetooth protocol, the second communication protocol or the third communication protocol is a Bluetooth protocol, and the data transmission channel is a serial port profile (SPP) channel.

[0018] In a possible implementation, the first communication protocol and the third communication protocol are the same communication protocol, or the first communication protocol and the second communication protocol are the same communication protocol. In this way, the wearable device uses the same communication protocol to communicate with the first terminal device and the second terminal device, which facilitates the management and operation of the wearable device and saves resources and power consumption.

[0019] In a possible implementation, the first broadcast message carries first information, and the first information is used to indicate that a first connection has been established between the wearable device and the first terminal device.

[0020] It can be understood that the first broadcast carries the first information, and after receiving the first broadcast message, the second terminal device can learn the current application scenario, that is, the wearable device has established a connection with the first terminal device, and there are devices with a trust relationship with the first terminal device around, so that the second terminal device can determine the display interface according to the scenario. For example, in general, in this scenario, the probability of the user connecting the wearable device in the second terminal device is relatively high. Therefore, after determining the current application scenario according to the first information, the second terminal device can pop up the information interface of the wearable device to remind the user whether to connect, etc., to facilitate user operation and improve user experience.

[0021] In a second aspect, the present application provides a connection method for a wearable device, which is executed by a first terminal device, and the first terminal device has established a first connection with the wearable device. The method includes: when the first terminal device enters a preset geographical area, determining that there is a second terminal device that has a trust relationship with the first terminal device around; after determining that there is a second terminal device that has a trust relationship with the first terminal device around, sending a notification message to the wearable device, the notification message is used to indicate that there is a second terminal device that has a trust relationship with the first terminal device around.

[0022] The method provided in the second aspect of the present application is to send notification information to the wearable device when the first terminal device establishes a connection with the wearable device and the first terminal device enters a preset geographical area and there is a second terminal device with a trust relationship around the first terminal device. In this way, it is convenient for the wearable device to obtain the current scene, so that it is convenient for the wearable device to send a discoverable broadcast to the second terminal device, without the user having to perform disconnection and unbinding operations, simplifying user operations and improving user experience.

[0023] In one possible implementation, determining whether there is a second terminal device that has a trust relationship with the first terminal device in the surrounding area includes: obtaining historical scanning information of the first terminal device, the historical scanning information is used to characterize device information of terminal devices that the first terminal device scanned and discovered within a preset geographical area within a historical time period; comparing information of multiple devices that have a trust relationship with the first terminal device with the historical scanning information, and if information of the second terminal device exists in both the historical scanning information and the information of the multiple devices, then determining that there is a second terminal device that has a trust relationship with the first terminal device in the surrounding area.

[0024] Multiple devices having a trust relationship with the first terminal device, that is, devices within the trust ring of the first terminal device.

[0025] In this implementation, by obtaining historical scanning information and determining whether the second terminal device is a device that has a trust relationship with the first terminal device based on the historical scanning information, the first terminal device does not need to scan surrounding devices to obtain device information of the surrounding devices, thereby saving power consumption of the first terminal device.

[0026] In a third aspect, the present application provides a connection method for a wearable device, which is executed by a second terminal device, and the second terminal device is located in a preset geographical area. The method includes: receiving a first broadcast message sent by the wearable device, the first broadcast message carrying first information, the first broadcast message being used for surrounding devices to discover the wearable device, the first information being used to characterize that a first connection has been established between the wearable device and the first terminal device, and the first connection is a short-range wireless communication connection based on a first communication protocol; in response to the first broadcast message, displaying a second interface according to the first information, and the second interface including a second control; in response to a connection instruction input by the user by selecting the second control, sending a first request message to the wearable device, the first request message being used to request to establish a third connection with the wearable device, and the third connection is a short-range wireless communication connection based on a third communication protocol.

[0027] In the method provided in the third aspect of the present application, the first broadcast message carries the first information, and the second terminal device can directly display the second interface according to the first information in the first broadcast message, and the user can trigger the connection between the second terminal device and the wearable device through the second interface. In this way, the user does not need to perform a scanning and discovery operation on the second terminal device, which simplifies the user operation and improves the user experience.

[0028] In a possible implementation, the first communication protocol and the third communication protocol are the same communication protocol.

[0029] In a possible implementation manner, the third connection only includes a data transmission channel.

[0030] In this implementation, the third connection only includes a data transmission channel, which can save channels, save the connection process between the wearable device and the second terminal device, and save device resources and power consumption.

[0031] In a possible implementation, the first communication protocol and the third communication protocol are both Bluetooth protocols, and the data transmission channel is a serial port profile SPP channel.

[0032] In a fourth aspect, the present application provides a connection method for a wearable device, which is executed by a second terminal device, the distance between the wearable device and the second terminal device is a distance for short-range wireless communication, and the second terminal device logs in to a first user account, the method comprising: in response to a user's operation of viewing surrounding wireless communication devices, obtaining device information of the wearable device and connection information for establishing a connection with the wearable device from a server according to the first user account, the device information and connection information being uploaded to the server by the first terminal device using the first user account; displaying a third interface according to the device information, the third interface including a third control; in response to a connection instruction input by the user by selecting the third control, establishing a third connection with the wearable device according to the connection information, the third connection being a short-range wireless communication connection based on a third communication protocol.

[0033] Optionally, when the third communication protocol is a Bluetooth protocol, the connection information may be, for example, a pairing key.

[0034] Optionally, the server may be a cloud service, or referred to as a cloud platform, cloud end, etc.

[0035] In the method provided in the fourth aspect of the present application, the second terminal device can obtain the device information and connection information of the wearable device from the server through the first user account, and then display the interface according to the information, thereby realizing the connection with the wearable device in response to the user's operation. The entire process does not require the user to perform disconnection and unbinding operations, and the third interface can be displayed without the user performing a scan and discovery operation, thereby simplifying user operations and improving user experience. In addition, the second terminal device can directly establish a connection with the wearable device based on the connection information, without having to obtain connection information from the wearable device, thereby simplifying the connection process.

[0036] In a possible implementation, the first terminal device has established a first connection with the wearable device, and the first connection is a short-range wireless communication connection based on a first communication protocol; the third connection only includes a data transmission channel.

[0037] In this implementation, the third connection only includes a data transmission channel, which can save channels, save the connection process between the wearable device and the second terminal device, and save device resources and power consumption.

[0038] In a possible implementation, the third communication protocol is a Bluetooth protocol, and the data transmission channel includes an SPP channel.

[0039] In a possible implementation, the first communication protocol is the same as the third communication protocol.

[0040] In a fifth aspect, the present application provides a connection method for a wearable device, the method being executed by a second terminal device, the method comprising: in response to a first instruction of a user, sending a second broadcast message to surrounding devices, the second broadcast message being used to request a plurality of surrounding wearable devices to establish a short-range wireless communication connection with the second terminal device and join a group, the plurality of wearable devices comprising a first wearable device and a second wearable device, the first wearable device being a device among the plurality of wearable devices that has not established a short-range wireless communication connection with the second terminal device, the second wearable device being a device among the plurality of wearable devices that has established a fourth connection with the second terminal device, the fourth connection being a short-range wireless communication based on a fourth communication protocol. Communication connection; receiving a connection consent message and a first teaming consent message sent by a first wearable device, wherein the connection consent message indicates that the first wearable device agrees to establish a connection with the second terminal device, and the first teaming consent message indicates that the first wearable device agrees to join the group; in response to the connection consent message and the first teaming consent message, establishing a fifth connection with the first wearable device, and adding the first wearable device to the group, the fifth connection is a short-range wireless communication connection based on a fifth communication protocol, and the fifth connection only includes a data transmission channel; in response to a second teaming consent message sent by a second wearable device, adding the second wearable device to the group, and the second teaming consent message indicates that the second wearable device agrees to join the group.

[0041] The method provided in the fifth aspect of the present application enables the second terminal device to be connected to multiple wearable devices at the same time, meeting the user's usage needs in scenarios such as team games and team fitness, and improving the user experience. In addition, when establishing a connection, the second wearable device has established a fourth connection with the second terminal device, so the first wearable device and the second terminal device only need to establish a data transmission channel to meet the user's usage needs (data transmission) in this scenario. In this way, the process of establishing a connection between the second terminal device and the first wearable device can be saved, saving resources and power consumption.

[0042] In a possible implementation, the fourth connection includes a data transmission channel and at least one of a call transmission channel and an audio transmission channel.

[0043] Optionally, when the fourth communication protocol is the Bluetooth protocol, the call transmission channel may be, for example, a hands free profile (HFP) channel, and the audio transmission channel may be, for example, an advanced audio distribution profile (A2DP) channel.

[0044] In this implementation, the fourth connection includes at least one of a call transmission channel and an audio transmission channel in addition to the data transmission channel, which can meet the user's call needs and audio transmission needs and further improve the user experience.

[0045] In a possible implementation, the fifth communication protocol is a Bluetooth protocol, and the data transmission channel is a serial port profile SPP channel.

[0046] In a possible implementation, the second broadcast message includes scene information, where the scene information includes team gaming or team fitness.

[0047] In one possible implementation, the method further includes: in response to a second instruction input by the user, based on a short-range wireless communication connection with each wearable device, obtaining data from each wearable device respectively, wherein the second instruction is used to instruct to start a game or to start fitness.

[0048] In a possible implementation, the second broadcast message is a Bluetooth low energy broadcast.

[0049] In this implementation, the second broadcast message is a Bluetooth low energy broadcast, which can save power consumption of the second terminal device.

[0050] In a sixth aspect, the present application provides a device, which is included in a wearable device, and the device has the function of implementing the behavior of the wearable device in the above-mentioned first aspect and the possible implementation of the above-mentioned first aspect. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions. For example, a receiving module or unit, a processing module or unit, etc.

[0051] In a seventh aspect, the present application provides an apparatus, which is included in a first terminal device, and has the function of implementing the behavior of the first terminal device in the second aspect and the possible implementation of the second aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. For example, a receiving module or unit, a processing module or unit, etc.

[0052] In an eighth aspect, the present application provides a device, which is included in a second terminal device, and has the function of implementing the second terminal device behavior in the third, fourth, and fifth aspects and the possible implementation methods of the third, fourth, and fifth aspects. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the above functions. For example, a receiving module or unit, a processing module or unit, etc.

[0053] In a ninth aspect, the present application provides a wearable device comprising: a processor, a memory and a short-range wireless communication module; the processor, the memory and the short-range wireless communication module cooperate with each other so that the wearable device executes any one of the methods in the technical solution of the first aspect.

[0054] In the tenth aspect, the present application provides a terminal device, including: a processor, a memory and a short-range wireless communication module; the processor, the memory and the short-range wireless communication module cooperate with each other so that the terminal device executes any one of the methods in the technical solution of the second aspect.

[0055] In the eleventh aspect, the present application provides a terminal device, including: a processor, a memory and a short-range wireless communication module; the processor, the memory and the short-range wireless communication module cooperate with each other so that the terminal device executes any one of the technical solutions of the third aspect, the fourth aspect or the fifth aspect.

[0056] In a twelfth aspect, the present application provides a chip, including a processor. The processor is used to read and execute a computer program stored in a memory to perform the method in the first aspect and any possible implementation thereof.

[0057] Optionally, the chip also includes a memory, and the memory is connected to the processor via a circuit or wire.

[0058] Further optionally, the chip also includes a communication interface.

[0059] In a thirteenth aspect, the present application provides a chip, including a processor. The processor is used to read and execute a computer program stored in a memory to perform the method in the second aspect and any possible implementation thereof.

[0060] In a fourteenth aspect, the present application provides a chip, including a processor, wherein the processor is configured to read and execute a computer program stored in a memory to execute the method in the third, fourth, or fifth aspect and any possible implementation thereof.

[0061] In the fifteenth aspect, the present application provides a computer-readable storage medium, which stores a computer program. When the computer program is executed by a processor, the processor executes any one of the methods in the technical solutions of the first, second, third, fourth or fifth aspects.

[0062] In the sixteenth aspect, the present application provides a computer program product, which includes: a computer program code, when the computer program code runs on an electronic device, the electronic device executes any one of the technical solutions of the first, second, third, fourth or fifth aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0063] Figure 1 is a schematic diagram of an application scenario of a connection method for a wearable device provided in an embodiment of the present application;

[0064] Figure 2 This is a schematic diagram of an application scenario in which a user performs physical fitness through a large-screen device, provided in an embodiment of the present application;

[0065] Figure 3 This is a schematic diagram of a process of disconnecting the Bluetooth connection between a mobile phone and a smart watch and releasing the binding relationship provided in an embodiment of the present application;

[0066] Figure 4 This is a schematic diagram of a process of establishing a Bluetooth connection between a smart watch and a large-screen device provided in an embodiment of the present application;

[0067] Figure 5 This is a schematic diagram of an interface of a smart watch during a pairing process provided in an embodiment of the present application;

[0068] Figure 6 is a flowchart of a method for connecting a wearable device provided in an embodiment of the present application;

[0069] Figure 7 is a schematic diagram of an application scenario of another wearable device connection method provided in an embodiment of the present application;

[0070] Figure 8 is a schematic diagram of interface changes corresponding to a connection method for a wearable device provided in an embodiment of the present application;

[0071] Fig. 9 This is a schematic diagram of an interface of a large-screen device provided in an embodiment of the present application;

[0072] Fig.10 This is a schematic diagram of a connection change between a smart watch, a mobile phone, and a large-screen device provided in an embodiment of the present application;

[0073] Fig.11 is a flowchart of another wearable device connection method provided in an embodiment of the present application;

[0074] Fig.12 This is another example of a connection change diagram between a smart watch, a mobile phone, and a large-screen device provided in an embodiment of the present application;

[0075] Fig.13 is a flowchart of another example of a connection method for a wearable device provided in an embodiment of the present application;

[0076] Fig.14 is a flowchart of another example of a connection method for a wearable device provided in an embodiment of the present application;

[0077] Fig.15 is a schematic diagram of an interface of another large-screen device provided in an embodiment of the present application;

[0078] Fig.16 This is another example of a connection change diagram between a smart watch and a mobile phone and a large-screen device provided in an embodiment of the present application;

[0079] Fig.17 is a schematic diagram of an application scenario of another connection method for a wearable device provided in an embodiment of the present application;

[0080] Fig.18 is a flowchart of another example of a connection method for a wearable device provided in an embodiment of the present application;

[0081] Fig.19 This is a schematic diagram of an interface for playing a team fitness game on a large-screen device provided in an embodiment of the present application;

[0082] Fig. 20 This is a schematic diagram of an interface in which a smart watch receives a team BLE broadcast sent by a large-screen device, provided in an embodiment of the present application;

[0083] Fig.21 This is a schematic diagram of a process of establishing Bluetooth connection between a large-screen device and multiple wearable devices provided in an embodiment of the present application;

[0084] Fig. 22 is a schematic structural diagram of a wearable device 100 provided in an embodiment of the present application;

[0085] Fig.23 is a schematic diagram of the structure of a first terminal device 200 provided in an embodiment of the present application;

[0086] Fig.24 is a schematic diagram of the structure of a second terminal device 300 provided in an embodiment of the present application;

[0087] Fig.25 is a schematic diagram of a software architecture of a wearable device 100 provided in an embodiment of the present application;

[0088] Fig.26 is a schematic diagram of a software architecture of a first terminal device 200 provided in an embodiment of the present application;

[0089] Fig. 27This is a schematic diagram of the software architecture of an example of a second terminal device 300 provided in an embodiment of the present application. DETAILED DESCRIPTION

[0090] The technical solutions in the embodiments of the present application will be described below in conjunction with the drawings in the embodiments of the present application. In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is only a description of the association relationship of associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of the present application, "multiple" means two or more than two.

[0091] In the following, the terms "first", "second", and "third" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first", "second", and "third" may explicitly or implicitly include one or more of the features.

[0092] References to "one embodiment" or "some embodiments" etc. described in the specification of the present application mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Therefore, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in the specification of the present application do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0093] In order to better understand the embodiments of the present application, the terms or concepts that may be involved in the embodiments are explained below.

[0094] 1. Connect

[0095] The connection in the embodiments of the present application mainly refers to a short-range wireless communication connection. The communication protocol of the short-range wireless communication connection can be one of the Bluetooth protocol, Matter protocol, Zigbee protocol, wireless fidelity (Wi-Fi) protocol, Thread protocol or Mesh protocol. In the embodiments of the present application, the short-range wireless communication connection based on the Bluetooth protocol (referred to as Bluetooth connection) is mainly used as an example for explanation.

[0096] 2. Bluetooth devices

[0097] A Bluetooth device refers to a module or device used in an electronic device to achieve Bluetooth connection. Bluetooth devices are mainly divided into classic Bluetooth devices, Bluetooth low energy (BLE) devices (or low-power Bluetooth devices, referred to as BLE Bluetooth devices) and dual-mode Bluetooth devices. Among them, classic Bluetooth devices include basic rate (BR) Bluetooth devices / enhanced data rate (EDR) Bluetooth devices, (high speed, HS) Bluetooth devices, etc. A dual-mode Bluetooth device is a Bluetooth device that integrates the controllers of classic Bluetooth devices and low-power Bluetooth devices.

[0098] 3. Transmission channel of Bluetooth connection

[0099] Taking classic Bluetooth devices as an example, a Bluetooth connection may include transmission channels for one or more profiles, of which the following are listed:

[0100] 3.1 HFP channel

[0101] HFP is the full name of hands free profile in English and hands-free profile in Chinese. HTP defines two roles, audio gateway (AG) and hands-free component (HF), to provide remote wireless control and voice connection between audio gateway and hands-free device through Bluetooth connection. The audio gateway can be a mobile phone, such as a cell phone. In short, based on the HFP channel, the Bluetooth device can control the phone (i.e., call) functions, such as answering, hanging up, rejecting, voice dialing, etc.

[0102] 3.2 A2DP Channel

[0103] A2DP is the full name of Advanced Audio Distribution Profile in English and Chinese. A2DP specifies the protocol stack software and usage methods for transmitting high-quality audio data using Bluetooth asynchronous transmission channels. Based on the A2DP channel, Bluetooth devices can transmit high-quality audio data to each other.

[0104] 3.3 SPP Channel

[0105] SPP is the full name of serial port profile in English. SPP defines the Bluetooth device requirements required to set up a simulated serial cable connection between two peer devices using the serial port emulation protocol (radio frequency communication, RFCOMM). These requirements are expressed in terms of services provided to applications and the functions and processes required to define interoperability between Bluetooth devices. In short, based on the SPP channel, Bluetooth devices can achieve point-to-point data transmission capabilities.

[0106] It should be noted that there are many types of Bluetooth profiles, which are not listed here one by one. Bluetooth devices can select the required profile and establish the corresponding profile channel as needed.

[0107] 4. Trust Ring and Trusted Devices

[0108] Two or more terminal devices establish a trust relationship through trusted authentication to form a trust ring. In other words, if there is a trust relationship between multiple devices, it can be understood that multiple devices form a trust ring.

[0109] Terminal devices can perform trusted authentication, establish a trust relationship, and form a trust circle through any of the following methods: 1) Log in to the same account on two or more terminal devices respectively, and the terminal devices under the same account trust each other, then the above two or more electronic devices constitute a trust circle; for example, two mobile phones of the same user, or the mobile phone, tablet computer, laptop computer, etc. of the same user can perform trusted authentication by logging into the user's account, establish a trust relationship, and form a trust circle. 2) Two or more terminal devices perform trusted authentication through a private protocol, establish a trust relationship, and form a trust circle; 3) Two or more electronic devices perform trusted authentication by logging into the cloud, establish a trust relationship, and form a trust circle. It can be understood that the above methods are only used for illustration and do not constitute any limitation on this application.

[0110] The terminal devices within the trust ring form a local area network through near-field communication, through which data can be synchronized to achieve device collaboration.

[0111] A terminal device in a trust ring can be called a trusted device of other devices. In other words, terminal devices that have a trust relationship through trusted authentication are called trusted devices. For example, if a mobile phone, tablet computer, and laptop computer form a trust ring, the tablet computer and the mobile phone can be called trusted devices of each other, that is, the tablet computer is a trusted device of the mobile phone, and the mobile phone is also a trusted device of the tablet computer.

[0112] The application scenarios of the embodiments of the present application are described below.

[0113] Wearable devices such as smart watches, sports bracelets, smart wristbands, smart glasses, smart headbands, and headphones are increasingly being used in people's lives. Wearable devices can be paired with terminal devices to achieve related functions. For example, if the wearable device is a smart watch and the terminal device is a mobile phone, the smart watch can be paired with the mobile phone, so that the smart watch can answer calls on the mobile phone or upload data from the smart watch to the mobile phone.

[0114] After the wearable device is paired and connected with the terminal device, a binding relationship between the two will be automatically established, so that encryption authentication can be performed and the link can be encrypted the next time the connection is made. Among them, establishing a binding relationship means saving information such as the pairing key (also called the link key) of the other device. However, when the wearable device is bound to the terminal device, the terminal device can obtain a variety of information of the wearable device, including the user's account information, private information, etc. Therefore, considering the security of user information, generally, the wearable device can only establish a connection with one terminal device. If the wearable device is currently connected to a terminal device, when it needs to establish a connection with other terminal devices, the wearable device needs to obtain the user's consent, first disconnect from the current terminal device, and cancel the binding relationship with the terminal device, so that the wearable device enters a pairable state, and then pair and connect with other terminal devices. Among them, canceling the binding relationship is also called canceling pairing, etc., which means deleting information such as the pairing key with the bound device. The unbinding relationship can be triggered by clicking the cancel pairing control, delete device control, or connect new device control in the wearable device or terminal device. The following is explained in combination with the application scenario.

[0115] For example, Figure 1 This is a schematic diagram of an application scenario of a connection method for a wearable device provided in an embodiment of the present application. Figure 1 As shown in Figure (a), the current user's smart watch has established a connection with the mobile phone. If the user needs to connect the smart watch to a large-screen device to perform body-sensing fitness through the large-screen device, the user needs to first disconnect the smart watch from the mobile phone and unbind the two. Figure 1 As shown in Figure (b) in the figure. Afterwards, the smart watch establishes a connection with the large-screen device, as shown in Figure 1 As shown in Figure (c).

[0116] After the smart watch establishes a connection with the large-screen device, the user can perform somatosensory fitness through the large-screen device. Somatosensory fitness is also called artificial intelligence (AI) fitness or AI sports, which refers to sports fitness based on somatosensory technology. Somatosensory technology means that users do not need to use complex control equipment, but directly interact with surrounding devices or environments through body movements. Specifically, during somatosensory fitness, the wearable device collects the user's motion data through sensors such as gravity sensors and gyroscopes, and transmits the motion data to the large-screen device based on the connection with the large-screen device. The sports application (application, APP) in the large-screen device displays or feedbacks the user's movements according to the motion data. In one embodiment, after the user disconnects the smart watch from the mobile phone, the application scenario of somatosensory fitness through the large-screen device can be as follows: Figure 2 shown.

[0117] Optionally, the user can disconnect the smart watch from the phone and cancel the binding relationship by operating the smart watch, or disconnect the phone from the smart watch and cancel the binding relationship by operating the phone. Figure 3 This embodiment is described by taking the example of disconnecting the connection with the smart watch and unbinding the relationship by operating the mobile phone. Figure 3 As shown in Figure (a) in FIG. 1 , a user can click on a card 302 of a smart watch (shown as smart watch a) in a device interface 301 in a sports APP (such as sports health). In response to the user's click, the mobile phone displays an information interface 303 of smart watch a, such as Figure 3 As shown in Figure (b) of FIG. 1 , the interface includes a selection control 304. When the user clicks the selection control 304, a tab sheet 305 is displayed in the interface. The tab sheet 305 includes a delete device control 306, as shown in FIG. Figure 3 As shown in Figure (c) in FIG. 300 , the user clicks the delete device control 306, and a card 307 is displayed in the interface to ask the user whether to delete the device. Figure 3 As shown in FIG. (d) in FIG. 307, the card 307 includes a confirmation control 308. After the user clicks the confirmation control 308, the mobile phone and the smart watch are disconnected and the binding relationship is released.

[0118] Afterwards, the user can operate the smart watch or large-screen device to scan and discover the device, initiate a pairing connection, and establish a Bluetooth connection between the two. Figure 4 The following is a schematic diagram of a process of establishing a Bluetooth connection between a smart watch and a large-screen device provided in an embodiment of the present application. Take the example of scanning and discovering a device by operating a large-screen device and initiating a pairing connection. Figure 4As shown in Figure (a), when the Bluetooth of the large-screen device and the smart watch are both turned on, the user can open the sports app in the large-screen device and enter the main interface 401 of the sports app. The user can select the device control 402 in the main interface 401 through the remote control, and the device interface 403 is displayed in the large-screen device, as shown in Figure 404. Figure 4 The device interface 403 includes an add device card 404. The user selects the add device card 404 through the remote control, and the large screen device starts scanning the surrounding Bluetooth devices and displays the add device interface 405. Figure 4 As shown in Figure (c) in the figure. After scanning for a certain period of time, the large-screen device finds a smart watch (shown as smart watch a in the figure), and displays an information card 406 of the smart watch in the interface. The information card 406 of the smart watch includes a connection control 407. The user selects the connection control 407 through the remote control, and the large-screen device establishes a physical link with the smart watch.

[0119] Afterwards, the large screen device displays a pairing confirmation interface 408, asking the user whether to confirm pairing with the smart watch. The pairing confirmation interface 408 may include a pop-up window 409, and the pop-up window 409 includes a confirmation control 410 and a cancel control 411, such as Figure 4 As shown in Figure (d).

[0120] When the user clicks the confirmation control 410, the large screen device initiates a pairing request to the smart watch, and the mobile phone displays a first pairing interface 412, such as Figure 4 As shown in Figure (e).

[0121] After the large-screen device initiates a pairing request, the smart watch displays a pairing request interface. For example, the pairing request interface of the smart watch can be as follows: Figure 5 As shown in 501 in (a) of FIG. 1 , the pairing request interface 501 includes an accept pairing control 502. The user clicks the accept pairing control 502, and the large-screen device and the smart watch begin pairing. The smart watch displays a third pairing interface 503, as shown in FIG. Figure 5 At the same time, the mobile phone displays the second pairing interface 413, as shown in FIG. Figure 4 After a while, the large-screen device and the smart watch are paired and connected. After the connection is established, the interface of the large-screen device and the smart watch can be as follows: Figure 1 As shown in Figure (c).

[0122] It should be noted that Figure 4 and Figure 5 This is just an example. In actual applications, other operation methods can also be used to establish a Bluetooth connection between a large-screen device and a smart watch. For example, the remote control can be used to select Figure 4In (b) of the figure, the selection control 304 in the device interface 403 is used to trigger the large-screen device to scan the surrounding Bluetooth devices.

[0123] Depend on Figures 1 to 5 It can be seen from the illustrated embodiment that when the wearable device is connected to a terminal device, if it needs to connect to other devices, the user needs to go through multiple steps to disconnect the connection with the current terminal device and release the binding relationship, so that the wearable device enters a pairing state before it can establish a connection with other terminal devices. The process is relatively cumbersome and complicated, and the user experience is poor.

[0124] In view of this, an embodiment of the present application provides a connection method for a wearable device, which can simplify the connection process between the wearable device and the terminal device and improve the user experience.

[0125] The connection method of the wearable device provided in the embodiment of the present application involves a wearable device, a first terminal device, a second terminal device, a server, etc. Among them, the wearable device can be a sports bracelet, a sports anklet, a smart watch, a smart wristband, a smart glasses, a smart headband, a headset, etc. The embodiment of the present application does not impose any restrictions on the specific type of the wearable device.

[0126] Optionally, the first terminal device and the second terminal device can be large-screen devices, mobile phones, tablet computers, vehicle-mounted devices, augmented reality (AR) / virtual reality (VR) devices, laptop computers, ultra-mobile personal computers (UMPC), netbooks, personal digital assistants (PDA), etc., which can install application programs (APP) and have short-range wireless communication functions. The embodiments of the present application do not impose any restrictions on the specific types of the first terminal device and the second terminal device.

[0127] The following embodiments of the present application will take the wearable device as a smart watch, the first terminal device as a mobile phone, the second terminal device as a large-screen device, and the connection between the devices as a Bluetooth connection as an example, and combine the accompanying drawings and application scenarios to specifically explain the connection method of the wearable device provided in the embodiments of the present application.

[0128] In order to facilitate understanding of the solution of this embodiment, the process of establishing a Bluetooth connection between a wearable device and a terminal device is first briefly described. Take device A and device B as an example, where one of device A and device B is a wearable device and the other is a terminal device. The process includes:

[0129] 1) Send discoverable broadcasts

[0130] At least one of device A and device B can actively send discoverable broadcasts (also called broadcast packets or broadcast messages) at a certain time interval so that the device can be discovered by other devices. The following is an example of device A sending discoverable broadcasts to the surroundings. Generally, device A will send discoverable broadcasts to the surroundings only when it is in a pairing state. When device A is in a paired state, considering the security of user information, device A no longer establishes a connection with other devices, so device A does not send discoverable broadcasts to the surroundings.

[0131] 2) Scan and find

[0132] After receiving the discoverable broadcast sent by device A, the surrounding device (such as device B) can initiate a scan request to device A to obtain more device information of device A, such as device name, device type, etc. After receiving the scan request, device A sends a scan response packet to device B in response. The scan response packet can include device information of device A. In this case, device B is the connection initiator, that is, the master device, and device A is the connection receiver, that is, the slave device. The device that receives the scan request also needs to send a scan response packet in response.

[0133] For example, device B initiates a scan request to device A. After receiving the scan request, device A sends a scan response packet to device B. After device B receives the scan response packet, the device information of device A is displayed on the interface of device B.

[0134] It should be noted that, generally, when device A has established a connection with a device (such as device C), considering the security of user information, device A no longer establishes a connection with other devices. Therefore, device A no longer sends discoverable broadcasts to the surroundings and cannot be scanned and discovered by other devices (such as device B).

[0135] 3) Establish a physical link

[0136] After the scanning discovery is completed, in response to the user's connection instruction, device A establishes a physical link with device B. Optionally, the physical link may include an advanced communication link (ACL) and a SCO link, etc. When the user enters an instruction to establish a connection with device A in the interface of device B (for example, clicks the connection control corresponding to device A), device B responds to the connection instruction and establishes a physical link with device B.

[0137] 3) Pairing

[0138] After the physical link is established, device A and device B enter the pairing phase. Specifically, device A sends a pairing request to device B, or device B sends a pairing request to device A, and the two enter the pairing phase. The entry into the pairing phase can be triggered by a user input command or automatically triggered by the device, that is, after the physical link is established, the pairing phase is automatically entered.

[0139] The pairing phase is essentially the process of device A and device B negotiating and determining the encryption key. The pairing phase may include pairing feature exchange, link authentication, key distribution and binding.

[0140] Pairing feature exchange: used to exchange the authentication requirements (authenticationrequirements) of both parties (device A and device B), as well as the human-computer interaction capabilities (IO capabilities) of both parties.

[0141] Link authentication: Device A initiates a link authentication request to device B, or device B initiates a link authentication request to device A. If the other end accepts the pairing request, device A and device B perform link authentication.

[0142] Key distribution: Device A and device B generate a pairing key based on random numbers, pin codes, media access control (MAC) addresses, etc. The pairing key may include a long-term key (LTK). MAC is also called a MAC address.

[0143] Binding: Device A and device B store LTK and establish a binding relationship between them. After device A and device B establish a binding relationship, if they reconnect again, they can skip the pairing stage and directly use LTK for encryption.

[0144] 4) Establish a profile channel

[0145] After pairing is completed, device A and device B establish a profile channel (also called a profile connection) based on the required profile.

[0146] It should be noted that when device A and device B have completed pairing and binding, and have not unbound (the stored key data has not been cleared), when device A and device B are subsequently connected, the two will no longer be paired and bound, and a physical link and a profile channel can be directly established to achieve Bluetooth connection.

[0147] The following is a detailed description of the connection method for the wearable device provided in the embodiment of the present application.

[0148] Scenario 1:

[0149] An embodiment of the present application provides a connection method for a wearable device. In this embodiment, when a smart watch has established a Bluetooth connection with a mobile phone, when the mobile phone enters a preset geo-fencing and there are trusted devices around the mobile phone, the smart watch can establish a Bluetooth connection with the trusted device without the user disconnecting the smart watch from the mobile phone or releasing the binding relationship between the two. The following is a detailed description with reference to the accompanying drawings.

[0150] For example, Figure 6 FIG. 1 is a flow chart of a connection method for a wearable device provided in an embodiment of the present application. Figure 6 As shown, the method includes:

[0151] S101. When the smart watch and the mobile phone have established a Bluetooth connection (also called the first connection), the mobile phone determines that the mobile phone has entered the target geo-fence based on the information of at least one preset geo-fence and the device information in the trust ring, and that a trusted large-screen device exists in the target geo-fence.

[0152] The preset geo-fence is information used to characterize the preset geographic area. Geofence is a new application of location based services (LBS), which is to use a virtual fence to enclose a virtual geographic boundary. When the mobile phone moves from outside the geo-fence to inside the geo-fence (i.e., entering the geo-fence) or from inside the geo-fence to outside the geo-fence (i.e., leaving the geo-fence), the corresponding service is triggered. For example, when an electronic device enters the geo-fence of a high-voltage power line, the corresponding management system will send a notification or warning to the electronic device.

[0153] The target geofence is any one of at least one preset geofence. Optionally, the mobile phone can pre-set and save information of one or more geofences, which are geofences corresponding to places where the user may connect the mobile phone and the large-screen device at the same time. For example, the preset geofence can be the geofence corresponding to the user's home, the geofence corresponding to the user's company, etc. When the smart watch and the mobile phone have established a Bluetooth connection, the mobile phone determines whether the mobile phone has entered a preset geofence (called the target geofence) based on the current location and the information of these preset geofences. If so, the mobile phone determines whether there is a trusted device in the target geofence based on the device information in the trust ring.

[0154] Optionally, the mobile phone can obtain historical Bluetooth scanning information, and determine whether there is a trusted device in the target geographic fence based on the historical Bluetooth scanning information. The historical Bluetooth scanning information represents the information of the terminal devices scanned and discovered by the mobile phone's Bluetooth device in the target geographic fence during the historical time period. Optionally, the historical Bluetooth scanning information may include the scanning time, scanning location, and device information of the terminal devices scanned and discovered by the mobile phone when scanning and discovering the terminal device. The device information of the terminal device scanned and discovered by the Bluetooth device may include, for example, a MAC address, a device name, etc. The mobile phone can determine which terminal devices the mobile phone has scanned and discovered in the target geographic fence during the historical time period based on the historical Bluetooth scanning information, and then determine whether there is a trusted device in the target geographic fence based on the device information in the trust ring. Specifically, the mobile phone can compare the historical Bluetooth scanning information with the device information in the trust ring to confirm whether the devices scanned by the mobile phone in the historical time period include the devices in the trust ring. If so, it is determined that there is a trusted device in the target geographic fence. In this implementation, the mobile phone can quickly determine whether there is a trusted device in the target geographic fence based on the historical Bluetooth scanning information, and save the power consumption of the mobile phone.

[0155] Optionally, after determining that it has entered the target geographic fence, the mobile phone can also actively scan and discover surrounding devices, obtain information about the surrounding devices, and compare the information about the surrounding devices with the device information in the trust ring to determine whether there are trusted devices in the target geographic fence.

[0156] Optionally, the mobile phone can also obtain device information and location information of each device in the trust ring from the cloud server to determine whether there is a trusted device in the target geofence. The embodiment of the present application does not limit the specific method for the mobile phone to determine whether there is a trusted device in the target geofence.

[0157] The trusted device of the mobile phone within the target geographic fence can be considered as a device trusted by the user and will not affect the user's information security. In this embodiment, the trusted device is a large-screen device as an example for explanation.

[0158] For example, Figure 7 This is a schematic diagram of an application scenario of another wearable device connection method provided in an embodiment of the present application. Figure 7 As shown, the target geo-fence 101 is the geo-fence corresponding to the user's home. The user carries a mobile phone 102 and wears a smart watch 103, and the mobile phone 102 has established a Bluetooth connection with the smart watch 103. When the user carries the mobile phone 102 home, the mobile phone 102 determines that it has entered the target geo-fence 101, and according to the historical Bluetooth scanning information, it is determined that there is a trusted device in the target geo-fence 101, and the trusted device is a large screen device 104.

[0159] S102. The mobile phone sends a notification message to the smart watch, where the notification message is used to indicate that there is a trusted device (large-screen device) nearby.

[0160] Optionally, the notification information may carry device information of the trusted device. In the embodiment of the present application, the notification information may carry device information of the large-screen device. The device information of the large-screen device includes but is not limited to the MAC address of the large-screen device.

[0161] In one possible implementation, the smart watch may subscribe to notification information from the mobile phone in advance, so that when the mobile phone determines that it has entered the target geo-fence and there is a trusted device within the target geo-fence, the mobile phone sends notification information to the smart watch.

[0162] S103: The smart watch sends a discoverable broadcast (ie, a first broadcast message) to surrounding devices in response to the notification information. The discoverable broadcast is used for surrounding devices to discover the smart watch.

[0163] In one embodiment, after receiving the notification information, the smart watch can periodically send a discoverable broadcast to surrounding devices so that surrounding devices can find the smart watch at any time when they need to connect to the smart watch. For example, the smart watch can send a discoverable broadcast to surrounding devices every 5 seconds until the trusted device receives the discoverable broadcast.

[0164] In one embodiment, it can be found that the broadcast may carry the device information of the smart watch and the Bluetooth connection information (i.e., the first information). The device information of the smart watch may include but is not limited to the MAC address. The Bluetooth connection information is used to indicate that the smart watch has currently established a Bluetooth connection with the mobile phone. Optionally, the Bluetooth connection information may be represented by a predefined field.

[0165] It can be understood that when the discoverable broadcast carries the device information of the smart watch, the smart watch can send a discoverable broadcast to all surrounding devices in response to the notification information, or it can send a discoverable broadcast to the large-screen device based on the device information of the large-screen device carried in the notification information, that is, the device information (such as MAC address) of the large-screen device carried in the discoverable broadcast can be carried. The smart watch sends a discoverable broadcast to the large-screen device. After other devices receive the discoverable broadcast, if they determine that the MAC address carried in the broadcast message is inconsistent with their own MAC address, they will discard the discoverable broadcast message and will not continue to parse it. In this way, the disturbance of the smart watch to other surrounding devices can be reduced, the power consumption of surrounding devices can be saved, and the user experience can be improved.

[0166] S104: The large-screen device receives the discoverable broadcast sent by the smart watch.

[0167] Optionally, the large-screen device can automatically receive the discoverable broadcast sent by the smart watch based on the communication mechanism preset in the Bluetooth protocol.

[0168] S105. In response to a scan and discover instruction input by the user on the large-screen device, the large-screen device scans and discovers the smart watch, and obtains and displays device information of the smart watch.

[0169] The scan discovery instruction is used to instruct the large-screen device to perform scan discovery. Optionally, after the user starts the large-screen device, the user can open an APP (such as a sports APP) in the large-screen device that needs to interact with the smart watch, and enter the scan discovery instruction through the APP, for example, click Add Device Card in the interface for managing Bluetooth connected devices in the sports APP.

[0170] For example, Figure 8 This is a schematic diagram of an interface provided in an embodiment of the present application. Figure 8 As shown in FIG. 4( a ), the large screen device starts the sports APP and displays the device interface 403 of the APP. The device interface 403 includes an add device card 404, and the user can select the add device card 404 through the remote control to input a scan discovery instruction.

[0171] It can be understood that although in step S103, the discoverable broadcast sent by the smart watch to the large-screen device can carry the device information of the smart watch (such as the MAC address), after the user enters the scan discovery command, the large-screen device can further obtain more device information from the smart watch, for example, one or more of the device name and device type of the smart watch, so as to display this information in the interface.

[0172] Specifically, in response to the scan discovery instruction input by the user, the large-screen device initiates a scan request to the smart watch. After receiving the scan request, the smart watch sends a scan response packet to the large-screen device in response. The scan response packet includes the device information of the smart watch. After receiving the scan response packet, the large-screen device displays the device information of the smart watch in the interface. For example, the interface of the large-screen device scanning and discovering the smart watch can be as follows: Figure 8 Interface 405 shown in Figure (b) .

[0173] It should be noted that since the discoverable broadcast is sent to surrounding devices only after the smart watch receives the notification information, when the discoverable broadcast sent by the smart watch to the large-screen device carries the device information of the smart watch and the Bluetooth connection information, if the large-screen device receives the discoverable broadcast, it means that the large-screen device can confirm the current application scenario based on the device information and Bluetooth connection information of the smart watch: the smart watch is connected to the mobile phone, and the large screen is a trusted device. In this scenario, the large-screen device can automatically trigger the scan and discovery operation by scanning and discovering the smart watch without being triggered by the user's scan and discovery instruction. After automatically scanning and discovering the smart watch, the large-screen device can display the device information of the smart watch in the interface in the form of a pop-up window, and ask the user whether to establish a connection with the smart watch.

[0174] In short, step S105 can also be replaced by: the large-screen device responds to the discoverable broadcast, scans and discovers the smart watch according to the Bluetooth connected information in the discoverable broadcast, and obtains and displays the device information of the smart watch. Optionally, the device information of the smart watch can be displayed in the form of a pop-up window (also called the second interface). In this way, the user does not need to manually trigger the scan discovery, which simplifies the user operation and improves the user experience.

[0175] For example, Fig. 9 As shown, the second interface can be shown as 901, and the smart watch device information can be displayed in a pop-up window 902.

[0176] S106. In response to the connection instruction 1 input by the user, the large-screen device establishes a physical link with the smart watch according to the device information of the smart watch.

[0177] The connection instruction 1 is used to instruct the large-screen device to establish a connection with the smart watch. Optionally, the large-screen device may display a connection control for inputting a connection instruction while displaying the device information of the smart watch, and the user may input the connection instruction 1 through the connection control.

[0178] For example, Figure 8 As shown in Figure (b) in the figure, the user can select Figure 8 In the interface 405 shown in FIG. (b), the connection control 407 in the card 406 of the smart watch a is used to input the connection instruction 1. Of course, the user can also input the connection instruction 1 by voice input or the like, and the embodiment of the present application does not make any limitation to this.

[0179] After receiving the connection instruction 1, the large-screen device establishes a physical link with the mobile phone.

[0180] S107. The large-screen device displays a pairing confirmation interface.

[0181] Specifically, after the large-screen device establishes a physical link with the smart watch, a pairing confirmation interface is displayed on the screen, and the pairing confirmation interface includes an inquiry message asking the user whether to confirm pairing with the smart watch. The inquiry message in the pairing confirmation interface can be displayed in a variety of forms, such as a pop-up window, a capsule, a card, or a floating window, etc., and the embodiments of the present application do not impose any restrictions on this.

[0182] Exemplarily, the confirmation pairing interface of the large-screen device may be as follows: Figure 8 The interface 408 shown in FIG. (c) in FIG. 408 includes a pop-up window 409. The pop-up window 409 includes a confirmation control 410 and a cancel control 411.

[0183] S108. In response to the user inputting a confirmation pairing instruction 1 in the confirmation interface of the large-screen device, the large-screen device sends a pairing request to the smart watch.

[0184] The confirmation pairing instruction 1 is used to instruct the large-screen device to initiate a pairing request to the smart watch. For example, Figure 8 As shown in FIG. 4( c), the user may, for example, click on the confirmation control 410 in the pop-up window 409 to input the confirmation pairing instruction 1. After the user inputs the confirmation pairing instruction 1, the large-screen device may display the first pairing interface 412, such as Figure 8 As shown in Figure (d).

[0185] In some embodiments, the large-screen device may not display the pairing confirmation interface, and does not require the user to enter a pairing confirmation command. After establishing a physical link with the smart watch, the large-screen device directly sends a pairing request to the smart watch. In other words, the "response to the user entering the pairing confirmation command 1 in the confirmation interface" in the above steps S107 and S108 may not be executed, and after step S105 is completed, the "large-screen device sends a pairing request to the smart watch" in step S108 is directly executed. In this way, user operations are further simplified and user experience is improved.

[0186] S109: In response to the pairing request of the large-screen device, the smart watch displays a pairing request interface.

[0187] Specifically, the smartwatch displays a pairing request interface according to the pairing request sent by the large-screen device. The pairing request interface includes inquiry information asking the user whether to accept the pairing request of the large-screen device. The inquiry information in the pairing request interface can be displayed in a variety of forms, such as a pop-up window, a capsule, a card, or a floating window, etc., and the present embodiment of the application does not impose any limitation on this. In one embodiment, the pairing request interface can be displayed with Figure 5 The interface 501 shown in (a) of FIG. 1 is similar to the interface 501 shown in FIG. 1 , except that the schematic diagram of the device connected to the smart watch in the pairing request interface can be a schematic diagram of a large-screen device instead of a schematic diagram of a mobile phone in the interface 501 .

[0188] S110 . In response to the user inputting an acceptance pairing instruction 1 in the pairing request interface of the smart watch, the smart watch automatically disconnects the Bluetooth connection with the mobile phone.

[0189] Specifically, the smartwatch can determine that there is a trusted device of the mobile phone nearby based on the notification information, and determine that the user agrees to establish a connection with the trusted device (large-screen device) based on the acceptance pairing instruction 1 input by the user, so the smartwatch can automatically disconnect the Bluetooth connection with the mobile phone. Automatic disconnection means that the smartwatch automatically disconnects the Bluetooth connection with the mobile phone without the user performing a disconnection operation (for example, clicking to delete the device, canceling pairing, etc.).

[0190] Optionally, the smart watch can disconnect the physical link with the watch and release the binding relationship with the mobile phone.

[0191] Optionally, the smart watch may only disconnect the physical link with the mobile phone without releasing the binding relationship with the mobile phone. In this embodiment, the smart watch receives the notification information sent by the mobile phone, so it can be determined that the current application scenario is: the smart watch is connected to the mobile phone, and there is a trusted device in the current surrounding environment-a large-screen device. In this scenario, if the smart watch receives the acceptance pairing instruction 1 of the user's consent to pair with the large-screen device, it can be confirmed that even if the smart watch does not release the binding relationship with the mobile phone, it will not affect the security of the user's information. Therefore, the smart watch can only disconnect the physical link with the mobile phone, so that when the smart watch is reconnected to the mobile phone later, there is no need to enter the pairing stage, and the user does not need to perform operations related to the pairing stage (such as pairing confirmation operations), saving the execution programs of the smart watch and the mobile phone, simplifying user operations, and improving user experience.

[0192] It should be noted that, in some other embodiments, “the smart watch automatically disconnects the Bluetooth connection with the mobile phone” can also be executed at other times, for example, when a pairing request sent by a large-screen device is received. This application does not make any limitation on this.

[0193] S111. The smart watch is paired with the large-screen device and a profile channel is established.

[0194] The accept pairing instruction 1 is used to indicate the acceptance of the pairing request of the large-screen device. Optionally, the pairing request interface may include an accept pairing control, such as Figure 5 In 502 shown in (a) of FIG. 1 , the user can click the accept pairing control 502 to input the accept pairing instruction 1. Of course, the user can also input the accept pairing instruction 1 in other ways, such as voice input, key selection, etc., and the embodiment of the present application does not make any limitation on this.

[0195] During the process of pairing the smart watch with the large-screen device and establishing a profile channel, the large-screen device may display a second pairing interface 413, such as Figure 8 As shown in Figure (e) in FIG. 1 , the smart watch can display a third pairing interface, and the third pairing interface can be Figure 5 The interface 503 shown in (b) of FIG. 1 is similar to the interface 503 shown in FIG. 1 , except that the schematic diagram of the device connected to the smart watch in the third pairing interface can be a schematic diagram of a large-screen device, rather than a schematic diagram of a mobile phone in interface 503, and the details are not repeated here.

[0196] Optionally, in this embodiment, the profile channels established between the smart watch and the large-screen device may include HFP channels, A2DP channels, and SPP channels. After the smart watch is paired with the large-screen device and these channels are established, the smart watch and the large-screen device complete the Bluetooth connection. After the Bluetooth connection is completed, the interface of the large-screen device can be as follows: Figure 8 As shown in Figure (f).

[0197] It should be noted that when the connection between the large-screen device and the smart watch is other connections, such as a Wi-Fi connection, pairing is not required and the above pairing process may not be performed.

[0198] In this embodiment, the schematic diagram of the connection change between the smart watch and the mobile phone and the large-screen device can be seen in Fig.10 .like Fig.10 As shown in (a) of FIG. 1 , before executing the method provided in this embodiment, the mobile phone and the smart watch establish a Bluetooth connection. Optionally, the Bluetooth connection between the mobile phone and the smart watch may include an HFP channel, an A2DP channel, and an SPP channel. Afterwards, the smart watch, the mobile phone, and the large-screen device execute the above steps S101 to S111, the smart watch disconnects the Bluetooth connection with the mobile phone, and establishes a Bluetooth connection with the large-screen device, as shown in FIG. Fig.10 Optionally, the Bluetooth connection between the smart watch and the large-screen device may also include an HFP channel, an A2DP channel, and an SPP channel.

[0199] As described above, in general, when a wearable device has established a connection with a terminal device, the wearable device is in a paired state. Considering the security of user information, it will no longer send discoverable broadcasts to the surroundings. Only when the user disconnects the connection and releases the binding relationship between the two, will the wearable device be triggered to send discoverable broadcasts to the surroundings again. In this embodiment, when the mobile phone and the smart watch have established a Bluetooth connection, when the mobile phone detects that it has entered the target geographic fence and there is a trusted large-screen device in the target geographic fence, the mobile phone sends a notification message to the smart watch. That is to say, the mobile phone notifies the smart watch after identifying the trusted large-screen device, so that the smart watch can know the current application scenario: the smart watch has established a connection with the mobile phone, and there is a trusted device of the mobile phone-a large-screen device around. In this scenario, if the smart watch does not release the binding relationship with the mobile phone, re-establishing a connection with the large-screen device will not affect the security of user information. Therefore, there is no need for the user to perform the relevant operations of disconnection and unbinding. The smart watch automatically sends discoverable broadcasts to the surrounding devices, so that the smart watch can be scanned and discovered by the large-screen device, and then establishes a Bluetooth connection with the trusted large-screen device with a higher security. In this way, the user is saved from performing the operations of disconnection and unbinding, and the user experience is improved. Furthermore, when the smart watch receives a pairing request from the large-screen device, since the smart watch can determine that the large-screen device is a trusted device of the mobile phone based on the notification information, the smart watch does not need to display an interface to ask the user, nor does it require the user to manually disconnect the connection. It can automatically disconnect from the mobile phone and establish a connection with the large-screen device. In this way, not only is it possible to switch the Bluetooth connection of the smart watch from the mobile phone to the large-screen device, but the user does not need to perform the operations of disconnection and unbinding, which simplifies user operations and further improves the user experience.

[0200] As analyzed above, the large-screen device is a trusted device of the mobile phone, so the smart watch can establish Bluetooth connections with the mobile phone and the large-screen device at the same time without affecting the security of user information. Fig.11 In another embodiment, after receiving the pairing request sent by the large-screen device, the smart watch may not disconnect from the large-screen device, but directly respond to the pairing request and display the pairing request interface. In other words, the above step S110 may not be executed, and after step S109 is executed, step S111 is directly executed. In this way, the smart watch establishes a second Bluetooth connection with the large-screen device while maintaining a Bluetooth connection with the mobile phone.

[0201] Optionally, in this embodiment, the profile channel established between the smart watch and the large-screen device may only include the SPP channel. That is, step S111 is: in response to the user inputting the acceptance pairing instruction 1 in the pairing request interface, the smart watch is paired with the large-screen device and the SPP channel is established.

[0202] Specifically, as mentioned above, the smart watch can know that the current smart watch has established a connection with the mobile phone; the large-screen device can also know that the smart watch has established a connection with the mobile phone by discovering the Bluetooth connection information in the broadcast. In the case where the smart watch and the mobile phone have established a connection, the Bluetooth connection between the large-screen device and the smart watch is generally only used to transmit data. Therefore, when establishing a profile channel, the smart watch or the large-screen device can initiate a request to the other end, and the two perform authentication and encryption, and after determining the current application scenario, only establish an SPP channel. This can simplify the process of establishing a connection between the large-screen device and the smart watch, save profile channels, and save power consumption and resources for both.

[0203] In this embodiment, the schematic diagram of the connection change between the smart watch and the mobile phone and the large-screen device can be seen in Fig.12 .like Fig.12 As shown in Figure (a), before executing the method provided in this embodiment, the mobile phone and the smart watch have established a Bluetooth connection. Optionally, the Bluetooth connection between the mobile phone and the smart watch may include an HFP channel, an A2DP channel, and an SPP channel. Afterwards, the smart watch, the mobile phone, and the large-screen device execute the method in this embodiment, and the smart watch maintains a Bluetooth connection with the mobile phone and establishes a Bluetooth connection with the large-screen device, such as Fig.12 As shown in Figure (b) in FIG. Optionally, the Bluetooth connection between the smart watch and the large-screen device may only include the SPP channel.

[0204] In this embodiment, similar to the previous embodiment, in this embodiment, when the smart watch is in a paired state, when the mobile phone connected to the smart watch enters the target geographic fence and there is a trusted device of the mobile phone, the smart watch can send a discoverable broadcast to the surroundings, so that the large-screen device can discover the smart watch without the user having to perform related operations of disconnection and unbinding, thereby simplifying user operations. Furthermore, when the smart watch receives a pairing request from the large-screen device, since the smart watch can determine that the large-screen device is a trusted device of the mobile phone based on the notification information, it will not affect the security of user information. Therefore, the smart watch does not disconnect from the mobile phone, and directly establishes a second Bluetooth connection with the large-screen device, thereby facilitating the user to interact with both the mobile phone and the large-screen device through the smart watch at the same time, thereby improving the user experience.

[0205] It should be noted that Figure 6 and Fig.11 The embodiment shown is described by taking the example of a user operating on the large-screen device side to discover a smart watch and establish a Bluetooth connection between the two. In some other embodiments, the user can also operate on the smart watch side to establish a Bluetooth connection between the two. For details, see Fig.13 , the above steps S105 to S111 may also be replaced by the following steps:

[0206] S121. The smart watch displays device information of the large-screen device according to the notification information.

[0207] Specifically, as described above, the notification information may include the device information of the large-screen device, and thus the smartwatch may display an interface (also referred to as a first interface) containing the large-screen device information according to the device information of the large-screen device. Optionally, the interface may include a connection control (also referred to as a first control) for the user to input a connection instruction.

[0208] The form of the first interface and the first control may be similar to the form of the device information and connection controls of the smart device displayed in the large-screen device, and will not be described in detail.

[0209] S122. In response to the user inputting the connection instruction 2, the smart watch establishes a physical link with the large-screen device according to the device information of the large-screen device.

[0210] The connection instruction 2 is used to instruct the smart watch to establish a connection with the large-screen device. Optionally, the user can input the connection instruction 2 by clicking the connection control in the interface displayed on the watch.

[0211] S123. The smart watch displays a pairing confirmation interface.

[0212] After the smart watch establishes a physical link with the large-screen device, a pairing confirmation interface is displayed on the screen. The pairing confirmation interface of the smart watch can be similar to the pairing confirmation interface of the large-screen device, and will not be described in detail.

[0213] S124: In response to the user inputting a confirmation pairing instruction 2 in the confirmation interface of the smart watch, the smart watch automatically disconnects the Bluetooth connection with the mobile phone.

[0214] The confirmation pairing instruction 2 is used to instruct the smart watch to initiate a pairing request with the large-screen device. After the smart watch receives the confirmation pairing instruction 2 from the user, it automatically disconnects the Bluetooth connection with the mobile phone. Similar to the above step S110, in this embodiment, the smart watch can disconnect the physical link with the watch and release the binding relationship with the mobile phone, or it can only disconnect the physical link with the mobile phone without releasing the binding relationship with the mobile phone. The specific beneficial effects are not repeated here.

[0215] S125. The smart watch sends a pairing request to the large-screen device.

[0216] S126. In response to the pairing request sent by the smart watch, the large-screen device displays a pairing request interface.

[0217] S127 . In response to the user inputting an acceptance pairing instruction 2 in the pairing request interface of the large-screen device, the smart watch is paired with the large-screen device and a profile channel is established.

[0218] same Figure 6 In the embodiment shown, in this embodiment, the smart watch may not disconnect the Bluetooth connection with the mobile phone before pairing and connecting with the large-screen device, that is, maintain the Bluetooth connection. For details, please refer to the above embodiment and will not be repeated here.

[0219] In this embodiment, the process of establishing a connection between the smart watch and the large-screen device is similar to the process of steps S106 to S111 above, except that in this embodiment, the user inputs a connection instruction and confirms a pairing instruction on the smart watch side, and inputs an acceptance pairing instruction on the large-screen device side. In other words, the user triggers the Bluetooth connection between the smart watch and the large-screen device on the smart watch side.

[0220] It is worth noting that, in addition to Figure 6 and Fig.11 In addition to the beneficial effects described above, in this embodiment, the smart watch receives notification information sent by the mobile phone, which may include device information of the large-screen device. Therefore, the smart watch can directly display the device information without scanning and discovering the large-screen device, and without the user manually triggering the scan and discovery, further simplifying user operations and improving user experience.

[0221] Scenario 2:

[0222] Another embodiment of the present application also provides a connection method for a wearable device. In this embodiment, when a smart watch has established a Bluetooth connection with a mobile phone, a second Bluetooth connection between the smart watch and the large-screen device can be achieved through cloud pairing. The following is a detailed description with reference to the accompanying drawings.

[0223] For example, Fig.14 A flowchart of another example of a method for connecting a wearable device provided in an embodiment of the present application is shown in FIG. Fig.14 As shown, the method includes:

[0224] S201: When a Bluetooth connection is established between the smart watch and the mobile phone, and the mobile phone is logged into a first user account, the mobile phone uploads device information and a pairing key of the smart watch to a server through the first user account.

[0225] The server may be a cloud server. It is understood that when the mobile phone logs in to the first user account, the device information, connection information, etc. of the wearable device currently connected to it may be uploaded to the cloud server. The connection information refers to information used by other devices to establish a short-range wireless communication connection with the wearable device. When the short-range wireless communication connection is a Bluetooth connection, the connection information may be a pairing key, etc.

[0226] The process of step S201 is also referred to as the mobile phone synchronizing the information of the smart watch with the cloud.

[0227] S202: When the first user account is logged in to the large-screen device, in response to the user viewing the surrounding wireless communication devices in the large-screen device, the large-screen device obtains device information and pairing key and other information of the smart watch from the server according to the first user account.

[0228] That is to say, the large-screen device and the mobile phone use the same user account (first user account). When the large-screen device is logged in (that is, online), if the user performs an operation to view surrounding wireless communication devices, the large-screen device can obtain the device information and pairing key of the smart watch from the cloud server according to the first user account. Optionally, the operation of viewing surrounding wireless communication devices can, for example, turn on the Bluetooth switch for the user, or, when the Bluetooth switch is turned on, the user opens a sports APP and views the device.

[0229] S203. The large-screen device displays device information of the smart watch.

[0230] The device information of the smart watch includes but is not limited to one or more of the device name, device type, MAC address, etc. of the smart watch.

[0231] Optionally, the large-screen device can display the device information of the smart watch on the device interface (also referred to as the third interface) of the sports APP in response to the user opening the sports APP and viewing the operation of the device. The device interface may include a control for inputting a connection instruction (also referred to as the third control). Exemplarily, the device interface may be as follows: Fig.15 As shown in 1501 in FIG. 1 , the device information of the smart watch may be displayed in a device information card 1502. The device information card 1502 may include a connection control 1503, which is used for the user to input a connection instruction.

[0232] S204: In response to the user inputting connection instruction 3 in the large-screen device, the large-screen device establishes a physical link with the smart watch according to the device information of the smart watch.

[0233] Specifically, the connection instruction 3 is used to instruct the large-screen device to establish a connection with the smart watch. The user can select Fig.15 The connection control 1503 in the interface 1501 is used to input the connection instruction 3.

[0234] S205: The large-screen device sends a pairing request to the smart watch.

[0235] S206: In response to the pairing request, the smart watch displays a pairing request interface.

[0236] S207 . In response to the user inputting an acceptance pairing instruction 3 on the pairing request interface of the smart watch, the large-screen device pairs with the smart watch according to the pairing key and establishes an SPP channel.

[0237] The process of steps S204 to S207 is similar to the process of steps S108 to S111, and will not be described in detail. It should be noted that in step S207, the large-screen device has already learned the pairing key of the smart watch. Therefore, in the pairing interface, the large-screen device and the smart watch no longer need to generate a pairing key based on random numbers, pin codes, MAC addresses and other information, which simplifies the pairing process.

[0238] The process of steps S202 to S207 is also referred to as the large-screen device obtaining the information of the smart watch from the cloud and pairing and connecting, which is referred to as cloud pairing.

[0239] In this embodiment, the connection change diagram between the smart watch, the mobile phone, and the large-screen device can be as follows: Fig.16 See Fig.16 In Figure (a), before executing the method provided in this embodiment, the mobile phone establishes a Bluetooth connection with the smart watch. The Bluetooth connection between the mobile phone and the smart watch may include an HFP channel, an A2DP channel, and an SPP channel. Afterwards, the smart watch, the mobile phone, and the large-screen device execute the above steps S201 to S207. The smart watch maintains a Bluetooth connection with the mobile phone. At the same time, the large-screen device establishes a Bluetooth connection with the smart watch through cloud pairing. Fig.16 As shown in Figure (b) in the figure, the profile channel between the smart watch and the large-screen device can only include the SPP channel.

[0240] In this embodiment, when the mobile phone establishes a Bluetooth connection with the smart watch, the large-screen device obtains the device information and pairing key of the smart watch from the server to achieve connection with the smart watch. Since the large-screen device and the mobile phone log in to the same user account, the large-screen device is a device that the user can trust. The smart watch can simultaneously establish two Bluetooth connections with the mobile phone and the large-screen device, which will not affect the security of the mobile phone and the large-screen device, and there is no need to release the binding relationship with the mobile phone, simplifying user operations, and facilitating users to interact with both the mobile phone and the large-screen device through the smart watch at the same time, thereby improving user experience. Moreover, the large-screen device obtains and displays the device information of the smart watch through the cloud server, and the user does not need to scan and discover the device information of the smart watch through the large-screen device or the smart watch, so it can further simplify operations and improve user experience. Moreover, the large-screen device can obtain the pairing key of the smart watch through the cloud service, and there is no need to negotiate the pairing key with the smart watch, simplifying the pairing process. In addition, the mobile phone synchronizes the information cloud of the smart watch only when the Bluetooth connection is established with the smart watch. Therefore, when the large-screen device is paired with the smart watch cloud, the mobile phone and the smart watch are still in a Bluetooth connection state. In this case, the Bluetooth connection between the smart watch and the large-screen device is generally only used to transmit data. Therefore, when establishing a profile channel, the large-screen device and the smart watch only establish an SPP channel. This can simplify the process of establishing a connection between the large-screen device and the smart watch, save profile channels, and save power consumption and resources of both.

[0241] Scenario 3:

[0242] The embodiment of the present application also provides a method for connecting a wearable device, which can be applied to application scenarios where a terminal device is connected to multiple wearable devices. For example, multiple users wear smart watches or sports bracelets, etc., and connect the smart watches or sports bracelets to a large-screen device for multi-person team fitness or games.

[0243] For example, Fig.17 This is a schematic diagram of an application scenario of another example of a connection method for a wearable device provided in an embodiment of the present application. Fig.17 As shown, the large-screen device is installed with a sports APP, which may include team fitness games, such as multiplayer racing games. Multiple users (team members) can wear smart watches respectively, and the smart watches are connected to the large-screen devices respectively. During the game, the sports data of the players are collected through the smart watches, and uploaded to the large-screen device based on the connection between the smart watches and the large-screen device. The large-screen device analyzes and compares the sports data of each team member, and outputs the game interface and game results.

[0244] The following describes the process of establishing connections between the large-screen device and each smart watch in this scenario.

[0245] For example, Fig.18 The following is a flow chart of another example of a method for connecting a wearable device provided in an embodiment of the present application. Fig.18 As shown, the method includes:

[0246] S301. In response to a user inputting a team formation instruction (also called a first instruction) on a large-screen device, the large-screen device sends a team formation BLE broadcast (also called a second broadcast message) to surrounding devices.

[0247] The team formation instruction is used to instruct the large-screen device to establish a connection with multiple wearable devices and form a team, which is to establish a game group or a fitness group. Optionally, the team formation instruction can carry the number of team members, that is, the number of wearable devices in the group, etc.

[0248] Optionally, BLE broadcast is used to request multiple wearable devices around to establish a Bluetooth connection with the large-screen device and join the group. The BLE broadcast may carry one or more of the device information, game information, scene information, number of team members, etc. of the large-screen device. Among them, the device information of the large-screen device may include, for example, one or more of the name of the large-screen device, the MAC address of the large-screen device, the manufacturer information of the large-screen device, etc. Game information may include the name of the game in progress, etc. Scene information is used to characterize the application scenario in which multiple wearable devices establish a connection with the large-screen device. The scene information may include team games or team fitness, etc.

[0249] For example, Fig.19 An example of an interface diagram of playing a team fitness game on a large-screen device is provided in an embodiment of the present application, such as Fig.19 As shown in FIG. 1 (a), the sports interface 1901 of the sports APP may include an option 1902 for a multiplayer running game. When the user selects the option 1902 for the multiplayer running game through the remote control, the multiplayer running game interface 1903 is entered, as shown in FIG. Fig.19 As shown in Figure (b) in the figure. The interface may include multiple team game controls 1904, and the user selects the corresponding team control 1904 according to the number of team members required. Taking the user selecting a 4-player team game as an example, in response to the user's selection, the large-screen device starts sending a team BLE broadcast to surrounding devices.

[0250] S302, each smart watch ( Fig.18 In the figure, smart watches a, b, c, and d are taken as examples. After receiving the team BLE broadcast sent by the large-screen device, the inquiry information and prompt information are displayed according to the team BLE broadcast.

[0251] The inquiry information is used to ask the user whether to agree to establish a connection between the smart watch and the large-screen device and join the team. The prompt information is used to prompt that after the smart watch and the large-screen device are connected, the data of the smart watch will be transmitted to the large-screen device.

[0252] In a specific embodiment, after the smart watch receives the team BLE broadcast sent by the large-screen device, the interface diagram can be as follows: Fig. 20 As shown in FIG. (a) of FIG. 2 , the interface includes inquiry information 2001 and prompt information 2002. The inquiry information 2001 includes an approval control 2003 and a rejection control 2004.

[0253] S303: In response to each user inputting a connection consent and team formation instruction in the interface of the smart watch, each smart watch sends a connection consent message and a team formation consent message to the large-screen device.

[0254] The connection consent message is used to indicate that the smartwatch agrees to establish a connection with the large-screen device. The team formation consent message indicates that the smartwatch agrees to connect and form a team, that is, agrees to join the group.

[0255] It can be understood that in this embodiment, the connection agreement message and the team agreement message are triggered by a user instruction-agree to connect and team up instruction. In other embodiments, the connection agreement message and the team agreement message can also be triggered by two instructions respectively. In addition, the connection agreement message and the team agreement message can be two separate messages, which are sent to the large-screen device separately, or they can be two parts of the same message, which are sent to the large-screen device through one message. The embodiment of the present application does not impose any limitation on this.

[0256] For example, the user can click Fig. 20 The consent control 2003 in Figure (a) inputs the consent to connect and form a team instruction.

[0257] S304: The large-screen device establishes physical links with each smart watch in response to the connection agreement message and the teaming agreement message.

[0258] S305: The large-screen device is paired with each smart watch and an SPP channel is established, and the smart watch is added to the group.

[0259] Specifically, after the physical link is established, the large-screen device sends a pairing request to the smart watch, and the large-screen device receives the pairing request, and the two enter the pairing stage. After the pairing is completed, the two establish an SPP channel. At this point, the large-screen device and the smart watch complete the establishment of a Bluetooth connection. After the Bluetooth connection is completed, the interface of the smart watch can be as follows Fig. 20 As shown in Figure (b) in FIG. 1 , the interface of the large-screen device can display the information of the team members, that is, the connected smart watches, such as Fig.19 As shown in Figure (c).

[0260] After the Bluetooth connection is established, the large-screen device adds the smart watch to the group.

[0261] S306. Each smart watch collects the user's exercise data.

[0262] Specifically, each smart watch can collect the user's exercise data in real time. Optionally, the user's exercise data may include but is not limited to one or more of the user's speed, number of steps, heart rate, blood oxygen level, blood pressure, etc.

[0263] S307: In response to the user inputting a start game instruction (also referred to as a second instruction) in the large-screen device, the large-screen device obtains motion data from the smart watch based on the SPP channel.

[0264] After the user inputs the command to start the game, the large-screen device can obtain motion data from the smart watch based on the established SPP channel, and then display games or fitness content based on the motion data.

[0265] In this embodiment, a team BLE broadcast is sent to surrounding devices through a large-screen device, and the smart watch displays prompt information and inquiry information in response to the team BLE broadcast. The user enters the consent connection and team command in the interface of the smart watch, indicating that the user trusts the large-screen device, that is, the large-screen device is a device that the user can trust, so the smart watch directly establishes a Bluetooth connection with the large-screen device, so that the large-screen device can establish a Bluetooth connection with multiple smart watches at the same time, so that multiple smart watches can send data to the large-screen device at the same time to meet the user's usage needs in scenarios such as team games and improve user experience. In addition, since the smart watch and the large-screen device only transmit data in the team game or fitness scenario, the profile channel between the large-screen device and the smart watch can only include the SPP channel, which can not only save the resources and power consumption of the smart watch and the large-screen device, but also further reduce the risk of user information loss, that is, further improve the security of user information. At the same time, by displaying prompt information and inquiry information in the interface of the smart watch, the user is informed of information such as the usage scenario, so as to increase interaction with the user, improve the security of user information, and improve user experience.

[0266] In another embodiment, before multiple smart watches establish a connection with the large-screen device, if the smart watch has established a Bluetooth connection with other terminal devices (such as a mobile phone), the smart watch can maintain the Bluetooth connection with the other terminal device and establish a second Bluetooth connection with the large-screen device. In this case, the smart watch can only establish an SPP channel with the large-screen device. In this way, it is convenient for users to interact with both the mobile phone and the large-screen device through the smart watch, which improves the user experience. In addition, establishing only an SPP channel between the smart watch and the large-screen device can save resources and power consumption of the smart watch and the large-screen device.

[0267] In this embodiment, the process of establishing a Bluetooth connection between the large-screen device and multiple wearable devices can be as follows: Fig.21As shown. Fig.21 In Figure (a), the wearable devices include smart watch a, smart watch b, smart watch c and smart watch d. Before executing the method provided in this embodiment, smart watch a has established a Bluetooth connection with the mobile phone. Optionally, the Bluetooth connection between the mobile phone and smart watch a may include an HFP channel, an A2DP channel and an SPP channel, etc. Afterwards, each smart watch, mobile phone and large-screen device executes the above steps to establish a Bluetooth connection with the large-screen device respectively, wherein smart watch a maintains a Bluetooth connection with the mobile phone, such as Fig.21 As shown in Figure (b) in FIG. Optionally, the Bluetooth connection between each smart watch and the large-screen device may only include an SPP channel.

[0268] In another embodiment, before the user inputs the team formation instruction in the large-screen device, if the large-screen device has established a Bluetooth connection with a smart watch, the smart watch confirms that it has established a connection with the large-screen device after receiving the BLE broadcast sent by the large-screen device. The smart watch maintains the connection and displays an inquiry message according to the BLE broadcast, asking the user whether to agree to form a team, that is, whether to agree to join the group. After the user inputs the team formation agreement instruction, the smart watch sends a team formation agreement message to the large-screen device. After receiving the team formation agreement message sent by the smart watch, the large-screen device adds the smart watch to the group.

[0269] It should be noted that in the above embodiments, the short-range wireless communication connection is a Bluetooth connection, and the profile channel of the classic Bluetooth device is used as an example for explanation. Based on the classic Bluetooth device, the data transmission channel between the wearable device and the terminal device can be an SPP channel. In some other embodiments, the Bluetooth device of the wearable device can also be a BLE Bluetooth device, or a dual-mode Bluetooth device, etc. In this case, it is also possible to establish a data transmission channel (i.e., a BLE data transmission channel) under its protocol based on the BLE Bluetooth device. In this way, for some wearable devices (such as sports bracelets, etc.) whose Bluetooth devices are BLE Bluetooth devices or dual-mode Bluetooth devices, the method provided in the embodiment of the present application is also applicable. Furthermore, the same is true for short-range wireless communication protocols of other communication protocols, which also have their own data transmission channels. When the transmission channel is established using the method provided in the embodiment of the present application, the transmission channel corresponding to the required function under the protocol is established.

[0270] In addition, for a wearable device that is a dual-mode Bluetooth device, when a connection is established with a large-screen device and a mobile phone at the same time through the method provided in the embodiment of the present application, a connection can be established with the mobile phone through a classic Bluetooth device, and a connection can be established with the large-screen device through a BLE Bluetooth device. Alternatively, a connection can be established with the large-screen device through a classic Bluetooth device, and a connection can be established with the mobile phone through a BLE Bluetooth device, which improves the flexibility of use and the applicability of the method.

[0271] The above describes in detail an example of a connection method for a wearable device provided in an embodiment of the present application. It is understandable that, in order to implement the above functions, the wearable device, the first terminal device, and the second terminal device include hardware and / or software modules corresponding to the execution of each function. It should be easily appreciated by those skilled in the art that, in combination with the units and algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application in combination with the embodiments, but such implementation should not be considered to exceed the scope of the present application.

[0272] The embodiment of the present application can divide the functional modules of the wearable device, the first terminal device and the second terminal device according to the above method example. For example, each function can be divided into various functional modules, such as a detection unit, a processing unit, a display unit, etc., or two or more functions can be integrated into one module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiment of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation.

[0273] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0274] The wearable device, the first terminal device, and the second terminal device provided in this embodiment are used to execute the connection method of the above-mentioned wearable device, and thus can achieve the same effect as the above-mentioned implementation method.

[0275] The hardware structure and software architecture of the wearable device, the first terminal device and the second terminal device provided in the embodiments of the present application are described below.

[0276] For example, Fig. 22 1 is a schematic diagram of a structure of a wearable device 100 provided in an embodiment of the present application. Fig. 22As shown, taking the wearable device 100 as a smart watch as an example, the wearable device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, a wireless communication module 150, an audio module 160, a speaker 160A, a microphone 160B, a button 170, a display screen 171, a sensor module 180, etc. The sensor module 180 may include an infrared light sensor 180A, a gyroscope sensor 180B, an acceleration sensor 180C, a touch sensor 180D, a photoplethysmo graphy (PPG) heart rate sensor 180E, an ambient light sensor 180F, etc.

[0277] It is understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the wearable device 100. In other embodiments of the present application, the wearable device 100 may include more or fewer components than shown in the figure, or combine certain components, or split certain components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0278] The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, etc. Among them, different processing units may be independent devices or integrated into one or more processors. The controller may generate an operation control signal according to the instruction opcode and the timing signal to complete the control of fetching and executing instructions.

[0279] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory.

[0280] In some embodiments of the present application, the processor 110 may send a discoverable broadcast (i.e., a first broadcast) to surrounding devices upon receiving a notification message sent by a terminal device. The notification message is used to indicate the presence of a trusted device in the surrounding area. The discoverable broadcast may carry device information of the wearable device 100 and Bluetooth connected information (i.e., the first information). The Bluetooth connected information is used to indicate that the wearable device 100 has currently established a Bluetooth connection with a certain terminal device.

[0281] The internal memory 121 can be used to store computer executable program codes, which include instructions. The internal memory 121 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as voice navigation, image playback function, etc.), etc. The data storage area may store data created during the use of the wearable device 100 (such as audio data, phone book, etc.), etc. In addition, the internal memory 121 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the wearable device 100 by running instructions stored in the internal memory 121 and / or instructions stored in a memory provided in the processor.

[0282] It is understandable that the interface connection relationship between the modules illustrated in the embodiment of the present application is only a schematic illustration and does not constitute a structural limitation on the wearable device 100. In other embodiments of the present application, the wearable device 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0283] The wearable device 100 can provide wireless communication solutions through modules such as the antenna 1, the wireless communication module 150, the modem processor and the baseband processor, including but not limited to wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication technology (NFC), infrared technology (IR) and other wireless communication solutions.

[0284] That is to say, the wireless communication module 150 can realize short-range wireless communication, or in other words, the wireless communication module 150 includes a short-range wireless communication module. In the embodiment of the present application, the wearable device 100 can perform short-range wireless communication with the terminal device based on the short-range wireless communication protocol through the wireless communication module 150. For example, a Bluetooth connection is established based on the Bluetooth protocol with a mobile phone, a large-screen device, etc. through the wireless communication module 150, and data is transmitted based on the Bluetooth connection. The wireless communication module 150 may include a Bluetooth device, and the Bluetooth device may be a classic Bluetooth device, a BLE Bluetooth device, or a dual-mode Bluetooth device. The embodiment of the present application does not impose any limitation on this.

[0285] Antenna 1 is used to transmit and receive electromagnetic wave signals. Each antenna in the wearable device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antenna. For example, the antenna can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0286] The wireless communication module 150 may be one or more devices integrating at least one communication processing module. The wireless communication module 150 receives electromagnetic waves via an antenna, modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 150 may also receive a signal to be sent from the processor 110, modulate the frequency of the signal, amplify the signal, and convert it into electromagnetic waves for radiation via the antenna.

[0287] The wearable device 100 implements the display function through a GPU, a display screen 171, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 171 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 110 may include one or more GPUs that execute program instructions to generate or change display information.

[0288] The infrared light sensor 180A is a sensor that uses infrared rays for data processing. It is used to sense certain characteristics of the surrounding environment. It can also be used to measure the heat emitted by the human body and detect movement.

[0289] The gyro sensor 180B can be used to determine the motion posture of the wearable device 100. In some embodiments, the angular velocity of the wearable device 100 around three axes (ie, x, y, and z axes) can be determined by the gyro sensor 180B. The gyro sensor 180B can be used to detect the motion state of the user.

[0290] The acceleration sensor 180C can detect the magnitude of acceleration of the wearable device 100 in various directions (generally three axes). When the wearable device 100 is stationary, the magnitude and direction of gravity can be detected. It can also be used to identify the posture of the wearable device and is applied to step counting, motion status feedback, etc.

[0291] The touch sensor 180D is also called a "touch panel". The touch sensor 180D can be set on the display screen 171, and the touch sensor 180D and the display screen 171 form a touch screen, also called a "touch screen". The touch sensor 180D is used to detect touch operations acting on or near it. The touch sensor 180D can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 171. In other embodiments, the touch sensor 180D can also be set on the surface of the wearable device 100, which is different from the position of the display screen 194, for example, it is set on the side of the dial of the smart watch.

[0292] The PPG heart rate sensor 180E is used to detect the intensity of reflected light after being absorbed by human blood and tissues, and to record the changes in blood vessel volume during the cardiac cycle to obtain the pulse waveform, and then calculate the heart rate based on the pulse waveform. The PPG heart rate sensor 180E is used to monitor the health of users.

[0293] The ambient light sensor 180F is used to sense the ambient light brightness. The wearable device 100 can adaptively adjust the brightness of the display screen 194 according to the perceived ambient light brightness. The ambient light sensor 180L can also be used to automatically adjust the white balance when taking pictures. The ambient light sensor 180F can also cooperate with a proximity light sensor (not shown in the figure) to detect whether the wearable device 100 is in a wearing state.

[0294] The structure of the first terminal device 200 is described below.

[0295] For example, Fig.23 2 is a schematic diagram of a structure of a first terminal device 200 provided in an embodiment of the present application. Taking the first terminal device 200 as a mobile phone as an example, Fig.23As shown, the first terminal device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a USB interface 230, a charging management module 240, a power management module 241, a battery 242, an antenna 2, an antenna 3, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, a sensor module 280, a button 290, a motor 291, an indicator 292, a camera 293, a display screen 294, and a subscriber identification module (SIM) card interface 295, etc. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, an air pressure sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity light sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, etc.

[0296] It is understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the first terminal device 200. In other embodiments of the present application, the first terminal device 200 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0297] The processor 210 may include one or more processing units, for example, the processor 210 may include an application processor, a modem processor, a GPU, an ISP, a controller, a memory, a video codec, a DSP, a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0298] The controller may be the nerve center and command center of the first terminal device 200. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0299] A memory may also be provided in the processor 210 for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory.

[0300] In an embodiment of the present application, the processor 210 can cooperate with other modules to determine, when a Bluetooth connection has been established between the wearable device and the first terminal device, that the first terminal device has entered the target geo-fence and that there is a trusted device within the target geo-fence based on information of at least one preset geo-fence and device information within the trust ring, and send notification information to the wearable device.

[0301] The wireless communication function of the first terminal device 200 can be implemented through antenna 2, antenna 3, mobile communication module 250, wireless communication module 260, modem processor and baseband processor.

[0302] Antenna 2 and antenna 3 are used to transmit and receive electromagnetic wave signals. Fig.23 The structures of antenna 2 and antenna 3 in the first terminal device 200 are only examples. Each antenna in the first terminal device 200 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of the antennas. For example, antenna 2 can be reused as a diversity antenna for a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0303] The wireless communication module 260 can provide solutions for wireless communication including WLAN (such as Wi-Fi network), Bluetooth, GNSS, FM, NFC, IR, etc. applied to the first terminal device 200. The wireless communication module 260 can be one or more devices integrating at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 3, modulates the electromagnetic wave signal and performs filtering, and sends the processed signal to the processor 210. The wireless communication module 260 can also receive the signal to be sent from the processor 210, modulate the frequency, amplify it, and convert it into electromagnetic waves for radiation through the antenna 3.

[0304] That is to say, the wireless communication module 260 can realize short-range wireless communication, or in other words, the wireless communication module 260 includes a short-range wireless communication module. In the embodiment of the present application, the first terminal device 200 can establish a short-range wireless communication connection with the wearable device 100 through the wireless communication module 260, and communicate based on the short-range wireless communication connection. Optionally, the wireless communication module 260 may include a Bluetooth device, and the Bluetooth device may be a classic Bluetooth device, a BLE Bluetooth device, or a dual-mode Bluetooth device, and the embodiment of the present application does not impose any limitation on this.

[0305] In some embodiments, the antenna 2 of the first terminal device 200 is coupled to the mobile communication module 250, and the antenna 3 is coupled to the wireless communication module 260, so that the first terminal device 200 can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology, etc. GNSS may include the global positioning system (GPS), the global navigation satellite system (GLONASS), the Beidou navigation satellite system (BDS), the quasi-zenith satellite system (QZSS) and / or the satellite based augmentation system (SBAS).

[0306] The first terminal device 200 implements the display function through a GPU, a display screen 294, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 210 may include one or more GPUs, which execute program instructions to generate or change display information.

[0307] The display screen 294 is used to display images, videos, etc. The display screen 294 includes a display panel.

[0308] The first terminal device 200 can realize the shooting function through ISP, camera 293, video codec, GPU, display screen 294 and application processor.

[0309] The internal memory 221 can be used to store computer executable program codes, and the executable program codes include instructions. The processor 210 executes various functional applications and data processing of the first terminal device 200 by running the instructions stored in the internal memory 221. The internal memory 221 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sports application), etc. The data storage area may store data created during the use of the first terminal device 200 (such as device information of a wearable device paired with the first terminal device 200, a pairing key, and information of a preset geographic fence, device information within a trust ring, etc.). In addition, the internal memory 221 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a UFS, etc.

[0310] The structure of the second terminal device 300 is described below.

[0311] For example, Fig.24 : is a schematic diagram of the structure of an example of a second terminal device 300 provided in an embodiment of the present application. The second terminal device 300 is taken as a large-screen device for example. The large-screen device involved in the embodiment of the present application may be a large-screen TV, a large-screen computer, a large-screen mobile Internet device (MID), a large-screen vehicle-mounted device, a large-screen virtual reality (VR) device, a large-screen augmented reality (AR) device, a large-screen smart home device, etc., or may be other devices capable of establishing a short-range wireless communication connection, which is not limited here.

[0312] like Fig.24 As shown, the second terminal device 300 may include a processor 310, an external memory interface 320, an internal memory 321, a universal serial bus (USB) interface 330, a charging management module 340, a power management module 341, a battery 342, an antenna 4, a wireless communication module 350, an audio module 360, a speaker 360A, a speaker interface 360B, a sensor module 370, a button 380, an indicator 381, a display screen 382, ​​etc. The sensor module 370 may include a pressure sensor 370A, a gyroscope sensor 370B, a magnetic sensor 370C, a distance sensor 370D, a proximity light sensor 370E, a touch sensor 370F, an ambient light sensor 370G, etc.

[0313] It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the second terminal device 300. In other embodiments of the present invention, the second terminal device 300 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0314] The processor 310 may include one or more processing units, for example, the processor 310 may include an application processor, a modem processor, a GPU, an ISP, a controller, a memory, a video codec, a DSP, a baseband processor, and / or an NPU, etc. Different processing units may be independent devices or integrated into one or more processors.

[0315] The controller may be the nerve center and command center of the second terminal device 300. The controller may generate an operation control signal according to the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0316] The processor 310 may also be provided with a memory for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. The memory may store instructions or data that the processor 310 has just used or cyclically used. If the processor 310 needs to use the instruction or data again, it may be directly called from the memory. This avoids repeated access, reduces the waiting time of the processor 310, and thus improves the efficiency of the system.

[0317] The processor 310 can control the execution of the application code to implement the functions of the second terminal device 300 in this embodiment. For example, after the second terminal device 300 receives the discoverable broadcast sent by the wearable device 100 through the wireless communication module 350, it responds to the connection instruction input by the user and pairs with the wearable device 100.

[0318] The wireless communication function of the second terminal device 300 can be implemented by antenna 4, wireless communication module 350, modulation and demodulation processor and baseband processor. Antenna 4 is used to transmit and receive electromagnetic wave signals. Antenna 4 in the second terminal device 300 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve the utilization of antennas. For example, one of the multiple antennas can be reused as a diversity antenna of a wireless local area network. In some other embodiments, the antenna can be used in combination with a tuning switch.

[0319] The modem processor may include a modulator and a demodulator. Among them, the modulator is used to modulate the low-frequency baseband signal to be sent into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After the low-frequency baseband signal is processed by the baseband processor, it is passed to the application processor. The application processor outputs a sound signal through an audio module 360 ​​(not limited to a speaker 360A, a speaker interface 360B, etc.), or displays an image or video through a display screen 382. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 310 and be set in the same device as the wireless communication module 350 or other functional modules.

[0320] The wireless communication module 350 can provide wireless communication solutions including Bluetooth (BT), wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) network), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., applied to the second terminal device 300. The wireless communication module 350 can be one or more devices integrating at least one communication processing module. The wireless communication module 350 receives electromagnetic waves via the antenna 4, modulates the frequency of the electromagnetic wave signal and filters it, and sends the processed signal to the processor 310. The wireless communication module 350 can also receive the signal to be sent from the processor 310, modulate the frequency of it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 4.

[0321] That is to say, the wireless communication module 350 can realize short-range wireless communication, or in other words, the wireless communication module 350 includes a short-range wireless communication module. In the embodiment of the present application, the second terminal device 300 can establish a short-range wireless communication connection with the wearable device 100 through the wireless communication module 350, and communicate based on the short-range wireless communication connection. Optionally, the wireless communication module 350 may include a Bluetooth device, and the Bluetooth device may be a classic Bluetooth device, a BLE Bluetooth device, or a dual-mode Bluetooth device, and the embodiment of the present application does not impose any limitation on this.

[0322] The second terminal device 300 implements the display function through a GPU, a display screen 382, ​​and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 382 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 310 may include one or more GPUs, which execute program instructions to generate or change display information.

[0323] The display screen 382 is used to display images, videos, etc. For example, after the second terminal device 300 receives a pairing request sent by the wearable device, the display screen 382 displays the pairing request and prompts the user whether a Bluetooth connection with the wearable device is required. If the second terminal device 300 receives an operation from the user to instruct the establishment of a Bluetooth connection with the wearable device, in response to the operation, an interface for establishing a Bluetooth connection with the wearable device 100 is displayed on the display screen 382.

[0324] The internal memory 321 can be used to store computer executable program codes, which include instructions. The processor 310 executes various functional applications and data processing of the second terminal device 300 by running the instructions stored in the internal memory 321. The internal memory 321 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function, etc. The data storage area may store data created during the use of the second terminal device 300, etc.

[0325] The software architecture of the wearable device 100, the first terminal device 200 and the second terminal device 300 is described below.

[0326] The software system of the wearable device 100, the first terminal device 200, and the second terminal device 300 can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. The embodiment of the present application takes the Android system of the layered architecture as an example to illustrate the software structure of the wearable device 100, the first terminal device 200, and the second terminal device 300.

[0327] Fig.25 1 is a software structure diagram of the wearable device 100 of the embodiment of the present application. The layered architecture divides the software into several layers, each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer. The application layer can include a series of application packages.

[0328] like Fig.25As shown, the application package may include applications such as calendar, clock, sleep monitoring, WLAN, Bluetooth, etc.

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

[0330] like Fig.25 As shown, the application framework layer may include a window manager, a content provider, a view system, a resource manager, a notification manager, a Bluetooth process, and the like.

[0331] The window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc.

[0332] Content providers are used to store and retrieve data and make it accessible to applications. The data can include images, audio, browsing history, and bookmarks.

[0333] The view system includes visual controls, such as controls for displaying text, controls for displaying images, etc. The view system can be used to build applications. The display interface can be composed of one or more views.

[0334] The resource manager provides various resources for the application, such as localized strings, icons, images, layout files, etc.

[0335] The notification manager enables applications to display notification information in the status bar. It can be used to convey notification-type messages and can disappear automatically after a short stay without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as notifications of applications running in the background, or a notification that appears on the screen in the form of a dialog window. For example, a text message is displayed in the status bar, a prompt sound is emitted, a wearable device vibrates, an indicator light flashes, etc.

[0336] The Bluetooth process may include a Bluetooth service, a Bluetooth profile, and the like.

[0337] Android runtime includes core libraries and virtual machines. Android runtime is responsible for scheduling and management of the Android system.

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

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

[0340] The system library can include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL) and Bluetooth stack.

[0341] The surface manager is used to manage the display subsystem and provide the fusion of 2D and 3D layers for multiple applications.

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

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

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

[0345] The Bluetooth protocol stack is used to provide all practical operations of Bluetooth, including: turning Bluetooth on and off, Bluetooth management, search management, link management, and implementation of various profiles.

[0346] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, Wi-Fi driver, Bluetooth driver, audio driver, and sensor driver.

[0347] In the embodiment of the present application, taking scenario 1 as an example, the wearable device 100 can receive the notification information sent by the first terminal device 200 through the Bluetooth driver. The Bluetooth driver passes the received notification information through the Bluetooth protocol stack in the system library and the Bluetooth process in the application framework layer, and finally uploads it to the Bluetooth application in the application layer. Further, the Bluetooth application sends a discoverable broadcast to the large-screen device through the Bluetooth process, Bluetooth protocol stack and Bluetooth driver according to the notification information.

[0348] Fig.261 is a software structure diagram of the first terminal device 200 of the embodiment of the present application. Similar to the wearable device 100, the software architecture of the first terminal device 200 may include an application layer, an application framework layer, an Android runtime and a system library, and a kernel layer from top to bottom. The application layer may include a series of application packages.

[0349] like Fig.26 As shown, taking the first terminal device 200 as a mobile phone as an example, the application package may include applications such as camera, gallery, calendar, call, map, WLAN, music, video, positioning, sports and Bluetooth.

[0350] The sports application may be, for example, sports health, etc. The positioning application user obtains the geographic location of the first terminal device 200 .

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

[0352] like Fig.26 As shown, the application framework layer may include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, a subscription manager, and a Bluetooth process, etc.

[0353] Content providers are used to store and retrieve data and make it accessible to applications. The data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

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

[0355] The phone manager is used to provide communication functions for the first terminal device 200, such as management of call status (including connection, disconnection, etc.).

[0356] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.

[0357] The window manager, notification manager, Bluetooth process, Android runtime, etc. are similar to the corresponding modules in the wearable device 100 and will not be described in detail.

[0358] The subscription manager is used to accept subscriptions from other devices or modules in the first terminal device 200, and send notifications when conditions are met. Specifically, in an embodiment of the present application, the subscription manager can accept subscriptions from the wearable device 100, and notify the wearable device 100 when the first terminal device 200 enters a preset geographic fence and there are trusted devices around it.

[0359] The system library can include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), image processor and Bluetooth.

[0360] The functions of each module in the system library can be found in the wearable device 100 and will not be described in detail.

[0361] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, camera driver, Wi-Fi driver, Bluetooth driver, audio driver, and sensor driver.

[0362] Specifically, in the embodiment of the present application, the first terminal device 200 can obtain the geographical location of the first terminal device 200 through the positioning application based on the above software architecture, and determine whether the first terminal device 200 enters the preset geographical fence according to the geographical location. Determine whether there is a device that the mobile phone can trust in the current geographical fence through the Bluetooth application. When it is determined that the first terminal device 200 enters the target geographical fence (any preset geographical fence) and there is a device that the mobile phone can trust in the target geographical fence, the subscription manager sends a notification message to the wearable device 100. The notification message carries the device information of the trusted device.

[0363] Fig. 27 : is a software structure block diagram of the second terminal device 300 of the embodiment of the present application. The system of the second terminal device 300 can be divided into four layers, from top to bottom, namely, the application layer, the application framework layer, the Android runtime (Android runtime) and the system library, and the kernel layer. The application layer can include a series of application packages.

[0364] like Fig. 27 As shown, taking the second terminal device 300 as a large-screen device as an example, the application package may include applications such as WLAN, Bluetooth and sports.

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

[0366] like Fig. 27 As shown, the application framework layer may include a window manager, a content provider, a view system resource manager, a notification manager, a Bluetooth process, and the like.

[0367] The functions of each module of the application framework layer refer to the wearable device 100 and the first terminal device 200, which will not be repeated here.

[0368] The system library may include multiple functional modules, such as surface manager, media libraries, 3D graphics processing library (such as OpenGL ES), 2D graphics engine (such as SGL), and Bluetooth protocol stack.

[0369] The kernel layer is the layer between hardware and software. The kernel layer contains at least display driver, Wi-Fi driver, Bluetooth driver, audio driver, and sensor driver.

[0370] In the embodiment of the present application, the second terminal device 300 can call the window manager of the application framework layer, the surface manager of the system library, etc. through the Bluetooth application or sports application of the application layer based on the above software architecture to display the interface of the Bluetooth function to the user. Based on the interface, the user can input scanning and discovery instructions, connection instructions, confirmation pairing instructions, acceptance pairing instructions, etc. The Bluetooth application responds to the user's instructions, and cooperates with the Bluetooth process of the application architecture layer, the Bluetooth protocol of the system library, and the Bluetooth driver of the kernel layer to realize data interaction with the wearable device 100, thereby realizing Bluetooth connection. In addition, in the embodiment of the present application, it is also possible to add the wearable device 100 to the group after the second terminal device 300 establishes a Bluetooth connection with the wearable device 100 based on the sports application of the application layer, and realize team games or team fitness based on the sports data transmitted by the wearable device 100.

[0371] An embodiment of the present application also provides a computer-readable storage medium, in which a computer program is stored. When the computer program is executed by a processor, the processor executes the connection method for a wearable device of any of the above embodiments.

[0372] The embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer executes the above-mentioned related steps to implement the connection method of the wearable device in the above-mentioned embodiment.

[0373] In addition, an embodiment of the present application also provides a device, which may specifically be a chip, a component or a module, and the device may include a connected processor and a memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor may execute the computer-executable instructions stored in the memory so that the chip executes the connection method of the wearable device in the above-mentioned method embodiments.

[0374] Among them, the wearable device, the first terminal device and the second terminal device, the computer-readable storage medium, the computer program product or the chip provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0375] Through the description of the above implementation methods, technical personnel in the relevant field can understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0376] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic, for example, the division of modules or units is only a logical function division, and there may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0377] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0378] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0379] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0380] The above contents are only specific implementation methods of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A method for connecting a wearable device, the method being performed by the wearable device, characterized in that: The wearable device has established a first connection with a first terminal device, the first connection being a short-range wireless communication connection based on a first communication protocol, and the method includes: Receiving notification information sent by the first terminal device, the notification information is used to indicate that there is a second terminal device having a trust relationship with the first terminal device in the vicinity, and the notification information is received after the wearable device enters a preset geographical area; In response to the notification information, sending a first broadcast message to surrounding devices, where the first broadcast message is used for the surrounding devices to discover the wearable device; Displaying a first interface according to the notification information, the first interface including a first control, and establishing a second connection with the second terminal device in response to a connection instruction input by a user by clicking the first control, the second connection being a short-range wireless communication connection based on a second communication protocol; Alternatively, in response to the first request message sent by the second terminal device, a third connection is established with the second terminal device, and the third connection is a short-range wireless communication connection based on a third communication protocol.

2. The method according to claim 1, characterized in that: The method further comprises: Before establishing a connection with the second terminal device, the physical link with the first terminal device is automatically disconnected.

3. The method according to claim 1, characterized in that The establishing a connection with the second terminal device includes: Maintaining the first connection with the first terminal device; A connection is established with the second terminal device, wherein the connection between the wearable device and the second terminal device only includes a data transmission channel.

4. The method according to claim 3, characterized in that The first communication protocol is a Bluetooth protocol, the second communication protocol or the third communication protocol is a Bluetooth protocol, and the data transmission channel is a serial port profile SPP channel.

5. The method according to any one of claims 1 to 4, characterized in that The first communication protocol and the third communication protocol are the same communication protocol, or the first communication protocol and the second communication protocol are the same communication protocol.

6. The method according to any one of claims 1 to 5, characterized in that The first broadcast message carries first information, and the first information is used to indicate that the wearable device has established the first connection with the first terminal device.

7. A method for connecting a wearable device, characterized in that: The method is performed by a first terminal device, the first terminal device has established a first connection with the wearable device, and is characterized in that the method includes: When the first terminal device enters a preset geographical area, determining that there is a second terminal device having a trust relationship with the first terminal device in the surrounding area; After determining that the second terminal device having a trust relationship with the first terminal device exists in the surrounding, notification information is sent to the wearable device, where the notification information is used to indicate that the second terminal device having a trust relationship with the first terminal device exists in the surrounding.

8. The method according to claim 7, characterized in that The determining that there is a second terminal device in the surrounding area that has a trust relationship with the first terminal device includes: Acquire historical scanning information of the first terminal device, where the historical scanning information is used to represent device information of terminal devices scanned and discovered by the first terminal device in the preset geographical area within a historical time period; The information of multiple devices that have a trust relationship with the first terminal device is compared with the historical scanning information. If the information of the second terminal device exists in both the historical scanning information and the information of the multiple devices, it is determined that the second terminal device that has a trust relationship with the first terminal device exists in the surrounding area.

9. A method for connecting a wearable device, the method being executed by a second terminal device, characterized in that: The second terminal device is located in a preset geographical area, and the method includes: Receive a first broadcast message sent by a wearable device, where the first broadcast message carries first information, where the first broadcast message is used for surrounding devices to discover the wearable device, where the first information is used to indicate that a first connection has been established between the wearable device and a first terminal device, where the first connection is a short-range wireless communication connection based on a first communication protocol; In response to the first broadcast message, displaying a second interface according to the first information, wherein the second interface includes a second control; In response to a connection instruction input by the user by selecting the second control, a first request message is sent to the wearable device, wherein the first request message is used to request to establish a third connection with the wearable device, and the third connection is a short-range wireless communication connection based on a third communication protocol.

10. The method according to claim 9, characterized in that The first communication protocol and the third communication protocol are the same communication protocol.

11. The method according to claim 9 or 10, characterized in that: The third connection includes only a data transmission channel.

12. The method according to claim 11, characterized in that The first communication protocol and the third communication protocol are both Bluetooth protocols, and the data transmission channel is a serial port profile SPP channel.

13. A method for connecting a wearable device, the method being executed by a second terminal device, characterized in that: The distance between the wearable device and the second terminal device is a distance for short-range wireless communication, the second terminal device logs in to the first user account, and the method includes: In response to the user's operation of viewing surrounding wireless communication devices, obtaining device information of the wearable device and connection information for establishing a connection with the wearable device from the server according to the first user account, wherein the device information and the connection information are uploaded to the server by the first terminal device using the first user account; Displaying a third interface according to the device information, wherein the third interface includes a third control; In response to a connection instruction input by the user by selecting the third control, a third connection is established with the wearable device according to the connection information, and the third connection is a short-range wireless communication connection based on a third communication protocol.

14. The method according to claim 13, characterized in that The first terminal device has established a first connection with the wearable device, where the first connection is a short-range wireless communication connection based on a first communication protocol; and the third connection only includes a data transmission channel.

15. The method according to claim 14, characterized in that The third communication protocol is a Bluetooth protocol, and the data transmission channel includes an SPP channel.

16. The method according to claim 14 or 15, characterized in that The first communication protocol is the same as the third communication protocol.

17. A method for connecting a wearable device, characterized in that: The method is executed by a second terminal device, and is characterized in that the method comprises: In response to a first instruction from a user, a second broadcast message is sent to surrounding devices, where the second broadcast message is used to request multiple surrounding wearable devices to establish a short-range wireless communication connection with the second terminal device and join a group, where the multiple wearable devices include a first wearable device and a second wearable device, where the first wearable device is a device among the multiple wearable devices that has not established a short-range wireless communication connection with the second terminal device, and the second wearable device is a device among the multiple wearable devices that has established a fourth connection with the second terminal device, where the fourth connection is a short-range wireless communication connection based on a fourth communication protocol; Receiving a connection consent message and a first teaming consent message sent by the first wearable device, wherein the connection consent message indicates that the first wearable device agrees to establish a connection with the second terminal device, and the first teaming consent message indicates that the first wearable device agrees to join the group; In response to the connection consent message and the first teaming consent message, establish a fifth connection with the first wearable device, and add the first wearable device to the group, wherein the fifth connection is a short-range wireless communication connection based on a fifth communication protocol, and the fifth connection only includes a data transmission channel; In response to a second teaming consent message sent by the second wearable device, the second wearable device is added to the group, where the second teaming consent message indicates that the second wearable device agrees to join the group.

18. The method according to claim 17, characterized in that The fourth connection includes the data transmission channel and at least one of a call transmission channel and an audio transmission channel.

19. The method according to claim 17 or 18, characterized in that The fifth communication protocol is the Bluetooth protocol, and the data transmission channel is a serial port profile SPP channel.

20. The method according to any one of claims 17 to 19, characterized in that The second broadcast message includes scene information, and the scene information includes team gaming or team fitness.

21. The method according to claim 20, characterized in that The method further comprises: In response to a second instruction input by the user, data is obtained from each of the wearable devices based on a short-range wireless communication connection with each of the wearable devices, wherein the second instruction is used to instruct to start a game or to start fitness.

22. A wearable device, characterized in that: include: Processor, memory and short-range wireless communication module; The processor, the memory and the short-range wireless communication module cooperate with each other so that the wearable device executes the method as claimed in any one of claims 1 to 6.

23. A terminal device, characterized in that: include: Processor, memory and short-range wireless communication module; The processor, the memory and the short-range wireless communication module cooperate with each other so that the terminal device executes the method as described in any one of claims 7 to 8.

24. A terminal device, characterized in that: include: Processor, memory and short-range wireless communication module; The processor, the memory and the short-range wireless communication module cooperate with each other so that the terminal device executes the method as described in any one of claims 9 to 21.

25. 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 a processor, the processor controls a corresponding device to execute the method according to any one of claims 1 to 21.

Citation Information

Cited By

  • NFC function control method, wearable device and computer program product

    WO2026144221A1