CN119071788A - Wearable device connection method and device - Google Patents
Wearable device connection method and device Download PDFInfo
- Publication number
- CN119071788A CN119071788A CN202310647974.8A CN202310647974A CN119071788A CN 119071788 A CN119071788 A CN 119071788A CN 202310647974 A CN202310647974 A CN 202310647974A CN 119071788 A CN119071788 A CN 119071788A
- Authority
- CN
- China
- Prior art keywords
- connection
- terminal device
- information
- wearable device
- wearable
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/50—Secure pairing of devices
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/08—Access restriction or access information delivery, e.g. discovery data delivery
- H04W48/10—Access restriction or access information delivery, e.g. discovery data delivery using broadcasted information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W48/00—Access restriction; Network selection; Access point selection
- H04W48/16—Discovering, processing access restriction or access information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/14—Direct-mode setup
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Security & Cryptography (AREA)
- Telephone Function (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the application provides a connection method and device of wearable equipment, the method is executed by the wearable equipment, the first connection is established between the wearable equipment and first terminal equipment, the method comprises the steps of receiving notification information sent by the first terminal equipment, wherein the notification information is used for indicating surrounding second terminal equipment with a trust relationship with the first terminal equipment, the notification information is received after the wearable equipment enters a preset geographic area, responding to the notification information, sending a first broadcast message to the surrounding equipment, displaying a first interface according to the notification information, wherein the first interface comprises a first control, responding to a connection instruction input by clicking the first control by a user, establishing second connection with the second terminal equipment, wherein the second connection is short-range wireless communication connection based on a second communication protocol, or responding to a first request message sent by the second terminal equipment, and establishing third connection with the second terminal equipment. The method can simplify the user operation and improve the user experience.
Description
Technical Field
The application relates to the technical field of electronics, in particular to a method and equipment for connecting wearable equipment.
Background
With the advancement of technology, wearable devices (such as smart watches, sport bracelets, etc.) are increasingly used, and functions are also increasingly enriched, for example, body-feeling fitness can be performed by connecting the wearable device with a terminal device. Specifically, the wearable device can be connected with terminal devices such as a mobile phone, a large-screen device or a tablet personal computer, the wearable device collects motion data of a user and transmits the motion data to the terminal device, and the terminal device displays or feeds back actions of the user according to the motion data.
Generally, a wearable device can only establish connection with a terminal device, and if the connection between the wearable device and other terminal devices is to be realized, a user needs to perform a relatively complex operation. Taking the smart watch as an example, under the condition that the smart watch is connected with the mobile phone, if a user needs to connect the smart watch with large screen equipment (such as a smart television), the connection between the smart watch and the mobile phone needs to be disconnected firstly, and the binding relationship between the smart watch and the mobile phone is released, so that the smart watch can enter a paired state. And then, the user controls the large-screen device to search the intelligent watch, and inputs a connection instruction through the large-screen device to instruct the large-screen device to establish connection with the intelligent watch. This process is cumbersome and the user experience is poor.
Disclosure of Invention
The application provides a connection method and equipment of wearable equipment, which can simplify user operation and improve user experience.
In a first aspect, the application provides a connection method of a wearable device, the method is executed by the wearable device, the wearable device and a first terminal device have established a first connection, the first connection is a short-range wireless communication connection based on a first communication protocol, the method comprises the steps of receiving notification information sent by the first terminal device, the notification information being used for indicating surrounding second terminal devices with a trust relationship with the first terminal device, the notification information being received after the wearable device enters a preset geographic area, sending a first broadcast message to surrounding devices in response to the notification information, the first broadcast message being used for the surrounding devices to find the wearable device, displaying a first interface according to the notification information, the first interface comprising a first control, responding to a connection instruction input by a user through clicking the first control, establishing a second connection with the second terminal device, the second connection being a short-range wireless communication connection based on the second communication protocol, or responding to a first request message sent by the second terminal device, establishing a third connection with the second terminal device, the third connection being a short-range wireless communication connection based on the third communication protocol.
Optionally, the first terminal device may be, for example, a mobile phone, a tablet computer, or the like. 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, or the like.
Optionally, the first communication protocol, the second communication protocol, and the third wireless communication protocol may be one of a bluetooth (blue) protocol, a Matter protocol, a Zigbee (Zigbee) protocol, a Wi-Fi (WIRELESS FIDELITY) protocol, a Thread protocol, or a Mesh (Mesh) protocol, respectively. The first communication protocol and the second communication protocol may be the same protocol or different protocols. Alternatively, the first communication protocol and the third communication protocol may be the same protocol or different protocols.
Optionally, the notification information may carry device information of the second terminal device. The device information of the second terminal device includes, but is not limited to, a media access control (MEDIA ACCESS control, MAC) address. The wearable device may display the first interface according to device information of the second terminal device in the notification information. The first interface may include device information of the second terminal device. In addition, in the case that the notification information carries the device information of the second terminal device, the wearable device may directionally send the discoverable broadcast to the second terminal device according to the device information of the second terminal device, that is, the discoverable broadcast carries the device information (such as the MAC address) of the second terminal device. The smart watch directionally transmits discoverable broadcast to the second terminal equipment, and after other equipment receives the discoverable broadcast, determines that the MAC address carried in the broadcast message is inconsistent with the self MAC address, discards the discoverable broadcast message and does not continue to analyze, so that the interference of the wearable equipment to other surrounding equipment can be reduced, the power consumption of the surrounding equipment is saved, and the user experience is improved.
Optionally, the first request message is used to request a connection to be established with the wearable device. When the third communication protocol is a bluetooth protocol, the first request message may be a pairing request.
In general, when a wearable device has established a connection with a terminal device, the wearable device is in a paired state, and in consideration of the security of user information, the wearable device does not send discoverable broadcast to the surroundings any more, and only after the user disconnects the connection and releases the binding relationship between the connection, the wearable device is triggered to send discoverable broadcast to the surroundings again. In the method provided by the first aspect of the present application, under the condition that the first terminal device and the wearable device have established bluetooth connection, the second terminal device having a trust relationship with the first terminal device in the current scene is obtained by receiving the notification information sent by the first terminal device. Under the scene, the wearable device does not break the binding relation with the first terminal device, and the connection with the second terminal device is re-established without affecting the safety of the user information, so that the wearable device sends discoverable broadcast to surrounding devices, and the wearable device can be scanned and discovered by the wearable device. And then, the user operates the second terminal device or the wearable device side, so that the second terminal device and the wearable device are connected in a short-distance wireless communication mode. That is, in this embodiment, when the wearable device has established the first connection with the first terminal device, the wearable device may send the discoverable broadcast to the surroundings without performing operations of disconnecting and unbinding by the user, so that the second connection or the third connection with the second terminal device may be established, the user operation is simplified, the user experience is improved, and the security of the second connection or the third connection established between the wearable device and the second terminal device is high. In addition, in the embodiment, the first interface is displayed according to the notification information, so that the user can trigger to connect the second terminal device based on the input instruction of the first interface, the user does not need to execute the operation of scanning to find the second terminal device on the wearable device side, the user operation is further simplified, and the user experience is improved.
In a possible implementation, the method further comprises automatically disconnecting the physical link with the first terminal device before establishing the connection with the second terminal device.
That is, before "establishing the 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. Or before the third connection is established with the second terminal device, the method further comprises automatically disconnecting the physical link with the first terminal device in response to the first request message sent by the second terminal device.
In the implementation mode, the wearable device receives the notification information sent by the first terminal device, so that the current application scene can be determined as that the wearable device is connected with the first terminal device, trusted devices exist in the current surrounding environment, and the trusted devices are the second terminal device. In this scenario, if the wearable device receives a connection instruction that indicates that the user establishes a connection with the second terminal device, or receives a first request message (for example, a pairing request) of the second terminal device, it may be confirmed that the connection between the wearable device and the second terminal device does not affect the security of the user information. Therefore, the wearable device can automatically disconnect the connection with the first terminal device without displaying an interface for inquiring the user or manual operation by the user, and then establish the connection with the second terminal device. Therefore, the short-distance wireless communication connection of the wearable device is switched from the first terminal device to the second terminal device, and the user does not need to execute related operations of disconnection and unbinding, so that the user operation is simplified, and the user experience is further improved. On the other hand, in such a scenario, the wearable device may confirm that the security of the user information is not affected even if the wearable device does not unbind from the first terminal device. Therefore, the wearable device can only disconnect the physical link with the first terminal device, so that when the subsequent wearable device is reconnected with the first terminal device, the establishment phase (for example, the pairing phase) of the logic link is not required to be re-entered, the related operation (for example, the pairing confirmation operation) for establishing the logic link is not required to be executed by the user, the execution programs of the wearable device and the first terminal device are saved, the user operation is simplified, and the user experience is improved.
In a possible implementation, the connection with the second terminal device is established, comprising maintaining the first connection with the first terminal device, and establishing the connection with the second terminal device, the connection of the wearable device with the second terminal device comprising only the data transmission channel.
That is, the wearable device does not disconnect the first connection with the first terminal device, in which case only the data transmission channel is included in the second or third connection established by the wearable device with the second terminal device.
In the implementation manner, after knowing the current application scene according to the notification information, the wearable device determines that the connection security with the second terminal device is high, so that the wearable device can directly establish the second path close range wireless communication connection with the second terminal device without disconnecting the connection with the first terminal device, and the user can conveniently interact with the first terminal device and the second terminal device through the wearable device at the same time, and the user experience is improved. Moreover, after determining the current application scenario, the wearable device only establishes a data transmission channel with the second terminal device. Therefore, the connection process between the wearable device and the second terminal device can be simplified, channels are saved, and the power consumption and resources of the wearable device and the second terminal device are saved.
In one 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 (serial port profile, SPP) channel.
In a possible implementation, the first communication protocol and the third communication protocol are the same communication protocol, or the first communication protocol and the second communication protocol are the same communication protocol. In this way, the wearable device adopts the same communication protocol to communicate with the first terminal device and the second terminal device, so that the wearable device is convenient to manage and operate, and resources and power consumption are saved.
In a possible implementation manner, the first broadcast message carries first information, where the first information is used to characterize that the wearable device has established a first connection with the first terminal device.
It can be understood that the first broadcast carries the first information, and after receiving the first broadcast message, the second terminal device can learn that the current application scenario, that is, the wearable device has established connection with the first terminal device, and devices with trust relationship with the first terminal device exist around the wearable device, so that the second terminal device can determine the display interface according to the scenario. For example, in general, in this scenario, the probability that the user connects the wearable device in the second terminal device is relatively high, so that the second terminal device may pop up the information interface of the wearable device after determining the current application scenario according to the first information, remind the user whether to connect, etc., so as to facilitate the user operation and improve the user experience.
In a second aspect, the application provides a method for connecting wearable equipment, the method is executed by first terminal equipment, the first terminal equipment and the wearable equipment have established first connection, the method comprises the steps of determining that second terminal equipment with trust relationship with the first terminal equipment exists around after the first terminal equipment enters a preset geographic area; after determining that the second terminal equipment with the trust relationship with the first terminal equipment exists around, sending notification information to the wearable equipment, wherein the notification information is used for indicating that the second terminal equipment with the trust relationship with the first terminal equipment exists around.
In the method provided by the second aspect of the present application, if the first terminal device enters a preset geographic area and there is a second terminal device having a trust relationship with the first terminal device around the first terminal device, notification information is sent to the wearable device under the condition that the first terminal device establishes a connection with the wearable device. Thus, the wearable device is convenient to acquire the current scene, so that the wearable device is convenient to send discoverable broadcasting to the second terminal device, the user is not required to execute operations of disconnection and unbinding, the user operation is simplified, and the user experience is improved.
In a possible implementation manner, determining that second terminal equipment with a trust relationship with first terminal equipment exists around includes obtaining historical scanning information of the first terminal equipment, wherein the historical scanning information is used for representing equipment information of the first terminal equipment which is found by scanning in a preset geographic area in a historical time period, comparing information of a plurality of equipment with the trust relationship with the first terminal equipment with the historical scanning information, and determining that the second terminal equipment with the trust relationship with the first terminal equipment exists around if the information of the second terminal equipment exists in the historical scanning information and the information of the plurality of equipment.
A plurality of devices having a trust relationship with the first terminal device, i.e. devices within the trust ring of the first terminal device.
In the implementation manner, by acquiring the history scanning information and determining whether the second terminal equipment is equipment with a trust relationship with the first terminal equipment according to the history scanning information, the first terminal equipment is not required to scan surrounding equipment to acquire equipment information of the surrounding equipment, and the power consumption of the first terminal equipment is saved.
The method comprises the steps of receiving a first broadcast message sent by the wearable device, wherein the first broadcast message carries first information, the first broadcast message is used for surrounding devices to find out the wearable device, the first information is used for representing that the wearable device and the first terminal device have established first connection, the first connection is short-range wireless communication connection based on a first communication protocol, responding to the first broadcast message, displaying a second interface according to the first information, the second interface comprises a second control, responding to a connection instruction input by a user through selecting the second control, and sending a first request message to the wearable device, wherein the first request message is used for requesting to establish third connection with the wearable device, and the third connection is short-range wireless communication connection based on the third communication protocol.
In the method provided by the third aspect of the present application, the first information is carried in the first broadcast message, and the second terminal device can directly display the second interface according to the first information in the first broadcast message, so that the user can trigger the connection between the second terminal device and the wearable device through the second interface. Therefore, the user does not need to perform scanning discovery operation on the second terminal equipment, the user operation is simplified, and the user experience is improved.
In one possible implementation, the first communication protocol and the third communication protocol are the same communication protocol.
In a possible implementation, the third connection comprises only a data transmission channel.
In the implementation manner, the third connection only comprises the data transmission channel, so that the channel can be saved, the connection flow of the wearable equipment and the second terminal equipment is saved, and equipment resources and power consumption are saved.
In one possible implementation, the first communication protocol and the third communication protocol are both bluetooth protocols, and the data transmission channel is a serial port configuration file SPP channel.
In a fourth aspect, the application provides a connection method of a wearable device, the method is executed by a second terminal device, the distance between the wearable device and the second terminal device is a distance capable of short-range wireless communication, the second terminal device logs in a first user account, the method comprises the steps of responding to operation of a user for checking surrounding wireless communication devices, obtaining device information of the wearable device and connection information for establishing connection with the wearable device from a server according to the first user account, uploading the device information and the connection information to the server by the first terminal device through the first user account, displaying a third interface according to the device information, wherein the third interface comprises a third control, responding to a connection instruction input by the user through selecting the third control, and establishing third connection with the wearable device according to the connection information, wherein the third connection is short-range wireless communication connection based on a third communication protocol.
Alternatively, in the case where the third communication protocol is the bluetooth protocol, the connection information may be, for example, a pairing key.
Alternatively, the server may be a cloud service, or referred to as a cloud platform, cloud, or the like.
In the method provided by the fourth aspect of the present application, the second terminal device can obtain the device information and the connection information of the wearable device from the server through the first user account, and further according to the information display interface, the connection with the wearable device is achieved in response to the operation of the user. The whole process can display the third interface without the operation of disconnecting and unbinding by a user and the scanning discovery operation by the user, thereby simplifying the user operation and improving the user experience. In addition, the second terminal equipment can directly establish connection with the wearable equipment according to the connection information, the connection information does not need to be acquired from the wearable equipment, and the connection process is simplified.
In a possible implementation manner, the first terminal device and the wearable device have established a first connection, the first connection is a short-range wireless communication connection based on a first communication protocol, and the third connection only comprises a data transmission channel.
In the implementation manner, the third connection only comprises the data transmission channel, so that the channel can be saved, the connection flow of the wearable equipment and the second terminal equipment is saved, and equipment resources and power consumption are saved.
In one possible implementation, the third communication protocol is a bluetooth protocol, and the data transmission channel includes an SPP channel.
In one possible implementation, the first communication protocol is the same as the third communication protocol.
In a fifth aspect, the application provides a connection method of wearable devices, which is executed by a second terminal device, and comprises the steps of responding to a first instruction of a user, sending a second broadcast message to surrounding devices, wherein the second broadcast message is used for requesting the surrounding wearable devices to establish close range wireless communication connection with the second terminal device and joining a group, the wearable devices comprise a first wearable device and a second wearable device, the first wearable device is a device which does not establish close range wireless communication connection with the second terminal device in the wearable devices, the second wearable device is a device which has established a fourth connection with the second terminal device in the wearable devices, the fourth connection is a close range wireless communication connection based on a fourth communication protocol, receiving a consent connection message sent by the first wearable device and a first peer group message, wherein the consent connection message characterizes the first wearable device consent to establish connection with the second terminal device, the first wearable device is joined to the group, responding to the consent connection message and the first wearable device is a fifth wearable device, the second wearable device is joined to the group, the wearable device is joined to the wearable device, and the wearable device is joined to the group, and the wearable device is joined to the wearable device.
The method provided by the fifth aspect of the application realizes that the second terminal equipment is connected with a plurality of wearable equipment at the same time, meets the use requirements of users in the scenes of team game, team fitness and the like, and improves the user experience. In addition, when the connection is established, the second wearable device establishes the fourth connection with the second terminal device, so that the first wearable device and the second terminal device only establish a data transmission channel to meet the use requirement (data transmission) of a user in the scene, the process of establishing the connection between the second terminal device and the first wearable device can be saved, and resources and power consumption are saved.
In a possible implementation manner, the fourth connection includes a data transmission channel, and further includes at least one of a call transmission channel and an audio transmission channel.
Alternatively, in the case where the fourth communication protocol is a 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 (advanced audio distribution profile, A2 DP) channel.
In this implementation manner, the fourth connection includes at least one of a call transmission channel and an audio transmission channel in addition to the data transmission channel, so that the call requirement and the audio transmission requirement of the user can be met, and the user experience is further improved.
In one possible implementation, the fifth communication protocol is a bluetooth protocol, and the data transmission channel is a serial port profile SPP channel.
In a possible implementation, the second broadcast message includes scene information, where the scene information includes a team game or team fitness.
In one possible implementation, the method further includes separately obtaining data from each of the wearable devices based on the close range wireless communication connection with each of the wearable devices in response to a second instruction entered by the user, the second instruction for instructing to start the game or to start the workout.
In one possible implementation, the second broadcast message is a bluetooth low energy broadcast.
In the implementation manner, the second broadcast message is Bluetooth low-power-consumption broadcast, so that the power consumption of the second terminal equipment can be saved.
In a sixth aspect, the present application provides an apparatus, which is included in a wearable device, the apparatus having a function of implementing the above first aspect and the behavior of the wearable device in the possible implementation manners of the above first aspect. The functions may be realized by hardware, or may be realized by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. Such as a receiving module or unit, a processing module or unit, etc.
In a seventh aspect, the present application provides an apparatus, which is included in a first terminal device, and which has a function of implementing the second aspect and the behavior of the first terminal device in the possible implementation manners of the second aspect. The functions may be realized by hardware, or may be realized by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. Such as a receiving module or unit, a processing module or unit, etc.
In an eighth aspect, the present application provides an apparatus, which is included in a second terminal device, and has a function of implementing the third, fourth, and fifth aspects and the second terminal device behavior in possible implementation manners of the third, fourth, and fifth aspects. The functions may be realized by hardware, or may be realized by hardware executing corresponding software. The hardware or software includes one or more modules or units corresponding to the functions described above. Such as a receiving module or unit, a processing module or unit, etc.
In a ninth aspect, the application provides a wearable device, which comprises a processor, a memory and a short-range wireless communication module, wherein the processor, the memory and the short-range wireless communication module are mutually matched, so that the wearable device executes any one of the methods in the technical scheme of the first aspect.
In a tenth aspect, the application provides a terminal device, which comprises a processor, a memory and a short-range wireless communication module, wherein the processor, the memory and the short-range wireless communication module are mutually matched, so that the terminal device executes any one of the methods in the technical scheme of the second aspect.
In an eleventh aspect, the present application provides a terminal device, including a processor, a memory, and a short-range wireless communication module, where the processor, the memory, and the short-range wireless communication module are mutually matched, so that the terminal device performs any one of the methods in the third aspect, the fourth aspect, or the fifth aspect.
In a twelfth aspect, the application provides a chip comprising a processor. The processor is configured to read and execute a computer program stored in the memory to perform the method of the first aspect and any possible implementation thereof.
Optionally, the chip further comprises a memory, and the memory is connected with the processor through a circuit or a wire.
Further optionally, the chip further comprises a communication interface.
In a thirteenth aspect, the present application provides a chip comprising a processor. The processor is configured to read and execute a computer program stored in the memory to perform the method of the second aspect and any possible implementation thereof.
In a fourteenth aspect, the present application provides a chip comprising a processor. The processor is configured to read and execute a computer program stored in the memory to perform the method of the third, fourth or fifth aspect and any possible implementation thereof.
In a fifteenth aspect, the present application provides a computer-readable storage medium, in which a computer program is stored, which when executed by a processor causes the processor to perform any one of the methods of the first, second, third, fourth or fifth aspects.
In a sixteenth aspect, the present application provides a computer program product comprising computer program code for causing an electronic device to perform any one of the methods of the first, second, third, fourth or fifth aspects when the computer program code is run on the electronic device.
Drawings
Fig. 1 is an application scenario schematic diagram of an example of a connection method of a wearable device according to an embodiment of the present application;
fig. 2 is a schematic diagram of an application scenario in which a user performs somatosensory exercise through a large screen device according to an embodiment of the present application;
Fig. 3 is a schematic diagram of a process of disconnecting bluetooth connection between a mobile phone and a smart watch and unbinding the bluetooth connection according to an embodiment of the present application;
fig. 4 is a schematic diagram illustrating a process of establishing a bluetooth connection between a smart watch and a large screen device according to an embodiment of the present application;
FIG. 5 is a schematic diagram of an interface of a smart watch during pairing according to an embodiment of the present application;
Fig. 6 is a flowchart of an example of a connection method of a wearable device according to an embodiment of the present application;
Fig. 7 is an application scenario schematic diagram of another example of a connection method of a wearable device according to an embodiment of the present application;
fig. 8 is an interface change schematic diagram corresponding to a connection method of a wearable device according to an embodiment of the present application;
FIG. 9 is a schematic diagram of an interface of a large screen device according to an embodiment of the present application;
fig. 10 is a schematic diagram of a connection change between a smart watch and a mobile phone, a large screen device according to an embodiment of the present application;
fig. 11 is a flowchart of another example of a connection method of a wearable device according to an embodiment of the present application;
fig. 12 is a schematic diagram of a connection change between a smart watch and a mobile phone, a large screen device according to another embodiment of the present application;
fig. 13 is a flowchart of another example of a connection method of a wearable device according to an embodiment of the present application;
Fig. 14 is a flowchart of another example of a connection method of a wearable device according to an embodiment of the present application;
FIG. 15 is a schematic diagram of an interface of another large screen device according to an embodiment of the present application;
fig. 16 is a schematic diagram of a connection change between a smart watch and a mobile phone, a large screen device according to another embodiment of the present application;
fig. 17 is an application scenario schematic diagram of a connection method of a wearable device according to another embodiment of the present application;
Fig. 18 is a flowchart of another example of a connection method of a wearable device according to an embodiment of the present application;
FIG. 19 is a schematic diagram of an interface for team fitness games via a large screen device according to an embodiment of the present application;
fig. 20 is an interface schematic diagram of an example of receiving, by a smart watch, a team BLE broadcast sent by a large screen device according to an embodiment of the present application;
fig. 21 is a schematic diagram illustrating a process of establishing bluetooth connection between a large screen device and a plurality of wearable devices according to an embodiment of the present application;
fig. 22 is a schematic structural diagram of an example of a wearable device 100 according to an embodiment of the present application;
fig. 23 is a schematic structural diagram of an example of a first terminal device 200 according to an embodiment of the present application;
fig. 24 is a schematic structural diagram of an example of a second terminal device 300 according to an embodiment of the present application;
fig. 25 is a schematic software architecture of an example of a wearable device 100 according to an embodiment of the present application;
Fig. 26 is a schematic software architecture diagram of an example of a first terminal device 200 according to an embodiment of the present application;
fig. 27 is a schematic software architecture diagram of an example of a second terminal device 300 according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be described below with reference to the accompanying drawings in the embodiments of the present application. In the description of the embodiment of the present application, unless otherwise indicated, "/" means or, for example, a/B may represent a or B, and "and/or" herein is merely an association relationship describing an association object, which means that three relationships may exist, for example, a and/or B, and that three cases, i.e., a alone, a and B together, and B alone, exist. In addition, in the description of the embodiments of the present application, "plurality" means two or more than two.
The terms "first," "second," "third," and the like, are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first", "a second", or a third "may explicitly or implicitly include one or more such feature.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
For a better understanding of embodiments of the present application, terms or concepts that may be referred to in the embodiments are explained below.
1. Connection
The connection in the embodiment of the application mainly refers to short-distance wireless communication connection. The communication protocol of the short-range wireless communication connection may be one of bluetooth (blue) protocol, matter protocol, zigbee (Zigbee) protocol, wireless fidelity (WIRELESS FIDELITY, wi-Fi) protocol, thread protocol, or Mesh (Mesh) protocol. In the embodiment of the application, a short-distance wireless communication connection (bluetooth connection for short) based on a bluetooth protocol is mainly taken as an example for explanation.
2. Bluetooth device
The bluetooth device refers to a module or a device for implementing a bluetooth connection in an electronic device. Bluetooth devices are largely divided into classical bluetooth (classic bluetooth) devices, bluetooth low energy (bluetooth low energy, BLE) devices (or referred to as bluetooth low energy devices, BLE devices for short) and dual mode bluetooth devices. Among other things, classical bluetooth devices include Basic Rate (BR) bluetooth devices/enhanced rate (ENHANCED DATA RATE, EDR) bluetooth devices, (HIGH SPEED, HS) bluetooth devices, etc. A dual mode bluetooth device is a bluetooth device that integrates a controller for both a classical bluetooth device and a low energy bluetooth device.
3. Transmission channel for Bluetooth connection
Taking a classical bluetooth device as an example, a bluetooth connection may include one or more profile (profile) transmission channels, to name a few:
3.1 HFP channel
English of HFP is called HANDS FREE profile, chinese is called hands-free profile. HTP defines two roles, an Audio Gateway (AG) and a hands-free component (HF), to provide a remote wireless control and voice connection between the audio gateway and hands-free device over a bluetooth connection. The audio gateway may be a mobile phone, such as a mobile phone. In short, based on the HFP channel, the bluetooth device can realize functions of controlling telephone (i.e., call), such as answering, hanging up, refusing to answer, voice dialing, and the like.
3.2, A2DP channel
English of A2DP is called advanced audio distribution profile, chinese is called advanced audio distribution configuration file. A2DP specifies protocol stack software and methods of use for transmitting high quality audio data using bluetooth unsynchronized transmission channels. Based on the A2DP channel, the Bluetooth devices can mutually transmit high-quality audio data.
3.3, SPP channel
English of SPP is called serial port profile, chinese is called serial port configuration file. SPP defines the Bluetooth device requirements required to set up an analog serial cable connection between two peer devices using a serial emulation protocol (radio frequency communication, RFCOMM), expressed in terms of the services provided to the application and the functions and procedures required to define interoperability between Bluetooth devices. In short, based on SPP channels, bluetooth devices are capable of point-to-point data transmission capabilities.
It should be noted that the profile of bluetooth is also various, and is not listed here. The Bluetooth device can select the required profile according to the requirement, and establish a corresponding profile channel.
4. Trust ring and trusted device
And the two or more terminal devices establish trust relationship through trusted authentication to form a trust ring. In other words, a plurality of devices have a trust relationship with each other, and it is understood that the plurality of devices form a trust ring.
The terminal devices can be trusted by any one of the following methods, a trust relationship is established, and a trust ring is formed, namely 1) the same account number is respectively logged in two or more terminal devices, the terminal devices under the same account number are mutually trusted, then the two or more electronic devices form a trust ring, for example, two mobile phones of the same user, or mobile phones, tablet computers, notebook computers and the like of the same user can be trusted by logging in the account number of the user, and the trust relationship is established, so that a trust ring is formed. 2) And 3) the two or more electronic devices perform the trusted authentication through logging in the cloud, establish the trust relationship and form the trust ring. It will be appreciated that the above several ways are for illustration only and are not to be construed as limiting the application in any way.
Terminal equipment in the trust ring forms a local area network through near field communication, and data can be synchronized through the local area network, so that the coordination of the equipment is realized.
A certain terminal device within a trust ring may be referred to as a trusted device of other devices. That is, by trusted authentication, a terminal device having a trust relationship is referred to as a trusted device. For example, a mobile phone, a tablet computer, and a notebook computer form a trust ring, and the tablet computer and the mobile phone may be referred to as trusted devices, i.e., the tablet computer is a trusted device of the mobile phone, and the mobile phone is also a trusted device of the tablet computer.
The application scenario of the embodiment of the present application is described below.
Wearable devices such as smart watches, sports bracelets, smart glasses, smart headbands, headphones, and the like are increasingly used in people's lives. The wearable device can be connected with the terminal device in a pairing mode, and related functions are achieved. Taking wearable equipment as an intelligent watch and terminal equipment as a mobile phone as an example, the intelligent watch can be connected with the mobile phone in a pairing way, so that the intelligent watch can answer an incoming call on the mobile phone, or data of the intelligent watch can be uploaded to the mobile phone.
After the wearable equipment and the terminal equipment are connected in a pairing mode, a binding relation between the wearable equipment and the terminal equipment can be automatically established, so that encryption authentication can be conveniently carried out in the next connection, and the link is encrypted. The binding relationship is to store information such as a pairing key (also referred to as a link key) of the peer device. However, in the case where the wearable device is bound to the terminal device, the terminal device can acquire various information of the wearable device, including account information, privacy information, and the like of the user. Therefore, in view of security of user information, in general, a wearable device can establish a connection with only one terminal device. If the wearable device is connected with one terminal device at present, when connection with other terminal devices is needed, the wearable device is required to be disconnected with the current terminal device through the approval of a user, the binding relation with the terminal device is released, and the wearable device is paired with the other terminal devices after entering a paired state. Here, the unbinding relationship is also called as unbinding peer-to-peer, and means that information such as a pairing key with the bound device is deleted. Unbinding may be triggered by clicking on a unpaired control, deleting a device control, or connecting a new device control in the wearable device or terminal device, etc. The following description is made in connection with an application scenario.
Fig. 1 is a schematic application scenario diagram of an example of a connection method of a wearable device according to an embodiment of the present application. As shown in fig. 1 (a), the smart watch of the current user has established a connection with the mobile phone. If the user needs to connect the smart watch with the large screen device to perform body-sensing exercise through the large screen device, the user needs to disconnect the smart watch from the mobile phone first and release the binding relationship between the smart watch and the mobile phone, as shown in the diagram (b) in fig. 1. The smart watch then establishes a connection with the large screen device, as shown in figure 1 (c).
After the intelligent watch is connected with the large-screen device, a user can perform body-sensing body-building through the large-screen device. Somatosensory exercise is also known as artificial intelligence (ARTIFICIAL INTELLIGENCE, AI) exercise or AI exercise, meaning exercise based on somatosensory technology. Somatosensory technology refers to the fact that a user does not need to use complex control equipment, but directly interacts with surrounding devices or environments through limb actions. Specifically, in the body-building process, the wearable device collects motion data of a user through sensors such as a gravity sensor and a gyroscope, and transmits the motion data to the large-screen device based on connection with the large-screen device. A motion Application (APP) in the large screen device displays or feeds back actions of the user according to the motion data, and the like. In one embodiment, after the user disconnects the smart watch from the mobile phone, an application scenario of somatosensory exercise through the large screen device may be as shown in fig. 2.
Optionally, the user may disconnect from the smart watch and unbind the smart watch by operating the smart watch, or disconnect from the smart watch by operating the smart watch and unbind the smart watch. Referring to fig. 3, this embodiment is illustrated by taking an example of disconnecting and unbinding the smart watch by operating the mobile phone. As shown in fig. 3 (a), a user may click on a card 302 of a smart watch (shown as smart watch a) in a device interface 301 in an exercise APP (e.g., exercise health). In response to the user's click, the handset displays the information interface 303 of the smart watch a, as shown in fig. 3 (b). A selection control 304 is included in the interface. The user clicks the select control 304, the tab 305 is displayed in the interface, and the tab 305 includes a delete device control 306, as shown in figure 3 (c). The user clicks the delete device control 306 and a card 307 is displayed in the interface for asking the user whether to delete the device, as shown in figure 3 (d). Included in the card 307 is a determination control 308. After the user clicks the determine control 308, the handset disconnects and unbundles from the smart watch.
And then, the user can initiate pairing connection by operating the intelligent watch or the large-screen device and scanning the discovery device, so that the intelligent watch or the large-screen device and the large-screen device establish Bluetooth connection. Fig. 4 is a schematic diagram illustrating a process of establishing a bluetooth connection between a smart watch and a large-screen device according to an embodiment of the present application. The description will be given taking as an example that the device is found by operating a large screen device scan, and the pairing connection is initiated. As shown in fig. 4 (a), in case that both the large screen device and the smart watch are opened bluetooth, the user can open the sports APP in the large screen device and enter the main interface 401 of the sports APP. The user may select the device control 402 in the main interface 401 via the remote control and display the device interface 403 in the large screen device, as shown in fig. 4 (b). The device interface 403 includes an add device card 404, and the user selects the add device card 404 via the remote controller, and the large screen device starts scanning the surrounding bluetooth devices, and displays an add device interface 405, as shown in fig. 4 (c). The large screen device scans for a certain period of time to find out the intelligent watch (shown as an intelligent watch a), an information card 406 of the intelligent watch is displayed in the interface, and a connection control 407 is included in the information card 406 of the intelligent watch. The user selects the connection control 407 through the remote control, and the large screen device establishes a physical link with the smart watch.
Thereafter, the large screen device displays a confirm pairing interface 408 asking the user if he confirms pairing with the smart watch. A popup window 409 may be included in the confirm pairing interface 408, with a confirm control 410 and a cancel control 411 included in the popup window 409, as shown in fig. 4 (d).
When the user clicks the confirmation control 410, the large screen device initiates a pairing request to the smart watch, and the handset displays a first pairing interface 412, as shown in fig. 4 (e).
After the large-screen device initiates the pairing request, the intelligent watch displays a pairing request interface. Illustratively, the pairing request interface of the smart watch may include an accept pairing control 502 in the pairing request interface 501 as shown in 501 in fig. 5 (a). The user clicks the accept pairing control 502 and the large screen device starts pairing with the smart watch, which displays a third pairing interface 503, as shown in figure 5 (b). At the same time, the handset displays a second pairing interface 413, as shown in fig. 4 (f). After a period of time, the large-screen device and the intelligent watch are paired, and connection is established. After the connection is established, the interface between the large screen device and the smart watch may be as shown in fig. 1 (c).
It should be noted that fig. 4 and fig. 5 are only examples, and in practical application, the bluetooth connection between the large-screen device and the smart watch may be established through other operation manners, for example, the selection control 304 in the device interface 403 in fig. 4 (b) may be selected through the remote controller, so as to trigger the large-screen device to scan surrounding bluetooth devices.
As can be seen from the embodiments shown in fig. 1 to fig. 5, when the wearable device establishes a connection with one terminal device, if other devices need to be connected, a user needs to disconnect the connection with the current terminal device and unbind the connection through multiple steps, so that the wearable device enters a mateable state, and then can establish a connection with the other terminal devices, which is complicated and complicated in process and poor in user experience.
In view of this, the embodiment of the application provides a connection method of a wearable device, which can simplify the connection process of the wearable device and a terminal device and improve user experience.
The method for connecting the wearable device provided by the embodiment of the application relates to the wearable device, a first terminal device, a second terminal device, a server and the like. The wearable device can be a sports bracelet, a sports foot ring, a smart watch, a smart wristband, smart glasses, a smart headband, an earphone and the like, and the embodiment of the application does not limit the specific type of the wearable device.
Alternatively, the first terminal device and the second terminal device may be large-screen devices, mobile phones, tablet computers, vehicle-mounted devices, augmented reality (augmented reality, AR)/Virtual Reality (VR) devices, notebook computers, ultra-mobile personal computer (UMPC), netbooks, personal Digital Assistants (PDA) and other electronic devices with short-range wireless communication functions, and Application (APP) may be installed in the first terminal device and the second terminal device.
The following embodiments of the present application specifically describe a connection method of a wearable device provided by the embodiments of the present application by taking a wearable device as an intelligent watch, a first terminal device as a mobile phone, a second terminal device as a large screen device, and bluetooth connection as an example, and combining with a drawing and an application scenario.
In order to facilitate understanding of the solution of this embodiment, a brief description will be first given of a procedure of establishing a bluetooth connection between a wearable device and a terminal device. Taking device a and device B as examples, one of the device a and the device B is a wearable device, and the other is a terminal device. The process comprises the following steps:
1) Transmitting discoverable broadcasts
At least one of device a and device B may actively transmit a discoverable broadcast (also referred to as a broadcast packet or broadcast message) at intervals so that the device can be discovered by other devices. The following description will take an example in which the device a transmits a discoverable broadcast to the surroundings. Typically, device a will not transmit a discoverable broadcast to the surroundings until it is in a pairable state. When the device a is in the paired state, the device a no longer establishes a connection with other devices in view of the security of the user information, and thus the device a does not transmit a discoverable broadcast to the surroundings.
2) Scan discovery
After receiving the discoverable broadcast sent by device a, the surrounding device (e.g., device B) may initiate a scan request to device a to obtain more device information of device a, such as device name, device type, etc. After receiving the scanning request, the device A sends a scanning response packet to the device B for response. The scan response packet may include device information of device a. In this case, device B is the connection initiator, i.e. the master device, and device a is the connection receiver, i.e. the slave device. The device receiving the scan request also needs to send a scan response packet to answer.
Taking the example that the device B initiates the scan request to the device a, the device a sends a scan response packet to the device B after receiving the scan request. And after the equipment B receives the scanning response packet, displaying the equipment information of the equipment A in an interface of the equipment B.
It should be noted that, in general, in a case where the device a has established a connection with one device (for example, the device C), the device a no longer establishes a connection with another device in view of security of user information, and thus the device a no longer transmits a discoverable broadcast to the surroundings, and cannot be scanned for discovery by another device (for example, the device B).
3) Establishing a physical link
After the scan discovery is completed, device a establishes a physical link with device B in response to a connection instruction from the user. Optionally, the physical links may include advanced communication links (advanced communication link, ACL), SCO links, and the like. When a user inputs an instruction to establish a connection with device a in the interface of device B (e.g., clicks on a connection control corresponding to device a), device B establishes a physical link with device B in response to the connection instruction.
3) Pairing
After the physical link is established, the device A and the device B enter a pairing stage. Specifically, the device a sends a pairing request to the device B, or the device B sends a pairing request to the device a, and both enter a pairing phase. The entering of the pairing phase can be triggered by a user input instruction or can be triggered automatically by the equipment, namely, after the establishment of the physical link is completed, the pairing phase is automatically entered.
The pairing phase is essentially the process by which device a negotiates with device B to determine the encryption key. The pairing phase may include several procedures of pairing feature exchange (pairing feature exchange), link authentication, key distribution, and binding.
Pairing feature exchange, namely, the requirement (authentication requirements) for authentication related to the exchange of the two parties (the device A and the device B), the man-machine interaction capability (IO capabilities) of the exchange of the two parties and the like.
Link authentication device a initiates a link authentication request to device B or device B to device a. And if the opposite end receives the pairing request, performing link authentication on the equipment A and the equipment B.
Key assignment device a and device B generate mating keys based on random numbers, pin codes, media access control (MEDIA ACCESS control, MAC) addresses, etc. The mating key may include a long-term key (LTK), among others. The MAC is also called a MAC address.
Binding, namely, the device A and the device B store LTKs, and a binding relationship is established between the device A and the device B. After the binding relationship between the device A and the device B is established, if reconnection is performed again, the pairing stage can be skipped, and the LTK can be directly used for encryption.
4) Establishing profile channels
After pairing is completed, device a and device B establish a profile channel (also referred to as a profile connection) based on the required profile.
It should be noted that, when the device a and the device B complete pairing and binding, and do not unbind (the stored key data is not emptied), and the subsequent device a and the device B are connected, the device a and the device B do not pair and bind any more, so that a physical link can be directly established, a profile channel can be established, and bluetooth connection can be realized.
The following describes a detailed procedure of the connection method of the wearable device provided by the embodiment of the application.
Scene one:
In this embodiment, when the smart watch and the mobile phone are connected by bluetooth, the mobile phone may enter a preset geofence (Geo-fencing), and when a trusted device exists around the mobile phone, the smart watch and the trusted device are connected by bluetooth, and the user does not need to disconnect the smart watch and the mobile phone and also does not need to disconnect the connection between the smart watch and the mobile phone. The following is a detailed description with reference to the accompanying drawings.
Fig. 6 is a schematic flow chart of an example of a method for connecting a wearable device according to an embodiment of the present application, as shown in fig. 6, where the method includes:
s101, under the condition that a Bluetooth connection (also called a first connection) is established between the smart watch and the mobile phone, the mobile phone determines that the mobile phone enters a target geofence according to information of at least one preset geofence and device information in a trust ring, and trusted large-screen devices exist in the target geofence.
The preset geofence is information characterizing a preset geographic area. Geofencing, a new application of location-based services (location based services, LBS), is to enclose a virtual geographic boundary with a virtual fence. When the handset moves from outside the geofence to inside the geofence (i.e., enters the geofence) or from inside the geofence to outside the geofence (i.e., leaves the geofence), the corresponding service is triggered. For example, the electronic device enters a geofence of a high-voltage line, and the corresponding management system may send a notification or alert to the electronic device.
The target geofence is any one of at least one preset geofence. Alternatively, the mobile phone may preset and store information of one or more geofences, where the user may connect the mobile phone with the large screen device at the same time. For example, the preset geofence may be a geofence corresponding to the user's home, a geofence corresponding to the user's company, and so on. In the case that the smart watch and the mobile phone have established a bluetooth connection, the mobile phone determines whether the mobile phone enters a certain preset geofence (called a target geofence) according to the current position and the information of the preset geofences. If so, the mobile phone determines whether trusted devices exist in the target geofence according to the device information in the trust ring.
Optionally, the mobile phone may obtain historical bluetooth scan information, and determine whether a trusted device exists in the target geofence according to the historical bluetooth scan information. The historical Bluetooth scanning information characterizes information of the terminal equipment found by the Bluetooth equipment of the mobile phone in the target geofence in a historical time period. Optionally, the historical bluetooth scan information may include scan time and scan location when the mobile phone scans to find the terminal device, and scan the found device information of the terminal device. The device information of the terminal device found by the bluetooth device scanning may include, for example, a MAC address, a device name, and the like. The mobile phone can determine which terminal devices are found by scanning in the target geofence in a historical time period according to the historical Bluetooth scanning information, and then determine whether trusted devices exist in the target geofence according to the device information in the trust ring. Specifically, the mobile phone can compare the historical bluetooth scanning information with the device information in the trust ring to confirm whether the device scanned by the mobile phone in the historical time period comprises the device in the trust ring. If so, it is determined that there is a trusted device within the target geofence. In the implementation mode, the mobile phone can quickly determine whether trusted equipment exists in the target geofence based on the historical Bluetooth scanning information, and the power consumption of the mobile phone is saved.
Optionally, after determining that the mobile phone enters the target geofence, actively scanning to find surrounding devices, acquiring information of the surrounding devices, comparing the information of the surrounding devices with the device information in the trust ring, and determining whether the trusted device exists in the target geofence.
Optionally, the mobile phone may also obtain device information and location information of each device in the trust ring from the cloud server, so as to determine whether a trusted device exists in the target geofence. The embodiment of the application does not limit the specific method for determining whether the trusted device exists in the target geofence by the mobile phone.
A trusted device of a cell phone within a target geofence may be considered a device that the user is trusted to not affect the security of the user's information. In this embodiment, a trusted device is exemplified as a large screen device.
Fig. 7 is a schematic application scenario diagram of another example of a connection method of a wearable device according to an embodiment of the present application. As shown in fig. 7, a target geofence 101 is illustrated as a geofence corresponding to a user's home. The user carries the handset 102 and wears the smart watch 103, and the handset 102 has established a bluetooth connection with the smart watch 103. When the user comes home with the mobile phone 102, the mobile phone 102 determines to enter the target geofence 101, and determines that a trusted device, which is the large screen device 104, exists in the target geofence 101 according to the historical bluetooth scan information.
S102, the mobile phone sends notification information to the intelligent watch, wherein the notification information is used for indicating that trusted devices (large screen devices) exist around.
Alternatively, the notification information may carry device information of the trusted device. In the embodiment of the application, the notification information can carry the equipment information of the large-screen equipment. The device information of the large screen device includes, but is not limited to, the MAC address of the large screen device, etc.
In one possible implementation, the smart watch may subscribe to notification information in advance with the phone, such that when the phone determines itself to enter the target geofence and there is a trusted device within the target geofence, the phone sends the notification information to the smart watch.
S103, the smart watch responds to the notification information and sends discoverable broadcasting (namely, a first broadcast message) to the surrounding devices, wherein the discoverable broadcasting is used for the surrounding devices to discover the smart watch.
In one embodiment, after receiving the notification information, the smart watch may periodically send a discoverable broadcast to the surrounding devices, so that the surrounding devices can discover the smart watch at any time when they need to connect to the smart watch. For example, the smart watch may send a discoverable broadcast to surrounding devices every 5s, until the trusted device receives the discoverable broadcast.
In one embodiment, device information of the smart watch and bluetooth connected information (i.e., first information) may be carried in the discoverable broadcast. The device information of the smart watch may include, but is not limited to, a MAC address. The bluetooth connected information is used to characterize that the smart watch has currently established a bluetooth connection with the handset. Alternatively, the bluetooth connected information may be characterized by predefined fields.
It can be understood that, in the case that the device information of the smart watch is carried in the discoverable broadcast, the smart watch may send the discoverable broadcast to all surrounding devices in response to the notification information, or may send the discoverable broadcast to the large-screen device in a directional manner according to 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 carried in the discoverable broadcast. The smart watch directionally transmits discoverable broadcast to the large-screen device, and after other devices receive the discoverable broadcast, the other devices determine that the MAC address carried in the broadcast message is inconsistent with the MAC address of the smart watch, so that the discoverable broadcast message is discarded and is not analyzed continuously, the interference of the smart watch to other surrounding devices can be reduced, the power consumption of the surrounding devices is saved, and the user experience is improved.
S104, the large-screen device receives discoverable broadcasting sent by the intelligent watch.
Optionally, the large screen device may automatically receive the discoverable broadcast sent by the smart watch based on a communication mechanism preset in the bluetooth protocol.
S105, responding to a scanning discovery instruction input by a user on the large screen device, and enabling the large screen device to scan and discover the intelligent watch to acquire and display device information of the intelligent watch.
The scan discovery instruction is used for instructing the large screen device to perform scan discovery. Optionally, after the user starts the large screen device, an APP (e.g., a sports APP) that needs to interact with the smart watch in the large screen device may be opened, and a scan discovery instruction is input through the APP, for example, by clicking an add device card in an interface for managing bluetooth connection devices in the sports APP.
Fig. 8 is a schematic diagram of an interface according to an embodiment of the present application. As shown in fig. 8 (a), the large screen device starts a motion APP and displays a device interface 403 of the APP. An add-on device card 404 is included in the device interface 403, and a user can select the add-on device card 404 through a remote controller to input a scan discovery instruction.
It will be appreciated that, although the discoverable broadcast sent by the smart watch to the large-screen device in step S103 may carry device information (such as a MAC address) of the smart watch, after the user inputs the scan discovery instruction, the large-screen device may further acquire more device information from the smart watch, for example, one or more of a device name, a device type, and the like of the smart watch, so as to display the information in the interface.
Specifically, in response to a scan discovery instruction input by a user, the large screen device initiates a scan request to the smart watch. After receiving the scanning request, the intelligent watch sends a scanning response packet to the large-screen device for response. The scan response packet includes device information of the smart watch. And after the large screen device receives the scanning response packet, displaying the device information of the intelligent watch in the interface. Illustratively, the large screen device scan discovers the interface of the smart watch may be as shown in interface 405 of fig. 8 (b).
It should be noted that, because the discoverable broadcast is sent to the surrounding devices after the smart watch receives the notification information, when the discoverable broadcast sent to the large-screen device by the smart watch carries the device information of the smart watch and the bluetooth connected information, if the large-screen device receives the discoverable broadcast, the large-screen device can confirm that the current application scenario is that the smart watch is connected with the mobile phone and the large screen is a trusted device according to the device information of the smart watch and the bluetooth connected information. In this scenario, the large-screen device scan discovery smart watch may also be automatically triggered to perform the scan discovery operation without being triggered by a scan discovery instruction of the user. After the intelligent watch is automatically scanned and found, the large screen device can display the device information of the intelligent watch in the interface in a popup window mode and inquire whether a user establishes connection with the intelligent watch.
In short, this step S105 may also be replaced by a large screen device scanning for finding the smart watch based on Bluetooth connected information in the discoverable broadcast in response to the discoverable broadcast, and acquiring and displaying device information of the smart watch. Alternatively, the device information of the smart watch may be displayed in the form of a popup window (also referred to as a second interface). Therefore, the user does not need to manually trigger scanning discovery, the user operation is simplified, and the user experience is improved.
For example, as shown in fig. 9, a second interface may be shown at 901 and smart watch device information may be displayed in a pop-up window 902.
And S106, responding to the connection instruction 1 input by the user, and establishing a physical link with the intelligent watch by the large-screen device according to the device information of the intelligent watch.
The connection instruction 1 is used for indicating the large-screen device to establish connection with the intelligent watch. Optionally, the large screen device may display the device information of the smart watch and simultaneously display a connection control for inputting a connection instruction, through which the user may input the connection instruction 1.
Illustratively, as shown in fig. 8 (b), the user may select a connection control 407 in the card 406 of the smart watch a in the interface 405 shown in fig. 8 (b) through the remote controller to input a connection instruction 1. Of course, the user may input the connection instruction 1 by means of voice input or the like, which is not limited in the embodiment of the present application.
After receiving the connection instruction 1, the large-screen equipment establishes a physical link with the mobile phone.
And S107, displaying a pairing confirmation interface by the large screen device.
Specifically, after the large-screen device establishes a physical link with the smart watch, a confirmation pairing interface is displayed in the screen, wherein the confirmation pairing interface comprises inquiry information for inquiring whether a user confirms pairing with the smart watch. The display form of the inquiry information in the confirmation pairing interface can be various, for example, a popup window, a capsule, a card or a floating window, and the embodiment of the application is not limited in any way.
The confirmation pairing interface of the large screen device may be, for example, an interface 408 shown in fig. 8 (c), for example. A pop-up window 409 is included in the interface 408. Included in the pop-up window 409 are a confirm control 410 and a cancel control 411.
S108, responding to the fact that the user inputs a pairing confirmation instruction 1 in a confirmation interface of the large-screen device, and the large-screen device sends a pairing request to the intelligent watch.
The confirmation pairing instruction 1 is used for indicating the large-screen device to initiate a pairing request to the intelligent watch. Illustratively, as shown in fig. 8 (c), the user may click on a confirmation control 410 in the pop-up window 409, for example, to input a confirmation pairing instruction 1. After the user inputs the confirm pairing instruction 1, the large screen device may display the first pairing interface 412, as shown in (d) of fig. 8.
In some embodiments, the large screen device may not display the pairing confirmation interface, and may not need to input a pairing confirmation instruction by the user, and may directly send a pairing request to the smart watch after establishing a physical link with the smart watch. That is, the above-described "response to the user inputting the confirmation pairing instruction 1 in the confirmation interface" in step S107 and step S108 may not be performed, but the "large screen device in step S108 is directly executed to send the pairing request to the smart watch after the completion of the execution of step S105. Therefore, the user operation is further simplified, and the user experience is improved.
And S109, responding to a pairing request of the large-screen device, and displaying a pairing request interface by the intelligent watch.
Specifically, the intelligent watch displays a pairing request interface according to a pairing request sent by the large-screen device. The pairing request interface includes inquiry information for inquiring whether the user accepts the pairing request of the large-screen device. The display form of the query information in the pairing request interface may be various, for example, a popup window, a capsule, a card, a floating window, etc., which is not limited in any way according to the embodiment of the present application. In one embodiment, the pairing request interface may be similar to interface 501 shown in fig. 5 (a), except that the schematic of the device connected to the smart watch in the pairing request interface may be a schematic of a large screen device, rather than a schematic of a cell phone in interface 501.
S110, responding to the pairing request interface input by the user of the intelligent watch to receive a pairing instruction 1, and automatically disconnecting the Bluetooth connection with the mobile phone by the intelligent watch.
Specifically, the smart watch can determine that the trusted device of the mobile phone exists around according to the notification information, and determine that the user agrees to establish connection with the trusted device (large screen device) according to the pairing receiving instruction 1 input by the user, so that the smart watch can automatically disconnect the Bluetooth connection with the mobile phone. Automatic disconnection refers to the smart watch autonomously disconnecting from the bluetooth of the handset without requiring the user to perform a disconnection operation (e.g., clicking a delete device, de-provisioning a peer-to-peer).
Optionally, the smart watch may break the physical link with the watch and unbind from the handset.
Alternatively, the smart watch may simply disconnect the physical link with the handset, without releasing the binding relationship with the handset. In the embodiment, the intelligent watch receives the notification information sent by the mobile phone, so that the current application scene can be determined as that the intelligent watch is connected with the mobile phone, and trusted equipment, namely large screen equipment exists in the current surrounding environment. In this scenario, if the smart watch receives the pairing acceptance instruction 1 that the user agrees to pair with the large-screen device, it can be confirmed that the security of the user information is not affected even if the smart watch does not release the binding relationship with the mobile phone. Therefore, the intelligent watch can only disconnect the physical link with the mobile phone, so that when the subsequent intelligent watch is reconnected with the mobile phone, the pairing stage is not required to be re-entered, and the user is not required to execute operations (such as pairing confirmation operations) related to the pairing stage, thereby saving the execution programs of the intelligent watch and the mobile phone, simplifying the user operation and improving the user experience.
It should be noted that, in some other embodiments, the "automatic disconnection of the smart watch from the bluetooth connection of the mobile phone" may also be performed at other times, for example, when a pairing request sent by the large screen device is received. The present application is not limited in any way.
S111, the intelligent watch is paired with the large-screen device and a profile channel is established.
The accept pairing instruction 1 is used for indicating that a pairing request of the large-screen device is accepted. Optionally, the pairing request interface may include an accept pairing control, for example 502 shown in fig. 5 (a), and the user may click on the accept pairing control 502 to input the accept pairing instruction 1. Of course, the user may input the pairing command 1 in other manners, for example, voice input, key selection, etc., which is not limited in any way in the embodiment of the present application.
In the process of pairing the smart watch and the large screen device and establishing the profile channel, the large screen device may display a second pairing interface 413, as shown in fig. 8 (e), and the smart watch may display a third pairing interface, which may be similar to the interface 503 shown in fig. 5 (b), except that the schematic diagram of the device connected to the smart watch in the third pairing interface may be a schematic diagram of the large screen device, rather than a schematic diagram of the mobile phone in the interface 503, which is not described in detail.
Optionally, in this embodiment, the profile channel established by the smart watch and the large-screen device may include an HFP channel, an A2DP channel, and an SPP channel. After the intelligent watch is paired with the large-screen device and the channels are established, the intelligent watch and the large-screen device are connected through Bluetooth. After the bluetooth connection is completed, the interface of the large screen device may be as shown in (f) of fig. 8.
It should be noted that, when the connection between the large-screen device and the smart watch is other connection, for example, wi-Fi connection, pairing is not required, and the above pairing process may not be performed.
In this embodiment, a schematic diagram of connection changes between the smart watch and the mobile phone, and the large screen device may be referred to fig. 10. As shown in fig. 10 (a), before the method provided in this embodiment is executed, the mobile phone establishes a bluetooth connection with the smart watch. Optionally, the bluetooth connection between the mobile phone and the smart watch may include an HFP channel, an A2DP channel, an SPP channel, and the like. Thereafter, the smart watch, the mobile phone and the large screen device perform the above steps S101 to S111, the smart watch disconnects the bluetooth connection with the mobile phone and establishes the bluetooth connection with the large screen device, as shown in (b) of fig. 10. Optionally, the bluetooth connection between the smart watch and the large screen device may also include an HFP channel, an A2DP channel, an SPP channel, and the like.
As described above, in general, when the wearable device has established a connection with one terminal device, the wearable device is in a paired state, and in consideration of the security of user information, no discoverable broadcast is sent to the surroundings any more, and only after the user disconnects the connection and releases the binding relationship between the connection, the wearable device is triggered to send the discoverable broadcast to the surroundings again. In this embodiment, when the mobile phone detects that the mobile phone enters the target geofence and the trusted large-screen device exists in the target geofence under the condition that the mobile phone and the smart watch are connected by bluetooth, the mobile phone sends notification information to the smart watch. That is, the mobile phone recognizes the trusted large-screen device and then notifies the smart watch, so that the smart watch can learn the current application scenario that the smart watch has established a connection with the mobile phone, and the trusted device of the mobile phone, namely the large-screen device, exists around the smart watch. Under the scene, the intelligent watch can automatically send discoverable broadcast to surrounding equipment without the related operations of disconnection and unbinding by a user under the condition that the intelligent watch does not release the binding relation with the mobile phone and reestablishes connection with the large screen equipment, so that the intelligent watch can be scanned and discovered by the large screen equipment, and further, bluetooth connection with higher security is established with the trusted large screen equipment. Therefore, related operations of disconnection and unbinding by a user are saved, and user experience is improved. Further, when the smart watch receives a pairing request of the large-screen device, the smart watch can determine that the large-screen device is a device trusted by the mobile phone according to the notification information, so that the smart watch can automatically disconnect the mobile phone and establish connection with the large-screen device without displaying an interface for inquiring a user or manually disconnecting the connection by the user. Therefore, the Bluetooth connection of the intelligent watch is switched to the large-screen device by the mobile phone, and the user is not required to execute related operations of disconnection and unbinding, so that the user operation is simplified, and the user experience is further improved.
As analyzed above, the large-screen device is a trusted device of the mobile phone, so that the smart watch simultaneously establishes Bluetooth connection with the mobile phone and the large-screen device, and the security of user information is not affected. Therefore, referring to fig. 11, in another embodiment, after receiving the pairing request sent by the large-screen device, the smart watch may also display the pairing request interface directly in response to the pairing request without disconnecting the connection with the large-screen device. That is, step S110 may not be performed, and step S111 may be performed directly after step S109 is performed. Thus, the intelligent watch establishes a second path of Bluetooth connection with the large screen device while maintaining Bluetooth connection with the mobile phone.
Alternatively, in this embodiment, the profile channel established between the smart watch and the large-screen device may include only the SPP channel. Step S111 is that in response to the user inputting the pairing acceptance instruction 1 in the pairing request interface, the smart watch is paired with the large-screen device and an SPP channel is established.
Specifically, as described above, the smart watch can learn that the current smart watch has established a connection with the mobile phone, and the large screen device can learn that the smart watch has established a connection with the mobile phone through the bluetooth connection information in the discoverable broadcast. In the case that the connection between the smart watch and the mobile phone is established, the bluetooth connection between the large screen device and the smart watch is generally only used for transmitting data, so that when the profile channel is established, the smart watch or the large screen device can initiate a request to the opposite terminal, authentication encryption is performed on the smart watch or the large screen device, and after the current application scene is determined, only the SPP channel is established. Therefore, the connection process between the large-screen device and the intelligent watch can be simplified, profile channels are saved, and power consumption and resources of the large-screen device and the intelligent watch are saved.
In this embodiment, a schematic diagram of connection changes between the smart watch and the mobile phone, and the large screen device may be seen in fig. 12. As shown in fig. 12 (a), before the method provided in this embodiment is performed, 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, and the like. Thereafter, the smart watch, the mobile phone, and the large screen device execute the method in the present embodiment, the smart watch maintains the bluetooth connection with the mobile phone, and establishes the bluetooth connection with the large screen device, as shown in fig. 12 (b). Alternatively, the bluetooth connection between the smart watch and the large screen device may include only the SPP channel.
In this embodiment, similar to the previous embodiment, in this embodiment, when a mobile phone connected to the smart watch enters a target geofence and a trusted device of the mobile phone exists in the paired state, the smart watch can send discoverable broadcast to the surrounding, so that the large screen device can discover the smart watch, and related operations of disconnection and unbinding are not required to be performed by a user, thereby simplifying user operations. Further, when the intelligent watch receives a pairing request of the large-screen device, the intelligent watch can determine that the large-screen device is a device trusted by the mobile phone according to the notification information, and the safety of user information cannot be affected, so that the intelligent watch is not disconnected with the mobile phone, and a second path of Bluetooth connection with the large-screen device is directly established, and therefore a user can interact with the mobile phone and the large-screen device simultaneously through the intelligent watch, and user experience is improved.
It should be noted that the embodiments shown in fig. 6 and fig. 11 are described by taking the example that the user operates on the large screen device side, discovers the smart watch, and establishes a bluetooth connection between the smart watch and the large screen device. In some other embodiments, the user may also operate on the smart watch side, establishing a bluetooth connection between the two. Specifically, referring to fig. 13, the above steps S105 to S111 may be replaced by the following steps:
S121, the intelligent watch displays equipment information of the large-screen equipment according to the notification information.
Specifically, as described above, the notification information may include device information of the large-screen device, and thus the smart watch may display an interface (also referred to as a first interface) including the large-screen device information according to the device information of the large-screen device. Optionally, a connection control (also referred to as a first control) for user input of a connection instruction may be included in the interface.
The form of the first interface and the first control may be similar to the form of the device information and the connection control of the intelligent device displayed in the large-screen device, and will not be described again.
S122, responding to the user input connection instruction 2, and establishing a physical link with the large-screen device by the intelligent watch according to the device information of the large-screen device.
The connection instruction 2 is used for indicating the smart watch to establish connection with the large-screen device. Alternatively, the user may enter connect instruction 2 by clicking a connect control in the interface shown in the wristwatch.
S123, the intelligent watch displays a pairing confirmation interface.
After the intelligent watch establishes a physical link with the large screen device, a pairing confirmation interface is displayed in the screen. The confirmation pairing confirmation interface of the smart watch can be similar to the confirmation pairing interface of the large-screen device, and is not repeated.
S124, responding to the fact that the user inputs a pairing confirmation instruction 2 in a confirmation interface of the intelligent watch, and automatically disconnecting the Bluetooth connection with the mobile phone.
The pairing confirmation instruction 2 is used for indicating the intelligent watch and the large-screen device to initiate a pairing request. After receiving the pairing confirmation instruction 2 of the user, the intelligent watch automatically disconnects Bluetooth with the mobile phone. Similar to step S110, in this embodiment, the smart watch may disconnect the physical link with the watch and release the binding relationship with the mobile phone, or may disconnect only the physical link with the mobile phone, but not release the binding relationship with the mobile phone. Specific advantageous effects and the like are not described herein.
S125, the intelligent watch sends a pairing request to the large-screen device.
And S126, responding to a pairing request sent by the intelligent watch, and displaying a pairing request interface by the large-screen device.
And S127, responding to the input of a pairing accepting instruction 2 by a user in a pairing request interface of the large-screen device, pairing the intelligent watch with the large-screen device and establishing a profile channel.
In the embodiment shown in fig. 6, before the smart watch is paired with the large-screen device, the bluetooth connection with the mobile phone may not be disconnected, i.e. the bluetooth connection is maintained.
In this embodiment, the process of establishing connection between the smart watch and the large-screen device is similar to the process of steps S106 to S111, except that in this embodiment, the user outputs a connection instruction and confirms a pairing instruction at the smart watch side, and inputs a pairing instruction at the large-screen device side. That is, the user triggers the bluetooth connection of the smart watch with the large screen device on the smart watch side.
It is noted that, in addition to the beneficial effects as described in fig. 6 and 11, in this embodiment, the smart watch receives notification information sent by the mobile phone, where the notification information may include device information of the large-screen device, so that the smart watch may directly display the device information without scanning to discover the large-screen device, without a user manually triggering the scanning discovery, which further simplifies user operation and improves user experience.
Scene II:
in this embodiment, in the case that the bluetooth connection is established between the smart watch and the mobile phone, the second path bluetooth connection between the smart watch and the large screen device may be implemented by a cloud pairing method. The following is a detailed description with reference to the accompanying drawings.
Fig. 14 is a flowchart of another method for connecting a wearable device according to an embodiment of the present application, as shown in fig. 14, where the method includes:
S201, when Bluetooth connection is established between the intelligent watch and the mobile phone, and the mobile phone logs in a first user account, the mobile phone uploads information such as device information and a pairing key of the intelligent watch to a server through the first user account.
The server may be a cloud server. It can be appreciated that the mobile phone can upload device information, connection information, and the like of the wearable device currently connected with the mobile phone to the cloud server under the condition of logging in the first user account. The connection information refers to information for establishing a short-range wireless communication connection between the wearable device and the other device, and when the short-range wireless communication connection is a bluetooth connection, the connection information may be a pairing key or the like.
The above-mentioned process of step S201 is also called that the mobile phone synchronizes the information cloud of the smart watch.
S202, under the condition that the large-screen device logs in the first user account, responding to operation of checking surrounding wireless communication devices in the large-screen device by a user, and acquiring device information, pairing keys and other information of the intelligent watch from a server by the large-screen device according to the first user account.
That is, the large-screen device and the mobile phone use the same user account number (first user account number), and if the user performs an operation of checking the surrounding wireless communication device while the large-screen device is in a login state (i.e., an online state), the large-screen device may acquire device information and a pairing key of the smart watch from the cloud server according to the first user account number. Alternatively, the operation of looking at the surrounding wireless communication device may be, for example, the user opening a bluetooth switch, or in case the bluetooth switch is open, the user opening a sports APP and looking at the device, etc.
S203, displaying the device information of the intelligent watch by the large-screen device.
The device information of the smart watch includes, but is not limited to, one or more of a device name, a device type, a MAC address, etc. of the smart watch.
Alternatively, the large screen device may display device information of the smart watch at a device interface (also referred to as a third interface) of the sports APP in response to a user opening the sports APP and viewing an operation of the device. A control (also referred to as a third control) for inputting a connect instruction may be included in the device interface. For example, the device interface may be as shown in 1501 in fig. 15, and the device information of the smart watch may be displayed in the device information card 1502. A connection control 1503 may be included in the device information card 1502 for a user to enter connection instructions.
S204, responding to the input of a connection instruction 3 by a user in the large-screen device, and establishing a physical link with the intelligent watch by the large-screen device according to the device information of the intelligent watch.
Specifically, the connection instruction 3 is used for indicating that the large-screen device is connected with the intelligent watch. The user can select a connection control 1503 in the interface 1501 in fig. 15 through the remote controller to input a connection instruction 3.
S205, the large screen device sends a pairing request to the intelligent watch.
S206, responding to the pairing request, and displaying a pairing request interface by the intelligent watch.
S207, responding to the pairing request interface input of the user on the intelligent watch to receive a pairing instruction 3, and pairing the large screen device with the intelligent watch according to the pairing key and establishing an SPP channel.
The processes of steps S204 to S207 are similar to those of steps S108 to S111, and will not be repeated. In step S207, the large-screen device already knows the pairing key of the smart watch, so that the large-screen device and the smart watch do not need to generate the pairing key based on the information such as the random number, the pin code, the MAC address and the like at the pairing interface, thereby simplifying the pairing process.
The above-mentioned processes of steps S202 to S207 are also called as the large screen device obtaining the information of the smart watch from the cloud, and pairing and connecting, and short for cloud pairing.
In this embodiment, a connection change schematic diagram of the smart watch, the mobile phone and the large screen device may be as shown in fig. 16. Referring to fig. 16 (a), before the method provided in this embodiment is performed, the mobile phone establishes a bluetooth connection with the smart watch. The bluetooth connection between the handset and the smart watch may include HFP channel, A2DP channel, SPP channel, etc. After that, the smart watch, the mobile phone and the large screen device perform the above steps S201 to S207, and the smart watch maintains the bluetooth connection with the mobile phone, and at the same time, the large screen device establishes the bluetooth connection with the smart watch by means of cloud pairing, as shown in (b) of fig. 16. The profile channel between the smart watch and the large screen device may include only the SPP channel.
In this embodiment, under the condition that the mobile phone establishes bluetooth connection with the smart watch, the large screen device obtains device information and a pairing key of the smart watch from the server, so as to realize connection with the smart watch. Because the large-screen equipment and the mobile phone are logged in the same user account, the large-screen equipment is user-trusted equipment, the intelligent watch can simultaneously establish two paths of Bluetooth connection with the mobile phone and the large-screen equipment, the safety of the mobile phone and the large-screen equipment cannot be influenced, the binding relation with the mobile phone does not need to be released, the user operation is simplified, the user can interact with the mobile phone and the large-screen equipment through the intelligent watch, and the user experience is improved. Moreover, the large-screen device acquires and displays the device information of the intelligent watch through the cloud server, and a user does not need to scan and find the device information of the intelligent watch through the large-screen device or the intelligent watch, so that the operation can be further simplified, and the user experience is improved. Moreover, the large-screen device can acquire the pairing key of the intelligent watch through the cloud service, and the pairing key does not need to be negotiated with the intelligent watch, so that the pairing process is simplified. In addition, the mobile phone synchronizes the information cloud of the intelligent watch under the condition that Bluetooth connection is established with the intelligent watch, so that when the large-screen device is matched with the intelligent watch cloud, the mobile phone and the intelligent watch are still in a Bluetooth connection state. In this case, the bluetooth connection between the smart watch and the large-screen device is generally only used for transmitting data, so when the profile channel is established, the large-screen device and the smart watch only establish the SPP channel, thus the connection process between the large-screen device and the smart watch can be simplified, the profile channel is saved, and the power consumption and resources of the large-screen device and the smart watch are saved.
Scene III:
the embodiment of the application also provides a method for connecting the wearable equipment, which can be applied to application scenes in which the terminal equipment is connected with a plurality of the wearable equipment. For example, a plurality of users wear a smart watch or a sports bracelet, respectively, and are connected with a large screen device through the smart watch or the sports bracelet to perform multi-person team fitness or games.
Fig. 17 is a schematic application scenario diagram of a connection method of a wearable device according to another embodiment of the present application. As shown in fig. 17, the large screen device is equipped with a sports APP, which may include team fitness games, such as multi-player race games. Multiple users (team members) can wear smart watches respectively, and the smart watches are connected with large-screen devices respectively. In the game process, the movement data of the team member are collected through the intelligent watch and uploaded to the large screen device based on the connection of the intelligent watch and the large screen device. The large screen device performs processing such as analysis and comparison on the motion data of each team member, and outputs a game interface, a game result and the like.
In this scenario, a process of establishing connection between the large-screen device and each smart watch will be described below.
Fig. 18 is a flowchart illustrating a connection method of a wearable device according to another embodiment of the present application. As shown in fig. 18, the method includes:
S301, in response to a user inputting a team forming instruction (also referred to as a first instruction) in the large screen device, the large screen device sends a team BLE broadcast (also referred to as a second broadcast message) to surrounding devices.
The team forming instruction is used for instructing the large screen device to establish connection with the plurality of wearable devices and form a team, namely, a game group or a body building group. Alternatively, the team command may carry the number of team members, i.e. the number of wearable devices in the group, etc.
Optionally, BLE broadcast is used to request multiple surrounding wearable devices to establish bluetooth connection with the large screen device and join the group. The BLE broadcast may carry one or more of device information, game information, scene information, number of players, etc. of the large screen device. The device information of the large-screen device may include one or more of a name of the large-screen device, a MAC address of the large-screen device, manufacturer information of the large-screen device, and the like, for example. The game information may include the name of the game being played, etc. The scene information is used for representing application scenes of connection between the plurality of wearable devices and the large-screen device, and the scene information can comprise team games, team fitness and the like.
Exemplary, fig. 19 is a schematic diagram of an interface for performing team fitness games through a large screen device according to an embodiment of the present application, where, as shown in fig. 19 (a), an option 1902 for a multi-player race game may be included in a sports interface 1901 of a sports APP. When the user selects the option 1902 of the multi-player racing game through the remote controller, the interface 1903 of the multi-player racing game is entered as shown in fig. 19 (b). A plurality of team game controls 1904 may be included in the interface, with the user selecting a corresponding team control 1904 based on the number of team members desired. Taking the example of a user selecting a 4-person team game, in response to the user's selection, the large screen device begins transmitting a team BLE broadcast to surrounding devices.
S302, after each smart watch (taking smart watch a, b, c, d as an example in fig. 18) receives the team BLE broadcast sent by the large-screen device, query information and prompt information are displayed according to the team BLE broadcast.
The inquiry information is used for inquiring whether the user agrees that the smart watch establishes connection with the large-screen device and joining in the team. After the prompt information is used for prompting the intelligent watch to be connected with the large screen device, data of the intelligent watch can be transmitted to the large screen device.
In a specific embodiment, after the smart watch receives the team BLE broadcast sent by the large screen device, the interface schematic may be as shown in fig. 20 (a). The interface includes inquiry information 2001 and prompt information 2002. Included in the inquiry information 2001 are an agreement control 2003 and a rejection control 2004.
And S303, responding to the fact that the user inputs a connection approval and team organization instruction in the interface of the intelligent watch, and sending a connection approval message and a team approval message to the large-screen device by the intelligent watch.
The consent connection message is used to characterize that the smart watch agrees to establish a connection with the large screen device. The consent team message characterizes that the smart watch agrees to connect and teams, i.e., agrees to join the group.
It will be appreciated that in this embodiment, the consent to connect message and the consent to team message are triggered by one instruction of the user—the consent to connect and team instruction. In other embodiments, the grant connect message and the grant team message may also be triggered by two instructions, respectively. In addition, the message of agreeing to connect and the message of agreeing to group can be two separate messages, send to the large-screen device separately, can also be two parts of content carried in the same message, send to the large-screen device through a message, the embodiment of the application does not limit this at all.
Illustratively, the user may enter the consent connection and team instruction by clicking on consent control 2003 in diagram (a) of fig. 20.
And S304, the large screen device responds to the connection agreement message and the team agreement message, and establishes physical links with each intelligent watch respectively.
S305, pairing the large screen device with each intelligent watch, establishing an SPP channel, and adding the intelligent watches into the group.
Specifically, after the physical link is established, the large-screen device sends a pairing request to the intelligent watch, and the large-screen device receives the pairing request and enters a pairing stage. After pairing is completed, the large-screen device and the intelligent watch establish an SPP channel, and accordingly Bluetooth connection is established between the large-screen device and the intelligent watch. After the bluetooth connection is completed, the interface of the smart watch may be as shown in (b) of fig. 20, and the interface of the large screen device may display information of team members, i.e., connected smart watches, as shown in (c) of fig. 19.
After the Bluetooth connection is established, the large-screen device adds the intelligent watch into the group.
S306, each intelligent watch collects motion data of the user.
Specifically, each intelligent watch can collect the motion data of the user in real time. Optionally, the user's athletic data may include, but is not limited to, one or more of the user's speed, number of steps, heart rate, blood oxygenation, blood pressure, etc.
S307, in response to the user inputting a game start instruction (also referred to as a second instruction) in the large screen device, the large screen device acquires motion data from the smart watch based on the SPP channel.
After a user inputs a game starting instruction, the large screen device can acquire motion data from the intelligent watch based on the established SPP channel, and then game or body-building content display is performed according to the motion data.
In this embodiment, the large screen device sends a team BLE broadcast to the surrounding devices, and the smart watch displays prompt information and inquiry information in response to the team BLE broadcast. The user inputs a command of agreeing to connect and forming a team in the interface of the intelligent watch, and the large screen equipment is characterized by being trusted by the user, namely, the large screen equipment is trusted by the user, so that the intelligent watch can directly establish Bluetooth connection with the large screen equipment, the large screen equipment can simultaneously establish Bluetooth connection with a plurality of intelligent watches, a plurality of intelligent watches can conveniently send data to the large screen equipment simultaneously, the use requirements of the user in the scenes of forming a team game and the like are met, and the user experience is improved. In addition, under the team game or body building scene, the intelligent watch and the large screen device only transmit data, so that a profile channel between the large screen device and the intelligent watch can only comprise an SPP channel, resources and power consumption of the intelligent watch and the large screen device can be saved, the risk of losing user information can be further reduced, and the safety of the user information is further improved. Meanwhile, through displaying prompt information and inquiry information in the interface of the intelligent watch, the user is informed of information such as use scenes, and therefore interaction with the user is increased, safety of the user information is improved, and user experience is improved.
In another embodiment, before the plurality of smart watches establish connection with the large screen device, if the smart watch has established a bluetooth connection with another terminal device (e.g., a mobile phone), the smart watch may maintain the bluetooth connection with the other terminal device and establish a second path bluetooth connection with the large screen device, and in this case, the smart watch may establish an SPP channel with only the large screen device. Thus, the user is convenient to interact with two devices of the mobile phone and the large screen device through the intelligent watch, user experience is improved, and the intelligent watch and the large screen device only establish the SPP channel so as to save resources and power consumption of the intelligent watch and the large screen device.
In this embodiment, the process of establishing bluetooth connection between a large-screen device and a plurality of wearable devices may be as shown in fig. 21. As seen in fig. 21 (a), the wearable device includes a smart watch a, a smart watch b, a smart watch c, and a smart watch d. Before the method provided in this embodiment is executed, the smart watch a has established a bluetooth connection with the handset. Optionally, the bluetooth connection between the mobile phone and the smart watch a may include an HFP channel, an A2DP channel, an SPP channel, and the like. Thereafter, each of the smart watch, the mobile phone, and the large screen device performs the above steps, and establishes bluetooth connection with the large screen device, respectively, wherein the smart watch a maintains bluetooth connection with the mobile phone, as shown in (b) of fig. 21. Alternatively, the bluetooth connection between each smart watch and the large screen device may include only the SPP channel.
In yet another embodiment, before the user inputs the team forming instruction in the large screen device, if the large screen device has established a bluetooth connection with a certain smart watch, the smart watch confirms that the smart watch has established a connection with the large screen device after receiving the BLE broadcast sent by the large screen device, and the smart watch maintains the connection and displays query information according to the BLE broadcast, so as to query whether the user agrees to form a team, i.e. whether the user agrees to join the group. After the user inputs the enqueue approval instruction, the smart watch sends a enqueue approval message to the large screen device. And after receiving the agreement to group message sent by the intelligent watch, the large screen device joins the intelligent watch into a group.
In the above embodiment, the short-range wireless communication connection is a bluetooth connection, and the profile channel of the classical bluetooth device is taken as an example for illustration, and the data transmission channel between the wearable device and the terminal device may be an SPP channel based on the classical bluetooth device. In some other embodiments, the bluetooth device of the wearable device may also be a BLE bluetooth device, or a dual mode bluetooth device, etc. In this case, a data transmission channel under its protocol (i.e., BLE data transmission channel) may also be established based on the BLE bluetooth device. Thus, for wearable devices (such as a sports bracelet) in which some bluetooth devices are BLE bluetooth devices or dual mode bluetooth devices, the method provided by the embodiment of the application is also applicable. Further, for the short-range wireless communication protocols of other communication protocols, the short-range wireless communication protocols also have respective data transmission channels, and when the transmission channels are established by using the method provided by the embodiment of the application, the transmission channels corresponding to the functions required under the protocol are established.
In addition, for the wearable device of the dual-mode Bluetooth device, when the connection is established between the wearable device and the large-screen device and between the wearable device and the mobile phone through the method provided by the embodiment of the application, the connection can be established between the wearable device and the mobile phone through the classical Bluetooth device, and the connection can be established between the wearable device and the large-screen device through the BLE Bluetooth device. Or the connection is established with the large screen device through the classical Bluetooth device, and the connection is established with the mobile phone through the BLE Bluetooth device, so that the flexibility of use is improved, and the applicability of the method is also improved.
Examples of the connection method of the wearable device provided by the embodiment of the application are described in detail above. It will be appreciated that the wearable device, the first terminal device and the second terminal device, in order to achieve the above-mentioned functions, comprise corresponding hardware and/or software modules for performing the respective functions. Those of skill in the art will readily appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as hardware or combinations of hardware and computer software. Whether a function is implemented as hardware or computer software driven hardware depends upon the particular application and design constraints imposed on the solution. Those skilled in the art may implement the described functionality using different approaches for each particular application in conjunction with the embodiments, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
The embodiment of the application can divide the functional modules of the wearable device, the first terminal device and the second terminal device according to the method example, for example, each function can be divided into each functional module corresponding to each function, for example, a detection unit, a processing unit, a display unit and the like, and two or more functions can be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. It should be noted that, in the embodiment of the present application, the division of the modules is schematic, which is merely a logic function division, and other division manners may be implemented in actual implementation.
It should be noted that, all relevant contents of each step related to the above method embodiment may be cited to the functional description of the corresponding functional module, which is not described herein.
The wearable device, the first terminal device and the second terminal device provided in the embodiment are configured to execute the connection method of the wearable device, so that the same effects as those of the implementation method can be achieved.
The hardware structure and the software architecture of the wearable device, the first terminal device and the second terminal device provided by the embodiment of the application are described below.
Fig. 22 is a schematic structural diagram of an example of a wearable device 100 according to an embodiment of the present application. As shown in fig. 22, 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 (universal serialbus, USB) interface 130, a charge 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, keys 170, a display 171, a sensor module 180, and the like. The sensor modules 180 may include an infrared light sensor 180A, a gyroscope sensor 180B, an acceleration sensor 180C, a touch sensor 180D, a photoplethysmography (photo plethysmo graphy, PPG) heart rate sensor 180E, an ambient light sensor 180F, and the like.
It is to be understood that the illustrated structure of the embodiments of the present application does not constitute a specific limitation on the wearable device 100. In other embodiments of the application, the wearable device 100 may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processingunit, GPU), an image signal processor (IMAGE SIGNAL processor, ISP), a controller, a video codec, a digital signal processor (DIGITAL SIGNAL processor, DSP), a baseband processor, and so forth. Wherein the different processing units may be separate devices or may be integrated in one or more processors. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.
A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory.
In some embodiments of the present application, the processor 110 may transmit a discoverable broadcast (i.e., a first broadcast) to surrounding devices upon receiving notification information transmitted by a terminal device. Wherein the notification information is used to indicate that there is a trusted device in the surroundings. The discoverable broadcast may carry device information of the wearable device 100 as well as bluetooth connected information (i.e., first information). Bluetooth connected information is used to characterize that the wearable device 100 has currently established a bluetooth connection with a certain terminal device.
The internal memory 121 may be used to store computer executable program code including instructions. The internal memory 121 may include a storage program area and a storage data area. The storage program area may store an operating system, an application program (such as voice navigation, image playing function, etc.) required for at least one function, and the like. The storage data area may store data created during use of the wearable device 100 (e.g., audio data, phonebook, etc.), and so on. In addition, the internal memory 121 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 110 performs various functional applications and data processing of the wearable device 100 by executing instructions stored in the internal memory 121 and/or instructions stored in a memory provided in the processor.
It should be understood that the interfacing relationship between the modules illustrated in the embodiments of the present application is only illustrative, and does not limit the structure of the wearable device 100. In other embodiments of the present application, the wearable device 100 may also use different interfacing manners, or a combination of multiple interfacing manners, in the above embodiments.
Solutions for wireless communication may be provided by the modules of the wearable device 100, such as the antenna 1, the wireless communication module 150, the modem processor, and the baseband processor, including but not limited to solutions for wireless communication such as wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (WIRELESS FIDELITY, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (NEAR FIELD communication, NFC), infrared technology (IR), and the like.
That is, the wireless communication module 150 can implement short-range wireless communication, or the wireless communication module 150 includes a short-range wireless communication module. In the embodiment of the present application, the wearable device 100 may perform close range wireless communication with the terminal device through the wireless communication module 150 based on a close range wireless communication protocol. For example, a bluetooth connection is established with a mobile phone, a large screen device, etc. through the wireless communication module 150 based on a bluetooth protocol, and data is transmitted based on the bluetooth connection. The wireless communication module 150 may include a bluetooth device, where the bluetooth device may be a classical bluetooth device, a BLE bluetooth device, or a dual-mode bluetooth device, which is not limited in this embodiment of the present application.
The antenna 1 is used for transmitting and receiving electromagnetic wave signals. Each antenna in the wearable device 100 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example, the antennas may be multiplexed into diversity antennas of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.
The wireless communication module 150 may be one or more devices that integrate at least one communication processing module. The wireless communication module 150 receives electromagnetic waves via an antenna, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 110. The wireless communication module 150 may also receive a signal to be transmitted from the processor 110, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via an antenna.
The wearable device 100 realizes a display function by a GPU, a display screen 171, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the 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 change display information.
The infrared light sensor 180A is a sensor for data processing using infrared rays, for sensing some characteristics of the surrounding environment, and also for measuring heat emitted from a human body, detecting movement, and the like.
The gyro sensor 180B may be used to determine a motion gesture of the wearable device 100. In some embodiments, the angular velocity of wearable device 100 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 180B. The gyro sensor 180B may be used to detect a motion state of a user.
The acceleration sensor 180C may detect the magnitude of acceleration of the wearable device 100 in various directions (typically three axes). The magnitude and direction of gravity can be detected when the wearable device 100 is stationary. The method can also be used for identifying the gesture of the wearable equipment and is applied to step counting, motion state feedback and the like.
The touch sensor 180D is also referred to as a "touch panel". The touch sensor 180K may be disposed on the display screen 171, and the touch sensor 180D and the display screen 171 form a touch screen, which is also called a "touch screen". The touch sensor 180D is used to detect a touch operation acting thereon or thereabout. The touch sensor 180D may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to a touch operation may be provided through the display screen 171. In other embodiments, the touch sensor 180D may also be disposed on the surface of the wearable device 100, different from the location of the display 194, for example, on the dial side of the smart watch.
The PPG heart rate sensor 180E is configured to detect reflected light intensity after absorption by human blood and tissue, trace a change in a volume of a blood vessel in a cardiac cycle, obtain a pulse waveform, and calculate a heart rate from the pulse waveform. The PPG heart rate sensor 180E is used for health monitoring of the user.
The ambient light sensor 180F is used to sense ambient light level. The wearable device 100 may adaptively adjust the display screen 194 brightness according to the perceived ambient light level. The ambient light sensor 180L may also be used to automatically adjust white balance when taking a photograph. The ambient light sensor 180F may also cooperate with a proximity light sensor (not shown) or the like to detect whether the wearable device 100 is in a worn state.
The structure of the first terminal apparatus 200 will be described below.
Fig. 23 is a schematic structural diagram of an example of a first terminal device 200 according to an embodiment of the present application. Taking the first terminal device 200 as a mobile phone, as shown in fig. 23, 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 key 290, a motor 291, an indicator 292, a camera 293, a display 294, a subscriber identity module (subscriber identification module, a SIM) card interface 295, and the like. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, a barometric sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, and the like.
It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the first terminal apparatus 200. In other embodiments of the application, the first terminal device 200 may include more or less components than shown, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
Processor 210 may include one or more processing units, for example, 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 Processor (NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.
The controller may be a neural center and a command center of the first terminal device 200. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.
A memory may also be provided in the processor 210 for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory.
In the embodiment of the present application, the processor 210 may cooperate with other modules to determine, when the wearable device and the first terminal device have established bluetooth connection, that the first terminal device enters the target geofence according to the information of at least one preset geofence and the device information in the trust ring, and that the trusted device exists in the target geofence, and send notification information to the wearable device.
The wireless communication function of the first terminal apparatus 200 can be implemented by the antenna 2, the antenna 3, the mobile communication module 250, the wireless communication module 260, a modem processor, a baseband processor, and the like.
The antennas 2 and 3 are used for transmitting and receiving electromagnetic wave signals. The structures of the antenna 2 and the antenna 3 in fig. 23 are only one example. Each antenna in the first terminal device 200 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example, the antenna 2 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.
The wireless communication module 260 may provide solutions for wireless communication including WLAN (e.g., wi-Fi network), bluetooth, GNSS, FM, NFC, IR, etc. applied on the first terminal device 200. The wireless communication module 260 may 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, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 210. The wireless communication module 260 may also receive a signal to be transmitted from the processor 210, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 3.
That is, the wireless communication module 260 can implement short-range wireless communication, or the wireless communication module 260 includes a short-range wireless communication module. In the embodiment of the present application, the first terminal device 200 may establish a short-range wireless communication connection with the wearable device 100 through the wireless communication module 260, and perform communication based on the short-range wireless communication connection. Optionally, the wireless communication module 260 may include a bluetooth device, where the bluetooth device may be a classical bluetooth device, a BLE bluetooth device, or a dual-mode bluetooth device, which is not limited in this embodiment of the present application.
In some embodiments, antenna 2 and mobile communication module 250 of first terminal device 200 are coupled, and antenna 3 and wireless communication module 260 are coupled, such that first terminal device 200 may communicate with a network and other devices via wireless communication techniques. The wireless communication techniques can include a global system for mobile communications (global system for mobile communications, GSM), general packet radio service (GENERAL PACKET radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation SATELLITE SYSTEM, GLONASS), a beidou satellite navigation system (beidou navigation SATELLITE SYSTEM, BDS), a quasi zenith satellite system (quasi-zenith SATELLITE SYSTEM, QZSS) and/or a satellite based augmentation system (SATELLITE BASED AUGMENTATION SYSTEMS, SBAS).
The first terminal apparatus 200 realizes a display function by a GPU, a display screen 294, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs that execute program instructions to generate or change display information.
The display 294 is used to display images, videos, and the like. The display 294 includes a display panel.
The first terminal apparatus 200 may implement a photographing function through an ISP, a camera 293, a video codec, a GPU, a display 294, an application processor, and the like.
The internal memory 221 may be used to store computer executable program code that includes instructions. The processor 210 executes various functional applications of the first terminal apparatus 200 and data processing by executing instructions stored in the internal memory 221. The internal memory 221 may include a storage program area and a storage data area. The storage area may store, among other things, an application program (such as a sports application program) required for an operating system, at least one function, and the like. The storage data area may store data created during use of the first terminal device 200 (e.g., device information of a wearable device paired with the first terminal device 200, a pairing key, and information of a preset geofence, device information within a trust ring, etc.), and the like. In addition, the internal memory 221 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, UFS, and the like.
The structure of the second terminal apparatus 300 will be described below.
Fig. 24 is a schematic structural diagram of an example of a second terminal device 300 according to an embodiment of the present application. The second terminal device 300 is exemplified as a large screen device. The large-screen device according to the embodiment of the present application may be a large-screen television, a large-screen computer, a large-screen mobile internet device (mobile INTERNET DEVICE, MID), a large-screen vehicle-mounted device, a large-screen Virtual Reality (VR) device, a large-screen augmented reality (augmented reality, AR) device, a large-screen smart home device, or other devices capable of establishing a short-range wireless communication connection, which is not limited herein.
As shown in fig. 24, the second terminal device 300 may include a processor 310, an external memory interface 320, an internal memory 321, a universal serial bus (universal serial bus, USB) interface 330, a charge 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 box interface 360B, a sensor module 370, keys 380, an indicator 381, a display 382, and the like. The sensor modules 370 may include, among other things, pressure sensors 370A, gyroscope sensors 370B, magnetic sensors 370C, distance sensors 370D, proximity sensors 370E, touch sensors 370F, ambient light sensors 370G, and the like.
It is to be understood that the structure illustrated in the embodiment of the present invention does not constitute a specific limitation on the second terminal apparatus 300. In other embodiments of the present invention, the second terminal device 300 may include more or less components than illustrated, or may combine certain components, or may split certain components, or may have a different arrangement of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.
The processor 310 may include one or more processing units, for example, the processor 310 may include an application processor, a modem processor, a GPU, an ISP, a controller, a memory, a video codec, a DSP, a baseband processor, and/or an NPU, etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.
The controller may be a neural center and a command center of the second terminal device 300. The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.
A memory may also be provided in the processor 310 for storing instructions and data. In some embodiments, the memory in the processor 310 is a cache memory. The memory may hold instructions or data that the processor 310 has just used or recycled. If the processor 310 needs to reuse the instruction or data, it may be called directly from the memory. Repeated accesses are avoided and the latency of the processor 310 is reduced, thereby improving the efficiency of the system.
The processor 310 may control 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 the discoverable broadcast transmitted by the wearable device 100 through the wireless communication module 350, it is paired with the wearable device 100 in response to a connection instruction input by the user.
The wireless communication function of the second terminal apparatus 300 can be implemented by the antenna 4, the wireless communication module 350, a modem processor, a baseband processor, and the like. The antenna 4 is used for transmitting and receiving electromagnetic wave signals. The antenna 4 in the second terminal device 300 may be used to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example, one of the plurality of antennas may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.
The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating 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. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through the audio module 360 (not limited to the speaker 360A, the speaker interface 360B, etc.), or displays images or video through the display screen 382. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the wireless communication module 350 or other functional module, independent of the processor 310.
The wireless communication module 350 may provide solutions for wireless communication including Bluetooth (BT), wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (WIRELESS FIDELITY, wi-Fi) network), global navigation satellite system (global navigation SATELLITE SYSTEM, GNSS), frequency modulation (frequencymodulation, FM), near field wireless communication technology (NEARFIELD COMMUNICATION, NFC), infrared technology (IR), etc., for use on the second terminal device 300. The wireless communication module 350 may be one or more devices that integrate 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 signals, and transmits the processed signals to the processor 310. The wireless communication module 350 may also receive a signal to be transmitted from the processor 310, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 4.
That is, the wireless communication module 350 can implement short-range wireless communication, or the wireless communication module 350 includes a short-range wireless communication module. In the embodiment of the present application, the second terminal device 300 may establish a short-range wireless communication connection with the wearable device 100 through the wireless communication module 350, and perform communication based on the short-range wireless communication connection. Optionally, the wireless communication module 350 may include a bluetooth device, where the bluetooth device may be a classical bluetooth device, a BLE bluetooth device, or a dual-mode bluetooth device, which is not limited in this embodiment of the present application.
The second terminal device 300 realizes a display function by a GPU, a display screen 382, an application processor, and the like. The GPU is a microprocessor for image processing, and is connected to the display screen 382 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 310 may include one or more GPUs that execute program instructions to generate or change display information.
The display 382 is for displaying images, videos, and the like. For example, after the second terminal device 300 receives the pairing request sent by the wearable device, the display screen 382 displays the pairing request, and prompts the user whether bluetooth connection with the wearable device is required. If the second terminal device 300 receives an operation for instructing to establish a bluetooth connection with the wearable device from the user, an interface for establishing a bluetooth connection with the wearable device 100 is displayed on the display screen 382 in response to the operation.
The internal memory 321 may be used to store computer executable program code comprising instructions. The processor 310 executes various functional applications of the second terminal apparatus 300 and data processing by executing instructions stored in the internal memory 321. The internal memory 321 may include a storage program area and a storage data area. The storage program area may store an operating system, an application program required for at least one function, and the like. The storage data area may store data created during use of the second terminal apparatus 300, and the like.
The software architecture of the wearable device 100, the first terminal device 200, and the second terminal device 300 is explained below.
The software systems of the wearable device 100, the first terminal device 200, and the second terminal device 300 may employ a layered architecture, an event driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. Taking an Android system with a layered architecture as an example, the embodiment of the application illustrates the software structures of the wearable device 100, the first terminal device 200 and the second terminal device 300.
Fig. 25 is a software structural block diagram of the wearable device 100 of the embodiment of the present application. The layered architecture divides the software into several layers, each with distinct roles and branches. The layers communicate with each other through a software interface. In some embodiments, the Android system is divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun rows (Android runtime) and system libraries, and a kernel layer, respectively. The application layer may include a series of application packages.
As shown in fig. 25, the application package may include calendar, clock, sleep monitor, WLAN, bluetooth, etc. applications.
The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.
As shown in fig. 25, 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.
The window manager is used for managing window programs. The window manager can acquire the size of the display screen, judge whether a status bar exists, lock the screen, intercept the screen and the like.
The content provider is used to store and retrieve data and make such data accessible to applications. The data may include images, audio, browsing history, bookmarks, and the like.
The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views.
The resource manager provides various resources to the application program, such as localization strings, icons, pictures, layout files, and the like.
The notification manager allows the application to display notification information in a status bar, can be used to communicate notification type messages, can automatically disappear after a short dwell, and does not require user interaction. Such as notification manager is used to inform that the download is complete, message alerts, etc. The notification manager may also be a notification in the form of a chart or scroll bar text that appears on the system top status bar, such as a notification of a background running application, or a notification that appears on the screen in the form of a dialog window. For example, a text message is prompted in a status bar, a prompt tone is emitted, the wearable device can vibrate, an indicator light blinks, and the like.
Bluetooth services (bluetooth service), bluetooth profiles (bluetooth profile), etc. may be included in the Bluetooth process.
Android runtime include core libraries and virtual machines. Android runtime is responsible for scheduling and management of the android system.
The core library comprises two parts, wherein one part is a function required to be called by java language, and the other part is an android core library.
The application layer and the application framework layer run in a virtual machine. The virtual machine executes java files of the application program layer and the application program framework layer as binary files. The virtual machine is used for executing the functions of object life cycle management, stack management, thread management, security and exception management, garbage collection and the like.
The system library may include a plurality of functional modules. Such as surface manager (surface manager), media library (media library), three-dimensional graphics processing library (e.g., openGL ES), 2D graphics engine (e.g., SGL), and bluetooth stack (bluetooth stack), etc.
The surface manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.
Media libraries support a variety of commonly used audio, video format playback and recording, still image files, and the like. The media library may support a variety of audio and video encoding formats, such as MPEG4, h.264, MP3, AAC, AMR, JPG, PNG, etc.
The three-dimensional graphic processing library is used for realizing three-dimensional graphic drawing, image rendering, synthesis, layer processing and the like.
The 2D graphics engine is a drawing engine for 2D drawing.
The Bluetooth protocol stack is used for providing all practical operations of Bluetooth, including switch Bluetooth, bluetooth management, search management, link management, realization of various profiles and the like.
The kernel layer is a layer between hardware and software. The kernel layer at least comprises a display driver, a Wi-Fi driver, a Bluetooth driver, an audio driver and a sensor driver.
In the embodiment of the present application, taking scenario one as an example, the wearable device 100 may receive the notification information sent by the first terminal device 200 through the bluetooth driver. And the Bluetooth driver finally uploads the received notification information to the Bluetooth application in the application layer through the Bluetooth protocol stack in the system library and the Bluetooth process in the application framework layer. Further, the bluetooth application sends discoverable broadcast to the large screen device through a bluetooth process, a bluetooth protocol stack and a bluetooth driver according to the notification information.
Fig. 26 is a software configuration block diagram of the first terminal apparatus 200 of the embodiment of the present application. Similar to the wearable device 100, the software architecture of the first terminal device 200 may include, from top to bottom, an application layer, an application framework layer, an Zhuoyun lines (Android runtime) and a system library, and a kernel layer. The application layer may include a series of application packages.
As shown in fig. 26, taking the first terminal device 200 as a mobile phone as an example, the application package may include applications such as a camera, a gallery, a calendar, a call, a map, WLAN, music, video, positioning, sports, and bluetooth.
The sports application may be, for example, sports health, etc. The positioning application user obtains the geographical location of the first terminal device 200.
The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.
As shown in fig. 26, 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, a bluetooth process, and the like.
The content provider is used to store and retrieve data and make such data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phonebooks, etc.
The view system includes visual controls, such as controls to display text, controls to display pictures, and the like. The view system may be used to build applications. The display interface may be composed of one or more views. For example, a display interface including a text message notification icon may include a view displaying text and a view displaying a picture.
The telephony manager is arranged to provide the communication functions of the first terminal device 200. Such as the management of call status (including on, hung-up, etc.).
The resource manager provides various resources for the application program, such as localization strings, icons, pictures, layout files, video files, and the like.
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 again.
The subscription manager is configured to accept subscriptions of other devices or modules in the first terminal device 200, and send a notification when a condition is satisfied. Specifically, in the embodiment of the present application, the subscription manager may accept subscription of the wearable device 100, and notify the wearable device 100 when the first terminal device 200 enters a certain preset geofence and there is a trusted device around.
The system library may include a plurality of functional modules. Such as surface manager (surface manager), media library (media library), three-dimensional graphics processing library (e.g., openGL ES), 2D graphics engine (e.g., SGL), image processor, bluetooth, etc.
The functions of each module in the system library are referred to the wearable device 100, and will not be described in detail.
The kernel layer is a layer between hardware and software. The kernel layer at least comprises a display driver, a camera driver, a Wi-Fi driver, a Bluetooth driver, an audio driver and a sensor driver.
Specifically, in the embodiment of the present application, the first terminal device 200 may acquire the geographic location of the first terminal device 200 through the positioning application program based on the software architecture, and determine that the first terminal device 200 enters the preset geofence according to the geographic location. A determination is made by the bluetooth application as to whether a cell phone trusted device exists in the current geofence. When it is determined that the first terminal device 200 enters the target geofence (any pre-set geofence) and that there is a cell phone trusted device in the target geofence, the subscription manager sends notification information to the wearable device 100. The notification information carries device information of the trusted device.
Fig. 27 is a software configuration block diagram of the second terminal device 300 of the embodiment of the present application. The system of the second terminal device 300 may be divided into four layers, from top to bottom, an application layer, an application framework layer, an Zhuoyun lines (Android runtime) and a system library, and a kernel layer, respectively. The application layer may include a series of application packages.
As shown in fig. 27, taking the second terminal device 300 as a large screen device as an example, the application package may include WLAN, bluetooth, sports, and other applications.
The application framework layer provides an application programming interface (application programming interface, API) and programming framework for the application of the application layer. The application framework layer includes a number of predefined functions.
As shown in fig. 27, 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.
The functions of each module of the application framework layer refer to the wearable device 100 and the first terminal device 200, and are not described in detail.
The system library may include a plurality of functional modules. Such as surface manager (surface manager), media library (media library), three-dimensional graphics processing library (e.g., openGL ES), 2D graphics engine (e.g., SGL), and bluetooth protocol stack, etc.
The kernel layer is a layer between hardware and software. The kernel layer at least comprises a display driver, a Wi-Fi driver, a Bluetooth driver, an audio driver and a sensor driver.
In the embodiment of the present application, the second terminal device 300 may display an interface in the use process of the bluetooth function to the user by calling a window manager of the application framework layer, a surface manager of the system library, and the like through the bluetooth application or the sports application of the application layer based on the software architecture. Based on the interface, the user can input a scan discovery instruction, a connection instruction, a confirm pairing instruction, an accept pairing instruction, and the like. The bluetooth application program responds to the instruction of the user, and realizes data interaction with the wearable device 100 through the mutual cooperation of the bluetooth process of the application program architecture layer, the bluetooth protocol of the system library and the bluetooth drive of the kernel layer, so as to realize bluetooth connection. In addition, in the embodiment of the present application, after the second terminal device 300 establishes bluetooth connection with the wearable device 100, the wearable device 100 may be added into a group based on the motion application program of the application program layer, and based on the motion data transmitted by the wearable device 100, a team game or a team fitness may be implemented.
The embodiment of the application also provides a computer readable storage medium, in which a computer program is stored, which when executed by a processor, causes the processor to execute the method for connecting the wearable device of any of the above embodiments.
The embodiment of the application also provides a computer program product, which when run on a computer, causes the computer to execute the above related steps to implement the method for connecting the wearable device in the above embodiment.
In addition, the embodiment of the application also provides a device which can be a chip, a component or a module, and the device can comprise a processor and a memory which are connected, wherein the memory is used for storing computer execution instructions, and when the device runs, the processor can execute the computer execution instructions stored in the memory so that the chip can execute the connection method of the wearable device in the method embodiments.
The wearable device, the first terminal device, the second terminal device, the computer readable storage medium, the computer program product, or the chip provided in this embodiment are used to execute the corresponding methods provided above, so that the beneficial effects achieved by the wearable device, the first terminal device, the second terminal device, the computer readable storage medium, the computer program product, or the chip can refer to the beneficial effects in the corresponding methods provided above, and are not described herein.
It will be appreciated by those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.
In the several embodiments provided by the present application, it should be understood that the disclosed apparatus and method may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of modules or units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and the parts shown as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.
The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods of the embodiments of the present application. The storage medium includes a U disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, an optical disk, or other various media capable of storing program codes.
The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the application is subject to the protection scope of the claims.
Claims (25)
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310647974.8A CN119071788A (en) | 2023-05-31 | 2023-05-31 | Wearable device connection method and device |
| PCT/CN2024/079196 WO2024244566A1 (en) | 2023-05-31 | 2024-02-29 | Method and device for connecting wearable device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310647974.8A CN119071788A (en) | 2023-05-31 | 2023-05-31 | Wearable device connection method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN119071788A true CN119071788A (en) | 2024-12-03 |
Family
ID=93636041
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310647974.8A Pending CN119071788A (en) | 2023-05-31 | 2023-05-31 | Wearable device connection method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN119071788A (en) |
| WO (1) | WO2024244566A1 (en) |
Family Cites Families (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN104104414A (en) * | 2014-06-18 | 2014-10-15 | 深圳市警豹电子科技有限公司 | Communication method for multiple bluetooth devices and forwarding method for bluetooth device matching information |
| CN104811903A (en) * | 2015-03-25 | 2015-07-29 | 惠州Tcl移动通信有限公司 | Method for establishing communication group and wearable device capable of establishing communication group |
| CN113225693B (en) * | 2019-04-18 | 2022-04-15 | 华为技术有限公司 | Bluetooth connection method, equipment and system |
| CN112615891B (en) * | 2019-09-18 | 2022-02-25 | 华为技术有限公司 | Pairing method and device |
| CN114915619B (en) * | 2021-01-29 | 2023-12-15 | 华为技术有限公司 | File sharing method and electronic equipment |
| CN115996371A (en) * | 2021-10-20 | 2023-04-21 | Oppo广东移动通信有限公司 | Bluetooth connection method and device, electronic equipment and storage medium |
| CN116193413B (en) * | 2023-04-27 | 2023-08-15 | 江西斐耳科技有限公司 | Bluetooth connection method, system, storage medium and device |
-
2023
- 2023-05-31 CN CN202310647974.8A patent/CN119071788A/en active Pending
-
2024
- 2024-02-29 WO PCT/CN2024/079196 patent/WO2024244566A1/en active Pending
Also Published As
| Publication number | Publication date |
|---|---|
| WO2024244566A1 (en) | 2024-12-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US12219470B2 (en) | Method for accessing wireless local area network and terminal | |
| WO2021023208A1 (en) | Data sharing method, graphical user interface, related device, and system | |
| US20230422154A1 (en) | Method for using cellular communication function, and related apparatus and system | |
| CN114077373A (en) | Interaction method between electronic devices and electronic devices | |
| US20230209438A1 (en) | Data Transmission Method and Electronic Device | |
| EP4247031B1 (en) | Access method and system and electronic device | |
| CN113676902B (en) | A system, method and electronic device for providing wireless Internet access | |
| CN114339698A (en) | Method for establishing wireless connection through equipment touch, electronic equipment and chip | |
| CN114499587B (en) | Audio synchronization communication method, system, wireless earphone, terminal and storage medium | |
| JP7234379B2 (en) | Methods and associated devices for accessing networks by smart home devices | |
| CN114449090B (en) | Data sharing method, device, system and electronic equipment, storage medium, chip | |
| CN114466339B (en) | Bluetooth pairing method, system, storage medium and chip | |
| CN114285938B (en) | Equipment recommendation method and device and computer readable storage medium | |
| CN114489876A (en) | Text input method, electronic equipment and system | |
| WO2023142993A1 (en) | Detection method, related electronic device and system | |
| CN117062252B (en) | A data transmission method and electronic device | |
| CN119071788A (en) | Wearable device connection method and device | |
| CN115242994B (en) | Video call system, method and device | |
| WO2023098356A1 (en) | Fingerprint identification method and system, and electronic device | |
| CN116567054A (en) | A detection method, related electronic equipment and system | |
| CN115297530B (en) | Network connection method and device | |
| CN116708674B (en) | Communication method and electronic equipment | |
| HK40068156B (en) | Audio pushing method and audio pushing system | |
| HK40068156A (en) | Audio pushing method and audio pushing system | |
| CN120475336A (en) | A collaborative method and electronic device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| CB02 | Change of applicant information |
Country or region after: China Address after: Unit 3401, unit a, building 6, Shenye Zhongcheng, No. 8089, Hongli West Road, Donghai community, Xiangmihu street, Futian District, Shenzhen, Guangdong 518040 Applicant after: Honor Terminal Co.,Ltd. Address before: 3401, unit a, building 6, Shenye Zhongcheng, No. 8089, Hongli West Road, Donghai community, Xiangmihu street, Futian District, Shenzhen, Guangdong Applicant before: Honor Device Co.,Ltd. Country or region before: China |
|
| CB02 | Change of applicant information |