Business data transmission method and electronic device

Abstract

The application provides a service data transmission method and an electronic device, and relates to the technical field of communication. In a weak network environment, a device 1 in a trust ring fails to refresh a trust ring device list, considers that the trust ring device list on the device 1 is unreliable, and does not bring other devices in the trust ring online. After receiving a registration notification message, it is indicated that a device 2 indicated by the registration notification message is a newly added device in the trust ring. Although the trust ring device list refresh fails, the device 1 still determines that the device 2 is reliable, so that the device 2 is brought online as a device in the trust ring where the device 1 is located. Then, the device 1 can transmit service data corresponding to the trust ring service with the device 2, realizes normal operation of the trust ring service, avoids the situation that the trust ring device list refresh fails due to the weak network environment, and cannot transmit service data with a newly added device in the trust ring, and improves user experience.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a service data transmission method and electronic device. Background Technology

[0002] With the continuous development of terminal technology and the increasing variety of terminals, multi-device collaboration is becoming more widespread. For example, devices logged into the same account can discover each other, forming a trust loop, which facilitates the transmission of business data between multiple devices and improves user convenience.

[0003] The devices in the trust ring may change, such as users adding devices as needed. However, if device A in the trust ring is unable to know about other devices in the trust ring due to factors such as a weak network environment, then after adding a new device, device A will be unable to transmit service data corresponding to the trust ring service with the new device, such as audio data corresponding to audio streaming services, affecting the user experience. Summary of the Invention

[0004] This application provides a business data transmission method and an electronic device to solve the technical problem that electronic devices cannot transmit business data with newly added devices in a trust ring.

[0005] To achieve the above objectives, the embodiments of this application adopt the following technical solutions:

[0006] Firstly, a business data transmission method is provided, applied to a first device. The first device can send a first request to the device cloud, which is used to obtain the list of trust ring devices corresponding to the trust ring in which the first device is located.

[0007] If the first device does not receive the trust ring device list sent by the device cloud, the first device can set the trust ring device list status of the first device to an unready state, which indicates that the trust ring device list refresh has failed.

[0008] Subsequently, while the first device was in a pre-ready state, a registration notification message was received from the device cloud. This registration notification message was sent by the device cloud after the second device joined the trust ring while the first device was in a pre-ready state.

[0009] In response to the registration notification message, the first device can include the second device as a device in the trust ring to transmit service data corresponding to the trust ring service with the second device.

[0010] In this application, after the first device fails to refresh the trust ring device list, it determines that the trust ring device list on the first device is untrustworthy, meaning the devices indicated by the trust ring device list are unreliable; in other words, the devices in the trust ring are unreliable. Subsequently, the first device receives a registration notification message indicating that a second device joined the trust ring to which the first device is located during the period when the trust ring device list refresh failed. Although the first device might mistakenly believe that the devices in the trust ring are unreliable due to the failure of the trust ring device list refresh, and thus mistakenly believe that the second device is unreliable, the registration notification message instructing the second device to join the ring is sent by the device cloud. Therefore, the reliability of the second device is relatively high, and the first device can then include the second device in the trust ring, enabling the second device to go online. Afterwards, the first device can transmit business data corresponding to the trust ring service with the second device, ensuring the normal operation of the trust ring service and facilitating user access.

[0011] In one possible design, the process of designating the second device as a device in the trust ring may include: the first device adding the information of the second device to a first device list, which includes information on all newly added devices in the trust ring while the first device is in a pre-ready state. This newly added device includes the second device. Then, for each device in the first device list, based on that information, the first device may designate that device as a device in the trust ring.

[0012] Based on this, this application adds a first device list to record information about all newly added devices in the trust ring where the first device is located during the period when the first device's trust ring device list refresh fails. Afterwards, the first device can consider all newly added devices to be reliable, thus including all newly added devices in the trust ring where the first device is located, and enabling the newly added devices to come online.

[0013] In one possible design, after receiving a registration notification message from the device cloud, the first device can also recognize the second device as a Bluetooth-paired device in response to the registration notification message. Thus, when the first device and the second device are close to each other, the first device can directly establish a connection with the second device via Bluetooth without having to obtain pairing information again, thereby improving communication efficiency.

[0014] In one possible design, upon receiving a registration notification message from the device cloud, the first device, in response to the notification message, can also obtain a second device list including information on devices that do not require Bluetooth pairing. Then, for each device in the second device list, based on that information, the first device can designate that device as a Bluetooth-paired device. This allows the first device to directly establish a connection with a Bluetooth-paired device when it is near a device that does not require Bluetooth pairing, thus improving communication efficiency.

[0015] In one possible design, the first device failed to refresh the trust ring device list due to poor network conditions; that is, the first device was in a weak network environment when the first request was sent.

[0016] In one possible design approach, after receiving the registration notification message from the device cloud, it indicates that the first device is now able to interact with the device cloud. At this point, the likelihood of successfully obtaining the trust ring device list from the device cloud is relatively high. For example, if the first device's network condition caused the trust ring device list refresh to fail, then after receiving the registration notification message from the device cloud, the first device's network condition is likely to recover. Therefore, the first device can resend the first request to the device cloud to try refreshing the trust ring device list again, avoiding unnecessary trust ring device list refresh operations that would increase the power consumption of the first device.

[0017] In one possible design, the first request is sent by the device management service in the first device. Upon receiving a first notification message from the connection service in the first device, the device management service can resend the first request to the device cloud. This first notification message indicates that the first device is still in a pre-ready state and requires an update to the trust ring device list.

[0018] In one possible design, upon receiving a list of trusted ring devices from the device cloud, the first device can set the status of the trusted ring device list to "ready." Then, the first device can add the devices indicated by the trusted ring device list as devices in the trusted ring, thus bringing them online. Afterward, the first device can transmit business data with the devices in the trusted ring.

[0019] In a second aspect, this application provides an electronic device that can serve as the first device. The electronic device includes a memory and one or more processors. The memory and the processors are coupled. The memory is used to store computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device performs the business data transmission method described in the first aspect above.

[0020] Thirdly, this application provides a chip, the chip including a communication interface and at least one processor:

[0021] The communication interface is used for inputting and / or outputting signaling or data;

[0022] The at least one processor is configured to execute a computer program to implement the business data transmission method described in the first aspect above.

[0023] Fourthly, this application provides a computer-readable storage medium including computer instructions that, when executed on an electronic device, cause the electronic device to perform the business data transmission method described in the first aspect above.

[0024] Fifthly, this application provides a computer program product, including a computer program that, when executed by a processor, implements the business data transmission method described in the first aspect above.

[0025] It is understood that the beneficial effects achieved by the electronic device described in the second aspect, the chip described in the third aspect, the computer-readable storage medium described in the fourth aspect, and the computer program product described in the fifth aspect can be referred to the beneficial effects in the first aspect and any of its possible design embodiments, which will not be repeated here. Attached Figure Description

[0026] Figure 1A A schematic diagram illustrating a trust ring device list refresh scenario provided in an embodiment of this application;

[0027] Figure 1B A schematic diagram of a trust loop provided for an embodiment of this application;

[0028] Figure 2A A schematic diagram of a trust ring service data transmission process is provided as an embodiment of this application;

[0029] Figure 2B A schematic diagram of a trust ring service data transmission process provided in this application embodiment;

[0030] Figure 3 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0031] Figure 4 A schematic diagram of the software structure of an electronic device provided in an embodiment of this application;

[0032] Figure 5 A flowchart illustrating a business data transmission method provided in an embodiment of this application;

[0033] Figure 6A second schematic diagram of a trust loop provided for an embodiment of this application;

[0034] Figure 7 A schematic diagram of a trust loop provided in an embodiment of this application. Figure 3 ;

[0035] Figure 8 A second schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0036] Figure 9 This is a schematic diagram of a chip system provided in an embodiment of this application. Detailed Implementation

[0037] To facilitate a clear description of the technical solutions in the embodiments of this application, the terms "exemplary" or "for example" are used in the embodiments of this application to indicate examples, illustrations, or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of terms such as "exemplary" or "for example" is intended to present related concepts in a specific manner. In the embodiments of this application, "at least one" refers to one or more, and "more" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone, where A and B can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. In the embodiments of this application, "first," "second," "1," and "2" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of indicated technical features. Therefore, features defined with "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this embodiment, unless otherwise stated, "multiple" means two or more.

[0038] To more clearly describe the solution of this application, some knowledge related to the embodiments of this application will be introduced below.

[0039] Trust ring: The same user account can log in on different electronic devices. When two or more electronic devices under the same user account trust each other, they form a trust ring. For an electronic device in the trust ring (e.g., electronic device 1), all other electronic devices in the trust ring (e.g., electronic device 2) can be understood as trusted devices of electronic device 1. Electronic devices in the trust ring are intelligently interconnected, supporting functions such as service flow and service sharing.

[0040] Weak network environment: also known as a weak network scenario. When the network status value of an electronic device is lower than a preset value, it indicates a poor network condition, and the electronic device can be considered to be in a weak network environment. The network status can be represented by indicators such as network signal strength and network transmission speed.

[0041] During the use of electronic devices, they frequently perform business operations. Some of these operations rely on network conditions. These operations typically involve a large amount of business data and are time-consuming. However, when network conditions are poor, indicating that the electronic device is in a weak network environment, these business operations will be affected, causing related services to malfunction. For example, in a trust ring scenario, electronic devices within the trust ring need to utilize the network to refresh the trust ring device list from the device cloud so that the electronic devices can become aware of the devices in the trust ring and thus conduct business transmissions with them.

[0042] For example, such as Figure 1A As shown, after device 1 in the trust ring powers on, it sends request 1 to the device cloud, carrying the user account 1 that device 1 is logged into. Request 1 is used to obtain the trust ring device list corresponding to user account 1. This trust ring device list includes information about the devices in the trust ring corresponding to user account 1, such as device identifiers and public keys. Subsequently, the device cloud responds to request 1 by sending the trust ring device list corresponding to user account 1 to device 1, enabling device 1 to know the latest trust ring device list and refresh the trust ring device list. Furthermore, since the trust ring device list has been refreshed, device 1 considers the devices indicated by the trust ring device list to be reliable. Therefore, device 1 can include these devices in the trust ring, enabling them to come online and conduct business data transmission with them. After the device comes online, the user can access the relevant interface provided by device 1 (see...). Figure 1B ), check the devices in the trust ring where device 1 is located, i.e., the devices that are already online. For example... Figure 1B All devices in the trust ring corresponding to user account 1 shown include mobile phone 10 and tablet computer 11, and mobile phone 10 can be the aforementioned device 1.

[0043] However, refreshing the trust ring device list is a time-consuming operation, such as... Figure 2A As shown, if device 1 is in a weak network environment, the trust ring device list refresh may fail. Device 1 determines that the trust ring device list status is not ready, meaning that information about devices in the trust ring is unreliable. A new device 2 registers with the device cloud agent through device 3 in the trust ring where device 1 is located. After successful agent registration, the device cloud adds device 2's information to the trust ring device list corresponding to the trust ring where device 1 is located, thus enabling device 2 to join the ring. The trust ring where device 1 is located is the trust ring corresponding to user account 1 logged in by device 1. Afterwards, the device cloud sends an agent registration notification message to device 1, which triggers device 1 to add device 2's information to the trust ring device list. However, because device 1's trust ring device list status is not ready, device 1 considers the trust ring device list unreliable. Therefore, device 1 determines that the newly joined device 2 is unreliable, and thus does not include device 2 in the trust ring. Consequently, device 1 cannot transmit business data corresponding to the trust ring service with device 2, such as being unable to transfer device 1's audio data to the headphones, affecting the user experience.

[0044] It should be noted that the above-mentioned power-on is only one possible scenario for triggering device 1 to refresh the trust ring device list; other scenarios are also possible. For example, Bluetooth switching from off to on, or responding to user input triggers, etc.

[0045] Therefore, to address the above problems, this application provides a solution to improve the success rate of newly connected devices coming online in weak network environments. For example... Figure 2B As shown, in a weak network environment, Device 1 fails to refresh the trust ring device list, and Device 1 determines that the trust ring device list status is not ready. Subsequently, Device 2 registers with the device cloud agent through Device 3 in the same trust ring as Device 1 to join the trust ring of Device 1. Then, the device cloud sends an agent registration notification message to Device 1. This agent registration notification message carries information about Device 2.

[0046] After receiving the device agent registration notification message, although the device list status of device 1 is in an inactive state, since the agent registration notification message was sent by the device cloud, the device cloud considers device 2 to be reliable. Therefore, device 1 can also determine that electronic device 2 is reliable and add device 2's information to the weak network device list. The weak network device list includes the device information carried in the agent registration notification message received in a weak network environment, that is, it includes the information of devices that have registered as agents in the trust ring where device 1 is located while device 1 is in an inactive state.

[0047] Subsequently, for each device in the weak network device list, Device 1 can use that information to add the device to its trust ring, enabling the new device to come online. This allows Device 2 to come online, preventing Device 2 from failing to connect due to Device 1 being in a weak network environment. Afterwards, Device 1 can transmit service data corresponding to the trust ring service with Device 2, ensuring the normal operation of the service and thus guaranteeing a good user experience.

[0048] For example, the above-mentioned devices (such as device 1, device 2 and device 3) can be mobile phones, tablets, wearable devices (such as smartwatches), Bluetooth headsets, personal digital assistants (PDAs), laptops, in-vehicle devices, Internet of Things devices and other electronic devices with wireless communication functions. The embodiments of this application do not impose special restrictions on the specific form of the electronic device.

[0049] Figure 3 A schematic diagram of the structure of the electronic device 100 is shown.

[0050] Electronic device 100 may include processor 110, external memory interface 120, internal memory 121, universal serial bus (USB) interface 130, charging management module 140, power management module 141, battery 142, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, button 190, motor 191, indicator 192, camera 193, display screen 194, and subscriber identification module (SIM) card interface 195, etc.

[0051] It is understood that the structures illustrated in the embodiments of the present invention do not constitute a specific limitation on the electronic device 100. In other embodiments of this application, the electronic device 100 may include more or fewer components than illustrated, or combine some components, or split some components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0052] Processor 110 may include one or more processing units, such as: application processor (AP), modem processor, graphics processing unit (GPU), image signal processor (ISP), controller, memory, video codec, digital signal processor (DSP), baseband processor, and / or neural network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0053] The controller can be the nerve center and command center of the electronic device 100. The controller can generate operation control signals according to the instruction opcode and timing signals to complete the control of fetching and executing instructions.

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

[0055] The charging management module 140 receives charging input from the charger. The power management module 141 receives input from the battery 142 and / or the charging management module 140 to power the devices in the electronic device 100.

[0056] The wireless communication function of electronic device 100 can be realized through antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modem processor and baseband processor, etc.

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

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

[0059] The modem processor may include a modulator and a demodulator. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0060] The wireless communication module 160 can provide solutions for wireless communication applications on the electronic device 100, including wireless local area networks (WLAN) (such as Wi-Fi), Bluetooth, Global Navigation Satellite System (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR). 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 antenna 2, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to processor 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0061] In some embodiments, antenna 1 of electronic device 100 is coupled to mobile communication module 150, and antenna 2 is coupled to wireless communication module 160, enabling electronic device 100 to communicate with networks and other devices via wireless communication technology. The wireless communication technology may include Global System for Mobile Communications (GSM), General Packet Radio Service (GPRS), Code Division Multiple Access (CDMA), Wideband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technologies, etc. The GNSS may include the Global Positioning System (GPS), the Global Navigation Satellite System (GLONASS), the BeiDou Navigation Satellite System (BDS), the Quasi-Zenith Satellite System (QZSS), and / or satellite-based augmentation systems (SBAS).

[0062] Electronic device 100 implements display functions through GPU, display screen 194, and application processor.

[0063] The display screen 194 is used to display images, videos, etc. In some embodiments, the electronic device 100 may include one or N display screens 194, where N is a positive integer greater than 1.

[0064] Electronic device 100 can perform shooting functions through ISP, camera 193, video codec, GPU, display 194 and application processor.

[0065] The ISP is used to process data fed back by the camera 193. The camera 193 is used to capture still images or videos. In some embodiments, the electronic device 100 may include one or N cameras 193, where N is a positive integer greater than 1.

[0066] The external storage interface 120 can be used to connect an external storage card, such as a Micro SD card, to expand the storage capacity of the electronic device 100.

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

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

[0069] The sensor module 180 may include pressure sensors, gyroscope sensors, barometric pressure sensors, magnetic sensors, accelerometers, distance sensors, proximity sensors, fingerprint sensors, temperature sensors, touch sensors, ambient light sensors, bone conduction sensors, etc.

[0070] Buttons 190 include a power button, volume buttons, etc. A motor 191 can generate vibration feedback. An indicator 192 can be an indicator light. A SIM card interface 195 is used to connect a SIM card. Electronic device 100 can support one or N SIM card interfaces, where N is a positive integer greater than 1.

[0071] For example, the software system of electronic device 100 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This embodiment of the invention uses the layered architecture Android system as an example to illustrate the software structure of electronic device 100.

[0072] Figure 4 This is a software structure block diagram of the electronic device 100 according to an embodiment of the present invention.

[0073] A layered architecture divides software into several layers, each with a clear role and function. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom: the application layer, the application framework layer, the Android runtime and system libraries, and the kernel layer.

[0074] The application layer can include a series of application packages.

[0075] like Figure 4 As shown, the application package may include applications such as device management services, iconnect services, calling, maps, navigation, WLAN, Bluetooth, music, and video.

[0076] The device management service interacts with the device cloud. For example, it retrieves the list of devices in the trust ring from the device cloud. Or, for instance, after a new device joins the trust ring through agent registration, the device cloud sends a device agent registration notification message to the device management service of electronic device 100 in the trust ring, triggering the device management service to update the information of the devices in the trust ring recorded locally.

[0077] The connectivity service manages the trust ring device list, such as refreshing it via the device management service. Additionally, the connectivity service can manage the weak network device list. The weak network device list includes information about new devices that register through other devices in the trust ring under weak network conditions. Simply put, the information in the weak network device list can be understood as information about devices that electronic device 100 considers unreliable due to trust ring refresh failure caused by a weak network, but which are actually reliable.

[0078] The application framework layer provides application programming interfaces (APIs) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0079] like Figure 4 As shown, the application framework layer may include a window manager, content provider, view system, phone manager, resource manager, notification manager, etc.

[0080] The window manager is used to manage windowed applications. It can retrieve screen size, determine the presence of a status bar, lock the screen, and capture screenshots, among other things.

[0081] Content providers store and retrieve data, making that data accessible to applications. This data may include videos, images, audio, made and received phone calls, browsing history and bookmarks, phone books, etc.

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

[0083] The phone manager is used to provide communication functions for electronic device 100. For example, it manages call status (including connection and disconnection).

[0084] The file explorer provides applications with various resources, such as localized strings, icons, images, layout files, video files, and more.

[0085] The notification manager allows applications to display notifications in the status bar. These notifications can be used to deliver informational messages and can disappear automatically after a short pause, requiring no user interaction. For example, the notification manager can be used to notify users of completed downloads or message alerts. The notification manager can also display notifications as icons or scrolling text in the top status bar, such as notifications from background applications, or as dialog boxes on the screen. Examples include displaying text messages in the status bar, emitting sounds, vibrating electronic devices, and flashing indicator lights.

[0086] The Android Runtime consists of core libraries and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system.

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

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

[0089] System libraries can include multiple functional modules. For example: surface manager, media libraries, 3D graphics processing libraries (e.g., OpenGL ES), 2D graphics engines (e.g., SGL), etc.

[0090] The Surface Manager is used to manage the display subsystem and provides the blending of 2D and 3D layers for multiple applications.

[0091] The media library supports playback and recording of various common audio and video formats, as well as still image files. It supports multiple audio and video encoding formats, such as MPEG4, H.264, MP3, AAC, AMR, JPG, and PNG.

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

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

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

[0095] It is understandable that the above Figure 4 The structure shown is merely an example; electronic devices can be divided into software layers according to their needs. For instance, an electronic device may include not only the software layers described above but also other software layers. Alternatively, an electronic device may include one or more of the software layers described above. Similarly, the content included in each software layer is also merely an example, and this application does not impose any limitations on it.

[0096] Considering that newly added devices are generally those currently used by users, this application provides a service data transmission method to ensure their successful online integration and enable data transmission between devices in the trust ring and the newly added device. In a weak network environment, if device 1 fails to refresh its trust ring device list, device 1 determines that its trust ring device list is in an unready state, meaning it considers the trust ring device list unreliable. In other words, it considers the locally recorded information about devices in the trust ring unreliable, and therefore, device 1 will not bring the devices in the trust ring online.

[0097] Subsequently, Device 1 receives a proxy registration notification message from the Device Cloud. This message indicates that a new Device 2 has registered with the Device Cloud proxy through Device 3, which is already in Device 1's trust ring, to join Device 1's trust ring. In response to the proxy registration notification message, although the trust ring device list is in a pre-ready state, Device 1 considers Device 2 reliable. Therefore, Device 1 can add Device 2 as a device in the trust ring, successfully bringing the device online and enabling Device 1 to interconnect with Device 2 to transmit business data, ensuring normal business operation.

[0098] The following will use an example where device 1 (or the first device) is a mobile phone, device 2 (or the second device) is an earphone, and device 3 is a tablet computer to illustrate the business data transmission method provided in this application. For example, as shown below... Figure 5 As shown, the data transmission method for this service is as follows:

[0099] S201. After the phone is powered on, the connection service in the phone is started.

[0100] S202, Device management service in mobile phones is now online.

[0101] In this embodiment of the application, after the mobile phone has entered the ring, the connection service of the mobile phone is started and the device management service is launched after the mobile phone is powered on, so that the mobile phone can use the connection service and the device management service to perform corresponding business operations.

[0102] Powering on is only one possible scenario for triggering the start of the connection service and the online launch of the device management service. Of course, there are other scenarios as well, such as when Bluetooth is started during power-on, the connection service starts and the device management service goes online.

[0103] S203. The device management service sends request 1 to the device cloud. Request 1 is used to trigger the retrieval of the trust ring device list corresponding to user account 1 logged in on the mobile phone.

[0104] Request 1 (or the first request) may include user account 1 corresponding to the mobile phone, i.e., user account 1 logged in on the mobile phone. Under normal circumstances, the device cloud responds to request 1 by returning the trust ring device list to the mobile phone, thus refreshing the trust ring device list on the mobile phone. This allows the mobile phone to know the devices in the trust ring corresponding to user account 1 and bring those devices online. Understandably, since the devices in the trust ring may change, such as being added or deleted, it is necessary to obtain the latest trust ring device list from the device cloud and refresh the trust ring device list recorded on the mobile phone.

[0105] However, under abnormal circumstances, the phone may experience a failure to refresh the Trust Ring device list. For example, this might occur when the phone is in a weak network environment. The following will explain the relevant details regarding this Trust Ring device list refresh failure.

[0106] S204. After time 1, the device management service did not receive the trusted ring device list sent by the device cloud. The mobile phone was in a weak network environment.

[0107] In this embodiment of the application, due to poor mobile network conditions, the transmission of business data between the device management service and the device cloud may be affected, which may result in the mobile phone still being unable to successfully obtain the trust ring device list corresponding to user account 1 from the device cloud after time 1, thus causing the mobile phone's trust ring device list to fail to refresh.

[0108] S205. The device management service sends notification message 1 to the connection service. Notification message 1 indicates that the trust ring device list status is not ready.

[0109] S206. In response to notification message 1, the connection service does not bring devices in the trust ring online.

[0110] For example, the notification message 1 above may carry deviceListReady status information, which is false, to indicate that the trust ring device list refresh failed.

[0111] In this embodiment, after receiving notification message 1, the connection service determines that the trust ring device list refresh failed and considers the phone's trust ring device list unreliable. That is, the devices in the trust ring determined by the phone are unreliable, and therefore, the devices in the determined trust ring will not be brought online. Accordingly, the relevant interface provided by the phone will not display the devices in the trust ring, as described above. Figure 1B The tablet computer 11 shown.

[0112] While the phone's trust ring device list is in an incomplete state, it's possible for an earphone to register and join the phone's trust ring through a proxy. The proxy registration process will be explained below.

[0113] S207. The headphones send a proxy registration request to the tablet computer.

[0114] The proxy registration request may include headset registration information. This headset registration information may include headset details such as the headset's identifier and key information, such as a public key. However, the headset registration information may also include other information, such as the user account number for tablet login; this application does not restrict its inclusion.

[0115] In this embodiment of the application, after the earphone is paired and connected with the tablet computer, in response to the relevant loop entry trigger operation input by the user, the earphone can send a proxy registration request to the tablet computer to join the trust ring in which the tablet computer is located, that is, to join the trust ring in which the mobile phone is located.

[0116] S208, the tablet computer responds to the agent registration request and registers with the device cloud as an agent.

[0117] In this embodiment, the tablet computer acts as an agent for the earphones and registers them with the device cloud. After receiving the earphone registration information sent by the tablet computer, the device cloud records the earphone information from the earphone registration information into the trusted ring device list corresponding to user account 1. The earphone registration is successful, and the earphones successfully enter the ring.

[0118] Optionally, after the headphones successfully register, the device cloud can return a registration success response message to the tablet to notify the tablet that the headphones have successfully registered. The tablet then responds to this registration success response message by sending a registration success message to the headphones, which includes user account 1. Upon receiving the registration success message, the headphones respond by establishing a session connection with the tablet, enabling interconnection between the tablet and the headphones, thus achieving the headphones' entry into the loop. Based on this, through proxy registration into the loop, devices without a specific type of user account (such as non-Honor accounts) can register with the device cloud on behalf of others, allowing non-Honor account devices (such as headphones) to join the trust loop.

[0119] It should be noted that when the headphones do not require a loop connection, once the headphones are paired and connected to the tablet, the tablet does not need to register as an agent, and the headphones do not support trust loop services, such as audio streaming.

[0120] S209. The device cloud sends an agent registration notification message to the device in the trust ring corresponding to user account 1. The agent registration notification message includes information about the headphones.

[0121] S210: The device management service in the mobile phone receives agent registration notification messages.

[0122] S211. The Device Management Service sends an agent registration notification message to the Connection Service.

[0123] The aforementioned agent registration notification message is used to notify the headphones that they have been registered into the ring through an agent, meaning that the headphones are a new device in the trust ring corresponding to user account 1.

[0124] Based on user habits, generally speaking, once a user adds headphones to the trust loop, there's a high probability they'll use the headphones for trust loop services. Furthermore, users might not only use the aforementioned tablet and headphones for these services, but also other devices within the trust loop, such as the aforementioned mobile phone. Therefore, to ensure a good user experience, the headphones need to be connected to the mobile phone for data transmission. This process will be described below.

[0125] S212. In response to the agent registration notification message, if the trust ring device list status is not ready, the connection service adds the headset information to the weak network device list.

[0126] The weakNetList indicates information about newly added devices to the trust ring corresponding to user account 1 while the trust ring device list is in an inactive state. Optionally, these newly added devices can be registered and joined to the trust ring through a proxy, such as the aforementioned headset. Alternatively, the newly added devices can also be directly registered and joined to the trust ring.

[0127] S213. The connection service integrates the weak network device list and the pairing-free device list to obtain integrated list 1.

[0128] The pairing-free device list includes information on devices that do not require Bluetooth pairing (i.e., pairing-free devices, or Bluetooth-free pairing-free devices). In other words, the phone can directly connect to the devices indicated in this list without prior pairing. The devices in the pairing-free device list do not have trust loop capabilities, meaning trust loop services are not required. Optionally, the information for the devices in the pairing-free device list may include the device's identifier.

[0129] The aforementioned integrated list 1 includes information on devices in the aforementioned weak network device list (or the first device list) and information on devices in the aforementioned pair-free device list (or the second device list).

[0130] S214. For the information of each device in the integrated list 1, the connection service uses the Bluetooth application to identify the device corresponding to the device's information as a paired device.

[0131] For example, the connection service sends Integration List 1 to the Bluetooth application, enabling the Bluetooth application to obtain information about the devices in Integration List 1. Based on this information, the application identifies the devices indicated in Integration List 1 as paired devices, allowing the phone to directly connect to them. For example, for each device in Integration List 1, if the device belongs to the weak network device list, the Bluetooth application can configure it based on the key information within that device's information to designate it as a paired device (or a Bluetooth-paired device). This allows the phone to connect directly via Bluetooth when the device is near it, without needing to obtain pairing information again, thus improving communication efficiency.

[0132] S215. For the information of each device in the weak network device list, the connection service shall treat the device corresponding to the information of that device as a device in the trust ring corresponding to user account 1.

[0133] In this embodiment of the application, since the information of the devices in the weak network device list is the information of newly joined devices, the connection service can bring this device online as a device in the trust ring corresponding to user account 1. Accordingly, as Figure 6 As shown, all devices in the trust ring corresponding to user account 1 include mobile phone 20 and headset 21. However, for other actual devices in the trust ring corresponding to user account 1, such as tablet computer 22, the connection service considers the tablet computer non-existent and does not list it online because the mobile phone fails to refresh the trust ring device list, thus improving security.

[0134] It should be noted that the steps described above for integrating the weak network device list and the pairing-free device list are optional. The connection service can directly treat the devices indicated in the weak network device list as paired devices without updating the Bluetooth of pairing-free devices. Similarly, the step described above for adding the headset information to the weak network device list is also optional; the connection service can directly treat the headset as a paired device.

[0135] Optionally, after a device comes online, the connectivity service can notify the device management service that the device has come online.

[0136] S216. When the earphone is close to the mobile phone, the mobile phone and the earphone transmit the service data corresponding to the trust ring service.

[0137] In this embodiment, when the earphone and the mobile phone are close together, the mobile phone determines that the earphone is connected to the mobile phone, and thus the mobile phone can establish a session connection with the earphone to transmit service data, such as the service data corresponding to the trust ring service, so that the user can use the earphone to perform the trust ring service normally and improve the user experience.

[0138] Optionally, when the earphones and the mobile phone are close together, the mobile phone can authenticate the earphones based on the earphones' information. After successful authentication, the phone can connect with the earphones.

[0139] In some embodiments, the mobile phone can also transmit business data with devices indicated in the list of unpaired devices, allowing users to directly use unpaired devices.

[0140] In some embodiments, the above describes how a mobile phone brings a newly added device (such as the aforementioned headphones) online in the trust ring when the device list status of the mobile phone is not ready, using proxy registration as an example. Of course, proxy registration is only one example of a device registering with the device cloud; a device can also register directly with the device cloud. Correspondingly, the proxy registration notification message described above is only one example of a registration notification message. It should be understood that whether it is proxy registration or direct registration, the process of the mobile phone bringing a newly added device online in the trust ring is similar.

[0141] In some embodiments, if the headset is registered through the phone's agent while the phone is in an unready state, the phone can directly consider the headset reliable and include it as a device in the trust loop without having to add the headset's information to the aforementioned weak network device list.

[0142] In some embodiments, generally speaking, if the mobile phone can normally receive the agent registration message sent by the device cloud, it indicates that the mobile phone's network status has been restored and it is no longer in a weak network environment. At this time, the success rate of refreshing the trust ring device list is relatively high.

[0143] Therefore, the phone can try refreshing the Trust Ring device list again. For example, the refresh attempt process is as follows:

[0144] S217. The connection service sends notification message 2 to the device management service. Notification message 2 indicates that the current trust ring device list is unreliable.

[0145] For example, notification message 2 can be similar to notification message 1 above, indicating that the trust ring device list is in a not ready state.

[0146] S218, The device management service resends request 1 to the device cloud.

[0147] In this embodiment, since network recovery typically takes time, if the device management service immediately refreshes the trust ring device list from the device cloud after a failed refresh, the likelihood of another failure remains high, leading to unnecessary refreshes and increased power consumption on the phone. Therefore, the device management service does not immediately refresh the trust ring device list after a failed refresh. Instead, it refreshes the trust ring device list on the phone again from the device cloud only after receiving notification message 2 (or the first notification message) sent by the connection service after the headset is connected. Since network recovery is more likely at this point, the probability of a successful trust ring device list refresh is higher, avoiding unnecessary refresh operations.

[0148] It should be noted that the above description of the device management service refreshing the trust ring device list again after the headphones are successfully launched is only one example. Other situations can also trigger the device management service to refresh again. For example, after the device management service receives the agent registration notification message sent by the device cloud, it will resend request 1 to the device cloud.

[0149] S219. The device cloud sends the latest list of trusted ring devices to the device management service.

[0150] S220, the device management service refreshes the locally stored list of trust ring devices based on the latest list of trust ring devices.

[0151] S221. The device management service sends notification message 3 to the connection service. Notification message 3 indicates that the trusted ring device list status is ready.

[0152] For example, the notification message 3 mentioned above can carry deviceListReady status information, which is true, to indicate that the trust ring device list has been successfully refreshed.

[0153] S222, The connection service will use the device information in the latest trust ring device list as the device in the trust ring corresponding to user account 1.

[0154] S223. The connection service sends an online notification message to the device management service.

[0155] The online notification message is used to notify devices in the trust ring that they have gone online.

[0156] In this embodiment, after receiving notification message 3, the connection service determines that the trust ring device list has been successfully refreshed and considers the phone's trust ring device list to be reliable. That is, the devices in the trust ring determined by the phone are reliable. Therefore, the connection service can bring the devices in the trust ring online, enabling the phone to transmit service data corresponding to the trust ring service with the devices in the trust ring. Accordingly, the relevant interface provided by the phone can include the devices in the trust ring, such as... Figure 7 The mobile phone 20, earphones 21, and tablet computer 22 are shown.

[0157] In some embodiments, while the device list in the trust ring is in a ready state, if a new device (such as a new headset) registers through the device agent in the trust ring corresponding to user account 1, the device cloud sends an agent registration notification message to the device management service on the mobile phone. Subsequently, the device management service sends an agent registration notification message to the connection service. The relevant content of the agent registration notification message described here can be found in the relevant sections S210-S211 above.

[0158] In response to the agent registration notification message, if the trust ring device list status is ready, the connection service adds the new headset information to the latest trust ring device list and refreshes the latest trust ring device list stored this time.

[0159] Next, the connection service integrates and pairs the cloud device list, resulting in Integration List 2. Integration List 2 represents the list of devices to be synchronized. The devices indicated in the cloud pairing device list represent devices that have already been Bluetooth paired with other devices in the trust ring. This cloud pairing device list can be obtained by the device management service from the device cloud.

[0160] Subsequently, for each device in the integrated list 2, the connectivity service pairs the device based on that information, designating it as a paired device and synchronizing cloud-paired devices. Furthermore, if the device belongs to the trust ring of user account 1, it is brought online. Based on this, the mobile phone can utilize the new headset's trust ring capability to conduct trust ring services with the new headset. Moreover, the mobile phone can directly transmit service data with cloud-paired devices (i.e., devices already paired with other devices in the trust ring), facilitating user experience.

[0161] It is understandable that the steps S217-S223 above are optional. That is, after the phone fails to refresh the trust ring device list, it will not trigger the device management service to try to refresh the trust ring device list again. Instead, it will refresh the trust ring device list again only if the conditions for refreshing the trust ring device list are met, such as the phone being turned on, the Bluetooth application switching from the off state to the on state again, or receiving a user-triggered operation.

[0162] In some embodiments, similar to the preceding text, the above describes, using proxy registration as an example, how a mobile phone can bring a newly added device (such as the aforementioned new headset) online in the trust ring when the device list status of the mobile phone is ready. Of course, proxy registration is only one example of a device registering with the device cloud; a device can also register directly with the device cloud.

[0163] It should be noted that the phone being in a weak network environment is only one possible reason for the failure to refresh the trust ring device list. Other reasons could also be, such as a phone malfunction causing the failure to refresh the trust ring device list.

[0164] Furthermore, the operations performed by the software modules in the aforementioned mobile phone (such as the device management service and connection service) can also be performed by other software modules. This application does not impose any restrictions on the software modules that perform the above steps. In addition, the operations performed by the software modules are actually all performed by the mobile phone; that is, the executing entity of the business data transmission method described in this application is the mobile phone.

[0165] The above primarily describes the solutions provided by the embodiments of this application from a methodological perspective. It is understood that, in order to achieve the above functions, the electronic device includes hardware structures and / or software modules corresponding to the execution of each function. Based on the units and algorithm steps of the various examples described in the embodiments disclosed in this application, the embodiments of this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by a computer driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the technical solutions of the embodiments of this application.

[0166] This application provides embodiments for dividing an electronic device into functional modules based on the above method examples. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into a single processing unit. The integrated unit can be implemented in hardware or as a software functional module. It should be noted that the unit division in this application embodiment is illustrative and represents only one logical functional division; in actual implementation, other division methods may be used.

[0167] like Figure 8 The diagram shown is a structural schematic of an electronic device provided in an embodiment of this application. This electronic device 1000 can be used to implement the methods executed by the electronic devices described in the above method embodiments. For example, the electronic device 1000 may include a processing unit 1001, a communication unit 1002, and a display unit 1003. The processing unit 1001 is used to support the electronic device 1000 in executing... Figures 1A to 7 The electronic device (such as device 1) described in any one of the following embodiments includes a communication unit 1002 for supporting the communication function of the electronic device 1000, and a display unit 1003 for supporting the display function of the electronic device 1000.

[0168] Optional, Figure 8 The illustrated electronic device 1000 may also include a storage unit ( Figure 8 (not shown in the image), this storage unit stores a program or instruction. When the processing unit 1001 executes the program or instruction, it causes... Figure 8 The electronic device 1000 shown can perform the method described in the above-described method embodiments.

[0169] Figure 8 The technical effects of the electronic device 1000 shown can be referred to the technical effects described in the above method embodiments, and will not be repeated here. Figure 8 The processing unit 1001 in the illustrated electronic device 1000 can be implemented by a processor or processor-related circuit components, and can be a processor or processing module. The communication unit 1002 can be implemented by a transceiver or transceiver-related circuit components, and can be a transceiver or transceiver module. The display unit 1003 can be implemented by display screen-related components.

[0170] This application also provides a chip system, such as... Figure 9 As shown, the chip system includes at least one processor 1101 and at least one interface circuit 1102. The processor 1101 and the interface circuit 1102 are interconnected via lines. For example, the interface circuit 1102 can be used to receive signals from other devices. As another example, the interface circuit 1102 can be used to send signals to other devices (e.g., the processor 1101). Exemplarily, the interface circuit 1102 can read instructions stored in memory and send those instructions to the processor 1101. When the instructions are executed by the processor 1101, the electronic device can perform the various steps performed by the electronic device in the above embodiments. Of course, the chip system may also include other discrete components, and this application embodiment does not specifically limit this.

[0171] Optionally, the chip system may contain one or more processors. These processors can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, an integrated circuit, etc. When implemented in software, the processor can be a general-purpose processor, implemented by reading software code stored in memory.

[0172] Optionally, the chip system may contain one or more memories. The memory may be integrated with the processor or disposed separately from it; this application does not limit this. For example, the memory may be a non-transient processor, such as a read-only memory (ROM), which may be integrated with the processor on the same chip or disposed separately on different chips. This application does not specifically limit the type of memory or the arrangement of the memory and processor.

[0173] For example, the chip system may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a micro controller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0174] It should be understood that each step in the above method embodiments can be completed by integrated logic circuits in the processor hardware or by instructions in software form. The method steps disclosed in the embodiments of this application can be directly manifested as being executed by a hardware processor, or being executed by a combination of hardware and software modules in the processor.

[0175] This application also provides a computer storage medium storing computer instructions. When the computer instructions are executed on an electronic device, the electronic device performs the business data transmission method described in the above method embodiments.

[0176] This application provides a computer program product, which includes a computer program or instructions that, when executed on an electronic device, cause the electronic device to perform the business data transmission method described in the above method embodiments.

[0177] In addition, this application embodiment also provides an apparatus, which may specifically be a chip, component, or module. The apparatus may include a connected processor and a memory. The memory stores computer execution instructions. When the apparatus is running, the processor executes the computer execution instructions stored in the memory to cause the apparatus to perform the business data transmission methods described in the above-described method embodiments. The electronic devices, computer storage media, computer program products, or chips provided in this embodiment are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they achieve can be referred to in the beneficial effects of the corresponding methods provided above, and will not be repeated here.

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

[0179] In the several embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. The embodiments can be combined with or referenced to each other without conflict. The apparatus embodiments described above are merely illustrative; for example, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another device, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0180] The units described as separate components may or may not be physically separate. A component shown as a unit can be one or more physical units; that is, it can be located in one place or distributed in multiple different locations. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

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

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

[0183] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for transmitting business data, characterized in that, Applied to a first device, the method includes: Send a first request to the device cloud; wherein, the first request is used to obtain the list of trust ring devices corresponding to the trust ring in which the first device is located; If the trust ring device list is not received after the first period of time, the trust ring device list status of the first device is set to an unready state, and the devices in the trust ring device list are not brought online; the unready state indicates that the trust ring device list refresh failed. While the first device is in an unready state, a registration notification message sent by the device cloud is received; wherein, the registration notification message is used to notify the second device to register and join the trust ring through the third device agent in the trust ring; In response to the registration notification message, the second device is designated as a device in the trust ring; The service data corresponding to the trust ring service transmitted with the second device; and After receiving the registration notification message, the first request is resent to the device cloud to obtain the trust ring device list again.

2. The method according to claim 1, characterized in that, The step of including the second device as a device in the trust ring includes: Add the information of the second device to the first device list; wherein the first device list includes information of all newly added devices in the trust ring while the first device is in a non-ready state; For each device in the first device list, the device corresponding to the device information is taken as a device in the trust ring.

3. The method according to claim 1 or 2, characterized in that, In response to the registration notification message, the method further includes: The second device is designated as a Bluetooth-paired device.

4. The method according to claim 1 or 2, characterized in that, In response to the registration notification message, the method further includes: For each device in the second device list, the device corresponding to the device information is considered a Bluetooth-paired device; the second device list includes information on devices that do not require Bluetooth pairing.

5. The method according to claim 1, characterized in that, Sending the first request to the device cloud includes: The device management service in the first device receives a first notification message sent by the connection service in the first device; the first notification message indicates that the first device is in a not-ready state; In response to the first notification message, the device management service sends a first request to the device cloud.

6. The method according to claim 1 or 2, characterized in that, When the first request is sent to the device cloud, the first device is in a weak network environment.

7. An electronic device, characterized in that, The electronic device includes a memory and one or more processors; the memory and the processors are coupled; the memory is used to store computer program code, the computer program code including computer instructions; when the processor executes the computer instructions, the electronic device performs the business data transmission method as described in any one of claims 1 to 6.

8. A computer-readable storage medium, characterized in that, It includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the business data transmission method as described in any one of claims 1 to 6.

9. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the business data transmission method as described in any one of claims 1 to 6.

Images