Data transmission method, electronic device, and system

Abstract

The present application provides a data transmission method, an electronic device, and a system. The method comprises: a second electronic device determining at least one user identifier, and sending the at least one user identifier to a first electronic device; in response to starting a first application, the first electronic device sending fifth information to indicate that the first electronic device is in a connectable state; the first electronic device receiving a user identifier of a third electronic device; and upon determining that the user identifier of the third electronic device belongs to the at least one user identifier, the first electronic device connecting to the third electronic device and transmitting data to the third electronic device. The data transmission method, the electronic device, and the system of the present application can improve the switching efficiency of a wearable device between electronic devices, and ensure the security and integrity of user data.

Description

Data transmission method, electronic device and system

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on March 18, 2024, with application number 202410322864.9, and invention name “Method, electronic device and system for transmitting data”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of electronic devices, and more specifically, to a method, electronic device, and system for transmitting data. Background Art

[0003] With the advancement and development of technology, electronic devices can provide a variety of rich user experiences. In addition to mobile phones, tablets, car computers, and smart screens, electronic devices used by users also include portable wearable devices such as smartwatches and glasses. Most wearable devices can be paired with mobile phones via Bluetooth technology. Users can view data captured by the wearable devices on their mobile phones, such as the user's heart rate and blood pressure recorded by a smartwatch. Users can also view message notifications and make mobile payments through wearable devices. Wearable devices provide convenience for users' daily lives.

[0004] Currently, wearable devices can only be connected to one electronic device at a time, and can switch between different devices with the same user account (or device account). Switching a wearable device between electronic devices with different user accounts requires complex user operations and may result in data loss during the switching process, causing inconvenience to the user.

[0005] Therefore, how to improve the efficiency of switching between electronic devices and ensure the security and integrity of user data is an urgent problem to be solved. Summary of the Invention

[0006] The present application provides a method, electronic device, and system for transmitting data, which can improve the efficiency of switching between wearable devices and electronic devices, and ensure the security and integrity of user data.

[0007] In a first aspect, a method for transmitting data is provided, which is applied to a first electronic device, which is connected to a second electronic device, and the method includes: receiving first information from a third electronic device, the first information including a user identifier of the third electronic device; determining whether the user identifier of the third electronic device belongs to at least one user identifier, the at least one user identifier corresponds to at least one electronic device, and the at least one electronic device is an electronic device trusted by the first electronic device.

[0008] It can be understood that the third electronic device is a peripheral device of the first electronic device, and the third electronic device can send the user identification of the third electronic device to the first electronic device so that the first electronic device can determine whether the user identification of the third electronic device belongs to at least one user identification, that is, so that the first electronic device can determine whether the third electronic device is a user trusted by the first electronic device.

[0009] For example, the user account of the third electronic device may be different from the user account of the first electronic device. Electronic devices with different user accounts may be mutually trusted electronic devices.

[0010] For example, the first electronic device can be a wearable device, the second electronic device can be a mobile phone terminal, tablet computer, personal computer, etc., and the third electronic device can also be a mobile phone terminal, tablet computer, personal computer, etc. The scenario in which the first electronic device and the second electronic device are connected can be a 2C scenario. The 2C scenario can be understood as the user's daily life scenario. The first electronic device can obtain the user's daily life data and transmit the data to the second electronic device; at the same time, the second electronic device can synchronize messages with the first electronic device.

[0011] It is understood that if a first electronic device carries an application and a second electronic device also carries the application, the first and second electronic devices can connect and transmit data through the application. The user account for the application carried by the first electronic device can be the same as the user account for the application carried by the second electronic device. In other words, the user account of the first electronic device can be the same as the user account of the second electronic device. The user identifier corresponds to the user account and the electronic device.

[0012] Based on the above solution, the first electronic device can receive the user identification from the surrounding device and determine whether the electronic device is trusted by the first electronic device by determining the user identification of the electronic device. In other words, the first electronic device can be connected to the third electronic device using the user identification of the third electronic device, thereby simplifying the process of switching the connection between electronic devices with different user accounts and saving power.

[0013] In combination with the first aspect, in certain implementations of the first aspect, the method also includes: when the user identifier of the third electronic device belongs to the at least one user identifier, sending second information to the third electronic device, the second information being used to request a connection with the third electronic device; receiving third information from the third electronic device to disconnect from the second electronic device and to establish a connection with the third electronic device, wherein the third information is feedback information of the second information.

[0014] It should be noted that when the first electronic device determines that the user identifier of the third electronic device belongs to at least one user identifier, it determines that the third electronic device is a trustworthy electronic device. Therefore, during the connection process between the first electronic device and the third electronic device, no mutual security authentication is required. Among them, the first electronic device can send information (second information) for requesting a connection to the third electronic device, and when positive feedback information (third information) is received from the third electronic device, the connection between the first electronic device and the third electronic device is realized. This connection process does not require security authentication, reduces the delay of the connection process, and saves power consumption.

[0015] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending first data to the third electronic device, where the first data is data obtained by the first electronic device through the first application of the first electronic device.

[0016] Exemplarily, the first application may be an application for pairing and connection, or an application for transmitting data.

[0017] In a possible case, although the user account of the third electronic device is different from the user account of the first electronic device, the third electronic device may be pre-configured as an electronic device trusted by the first electronic device.

[0018] Based on the above solution, when the first electronic device is connected to the third electronic device, data can be transmitted between the first electronic device and the third electronic device, wherein the transmitted data can be data acquired by the first application hosted on the first electronic device.

[0019] In combination with the first aspect, in some implementations of the first aspect, the method further includes: sending second data to the third electronic device, where the second data is data exchanged between the first electronic device and the second electronic device.

[0020] Optionally, the second data may be data related to the second electronic device, including data of interaction between the second electronic device and the first electronic device, and device data of the second electronic device (eg, device identification).

[0021] It should be noted that before the first electronic device is connected to the third electronic device, the first electronic device is connected to the second electronic device. The second data can be understood as data exchanged between the first and second electronic devices, such as heart rate, blood pressure, etc. When the first electronic device disconnects from the second electronic device and establishes a connection with the third electronic device, the first electronic device does not need to be initialized, that is, it does not need to delete the data exchanged with the second electronic device, nor does it need to log out of the original logged-in user account. This ensures the integrity of user data.

[0022] In combination with the first aspect, in certain implementations of the first aspect, before receiving the first information from the third electronic device, the method also includes: receiving fourth information from the second electronic device, the fourth information including the at least one user identifier; and sending fifth information in response to starting the first application, the fifth information being used to indicate that the first electronic device is in a connectable state.

[0023] Exemplarily, the fourth information may include a trusted user list.

[0024] Based on the above scheme, the first electronic device can obtain at least one user identifier to determine the electronic device or user that the first electronic device can trust. When the first electronic device starts the first application, it can broadcast a Bluetooth message to indicate that the first electronic device can be connected, and the first electronic device can try to connect to other electronic devices. In other words, the electronic devices or users trusted by the first electronic device are pre-set, so that when the first electronic device is paired and connected with other electronic devices, if the other electronic devices are trusted by the first electronic device, there is no need for a security authentication process, nor is there a need to initialize the user data stored on the first electronic device, thereby improving the switching efficiency of wearable devices while ensuring the security and integrity of data transmission.

[0025] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving sixth information from the second electronic device, where the sixth information is used to update the at least one user identifier.

[0026] Based on the above scheme, at least one user identifier can be updated. When the first electronic device is connected to the second electronic device, at least one user identifier can be updated through the user's operation on the second electronic device, and the first electronic device can update at least one user identifier based on information from the third electronic device.

[0027] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving seventh information from the third electronic device, where the seventh information is used to update the at least one user identifier.

[0028] Based on the above solution, at least one user identifier can be updated. When the first electronic device is connected to the third electronic device, at least one user identifier can be updated through user operations on the third electronic device, and the first electronic device can update the at least one user identifier based on information from the third electronic device.

[0029] In combination with the first aspect, in some implementations of the first aspect, the third electronic device includes the first application.

[0030] That is, the first electronic device and the third electronic device can be paired and connected through the first application, and after the first electronic device and the third electronic device are connected, data can be transmitted to the third electronic device through the first application.

[0031] In combination with the first aspect, in some implementations of the first aspect, the user identifier of the second electronic device is different from the user identifier of the third electronic device.

[0032] That is, the first electronic device can be switched between two electronic devices with different user identities, and the first electronic device can be switched between two electronic devices with different user accounts.

[0033] In a second aspect, a method for transmitting data is provided, which is applied to a second electronic device, which is connected to a first electronic device, and the method includes: determining at least one user identifier, which corresponds to at least one electronic device, and the at least one electronic device is an electronic device trusted by the first electronic device; sending fourth information to the first electronic device, which includes the at least one user identifier.

[0034] Based on the above solution, at least one user identifier may be configured on the second electronic device, and the configured at least one user identifier may be sent to the first electronic device so that the first electronic device can subsequently switch the connection.

[0035] In combination with the second aspect, in some implementations of the second aspect, determining at least one user identifier includes: determining the at least one user identifier in response to an operation on the at least one user identifier.

[0036] Based on the above solution, at least one user identification may be configured by a user's operation on the second electronic device, for example, the user inputs the user identification.

[0037] In combination with the second aspect, in some implementations of the second aspect, the method further includes: in response to the operation of updating the at least one user identifier, sending sixth information to the first electronic device, where the sixth information is used to update the at least one user identifier.

[0038] Based on the above solution, when the second electronic device is connected to the first electronic device, the at least one user identifier can be updated by the user updating (including deleting and adding) the user identifier on the second electronic device.

[0039] In a third aspect, a method for transmitting data is provided, which is applied to a third electronic device, and the method includes: receiving fifth information from a first electronic device, where the fifth information is used to indicate that the first electronic device is in a connectable state; and sending first information to the first electronic device, where the first information includes a user identifier of the third electronic device.

[0040] Based on the above solution, the third electronic device may send the user identification of the third electronic device to the first electronic device, so that the first electronic device can determine whether the third electronic device is trustworthy.

[0041] In combination with the third aspect, in certain implementations of the third aspect, the method also includes: when the user identifier of the third electronic device belongs to at least one user identifier, receiving second information from the first electronic device, the second information is used to request the third electronic device to connect to the first electronic device, the at least one user identifier corresponds to at least one electronic device, and the at least one electronic device is an electronic device trusted by the first electronic device; sending third information to the first electronic device to disconnect the first electronic device from the second electronic device and to establish a connection with the first electronic device, the second electronic device is an electronic device trusted by the first electronic device.

[0042] It should be noted that when the user identifier of the third electronic device belongs to at least one user identifier, it means that the third electronic device is an electronic device trusted by the first electronic device. Therefore, in the process of connecting the first electronic device and the third electronic device, no mutual security authentication is required. The third electronic device can connect the third electronic device to the first electronic device by receiving information (second information) sent from the first electronic device for requesting a connection and sending positive feedback information (third information) to the first electronic device. This connection process does not require security authentication, reduces the delay of the connection process, and saves power consumption.

[0043] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: receiving first data from the first electronic device, where the first data is data obtained by the first electronic device through a first application of the first electronic device.

[0044] Based on the above solution, when the first electronic device is connected to the third electronic device, data can be transmitted between the first electronic device and the third electronic device, wherein the transmitted data can be data acquired by the first application hosted on the first electronic device.

[0045] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: receiving second data from the first electronic device, the second data being data generated by interaction between the first electronic device and a second electronic device, and the second electronic device being an electronic device trusted by the first electronic device.

[0046] Optionally, the second data may be data related to the second electronic device, including data of interaction between the second electronic device and the first electronic device, and device data of the second electronic device (eg, device identification).

[0047] It should be noted that before the first electronic device is connected to the third electronic device, the first electronic device is connected to the second electronic device. The second data can be understood as data exchanged between the first and second electronic devices, such as heart rate, blood pressure, etc. When the first electronic device disconnects from the second electronic device and establishes a connection with the third electronic device, the first electronic device does not need to be initialized, that is, it does not need to delete the data exchanged with the second electronic device, nor does it need to log out of the original logged-in user account. This ensures the integrity of user data.

[0048] In combination with the third aspect, in certain implementations of the third aspect, the method further includes: in response to the operation of updating the at least one user identifier, sending seventh information to the first electronic device, where the seventh information is used to update the at least one user identifier.

[0049] Based on the above solution, when the first electronic device is connected to the third electronic device, at least one user identification can be updated through the user's operation on the third electronic device.

[0050] In combination with the third aspect, in some implementations of the third aspect, the third electronic device includes the first application.

[0051] In a fourth aspect, a device for transmitting data is provided, which is connected to a second electronic device and includes: a transceiver unit for receiving first information from a third electronic device, wherein the first information includes a user identifier of the third electronic device; and a processing unit for determining whether the user identifier of the third electronic device belongs to at least one user identifier, wherein the at least one user identifier corresponds to at least one electronic device, and the at least one electronic device is an electronic device trusted by the device.

[0052] In combination with the fourth aspect, in certain implementations of the fourth aspect, the transceiver unit is further used to send second information to the third electronic device when the user identifier of the third electronic device belongs to the at least one user identifier, and the second information is used to request a connection with the third electronic device; the transceiver unit is also used to receive third information from the third electronic device so as to disconnect from the second electronic device and establish a connection with the third electronic device, wherein the third information is feedback information of the second information.

[0053] In combination with the fourth aspect, in certain implementations of the fourth aspect, the transceiver unit is further used to send first data to the third electronic device, where the first data is data obtained by the device through the first application of the device.

[0054] In combination with the fourth aspect, in certain implementations of the fourth aspect, the transceiver unit is further configured to send second data to the third electronic device, where the second data is data exchanged between the apparatus and the second electronic device.

[0055] In combination with the fourth aspect, in certain implementations of the fourth aspect, the transceiver unit is further used to receive fourth information from the second electronic device, where the fourth information includes the at least one user identifier; the transceiver unit is further used to send fifth information in response to starting the first application, where the fifth information is used to indicate that the device is in a connectable state.

[0056] In combination with the fourth aspect, in some implementations of the fourth aspect, the transceiver unit is further used to receive sixth information from the second electronic device, and the sixth information is used to update the at least one user identifier.

[0057] In combination with the fourth aspect, in certain implementations of the fourth aspect, the transceiver unit is further used to receive seventh information from the third electronic device, and the seventh information is used to update the at least one user identifier.

[0058] In combination with the fourth aspect, in some implementations of the fourth aspect, the third electronic device includes the first application.

[0059] In combination with the fourth aspect, in certain implementations of the fourth aspect, the user identifier of the second electronic device is different from the user identifier of the third electronic device.

[0060] In a fifth aspect, a device for transmitting data is provided, which is connected to a first electronic device and includes: a processing unit for determining at least one user identifier, the at least one user identifier corresponding to at least one electronic device, and the at least one electronic device being an electronic device trusted by the first electronic device; a transceiver unit for sending fourth information to the first electronic device, the fourth information including the at least one user identifier.

[0061] In combination with the fifth aspect, in certain implementations of the fifth aspect, the processing unit is specifically configured to determine the at least one user identifier in response to an operation on the at least one user identifier.

[0062] In combination with the fifth aspect, in certain implementations of the fifth aspect, the transceiver unit is further used to send sixth information to the first electronic device in response to an operation of updating the at least one user identifier, and the sixth information is used to update the at least one user identifier.

[0063] In the sixth aspect, a device for transmitting data is provided, which includes: a transceiver unit, not used to receive fifth information from a first electronic device, the fifth information being used to indicate that the first electronic device is in a connectable state; the transceiver unit is also used to send first information to the first electronic device, the first information including a user identifier of the device.

[0064] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is further used to receive second information from the first electronic device when the user identifier of the device belongs to at least one user identifier, and the second information is used to request the device to connect to the first electronic device, and the at least one user identifier corresponds to at least one electronic device, and the at least one electronic device is an electronic device trusted by the first electronic device; the transceiver unit is also used to send third information to the first electronic device to disconnect the first electronic device from the second electronic device and to establish a connection with the first electronic device, and the second electronic device is an electronic device trusted by the first electronic device.

[0065] In combination with the sixth aspect, in some implementations of the sixth aspect, the transceiver unit is further used to receive first data from the first electronic device, where the first data is data obtained by the first electronic device through a first application of the first electronic device.

[0066] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is further used to receive second data from the first electronic device, where the second data is data exchanged between the first electronic device and the second electronic device, and the second electronic device is an electronic device trusted by the first electronic device.

[0067] In combination with the sixth aspect, in certain implementations of the sixth aspect, the transceiver unit is further used to send seventh information to the first electronic device in response to an operation of updating the at least one user identifier, and the seventh information is used to update the at least one user identifier.

[0068] In combination with the sixth aspect, in certain implementations of the sixth aspect, the device includes the first application.

[0069] In the seventh aspect, an electronic device is provided, which can be used to execute the method in the above-mentioned first aspect and any possible implementation thereof; or to execute the method in the above-mentioned second aspect and any possible implementation thereof; or to execute the method in the above-mentioned third aspect and any possible implementation thereof.

[0070] In an eighth aspect, a system for transmitting data is provided, which includes the first electronic device, the second electronic device and the third electronic device as described in the first aspect and any possible implementation thereof; or the second aspect and any possible implementation thereof; or the third aspect and any possible implementation thereof.

[0071] In the ninth aspect, a device for transmitting data is provided, comprising: a processor coupled to a memory, the memory being used to store a computer program, the processor being used to run the computer program, so that the device for transmitting data executes the method as described in the first aspect above and any possible implementation thereof; or executes the method as described in the second aspect above and any possible implementation thereof; or executes the method as described in the third aspect above and any possible implementation thereof.

[0072] In combination with the ninth aspect, in certain implementations of the ninth aspect, one or more of the memory and the transceiver are further included, and the transceiver is used to receive signals and / or send signals.

[0073] In the tenth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a computer, the computer implements the above-mentioned first aspect and any method that can be implemented in the first aspect; or implements the above-mentioned second aspect and any method that can be implemented in the second aspect; or implements the above-mentioned third aspect and any method that can be implemented in the third aspect.

[0074] In the eleventh aspect, a computer program product comprising instructions is provided. When the computer program product is run on a computer, the computer is caused to execute the above-mentioned first aspect and any method that can be implemented in the first aspect; or execute the above-mentioned second aspect and any method that can be implemented in the second aspect; or execute the above-mentioned third aspect and any method that can be implemented in the third aspect.

[0075] In the twelfth aspect, a chip is provided, which includes a processor and a data interface. The processor reads instructions stored in a memory through the data interface to execute the above-mentioned first aspect and any method that can be implemented in the first aspect; or execute the above-mentioned second aspect and any method that can be implemented in the second aspect; or execute the above-mentioned third aspect and any method that can be implemented in the third aspect.

[0076] In combination with the twelfth aspect, in one possible implementation, the processor is coupled to the memory through an interface.

[0077] In combination with the twelfth aspect, in a possible implementation, the chip system also includes a memory, in which a computer program or computer instructions are stored. BRIEF DESCRIPTION OF THE DRAWINGS

[0078] FIG1 is a schematic diagram of the structure of a wearable device.

[0079] Figure 2 is a software structure diagram of a wearable device.

[0080] FIG3 is a schematic diagram of an applicable scenario of a method for transmitting data provided in an embodiment of the present application.

[0081] FIG4 is a schematic diagram of a system architecture of a wearable device provided in an embodiment of the present application.

[0082] FIG5 is a schematic flowchart of a method for transmitting data provided in an embodiment of the present application.

[0083] FIG6 is a set of GUIs provided in an embodiment of the present application.

[0084] FIG7 is a schematic flowchart of a method for transmitting data provided in an embodiment of the present application.

[0085] FIG8 is a schematic block diagram of a device for transmitting data provided in an embodiment of the present application.

[0086] FIG9 is a schematic block diagram of a device for transmitting data provided in an embodiment of the present application. DETAILED DESCRIPTION

[0087] The technical solution in this application will be described below with reference to the accompanying drawings.

[0088] The terms used in the following embodiments are only for the purpose of describing specific embodiments and are not intended to limit the present application. As used in the specification of this application and the appended claims, the singular expressions "a", "an", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one, two or more. The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and subsequent associated objects are in an "or" relationship.

[0089] References to "one embodiment" or "some embodiments" in this specification mean that a particular feature, structure, or characteristic described in conjunction with that embodiment is included in one or more embodiments of the present application. Thus, phrases such as "in one embodiment," "in some embodiments," "in other embodiments," and "in yet other embodiments" appearing in various places in this specification do not necessarily refer to the same embodiment, but rather mean "one or more but not all embodiments," unless otherwise specifically emphasized. The terms "including," "comprising," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0090] The following describes wearable devices, user interfaces for such wearable devices, and embodiments for using such wearable devices. In some embodiments, the wearable device may be a portable wearable device that also includes other functions such as a personal digital assistant and / or a music player, such as a mobile phone, a tablet computer, a wearable device with wireless communication functions (such as a smart watch), etc. Exemplary embodiments of portable wearable devices include but are not limited to devices equipped with Or portable wearable devices with other operating systems.

[0091] 1 shows a schematic structural diagram of a wearable device 100. The wearable device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display 194, and a subscriber identification module (SIM) card interface 195. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0092] It should be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the wearable device 100. In other embodiments of the present application, the wearable device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0093] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0094] The controller may be the nerve center and command center of the wearable device 100. The controller may generate an operation control signal based on the instruction operation code and the timing signal to complete the control of fetching and executing instructions.

[0095] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use the same instruction or data again, it can directly access the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0096] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0097] The wireless communication function of the wearable device 100 can be implemented through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor.

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

[0099] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the wearable device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0100] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0101] The wireless communication module 160 can provide wireless communication solutions applied to the 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), infrared technology (IR), etc. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

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

[0103] Wearable device 100 implements display functionality through a GPU, display screen 194, and an application processor. The GPU is a microprocessor for image processing that connects display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or modify display information.

[0104] Display screen 194 is used to display images, videos, etc. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), a MiniLED, a MicroLed, a Micro-oLed, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the wearable device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0105] The wearable device 100 can implement a shooting function through an ISP, a camera 193, a video codec, a GPU, a display screen 194, and an application processor.

[0106] The ISP processes data fed back by camera 193. For example, when taking a photo, the shutter is opened, and light is transmitted through the lens to the camera's photosensitive element. The light signal is converted into an electrical signal, which is then passed to the ISP for processing and converted into a visible image. The ISP can also perform algorithmic optimization on image noise and brightness. It can also optimize parameters such as exposure and color temperature of the captured scene. In some embodiments, the ISP can be located within camera 193.

[0107] The camera 193 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the light signal into an electrical signal, and then passes the electrical signal to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV or other format. In some embodiments, the wearable device 100 may include 1 or N cameras 193, where N is a positive integer greater than 1.

[0108] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the wearable device 100 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0109] Video codecs are used to compress or decompress digital video. The wearable device 100 can support one or more video codecs. This allows the wearable device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0110] The NPU is a neural network (NN) computing processor that rapidly processes input information and continuously self-learns by drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain. The NPU can enable intelligent cognitive applications such as image recognition, face recognition, speech recognition, and text comprehension in the wearable device 100.

[0111] The external memory interface 120 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the wearable device 100. The external memory card communicates with the processor 110 through the external memory interface 120 to implement data storage functions. For example, files such as music and videos can be saved on the external memory card.

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

[0113] The wearable device 100 can implement audio functions such as music playback and recording through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor.

[0114] The audio module 170 is used to convert digital audio information into analog audio signal output, and is also used to convert analog audio input into digital audio signals. The audio module 170 can also be used to encode and decode audio signals. In some embodiments, the audio module 170 can be provided in the processor 110, or some functional modules of the audio module 170 can be provided in the processor 110.

[0115] The speaker 170A, also called a "speaker," is used to convert audio electrical signals into sound signals. The wearable device 100 can listen to music or make hands-free calls through the speaker 170A.

[0116] The receiver 170B, also called the "earpiece", is used to convert audio electrical signals into sound signals. When the wearable device 100 receives a call or voice message, the user can hear the voice by placing the receiver 170B close to the ear.

[0117] Microphone 170C, also known as "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can speak by putting their mouth close to the microphone 170C to input the sound signal into the microphone 170C. The wearable device 100 can be provided with at least one microphone 170C. In other embodiments, the wearable device 100 can be provided with two microphones 170C, which can not only collect sound signals but also realize noise reduction function. In other embodiments, the wearable device 100 can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify the source of sound, realize directional recording function, etc.

[0118] The pressure sensor 180A is used to sense pressure signals and convert them into electrical signals. In some embodiments, the pressure sensor 180A can be set on the display screen 194. There are many types of pressure sensors 180A, such as resistive pressure sensors, inductive pressure sensors, capacitive pressure sensors, etc. A capacitive pressure sensor can be a device comprising at least two parallel plates made of conductive material. When force acts on the pressure sensor 180A, the capacitance between the electrodes changes. The wearable device 100 determines the intensity of the pressure based on the change in capacitance. When a touch operation is applied to the display screen 194, the wearable device 100 detects the intensity of the touch operation based on the pressure sensor 180A. The wearable device 100 can also calculate the position of the touch based on the detection signal of the pressure sensor 180A. In some embodiments, touch operations acting on the same touch position but with different touch operation intensities can correspond to different operation instructions. For example, when a touch operation with a touch operation intensity greater than or equal to the first pressure threshold is applied to the alarm application icon, the instruction to create a new alarm is executed.

[0119] The fingerprint sensor 180H is used to collect fingerprints. The wearable device 100 can use the collected fingerprints to unlock the device, access app locks, take photos, answer calls, and more. For example, when a phone detects a touch operation on the lock screen, the phone can collect the user's fingerprint information through the fingerprint sensor 180H and match the collected fingerprint information with the fingerprint information pre-set in the phone. If the match is successful, the phone can enter the non-lock screen interface from the lock screen.

[0120] The touch sensor 180K is also called a "touch panel." The touch sensor 180K can be set on the display screen 194. The touch sensor 180K and the display screen 194 form a touch screen, also called a "touch screen." The touch sensor 180K is used to detect touch operations acting on or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K can also be set on the surface of the wearable device 100, at a different location from the display screen 194.

[0121] Figure 2 is a block diagram of the software structure of the wearable device 100 according to an embodiment of the present application. The layered architecture divides the software into several layers, each with clear roles and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer. The application layer can include a series of application packages.

[0122] As shown in Figure 2, the application layer may include camera, settings, skin modules, user interface (UI), third-party applications, etc. Among them, third-party applications may include gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message, etc.

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

[0124] As shown in FIG2 , the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

[0125] The window manager manages windowed applications. It can determine the display size, determine whether a status bar is present, lock the screen, and take screenshots. Content providers store and retrieve data and make it accessible to applications. This data can include video, images, audio, incoming and outgoing calls, browsing history and bookmarks, and phone books.

[0126] The view system includes visual controls, such as controls for displaying text and images. The view system is used to build applications. A display interface can consist of one or more views.

[0127] The phone manager is used to provide communication functions for the wearable device 100, such as management of call status (including answering, hanging up, etc.).

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

[0129] The Notification Manager allows applications to display notifications in the status bar. These messages can be displayed briefly and then disappear automatically, without requiring user interaction. For example, the Notification Manager can be used to notify users of completed downloads and message reminders. The Notification Manager can also display notifications in the top status bar as icons or scrolling text, such as notifications from background applications, or as dialog windows on the screen. Examples include displaying text messages in the status bar, emitting a sound, vibrating the wearable device, or flashing the indicator light.

[0130] The Android runtime includes the core library and the virtual machine. The Android runtime is responsible for calling and managing the Android system.

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

[0132] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

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

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

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

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

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

[0138] In addition, the system library can also include status monitoring service modules, such as a physical status recognition module for analyzing and identifying user gestures; a sensor service module for monitoring sensor data uploaded by various sensors at the hardware layer to determine the physical status of the wearable device 100.

[0139] The kernel layer is the layer between hardware and software. The kernel layer includes at least display driver, camera driver, audio driver, and sensor driver.

[0140] The hardware layer may include various sensors, such as those described in FIG1 .

[0141] In conjunction with the wearable devices described in Figures 1 and 2 above, in embodiments of the present application, wearable devices, such as smart watches, can be paired and connected to mobile phone terminals via Bluetooth. This embodiment of the present application will take the wearable device having the structure shown in Figures 1 and 2 as an example, and in conjunction with the accompanying drawings, specifically introduce the data transmission method, electronic device, and system provided in the embodiments of the present application.

[0142] With the advancement and development of science, wearable devices provide users with a richer range of services in their daily lives and production. Wearable devices can connect to other electronic devices via Bluetooth technology. These devices can range from mobile phones and tablets that users often use in daily life to specialized equipment used in production, such as mining lamps. Therefore, wearable device usage scenarios can be divided into two categories, depending on the type of device they connect to.

[0143] As shown in Figure 3, a schematic diagram of an applicable scenario of the method for transmitting data provided in an embodiment of the present application is shown. The scenario includes a wearable device 310, an electronic device 320, and an electronic device 330. In the embodiment provided in the present application, the wearable device is a smart watch, and the electronic device 320 and the electronic device 330 are mobile phone terminals. The scenarios in which the wearable device is connected to the electronic device can include 2C scenarios and 2B scenarios. Among them, the 2C scenario can be understood as the user's life scenario. The wearable device 310 obtains the user's life data (for example, heart rate, blood pressure, etc.) and can transmit the user's life data to the electronic device 320 connected to it. Similarly, the electronic device 320 can also synchronize message notifications to the wearable device 310. The 2B scenario can be understood as the user's production scenario. The wearable device 310 obtains the user's production data and can transmit the user's production data to the electronic device 330 matched with it, so as to facilitate monitoring of the user's production data while working and ensure the user's production safety.

[0144] Whether in the above-mentioned 2C scenario or 2B scenario, the wearable device 310 can only be paired and connected to one electronic device at a time. More specifically, the wearable device 310 is paired and connected with the electronic device through an application (for example, a sports and health application) carried on the electronic device. When the wearable device 310 is paired and connected with the electronic device 320 or the electronic device 330, a trust authentication or verification process needs to be completed before a secure channel for data transmission can be established between the devices. Generally speaking, electronic devices carrying applications with the same user account trust each other. Since the above-mentioned 2C scenario is a user's life scenario, the wearable device 310 and the electronic device 320 are usually devices belonging to the same user, and the user accounts of a certain application carried on the wearable device 310 and the electronic device 330 are also the same. The wearable device 310 and the electronic device 320 trust each other, and the wearable device 310 can transmit corresponding user data to the electronic device 320 through the application. The above-mentioned 2B scenario is a user's production scenario. Although the wearable device 310 and the electronic device 330 may belong to the same user's devices, the user accounts of a certain application carried on the wearable device 310 and the electronic device 330 may be different. If the wearable device 310 switches from the electronic device 320 to the electronic device 330, in order to protect the user's privacy data, the wearable device 310 will delete the user data and needs to authenticate with the electronic device 330. This switching process is relatively cumbersome, and switching back and forth will cause the user's data to be lost, affecting the user's experience.

[0145] In addition, in addition to the aforementioned issues that may arise when switching between 2C scenarios and 2B scenarios, wearable devices may also encounter the aforementioned issues when switching between different electronic devices within a 2C scenario, or between different electronic devices within a 2B scenario. Simply put, when a wearable device switches between electronic devices with different user accounts, the operation is more complicated and may also cause user data loss.

[0146] Based on this, embodiments of the present application provide a method, electronic device, and system for transmitting data. These simplify the operations required when a wearable device switches between electronic devices with different user accounts, ensure the security and integrity of data during the switch, and make the data transmission process of the wearable device more flexible, thereby improving the user experience.

[0147] For ease of understanding, Figure 4 shows a schematic diagram of the system architecture of a wearable device. The wearable device includes a trusted user list and a connection module. The wearable device can be paired and connected with other electronic devices through the connection module. The wearable device stores a trusted user list. The users in the trusted user list are the trusted users of the wearable device, and the wearable device can be directly paired and connected with the devices of the trusted users. In addition, the wearable device also carries a data sharing application, and the wearable device can use this type of application to transmit user data to other paired and connected electronic devices. Of course, the method for transmitting data provided in the embodiment of the present application also involves other electronic devices paired and connected with the wearable device. These electronic devices will also carry data sharing applications. Through this type of application, the user can view the data transmitted from the wearable device on the electronic device. In the method for transmitting data provided in the embodiment of the present application, there is no limitation on the specific data sharing application. This is an application that can assist in transmitting data between wearable devices and electronic devices, such as sports health applications.

[0148] As shown in Figure 5, a schematic flow chart of a method for transmitting data provided in an embodiment of the present application is shown. This method can be applied to a communication system including a wearable device, a 2B device, and a 2C device, wherein the 2B device can be the electronic device 330 shown in Figure 3, and the 2C device can be the electronic device 320 shown in Figure 3. The following describes method 500 in detail, assuming that the wearable device is a smartwatch and the 2B device and 2C device are mobile phone terminals.

[0149] S501: The wearable device is paired and connected with the 2C device.

[0150] It should be noted that both wearable devices and 2C devices support Bluetooth connection, and pairing and connection can be completed through Bluetooth technology.

[0151] For example, the 2C device carries an application that supports pairing with the wearable device, and the wearable device and the 2C device are paired through the application. The application may be a sports and health application.

[0152] It is understood that the user ID of the 2C device can be the user ID of the application used for pairing and connection. The user ID can also be a user account. The wearable device and the 2C device have the same user ID, or the wearable device and the 2C device have the same user account. This shows that the wearable device and the 2C device belonging to the same user account trust each other and can complete the pairing connection.

[0153] Specifically, the wearable device turns on the pairing connection function, the 2C device starts the above-mentioned application that supports pairing connection, and scans and discovers the wearable device through the application, and completes the pairing connection between the wearable device and the 2C device in response to the user's operations on the 2C device and the wearable device.

[0154] S502: The 2C device determines a trusted user list.

[0155] It should be noted that the trusted user list can be determined through the user's operation on the 2C device. It can also be understood that the trusted user is configured in response to the user's operation on the 2C device. Of course, the trusted user list can also be pre-configured in the electronic device, and this embodiment of the application is not limited to this.

[0156] Exemplarily, the trusted user list is determined by the user operating an application supporting pairing connection hosted on the 2C device.

[0157] It should be noted that the operation of the user determining the trusted user list includes but is not limited to adding a trusted user and deleting a trusted user.

[0158] For ease of understanding, as shown in FIG6 , a set of graphical user interfaces (GUIs) provided by the present application is shown, and a method for determining a trusted user list is introduced by taking a mobile phone terminal as an example of a 2C device.

[0159] As shown in (a) of Figure 6, the display interface of the sports health application of the mobile terminal is shown. A plurality of controls are included at the bottom of the display interface, including controls for health, sports, equipment and me. The display interface is the interface corresponding to the device control. The display interface includes a plurality of tags, including a connected device tag 601, an add device tag 602 and a set trusted user tag 603. Among them, the connected device tag 601 indicates that the mobile terminal is connected to the smart watch 1; the add device tag 602 indicates that the mobile terminal can also establish a connection with other devices; the device trusted user tag 603 indicates that one or more trusted users can be added or deleted. In response to the user's operation on the device trusted user tag 603, the mobile terminal can display a GUI as shown in (b) of Figure 6.

[0160] As shown in FIG6(b), in response to the user's operation on the Set Trusted User tab 603, the mobile terminal displays a Set Trusted User interface. This interface displays a Trusted User list 604, which displays the identities of the established trusted users, such as User A's identity, User B's identity, and User C's identity. This indicates that User A, User B, and User C are trusted users of the mobile terminal. Alternatively, the devices corresponding to the trusted users displayed in Trusted User list 604 are trusted devices, such as User A's device, User B's device, and User C's device are trusted devices of the mobile terminal. Trusted User list 604 also includes multiple controls, such as a Delete control and an Add New User control 605. The Delete control corresponds to different users. In response to the user's operation on the Delete control, the corresponding user can be deleted from the Trusted User list. The Add New User control allows the user to add a new trusted user. In response to the user's operation on the Add New User control 605, the mobile terminal may display the GUI shown in FIG6(c).

[0161] As shown in (c) of Figure 6, in response to the user's operation on the add new user control 605, the mobile terminal displays a trusted user interface. The interface includes a prompt message 606 for prompting the user to enter a user ID, and the user ID corresponds to the user one-to-one. Among them, the user ID can be a user account or a verification code displayed on the user device. The embodiment of the present application does not limit the method for the user to obtain the user ID or user account. For example, in response to the user's operation on the add new user control, a verification code can be displayed on the peripheral device in the mobile terminal, and the verification code is used to identify the user ID of the peripheral device. The prompt message 606 includes an input box 607, an add control 608, and a cancel control. The user can enter the user ID corresponding to the user in the input box 607 to add the user. In response to the user's operation of entering the user ID in the input box 607 and the operation of the add control 608, the mobile terminal can display the GUI shown in (d) of Figure 6.

[0162] As shown in FIG6(d), in response to the user entering a user ID in input box 607 and clicking on add control 608, the mobile terminal displays a user interface for setting up trusted users. Trusted user list 604 on this interface is updated, with the ID of user D added. The trusted user list also includes a save control 609. Clicking on save control 609 completes the update of the trusted user list. The updated trusted user list now includes the IDs of user A, user B, user C, and user D. Compared to the trusted user list before the update, the trusted user list now includes the IDs of user D.

[0163] In addition to adding trusted users to the trusted user list, the user can also delete users from the trusted user list. The delete control 610 included in the trusted user list 604 corresponds to user A. In response to the user's operation on the delete control 610, the mobile terminal can display the GUI shown in (e) of FIG. 6 .

[0164] As shown in FIG6(e), in response to the user's operation on the delete control 610, the mobile terminal displays a user interface for setting up trusted users. The trusted user list 604 on this interface is updated, and the identifier of user A is deleted. In response to the user's operation on the save control 609, the trusted user list is updated. The updated trusted user list includes the identifiers of user B, user C, and user D. Compared to the trusted user list before the update, trusted user A has been deleted.

[0165] S503: The 2C device sends a trusted user list, and correspondingly, the wearable device receives the trusted user list.

[0166] It should be noted that after determining the trusted user list based on the user's operation on the 2C device, the 2C device can synchronize the trusted user list to the wearable device. The trusted user list synchronized by the 2C device to the wearable device in step S503 can be the trusted user list most recently updated by the user.

[0167] It is understandable that every time a user updates (including adding or deleting) the trusted list, the 2C device needs to send the updated trusted user list to the wearable device; or, every time a user updates the trusted list, the 2C device can send a notification message to the wearable device, notifying the wearable device that a user identifier has been added or deleted from the original trusted list.

[0168] It should be noted that the prerequisite for the 2C device to synchronize the trusted user list with the wearable device is that the 2C device and the wearable device are connected. In other words, if the wearable device is connected to device 1 and then switches to device 2, the user can complete the update of the trusted user list on device 2, and device 2 will synchronize the updated trusted user list with the wearable device.

[0169] It is understood that the embodiments of the present application do not limit the specific method by which the 2C device synchronously updates the user list to the wearable device. The 2C device may send the trusted user list to the wearable device at a certain period, or may send the trusted user list to the wearable device whenever the trusted user list is updated. In addition, the embodiments of the present application do not limit the specific form of the information carrying the trusted user list.

[0170] S504: The wearable device stores a list of trusted users.

[0171] It should be noted that the wearable device can store a trusted user list from the 2C device so as to verify the user identification in subsequent steps. The trusted user list includes the identification of the trusted user, which corresponds to the trusted user.

[0172] It is understandable that when the trusted user list is updated, the wearable device can receive the updated trusted user list from the 2C device and store the updated trusted user list; or when the trusted user list is updated, the wearable device can receive notification information from the 2C device and modify the stored trusted user list according to the notification information.

[0173] S505: The wearable device starts a data sharing application.

[0174] For example, a data sharing application may be started through a user's operation on a wearable device.

[0175] It is understandable that the data sharing application is similar to the sports health application mentioned above and can support pairing connection. The wearable device can also transmit corresponding data to the paired connected device through the data sharing application.

[0176] S506: The wearable device sends a Bluetooth broadcast message, and correspondingly, the 2B device receives the Bluetooth broadcast message.

[0177] It should be noted that this broadcast message is used to indicate that the wearable device can be connected.

[0178] S507, the 2B device starts a data sharing application.

[0179] For example, a data sharing application may be started through a user's operation on a 2B device.

[0180] It should be noted that the data sharing application started on the 2B device in step S507 is the same as the data sharing application started on the wearable device in step S505 above.

[0181] It is understandable that after the 2B device starts the data sharing application, it can receive Bluetooth broadcast messages from the wearable device through the data sharing application. Through the user's operation on the data sharing application of the 2B device, it attempts to pair with the wearable device.

[0182] Exemplarily, the operation of the user triggering the pairing connection with the wearable device on the 2B device is similar to the operation of the user triggering the pairing connection with the wearable device on the 2C device in step S501 above.

[0183] It should be noted that the embodiment of the present application does not limit the execution order of step S507, and step S507 can be executed before step S508.

[0184] S508, the 2B device sends the user identification of the 2B device, and correspondingly, the wearable device receives the user identification of the 2B device.

[0185] It should be noted that the 2B device starts the data sharing application, and the user account logged in on the data sharing application corresponds to a certain user identifier. The 2B device sends the user identifier corresponding to the user account logged in on the data sharing application to the wearable device. The specific form of the user identifier is not limited in this embodiment of the application.

[0186] It should be noted that the embodiment of the present application does not limit the specific form of the information carrying the user identification. For example, the 2B device can send the user identification to the wearable device via Bluetooth data.

[0187] S509: The wearable device verifies the user ID.

[0188] It should be noted that the user identifier corresponds to the user one-to-one. The wearable device compares the user identifier received in step S508 with the trusted user in the trusted user list stored in step S504. This comparison is the process of the wearable device verifying the user identifier. If the user identifier received by the wearable device in step S508 belongs to the trusted user in the trusted user list, it means that the user corresponding to the user identifier is trusted, and the 2B device that logs into the data sharing application of the user account is trusted; if the user identifier received by the wearable device in step S508 does not belong to the trusted user in the trusted user list, it means that the user corresponding to the user identifier is not trusted, and the 2B device that logs into the data sharing application of the user account is not trusted.

[0189] For example, if the wearable device receives user identification B from the 2B device, user identification B corresponds to user B. The wearable device determines that user B is included in the trusted user list, that is, user B is trusted, and can directly establish a connection with the 2B device. If the wearable device receives user identification E from the 2B device, user identification E corresponds to user E. The wearable device determines that user E is not included in the trusted user list, that is, user B is untrusted. If the wearable device needs to establish a connection with the 2B device, it must first perform security authentication with the 2B device.

[0190] It can be seen that according to the result of the wearable device verifying the user identification, the method for transmitting data provided in the embodiment of the present application will optionally perform the following two steps.

[0191] Optionally, in S510, when the wearable device is successfully verified, data is transmitted to the 2B device.

[0192] Exemplarily, successful verification of the wearable device indicates that the user identifier received in step S508 is included in the trusted user list.

[0193] It should be noted that when the wearable device determines that the user ID of the 2B device is included in the trusted user list, the wearable device and the 2B device can establish a connection without security authentication. While the wearable device is connected to the 2B device, the connection with the 2C device can be disconnected.

[0194] It is understandable that when the wearable device is paired with the 2B device, the wearable device can transmit data to the 2B device through the data sharing application, so that the user can view the relevant data on the 2B device.

[0195] It should be noted that when a wearable device switches from a 2C device to a 2B device, although the user accounts of the 2B device and the 2C device are different, because the 2B device is trusted, the wearable device does not need to delete the previously stored user data for data security. This simplifies the operation of switching between different user account devices, ensures data security, and avoids data loss.

[0196] Furthermore, in the method for determining the trusted user list described in step S502 above, the wearable device is paired with the 2C device and connected. Through the user's operation on the 2C device, a trusted user can be added to the trusted user list or a trusted user can be deleted. When the wearable device verifies that the user identifier of the 2B device belongs to the trusted user list, the wearable device can be paired with the 2B device. Through the user's operation on the 2B device, a trusted user can also be added to the trusted user list or a trusted user can be deleted. The user's operation on the 2B device is similar to the above description of Figure 6 and will not be repeated here.

[0197] Optionally, in S511, when the wearable device fails to be inspected, security authentication with the 2B device is performed.

[0198] Exemplarily, failure of the wearable device verification indicates that the user identifier received in step S508 is not included in the trusted user list.

[0199] It should be noted that when the wearable device determines that the user identifier of the 2B device is not included in the trusted user list, the wearable device needs to perform security authentication with the 2B device first. Only after the security authentication is passed can a connection be established.

[0200] It is understandable that the disconnection between the wearable device and the 2B device in step S511 indicates that the wearable device will not send data to the 2B device. However, since the wearable device sends a broadcast message in step S506, other 2B devices may also receive the broadcast message. After receiving the broadcast message, the other 2B devices can send their user identification to the wearable device so that the wearable device can verify the user identification of the device.

[0201] It should be noted that the embodiments of the present application do not limit the application for pairing connection (or data transmission) carried by the 2C device and the application for pairing connection (or data transmission) carried by the 2B device. The applications for pairing connection (or data transmission) carried by the 2C device and the 2B device may be the same or different.

[0202] In the above method 500, before switching, the wearable device is connected to the 2C device, and after switching, the wearable device is connected to the 2B device. The user account of the 2C device is different from the user account of the 2B device. The method for transmitting data provided in the embodiment of the present application is not only applicable to the scenario in which the above-mentioned wearable device switches from a device in the 2C scene to a device in the 2B scene, but can also be applied to the switching of the wearable device between different electronic devices in a single scene (for example, a 2C scene, or a 2B scene), and the user accounts of the electronic devices connected before and after the wearable device switches are different.

[0203] FIG7 is a schematic flow chart of a method for transmitting data according to an embodiment of the present application. This method can be applied to the scenario shown in FIG2 . In method 700, the first electronic device can be a wearable device, the second electronic device can be a 2C device, and the third electronic device can be a 2B device. The user identifier of the second electronic device is different from the user identifier of the third electronic device. Method 700 is described in detail below.

[0204] S701: The second electronic device determines at least one user identifier.

[0205] It should be noted that the second electronic device is connected to the first electronic device. At least one user identifier corresponds to at least one electronic device, and at least one electronic device is trusted by the first electronic device. In other words, if the first electronic device trusts a certain electronic device, then the first electronic device trusts the user of the electronic device. If the first electronic device trusts a certain electronic device, when the first electronic device attempts to connect to the electronic device, trust authentication may not be required.

[0206] Exemplarily, the second electronic device may determine a trusted user list, where the trusted user list includes at least one user identifier, and the electronic device or the corresponding user corresponding to the at least one user identifier in the trusted list is trusted.

[0207] Specifically, the second electronic device determines at least one user identification in response to an operation on at least one user identification.

[0208] That is, by the user inputting the user ID on the second electronic device, the user ID can be added to the trusted user list, that is, the electronic device corresponding to the user ID is added as a trusted device, or the user corresponding to the user ID is added as a trusted user.

[0209] For example, the second electronic device is a mobile phone terminal as shown in Figure 6. As shown in (c) in Figure 6, through the operation of the user inputting the user identification, the mobile phone terminal displays the interface as shown in (d) in Figure 6. The trusted user list in the interface is added with user D corresponding to the above-mentioned input user identification.

[0210] S702: The second electronic device sends fourth information, and correspondingly, the first electronic device receives the fourth information.

[0211] It should be noted that the fourth information includes at least one user identifier. That is, after determining the at least one user identifier, the at least one user identifier can be sent to the first electronic device.

[0212] Exemplarily, the first electronic device may store at least one user identification.

[0213] Furthermore, when the first electronic device is connected to the second electronic device, at least one user identification can be updated through user operations on the second electronic device.

[0214] Specifically, in response to the user's operation of updating at least one user identification on the second electronic device, sixth information is sent to the first electronic device, where the sixth information is used to update the at least one user identification.

[0215] Exemplarily, updating at least one user identifier may include adding a new user identifier or deleting an existing user identifier.

[0216] For example, as shown in (d) in FIG6 , the identifier of user D in the trusted user list may be deleted.

[0217] S703: The first electronic device sends fifth information in response to starting the first application program, and correspondingly, the third electronic device receives the fifth information.

[0218] It should be noted that the fifth information is used to indicate that the first electronic device is in a connectable state. The first electronic device in the connectable state can attempt to establish a connection with other electronic devices.

[0219] For example, the first application may be the data sharing application in method 500. The fifth information may be information broadcast via Bluetooth technology. That is, after the first application on the first electronic device is launched, the first electronic device may broadcast a Bluetooth message indicating that the first electronic device is currently connectable.

[0220] It can be understood that the third electronic device can be a peripheral device of the first electronic device, and the third electronic device can receive the fifth information broadcast by the first electronic device.

[0221] S704: The third electronic device sends the first information, and correspondingly, the first electronic device receives the first information.

[0222] It should be noted that the first information includes the user identification of the third electronic device. When the third electronic device receives the fifth information from the first electronic device, it determines that the first electronic device is connectable based on the fifth information and can send the user identification of the third electronic device to the first electronic device.

[0223] S705: The first electronic device determines whether the user identifier of the third electronic device belongs to at least one user identifier.

[0224] In one implementation, when the user identifier of the third electronic device belongs to at least one user identifier, the first electronic device sends second information to the third electronic device, and the second information is used to request a connection with the third electronic device; the first electronic device receives third information from the third electronic device to disconnect from the second electronic device and to establish a connection with the third electronic device, wherein the third information is feedback information of the second information.

[0225] It should be noted that when the user identifier of the third electronic device belongs to at least one user identifier, it means that the third electronic device is an electronic device trusted by the first electronic device. When establishing a connection between the first electronic device and the third electronic device, no security authentication is required. The first electronic device requests to establish a connection with the third electronic device, and when the first electronic device receives positive feedback (third information) from the third electronic device, a communication connection can be established. That is, the method for transmitting data provided in this application can simplify the process of switching the first electronic device between electronic devices of different user accounts.

[0226] In one implementation, a first electronic device is connected to a third electronic device, and the first electronic device sends first data to the third electronic device, where the first data is data acquired by the first electronic device through a first application of the first electronic device.

[0227] It should be noted that after the first electronic device is connected to the third electronic device, the first electronic device disconnects from the second electronic device and can transmit data to the third electronic device. Furthermore, the first electronic device activates the first application and can transmit data to the third electronic device through the first application.

[0228] Exemplarily, the first application may be a data sharing application.

[0229] It can be understood that the third electronic device includes the first application.

[0230] Optionally, before the third electronic device sends the first information to the first electronic device, the first application is also started on the third electronic device.

[0231] In one implementation, a first electronic device is connected to a third electronic device, and the first electronic device sends second data to the third electronic device, where the second data is data exchanged between the first electronic device and the second electronic device.

[0232] Optionally, the second data may be data related to the second electronic device, including data of interaction between the second electronic device and the first electronic device, and device data of the second electronic device (eg, device identification).

[0233] It can be seen that when the third electronic device is a trusted device of the first electronic device, or the user of the third electronic device is a trusted user of the first electronic device, the first electronic device and the third electronic device can establish a connection without security authentication, and there is no need to delete the data (second data) transmitted between the first electronic device and the historically connected electronic device (for example, the second electronic device). After the first electronic device is connected to the third electronic device, even if the user account of the first electronic device is different from the user account of the third electronic device, the first electronic device can transmit data to the third electronic device. This simplifies the operation of switching the first electronic device between electronic devices with different user accounts, improves switching efficiency, and ensures the security and integrity of user data.

[0234] Furthermore, when the first electronic device is connected to the third electronic device, at least one user identification can be updated through user operations on the third electronic device.

[0235] Specifically, in response to the user's operation of updating at least one user identification on the third electronic device, seventh information is sent to the first electronic device, where the seventh information is used to update the at least one user identification.

[0236] Exemplarily, updating at least one user identifier may include adding a new user identifier or deleting an existing user identifier.

[0237] It can be understood that the operation of the user updating the user identification on the third electronic device is similar to the operation of the user updating the user identification on the second electronic device.

[0238] The data transmission method provided in the embodiment of the present application can configure a trusted user for the wearable device. That is, when the wearable device needs to switch to an electronic device with a different user account, if the user of the electronic device is a trusted user of the wearable device, the security authentication process between the wearable device and the electronic device can be omitted, thereby improving the efficiency of the wearable device switching while ensuring the security and integrity of the user data.

[0239] The data transmission method provided by the embodiments of the present application is described in detail above with reference to Figures 1 to 7. In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced to each other. The technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0240] The apparatus provided in the embodiments of the present application will be described in detail below with reference to Figures 8 and 9. It should be understood that the description of the apparatus embodiment corresponds to the description of the method embodiment, and therefore, for matters not described in detail, reference can be made to the method embodiment above, and for the sake of brevity, no further description will be given here.

[0241] FIG8 shows a schematic block diagram of an apparatus 800 provided in an embodiment of the present application. The apparatus 800 may include a unit for executing the method for transmitting data in FIG7 .

[0242] Specifically, the device 800 includes a processing unit 810 and a transceiver unit 820 .

[0243] Optionally, the device 800 also includes a storage unit, which can be used to store instructions and / or data, and the processing unit 810 can read the instructions and / or data in the storage unit so that the device implements the relevant actions performed by the electronic device in the aforementioned various method embodiments.

[0244] The apparatus 800 can be used to execute the actions performed by the electronic device in each of the above method embodiments. In this case, the apparatus 800 can be a component of the electronic device, for example, the apparatus 800 can also be a chip or integrated circuit in the electronic device. The processing unit 810 is used to execute the processing-related operations of the electronic device in the above method embodiments, and the transceiver unit 820 is used to execute the transceiver-related operations of the electronic device in the above method embodiments.

[0245] It should be understood that the specific process of each unit executing the above corresponding steps has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here.

[0246] In a specific implementation, the actions performed by the processing unit 810 and the transceiver unit 820 may be implemented by one processor, or may be implemented by multiple processors.

[0247] Figure 9 is another schematic block diagram of an apparatus provided in an embodiment of the present application. The apparatus 900 shown in Figure 9 may include: a processor 910, a transceiver 920, and a memory 930. The processor 910, the transceiver 920, and the memory 930 are connected via an internal connection path. The memory 930 is used to store instructions, and the processor 910 is used to execute the instructions stored in the memory 930 to implement the methods in the above embodiments. Optionally, the memory 930 can be coupled to the processor 910 via an interface or integrated with the processor 910.

[0248] It should be noted that the transceiver 920 may include but is not limited to a transceiver device such as an input / output interface to implement communication between the device 900 and other devices or a communication network.

[0249] The memory 930 may be a volatile memory and / or a non-volatile memory. The non-volatile memory may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory may be a random access memory (RAM). For example, RAM may be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0250] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0251] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0252] The transceiver 920 uses a transceiver device such as but not limited to a transceiver to implement communication between the apparatus 900 and other devices or a communication network, so as to receive / send data / information used to implement the methods in the above embodiments.

[0253] The device 900 may be a chip or a circuit provided in the above-mentioned electronic device.

[0254] An embodiment of the present application further provides a computer program product, which includes computer program code. When the computer program code runs on a computer, the computer implements the methods in the above embodiments of the present application.

[0255] An embodiment of the present application further provides a computer-readable storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the computer implements the methods in the above embodiments of the present application.

[0256] An embodiment of the present application also provides a chip, including a circuit, for executing the methods in the above embodiments of the present application.

[0257] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0258] In the description of the embodiments of the present application, unless otherwise specified, " / " means or, for example, A / B can mean A or B; "and / or" in this article is a kind of association relationship that describes associated objects, indicating that there can be three relationships, for example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. In this application, "at least one" refers to one or more, and "more than one" refers to two or more. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, c can be single or multiple.

[0259] In the embodiments of this application, prefixes such as "first" and "second" are used only to distinguish different description objects and have no limiting effect on the position, order, priority, quantity, or content of the described objects. The use of prefixes such as ordinal numbers in the embodiments of this application to distinguish description objects does not constitute a limitation on the described objects. For a statement of the described objects, please refer to the description in the context of the claims or embodiments, and the use of such prefixes should not constitute an unnecessary limitation.

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

[0261] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between the various embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0262] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0263] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0264] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for transmitting data, characterized in that: The method is applied to a first electronic device, where the first electronic device is connected to a second electronic device, and includes: receiving first information from a third electronic device, where the first information includes a user identifier of the third electronic device; It is determined whether the user identifier of the third electronic device belongs to at least one user identifier, the at least one user identifier corresponds to at least one electronic device, and the at least one electronic device is an electronic device trusted by the first electronic device.

2. The method according to claim 1, characterized in that The method further comprises: When the user identifier of the third electronic device belongs to the at least one user identifier, sending second information to the third electronic device, where the second information is used to request a connection with the third electronic device; receiving third information from the third electronic device to disconnect from the second electronic device and to establish a connection with the third electronic device, wherein the third information is feedback information of the second information; 3. The method according to claim 2, characterized in that The method further comprises: First data is sent to the third electronic device, where the first data is data acquired by the first electronic device through a first application of the first electronic device.

4. The method according to claim 2 or 3, characterized in that The method further comprises: Second data is sent to the third electronic device, where the second data is data exchanged between the first electronic device and the second electronic device.

5. The method according to claim 3, characterized in that Before receiving the first information from the third electronic device, the method further includes: receiving fourth information from the second electronic device, the fourth information including the at least one user identifier; In response to starting the first application, fifth information is sent, where the fifth information is used to indicate that the first electronic device is in a connectable state.

6. The method according to claim 1, characterized in that The method further comprises: Receive sixth information from the second electronic device, where the sixth information is used to update the at least one user identifier.

7. The method according to any one of claims 2 to 4, characterized in that The method further comprises: Receive seventh information from the third electronic device, where the seventh information is used to update the at least one user identifier.

8. The method according to claim 3 or 5, characterized in that The third electronic device includes the first application.

9. The method according to any one of claims 1 to 8, characterized in that The user identification of the second electronic device is different from the user identification of the third electronic device.

10. A method for transmitting data, characterized in that: The method is applied to a second electronic device connected to a first electronic device, and includes: Determining at least one user identifier, where the at least one user identifier corresponds to at least one electronic device, and the at least one electronic device is an electronic device trusted by the first electronic device; Fourth information is sent to the first electronic device, where the fourth information includes the at least one user identifier.

11. The method according to claim 10, characterized in that The determining of at least one user identifier includes: In response to the operation on the at least one user identification, the at least one user identification is determined.

12. The method according to claim 10 or 11, characterized in that The method further comprises: In response to the operation of updating the at least one user identifier, sixth information is sent to the first electronic device, where the sixth information is used to update the at least one user identifier.

13. A method for transmitting data, characterized in that: The method is applied to a third electronic device, and includes: receiving fifth information from the first electronic device, wherein the fifth information is used to indicate that the first electronic device is in a connectable state; First information is sent to the first electronic device, where the first information includes a user identifier of the third electronic device.

14. The method according to claim 13, characterized in that The method further comprises: When the user identifier of the third electronic device belongs to at least one user identifier, receiving second information from the first electronic device, the second information being used to request the third electronic device to connect to the first electronic device, the at least one user identifier corresponding to at least one electronic device, and the at least one electronic device being an electronic device trusted by the first electronic device; The third information is sent to the first electronic device so that the first electronic device is disconnected from a second electronic device and is connected to the first electronic device, where the second electronic device is an electronic device trusted by the first electronic device.

15. The method according to claim 14, characterized in that The method further comprises: First data is received from the first electronic device, where the first data is data acquired by the first electronic device through a first application of the first electronic device.

16. The method according to claim 14 or 15, characterized in that The method further comprises: Second data is received from the first electronic device, where the second data is data exchanged between the first electronic device and a second electronic device, and the second electronic device is an electronic device trusted by the first electronic device.

17. The method according to any one of claims 14 to 16, characterized in that The method further comprises: In response to the operation of updating the at least one user identifier, seventh information is sent to the first electronic device, where the seventh information is used to update the at least one user identifier.

18. The method according to claim 15, characterized in that The third electronic device includes the first application.

19. A device for transmitting data, characterized in that: The device for transmitting data includes a unit for executing the method as claimed in any one of claims 1 to 9; or includes a unit for executing the method as claimed in any one of claims 10 to 12; or includes a unit for executing the method as claimed in any one of claims 13 to 18.

20. An electronic device, characterized in that: The electronic device is configured to execute the method according to any one of claims 1 to 9; or to execute the method according to any one of claims 10 to 12; or to execute the method according to any one of claims 13 to 18.

21. A device for transmitting data, characterized in that: A processor coupled to a memory, the memory being used to store a computer program, the processor being used to run the computer program so that the device for transmitting data performs the method according to any one of claims 1 to 9; or performs the method according to any one of claims 10 to 12; or performs the method according to any one of claims 13 to 18.

22. A computer-readable storage medium, characterized in that A computer program is stored thereon, and when the computer program is executed by a computer, the computer implements the method according to any one of claims 1 to 9; or implements the method according to any one of claims 10 to 12; or implements the method according to any one of claims 13 to 18.

23. A computer program product comprising instructions, characterized in that When the computer program product is run on a computer, the computer is enabled to perform the method according to any one of claims 1 to 9; or the method according to any one of claims 10 to 12; or the method according to any one of claims 13 to 18.

24. A chip, characterized in that: The chip includes a processor and a data interface, and the processor reads instructions stored in the memory through the data interface to execute the method as described in any one of claims 1 to 9; or executes the method as described in any one of claims 10 to 12; or executes the method as described in any one of claims 13 to 18.

Images