Method and device for connecting wearable device
By receiving notification information in the wearable device and automatically sending broadcasts, the user is allowed to directly establish a connection with the second terminal device in the trust relationship, solving the complex operation problems in the prior art and improving the user experience and device resource utilization efficiency.
Patent Information
- Application Number
- PCT/CN2024/079196
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-31
- Filing Date
- 2024-02-29
- Publication Date
- 2024-12-05
AI Technical Summary
When existing wearable devices need to be connected to multiple terminal devices, the user operation is complicated and the user experience is poor, especially when it is necessary to disconnect and unbind relationship with another terminal device. The process is cumbersome when establishing a connection.
After receiving notification information in the wearable device, the broadcast message is automatically sent to the surrounding device, allowing the user to enter a connection command on the interface, and directly establish a wireless communication connection with the second terminal device in the trust relationship without disconnecting from the first terminal Device connection and binding relationship simplifies user operations.
It realizes that the wireless communication connection process between the wearable device and multiple terminal devices is simplified without affecting the security of user information, improves the user experience, and saves user operation steps and device resources.
Smart Images

Figure CN2024079196_05122024_PF_FP_ABST
Abstract
Description
Wearable device connection method and device
[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office on May 31, 2023, with application number 202310647974.8 and application name “Connection method and device for wearable devices”, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] 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
[0003] With the advancement of technology, wearable devices (such as smart watches and fitness trackers) are becoming more and more widely used 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. The wearable devices collect the user's motion data and transmit it to the terminal device. The terminal device then displays or provides feedback on the user's movements based on the motion data.
[0004] Generally, a wearable device can only establish a connection with one terminal device. To connect the wearable device to 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 release the binding relationship between the two, so that the smart watch enters a pairing state. 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 relatively cumbersome and the user experience is poor.
[0005] Summary of the Invention
[0006] The present application provides a method and device for connecting a wearable device, which can simplify user operations and improve user experience.
[0007] In the first aspect, the present application provides a connection method for a wearable device, which is executed by the wearable device, and 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 the surrounding devices, and the first broadcast message is used for the 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 the 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 the 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.
[0008] 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.
[0009] 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, Matter, Zigbee, Wi-Fi, Thread, or Mesh. 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.
[0010] 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 no longer 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.
[0011] 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.
[0012] Generally, 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. However, 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 the 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, to establish a short-range wireless communication connection between the second terminal device and the wearable device. In other words, 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 area without the user having to perform a disconnection or unbinding operation, thereby establishing 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 based on the notification information, so that the user can trigger the connection to the second terminal device by inputting instructions based on the first interface, without the user having to perform an operation of scanning and discovering the second terminal device on the wearable device side, further simplifying user operations and improving user experience.
[0013] In a possible implementation, the method further includes: automatically disconnecting the physical link with the first terminal device before establishing a connection with the second terminal device.
[0014] That is, before "establishing a second connection with the second terminal device," the method further includes: automatically disconnecting the physical link with the first terminal device (i.e., the physical link in the first connection) in response to a connection instruction input by the user by clicking the first control. Alternatively, before "establishing a third connection with the second terminal device," the method further includes: automatically disconnecting the physical link with the first terminal device in response to a first request message sent by the second terminal device.
[0015] In this implementation, the wearable device receives a notification message sent by the first terminal device, and can thus determine 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 confirm that the connection between the wearable device and the second terminal device will not affect the security of the user's information. Therefore, the wearable device can automatically disconnect from the first terminal device and then establish a connection with the second terminal device without displaying an interface to query the user or requiring manual operation by 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, simplifying user operations and further improving the user experience. On the other hand, in this scenario, the wearable device can confirm that even if the wearable device does not unbind with the first terminal device, it will not affect the security of the user's information. Therefore, the wearable device can only disconnect the physical link with the first terminal device. In this way, when the wearable device is reconnected with the first terminal device subsequently, 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.
[0016] In one 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.
[0017] 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.
[0018] In this implementation, after the wearable device learns about the current application scenario based on the notification information, it determines that the connection with the second terminal device is highly secure. Therefore, the wearable device can directly establish a second short-range wireless communication connection with the second terminal device without disconnecting from the first terminal device, thereby facilitating the user to interact with both the first and second terminal devices 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 for both.
[0019] 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.
[0020] In one 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.
[0021] 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.
[0022] It is understandable 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 nearby devices with a trusted relationship with the first terminal device, so that the second terminal device can determine the display interface based on the scenario. For example, in general, in this scenario, the probability of the user connecting the wearable device to the second terminal device is relatively high. Therefore, after the second terminal device determines the current application scenario based on the first information, it can pop up the wearable device information interface to remind the user whether to connect, etc., to facilitate user operation and improve user experience.
[0023] 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 in the surrounding area; after determining that there is a second terminal device that has a trust relationship with the first terminal device in the surrounding area, sending a notification message to the wearable device, and the notification message is used to indicate that there is a second terminal device that has a trust relationship with the first terminal device in the surrounding area.
[0024] The method provided in the second aspect of this application sends a notification message to the wearable device when a first terminal device establishes a connection with the wearable device and the first terminal device enters a preset geographical area and is nearby a second terminal device with a trusted relationship. This facilitates the wearable device to understand the current scene and thus facilitates the wearable device to send a discoverable broadcast to the second terminal device, eliminating the need for the user to disconnect or unbind, simplifying user operations and improving the user experience.
[0025] 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, where the historical scanning information is used to represent device information of terminal devices scanned and discovered by the first terminal device in 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; 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.
[0026] Multiple devices that have a trust relationship with the first terminal device, that is, devices within the trust ring of the first terminal device.
[0027] 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.
[0028] 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, a second interface is displayed according to the first information, and 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, the first request message being used to request establishment of a third connection with the wearable device, and the third connection is a short-range wireless communication connection based on a third communication protocol.
[0029] In the method provided in the third aspect of this application, the first broadcast message carries the first information, and the second terminal device can directly display the second interface based on the first information in the first broadcast message. The user can trigger the connection between the second terminal device and the wearable device through the second interface. This eliminates the need for the user to perform a scanning and discovery operation on the second terminal device, simplifies user operations, and improves the user experience.
[0030] In a possible implementation, the first communication protocol and the third communication protocol are the same communication protocol.
[0031] In a possible implementation, the third connection only includes a data transmission channel.
[0032] 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.
[0033] 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.
[0034] 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 includes: in response to the user's operation of viewing the 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 are uploaded to the server by the first terminal device using the first user account; according to the device information, a third interface is displayed, and the third interface includes a third control; in response to the 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.
[0035] Optionally, when the third communication protocol is the Bluetooth protocol, the connection information may be, for example, a pairing key.
[0036] Optionally, the server may be a cloud service, or referred to as a cloud platform, cloud end, etc.
[0037] 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 an interface based on the information, thereby achieving connection with the wearable device in response to the user's operation. The entire process does not require the user to perform disconnection or unbinding operations, and the third interface can be displayed without the user performing a scan and discovery operation, thereby simplifying user operations and improving the 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, simplifying the connection process.
[0038] In one 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.
[0039] 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.
[0040] In a possible implementation, the third communication protocol is a Bluetooth protocol, and the data transmission channel includes an SPP channel.
[0041] In one possible implementation, the first communication protocol is the same as the third communication protocol.
[0042] In a fifth aspect, the present application provides a method for connecting a wearable device, which is executed by a second terminal device, and the method includes: 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 including 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, and 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 the first wearable device, the connection consent message indicating that the first wearable device agrees to establish a connection with the second terminal device, and the first teaming consent message indicating 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 the second teaming consent message sent by the second wearable device, adding the second wearable device to the group, the second teaming consent message indicating that the second wearable device agrees to join the group.
[0043] The method provided in the fifth aspect of this application enables the second terminal device to connect to multiple wearable devices simultaneously, meeting the user's usage needs in scenarios such as team gaming and team fitness, and improving the user experience. In addition, when establishing a connection, the second wearable device has already established a fourth connection with the second terminal device. Therefore, 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.
[0044] 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.
[0045] Optionally, when the fourth communication protocol is the Bluetooth protocol, the call transmission channel may be, for example, a handsfree profile (HFP) channel, and the audio transmission channel may be, for example, an advanced audio distribution profile (A2DP) channel.
[0046] In this implementation, in addition to the data transmission channel, the fourth connection also includes at least one of a call transmission channel and an audio transmission channel, which can meet the user's call needs and audio transmission needs and further improve the user experience.
[0047] In a possible implementation, the fifth communication protocol is a Bluetooth protocol, and the data transmission channel is a Serial Port Profile (SPP) channel.
[0048] In one possible implementation, the second broadcast message includes scene information, where the scene information includes team gaming or team fitness.
[0049] In one possible implementation, the method further includes: in response to a second instruction input by the user, obtaining data from each wearable device based on a short-range wireless communication connection with each wearable device, wherein the second instruction is used to instruct to start a game or start fitness.
[0050] In a possible implementation, the second broadcast message is a Bluetooth low energy broadcast.
[0051] In this implementation, the second broadcast message is a Bluetooth low energy broadcast, which can save power consumption of the second terminal device.
[0052] In a sixth aspect, the present application provides an apparatus, which is included in a wearable device and has the function of implementing the wearable device behavior in the first aspect and the possible implementation of the first 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.
[0053] In a seventh aspect, the present application provides an apparatus, included in a first terminal device, that implements the behavior of the first terminal device described in the second aspect and possible implementations of the second aspect. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functionality described above. For example, a receiving module or unit, a processing module or unit, etc.
[0054] In an eighth aspect, the present application provides an apparatus, included in a second terminal device, having the functionality to implement the second terminal device's behavior in the third, fourth, and fifth aspects and their possible implementations. The functionality can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the aforementioned functionality, such as a receiving module or unit, a processing module or unit, etc.
[0055] In the 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.
[0056] In the tenth aspect, the present application provides a terminal 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 terminal device executes any one of the methods in the technical solution of the second aspect.
[0057] In the eleventh aspect, the present application provides a terminal 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 terminal device executes any one of the methods in the technical solutions of the third aspect, the fourth aspect or the fifth aspect.
[0058] In a twelfth 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 perform the method in the first aspect and any possible implementation thereof.
[0059] Optionally, the chip also includes a memory, and the memory is connected to the processor via circuits or wires.
[0060] Further optionally, the chip also includes a communication interface.
[0061] In a thirteenth 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 perform the method in the second aspect and any possible implementation thereof.
[0062] 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 perform the method in the third, fourth, or fifth aspect and any possible implementation thereof.
[0063] 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.
[0064] In the sixteenth aspect, the present application provides a computer program product, which includes: a computer program code, which, when the computer program code runs on an electronic device, enables the electronic device to execute any one of the technical solutions of the first, second, third, fourth or fifth aspects. BRIEF DESCRIPTION OF THE DRAWINGS
[0065] FIG1 is a schematic diagram of an application scenario of a connection method for a wearable device provided in an embodiment of the present application;
[0066] FIG2 is a schematic diagram of an application scenario in which a user performs somatosensory fitness through a large-screen device, provided in an embodiment of the present application;
[0067] FIG3 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;
[0068] FIG4 is a schematic diagram of a process of establishing a Bluetooth connection between a smartwatch and a large-screen device according to an embodiment of the present application;
[0069] FIG5 is a schematic diagram of an interface of a smart watch during a pairing process provided by an embodiment of the present application;
[0070] FIG6 is a flow chart of a method for connecting a wearable device according to an embodiment of the present application;
[0071] FIG7 is a schematic diagram of an application scenario of another connection method for a wearable device provided in an embodiment of the present application;
[0072] FIG8 is a schematic diagram of interface changes corresponding to a connection method for a wearable device provided in an embodiment of the present application;
[0073] FIG9 is a schematic diagram of an interface of a large-screen device provided in an embodiment of the present application;
[0074] FIG10 is a schematic diagram of a connection change between a smartwatch, a mobile phone, and a large-screen device according to an embodiment of the present application;
[0075] FIG11 is a flow chart of another method for connecting a wearable device according to an embodiment of the present application;
[0076] FIG12 is a schematic diagram of another example of connection changes between a smartwatch, a mobile phone, and a large-screen device provided in an embodiment of the present application;
[0077] FIG13 is a flow chart of another example of a method for connecting a wearable device according to an embodiment of the present application;
[0078] FIG14 is a flow chart of another example of a method for connecting a wearable device according to an embodiment of the present application;
[0079] FIG15 is a schematic diagram of an interface of another large-screen device provided in an embodiment of the present application;
[0080] FIG16 is a schematic diagram of another example of connection changes between a smartwatch, a mobile phone, and a large-screen device provided in an embodiment of the present application;
[0081] FIG17 is a schematic diagram of an application scenario of another method for connecting a wearable device provided in an embodiment of the present application;
[0082] FIG18 is a flow chart of another example of a method for connecting a wearable device according to an embodiment of the present application;
[0083] FIG19 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;
[0084] FIG20 is a schematic diagram of an interface in which a smartwatch receives a team BLE broadcast sent by a large-screen device, according to an embodiment of the present application;
[0085] FIG21 is a schematic diagram of a process of establishing Bluetooth connections between a large-screen device and multiple wearable devices according to an embodiment of the present application;
[0086] FIG22 is a schematic structural diagram of a wearable device 100 provided in an embodiment of the present application;
[0087] FIG23 is a schematic structural diagram of a first terminal device 200 provided in an embodiment of the present application;
[0088] FIG24 is a schematic structural diagram of a second terminal device 300 provided in an embodiment of the present application;
[0089] FIG25 is a schematic diagram of a software architecture of a wearable device 100 according to an embodiment of the present application;
[0090] FIG26 is a schematic diagram of the software architecture of a first terminal device 200 provided in an embodiment of the present application;
[0091] Figure 27 is a schematic diagram of the software architecture of a second terminal device 300 provided in an embodiment of the present application. DETAILED DESCRIPTION
[0092] The technical solutions in the embodiments of the present application will be described below in conjunction with the accompanying 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 merely a description of the association relationship of associated objects, indicating that three relationships can exist, 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.
[0093] In the following, the terms "first," "second," and "third" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the quantity of the technical features indicated. Therefore, a feature specified as "first," "second," or "third" may explicitly or implicitly include one or more of the features.
[0094] References to "one embodiment" or "some embodiments" in this specification mean that one or more embodiments of the present application include a particular feature, structure, or characteristic described in conjunction with that embodiment. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in other embodiments" appearing in different places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.
[0095] To better understand the embodiments of the present application, the terms or concepts that may be involved in the embodiments are explained below.
[0096] 1. Connect
[0097] 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.
[0098] 2. Bluetooth devices
[0099] A Bluetooth device refers to a module or device used in electronic devices to achieve Bluetooth connectivity. Bluetooth devices are mainly divided into classic Bluetooth devices, Bluetooth low energy (BLE) devices (also known as 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, and high speed (HS) Bluetooth devices. Dual-mode Bluetooth devices are Bluetooth devices that integrate the controllers of classic Bluetooth devices and low-power Bluetooth devices.
[0100] 3. Transmission channel of Bluetooth connection
[0101] Taking classic Bluetooth devices as an example, a Bluetooth connection may include transmission channels for one or more profiles, of which the following are some examples:
[0102] 3.1 HFP channel
[0103] HFP stands for handsfree profile in English and handsfree profile in Chinese. HTP defines two roles: audio gateway (AG) and handsfree component (HF). It provides remote wireless control and voice connection between the audio gateway and the handsfree device via 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) function, such as answering, hanging up, rejecting, voice dialing, etc.
[0104] 3.2 A2DP Channel
[0105] A2DP stands for Advanced Audio Distribution Profile (A2DP). It specifies the protocol stack and usage methods for transmitting high-quality audio data using Bluetooth asynchronous transmission channels. Using A2DP channels, Bluetooth devices can transmit high-quality audio data to each other.
[0106] 3.3 SPP Channel
[0107] SPP stands for Serial Port Profile. It defines the Bluetooth device requirements needed to simulate a serial cable connection between two peer devices using the Radio Frequency Communication (RFCOMM) protocol. These requirements are expressed as services provided to applications and define the functions and procedures required for interoperability between Bluetooth devices. In short, over SPP channels, Bluetooth devices enable point-to-point data transmission.
[0108] It should be noted that there are many different 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.
[0109] 4. Trust Ring and Trusted Devices
[0110] Two or more terminal devices establish a trust relationship through trusted authentication, forming a trust ring. In other words, multiple devices have a trust relationship with each other, which can be understood as forming a trust ring.
[0111] 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 form 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 to this application.
[0112] The terminal devices within the trust ring form a local area network through near-field communication, through which data can be synchronized and device collaboration can be achieved.
[0113] Within a trust ring, a terminal device can be considered a trusted device for other devices. In other words, through trusted authentication, terminal devices that establish a trust relationship are called trusted devices. For example, if a mobile phone, tablet computer, and laptop computer form a trust ring, the tablet and the mobile phone can be considered trusted devices for each other. That is, the tablet is a trusted device for the mobile phone, and the mobile phone is also a trusted device for the tablet.
[0114] The application scenarios of the embodiments of the present application are described below.
[0115] Wearable devices such as smartwatches, fitness trackers, smart wristbands, smart glasses, smart headbands, and headphones are increasingly being used in our daily lives. Wearable devices can be paired with end devices to enable related functions. For example, if the wearable device is a smartwatch and the end device is a mobile phone, the smartwatch can be paired with the phone to answer calls or upload data from the smartwatch to the phone.
[0116] After a wearable device is paired and connected to a terminal device, a binding relationship is automatically established between the two devices. This facilitates encryption authentication and link encryption during the next connection. Establishing a binding relationship involves saving information such as the pairing key (also known as the link key) of the other device. However, when a wearable device is bound to a terminal device, the terminal device can access various information about the wearable device, including the user's account information and private information. Therefore, to ensure the security of user information, wearable devices are generally limited to establishing a connection with a single terminal device. If a wearable device is currently connected to a terminal device, when establishing a connection with another terminal device, the wearable device must obtain the user's consent, first disconnect from the current terminal device, and release the binding relationship with that terminal device. This allows the wearable device to enter a pairing state before pairing with another terminal device. Removing a binding relationship, also known as unpairing, refers to deleting information such as the pairing key of the bound device. Unbinding can be triggered by clicking the Unpair control, Delete Device control, or Connect New Device control on either the wearable device or the terminal device. This is explained below with reference to application scenarios.
[0117] For example, 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. As shown in Figure 1 (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 somatosensory fitness through the large-screen device, the user needs to first disconnect the smart watch from the mobile phone and unbind the two, as shown in Figure 1 (b). Afterwards, the smart watch establishes a connection with the large-screen device, as shown in Figure 1 (c).
[0118] 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, also known as artificial intelligence (AI) fitness or AI sports, refers to sports fitness based on somatosensory technology. Somatosensory technology means that users do not need to use complex control devices, 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 (APP) in the large-screen device displays or feeds back the user's movements based on 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 shown in Figure 2.
[0119] Optionally, the user can disconnect the smartwatch from the phone and unbind the smartwatch by operating the smartwatch, or disconnect the smartwatch from the phone and unbind the smartwatch by operating the phone. Referring to Figure 3, this embodiment uses disconnecting the smartwatch from the phone and unbinding the smartwatch as an example. As shown in Figure 3(a), the user can click on a card 302 for a smartwatch (shown as smartwatch a) in the device interface 301 of a sports app (e.g., Sports Health). In response to the user's click, the phone displays an information interface 303 for smartwatch a, as shown in Figure 3(b). This interface includes a selection control 304. The user clicks on the selection control 304, and a tab 305 appears on the interface. Tab 305 includes a delete device control 306, as shown in Figure 3(c). The user clicks on the delete device control 306, and a card 307 appears on the interface, asking the user whether to delete the device, as shown in Figure 3(d). Card 307 includes an OK control 308. After the user clicks on the OK control 308, the phone disconnects from the smartwatch and unbinds the smartwatch.
[0120] 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. For example, Figure 4 is a schematic diagram of the 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 operation of the large-screen device to scan and discover the device, and initiate a pairing connection as an example for illustration. As shown in Figure (a) in Figure 4, when Bluetooth is turned on on both the large-screen device and the smart watch, 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 (b) in 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 for surrounding Bluetooth devices and displays the add device interface 405, as shown in Figure (c) in Figure 4. After scanning for a certain period of time, the large-screen device discovers the smartwatch (shown as smartwatch a) and displays the smartwatch information card 406 on the interface. The smartwatch information card 406 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 smartwatch.
[0121] Afterwards, the large-screen device displays a pairing confirmation interface 408, asking the user whether to confirm pairing with the smartwatch. The pairing confirmation interface 408 may include a pop-up window 409, which includes a confirmation control 410 and a cancel control 411, as shown in Figure 4 (d).
[0122] 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 , as shown in FIG. 4 ( e ).
[0123] 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 shown as 501 in Figure (a) of Figure 5, and 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 Figure (b) of Figure 5. At the same time, the mobile phone displays a second pairing interface 413, as shown in Figure (f) of Figure 4. After a period of time, the large-screen device and the smart watch complete pairing and establish a connection. After the connection is established, the interface of the large-screen device and the smart watch can be as shown in Figure (c) of Figure 1.
[0124] It should be noted that Figures 4 and 5 are only used as an example. In actual applications, the Bluetooth connection between the large-screen device and the smart watch can also be established through other operating methods. For example, the selection control 304 in the device interface 403 in Figure (b) of Figure 4 can be selected through the remote control to trigger the large-screen device to scan for surrounding Bluetooth devices.
[0125] It can be seen from the embodiments shown in Figures 1 to 5 that when a 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 from 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.
[0126] 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.
[0127] The wearable device connection method provided in the embodiments of the present application involves a wearable device, a first terminal device, a second terminal device, and a server. The wearable device may be a sports bracelet, a sports anklet, a smart watch, a smart wristband, smart glasses, a smart headband, headphones, etc. The embodiments of the present application do not impose any restrictions on the specific type of wearable device.
[0128] 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 (UMPCs), netbooks, personal digital assistants (PDAs), etc., which can install applications (APPs) 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.
[0129] The following embodiments of this 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. Combined with the accompanying drawings and application scenarios, the connection method of the wearable device provided in the embodiments of this application will be specifically explained.
[0130] To facilitate understanding of the solution of this embodiment, we first briefly describe the process of establishing a Bluetooth connection between a wearable device and a terminal device. This process involves the following:
[0131] 1) Send discoverable broadcast
[0132] At least one of device A and device B can actively send discoverable broadcasts (also called broadcast packets or broadcast messages) at regular intervals so that the device can be discovered by other devices. The following example uses device A sending a discoverable broadcast to its surroundings as an example. Generally, device A will only send discoverable broadcasts to its surroundings when it is in a pairing state. When device A is in the paired state, considering the security of user information, device A no longer establishes connections with other devices, and therefore device A does not send discoverable broadcasts to its surroundings.
[0133] 2) Scan and find
[0134] After receiving the discoverable broadcast from device A, a nearby device (for example, device B) can initiate a scan request to device A to obtain more information about it, such as its name and type. After receiving the scan request, device A responds by sending a scan response packet to device B. This scan response packet may include device A's information. In this case, device B is the connection initiator, or the master, and device A is the connection receiver, or the slave. The device that receives the scan request also needs to respond with a scan response packet.
[0135] For example, if 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 receiving the scan response packet, device B displays device A's device information on its interface.
[0136] 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 surrounding area and cannot be scanned and discovered by other devices (such as device B).
[0137] 3) Establish a physical link
[0138] After the scan and discovery are complete, device A establishes a physical link with device B in response to a user's connection instruction. Optionally, the physical link may include an advanced communication link (ACL) or a SCO link. When the user enters a connection instruction with device A on device B's interface (for example, by clicking the connection control corresponding to device A), device B responds to the connection instruction and establishes a physical link with device B.
[0139] 3) Pairing
[0140] After the physical link is established, devices A and 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. The pairing phase can be triggered by a user input command or automatically by the device. That is, after the physical link is established, the pairing phase automatically begins.
[0141] The pairing phase is essentially the process of device A and device B negotiating and determining the encryption key. The pairing phase can include pairing feature exchange, link authentication, key distribution, and binding.
[0142] Pairing feature exchange: used to exchange authentication requirements and I / O capabilities between two parties (device A and device B).
[0143] 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.
[0144] Key distribution: Device A and device B generate a pairing key based on information such as a random number, a PIN code, and a media access control (MAC) address. The pairing key may include a long-term key (LTK). MAC is also called a MAC address.
[0145] Binding: Device A and device B store the LTK and establish a binding relationship between them. After device A and device B establish a binding relationship, if they reconnect, they can skip the pairing phase and directly use the LTK for encryption.
[0146] 4) Establish a profile channel
[0147] After pairing is complete, device A and device B establish a profile channel (also called a profile connection) based on the required profile.
[0148] It should be noted that when device A and device B have completed pairing and binding and have not been 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. They can directly establish a physical link and a profile channel to achieve Bluetooth connection.
[0149] The following describes the detailed process of the connection method of the wearable device provided in the embodiment of the present application.
[0150] Scenario 1:
[0151] One embodiment of the present application provides a method for connecting a wearable device. In this embodiment, if a smartwatch and a mobile phone have established a Bluetooth connection, the smartwatch can establish a Bluetooth connection with the trusted device when the mobile phone enters a preset geo-fencing area and there are nearby trusted devices. This method does not require the user to disconnect the smartwatch and mobile phone or to unbind the smartwatch from the mobile phone. This method is described in detail below with reference to the accompanying figures.
[0152] For example, FIG6 is a flow chart of a method for connecting a wearable device according to an embodiment of the present application. As shown in FIG6 , the method includes:
[0153] S101. When the smart watch and the mobile phone have established a Bluetooth connection (also called a 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 there is a trusted large-screen device in the target geo-fence.
[0154] A preset geofence is information used to represent a preset geographic area. Geofencing, a new application of location-based services (LBS), uses a virtual fence to enclose a virtual geographic boundary. When a phone moves from outside the geofence to inside (entering the geofence) or from inside the geofence to outside (leaving the geofence), the corresponding service is triggered. For example, if an electronic device enters the geofence of a high-voltage power line, the corresponding management system will send a notification or warning to the electronic device.
[0155] The target geofence is any one of at least one preset geofence. Optionally, the mobile phone can pre-set and save information on 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 smartwatch 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.
[0156] Optionally, the mobile phone can obtain historical Bluetooth scan information and use this information to determine whether any trusted devices exist within the target geofence. This historical Bluetooth scan information represents information about devices discovered by the mobile phone's Bluetooth device within the target geofence during a historical time period. Optionally, this historical Bluetooth scan information may include the scan time and location when the mobile phone discovered the device, as well as device information about the discovered device. For example, the device information about the discovered device may include a MAC address and device name. Based on this historical Bluetooth scan information, the mobile phone can determine which devices it discovered within the target geofence during the historical time period and, based on the device information within the trust ring, determine whether any trusted devices exist within the target geofence. Specifically, the mobile phone can compare this historical Bluetooth scan information with the device information within the trust ring to determine whether any devices scanned by the mobile phone during the historical time period include any devices within the trust ring. If so, the mobile phone determines that any trusted devices exist within the target geofence. In this implementation, the mobile phone can quickly determine whether any trusted devices exist within the target geofence based on this historical Bluetooth scan information, while also conserving power consumption.
[0157] Optionally, after confirming that it has entered the target geofence, 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 geofence.
[0158] 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 within the target geofence. The embodiment of the present application does not impose any limitation on the specific method for the mobile phone to determine whether there is a trusted device within the target geofence.
[0159] 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.
[0160] For example, FIG7 is a schematic diagram of another application scenario of a wearable device connection method provided in an embodiment of the present application. As shown in FIG7 , target geofence 101 is the geofence corresponding to the user's home. The user carries a mobile phone 102 and wears a smartwatch 103, and a Bluetooth connection is established between the mobile phone 102 and the smartwatch 103. When the user returns home with the mobile phone 102, the mobile phone 102 determines that it has entered the target geofence 101 and, based on historical Bluetooth scan information, determines that a trusted device exists within the target geofence 101, which is a large-screen device 104.
[0161] 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.
[0162] Optionally, the notification information may carry the device information of the trusted device. In the embodiment of the present application, the notification information may carry the 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.
[0163] In one possible implementation, the smartwatch may pre-subscribe to notification information from the mobile phone. Thus, when the mobile phone determines that it has entered a target geofence and there is a trusted device within the target geofence, the mobile phone sends a notification message to the smartwatch.
[0164] 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.
[0165] In one embodiment, after receiving the notification information, the smartwatch can periodically send a discoverable broadcast to surrounding devices so that surrounding devices can always find the smartwatch when they need to connect to the smartwatch. For example, the smartwatch can send a discoverable broadcast to surrounding devices every 5 seconds until the trusted device receives the discoverable broadcast.
[0166] In one embodiment, the discovery broadcast may carry the device information of the smartwatch and Bluetooth connection information (i.e., the first information). The device information of the smartwatch may include, but is not limited to, a MAC address. The Bluetooth connection information is used to indicate that the smartwatch has currently established a Bluetooth connection with the mobile phone. Optionally, the Bluetooth connection information may be represented by a predefined field.
[0167] 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 the MAC address) of the large-screen device can be carried in the discoverable broadcast. 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 no longer 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.
[0168] S104: The large-screen device receives the discoverable broadcast sent by the smart watch.
[0169] 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.
[0170] 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.
[0171] The scan discovery command is used to instruct the large-screen device to perform a scan discovery. Optionally, after the user starts the large-screen device, they can open an app on the large-screen device that needs to interact with the smartwatch (such as a sports app) and enter the scan discovery command through the app. For example, in the sports app's interface for managing Bluetooth connected devices, click the Add Device card.
[0172] For example, Figure 8 is a schematic diagram of an interface provided by an embodiment of the present application. As shown in Figure 8 (a), a large-screen device launches a sports app and displays the app's device interface 403. Device interface 403 includes an add device card 404, which the user can select using the remote control to enter a scan and discover command.
[0173] 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, such as one or more of the device name and device type of the smart watch, so as to display this information in the interface.
[0174] Specifically, in response to a scan discovery command input by the user, the large-screen device initiates a scan request to the smartwatch. After receiving the scan request, the smartwatch sends a scan response packet to the large-screen device in response. The scan response packet includes the device information of the smartwatch. After receiving the scan response packet, the large-screen device displays the device information of the smartwatch in an interface. For example, the interface of the large-screen device scanning and discovering the smartwatch may be shown as interface 405 in Figure 8 (b).
[0175] It should be noted that since the discoverable broadcast is sent by the smartwatch to the surrounding devices only after receiving the notification information, when the discoverable broadcast sent by the smartwatch to the large-screen device carries the device information of the smartwatch 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 smartwatch: the smartwatch 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 smartwatch without being triggered by the user's scan and discovery instruction. After automatically scanning and discovering the smartwatch, the large-screen device can display the device information of the smartwatch in the interface in the form of a pop-up window and ask the user whether to establish a connection with the smartwatch.
[0176] In short, step S105 can also be replaced by: the large-screen device responds to the discoverable broadcast, scans and discovers the smartwatch based on the Bluetooth connected information in the discoverable broadcast, and obtains and displays the device information of the smartwatch. Optionally, the device information of the smartwatch can be displayed in the form of a pop-up window (also known as the second interface). In this way, the user does not need to manually trigger the scan discovery, simplifying the user operation and improving the user experience.
[0177] Exemplarily, as shown in FIG. 9 , the second interface may be shown as 901 , and the smartwatch device information may be displayed in a pop-up window 902 .
[0178] 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.
[0179] 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 can display a connection control for inputting the connection instruction while displaying the device information of the smart watch, and the user can input the connection instruction 1 through the connection control.
[0180] For example, as shown in FIG8(b), the user can use the remote control to select the connection control 407 in the card 406 of the smart watch a in the interface 405 shown in FIG8(b) to input the connection instruction 1. Of course, the user can also input the connection instruction 1 by voice input or other methods, and this embodiment of the application does not impose any limitation on this.
[0181] After receiving the connection instruction 1, the large-screen device establishes a physical link with the mobile phone.
[0182] S107. The large-screen device displays a pairing confirmation interface.
[0183] Specifically, after the large-screen device establishes a physical link with the smartwatch, a pairing confirmation interface is displayed on the screen. The pairing confirmation interface includes a query message asking the user whether to confirm pairing with the smartwatch. The query message in the pairing confirmation interface can be displayed in various 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.
[0184] For example, the pairing confirmation interface of the large-screen device may be, for example, interface 408 as shown in FIG8(c). Interface 408 includes a pop-up window 409. Pop-up window 409 includes a confirmation control 410 and a cancel control 411.
[0185] 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.
[0186] The confirmation pairing instruction 1 is used to instruct the large-screen device to initiate a pairing request with the smartwatch. For example, as shown in FIG8(c), the user can click the confirmation control 410 in the pop-up window 409 to enter the confirmation pairing instruction 1. After the user enters the confirmation pairing instruction 1, the large-screen device can display a first pairing interface 412, as shown in FIG8(d).
[0187] In some embodiments, the large-screen device may not display the pairing confirmation interface, nor require the user to enter a pairing confirmation command. Instead, after establishing a physical link with the smartwatch, the large-screen device directly sends a pairing request to the smartwatch. In other words, the "response to the user entering the pairing confirmation command 1 in the confirmation interface" in steps S107 and S108 may not be performed, and after step S105 is completed, the "large-screen device sends a pairing request to the smartwatch" in step S108 may be directly executed. This further simplifies user operations and improves the user experience.
[0188] S109: In response to the pairing request from the large-screen device, the smart watch displays a pairing request interface.
[0189] Specifically, the smartwatch displays a pairing request interface based on 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 query information in the pairing request interface can be displayed in various forms, such as pop-up windows, capsules, cards or floating windows, etc., and the embodiments of the present application do not impose any restrictions on this. In one embodiment, the pairing request interface can be similar to the interface 501 shown in (a) of Figure 5, except that the schematic diagram of the device connected to the smartwatch in the pairing request interface can be a schematic diagram of the large-screen device, rather than the schematic diagram of the mobile phone in interface 501.
[0190] 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.
[0191] Specifically, based on the notification information, the smartwatch can determine that there is a trusted device nearby, such as a mobile phone, and based on the user's input of the accept pairing instruction 1, it determines that the user agrees to establish a connection with the trusted device (large-screen device), 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.).
[0192] Optionally, the smartwatch can disconnect the physical link with the watch and release the binding relationship with the mobile phone.
[0193] Optionally, the smartwatch may only disconnect the physical link with the mobile phone without releasing the binding relationship with the mobile phone. In this embodiment, the smartwatch receives the notification information sent by the mobile phone, and thus can determine that the current application scenario is: the smartwatch 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 smartwatch receives an accept pairing instruction 1 in which the user agrees to pair with the large-screen device, it can be confirmed that even if the smartwatch does not release the binding relationship with the mobile phone, it will not affect the security of the user information. Therefore, the smartwatch can only disconnect the physical link with the mobile phone, so that when the smartwatch is reconnected to the mobile phone later, there is no need to enter the pairing stage again, 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 smartwatch and the mobile phone, simplifying user operations, and improving user experience.
[0194] 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 is received from a large-screen device. This application does not impose any limitation on this.
[0195] S111. Pair the smart watch with the large-screen device and establish a profile channel.
[0196] Accepting pairing instruction 1 is used to indicate acceptance of the pairing request of the large-screen device. Optionally, the pairing request interface may include an accept pairing control, such as 502 shown in Figure 5 (a). The user can click on the accept pairing control 502 to enter the accept pairing instruction 1. Of course, the user can also enter the accept pairing instruction 1 in other ways, such as voice input, key selection, etc., and this embodiment of the application does not impose any limitation on this.
[0197] During the process of pairing the smart watch with the large-screen device and establishing a profile channel, the large-screen device can display a second pairing interface 413, as shown in Figure 8 (e), and the smart watch can display a third pairing interface. The third pairing interface can be similar to the interface 503 shown in Figure 5 (b), with the difference that the schematic diagram of the device connected to the smart watch in the third pairing interface can be a schematic diagram of the large-screen device, rather than the schematic diagram of the mobile phone in interface 503. The details are not repeated here.
[0198] Optionally, in this embodiment, the profile channels established between the smartwatch and the large-screen device may include an HFP channel, an A2DP channel, and an SPP channel. After the smartwatch and the large-screen device are paired and these channels are established, the smartwatch and the large-screen device complete a Bluetooth connection. After the Bluetooth connection is completed, the interface of the large-screen device may be as shown in Figure 8 (f).
[0199] 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.
[0200] In this embodiment, a schematic diagram of the connection changes between the smart watch and the mobile phone and the large-screen device can be seen in Figure 10. As shown in Figure (a) in Figure 10, 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, etc. 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 Figure (b) in Figure 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, etc.
[0201] As described above, under normal circumstances, when a wearable device is already connected to a terminal device, it is in a paired state. Considering the security of user information, the wearable device no longer sends discoverable broadcasts to the surrounding area. Only after 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 surrounding area again. In this embodiment, when a mobile phone and a smartwatch have established a Bluetooth connection, when the mobile phone detects that it has entered a target geofence and a trusted large-screen device is present within the target geofence, the mobile phone sends a notification message to the smartwatch. In other words, after the mobile phone recognizes the trusted large-screen device, it notifies the smartwatch. This allows the smartwatch to understand the current application scenario: the smartwatch is already connected to the mobile phone and a trusted large-screen device is nearby. In this scenario, reconnecting the smartwatch to the large-screen device without releasing the binding relationship with the mobile phone will not affect the security of user information. Therefore, the user does not need to perform disconnection and unbinding operations. The smartwatch automatically sends discoverable broadcasts to surrounding devices, allowing the smartwatch to be scanned and discovered by the large-screen device, thereby establishing a more secure Bluetooth connection with the trusted large-screen device. This saves the user from having to perform the disconnection and unbinding operations, improving the user experience. Furthermore, when the smartwatch receives a pairing request from the large-screen device, since the smartwatch can determine that the large-screen device is a trusted device based on the notification information, the smartwatch automatically disconnects from the phone and establishes a connection with the large-screen device without displaying an interface asking the user or requiring the user to manually disconnect. This not only switches the smartwatch's Bluetooth connection from the phone to the large-screen device, but also eliminates the need for the user to perform the disconnection and unbinding operations, simplifying user operations and further improving the user experience.
[0202] 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. Therefore, referring to Figure 11, in another embodiment, after receiving the pairing request sent by the large-screen device, the smart watch can also directly respond to the pairing request without disconnecting from the large-screen device and display the pairing request interface. In other words, the above step S110 can also be omitted, 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.
[0203] Optionally, in this embodiment, the profile channel established between the smartwatch and the large-screen device may only include an SPP channel. That is, step S111 is: in response to the user inputting an accept pairing instruction 1 in the pairing request interface, the smartwatch and the large-screen device are paired and an SPP channel is established.
[0204] Specifically, as described above, the smartwatch can learn that it is currently connected to the phone; the large-screen device can also learn that the smartwatch is connected to the phone by discovering the Bluetooth connection information in the broadcast. When the smartwatch and phone are already connected, the Bluetooth connection between the large-screen device and the smartwatch is generally only used for data transmission. Therefore, when establishing a profile channel, the smartwatch or large-screen device can initiate a request to the other end, and the two parties will perform authentication and encryption. After determining the current application scenario, only the SPP channel is established. This can simplify the process of establishing a connection between the large-screen device and the smartwatch, save profile channels, and save power and resources for both.
[0205] In this embodiment, a schematic diagram of the connection changes between the smart watch and the mobile phone and the large-screen device can be seen in Figure 12. As shown in Figure (a) in Figure 12, 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, an SPP channel, etc. Afterwards, the smart watch, the mobile phone and the large-screen device execute the method in this embodiment, the smart watch maintains a Bluetooth connection with the mobile phone, and establishes a Bluetooth connection with the large-screen device, as shown in Figure (b) in Figure 12. Optionally, the Bluetooth connection between the smart watch and the large-screen device may only include an SPP channel.
[0206] In this embodiment, similar to the previous embodiment, when the smartwatch is in a paired state, when the mobile phone connected to the smartwatch enters the target geographic fence and there is a trusted device of the mobile phone, the smartwatch can send a discoverable broadcast to the surrounding area, so that the large-screen device can discover the smartwatch without the user having to perform related operations such as disconnection and unbinding, thereby simplifying user operations. Furthermore, when the smartwatch receives a pairing request from the large-screen device, since the smartwatch 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 smartwatch 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 smartwatch at the same time, thereby improving the user experience.
[0207] It should be noted that the embodiments shown in Figures 6 and 11 are described as an example in which a user operates on the large-screen device side, discovers the smartwatch, and establishes a Bluetooth connection between the two. In some other embodiments, the user can also operate on the smartwatch side to establish a Bluetooth connection between the two. Specifically, referring to Figure 13, the above steps S105 to S111 can also be replaced by the following steps:
[0208] S121. The smartwatch displays device information of the large-screen device according to the notification information.
[0209] 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 based on 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.
[0210] The form of the first interface and the first control may be similar to the form of the device information and connection control of the smart device displayed in the large-screen device, and will not be repeated here.
[0211] S122 . In response to the user inputting 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.
[0212] Connection instruction 2 is used to instruct the smartwatch to establish a connection with the large-screen device. Optionally, the user can enter connection instruction 2 by clicking the connection control in the interface displayed on the watch.
[0213] S123. The smart watch displays a pairing confirmation interface.
[0214] After the smartwatch establishes a physical link with the large-screen device, a pairing confirmation interface is displayed on the screen. The pairing confirmation interface of the smartwatch can be similar to the pairing confirmation interface of the large-screen device, so I will not repeat it here.
[0215] 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.
[0216] Confirm pairing instruction 2 is used to instruct the smartwatch to initiate a pairing request with the large-screen device. After receiving the user's confirm pairing instruction 2, the smartwatch automatically disconnects from the Bluetooth connection with the mobile phone. Similar to step S110 above, in this embodiment, the smartwatch 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 further described here.
[0217] S125. The smart watch sends a pairing request to the large-screen device.
[0218] S126. In response to the pairing request sent by the smart watch, the large-screen device displays a pairing request interface.
[0219] 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.
[0220] Similar to the embodiment shown in FIG6 , 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.
[0221] In this embodiment, the process of establishing a connection between the smartwatch and the large-screen device is similar to the process of steps S106 to S111 described above. The difference is that in this embodiment, the user inputs the connection command and confirms the pairing command on the smartwatch, while the user inputs the acceptance command on the large-screen device. In other words, the user triggers the Bluetooth connection between the smartwatch and the large-screen device on the smartwatch.
[0222] It is worth noting that in addition to the beneficial effects described in Figures 6 and 11, 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 there is no need for the user to manually trigger the scan and discovery, which further simplifies user operations and improves user experience.
[0223] Scenario 2:
[0224] Another embodiment of the present application provides a method for connecting a wearable device. In this embodiment, when a Bluetooth connection is already established between a smartwatch and a mobile phone, a second Bluetooth connection can be established between the smartwatch and a large-screen device through cloud pairing. This is described in detail below with reference to the accompanying drawings.
[0225] For example, FIG14 is a flow chart of another example of a method for connecting a wearable device according to an embodiment of the present application. As shown in FIG14 , the method includes:
[0226] 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.
[0227] The server may be a cloud server. It is understood that when a mobile phone is logged into the first user account, it may upload device information, connection information, and the like of the wearable device currently connected to it to the cloud server. The connection information refers to information used by other devices to establish a near-field wireless communication connection with the wearable device. If the near-field wireless communication connection is a Bluetooth connection, the connection information may include a pairing key, etc.
[0228] The process of step S201 is also referred to as the mobile phone synchronizing the smart watch's information with the cloud.
[0229] S202. When the first user account is logged in on the large-screen device, in response to the user viewing the surrounding wireless communication devices on 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.
[0230] That is, the large-screen device and the mobile phone use the same user account (the first user account). When the large-screen device is logged in (i.e., 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 based on 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.
[0231] S203. The large-screen device displays device information of the smart watch.
[0232] 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.
[0233] Optionally, the large-screen device can display the device information of the smart watch on the device interface of the sports APP (also referred to as the third interface) in response to the user opening the sports APP and viewing the operation of the device. The device interface may include a control for entering a connection instruction (also referred to as a third control). Exemplarily, the device interface may be shown as 1501 in Figure 15, and the device information of the smart watch may be displayed in the device information card 1502. The device information card 1502 may include a connection control 1503, which is used for the user to enter a connection instruction.
[0234] 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.
[0235] 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 the connection control 1503 in the interface 1501 in Figure 15 through the remote control to input the connection instruction 3.
[0236] S205: The large-screen device sends a pairing request to the smart watch.
[0237] S206: In response to the pairing request, the smart watch displays a pairing request interface.
[0238] 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.
[0239] The process of steps S204 to S207 is similar to that of steps S108 to S111 and will not be repeated here. 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 information such as a random number, PIN code, MAC address, etc., which simplifies the pairing process.
[0240] 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.
[0241] In this embodiment, a schematic diagram of the connection changes between the smart watch, the mobile phone, and the large-screen device can be shown in Figure 16. Referring to Figure 16 (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 HFP channels, A2DP channels, SPP channels, etc. 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, as shown in Figure 16 (b). The profile channel between the smart watch and the large-screen device may only include the SPP channel.
[0242] In this embodiment, when the mobile phone establishes a Bluetooth connection with the smartwatch, the large-screen device connects to the smartwatch by obtaining the smartwatch's device information and pairing key from a server. Because the large-screen device and the mobile phone are logged into the same user account, the large-screen device is a trusted device. The smartwatch can simultaneously establish two Bluetooth connections with the mobile phone and the large-screen device. This does not affect the security of the mobile phone or the large-screen device, and does not require unbinding from the mobile phone. This simplifies user operations and allows users to interact with both devices simultaneously through the smartwatch, improving the user experience. Furthermore, the large-screen device obtains and displays the smartwatch's device information through a cloud server, eliminating the need for the user to scan and retrieve the smartwatch's device information through the large-screen device or the smartwatch. This further simplifies operations and improves the user experience. Furthermore, the large-screen device can obtain the smartwatch's pairing key through the cloud service, eliminating the need to negotiate a pairing key with the smartwatch, simplifying the pairing process. Furthermore, the mobile phone synchronizes smartwatch information with the cloud only after establishing a Bluetooth connection with the smartwatch. Therefore, while the large-screen device and the smartwatch are cloud-pairing, the mobile phone and the smartwatch remain connected via Bluetooth. In this case, the Bluetooth connection between the smartwatch and the large-screen device is generally only used for data transmission. Therefore, when establishing a profile channel, the large-screen device and the smartwatch only establish an SPP channel. This simplifies the process of establishing a connection between the large-screen device and the smartwatch, saves profile channels, and saves power consumption and resources for both.
[0243] Scenario 3:
[0244] 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 can connect their smartwatches or fitness bands to a large-screen device to perform group fitness or gaming.
[0245] For example, Figure 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. As shown in Figure 17, the large-screen device is installed with a sports APP, which may include team fitness games, such as multi-person racing games. Multiple users (team members) can wear smart watches respectively, and the smart watches establish connections with the large-screen devices respectively. During the game, the motion data of the players is 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 motion data of each player, and outputs the game interface and game results, etc.
[0246] The following describes the process of establishing connections between the large-screen device and each smartwatch in this scenario.
[0247] For example, FIG18 is a flowchart of another example of a wearable device connection method provided in an embodiment of the present application. As shown in FIG18 , the method includes:
[0248] S301. In response to a user inputting a team formation instruction (also referred to as a first instruction) on a large-screen device, the large-screen device sends a team formation BLE broadcast (also referred to as a second broadcast message) to surrounding devices.
[0249] The teaming command instructs the large-screen device to connect with multiple wearable devices and form a team. Teaming also means establishing a gaming or fitness group. Optionally, the teaming command can include the number of team members, that is, the number of wearable devices in the group.
[0250] Optionally, BLE broadcast is used to request multiple wearable devices in the surrounding area to establish a Bluetooth connection with the large-screen device and join the group. The BLE broadcast can 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 ongoing game, 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 gaming or team fitness, etc.
[0251] Exemplarily, FIG19 is a schematic diagram of an interface for playing a team fitness game through a large-screen device provided in an embodiment of the present application. As shown in FIG19(a), the sports interface 1901 of the sports APP may include an option 1902 for a multiplayer racing game. When the user selects the option 1902 for the multiplayer racing game through the remote control, the interface 1903 of the multiplayer racing game is entered, as shown in FIG19(b). 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's selection of a 4-person team game as an example, in response to the user's selection, the large-screen device starts sending a team BLE broadcast to the surrounding devices.
[0252] S302. After each smart watch (taking smart watches a, b, c, and d as an example in FIG18 ) receives the team BLE broadcast sent by the large-screen device, it displays inquiry information and prompt information according to the team BLE broadcast.
[0253] The query message is used to ask the user whether to agree to establish a connection between the smartwatch and the large-screen device and join the team. The prompt message is used to prompt that after the smartwatch and the large-screen device are connected, the data of the smartwatch will be transmitted to the large-screen device.
[0254] In a specific embodiment, after the smartwatch receives the team BLE broadcast sent by the large-screen device, the interface diagram may be as shown in Figure 20 (a). The interface includes a query message 2001 and a prompt message 2002. The query message 2001 includes an approval control 2003 and a rejection control 2004.
[0255] S303: In response to each user inputting a connection and teaming consent instruction in the interface of the smart watch, each smart watch sends a connection consent message and a teaming consent message to the large-screen device.
[0256] The "Connect" message indicates that the smartwatch agrees to establish a connection with the large-screen device. The "Teaming" message indicates that the smartwatch agrees to connect and form a team, that is, agrees to join the group.
[0257] It can be understood that in this embodiment, the connection consent message and the team consent message are triggered by a user instruction - the connection consent and team consent instruction. In other embodiments, the connection consent message and the team consent message can also be triggered by two instructions respectively. In addition, the connection consent message and the team consent message can be two separate messages sent to the large-screen device respectively, or they can be two parts of the same message and sent to the large-screen device through one message. This embodiment of the application does not impose any restrictions on this.
[0258] For example, the user may input an instruction to agree to connect and form a team by clicking the agree control 2003 in FIG. 20 ( a ).
[0259] S304: The large-screen device establishes a physical link with each smart watch in response to the connection agreement message and the teaming agreement message.
[0260] 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.
[0261] Specifically, after the physical link is established, the large-screen device sends a pairing request to the smartwatch, which receives the request, and the two enter the pairing phase. After pairing is complete, the two establish an SPP channel, completing the Bluetooth connection between the large-screen device and the smartwatch. After the Bluetooth connection is established, the smartwatch's interface may appear as shown in Figure 20 (b), and the large-screen device's interface may display information about team members, i.e., connected smartwatches, as shown in Figure 19 (c).
[0262] After the Bluetooth connection is established, the large-screen device adds the smartwatch to the group.
[0263] S306. Each smart watch collects the user's exercise data.
[0264] Specifically, each smartwatch can collect the user's motion data in real time. Optionally, the user's motion 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.
[0265] 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.
[0266] 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 the game or fitness content based on the motion data.
[0267] In this embodiment, a large-screen device transmits a teaming BLE broadcast to surrounding devices, and the smartwatch displays a prompt and inquiry message in response to the teaming BLE broadcast. When the user enters a connection consent and teaming command in the smartwatch interface, this indicates that the user trusts the large-screen device, indicating that the large-screen device is a trustworthy device. Consequently, the smartwatch directly establishes a Bluetooth connection with the large-screen device. This allows the large-screen device to establish Bluetooth connections with multiple smartwatches simultaneously, facilitating data transmission from multiple smartwatches to the large-screen device, meeting user needs in scenarios such as team gaming and improving the user experience. Furthermore, since only data is transmitted between the smartwatch and the large-screen device in these team gaming or fitness scenarios, the profile channel between the large-screen device and the smartwatch can consist solely of an SPP channel. This not only conserves resources and power consumption for both the smartwatch and the large-screen device, but also further reduces the risk of user information loss, thereby further improving user information security. Furthermore, by displaying prompts and inquiries in the smartwatch interface to inform the user of usage scenarios and other information, user interaction is enhanced, user information security is improved, and the user experience is improved.
[0268] In another embodiment, before multiple smart watches establish a connection with the large-screen device, if the smart watch has already established a Bluetooth connection with another terminal device (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. This makes it easier for users to interact with both the mobile phone and the large-screen device through the smart watch, improving 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 both the smart watch and the large-screen device.
[0269] In this embodiment, the process of establishing a Bluetooth connection between a large-screen device and multiple wearable devices can be shown in Figure 21. As shown in Figure 21 (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, as shown in Figure 21 (b). Optionally, the Bluetooth connection between each smart watch and the large-screen device may only include an SPP channel.
[0270] In another embodiment, before the user enters a team formation instruction on the large-screen device, if the large-screen device has established a Bluetooth connection with a smartwatch, the smartwatch, upon receiving the BLE broadcast sent by the large-screen device, confirms that it has established a connection with the large-screen device. The smartwatch maintains the connection and displays a query message based on the BLE broadcast, asking the user whether to agree to team formation, that is, whether to agree to join the group. After the user enters the team formation agreement instruction, the smartwatch sends a team formation agreement message to the large-screen device. After receiving the team formation agreement message sent by the smartwatch, the large-screen device adds the smartwatch to the group.
[0271] 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, a data transmission channel (i.e., a BLE data transmission channel) under its protocol can also be established 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 establishing a transmission channel using the method provided in the embodiment of the present application, a transmission channel corresponding to the required function under the protocol is established.
[0272] In addition, for a wearable device that is a dual-mode Bluetooth device, when simultaneously establishing a connection with a large-screen device and a mobile phone using the method provided in the embodiments of this application, a connection can be established with the mobile phone through the classic Bluetooth device and with the large-screen device through the BLE Bluetooth device. Alternatively, a connection can be established with the large-screen device through the classic Bluetooth device and with the mobile phone through the BLE Bluetooth device, thereby increasing the flexibility of use and the applicability of the method.
[0273] 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. Those skilled in the art should easily appreciate 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 a hardware or computer software driven hardware manner 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 be beyond the scope of the present application.
[0274] In the embodiment of the present application, the wearable device, the first terminal device, and the second terminal device can be divided into functional modules 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-mentioned 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.
[0275] 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.
[0276] The wearable device, the first terminal device, and the second terminal device provided in this embodiment are used to execute the above-mentioned wearable device connection method, and thus can achieve the same effect as the above-mentioned implementation method.
[0277] 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.
[0278] For example, FIG22 is a schematic diagram of the structure of a wearable device 100 provided in an embodiment of the present application. As shown in FIG22, 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 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 photoplethysmography (PPG) heart rate sensor 180E, an ambient light sensor 180F, etc.
[0279] It is understood that the structures illustrated in the embodiments of the present application do 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, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0280] 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. The different processing units may be independent devices or integrated into one or more processors. The controller may generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.
[0281] The processor 110 may further include a memory for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory.
[0282] 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 notification information sent by a terminal device. The notification information is used to indicate the presence of trusted devices in the surrounding area. The discoverable broadcast may carry device information of the wearable device 100 and Bluetooth connected information (i.e., 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.
[0283] The internal memory 121 can be used to store computer executable program code, which includes instructions. The internal memory 121 may include a program storage area and a data storage area. 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.
[0284] It is understood 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 a different interface connection method from the above embodiment, or a combination of multiple interface connection methods.
[0285] 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.
[0286] 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, which 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.
[0287] Antenna 1 is used to transmit and receive electromagnetic wave signals. Each antenna in wearable device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, an antenna can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antenna can be used in conjunction with a tuning switch.
[0288] The wireless communication module 150 can be one or more devices that integrate at least one communication processing module. The wireless communication module 150 receives electromagnetic waves via an antenna, frequency-modulates and filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 150 can also receive signals to be transmitted from the processor 110, frequency-modulate them, amplify them, and convert them into electromagnetic waves for radiation via the antenna.
[0289] Wearable device 100 implements display functionality through a GPU, display screen 171, and an application processor. The GPU is a microprocessor for image processing that connects display screen 171 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.
[0290] 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 motion.
[0291] 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 (i.e., x, y, and z axes) can be determined by the gyro sensor 180B. The gyro sensor 180B can be used to detect the user's motion state.
[0292] Accelerometer 180C can detect the magnitude of acceleration of wearable device 100 in all directions (generally three axes). It can also detect the magnitude and direction of gravity when wearable device 100 is stationary. It can also be used to identify the wearable device's posture, for applications such as step counting and motion status feedback.
[0293] The touch sensor 180D is also called a "touch panel". The touch sensor 180D can be set on the display screen 171. 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, at a different location from the display screen 194, for example, on the side of the dial of a smart watch.
[0294] The PPG heart rate sensor 180E detects the intensity of reflected light absorbed by human blood and tissue, charting changes in vascular volume during the cardiac cycle. This produces a pulse waveform, which is then used to calculate heart rate. The PPG heart rate sensor 180E is used to monitor user health.
[0295] 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 based on the perceived ambient light brightness. The ambient light sensor 180F can also be used to automatically adjust the white balance when taking photos. The ambient light sensor 180F can also cooperate with a proximity light sensor (not shown) to detect whether the wearable device 100 is being worn.
[0296] The structure of the first terminal device 200 is described below.
[0297] For example, FIG23 is a schematic diagram of the 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, as shown in FIG23, 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 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.
[0298] It should be understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the first terminal device 200. In other embodiments of this application, the first terminal device 200 may include more or fewer components than illustrated, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0299] 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). The different processing units may be independent devices or integrated into one or more processors.
[0300] 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.
[0301] The processor 210 may further include a memory for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory.
[0302] In an embodiment of the present application, the processor 210 can cooperate with other modules to determine that the first terminal device has entered the target geofence and that there is a trusted device within the target geofence based on the information of at least one preset geofence and the device information within the trust ring, when a Bluetooth connection has been established between the wearable device and the first terminal device, and a notification message is sent to the wearable device.
[0303] 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.
[0304] Antenna 2 and Antenna 3 are used to transmit and receive electromagnetic wave signals. The structures of Antenna 2 and Antenna 3 in Figure 23 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 antenna utilization. For example, Antenna 2 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antenna can be used in conjunction with a tuning switch.
[0305] The wireless communication module 260 can provide wireless communication solutions for the first terminal device 200, including WLAN (such as Wi-Fi network), Bluetooth, GNSS, FM, NFC, IR, etc. The wireless communication module 260 can be one or more devices that integrate at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 3, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 210. The wireless communication module 260 can also receive signals to be transmitted from the processor 210, frequency modulate them, amplify them, and convert them into electromagnetic waves for radiation via the antenna 3.
[0306] That is to say, the wireless communication module 260 is capable of achieving short-range wireless communication, or in other words, the wireless communication module 260 includes a short-range wireless communication module. In an 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, which may be a classic Bluetooth device, a BLE Bluetooth device, or a dual-mode Bluetooth device. This embodiment of the present application does not impose any restrictions on this.
[0307] 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-CDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. 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).
[0308] The first terminal device 200 implements display functionality through a GPU, display screen 294, and an application processor. The GPU is a microprocessor for image processing that 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 that execute program instructions to generate or modify display information.
[0309] The display screen 294 is used to display images, videos, etc. The display screen 294 includes a display panel.
[0310] The first terminal device 200 can realize the shooting function through the ISP, camera 293, video codec, GPU, display screen 294 and application processor.
[0311] The internal memory 221 can be used to store computer executable program code, and the executable program code includes 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 can store an operating system, an application required for at least one function (such as a sports application), etc. The data storage area can 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.
[0312] The structure of the second terminal device 300 is described below.
[0313] For example, FIG24 is a schematic diagram of the structure of a second terminal device 300 provided in an embodiment of the present application. The second terminal device 300 is taken as an example of a large-screen device for illustration. The large-screen device involved in the embodiment of the present application can 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 can also be other devices capable of establishing a short-range wireless communication connection, without limitation herein.
[0314] As shown in FIG24 , 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.
[0315] It should 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, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
[0316] 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. The different processing units may be independent devices or integrated into one or more processors.
[0317] 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.
[0318] Processor 310 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 310 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 310. If processor 310 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 310 latency, and thus improves system efficiency.
[0319] The processor 310 can control the execution of application code to implement the functions of the second terminal device 300 in this embodiment. For example, after the second terminal device 300 receives a 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.
[0320] The wireless communication functionality of the second terminal device 300 can be implemented using antenna 4, wireless communication module 350, a modem processor, and a 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 antenna utilization. For example, one of the multiple antennas can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antenna can be used in conjunction with a tuning switch.
[0321] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted 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 being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through the audio module 360 (not limited to the speaker 360A, the speaker interface 360B, etc.) or displays an image or video through the 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.
[0322] 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 technology (IR), etc. applied on 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, frequency modulates and filters the electromagnetic wave signal, 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, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 4.
[0323] 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, which can 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 restrictions on this.
[0324] The second terminal device 300 implements display functionality through a GPU, display screen 382, and an application processor. The GPU is a microprocessor for image processing that 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 that execute program instructions to generate or modify display information.
[0325] The display screen 382 is used to display images, videos, etc. For example, after the second terminal device 300 receives a pairing request from the wearable device, the display screen 382 displays the pairing request and prompts the user whether to establish a Bluetooth connection with the wearable device. If the second terminal device 300 receives an operation from the user to instruct to establish 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.
[0326] The internal memory 321 can be used to store computer-executable program code, which includes instructions. The processor 310 executes the instructions stored in the internal memory 321 to execute various functional applications and data processing of the second terminal device 300. The internal memory 321 can include a program storage area and a data storage area. The program storage area can store the operating system, at least one application required for a function, and the like. The data storage area can store data generated during the use of the second terminal device 300, and the like.
[0327] The software architecture of the wearable device 100 , the first terminal device 200 , and the second terminal device 300 is described below.
[0328] The software systems 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 microkernel architecture, a microservice architecture, or a cloud architecture. This embodiment of the application takes the Android system with a 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.
[0329] Figure 25 is a software structure diagram of the wearable device 100 according to an embodiment of the present application. The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer. The application layer can include a series of application packages.
[0330] As shown in FIG25 , the application package may include applications such as calendar, clock, sleep monitoring, WLAN, and Bluetooth.
[0331] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.
[0332] As shown in FIG25 , 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.
[0333] The window manager is used to manage window programs. The window manager can obtain the display size, determine whether there is a status bar, lock the screen, take screenshots, etc.
[0334] Content providers are used to store and retrieve data and make it accessible to applications. Data can include images, audio, browsing history, and bookmarks.
[0335] The view system includes visual controls, such as controls for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views.
[0336] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, etc.
[0337] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically, without requiring user interaction. For example, the Notification Manager can be used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar of the system as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include displaying text messages in the status bar, emitting a sound, vibrating wearable devices, or flashing indicator lights.
[0338] The Bluetooth process may include Bluetooth service, Bluetooth profile, etc.
[0339] The Android runtime includes the core library and the virtual machine. The Android runtime is responsible for scheduling and management of the Android system.
[0340] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.
[0341] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.
[0342] 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 protocol stack.
[0343] The surface manager is used to manage the display subsystem and provide fusion of 2D and 3D layers for multiple applications.
[0344] The media library supports playback and recording of a variety of common audio and video formats, as well as static image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.
[0345] The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.
[0346] A 2D graphics engine is a drawing engine for 2D drawings.
[0347] 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 the implementation of various profiles.
[0348] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, Wi-Fi driver, Bluetooth driver, audio driver, and sensor driver.
[0349] In the embodiment of the present application, taking scenario 1 as an example, the wearable device 100 can receive 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. Furthermore, the Bluetooth application sends a discoverable broadcast to the large-screen device through the Bluetooth process, Bluetooth protocol stack, and Bluetooth driver based on the notification information.
[0350] Figure 26 is a block diagram of the software architecture of the first terminal device 200 according to an embodiment of the present application. Similar to the wearable device 100, the software architecture of the first terminal device 200 may include, from top to bottom, an application layer, an application framework layer, an Android runtime and system libraries, and a kernel layer. The application layer may include a series of application packages.
[0351] As shown in FIG26 , 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.
[0352] The sports application may be, for example, sports health, etc. The positioning application user obtains the geographic location of the first terminal device 200 .
[0353] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.
[0354] As shown in FIG26 , 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.
[0355] Content providers are used to store and retrieve data and make it accessible to applications. Data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.
[0356] The view system includes visual controls, such as those for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views. For example, a display interface containing a text notification icon might include a view for displaying text and a view for displaying images.
[0357] The phone manager is used to provide communication functions for the first terminal device 200, such as management of call status (including answering, hanging up, etc.).
[0358] The resource manager provides various resources for applications, such as localized strings, icons, images, layout files, video files, and so on.
[0359] 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.
[0360] 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 geo-fence and there are trusted devices nearby.
[0361] 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.
[0362] The functions of each module in the system library can be found in the wearable device 100 and will not be described in detail.
[0363] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, Wi-Fi driver, Bluetooth driver, audio driver, and sensor driver.
[0364] Specifically, in an embodiment of the present application, the first terminal device 200 can obtain the geographic location of the first terminal device 200 through a positioning application based on the above-mentioned software architecture, and determine, based on the geographic location, whether the first terminal device 200 has entered a preset geofence. A Bluetooth application is used to determine whether there are any devices trusted by the mobile phone within the current geofence. When it is determined that the first terminal device 200 has entered a target geofence (any preset geofence) and that there are any devices trusted by the mobile phone within the target geofence, the subscription manager sends a notification message to the wearable device 100. The notification message carries the device information of the trusted device.
[0365] Figure 27 is a block diagram of the software structure of the second terminal device 300 according to an embodiment of the present application. The system of the second terminal device 300 can be divided into four layers: the application layer, the application framework layer, the Android runtime and system library, and the kernel layer. The application layer can include a series of application packages.
[0366] As shown in FIG27 , 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.
[0367] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.
[0368] As shown in FIG27 , 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.
[0369] The functions of each module of the application framework layer can be found in the wearable device 100 and the first terminal device 200 and will not be repeated here.
[0370] The system library can include multiple functional modules, such as a surface manager, media libraries, a 3D graphics processing library (e.g., OpenGL ES), a 2D graphics engine (e.g., SGL), and a Bluetooth protocol stack.
[0371] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, Wi-Fi driver, Bluetooth driver, audio driver, and sensor driver.
[0372] In an embodiment of the present application, the second terminal device 300 can, based on the above-mentioned software architecture, 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 to display the interface of the Bluetooth function to the user. Based on this interface, the user can input scanning and discovery instructions, connection instructions, confirmation pairing instructions, acceptance of 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 an 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.
[0373] An embodiment of the present application also provides a computer-readable storage medium, which stores a computer program. 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.
[0374] An embodiment of the present application also provides a computer program product. When the computer program product is run on a computer, the computer is caused to execute the above-mentioned related steps to implement the connection method of the wearable device in the above-mentioned embodiment.
[0375] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory to enable the chip to execute the connection method of the wearable device in the above-mentioned method embodiments.
[0376] 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.
[0377] 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 distributed and completed by 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.
[0378] In the several embodiments provided in this 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 merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, 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.
[0379] Units described as separate components may or may not be physically separate, and 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 places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.
[0380] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0381] 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 and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.
[0382] The above content is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of the present application. Therefore, the scope of protection of the present application should be based on the scope of protection 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 only includes 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, 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.
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
Patent Citations
Communication method for multiple bluetooth devices and forwarding method for bluetooth device matching information
CN104104414A
Method for establishing communication group and wearable device capable of establishing communication group
CN104811903A
Pairing method and device
CN112615891A
Bluetooth connection method, device and system
CN113225693A
Bluetooth connection method and device, electronic equipment and storage medium
CN115996371A
Cited By
Device grouping method and system, electronic device, storage medium and computer program
CN121357729A
Security control method, and device, medium, program product, apparatus and chip
WO2026152755A1
Connection method, system and related apparatus
WO2026208737A1
