Control method and device of wearable device, and wearable device

Abstract

The present disclosure provides a wearable device control method and device, and a wearable device, relating to the technical field of terminals. When the wearable device is in an unworn state, a first mode is entered based on first interaction information. During the duration of the first mode, a second mode is entered in response to second interaction information input by a user. The second mode is different from the first mode, and the second mode is a mode for managing the wearable device. The present disclosure can reduce the probability of the wearable device being triggered by mistake, thereby reducing the invalid power consumption of the wearable device and improving the user experience.

Description

Technical Field

[0001] This disclosure relates to the field of terminal technology, and in particular to a control method, apparatus and wearable device for a wearable device. Background Technology

[0002] Users can input interactive information into wearable devices to perform corresponding operations. However, if wearable devices are subjected to accidental collisions, friction, or pressure, they are prone to generating unintended interactions, leading to false triggering and affecting the user experience. Summary of the Invention

[0003] This disclosure provides a control method, apparatus, and wearable device for wearable devices, which can reduce the probability of wearable devices being falsely triggered, thereby reducing the ineffective power consumption of wearable devices and improving user experience.

[0004] The technical solution disclosed herein to solve the above-mentioned technical problems is as follows:

[0005] In a first aspect, this disclosure provides a control method for a wearable device. When the wearable device is not worn, it enters a first mode based on first interactive information. During the duration of the first mode, it enters a second mode in response to second interactive information input by the user. The second mode differs from the first mode; the second mode is a mode for managing the wearable device.

[0006] Based on the above technical solution, the present disclosure can be further improved as follows.

[0007] Furthermore, if no second interactive information is received within the target duration after entering the first mode, the first mode will be exited.

[0008] Furthermore, when entering the first mode, if first target information is detected, the first mode is exited. The first target information includes at least one of wearing information, Bluetooth pairing information, and storage information. And / or, when entering the second mode, if second target information is detected, the second mode is maintained until the management of the wearable device is completed. The second target information includes at least one of wearing information, Bluetooth pairing information, and storage information.

[0009] Furthermore, the first mode includes a mode for performing Bluetooth pairing tasks.

[0010] Furthermore, in response to third interactive information input by the user, a third mode is entered. The third mode includes a mode for performing Bluetooth pairing tasks, and the third interactive information differs from the first interactive information.

[0011] Furthermore, in response to entering the first mode, a first signal is output. And / or, in response to entering the second mode, a second signal is output; the second signal is different from the first signal.

[0012] Furthermore, both the first signal and the second signal are light signals. The second signal differs from the first signal in at least one of the following: color, flashing frequency, and brightness.

[0013] Furthermore, both the first signal and the second signal are sound signals. The second signal differs from the first signal in at least one of the following aspects: timbre, sound effect, intensity, and content.

[0014] Furthermore, while the wearable device is in the wearing state, a fourth interactive information input by the user is acquired. This fourth interactive information is input by the user via at least one button, and / or at least one touch control, and / or voice input. Based on this fourth interactive information, the recording function is activated. And / or, while the wearable device is in the wearing state and the recording function is activated, the recording function is deactivated in response to the input fourth interactive information.

[0015] Furthermore, while the wearable device is in the wearing state, the system acquires the fifth interaction information input by the user. This fifth interaction information is input by the user via at least one button, and / or at least one touch control, and / or voice input. Based on this fifth interaction information, the system controls the voice interaction function to be enabled. And / or, while the wearable device is in the wearing state and the voice interaction function is enabled, the system controls the voice interaction function to be disabled in response to the input fifth interaction information.

[0016] Furthermore, while the wearable device is in a wearing state, the system acquires a sixth interactive information input by the user. This sixth interactive information is input by the user via at least one button, and / or at least one touch control, and / or voice input. Based on this sixth interactive information, the system connects to the target device. And / or, while the wearable device is in a wearing state and connected to the target device, the system disconnects from the target device in response to the input of the sixth interactive information.

[0017] In a second aspect, this disclosure provides a control device for a wearable device, including a controller and a memory; the controller and the memory are coupled; the memory is used to store computer instructions; the computer instructions are loaded and executed by the controller to enable the control device for the wearable device to implement the control method for the wearable device as described in the first aspect and any one thereof.

[0018] Thirdly, this disclosure provides a wearable device configured to operate under the control of a wearable device control method as described in the first aspect and any one thereof.

[0019] Based on the control method, apparatus, and wearable device provided in this disclosure, the wearable device first enters a first mode based on first interactive information input by the user to filter out initial interference caused by a single accidental touch or improper operation. Then, only if, during the duration of the first mode, the wearable device receives second interactive information actively input by the user, will it enter a second mode for managing the wearable device. This allows for accurate identification of user intent, reduces the probability of the wearable device being accidentally triggered, thereby reducing unnecessary power consumption and improving user experience. Attached Figure Description

[0020] Figure 1 This is a schematic diagram of the hardware structure of a wearable device provided in an embodiment of this application;

[0021] Figure 2 A flowchart illustrating the control method for a wearable device provided in an embodiment of this application;

[0022] Figure 3 This is a schematic diagram of the management process for wearable devices provided in an embodiment of this application;

[0023] Figure 4 A schematic diagram of the structure of a control device for a wearable device provided in an embodiment of this application;

[0024] Figure 5 This is a schematic diagram illustrating one possible presentation of a wearable device provided in an embodiment of this application. Detailed Implementation

[0025] The technical solutions of the embodiments of this application will be described below with reference to the accompanying drawings. In the description of this application, unless otherwise stated, " / " indicates that the objects before and after are in an "or" relationship. For example, A / B can represent A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone, where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" refers to two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Furthermore, to facilitate a clear description of the technical solutions in the embodiments of this application, the terms "first" and "second" are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first" and "second" do not limit the quantity or execution order, and that "first" and "second" are not necessarily different. Meanwhile, in the embodiments of this application, words such as "exemplary" or "for example" are used to indicate that something is being used as an example, illustration, or description. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design schemes.

[0026] With the development of smart terminal technology, wearable devices have become deeply integrated into users' daily lives, serving as a key platform for convenient user interaction and functional control. Users can typically control wearable devices by inputting interactive information into them.

[0027] However, due to their inherent portability, wearable devices exhibit significant diversity in usage scenarios and storage conditions. Specifically, wearable devices may not only interact in ways that align with the user's intent when in use, but may also interact in ways that are not intended by the user when placed in a pocket, backpack, or on a table, due to unexpected external physical forces (such as accidental collisions, friction between objects, or compression).

[0028] Such non-user-intended interactions may not only cause wearable devices to operate unexpectedly, such as accidentally activating a function or accidentally modifying device settings, but may also increase the power consumption of wearable devices and even affect the normal use of wearable devices in certain scenarios, thus adversely affecting the user experience.

[0029] To address the issues of accidental triggering in wearable devices, this application provides a control method and apparatus for wearable devices. This method and apparatus can be applied to the control of wearable devices. In this application, "wearable device" refers to a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into a user's clothing or accessories. Specifically, wearable devices may include smartwatches, smart glasses, smart bracelets, smart helmets, smart jewelry, etc., but this application does not limit the scope of these examples.

[0030] The methods and apparatus provided in this application address high-risk scenarios where wearable devices, when not in use, are susceptible to unexpected physical interference such as collisions, friction, pressure, and accidental touches, as well as accidental triggering by users. For example, when placing unworn smart glasses in a backpack, the "factory reset" button may be accidentally pressed due to pressure from the item, resulting in the loss of long-term recorded health data. Another example is when a user accidentally presses a button used to unpair Bluetooth from a mobile phone and delete all synchronized records, requiring cumbersome reconfiguration and rendering some historical interaction data unrecoverable. Through a design of layered triggering modes and dynamic state control, the system distinguishes between the user's true operational intent and accidental interference, reducing the probability of accidental triggering of wearable devices.

[0031] The reason for focusing on the core control logic in the unworn state is not only because wearable devices are susceptible to unexpected interference such as collisions, friction, and pressure when not worn, but also because users cannot easily observe the status of the wearable device in real time. If improper operation (e.g., accidentally touching a key button) directly triggers high-risk management operations (e.g., data erasure, disconnection of key connections, system reset, etc.), it can easily cause irreparable damage. In the worn state, users can perceive the feedback from the wearable device in real time, allowing them to promptly stop erroneous operations, thus reducing the risk. Therefore, the method and apparatus provided in this application, when the wearable device is in the unworn state, must first enter a first mode based on the first interaction information input by the user to filter out initial interference caused by a single accidental touch or improper operation. Then, only if a second interaction information actively input by the user is received again during the first mode will the system switch to a second mode for device management. In this case, a single improper operation by the user cannot directly trigger a high-risk operation, thereby avoiding irreparable consequences.

[0032] Furthermore, for wearable devices in a worn state, the device control method provided in this application also incorporates convenient operation logic: users can activate or deactivate recording and voice interaction functions, as well as connect or disconnect from the target device, via buttons, touch controls, or voice input. Even if these functions are accidentally triggered while the user is wearing the wearable device, the user can quickly perceive and correct the error, thus eliminating the need for strict hierarchical control. This design complements the high-risk operation control measures in the unworn state, ensuring both ease of operation when the wearable device is worn and reducing the probability of accidental triggering when the device is unworn through state differentiation.

[0033] Figure 1 This is a schematic diagram of the hardware structure of a wearable device provided in an embodiment of this application.

[0034] like Figure 1 As shown, the wearable device 100 may include a control module 101, an image acquisition module 102, an image processing module 103, a communication module 104, a power module (including a power supply 105A, a first power supply module 105B, a second power supply module 105C, a power conversion module 105D, a charging management chip 105E, etc.), a transmission channel switching module 106, an audio acquisition module 107, an audio playback module 108, a sensor module (including an inertial detection module 109A, a wear detection module 109B, etc.), and a communication module 104. Interactive components (including buttons 110A, touch controls 110B, etc.), clock modules (including first clock unit 111A, second clock unit 111B, third clock unit 111C, etc.), indicators (including first indicator light 112A, second indicator light 112B and indicator light control circuit 112C, etc.), charging interface 113, dual-channel intelligent power amplifier 114, front-end module 115, duplexer 116, embedded multimedia memory card 117, internal memory 118, light sensing module 119, etc.

[0035] It is understood that the structures illustrated in the embodiments of this application do not constitute a specific limitation on the wearable device 100. In other embodiments of this application, the wearable device 100 may include more or fewer components than illustrated (e.g., in some examples, the sensor module may also include a barometric pressure sensor, a magnetic sensor, a distance sensor, a proximity sensor, a fingerprint sensor, a temperature sensor, a bone conduction sensor, etc.), or combine certain components (e.g., combine the second clock unit 111B and the third clock unit 111C), or split certain components (e.g., split the indicator light control circuit 109C into a first indicator light control circuit for controlling the first indicator light 109A and a second indicator light control circuit for controlling the second indicator light 109B), or arrange the components differently (e.g., the relative positions of the components change). The illustrated components can be implemented in hardware, software, or a combination of software and hardware.

[0036] The control module 101 may include one or more processing units, such as an application processor (AP), a modem processor, a controller, a memory, a digital signal processor (DSP), a baseband processor, and / or a neural network processing unit (NPU). These different processing units may be independent devices or integrated into one or more processors.

[0037] The controller can serve as the neural center and command center of the wearable device 100. The controller can generate operation control signals based on instruction opcodes and timing signals to control the fetching and execution of instructions.

[0038] The control module 101 may also include a memory for storing instructions and data. In some embodiments, the memory in the control module 101 is a cache memory. This memory can store instructions or data that the control module 101 has just used or that are used repeatedly. If the control module 101 needs to use the instruction or data again, it can directly retrieve it from the memory. This avoids repeated accesses, reduces the waiting time of the control module 101, and thus improves the efficiency of the system.

[0039] In some embodiments, the control module 101 may include one or more interfaces. Interfaces may include inter-integrated circuit (I2C) interfaces, inter-integrated circuit sound (I2S) interfaces, universal asynchronous receiver / transmitter (UART) interfaces, serial peripheral interface (SPI) interfaces, general-purpose input / output (GPIO) interfaces, universal serial bus (USB) interfaces, 5G radio frequency power amplifier (RFPA-5G) interfaces, 5G radio frequency receiver (RFRX-5G) interfaces, 24GHz radio frequency power amplifier (RFPA-24G) interfaces, Bluetooth front end (BT-FR) interfaces, pulse density modulation (PDM) interfaces, interrupt (INT) interfaces, and secure digital input / output (SDIO) interfaces, etc.

[0040] The I2C interface is a bidirectional synchronous serial bus, including a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the control module 101 may include multiple sets of I2C interfaces. The control module 101 can be coupled to the first power supply module 105B, the transmission channel switching module 106, the wear detection module 109B, the button 110A, the touch controller 110B, the indicator light control circuit 112C, the light sensor module 119, etc., through different I2C interfaces. For example, the control module 101 can be coupled to the wear detection module 109B through the I2C interface, enabling the control module 101 and the wear detection module 109B to communicate through the I2C interface to realize the wear detection function of the wearable device 100. The image processing module 103 can be coupled to the second power supply module 105C, the transmission channel switching module 106, the image acquisition module 102, etc., through different I2C interfaces. For example, the image processing module 103 can be coupled to the transmission channel switching module 106 via the I2C interface to receive control commands transmitted by the transmission channel switching module 106 to instruct the image processing module 103 to enter a sleep state.

[0041] The I2S interface can be used for audio communication. In some embodiments, the control module 101 may include multiple sets of I2S interfaces. The control module 101 can be coupled to the dual-channel intelligent power amplifier 114, the image processing module 103, etc., through different I2S interfaces. For example, the control module 101 can be coupled to the image processing module 103 through the I2S interface to send audio data to the image processing module 103. Correspondingly, the image processing module 103 may also include multiple sets of I2S interfaces. The image processing module 103 can be coupled to the control module 101 through the I2S interface to receive the audio data sent by the control module 101.

[0042] The UART interface is a universal serial data bus used for asynchronous communication. This bus can be a bidirectional communication bus. It converts the data to be transmitted between serial and parallel communication. In some embodiments, the UART interface is typically used to connect the control module 101 and the image processing module 103. For example, the control module 101 is coupled to the image processing module 103 via the UART interface, which serves as a communication control link and status transmission link between the control module 101 and the image processing module 103.

[0043] The SPI interface is a high-speed synchronous serial communication interface. The control module 101 may include multiple SPI interfaces. The control module 101 can be coupled to the image processing module 103 via the SPI interface to realize image data transmission between the control module 101 and the image processing module 103. The image processing module 103 may also include multiple SPI interfaces. The image processing module 103 can be coupled to the control module 101, internal memory 118, etc., via the SPI interface. For example, the image processing module 103 can be coupled to the internal memory 118 via the SPI interface to realize mutual transmission of image data.

[0044] The GPIO interface is configurable via software. It can be configured as either a control signal or a data signal. The control module 101 can be coupled to the dual-channel intelligent power amplifier 114, the transmission channel switching module 106, the image processing module 103, and the first power supply module 105B via the GPIO interface. Correspondingly, the image processing module 103 can also be coupled to the control module 101 via the GPIO interface.

[0045] The USB interface is an interface that conforms to the USB standard specification, specifically a Mini USB interface, a Micro USB interface, a USB Type-C interface, etc. The control module 101 and the image processing module 103 can be coupled via the USB interface to transmit large amounts of image data. In some embodiments, the user can choose to use either the USB interface or the SPI interface to implement image data transmission between the control module 101 and the image processing module 103, depending on their needs.

[0046] The RFPA-5G interface is used to connect the 5G RF power amplifier circuit and the control module 101. Its main function is to amplify the low-power 5G RF signal output by the control module 101 to enhance the transmission distance and coverage of the 5G signal. In the wearable device 100, the 5G RF power amplifier circuit may include a front-end module 115 and a duplexer 116. The control module 101 can couple to the front-end module 115, etc., via the RFPA-5G interface. For example, the control module 101 controls the operating state of the front-end module 115 through the RFPA-5G interface, amplifying the transmitted signal when the communication module 104 is transmitting 5G data to ensure the stability of long-distance communication.

[0047] The RFRX-5G interface is a key interface in the 5G signal reception link, used to transmit the 5G radio frequency signal received by the duplexer 116 to the modem processor of the control module 101. In the wearable device 100, the control module 101 can couple the duplexer 116 via the RFRX-5G interface. For example, when the wearable device 100 is in 5G communication mode, the duplexer 116 can transmit the received base station signal to the control module 101 via the RFRX-5G interface. After demodulation processing, valid data is obtained, ensuring normal reception of 5G communication.

[0048] The RFPA-24G interface is used to amplify the power of 24GHz band radio frequency signals, suitable for short-range, high-bandwidth wireless communication or sensing scenarios. In wearable device 100, control module 101 can couple duplexer 116 via the RFPA-24G interface. For example, if wearable device 100 has short-range wireless data transmission capability in the 24GHz band, control module 101 can control duplexer 116 via the RFPA-24G interface to enhance the transmission strength of the signal in this band, ensuring high-speed short-range communication with peripheral devices.

[0049] The BT-FR interface is the interface connecting the control module 101 and the Bluetooth front-end circuit, responsible for the transmission and reception of Bluetooth signals. In the wearable device 100, the control module 101 can couple to the duplexer 116 through the BT-FR interface to realize data transmission with the communication module 104 through the duplexer 116.

[0050] The PDM interface is a digital audio transmission interface that uses pulse density to represent the amplitude of audio signals, making it suitable for short-range, low-power audio data transmission. In the wearable device 100, the control module 101 can be coupled to the audio acquisition module 107 via the PDM interface. For example, after the audio acquisition module 107 acquires the user's voice signal, it transmits the digital audio signal to the control module 101 via the PDM interface, where it is processed to achieve voice interaction functionality.

[0051] The INT interface is used for signal transmission. In the wearable device 100, the control module 101 can couple sensor modules (such as the inertial detection module 109A and the wear detection module 109B), interactive components, and the light sensing module 119 via the INT interface. For example, when the wearable device 100 is in sleep mode, and the user moves the wearable device 100, the inertial detection module 109A can detect the pose information of the wearable device 100 and send the pose information to the control module 101 via the INT interface. The control module 101 can then control the wearable device 100 to enter the working mode based on the pose information. The image processing module 103 can also be coupled to the inertial detection module 109A via the INT interface, and the image processing module 103 can receive the pose information sent by the inertial detection module 109A via the INT interface.

[0052] The SDIO interface is used for connection and data interaction between the control module 101 and SDIO-compatible peripherals. In the wearable device 100, the control module 101 can couple with the embedded multimedia memory card 117 via the SDIO interface. For example, the control module 101 communicates with the embedded multimedia memory card 117 via the SDIO interface to store multimedia content into the embedded multimedia memory card 117.

[0053] It is understood that the interface connection relationships between the modules illustrated in the embodiments of this disclosure are merely illustrative and do not constitute a structural limitation on the wearable device 100. In other embodiments of this application, the wearable device 100 may also employ different interface connection methods or combinations of multiple interface connection methods as described in the above embodiments.

[0054] The image acquisition module 102 can be used to capture still images or videos. In some embodiments, the image acquisition module 102 may include a lens, a photosensitive element, etc. The lens can generate an optical image (light signal) of the corresponding object and project the generated optical image onto the photosensitive element. The photosensitive element may be a charge-coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element can convert the light signal into an electrical signal and transmit the obtained electrical signal to the image processing module 103. In some embodiments, the image acquisition module 102 may include one or N cameras, where N is a positive integer greater than 1.

[0055] The image processing module 103 may be an image signal processor (ISP). The image processing module 103 processes image data fed back by the image acquisition module 102. For example, when the snapshot function, live streaming function, or shooting function of the wearable device 100 is enabled, light can be transmitted through the lens of the image acquisition module 102 to the photosensitive element of the image acquisition module 102. The light signal is converted into an electrical signal, and the photosensitive element transmits the electrical signal to the image processing module 103 for processing, converting it into an image visible to the naked eye. The image processing module 103 can also perform algorithmic optimization of image noise, brightness, and skin tone; perform image stabilization; add audio to image data to obtain video data; and optimize parameters such as exposure and color temperature of the shooting scene. Furthermore, the image processing module 103 may also include at least one interface. The description of the interfaces included in the image processing module 103 can be found in the descriptions of the foregoing embodiments and will not be repeated here. In some embodiments, the image processing module 103 may be located within the image acquisition module 102.

[0056] The communication module 104 may include at least one antenna, a mobile communication module, a wireless communication module, etc. Specifically, the wireless communication function of the wearable device 100 can be implemented through the communication module 104, a modem processor, and a baseband processor. For example, the wearable device 100 can connect to a target unit through the communication module 104, the modem processor, and the baseband processor. The target unit can be a server or a target device (e.g., a vehicle infotainment system, a mobile phone, a tablet computer, a computer, etc.).

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

[0058] The mobile communication module can provide solutions for wireless communication, including 2G / 3G / 4G / 5G, applied to wearable device 100. The mobile communication module may include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module can receive electromagnetic waves via an antenna, and perform filtering, amplification, and other processing on the received electromagnetic waves before transmitting them to a modem processor for demodulation. The mobile communication module can also amplify the signal modulated by the modem processor and convert it into electromagnetic waves for radiation via the antenna. In some embodiments, at least some functional modules of the mobile communication module may be housed in the control module 101. In some embodiments, at least some functional modules of the mobile communication module and at least some modules of the control module 101 may be housed in the same device.

[0059] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs a sound signal through an audio device (not limited to audio playback module 108, etc.) or displays an image or video on a display screen. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the control module 101 and may be housed in the same device as the mobile communication module or other functional modules.

[0060] The wireless communication module can provide solutions for wireless communication applications on wearable device 100, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR) technologies. The wireless communication module can be one or more devices integrating at least one communication processing module. The wireless communication module receives electromagnetic waves via an antenna, modulates and filters the electromagnetic wave signals, and sends the processed signal to control module 101. The wireless communication module can also receive signals to be transmitted from control module 101, modulate and amplify them, and then convert them into electromagnetic waves for radiation via the antenna.

[0061] In some embodiments, the antenna may include antenna 1 and antenna 2. Antenna 1 and antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in the wearable device 100 may be used to cover one or more communication frequency bands. Different antennas may also be multiplexed to improve antenna utilization. For example, antenna 1 may be multiplexed as a diversity antenna for a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

[0062] The wearable device 100 has antenna 1 coupled to a mobile communication module and antenna 2 coupled to a wireless communication module, enabling the wearable device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time-Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies. The GNSS may include Global Positioning System (GPS), Global Navigation Satellite System (GLONASS), BeiDou Navigation Satellite System (BDS), Quasi-Zenith Satellite System (QZSS), and / or Satellite Based Augmentation Systems (SBAS).

[0063] The power supply 105A is the core energy storage component of the wearable device 100. It typically uses a miniaturized, high-energy-density lithium-ion battery (or lithium polymer battery) to suit the portable form factor and battery life requirements of the wearable device 100. Its core function is to provide basic DC power to the entire wearable device 100, serving as the energy source for the normal operation of all modules. The power supply 105A can continuously power all power-consuming components such as the control module 101 and sensor modules. At the same time, the power supply 105A can also feed back status information such as remaining power and voltage to the control module 101, allowing users to monitor the battery life of the wearable device 100 in real time.

[0064] The first power supply module 105B is connected to both the power supply 105A and the control module 101, providing power to the control module 101. Furthermore, even when the wearable device 100 is in a low-power mode (e.g., standby or sleep mode), the first power supply module 105B maintains a stable voltage output to ensure that the control module 101 does not interrupt its operation (e.g., maintaining the system clock, receiving wear information, etc.), thus preventing core functions from failing.

[0065] The second power supply module 105C is connected to both the power supply 105A and the image processing module 103, and is used to supply power to the image processing module 103. Furthermore, since the image acquisition module 102 is connected to the image processing module 103, the second power supply module 105C can indirectly supply power to the image acquisition module 102 through the image processing module 103. The second power supply module 105C is also connected to the first power supply module 105B. The control module 101 can control the second power supply module 105C through the first power supply module 105B to control the power supply status of the image processing module 103.

[0066] In addition, the power supply module may also include a third power supply module, which can be connected to the communication module 104, transmission channel switching module 106, audio acquisition module 107, audio playback module 108, sensor module, interactive component, clock module, indicator, dual-channel intelligent power amplifier 114, front-end module 115, duplexer 116, embedded multimedia storage card 117, internal memory 118, and light sensing module 119, respectively, to supply power to the aforementioned modules. The third power supply module is also connected to the first power supply module 105B. The control module 101 can control the third power supply module through the first power supply module 105B to control the power supply status of each module connected to the third power supply module.

[0067] The input terminal of the power conversion module 105D is connected to the power supply 105A, and the output terminal is connected to the first power supply module 105B, the second power supply module 105C, and the third power supply module, respectively. It is used to convert the fixed DC voltage output by the power supply 105A (for example, the 3.7V nominal voltage commonly found in lithium-ion batteries) into a multi-level stable voltage that meets the needs of different modules (the first power supply module 105B, the second power supply module 105C, and the third power supply module).

[0068] The charging management chip 105E is connected to the charging interface 113 and the power supply 105A respectively. It is used to receive external charging input through the charging interface 113 and send the external charging input to the power supply 105A to charge the power supply 105A. Specifically, the charging management chip 105E receives external wired charging input through the charging interface 113 on one end (in some scenarios, it is compatible with the input of wireless charging receiver circuits), and is directly coupled to the power supply 105A on the other end. It is responsible for coordinating the entire charging process: First, it automatically switches the charging mode. Based on the remaining power and temperature of the power supply 105A, it performs constant current fast charging (quickly replenishing power) when the power is low, and switches to constant voltage trickle charging (avoiding overcharging) when the power is close to full. Second, it integrates multiple protection logics. When the external charging voltage is abnormal (too high / too low), the charging current is too large, or the temperature of the power supply 105A exceeds the threshold (e.g., 45℃), it automatically cuts off the charging path to ensure charging safety. Third, it supports the "charging while supplying power" function. While charging the power supply 105A, it can supply power to the power conversion module 105D to ensure that the core components such as the control module 101, sensor module, and interactive component 111 can still work normally during charging without affecting user use. In addition, the charging management chip 105F also communicates with the control module 101 to provide feedback on charging progress (such as remaining charging time), charging status (such as fast charging / slow charging), and fault information (such as poor contact of the charging interface) to the control module 101, so that the control module 101 can inform the user through an indicator or user interface.

[0069] The audio acquisition module 107 is used to convert sound signals into electrical signals. For example, when the recording function or voice interaction function of the wearable device 100 is enabled, the user can input sound signals into the audio acquisition module 107 by speaking into it. In some embodiments, in addition to acquiring sound signals, the audio acquisition module 107 can also implement noise reduction. In other embodiments, the audio acquisition module 107 may include one or N microphones (also referred to as "microphones," "receivers," etc.), where N is a positive integer greater than 1.

[0070] The audio playback module 108 is used to convert audio electrical signals into sound signals. In some embodiments, the audio playback module 108 may include one or N speakers (also referred to as "loudspeakers," etc.), where N is a positive integer greater than 1. Users can listen to music or hands-free calls through the speaker 170A of the audio playback module 108. The inertial detection module 109A is used to determine the pose information of the wearable device 100. The inertial detection module 109A may be connected to the control module 101 and / or the image processing module 103 respectively, and is used to send pose information to the control module 101 and / or the image processing module 103 to support image stabilization based on the pose information. In some embodiments, the inertial detection module 109A may be an inertial measurement unit (IMU). An inertial measurement unit is composed of devices such as gyroscopes and accelerometers.

[0071] The transmission channel switching module 106 is connected to the control module 101, the image processing module 103, and the inertial detection module 109A, respectively. Under the control of the control module 101, the transmission channel switching module 106 connects the image processing module 103 and the inertial detection module 109A to enable data interaction between them, and / or, under the control of the control module 101, connects the control module 101 and the inertial detection module 109A to enable data interaction between them.

[0072] Specifically, the control module 101 can control the transmission channel switching module 106 to connect the inertial detection module 109A and the control module 101, or connect the inertial detection module 109A and the image processing module 103, based on different scenarios or user input instructions.

[0073] When the transmission channel switching module 106 connects the inertial detection module 109A and the control module 101, the inertial detection module 109A can send the determined pose information to the control module 101. When the transmission channel switching module 106 connects the inertial detection module 109A and the image processing module 103, the inertial detection module 109A can send the determined pose information to the image processing module 103.

[0074] It should be noted that those skilled in the art can customize the control logic of the control module 101 on the control transmission channel switching module 106 in various scenarios based on actual scenarios and needs, or as a user. For example, when the wearable device 100 has its live streaming function enabled, the control module 101 can control the transmission channel switching module 106 to connect the image processing module 103 and the inertial detection module 109A to trigger subsequent image stabilization at the image processing module 103, ensuring the smoothness of the wearable device 100's live stream. Alternatively, when the wearable device 100 has its camera function enabled, the control module 101 can control the transmission channel switching module 106 to connect the control module 101 and the inertial detection module 109A to trigger subsequent image stabilization by the control module 101 through an external unit such as a server, ensuring the image quality of the wearable device 100 when taking photos.

[0075] The wear detection module 109B can be used to determine whether the wearable device 100 is in a wearing state. For example, the wear detection module 109B can generate wearing information when it comes into contact with human skin. The wearing information is used to characterize that the wearable device 100 is in a wearing state. The wear detection module 109B can be connected to the control module 101 and send the wearing information to the control module 101 after generating it, so that the control module 101 can sense the wearing state of the wearable device 100. In some embodiments of this application, the wear detection module 109B can be at least one of capacitive, infrared reflective, or pressure sensors.

[0076] Button 110A may include mechanical buttons and membrane buttons, supporting single-button or multi-button designs. Its functions can be defined via software, such as a power button (e.g., long press to turn on / off, short press to wake the screen) and function keys (e.g., single click to start taking photos, double click to switch music). Button 110A is connected to control module 101 and can generate key signal inputs related to user settings and function control of the wearable device 100, and send these key signal inputs to control module 101.

[0077] The touch controller 110B may include a capacitive touch panel or touch strip, supporting single-point touch, swipe, long press, and other operations. For example, swiping the touch strip adjusts the volume, and long pressing the capacitive touch panel activates voice interaction. The touch controller 110B can be connected to the control module 101. When the touch controller 110B receives a touch, it generates a touch signal and sends the touch signal to the control module 101. The control module 101 can execute the command corresponding to the received touch signal.

[0078] The first clock unit 111A can be a real-time clock, connected to the control module, used to maintain the system time (year / month / day / hour / minute / second). Even when the wearable device 100 is in sleep mode, the first clock unit 111A can continue to work; it outputs a time signal to the control module 101, which can be used for log recording (such as timestamps of exercise data), timed reminders (such as alarm clocks), and also supports data retention when power is off to avoid time loss. In some embodiments of this application, the first clock unit 111A can use a 32kHz crystal oscillator.

[0079] The second clock unit 111B can be a high-frequency clock unit, connected to the control module 101, used to provide high-speed timing signals to the control module 101 to support complex calculations (such as 5G communication protocol parsing); the clock frequency can be dynamically adjusted according to the load of the control module 101, outputting a high-frequency clock under high load to ensure computing power, and reducing the frequency under low load to reduce power consumption. In some embodiments of this application, the second clock unit 111B can use a 24MHz crystal oscillator or a 48MHz crystal oscillator.

[0080] The third clock unit 111C can be a high-frequency clock unit, connected to the image processing module 103, used to provide high-speed timing signals to the image processing module 103 to support complex calculations (such as image processing); the clock frequency can be dynamically adjusted according to the load of the image processing module 103, outputting a high-frequency clock under high load to ensure computing power, and reducing the frequency under low load to reduce power consumption. In some embodiments of this application, the third clock unit 111C can use a 24MHz crystal oscillator or a 48MHz crystal oscillator.

[0081] The first indicator light 112A can be used to provide feedback on the status of the image acquisition module 102 and the image processing module 103. For example, a flashing green light on the first indicator light 112A indicates that the image acquisition module 102 and the image processing module 103 are in operation. A flashing red light on the first indicator light 112A indicates that the image acquisition module 102 and the image processing module 103 are in a non-operational state (the image acquisition module 102 is in a turned-off state, and the image processing module 103 is in a sleep or turned-off state). In other embodiments of this application, the first indicator light 112A can also be used to provide feedback on the charging status or battery status of the wearable device 100. For example, a solid green light on the first indicator light 112A indicates that the wearable device 100 is charging. A solid red light on the first indicator light 112A indicates that the battery level of the wearable device 100 is below a battery threshold.

[0082] The second indicator light 112B can be used to indicate the mode of the wearable device 100. For example, a solid green second indicator light 112B indicates that the wearable device 100 is in working mode. A solid red second indicator light 112B indicates that the wearable device 100 is in standby mode, and a solid white second indicator light 112B indicates that the wearable device 100 is in sleep mode. As another example, a solid blue second indicator light 112B indicates that the wearable device 100 is in the first mode. A flashing orange second indicator light 112B indicates that the wearable device 100 is in the second mode, and a flashing blue second indicator light 112B indicates that the wearable device 100 is in the third mode.

[0083] The input terminal of the indicator light control circuit 112C is connected to the control module 101, and the output terminal is connected to the first indicator light 112A and the second indicator light 112B respectively. It is used to control the lighting status, color, frequency and other properties of the first indicator light 112A and the second indicator light 112B under the control of the control module 101.

[0084] The charging interface 113 can be used to receive external electrical energy input and transmit that electrical energy input to the power supply 105A to increase the power of the power supply 105A. The charging interface 113 can be a quick-connect electrical connector. For example, the charging interface 113 can be a flexible electrical connector. A flexible electrical connector can include a pogo pin. A pogo pin is a cylindrical electronic connector with an internal spring, mainly composed of a pin, a spring, and a pin tube, used for reliable electrical signal transmission or current conduction in the wearable device 100. The spring design of the charging interface 113 provides stable contact pressure and maintains connection reliability after multiple insertions and removals.

[0085] The dual-channel intelligent power amplifier 114 is used to amplify and intelligently optimize the audio signal sent by the control module 101, and to drive the audio playback module 108 to output the corresponding audio.

[0086] The front-end module 115 is used to amplify, filter, and control the switching of received radio frequency signals (5G, 24GHz, Bluetooth signals, etc.) to improve the strength and anti-interference capability of the radio frequency signals. The front-end module 115 can be connected to the control module 101 and the communication module 104 respectively to realize the transmission of communication signals between the control module 101 and the communication module 104.

[0087] The duplexer 116 is connected to the front-end module 115, the control module 101, and the communication module 104 respectively. It is used to isolate the transmitted and received signals to avoid mutual interference, and at the same time supports the switching and multiplexing of multi-band signals.

[0088] The embedded multimedia memory card 117 is connected to the control module 101 and is a high-capacity non-volatile storage component of the wearable device 100. It is used for long-term storage of device firmware and user data (such as images, videos, and health records) and supports high-speed read and write and stable storage.

[0089] The internal memory 118 is connected to the image processing module 103 and serves as a high-speed temporary storage component of the wearable device 100. It is used to temporarily store instructions and data generated during the operation of the image processing module 103, thereby improving data access speed. In some embodiments of this application, the internal memory 118 may be NOR flash memory.

[0090] The light sensing module 119 is connected to the control module 101 and is used to detect ambient light values, providing data support for display adjustment and function adaptation of the wearable device 100. In some embodiments of this application, after detecting the ambient light value, the light sensing module 119 can send the ambient light value to the control module 101. After receiving the ambient light value, if the ambient light value is lower than the light sensing threshold, and the image acquisition module 102 and the image processing module 103 are in operation, the control module 101 can control the image acquisition module 102 to switch to a shutdown state and the image processing module 103 to a sleep state or a shutdown state.

[0091] The embodiments of this application provide the above-mentioned... Figure 1 The wearable device 100 shown can operate under the control of the wearable device control method provided in the embodiments of this application. The following will be combined with... Figure 1 The wearable device 100 shown illustrates the control method for the wearable device provided in this application embodiment.

[0092] Figure 2 This is a flowchart illustrating the control method for a wearable device provided in an embodiment of this application. Figure 2 As shown, the control method for wearable devices provided in this application embodiment may include the following steps:

[0093] S201: When the wearable device is not worn, enter the first mode based on the first interaction information.

[0094] The wearable device may include a component for detecting the wearing status of the wearable device. The wearing status of the wearable device may include a worn state and an unworn state. For example, the component for detecting the wearing status of the wearable device may be a wearing detection module. The wearing detection module can confirm the wearing status of the wearable device by detecting human biometric features. Alternatively, the wearing detection module can confirm the wearing status of the wearable device by infrared sensing. This application does not limit the method by which the wearing detection module confirms the wearing status of the wearable device.

[0095] The wearable device may also include at least one interactive component and / or an audio acquisition module. The at least one interactive component may include at least one button and / or at least one touch control.

[0096] Users can input first interactive information into a wearable device by selecting at least one button. The selection operation of the user on the at least one button can include long-pressing, tapping, etc. For example, a user can input first interactive information into the wearable device by long-pressing a target button among at least one of the buttons for at least 5 seconds (5s).

[0097] Alternatively, a user can input first interactive information into the wearable device by selecting at least one touch control. The user's selection of the at least one touch control may include long-pressing, tapping, swiping, etc. For example, a user can long-press a target touch control among at least one touch control for at least 5 seconds to input first interactive information into the wearable device.

[0098] Alternatively, with the voice interaction function of the wearable device enabled, the user can issue a voice command to input the first interactive information into the wearable device. For example, with the voice interaction function of the wearable device enabled, the user can issue the voice command "Enter First Mode" to input the first interactive information into the wearable device.

[0099] The first mode is a preparatory mode for managing wearable devices. Managing wearable devices includes at least one of the following: system handling, factory reset, data management, application management, configuration management, and parameter management. The following will describe the content of managing wearable devices in detail with specific examples.

[0100] Managing wearable devices can include system actions, such as updating the system version, detecting and fixing system vulnerabilities.

[0101] Managing wearable devices can also include resetting them to factory settings. This involves deleting user data (e.g., user identification information, health records, captured image data), installed applications, and configured device parameters from the wearable device, restoring all stored data, installed applications, and configured parameters to their initial factory state.

[0102] Managing wearable devices can also include managing their data. This includes, for example, deleting or modifying user identity information stored in the wearable device, backing up critical data stored in the wearable device, and recovering data that has been deleted from the wearable device.

[0103] Managing wearable devices can also include managing the applications installed on them. For example, deleting applications already installed on a wearable device, or installing new applications.

[0104] Managing wearable devices can also include managing their configurations. This includes, for example, clearing or resetting network configurations (Bluetooth pairing information), account configurations (login accounts), and feature configurations (permission settings).

[0105] Managing wearable devices can also include managing their parameters. For example, resetting or adjusting the device's functional parameters (sensor sensitivity, performance parameters, etc.).

[0106] When the wearable device is not worn, it enters the first mode based on the first interaction information, which can provide pre-state support for subsequent management operations: it avoids the accidental start of management operations when the wearable device is not worn, reducing unnecessary power consumption; and it provides a convenient entry point for the management operations that the user may perform later, improving the pertinence and efficiency of management operations.

[0107] S202: During the duration of the first mode, in response to the second interactive information input by the user, enter the second mode.

[0108] The second mode differs from the first mode. The second mode is for managing wearable devices.

[0109] Furthermore, the method by which a user inputs the second interactive information into the wearable device can refer to the aforementioned description of a user inputting the first interactive information into the wearable device. That is, the user can input the second interactive information into the wearable device through at least one button, and / or at least one touch control, and / or voice.

[0110] The method by which the user inputs the second interactive information into the wearable device can be the same as the method by which the wearable device inputs the first interactive information. For example, when the wearable device is not being worn, the user inputs the first interactive information into the wearable device by pressing and holding a target touch control among at least one touch control for at least 5 seconds. The wearable device then enters a second mode based on the first interactive information input by the user. Subsequently, during the duration of the first mode, the user can again input the second interactive information into the wearable device by pressing and holding a target touch control among at least one touch control for at least 5 seconds. The wearable device can then enter the second mode in response to the second interactive information input by the user.

[0111] The way a user inputs second interactive information into a wearable device can also differ from the way the wearable device inputs first interactive information. For example, when the wearable device is not being worn, the user inputs first interactive information by pressing and holding a target touch control among at least one touch control for at least 5 seconds. The wearable device then enters a second mode based on the user's input of the first interactive information. Afterward, during the duration of the first mode, the user can input second interactive information into the wearable device by continuously tapping a target button among at least one button five times. The wearable device can then enter the second mode in response to the user's input of the second interactive information.

[0112] Based on the embodiment of this application, the wearable device is first put into a preparation mode (first mode) for managing the wearable device, and then put into an execution mode (second mode) for managing the wearable device. This can accurately locate the user's management needs when the wearable device is not worn, effectively reduce the probability of false triggering of the wearable device, reduce the ineffective power consumption of the wearable device, and improve the battery life of the wearable device.

[0113] In addition, in some embodiments, if the wearable device does not receive the second interaction information within the target duration after entering the first mode, it will exit the first mode.

[0114] It should be noted that those skilled in the art can set the specific value of the target duration based on actual scenarios and needs, or users can also customize the specific value of the target duration through interaction with the wearable device. For example, the target duration can be set to 3 minutes (3 min). This customizable setting of the target duration allows it to adapt to diverse usage scenarios and user needs.

[0115] For example, a wearable device may include a clock module and a control module. After the wearable device enters a first mode, the control module may monitor the duration of the first mode based on the clock module. If the control module detects that the duration of the first mode exceeds a target duration based on the clock module, the control module may control the wearable device to exit the first mode, and may also control the wearable device to enter a default low-power state (e.g., sleep state or standby state).

[0116] This automatic exit mechanism effectively prevents the first mode from remaining active for extended periods without subsequent operation, thus reducing unnecessary power consumption and extending the wearable device's battery life. Furthermore, the absence of user intervention to exit the first mode reduces the user's workload and redundant interactions with the device. Additionally, this automatic exit mechanism reduces the risk of accidental triggering (e.g., accidental activation of other functional modules) that may result from the first mode remaining active for an extended period, further minimizing unnecessary power consumption and contributing to longer battery life.

[0117] Figure 3 This is a schematic diagram illustrating the management process of wearable devices provided in an embodiment of this application. Figure 3 As shown, in some embodiments, when a wearable device enters a first mode, if it detects first target information, it exits the first mode. The first target information includes at least one of wearing information, Bluetooth pairing information, and storage information. And / or, when entering a second mode, if it detects second target information, it maintains the second mode until the management of the wearable device is completed; the second target information includes at least one of wearing information, Bluetooth pairing information, and storage information.

[0118] Specifically, wearing information can be generated by the wearing detection module of the wearable device. For example, the wearing detection module can detect changes in human biometrics (such as skin capacitance) or infrared sensing signals from nothing to something, confirm that the wearable device has changed from an unworn state to a worn state, and send the corresponding wearing information to the control module of the wearable device.

[0119] The communication module of a wearable device may have Bluetooth functionality. Bluetooth pairing information can be determined based on the wearable device's communication module. For example, when the communication module receives an input Bluetooth pairing request, or when the communication module generates a Bluetooth pairing request to send to an external device, or when the communication module is in a Bluetooth pairing state, the communication module can generate Bluetooth pairing information and send it to the wearable device.

[0120] Storage information can be generated based on the wearable device's light-sensing module or specific sensors. Taking storage information generated based on the light-sensing module as an example, when the wearable device is placed in the storage box, the light-sensing module detects a sudden drop in ambient light sensitivity and maintains a low sensitivity state, thus generating storage information to characterize that the wearable device is in a stored state. The light-sensing module can then send this storage information to the control module.

[0121] Upon receiving the aforementioned first target information, the wearable device's control module can control the wearable device to exit the first mode. This design allows the wearable device to dynamically adjust its state according to the actual scenario. For example, when wearing information is detected, it indicates that the user may be switching from a management preparation state to a usage state; exiting the first mode can avoid conflicts between management-related functions and daily usage functions. When Bluetooth pairing information is detected, it indicates that the device has entered a communication interaction scenario; exiting the first mode prioritizes the normal operation of communication functions. When storage information is detected, it indicates that the device is in a storage state; exiting the first mode and entering a low-power state can reduce unnecessary energy consumption, thereby improving the intelligence of device state switching and scenario adaptability.

[0122] Furthermore, since the first mode is a preparatory mode for managing wearable devices, if the first target information (i.e., the scenario has deviated from the management requirements) is detected and the first mode is maintained, the second interactive information may be triggered due to user misoperation (such as accidentally touching interactive components after wearing the device or accidentally touching touch controls when storing it), thus mistakenly entering the management mode. Timely exiting the first mode can prevent such unintended management mis-triggers from the source, ensuring that management operations are only initiated in the user's clearly defined management scenario. It also reduces the resource consumption of wearable devices due to accidental management operations (such as avoiding accidental startup of management-related system processes). This improves the intelligence and scenario adaptability of wearable device state switching, ensures the accuracy of wearable device management operations, and benefits the user experience.

[0123] When a wearable device enters its second mode, if the aforementioned second target information is detected, the device will maintain this mode until management is complete. Since the second mode is the execution mode for managing the wearable device (such as performing factory resets or system updates), these operations typically need to be executed completely to avoid incomplete data or system malfunctions. Therefore, even if the aforementioned second target information is detected, the wearable device will prioritize ensuring the continuity of management operations. This design ensures the integrity and reliability of management operations, preventing malfunctions due to interruptions (e.g., interrupted factory resets may result in residual data or corrupted system files). It also reduces the burden on users who need to re-initiate management operations when switching scenarios (e.g., wearing or storing the device), improving management efficiency and enhancing user experience.

[0124] Additionally, in some embodiments, the first mode includes a mode for performing Bluetooth pairing tasks. That is, the first mode may specifically be a preparation and execution state for establishing a Bluetooth connection between the wearable device and an external device (e.g., a smartphone, tablet, other wearable devices, etc.).

[0125] Among them, the communication module (including Bluetooth front-end circuit, duplexer, etc.), control module and interaction components of the wearable device can jointly support the operation of the first mode.

[0126] When the wearable device is not worn, the user can input initial interaction information into the device. Based on this information, the control module can drive the communication module to activate Bluetooth, enter a discoverable state, and transmit a Bluetooth broadcast signal (including device identification information) via a duplexer and antenna. In this state, the communication module can continuously listen for pairing requests from external devices. Once a legitimate request is received (e.g., a signal containing the correct pairing code), the control module will coordinate with the communication module to complete pairing negotiations (e.g., key exchange, link encryption) until a stable Bluetooth connection is established.

[0127] This design, which explicitly defines the first mode as the Bluetooth pairing task mode, provides users with a convenient way to initiate the Bluetooth pairing process. Specifically, users do not need to rely on complex menu hierarchies or additional devices; they only need to input the first interaction information using their familiar interaction method when the wearable device is not being worn. For example, users accustomed to physical button operation can long-press a preset target button to input the first interaction information into the wearable device, thereby enabling the wearable device to quickly initiate the Bluetooth pairing task.

[0128] Additionally, in some embodiments, the wearable device may also enter a third mode in response to third interactive information input by the user. The third mode includes a mode for performing Bluetooth pairing tasks, and the third interactive information differs from the first interactive information.

[0129] Although both the first and third modes are for performing Bluetooth pairing tasks, the third mode is not a preparatory mode for managing the wearable device because it is not triggered by the initial user input. In the third mode, the wearable device's control module can only drive the communication module to execute Bluetooth pairing-related functionalities, such as activating Bluetooth, entering discoverable state, sending Bluetooth broadcast signals, responding to pairing requests from external devices, and completing pairing negotiations. It will not activate any preparatory mechanisms related to device management (such as reserving system resources for subsequent management operations or triggering management mode listening logic).

[0130] This means that even if a user inputs the second interactive information in the third mode, which would normally trigger the second mode, the control module will not respond to enter the mode for managing the wearable device. This clearly distinguishes between a standalone scenario solely for Bluetooth pairing and a scenario involving the management of potentially associated devices, precisely catering to diverse user needs. When a user only needs to complete Bluetooth pairing (e.g., temporarily connecting to an external device for data transfer) and has no management intent, they can input the third interactive information to put the wearable device into the third mode. This allows the wearable device to directly and efficiently perform Bluetooth pairing, avoiding unnecessary management preparation processes. Furthermore, by differentiating the functional boundaries between the first and third modes, user confusion due to similar operations is reduced. This ensures that management operations are only triggered when the user explicitly initiates management preparation through the first interactive information, improving the accuracy of wearable device function calls and the convenience of user operation.

[0131] Furthermore, if a wearable device does not receive any input interaction information within a certain period of time after entering the third mode, it can exit the third mode.

[0132] It should be noted that those skilled in the art can set the specific value of the aforementioned duration based on actual scenarios and needs, or users can also customize the specific value of the aforementioned duration through interaction with the wearable device. For example, the aforementioned duration can be set to 3 minutes (3 min). This customizable setting of the aforementioned duration allows it to adapt to diverse usage scenarios and user needs.

[0133] The description of the wearable device's monitoring of the duration of the third mode can be found in the description of the wearable device's monitoring of the duration of the first mode in the foregoing embodiments, and will not be repeated here.

[0134] This automatic exit mechanism for the third mode effectively prevents the third mode from remaining active for extended periods without subsequent operation, thereby reducing the wasted power consumption of wearable devices and improving their battery life. Furthermore, since users do not need to actively exit the third mode, it reduces the user's workload and minimizes redundant interactions with the wearable device. In addition, this automatic exit mechanism reduces the risk of accidental triggering caused by the third mode remaining active for extended periods (e.g., accidental connection to devices not intended by the user, leading to security issues), further reducing wasted power consumption and improving battery life.

[0135] In addition, wearable devices can enter a third mode in various scenarios.

[0136] Specifically, wearable devices can enter a third mode in response to user input of third-party interaction information while being worn. Wearable devices can also enter a third mode in response to user input of third-party interaction information when not worn and not stored. The following will provide a detailed explanation of how wearable devices enter the third mode in different scenarios.

[0137] In the first scenario, when the wearable device is in the wearing state, the user can trigger the wearable device to enter the third mode by inputting corresponding third interactive information into the wearable device (such as long-pressing the button associated with the Bluetooth pairing function on the wearable device, or making a specific swipe on the touch control associated with the Bluetooth pairing function, or inputting a specific voice command into the wearable device).

[0138] After the wearable device enters the third mode, it can output a prompt signal. This prompt signal may include an audio signal and / or a light signal. Taking a light signal as an example, the output of the prompt signal may depend on the wearable device's indicator. The wearable device's indicator may include an indicator light (such as the first indicator light described above) and an indicator light control circuit. When the control module determines that the wearable device has entered the third mode, it can send a target control command to the indicator light control circuit. The indicator light control circuit can then drive the indicator light to output a corresponding light signal (e.g., flashing blue once per second) based on the target control command during the duration of the third mode.

[0139] Once a wearable device enters the third mode, it will remain in this mode even if its wearing status changes from worn to unworn, or if it is stored in its case. Furthermore, if the wearable device is in the third mode and stored in its case, the case can output a corresponding notification signal (such as a light signal) to indicate to the user that the device is in the third mode, or to indicate that the device has exited the third mode.

[0140] As can be seen, in the first scenario, wearable devices support users to input third-party interactive information through various interaction methods such as buttons, touch swipes, and voice commands. This adapts to the operating habits of different users, avoiding reliance on a single method and lowering the barrier to triggering the third mode. Furthermore, wearable devices can use light and sound signals to provide users with a clear indication of the mode they are in, preventing repeated operations or misjudgments. In addition, once a wearable device enters the third mode, it will not exit the third mode even if it changes from a worn state to a non-worn state or is placed in its storage case. This ensures the Bluetooth pairing process remains uninterrupted, and the storage case can even simultaneously output prompts. Even if the user cannot directly observe the wearable device itself, they can still know whether the wearable device is still in the third mode or has exited it, which is beneficial to the user experience.

[0141] In the second scenario, when the wearable device is not being worn and is not stored (e.g., smart glasses are placed on a table and not in a glasses case), the user can trigger the wearable device to enter the third mode by inputting corresponding third interactive information (e.g., long-pressing the button associated with the Bluetooth pairing function on the wearable device, or making a specific swipe on the touch control associated with the Bluetooth pairing function, or inputting a specific voice command to the wearable device).

[0142] Once the wearable device enters the third mode, it can output a prompt signal. For a description of the prompt signal output by the wearable device, please refer to the description of the prompt signal output by the wearable device in the first scenario mentioned above; it will not be repeated here.

[0143] Once a wearable device enters the third mode, it will remain in this mode even if its wearing status changes from unworn to worn, or if it is stored in its case. Furthermore, if the wearable device is in the third mode and stored in its case, the case can output a corresponding notification signal (such as a light signal) to indicate to the user that the device is in the third mode, or to indicate that the device has exited the third mode.

[0144] As can be seen, in the second scenario, wearable devices support users to input third-mode interactive information through various interaction methods such as buttons, touch swipes, and voice commands. This adapts to different users' operating habits, avoiding reliance on a single method and lowering the barrier to triggering the third mode. Furthermore, wearable devices can use light and sound signals to provide users with a clear indication of the mode they are in, preventing repeated operations or misjudgments. In addition, once a wearable device enters the third mode, it will not exit the third mode even if it changes from an unworn state to a worn state or is placed in its storage case. This ensures the Bluetooth pairing process remains uninterrupted, and the storage case can even simultaneously output prompts. Even if the user cannot directly observe the wearable device itself, they can still know whether the wearable device is still in the third mode or has exited it, which is beneficial to the user experience.

[0145] In the third scenario, when the wearable device is not being worn and is stored away (such as smart glasses being placed in a glasses case and not being taken out for use), the user can trigger the wearable device to enter the third mode by inputting the corresponding third interaction information into the wearable device or storage box.

[0146] Specifically, the input of third-party interactive information can be achieved in several ways: for example, by long-pressing the button on the storage box associated with the Bluetooth pairing function; or, if the storage box is equipped with a touch control, a specific sliding operation (such as sliding a circle around the entire screen) can be performed on the touch control; if the storage box and the device support voice linkage, a specific voice command such as "start Bluetooth pairing" can be input to the storage box; or, if the wearable device is connected to the target device (such as a mobile phone), third-party interactive information can be input to the wearable device through operations on the target device, etc.

[0147] After the wearable device enters the third mode, it can output prompt signals synchronously with the storage box, or only the storage box can output prompt signals (such as light signals) to ensure that the user clearly perceives that the wearable device is in the third mode.

[0148] Once a wearable device enters the third mode, it will remain in the third mode even if it changes from a stored state to an unstored state (the user takes the wearable device out of the storage box) or from an unstored state to a worn state (the user wears the wearable device).

[0149] As can be seen, in the third scenario, wearable devices support inputting third-party interactive information in multiple ways, such as long-pressing the storage box button, sliding the storage box, inputting voice commands into the storage box, or even operating through a connected target device (such as a mobile phone). The core advantage is that users can trigger Bluetooth pairing without taking the device out of the storage box. This design is precisely adapted to actual scenarios where wearable devices are inconvenient to take out (such as when the storage box is sealed, the device is stored deep in a backpack or drawer), while covering the operating preferences of different users. It does not rely on a single interaction method and lowers the operating threshold for users to trigger the wearable device to enter the third mode.

[0150] Furthermore, once the wearable device enters the third mode, whether it outputs a prompt signal synchronously with the storage box or outputs a light signal solely through the storage box, it ensures that users can intuitively perceive whether the wearable device is in the third mode through the status of the storage box without directly touching the wearable device. This avoids the problem of not being able to determine the mode due to the wearable device being blocked by the storage box, and reduces the invalid operations of users repeatedly opening the storage box to check or repeatedly triggering interactive information because they are unsure of the mode of the wearable device.

[0151] Furthermore, once a wearable device enters the third mode, it can remain in the third mode even after changing from a stored state to an unstored state (being taken out) and then back to a worn state. This effectively avoids interruptions to the Bluetooth pairing process (third mode) caused by routine operations such as "taking out the device" and "putting on the device," ensuring the continuity of the Bluetooth pairing process and reducing pairing failures caused by process interruptions. Especially for users who need to prepare to wear the device while completing Bluetooth pairing (such as when rushing out the door), this uninterrupted state design further enhances operational convenience and optimizes the user's Bluetooth pairing experience in device storage scenarios.

[0152] Additionally, in some embodiments, the wearable device may output a first signal in response to entering a first mode, and / or output a second signal in response to entering a second mode. The second signal is different from the first signal.

[0153] Specifically, when the wearable device's control module detects that the wearable device meets the conditions for entering the first mode (such as receiving the first interactive information in an unworn state) and completes the mode switch, it can drive the wearable device's signal output components (such as indicators, audio playback modules, etc.) to generate and output the first signal. And / or, when the control module responds to the second interactive information and controls the wearable device to switch from the first mode to the second mode, it can drive the same or different signal output components to generate and output a second signal that is clearly distinguishable from the first signal.

[0154] The core value of this type of signal output lies in providing clear status indications. The first signal promptly informs the user that the device has successfully entered the first mode, eliminating the need for repeated operations to confirm the mode switch. For example, the first signal allows the user to quickly know that the wearable device has entered the management preparation state (first mode), enabling them to input targeted second interaction information and avoid repeated triggering or operational hesitation due to unclear status. The second signal, differing from the first, intuitively indicates that the wearable device has switched from the first mode to the second mode, clearly indicating that it has entered a state where management operations can be performed. This allows the user to understand that management-related operations can now be carried out, effectively distinguishing the device status between the management preparation and management execution phases.

[0155] This design, which distinguishes the mode states of wearable devices through different signals, helps users grasp the working stage of the wearable device in real time, reducing operational errors caused by ambiguity in the wearable device's state (such as mistakenly treating a wearable device that has not entered the first mode as one that has entered the first mode, and inputting a second interactive message into the wearable device, or mistakenly treating a wearable device that has entered the second mode as one that is still in the first mode, and repeatedly inputting the first interactive message into the wearable device). It can significantly improve the certainty and convenience of user operations, and give users a clearer understanding of the goals and boundaries of subsequent operations, which is beneficial to the user experience.

[0156] In some embodiments, both the first signal and the second signal are light signals. The second signal differs from the first signal in at least one of the following: color, flashing frequency, and brightness.

[0157] The output of the first and second signals can depend on the indicators of the wearable device. The indicators of the wearable device can include indicator lights (such as the first or second indicator light described above) and an indicator light control circuit. When the control module determines that the wearable device has entered the first mode, it can send a preset first control command to the indicator light control circuit, which can then drive the indicator light to output the first signal based on the first control command.

[0158] When the control module determines that the wearable device has entered the second mode, it can send a preset second control command to the indicator light control circuit. The indicator light control circuit can then drive the indicator light to output a second signal based on the second control command.

[0159] Specifically, regarding color differentiation, the first signal can use a low-saturation blue light to indicate that the wearable device is in the first management preparation mode. The second signal can use a high-saturation orange light to indicate that the wearable device has entered the second management execution mode. Through intuitive color differentiation, users can quickly understand the current mode stage of the wearable device.

[0160] Regarding the difference in flashing frequency, the first signal can be set to low-frequency flashing (e.g., flashing once every 2 seconds) to indicate that the wearable device is in the first mode of management preparation. The second signal is set to high-frequency flashing (e.g., flashing once every 0.5 seconds) to indicate that the wearable device is entering the second mode of management execution. Even in low-light environments, users can clearly distinguish the mode of the wearable device by the difference in flashing rhythm.

[0161] Regarding brightness differences, the first signal can use a low brightness output (e.g., 30% of maximum brightness) to indicate that the wearable device is in the first management preparation mode. The second signal uses a high brightness output (e.g., 80% of maximum brightness) to indicate that the wearable device is entering the second management execution mode. This avoids mode confusion caused by similar brightness.

[0162] In addition, there can be combinations of multi-dimensional differences. For example, the first signal is "blue, flashing every 2 seconds, 30% brightness", and the second signal is "orange, flashing every 0.5 seconds, 80% brightness". The synergistic differences in color, frequency and brightness further enhance the prompting effect.

[0163] This design, based on the differentiation of light signals, allows users to visually perceive the mode switching results of wearable devices, significantly improving the clarity and accuracy of mode status prompts and benefiting the user experience.

[0164] Furthermore, users can customize the display of light signals when the wearable device is in different modes, allowing the device to fully adapt to individual user needs and actual usage scenarios. For example, users sensitive to specific colors can avoid inappropriate colors (e.g., changing the default orange to red to avoid visual stimulation). Users who frequently use wearable devices at night can reduce the brightness of the second signal light (e.g., from 80% to 40%) to avoid strong light affecting sleep. Users who prefer unique identifiers can set their own flashing frequency combinations (e.g., 3 seconds / time in the first mode and 1.5 seconds / time in the second mode) to quickly identify the wearable device's mode through familiar light frequencies.

[0165] This design, which balances user personalization with the functionality of wearable devices, not only provides users with a user experience that better suits their habits, but also ensures the accuracy of wearable device mode status prompts.

[0166] In some embodiments, both the first signal and the second signal are audio signals. The second signal differs from the first signal in at least one of the following: timbre, sound effect, intensity, or content.

[0167] The output of the first and second signals can depend on the audio playback module of the wearable device. When the control module determines that the wearable device has entered the first mode, it can send a preset third control command to the audio playback module, and the audio playback module can output the first signal based on the third preset command.

[0168] When the control module determines that the wearable device has entered the second mode, it can send a preset fourth control command to the audio playback module, and the audio playback module can output a second signal based on the fourth preset command.

[0169] Specifically, regarding timbre differences, the first signal can use a low-frequency monotone timbre (such as the bass register of a piano) to indicate that the wearable device is in the first management preparation mode. The second signal can use a high-frequency polyphonic timbre (such as the treble register of a violin) to indicate that the wearable device has entered the second management execution mode. Users can quickly distinguish the current mode stage of the wearable device through these different timbre characteristics.

[0170] Regarding the sound effect differences, the first signal can be set to a short, monosyllabic sound (such as a "beep") to indicate that the wearable device is in the first management preparation mode. The second signal is set to a continuous disyllabic sound (such as a "beep beep") to indicate that the wearable device is entering the second management execution mode. Even in noisy environments, users can clearly distinguish the mode of the wearable device through the rhythmic differences in the sound effects.

[0171] Regarding the intensity difference, the first signal can use a low-intensity output (e.g., 30% of maximum volume) to indicate that the wearable device is in the first mode of management preparation. The second signal uses a high-intensity output (e.g., 70% of maximum volume) to indicate that the wearable device is entering the second mode of management execution. This avoids mode confusion caused by similar intensities.

[0172] Regarding content differences, the first signal can use concise voice prompts (such as "Ready") to indicate that the wearable device is in the first management preparation mode. The second signal uses clear operational instructions (such as "Executable Management") to indicate that the wearable device is entering the second management execution mode. These semantic differences further strengthen the mode distinction.

[0173] In addition, there can be combinations of multi-dimensional differences. For example, the first signal is "piano bass tone, single-syllable 'beep' sound, 30% volume", and the second signal is "violin treble tone, two-syllable 'beep beep' sound, 70% volume". The recognition of the prompt is improved by the coordinated differences in tone, sound effect and intensity.

[0174] This design based on the differentiation of sound signals allows users to intuitively perceive the mode switching results of wearable devices through hearing. Especially in scenarios where the wearable device is not in sight (such as when it is stored in a pocket), it can still accurately identify the mode status, significantly improving the applicability and accuracy of wearable device mode status prompts and benefiting the user experience.

[0175] Furthermore, users can customize how the sound signals are displayed when the wearable device is in different modes, allowing the device to fully adapt to individual user needs and actual usage scenarios. For example, users with low hearing sensitivity can increase the intensity of the second signal (e.g., from 70% to 90%) for clearer perception. Users who prefer quiet environments can change the sound effect of the first signal to a softer "dong" sound to reduce abruptness. Users who need clear semantic guidance can customize the voice content (e.g., changing the first signal to "Entering preparatory mode" and the second signal to "Entering management mode") to quickly identify the wearable device's mode status through the content.

[0176] This design, which balances user personalization with the functionality of wearable devices, not only provides users with a user experience that better suits their habits, but also ensures the accuracy of wearable device mode status prompts.

[0177] Additionally, in some embodiments, while the wearable device is in a wearing state, a fourth interactive information input by the user is acquired. This fourth interactive information is input by the user via at least one button, and / or at least one touch control, and / or voice input. Based on this fourth interactive information, the recording function is activated. And / or, while the wearable device is in a wearing state and the recording function is activated, the recording function is deactivated in response to the input fourth interactive information.

[0178] The description of detecting the wearing status of wearable devices can be found in the description in the foregoing embodiments, and will not be repeated here.

[0179] Specifically, when a user inputs fourth interactive information to a wearable device via a button, this can be achieved by performing a specific operation on the button on the wearable device corresponding to the recording function (which can also be referred to as the recording button in this embodiment).

[0180] For example, a user can double-click the record button on a wearable device. Once the record button detects two consecutive presses, it transmits these signals to the control module. The control module then interprets these two presses as a command to switch the recording function's state. That is, if the wearable device's recording function is disabled, the control module, upon recognizing the command to switch the recording function's state, can control the device to switch from disabled to enabled recording.

[0181] Furthermore, with the recording function of the wearable device enabled, the user can double-click the record button on the device again to trigger the control module to recognize the command to switch the recording function status. Since the recording function is enabled, the control module can switch the recording function from enabled to disabled after recognizing the command.

[0182] For example, a user can perform a "press and hold the record button for 2 seconds" operation on the wearable device. After detecting the continuous press signal, the record button can transmit the continuous press signal to the control module. The control module can recognize the continuous press signal as a command to start the recording function and control the wearable device to keep the recording function in the active state.

[0183] Furthermore, with the recording function of the wearable device enabled, the user can perform a "double-tap record button" operation on the wearable device. After detecting two consecutive click signals, the record button can transmit these two consecutive click signals to the control module. The control module can recognize these two consecutive click signals as a command to turn off the recording function and control the wearable device to turn off the recording function.

[0184] When a user inputs fourth interactive information to a wearable device through a touch control, it can be achieved by performing specific operations on the touch control associated with the recording function (which may also be referred to as the recording slider in this embodiment).

[0185] For example, a user can perform a "swipe forward" operation on the recording slider. The touch control circuitry included in the recording slider can convert this "swipe forward" operation into an electrical signal and transmit it to the control module. The control module can then recognize the received electrical signal as a command to switch the recording function state. That is, if the recording function of the wearable device is not enabled, after the control module recognizes the command to switch the recording function state, it can control the recording function of the wearable device to switch from the disabled state to the enabled state.

[0186] Furthermore, with the recording function of the wearable device enabled, the user can again perform a "swipe forward" operation on the recording slider to trigger the control module to recognize the command for switching the recording function status again. Since the recording function of the wearable device is enabled, after recognizing the command for switching the recording function status, the control module can control the recording function of the wearable device to switch from the enabled state to the disabled state.

[0187] For example, a user can perform a "swipe forward" operation on the recording slider. The touch control circuitry included in the recording slider can convert this "swipe forward" operation into an electrical signal and transmit it to the control module. The control module can recognize the received electrical signal as a command to start the recording function and control the recording function of the wearable device to be turned on.

[0188] Furthermore, with the recording function of the wearable device enabled, the user can perform a "swipe backward" operation on the recording slider. The touch control circuitry included in the recording slider converts this "swipe backward" operation into an electrical signal and transmits it to the control module. The control module can recognize the received electrical signal as a command to turn off the recording function and control the recording function of the wearable device to be turned off.

[0189] When a user inputs fourth interactive information into a wearable device via voice, it can do so by issuing a specific voice command to the device's audio acquisition module. For example, a user can issue the voice command "Start recording." After the audio acquisition module detects the voice signal corresponding to this command, it converts the voice signal into an electrical signal and transmits it to the control module. The control module can then recognize the received electrical signal as a command to activate the recording function and control the wearable device to start recording.

[0190] Furthermore, with the recording function of the wearable device enabled, the user can issue a voice command to the audio acquisition module to "stop recording." After detecting the voice signal corresponding to this command, the audio acquisition module converts the voice signal into an electrical signal and transmits it to the control module. The control module can then recognize the received electrical signal as a command to turn off the recording function and control the wearable device to disable the recording function.

[0191] As can be seen, the embodiments of this application take "wearable device being worn" as the premise for responding to the fourth interactive information. Combined with the ability of the wear detection module in the aforementioned embodiments to determine the wearing status of the wearable device, it can effectively avoid the unexpected start and stop of the recording function caused by accidental touch of the recording button or recording slider when the wearable device is not being worn (such as when it is placed on a table or in a storage box), or by environmental noise interfering with the audio acquisition module. This reduces the occupation of the wearable device's storage space and unnecessary energy consumption by invalid recordings, and ensures that the recording function is only triggered when the user is actually using the wearable device, thereby improving the scenario matching degree of wearable device function control.

[0192] Furthermore, it covers three fourth types of interactive information input methods: buttons, touch controls, and voice. Clear operation paths are designed for each method to fully adapt to different users' operating habits. For example, users who prefer the precise feedback of physical buttons can control the recording function of the wearable device by operating the recording button; users who prefer quick touchscreen operations can control the recording function of the wearable device by operating the recording slider; and users who need contactless operation (such as when their hands are busy) can control the recording function of the wearable device by voice commands. This eliminates the need to rely on a single interaction method, lowers the user's operating threshold, and improves the ease of use of the recording function.

[0193] Furthermore, two flexible logics are designed for both buttons and touch controls: "switching states with the same operation" and "different operations controlling start / stop separately," balancing operational simplicity and accuracy. "Switching with the same operation" (such as double-clicking the record button or sliding the record slider forward) eliminates the need for users to remember and distinguish between "on" and "off" operations; switching recording states is achieved simply by repeating the same action, reducing the cost of memorizing operations. "Different operations controlling separately" (such as long-pressing the record button to turn on + double-clicking to turn off, or sliding forward to turn on + sliding backward to turn off) allows the control module to more accurately identify the user's specific intent through differences in operation methods. This avoids ambiguity of a single operation in different scenarios (such as mistakenly interpreting an on operation as a off operation), reduces recording start / stop errors caused by operational confusion, and improves the accuracy of wearable devices in recognizing recording-related commands.

[0194] Furthermore, whether it's the signal transmission from buttons and touch controls (such as the press signal of the record button and the touch electrical signal of the record slider), or the voice signal conversion from the audio acquisition module, the control module's precise recognition and response ensure that the recording function can smoothly start audio acquisition and data storage when "on," and complete the encapsulation and saving of the recording file when "off," guaranteeing the integrity of the recorded content. The explicit "start recording" and "stop recording" commands in the voice interaction further strengthen the correspondence between user intent and function response, allowing users to intuitively control the recording process and comprehensively improving the control reliability and user experience of the wearable device's recording function.

[0195] Additionally, in some embodiments, while the wearable device is in a wearing state, fifth interaction information input by the user is acquired. The fifth interaction information is interaction information input by the user via at least one button, and / or at least one touch control, and / or voice input. Based on the fifth interaction information, the voice interaction function is enabled. And / or, while the wearable device is in a wearing state and the voice interaction function is enabled, the voice interaction function is disabled in response to the input fifth interaction information.

[0196] The description of detecting the wearing status of wearable devices can be found in the description in the foregoing embodiments, and will not be repeated here.

[0197] Specifically, when a user inputs the fifth interactive information to the wearable device via a button, this can be achieved by performing a specific operation on the button on the wearable device corresponding to the voice interaction function (which can also be referred to as the voice interaction button in this embodiment). The voice interaction button may be the same button as the aforementioned recording button, or it may be a different button; this embodiment does not impose any restrictions.

[0198] For example, a user can perform a "click on the voice interaction button" operation on a wearable device. After detecting a single press signal, the voice interaction button can transmit the signal to the control module. The control module can then recognize this press signal as a command to switch the voice interaction function state. That is, if the voice interaction function is not enabled, the control module controls it to switch to the enabled state and plays the interactive voice (e.g., "I am here") through the audio playback module; if the voice interaction function is enabled, the control module controls it to switch to the disabled state, simplifying the user's operation logic.

[0199] For example, a user can perform a "press and hold the voice interaction button for 2 seconds" operation on the wearable device. Upon detecting the continuous press signal, the voice interaction button transmits this signal to the control module. The control module can then interpret this press signal as a command to activate the voice interaction function. If the voice interaction function is not activated, the control module can activate it and play an interactive voice message (e.g., "How can I help you?"). Furthermore, when the voice interaction function is activated, a user can perform a "click on the voice interaction button" operation on the wearable device. The voice interaction button will then transmit the detected click signal to the control module. The control module can then interpret this press signal as a command to deactivate the voice interaction function, thus switching the voice interaction function to an inactive state.

[0200] When a user inputs the fifth interactive information to a wearable device via a touch control, this can be achieved by performing specific operations on the touch control associated with the voice interaction function (also referred to as the voice interaction slider in this embodiment). The voice interaction slider may be the same button as the aforementioned recording slider, or it may be a different button; this embodiment does not impose such limitations.

[0201] For example, a user can perform a "long press for 700ms" operation on the voice interaction slider. The touch control circuitry within the slider detects this 700ms press signal, converts it into a corresponding electrical signal, and transmits it to the control module. Upon receiving this signal, the control module recognizes it as a command to activate the voice interaction function. If the wearable device's voice interaction function is disabled, the control module can switch it from disabled to enabled and drive the audio playback module to play interactive voice messages (such as "Voice interaction is enabled; you can state your needs") to provide clear feedback on the activation status and allow the user to understand that voice interaction is currently available.

[0202] Furthermore, when the voice interaction function of the wearable device is enabled, the user can perform a "double-tap" operation on the voice interaction slider. The touch control circuit of the voice interaction slider will convert the two consecutive click signals into electrical signals and transmit them to the control module. The control module can recognize this as a command to end the voice interaction function. Since the voice interaction function is enabled at this time, the control module will control the function to switch from the enabled state to the disabled state and drive the audio playback module to play a prompt voice (such as "Voice interaction has ended"), simultaneously informing the user that the operation has taken effect.

[0203] For example, a user can perform an "upward swipe" operation on the voice interaction slider. The touch control circuit of the voice interaction slider converts this swipe signal into an electrical signal and transmits it to the control module. The control module recognizes this as a command to switch the state of the voice interaction function. That is, if the voice interaction function is not enabled, the control module controls it to switch to the enabled state and play the interactive voice; if the voice interaction function is already enabled, the control module controls it to switch to the disabled state, achieving bidirectional switching of function states through the same swipe operation.

[0204] When a user inputs fifth interactive information into a wearable device via voice, it can do so by issuing specific voice commands to the device's audio acquisition module. For example, a user can issue the voice command "Hello, xx Communications." After detecting this voice signal, the audio acquisition module converts it into an electrical signal and transmits it to the control module. The control module verifies the validity of the command through voice recognition and recognizes it as a command to activate the voice interaction function. If the voice interaction function is not activated, it controls it to activate and plays interactive voice (such as "Hello"). Furthermore, when the voice interaction function is activated, if the user issues the voice command "Turn off voice interaction" to the audio acquisition module, the audio acquisition module converts the voice signal into an electrical signal and transmits it to the control module. The control module recognizes this as a command to turn off the voice interaction function, thereby controlling the voice interaction function to switch to an inactive state, achieving contactless function start / stop control.

[0205] As can be seen, the embodiments of this application take "wearable device being worn" as the premise for responding to the fifth interactive information. Combined with the ability of the wear detection module in the aforementioned embodiments to determine the wearing status of the wearable device, it can effectively avoid the unexpected start and stop of the voice interaction function caused by accidental touch of the voice interaction button or voice interaction slider when the wearable device is not being worn (such as when it is placed on a table or in a storage box), or by environmental noise interfering with the audio acquisition module. This reduces the ineffective energy consumption caused by accidental activation of the function (such as the voice recognition module running idle or the audio playback module not working properly), and ensures that the voice interaction function is only triggered in the scenario where the user actually uses the device, thereby improving the scenario matching degree of function control.

[0206] Furthermore, it covers three types of fifth interactive information input methods: buttons, touch controls, and voice. It also designs clear operation paths for each method to fully adapt to the operating habits of different users. This eliminates the need for users to rely on a single form of interaction with wearable devices, lowers the operating threshold, and improves the ease of use of voice interaction functions.

[0207] In addition, two flexible logics are designed for buttons and touch controls: "switching states for the same operation" and "controlling start and stop for different operations respectively," which balances operation simplification and accuracy and is beneficial to user experience.

[0208] Furthermore, whether it is the electrical signal of the touch control, the pressing signal of the button, or the voice signal of the audio acquisition module, all are accurately recognized and responded to by the control module. When the device is turned on, interactive voice is played synchronously, and when it is turned off, prompt voice is played. This not only ensures the reliability of starting and stopping the voice interaction function, but also enhances the user's perception of the function status through voice feedback. This allows the user to intuitively control the voice interaction process and improves the user's control experience and reliability of the voice interaction function of the wearable device.

[0209] Additionally, in some embodiments, while the wearable device is in a wearing state, sixth interaction information input by the user is acquired. The sixth interaction information is interaction information input by the user via at least one button, and / or at least one touch control, and / or voice input. Based on the sixth interaction information, the target device is connected. And / or, while the wearable device is in a wearing state and connected to the target device, in response to the input sixth interaction information, the connection to the target device is disconnected.

[0210] For a description of detecting the wearing status of wearable devices, please refer to the description in the foregoing embodiments, which will not be repeated here.

[0211] The target device may include electronic devices with communication functions such as in-vehicle systems, smartphones, tablets, laptops, smartwatches, Bluetooth headsets, and smart speakers. This application embodiment does not limit the specific type of the target device. Users can perform operations on the target device to trigger it to send a connection request to the wearable device.

[0212] For example, the target device (such as an in-vehicle infotainment system) can send a connection request containing the target device's identification information to the wearable device via communication methods such as Bluetooth, Wi-Fi, or Near Field Communication (NFC). Upon receiving the connection request, the wearable device's communication module can transmit it to the control module. The control module will then wait for user input of a sixth interaction message to confirm whether to control the communication module to perform the connection operation.

[0213] After receiving a connection request, the control module can trigger the wearable device to prompt the user for input in response. For example, the control module can trigger the wearable device's indicator light to flash blue once per second to alert the user. Alternatively, the control module can trigger the wearable device's audio playback module to play a prompt tone saying "Received target device connection request, please confirm connection," prompting the user to respond to the connection request.

[0214] Specifically, when a user inputs the sixth interactive information to the wearable device via a button, this can be achieved by performing a specific operation on the button on the wearable device corresponding to the communication connection function (which can also be referred to as the communication button in this embodiment). The communication button can be the same button as the aforementioned recording button and voice interaction button, or it can be a different button; this embodiment does not impose any restrictions.

[0215] For example, after the control module receives a connection request, the user can perform a "click on the communication button" operation on the wearable device. Once the communication button detects a single press signal, it can transmit that signal to the control module. The control module can then recognize this press signal as an instruction to accept the connection request and control the communication module to establish a connection with the target device.

[0216] Alternatively, after receiving a connection request, the user can perform a "double-click communication button" operation on the wearable device. Once the communication button detects two consecutive presses, it transmits the signal to the control module. The control module can then interpret this signal as a command to reject the connection request and control the communication module to refuse to establish a connection with the target device.

[0217] When a user inputs the sixth interactive information to a wearable device via a touch controller, specific operations can be performed through the touch controller (also referred to as the communication slider in this embodiment) on the wearable device corresponding to the communication connection function. The communication slider can be the same slider as the aforementioned recording slider and voice interaction slider, or it can be a different slider; this embodiment does not impose any restrictions.

[0218] For example, after receiving a connection request, the user can perform a "click" operation on the communication slider. The touch control circuitry within the communication slider detects this click signal, converts it into a corresponding electrical signal, and transmits it to the control module. The control module can then interpret this electrical signal as an instruction to accept the connection request and control the communication module to establish a connection with the target device.

[0219] Alternatively, after receiving a connection request, the user can perform a "long press for 1 second" operation on the communication slider. The touch control circuit of the communication slider can convert this long press signal into an electrical signal and transmit it to the control module. The control module can recognize this electrical signal as an instruction to reject the connection request and control the communication module to refuse to establish a connection with the target device.

[0220] When a user inputs the sixth interactive information into a wearable device via voice, it can be achieved by issuing specific voice commands to the audio acquisition module of the wearable device.

[0221] For example, after receiving a connection request, the user can issue a voice command to "agree to connect." The audio acquisition module detects this voice signal, converts it into an electrical signal, and transmits it to the control module. After verifying the validity of the command through voice recognition, the control module can recognize it as an instruction to accept the connection request and control the communication module to establish a connection with the target device.

[0222] Alternatively, after receiving a connection request, the user can issue a "refuse connection" voice command. The audio acquisition module can convert the voice signal into an electrical signal and transmit it to the control module. The control module can recognize it as a command to refuse the connection request and control the communication module to refuse to establish a connection with the target device.

[0223] As can be seen, this application embodiment takes "wearable device being worn" as a prerequisite for responding to the sixth interactive information. Combined with the ability of the wear detection module in the aforementioned embodiment to determine the wearing status of the wearable device, it can effectively avoid unexpected operations caused by accidental touches of communication buttons or communication sliders, or interference from ambient noise with the audio acquisition module, when the wearable device is not being worn (e.g., placed on a table or in a storage box). For example, it avoids accidental touches of communication buttons causing the wearable device to accept connection requests from unfamiliar devices, thereby leading to security risks such as information leakage; it also avoids accidental touches of communication sliders or ambient noise being mistakenly identified as "reject connection" commands, resulting in missed connections with important target devices and interruptions in scenarios such as data synchronization and functional linkage. It ensures that the communication connection function only responds in scenarios where the user is actually using the wearable device and can actively control the operation, improving the scenario matching and security of wearable device function control.

[0224] Furthermore, for the three interaction methods—buttons, touch controls, and voice—clear operational distinction logic was designed to differentiate between "accept connection" and "reject connection." For example, the connection button distinguishes commands by the number of "single" versus "double" clicks. The connection slider distinguishes commands by the operation method of "single" versus "long press for 1 second." Voice input distinguishes commands by the semantic difference between "agree to connect" and "reject connection." This clear operational boundary design allows the control module to accurately identify the user's specific intent without needing to infer user needs through complex logic. This effectively reduces erroneous responses caused by ambiguous operations (such as a single operation corresponding to multiple commands), significantly improving the accuracy of wearable devices in recognizing connection request response commands.

[0225] In addition, the design covering three types of interaction methods fully adapts to the operating habits of different users, reduces the operating threshold for users of wearable devices, and allows users with different needs to respond to connection requests conveniently, thereby improving the ease of use of wearable device communication connection functions.

[0226] Furthermore, whether it's the press signal transmitted by the communication button, the electrical signal converted by the communication slider, or the voice electrical signal transmitted by the audio acquisition module, the control module can accurately analyze and respond to ensure that when "accepting connection," the communication module can stably respond to the target device's request and establish a reliable connection; when "rejecting connection," the communication module can clearly send a rejection instruction to the target device, avoiding interference from connection retries. In addition, after the communication module responds to the target device, the wearable device can also output feedback signals through the audio playback module (such as playing "target device connected" or "connection request rejected" prompt tone) or indicators (such as a solid green indicator light when the connection is successful, and a flashing red indicator light when the connection is rejected), allowing users to intuitively know the connection result between the wearable device and the target device, improving the control reliability of the wearable device's communication connection function and the user experience.

[0227] In addition, in some embodiments, while the wearable device is in use, the user can input more different interactive information to control the wearable device to perform more functions. The functions of the wearable device may include shooting functions (taking photos, live streaming, snapshots, etc.), music playback functions, music switching functions (previous or next track), answering phone calls functions (answering and hanging up), rejecting phone calls, the ability to mute the microphone during a call, volume adjustment functions, forced restart functions, etc.

[0228] The shooting function of the wearable device can be controlled by the user through interactive information input via at least one button, and / or at least one touch control, and / or voice input. The following describes in detail the process of controlling the wearable device to perform the shooting function, using an example of the user inputting interactive information to the wearable device based on a button corresponding to the shooting function (which in this embodiment can also be called a photo button; the photo button can be the same as or different from the buttons provided in the aforementioned embodiments (e.g., the recording button, etc.); this embodiment does not impose any restrictions.

[0229] For example, a user can click the shutter button. After detecting a single press signal, the shutter button can transmit the signal to the control module. The control module can then interpret this single press signal as a command to take a photo and control the wearable device to capture the image.

[0230] For example, a user can press and hold the shutter button for 100ms. Upon detecting this sustained press signal, the shutter button transmits it to the control module. The control module interprets this sustained press signal as a command to start video recording and controls the wearable device to begin recording. During recording, the user can also double-click the shutter button. Upon detecting these two consecutive press signals, the shutter button transmits them to the control module. The control module interprets these two consecutive press signals as a command to stop video recording and controls the wearable device to stop recording.

[0231] For example, a user can press and hold the camera button for 3 seconds. Upon detecting this sustained pressure signal, the camera button transmits it to the control module. The control module interprets this signal as a command to start live streaming and controls the wearable device to activate the real-time video streaming function. During the live stream, the user can press and hold the camera button again for 3 seconds. The camera button detects this sustained pressure signal and transmits it to the control module. The control module interprets this signal as a command to stop the live stream and controls the wearable device to terminate the live stream process.

[0232] For example, a user can tap the shutter button three times consecutively. Upon detecting these three presses, the shutter button transmits them to the control module. The control module interprets these three presses as a command to take a snapshot, controls the wearable device to capture the current scene to generate a snapshot, and can process the snapshot in real time.

[0233] Among them, snapshots refer to short-term still photos taken quickly by wearable devices. They are usually used in scenarios such as real-time image recognition (such as recognizing objects, text, QR codes, etc.) and instant information recording. Their shooting response speed is faster than regular photos, and the image file size is smaller.

[0234] It is evident that by designing a logic where "different interactive operations correspond to different sub-functions" for the shooting function of wearable devices, the control module can accurately identify the specific function the user wants to perform (taking a photo, starting / stopping video recording, starting / stopping live streaming, taking a snapshot) based on differences in user operations (such as single trigger, short-term continuous trigger, multiple consecutive triggers, and long-term continuous trigger). This avoids the functional confusion caused by a single operation corresponding to multiple commands, and expands the diverse sub-scenarios under the broad category of shooting functions (regular photo taking, video recording, live streaming, and quick image recognition snapshots). Furthermore, users do not need to rely on complex operations; they can control the wearable device to achieve different shooting functions simply through differences in operation, effectively improving the accuracy and ease of use of wearable device function control, and benefiting the user experience.

[0235] Music-related functions (music playback, music switching, etc.) of wearable devices can be controlled by interactive information input from the user via at least one button, and / or at least one touch control, and / or voice input. The following describes in detail the process of controlling a wearable device to implement music-related functions, using an interactive information input by the user to a touch control associated with the music function (also referred to as a music slider in this embodiment; the music slider can be the same as or different from the touch controls provided in the foregoing embodiments (e.g., recording slider, etc.), without limitation in this embodiment).

[0236] For example, a user can tap the music slider once. The touch control circuitry within the music slider detects this tap signal, converts it into a corresponding electrical signal, and transmits it to the control module. The control module can then interpret this electrical signal as a command to play music and control the wearable device to start playing music (e.g., play the default music; or play the music that was playing when playback was last paused). While the wearable device is playing music, the user can tap the music slider again. The touch control circuitry of the music slider converts this tap signal into an electrical signal and transmits it to the control module. The control module can then interpret this tap signal as a command to pause music playback and control the wearable device to pause music playback.

[0237] For example, while the wearable device is playing music, the user can tap the music slider three times. The touch control circuit of the music slider detects these three consecutive taps, converts them into corresponding electrical signals, and transmits them to the control module. The control module can then interpret these electrical signals as a command to switch to the previous track and control the wearable device to switch to the previous track. The user can also tap the music slider twice. The touch control circuit of the music slider converts these two consecutive taps into electrical signals and transmits them to the control module. The control module can then interpret these electrical signals as a command to switch to the next track and control the wearable device to switch to the next track.

[0238] It is evident that by designing a logic where "different interactive operations correspond to different sub-functions" for the music-related functions of wearable devices, the control module can accurately identify the specific function the user wants to perform (play music, pause music, switch to the previous track, switch to the next track) based on the differences in user operations (such as single tap, double single tap, triple tap, double tap). This avoids the functional confusion caused by a single operation corresponding to multiple commands, while also covering the core scenarios of playback control and music switching within the broader category of music functions. Furthermore, users do not need to rely on complex operations; they can control the wearable device to achieve different music-related functions simply through differences in operation, effectively improving the accuracy and ease of use of wearable device function control, thus benefiting the user experience.

[0239] The phone-related functions of wearable devices (answering calls, rejecting calls, and muting the microphone during calls) can be controlled based on interactive information input by the user through at least one button, and / or at least one touch control, and / or voice input. The following describes in detail the process of controlling a wearable device to implement phone-related functions, using an example of a user inputting interactive information based on a touch control associated with the phone function (also referred to as a phone slider in this embodiment; the phone slider can be the same as or different from the touch controls provided in the foregoing embodiments, and this embodiment does not impose such limitations).

[0240] For example, when a call comes in, the user can tap the phone slider once. The touch control circuitry within the slider detects this single tap signal, converts it into a corresponding electrical signal, and transmits it to the control module. Upon receiving this signal, the control module interprets it as an instruction to answer the call and controls the wearable device to establish a call connection with the caller, putting the wearable device into call mode. If the user needs to end the call while the wearable device is in call mode, they can tap the phone slider twice. The touch control circuitry detects these two consecutive taps, converts them into electrical signals, and transmits them to the control module. The control module interprets these signals as an instruction to hang up the call and controls the wearable device to terminate the current call connection, exiting call mode.

[0241] For example, when a call comes in and the user is unable to answer, they can perform a "long press for 700ms" operation on the phone slider. The touch control circuit of the phone slider detects the press signal of this duration, converts it into an electrical signal, and transmits it to the control module. The control module can then recognize this electrical signal as a command to reject the call and control the wearable device to reject the incoming call.

[0242] For example, during a call on a wearable device, if the user needs to temporarily prevent the other party from hearing their voice (e.g., in a noisy environment), they can tap the phone slider once. The slider's touch control circuit detects this tap signal and converts it into an electrical signal, which is then transmitted to the control module. The control module interprets this signal as a command to mute the microphone and stops the wearable device from collecting audio signals from the current environment. In this situation, the other party cannot hear the wearable device until the user performs a specific action (such as tapping the phone slider again) to restore microphone functionality.

[0243] It is evident that by designing a logic where "different interactive operations correspond to different sub-functions" for the phone-related functions of wearable devices, the control module can accurately identify the specific function the user wants to perform (answer a call, hang up a call, reject a call, or mute the microphone during a call) based on differences in user operations (such as a single tap, two consecutive taps, or a 700ms long press). This avoids the confusion caused by a single operation corresponding to multiple commands (e.g., not misinterpreting "long press on the phone slider" as "answer a call"), while also covering core scenarios such as call start / stop, call rejection, and temporary mute within the broader category of phone functions. Furthermore, users do not need to remember complex operation steps; they can control the wearable device to achieve different phone-related functions simply by varying the number of taps or the duration of taps. This effectively improves the accuracy and ease of use of the wearable device's phone function control, thus enhancing the user experience.

[0244] The volume adjustment function of a wearable device can be controlled by the user through interactive information input via at least one button, and / or at least one touch control, and / or voice input (wherein, the volume adjustment function of the wearable device cannot be implemented based on voice input in a call scenario). The following describes in detail the process of controlling the volume adjustment function of a wearable device by inputting interactive information based on a touch control associated with the volume adjustment function (which may also be referred to as a volume adjustment slider in this embodiment; the volume adjustment slider may be the same as or different from the touch controls provided in the aforementioned embodiments, and this embodiment does not impose any restrictions).

[0245] For example, when playing audio on a wearable device, a user can slide a volume control slider. To increase the volume, the user slides forward on the slider. The touch control circuitry within the slider detects this forward slide signal, converts it into a corresponding electrical signal, and transmits it to the control module. The control module interprets this electrical signal as a command to increase the volume and controls the wearable device to raise the current audio output volume. Conversely, to decrease the volume, the user slides backward on the slider. The touch control circuitry detects this backward slide signal, converts it into an electrical signal, and transmits it to the control module. The control module interprets this electrical signal as a command to decrease the volume and controls the audio playback module to lower the current audio output volume.

[0246] It is evident that by designing a logic where "different interactive operations correspond to different sub-functions" for the volume adjustment function of wearable devices, the control module can accurately identify the specific function (increase volume, decrease volume) that the user wants to perform based on the differences in user operations (such as sliding forward or backward on the music slider). This avoids the functional confusion caused by a single operation corresponding to multiple commands, and also covers diverse sub-scenarios for increasing and decreasing volume under the broad category of volume adjustment, adapting to different usage needs. Furthermore, users do not need to rely on complex operations; they can control the wearable device to achieve different volume adjustment functions simply through differences in operation, effectively improving the accuracy and ease of use of wearable device function control, and benefiting the user experience.

[0247] The forced restart function of a wearable device can be controlled based on interactive information input by the user through at least one button and / or at least one touch control. The following describes in detail the process of controlling the wearable device to implement the forced restart function, using an example of the user inputting interactive information based on a button corresponding to the forced restart function (which in this embodiment can also be called a restart button; the restart button can be the same as the buttons provided in the aforementioned embodiments (e.g., the camera button, volume control button, etc.), or it can be different from the buttons provided in the aforementioned embodiments; this embodiment does not impose any restrictions).

[0248] For example, when a wearable device experiences abnormal states such as lag, unresponsiveness, or a black screen, the user can press and hold the restart button for 10 seconds. Once the restart button detects this duration of pressure, it transmits the signal to the control module. Upon receiving this pressure signal, the control module uses preset verification logic to confirm that the duration meets the forced restart trigger conditions (excluding accidental short presses). It then identifies this as a command to execute a forced restart and controls the wearable device to begin the forced restart process.

[0249] During the forced restart process of a wearable device, the control module can terminate all currently running processes, reinitialize the hardware and system software, and complete the device restart. Furthermore, the control module can control the wearable device's indicator light to remain constantly red until the device is completely powered off, providing a clear indication to the user that a forced restart is in progress. Additionally, if the wearable device was in a data processing state before the forced restart (e.g., unsaved video recording, incomplete file transfer), the control module can trigger a temporary data cleanup mechanism to delete incomplete temporary data, preventing invalid data from consuming storage space.

[0250] As can be seen, by designing the forced restart function of wearable devices with the logic of "multiple interactive operations corresponding to the same function," the control module can accurately identify the forced restart function that the user wants to execute based on the differences in user operations (such as long-pressing a button for a specific duration or long-pressing a corresponding touch control), effectively avoiding confusion with operations of other functions (such as starting a live broadcast or answering a phone call). Furthermore, users do not need to rely on a single or complex operation; they can control the wearable device to force restart through multiple simple interactive operations (such as long-time triggering of different components), effectively improving the flexibility, efficiency, and ease of use of the forced restart function control, thus benefiting the user experience.

[0251] Figure 4 This is a schematic diagram of the structure of a control device for a wearable device provided in an embodiment of this application. Figure 4 As shown in the illustration, the control device for a wearable device provided in this application includes a controller and a memory. The controller and memory are coupled. The memory stores computer instructions, which are loaded and executed by the controller to enable the device to implement the aforementioned control method for the wearable device.

[0252] Figure 5 This is a schematic diagram illustrating one possible presentation form of the wearable device provided in an embodiment of this application. For example... Figure 5 As shown, the wearable device provided in this application embodiment can be smart glasses 500. The smart glasses 500 may include a frame 501 and temples 502; the left and right temples of the temples 502 are respectively hinged to both ends of the frame 501. The frame 501 includes a bridge portion 501A. The temples 502 include a bent portion 502A.

[0253] The smart glasses 500 includes a first indicator light 503, a second indicator light 504, a light sensing module 505, a charging port 506, an image acquisition module 507, and an audio acquisition module, including a first microphone 508 disposed on the frame 501.

[0254] The side of the temple 502 relative to the frame 501 can be called the rear side of the smart glasses 500, and the side opposite to the rear side of the frame 501 can be called the front side of the smart glasses 500.

[0255] The first indicator light 503 can be located on the front side of the frame 501, for example, in the upper right corner of the front side of the frame 501.

[0256] The light sensing module 505 can also be located on the front side of the lens frame 501, for example, in the upper right corner of the front side of the lens frame 501, adjacent to the first indicator light 503.

[0257] The second indicator light 504 can be located on the rear side of the frame 501, for example, in the upper right corner of the rear side of the frame 501.

[0258] The image acquisition module 507 can also be located on the front side of the frame 501, for example, in the upper left corner of the front side of the frame 501.

[0259] The first microphone 508 can be located below the bridge of the nose 501A, and the pickup hole of the first microphone 508 faces downwards from the bridge of the nose 501A.

[0260] The charging port 506 can also be located below the bridge of the nose 501A, adjacent to the first microphone 508.

[0261] The audio acquisition module of the smart glasses 500 includes at least one second microphone, which can be distributed on the temple 502. For example, microphones 509 and 510 of the at least one second microphone are disposed on the left temple of the temple 502, and microphone 511 is disposed on the right temple of the temple 502. The pickup hole of microphone 509 can be positioned facing outward of the left temple; the pickup hole of microphone 511 can be positioned facing outward of the right temple; and the pickup hole of microphone 510 can be positioned facing the ground, etc.

[0262] Both the button 512 and the touch control 513 of the smart glasses 500 can be located on the temple 502. For example, the button 512 is located on the upper surface of the right temple, and the touch control 513 is located on the surface of the right temple away from the left temple.

[0263] The audio playback module of the smart glasses 500 includes speakers that can be distributed and arranged on the temples 502. For example, the first speaker 514 can be located on the right temple, and the second speaker 515 can be located on the left temple. Each speaker can include a sound leakage control and a sound outlet; taking the first speaker 514 as an example, the sound leakage outlet of the first speaker 514 can be located on the upper surface of the right temple, and the sound outlet of the first speaker 514 can be located on the lower surface of the right temple.

[0264] The power source for the smart glasses 500 may include multiple batteries, which may be distributed on the temples 502. For example, the smart glasses 500 may include a first battery 516 and a second battery 517 connected in parallel; the first battery 516 may be located at the end of the left temple closer to the frame 501, and the second battery 517 may be located at the end of the left temple away from the frame 501; and / or, the smart glasses 500 may also include a third battery 518; wherein the third battery 518 may be located at the end of the right temple away from the frame 501, etc.

[0265] The wear detection module 519 of the smart glasses 500 can also be located on the temple 502. For example, the wear detection module 519 can be located below the bend 502A of the right temple.

[0266] The control module, image processing module, communication module, transmission channel switching module, clock module, dual-channel intelligent power amplifier, front-end module, duplexer, embedded multimedia storage card, internal memory, first power supply module, second power supply module, power conversion module, third power supply module, charging management chip, first clock unit, second clock unit, third clock unit, inertial detection module, and indicator light control circuit of the smart glasses 500 can all be distributed on the temple 502, or distributed on the frame 501, or partially on the frame 501 and partially on the temple 502. This application embodiment does not limit the specific placement of the control module, image processing module, communication module, transmission channel switching module, clock module, dual-channel intelligent power amplifier, front-end module, duplexer, embedded multimedia storage card, internal memory, first power supply module, second power supply module, power conversion module, third power supply module, charging management chip, first clock unit, second clock unit, third clock unit, inertial detection module, and indicator light control circuit of the smart glasses 500.

[0267] In some solutions, multiple embodiments of this application can be combined, and the combined solution can be implemented. Optionally, some operations in the processes of each method embodiment may be combined, and / or the order of some operations may be changed. Furthermore, the execution order between the steps of each process is merely exemplary and does not constitute a limitation on the execution order between steps; other execution orders are also possible. It is not intended to indicate that the execution order is the only possible order in which these operations can be performed. Those skilled in the art will conceive of various ways to reorder the operations described herein. In addition, it should be noted that the process details involved in one embodiment of this document are similarly applicable to other embodiments, or different embodiments may be combined.

[0268] Furthermore, some steps in the method embodiments can be equivalently replaced with other possible steps. Alternatively, some steps in the method embodiments may be optional and can be deleted in certain use cases. Or, other possible steps may be added to the method embodiments. Moreover, the various method embodiments can be implemented individually or in combination.

[0269] Through the above description of the embodiments, those skilled in the art can clearly understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0270] In the several embodiments provided in this application, it should be understood that the disclosed methods, wearable devices, and apparatuses can be implemented in other ways. For example, the wearable device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another module, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual couplings, direct couplings, or communication connections may be through some interfaces; indirect couplings or communication connections between modules or units may be electrical, mechanical, or other forms.

[0271] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0272] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, in essence, or the part that contributes, or all or part of the technical solution, can be embodied in the form of a software product. This software product is stored in a storage medium and includes several instructions to cause a device (which may be a microcontroller, chip, etc.) or processor to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0273] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A control method for a wearable device, characterized in that, include: When the wearable device is not worn, it enters the first mode based on the first interaction information; During the duration of the first mode, in response to the second interactive information input by the user, the system enters the second mode; The second mode is different from the first mode; The second mode is the mode for managing the wearable device.

2. The method according to claim 1, characterized in that, The method further includes: If the second interaction information is not received within the target duration after entering the first mode, exit the first mode.

3. The method according to claim 1 or 2, characterized in that, The method further includes: If the first target information is detected when the first mode is entered, the first mode is exited; the first target information includes at least one of wearing information, Bluetooth pairing information, and storage information; and / or, When entering the second mode, if second target information is detected, the second mode is maintained until the management of the wearable device is completed; the second target information includes at least one of wearing information, Bluetooth pairing information, and storage information.

4. The method according to claim 1, characterized in that, The first mode includes a mode for performing Bluetooth pairing tasks.

5. The method according to claim 4, characterized in that, The method further includes: In response to a third interactive message input by the user, a third mode is entered; the third mode includes a mode for performing Bluetooth pairing tasks; the third interactive message is different from the first interactive message.

6. The method according to any one of claims 1-5, characterized in that, The method further includes; In response to entering the first mode, a first signal is output; and / or, In response to entering the second mode, a second signal is output; the second signal is different from the first signal.

7. The method according to claim 6, characterized in that, Both the first signal and the second signal are light signals; the second signal differs from the first signal in that at least one of the following is different: color, flashing frequency, and brightness.

8. The method according to claim 6, characterized in that, Both the first signal and the second signal are sound signals; the second signal differs from the first signal in at least one of the following: timbre, sound effect, intensity, and content.

9. The method according to any one of claims 1-8, characterized in that, The method further includes: When the wearable device is in the wearing state, the fourth interactive information input by the user is acquired; the fourth interactive information is the interactive information input by the user through at least one button, and / or, at least one touch control, and / or, voice input. Based on the aforementioned fourth interactive information, control the recording function to be activated; and / or, When the wearable device is in the wearing state and the recording function is in the on state, the recording function is turned off in response to the input of the fourth interactive information.

10. The method according to any one of claims 1-9, characterized in that, The method further includes: When the wearable device is in the wearing state, the fifth interactive information input by the user is acquired; the fifth interactive information is the interactive information input by the user through at least one button, and / or, at least one touch control, and / or, voice input. Based on the fifth interactive information, control the voice interaction function to be activated; and / or, When the wearable device is in the wearing state and the voice interaction function is in the enabled state, the voice interaction function is turned off in response to the input of the fifth interaction information.

11. The method according to any one of claims 1-10, characterized in that, The method further includes: When the wearable device is in the wearing state, the sixth interactive information input by the user is acquired; the sixth interactive information is the interactive information input by the user through at least one button, and / or, at least one touch control, and / or, voice input. Based on the sixth interactive information, connect to the target device; and / or, When the wearable device is in a wearing state and connected to the target device, In response to the input of the sixth interactive information, the connection with the target device is disconnected.

12. A control device for a wearable device, characterized in that, The control device of the wearable device includes a controller and a memory; the controller and the memory are coupled; the memory is used to store computer instructions; the computer instructions are loaded and executed by the controller to enable the control device of the wearable device to implement the control method of the wearable device as described in any one of claims 1-11.

13. A wearable device, characterized in that, The wearable device is configured to operate under the control of the wearable device control method as described in any one of claims 1-11.

Images