A data processing method and electronic device

Abstract

Embodiments of the present application relate to the field of communication, in particular to a data processing method and an electronic device, which can delete residual data of a cloud-side server, such as a service server. The method comprises: receiving first indication information sent by the service server; the first indication information is used to indicate that the service server has deleted a first binding relationship; in response to the first indication information, sending second indication information to the service server, the second indication information is used to instruct the service server to delete a second binding relationship.

Description

TECHNICAL FIELD

[0001] Embodiments of the present application relate to the field of communication, and in particular, to a data processing method and an electronic device. BACKGROUND

[0002] With the development of internet of things (IoT) technology, various IoT devices are widely used in various fields to provide convenience for people's life. A user can add a device card of an IoT device in a first application of an electronic device, such as a smart space application, to facilitate the user to manage the IoT device.

[0003] When adding the device card of the IoT device, the electronic device and the IoT device interact with a server at a cloud side to implement business registration. In a case where the electronic device and the IoT device support multiple businesses, the server at the cloud side saves registration information corresponding to multiple businesses related to the IoT device. When the electronic device no longer controls the IoT device, the registration information saved by the server at the cloud side cannot be deleted, resulting in data residue of the server at the cloud side and waste of storage space of the server at the cloud side. SUMMARY

[0004] Embodiments of the present application provide a data processing method and an electronic device for deleting residue data of a server at a cloud side, such as a business server.

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

[0006] In a first aspect, a data processing method is provided, applied to a first electronic device, the first electronic device having a first binding relationship with a first IoT device, the first binding relationship corresponding to a first business, the first IoT device further having a second binding relationship with at least one second electronic device, the second binding relationship corresponding to a second business, the first business being different from the second business, and the at least one second electronic device including the first electronic device. The method comprises: receiving first indication information sent by a business server; the first indication information being used to indicate that the business server has deleted the first binding relationship; and in response to the first indication information, sending second indication information to the business server, the second indication information being used to instruct the business server to delete the second binding relationship.

[0007] In the present application, after the first electronic device receives the first indication information used to indicate that the business server has deleted the first binding relationship, the first electronic device can actively trigger the business server to delete the second binding relationship between the first IoT device and the at least one second electronic device. In this way, when the electronic device is not using the first IoT device, the first electronic device can actively trigger the business server to delete the residue binding data, thereby avoiding the waste of storage space of the business server.

[0008] In a possible implementation of the first aspect, the first electronic device comprises a first application, the first application being configured to support the first electronic device to perform the first service with the first IoT device; the first electronic device supports the second service and does not support initiating the second service in the first application. Before sending the second indication information to the service server in response to the first indication information, the first electronic device acquires, from the service server, registration information corresponding to the first service, the registration information comprising a plurality of binding relationships between electronic devices and IoT devices, and being configured to indicate that the first service can be performed between the bound electronic devices and IoT devices. The first electronic device determines that the first binding relationship is not included in the registration information. Because the first binding relationship is not included in the registration information, the first electronic device can actively trigger the service server to delete the second binding relationship between the first IoT device and the at least one second electronic device in response to the first indication information. In the case that the first electronic device does not support initiating the second service in the first application, the second electronic device can actively acquire the registration information corresponding to the first service, and trigger the service server to delete the second binding relationship corresponding to the first IoT device based on the registration information corresponding to the first service.

[0009] In a possible implementation of the first aspect, the first electronic device acquires the registration information from the service server in the case that a trigger condition is met; the trigger condition comprises one or more of the following conditions: the first electronic device switches a connected wireless network, the first electronic device logs in a device account again after logging out of the device account, the first electronic device re-enables a collaboration function after disabling the collaboration function, or the first electronic device restarts.

[0010] In the conventional technology, the mobile phone B can acquire the trust circle data from the server in the case that a trigger condition is met. In this solution, the conventional logic is followed, and the mobile phone B can acquire the third data set from the service server in the case that a trigger condition is met. In this way, the development investment can be reduced, and the original execution logic can be avoided from being changed too much.

[0011] In a possible implementation of the first aspect, the first electronic device comprises a first application and a first module; the first application is configured to support the first electronic device to perform the first service with the first IoT device; the first module is configured to support the first electronic device to perform the second service with the first IoT device; the first module acquires the registration information from the service server, and then the first module determines whether the first binding relationship is included in the registration information. For example, the first module can be a trust circle module.

[0012] In a possible implementation of the first aspect, the first electronic device comprises a first application, the first application being configured to support the first electronic device to perform the first service with the first IoT device; the first electronic device supports the second service and supports initiating the second service in the first application.

[0013] In one possible implementation of the first aspect, the first electronic device includes a first application, a first module, and a second module. The first application supports the first electronic device and the first IoT device in performing a first service; the first module supports the first electronic device and the first IoT device in performing a second service; and the second module supports triggering the first electronic device and the IoT device to perform the second service within the first application, i.e., the second module supports initiating the second service within the first application. When the first electronic device supports the second service and supports initiating the second service within the first application, in response to the first instruction information, the first application triggers the first module to send the second instruction information to the service server via the second module.

[0014] In one possible implementation of the first aspect, the first electronic device may display a device management interface, which includes a device card corresponding to the first IoT device to indicate that the first electronic device and the first IoT device have a first binding relationship; receive a first operation to delete the device card; and in response to the first operation, send a request message to the business server to request the business server to delete the first binding relationship.

[0015] In one possible implementation of the first aspect, the third electronic device can display a device management interface, which includes a device card corresponding to the first IoT device, used to indicate that a first binding relationship exists between the first electronic device and the first IoT device; receive a first operation to delete the device card; and in response to the first operation, send a request message to the business server, the request message being used to request the business server to delete the first binding relationship. The third electronic device includes a first application, and the third electronic device supports the first business but does not support a second business.

[0016] In one possible implementation of the first aspect, the first electronic device can further delete the registration information corresponding to the first IoT device and the second service stored in the first electronic device. Optionally, this registration information can be trust ring registration information. This removes residual data in the first electronic device, avoiding waste of storage space. The first electronic device can delete the registration information corresponding to the first IoT device and the second service stored in it upon receiving a first instruction. Alternatively, the first electronic device can delete the registration information corresponding to the first IoT device and the second service stored in it upon sending a request. Alternatively, the first electronic device can receive a third instruction from the service server, indicating that the service server has deleted the second binding relationship between the first electronic device and the first IoT device. Upon receiving the third instruction, the first electronic device deletes the registration information corresponding to the first IoT device and the second service stored in it. The registration information corresponding to the first IoT device and the second service can, for example, be the trust ring registration information of the first IoT device.

[0017] In one possible implementation of the first aspect, the first business is IoT business, and the second business is device collaboration business.

[0018] In one possible implementation of the first aspect, before performing the data processing provided in this application, the following method can be executed to bind the first IoT device to the electronic device. The method includes: receiving a second operation of adding a device card for the first IoT device in a device management interface; responding to the second operation, sending first registration information to the first IoT device, the first registration information being used to trigger the first IoT device to send registration information to a business server to register a first binding relationship between the first IoT device and the second electronic device; and, if it is found that the first binding relationship between the first IoT device and the second electronic device has been successfully registered in the business server, sending second registration information to the business server; the second registration information being used to register a second binding relationship between the first IoT device and the second electronic device in the business server.

[0019] Secondly, a data processing system is provided, including a first electronic device and a business server; the business server includes a first binding relationship between the first electronic device and a first IoT device and a second binding relationship between the first electronic device and the first IoT device, the first binding relationship corresponding to a first service, the first IoT device also having a second binding relationship with at least one second electronic device, the second binding relationship corresponding to a second service, the first service and the second service being different, the at least one second electronic device including the first electronic device; the first electronic device is used to receive a first indication information sent by the business server; the first indication information is used to indicate that the business server has deleted the first binding relationship; in response to the first indication information, the first electronic device sends a second indication information to the business server, the second indication information being used to instruct the business server to delete the second binding relationship.

[0020] In one possible implementation of the second aspect, the first electronic device includes a first application, which supports the first electronic device and the first IoT device to perform a first service; the first electronic device supports a second service but does not support initiating a second service in the first application.

[0021] In one possible implementation of the second aspect, the first electronic device is further configured to obtain registration information from the business server before sending the second instruction information to the business server in response to the first instruction information, provided that a triggering condition is met; the registration information includes multiple sets of binding relationships between electronic devices and IoT devices, used to indicate that the bound electronic devices and IoT devices can realize the first service; and it is determined that the registration information does not include the first binding relationship.

[0022] Thirdly, an electronic device is provided, comprising: a memory and one or more processors; the memory is coupled to the processors; wherein the memory is used to store computer program code, the computer program code including computer instructions; when the computer instructions are executed by the processor, the electronic device performs the method as described in any of the first aspects.

[0023] Fourthly, a chip system is provided that can be applied to an electronic device including memory. The chip system includes one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via lines. The interface circuits are used to receive signals from the aforementioned memory and send the signals to the processors, the signals including computer instructions stored in the memory. When the processor executes the computer instructions, the electronic device performs a method as described in the first aspect and any of its possible design embodiments.

[0024] Fifthly, a computer-readable storage medium is provided, including computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any of the first aspects.

[0025] A sixth aspect is a computer program product comprising a computer program / instructions that, when executed by a processor, implement the steps of any of the methods in the first aspect.

[0026] In understanding, the beneficial effects that the electronic device of any of the possible designs of the third aspect, the chip system of the fourth aspect, the computer-readable storage medium of the fifth aspect, and the computer program product of the sixth aspect can achieve can be referred to the beneficial effects of the first aspect and any of its possible designs, which will not be repeated here. Attached Figure Description

[0027] Figure 1 A schematic diagram of a device management interface provided in an embodiment of this application;

[0028] Figure 2 This is a schematic diagram of another device management interface provided in an embodiment of this application;

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

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

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

[0032] Figure 6This is a schematic diagram illustrating a method for binding an IoT device according to an embodiment of this application;

[0033] Figure 7 This is a schematic diagram of an interface for binding an IoT device, provided as an embodiment of this application.

[0034] Figure 8 A schematic diagram illustrating a data processing method provided in an embodiment of this application;

[0035] Figure 9 A schematic diagram illustrating another data processing method provided in an embodiment of this application;

[0036] Figure 10 This is a schematic diagram of another data processing method provided in an embodiment of this application. Detailed Implementation

[0037] With the development of Internet of Things (IoT) technology, various IoT devices are widely used in various fields, providing convenience for people's lives. These IoT devices can include, for example, security equipment (smart door locks, network cameras, etc.), lighting equipment (smart desk lamps, smart panels, etc.), audio and video equipment (large screens, smart speakers, Bluetooth headsets, smart glasses, etc.), and smart home appliances (air conditioners, refrigerators, washing machines, etc.).

[0038] Electronic devices can manage and control IoT devices. These electronic devices can be control terminals. They include control applications for managing IoT devices, such as smart space applications. The electronic device can add device cards for IoT devices to the control application, and these device cards can be displayed on the application's interface. When an IoT device is online, the electronic device can respond to user actions, such as actions on the device card, and control the IoT device to execute corresponding control commands. For example, the electronic device can control IoT devices such as turning a large screen on and off, adjusting volume, and changing channels.

[0039] Taking a mobile phone as an example and smart space applications as control applications, such as... Figure 1As shown, the mobile phone displays the main interface, which includes an application icon 101 corresponding to the Smart Space application. In response to the user's operation on the application icon 101, the mobile phone displays the Smart Space application interface 102. Interface 102 includes device cards for IoT devices already added to the mobile phone, such as device card 103 for headphones and device card 104 for speakers. The process of adding an IoT device includes: the mobile phone discovering the IoT device, and the mobile phone and IoT device binding. Binding includes the mobile phone instructing the IoT device to register with the cloud server. After successful IoT registration, the mobile phone has the authority to manage the IoT device. The mobile phone instructing the IoT device to register includes: the mobile phone sending an instruction message to the IoT device, instructing it to register. The IoT device responds to this instruction message by interacting with the cloud server to complete the registration. After successful registration, the cloud server can save the binding relationship between the IoT device and the mobile phone.

[0040] In some embodiments, the electronic device includes a trust ring module that supports device collaboration between the electronic device and other electronic devices. This device collaboration can include various collaborative services such as application continuation, screen sharing, call sharing, notification sharing, keyboard and mouse sharing, camera sharing, and network sharing. For example, if the IoT device is a large screen, electronic devices such as mobile phones can project their screens onto the large screen. Figure 2 As shown, after the device card 202 of the large screen is added to the interface 201 of the smart space application, in response to the user's operation on the card, such as a click operation, the mobile phone displays the interface 203, which includes a screen mirroring option 204. In response to the user's operation on this option, the mobile phone mirrors the screen onto the large screen.

[0041] Optionally, electronic devices and IoT devices can be electronic devices within the same trust ring. Electronic devices and IoT devices can establish a trust relationship through trusted authentication, forming a trust ring. There are several ways for electronic devices and IoT devices to form a trust ring. For example, electronic devices and IoT devices can log into the same account, and multiple electronic devices under the same account can trust each other, forming a trust ring. Another example is that electronic devices and IoT devices may not log into the same account, but they can establish a trust relationship through trusted authentication via a protocol, forming a trust ring, etc. For instance, such as... Figure 3 As shown, mobile phones, smartwatches, tablets, large screens, and personal computers (PCs) form a trust ring by logging into the same account.

[0042] In electronic device control applications such as smart space applications that support device collaboration, in response to a user adding an IoT device, the mobile phone can be bound to that IoT device twice: once for IoT services (IoT binding) and once for trust ring binding (trust ring binding). Trust ring binding involves the IoT device interacting with the cloud server to register a trust ring. After the IoT device completes trust ring registration, the cloud server stores the binding relationship between the IoT device and the mobile phone.

[0043] When adding a device card for an IoT device to a control application, the IoT device needs to be bound twice. In this way, the cloud server will save two binding relationships: one binding relationship corresponding to the IoT business and the other binding relationship corresponding to the trust ring.

[0044] In other words, when an electronic device and an IoT device support multiple services, the cloud-side server stores registration information corresponding to these multiple services. When the electronic device no longer controls the IoT device, the registration information stored on the cloud-side server cannot be deleted, resulting in data residue on the cloud-side server and wasting its storage space.

[0045] Therefore, embodiments of this application provide a data processing method and an electronic device that can delete the binding relationship of electronic devices in a cloud server and avoid data residue.

[0046] The method provided in this application can be applied to electronic devices with data processing capabilities. These electronic devices may include mobile phones, tablets, laptops, netbooks, personal digital assistants (PDAs), wearable devices (e.g., smartwatches, smart bracelets), in-vehicle devices, virtual reality devices, etc., and this application does not impose any limitations on them. In this application, the aforementioned electronic devices are those capable of running an operating system and installing applications. Optionally, the operating system running on the electronic device may be... system, system, Systems, etc.

[0047] Take a mobile phone as an example. Figure 4 As shown, the electronic device 400 may include: a processor 410, a memory 420, a universal serial bus (USB) interface 430, a power management module 440, antennas such as antenna 1 and antenna 2, a communication module 450, a display screen 460, an audio module 470, a camera 480, a sensor module 490, etc.

[0048] Processor 410 may include one or more processing units, such as application processors (APs), central processing units (CPUs), modem processors, graphics processing units (GPUs), ISPs, controllers, memory, video codecs, digital signal processors (DSPs), baseband processors, and / or neural network processing units (NPUs). Different processing units may be independent devices or integrated into one or more processors. The controller may serve as the central nervous system and command center of the electronic device 400. The controller can generate operation control signals based on instruction opcodes and timing signals to control instruction fetching and execution.

[0049] In this embodiment of the application, processor 410,

[0050] The memory 420 can be used to store computer executable program code, which includes instructions. The processor 410 executes various functional applications and data processing of the electronic device by running the instructions stored in the memory 420. The memory 420 may include a program storage area and a data storage area. The program storage area may store the operating system and at least one application program required for a function (such as sound playback, interface display, etc.). The data storage area may store data created during the use of the electronic device (such as notification messages). Furthermore, the memory 420 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.

[0051] In this embodiment, the memory 420 stores computer-executable program code, which includes instructions. The processor 410 executes an image processing method provided in this embodiment by running the instructions stored in the memory 420.

[0052] The power management module 440 is used to connect the battery to the processor 410. The power management module 440 receives battery and / or power input to power the processor 410, memory 420, communication module 450, display screen 460, and camera 480, etc. The power management module 440 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage current, impedance). In some other embodiments, the power management module 440 may also be located within the processor 410.

[0053] The communication module 450 can provide solutions for wireless communication applications on the electronic device 400, including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), and infrared (IR). The communication module 450 can be one or more devices integrating at least one communication processing module. The communication module 450 receives electromagnetic waves via an antenna, performs frequency modulation and filtering of the electromagnetic wave signal, and sends the processed signal to the processor 410. The communication module 450 can also receive signals to be transmitted from the processor 410, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via the antenna.

[0054] In some embodiments, the antenna of the electronic device 400 is coupled to the communication module 450, enabling the electronic device 400 to communicate with networks and other devices via wireless communication technologies. The wireless communication technologies 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, Global Navigation Satellite System (GNSS), WLAN, NFC, FM, and / or IR technologies. The GNSS may include Global Positioning System (GPS), BeiDou Navigation Satellite System (BDS), GLONASS, and / or Galileo.

[0055] Electronic device 400 implements display functions through a GPU, a display screen 460, and an application processor. The GPU is a microprocessor for image processing, connecting the display screen 460 and the application processor. The GPU is used to perform mathematical and geometric calculations and for graphics rendering. Processor 410 may include one or more GPUs, which execute program instructions to generate or modify display information.

[0056] Display screen 460 is used to display images, videos, etc. Display screen 460 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 (AMOLED), a flexible light-emitting diode (FLED), a Mini-LED, a Micro-OLED, a quantum dot light-emitting diode (QLED), etc.

[0057] Electronic device 400 can achieve shooting and recording functions through ISP, camera 480, video codec, GPU, display 460 and application processor.

[0058] The audio module 470 is used to convert digital audio information into analog audio signal output, and also to convert analog audio input into digital audio signal. The audio module 470 can also be used for encoding and decoding audio signals. In some embodiments, the audio module 470 may be located in the processor 410, or some functional modules of the audio module 470 may be located in the processor 410.

[0059] The camera 480 is used to capture still images or videos. An object passes through the lens, generating an optical image that is projected onto a photosensitive element. This 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, which is then passed to an ISP (Image Signal Processor) for conversion into a digital image signal. The ISP outputs the digital image signal to a DSP (Digital Signal Processor) for further processing. The DSP converts the digital image signal into standard image signals in formats such as RGB and YUV.

[0060] The sensor module 490 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, and bone conduction sensors, etc.

[0061] It is understood that the structure illustrated in this embodiment does not constitute a specific limitation on the electronic device 400. In other embodiments, the electronic device 400 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.

[0062] Taking the aforementioned electronic device 400 as an example, which is a mobile phone, the software system of the electronic device 400 can adopt a layered architecture, event-driven architecture, microkernel architecture, microservice architecture, or cloud architecture. This application embodiment uses a layered architecture. Taking the system as an example, the software structure of electronic device 400 is illustrated.

[0063] Figure 5 This is a software structure block diagram of the electronic device 400 according to an embodiment of this application.

[0064] 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 system libraries, and the kernel layer.

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

[0066] like Figure 5 As shown, the application package may include a first application, as well as applications such as gallery, call, map, navigation, WLAN, Bluetooth, music, video, SMS, and social networking. The first application may be a control application, such as a smart space application. Optionally, the application package may also include a second application, which may be a collaborative application, such as a trust ring application.

[0067] 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.

[0068] like Figure 5 As shown, the application framework layer may include a content provider, a view system, a resource manager, a notification manager, an input system, a first module, a networking module, etc.

[0069] The input system is used to monitor the phone's input modules (such as touchscreen drivers) and convert the parameters input by the input modules into usable events, which are then passed to the relevant upper-layer modules. For example, the input system is used to monitor the phone's touchscreen through the touchscreen driver and convert the touch parameters generated by the touchscreen input into usable events, which are then passed to the upper-layer APP.

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

[0071] A view system includes visual controls, such as controls for displaying text and controls for displaying images. View systems can be used to build the display interface of an application.

[0072] The notification manager allows applications to display notification information in the status bar. It can be used to convey informational messages and can disappear automatically after a short time without user interaction.

[0073] The first module supports device collaboration services for electronic devices 400. This first module can be a collaboration module, such as a trust ring module. The networking module is used to implement device connection, authentication, and other events.

[0074] Optionally, the application framework layer may also include a second module. This second module can be used to support device collaboration functionality within the first application. The second module manages both the first application and the first module.

[0075] 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.

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

[0077] 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.

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

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

[0080] The kernel layer is the layer between hardware and software. The kernel layer can contain touchscreen drivers, display drivers, camera drivers, sensor drivers, etc.

[0081] This application embodiment includes multiple electronic devices and a first IoT device. The multiple electronic devices can be control terminals for managing the first IoT device. Each of the multiple electronic devices includes a control application, such as a smart space application, for managing the first IoT device. The multiple devices support a first service, such as an IoT service. The multiple electronic devices may include a first device and a second device.

[0082] The first device supports not only IoT services but also device collaboration services such as trust ring services. The first device may include a trust ring module, which supports device collaboration services for electronic devices. The first device may include electronic device 1 and electronic device 2. Electronic device 1's smart space application supports collaboration services. Electronic device 2's smart space application does not support collaboration services. Electronic device 1 supports device collaboration services and can initiate device collaboration services within its smart space application. Electronic device 2 supports device collaboration services and can initiate device collaboration services within its smart space application.

[0083] The second device is an electronic device that does not support device collaboration services. The second device may not include a trust ring module. The second device may include electronic device 3.

[0084] Electronic device 1 and electronic device 2 can be electronic devices within the same trust ring. For example, electronic device 1 and electronic device 2 can log in to the same device account, and with device collaboration and wireless communication functions enabled, both electronic device 1 and electronic device 2 can apply to join the trust ring of the logged-in device account. For instance, when interacting with a cloud-side server, they can apply to join the trust ring of the logged-in device account. Optionally, if the first device includes a device not logged into a device account, such as electronic device 2, after a logged-in device, such as electronic device 1, joins the trust ring of the logged-in device account, it can add devices not logged into a device account, such as electronic device 2, to the same trust ring. This can be referenced from existing technologies and will not be elaborated further. When the wireless communication function of the first IoT device is enabled, electronic device 1 can add the first IoT device to its trust ring while adding the device card of the first IoT device. Enabling the wireless communication function refers to enabling the WLAN and / or Bluetooth functions.

[0085] The following example uses mobile phone A as electronic device 1, mobile phone B as electronic device 2, mobile phone C as electronic device 3, and a large screen as the first IoT device to introduce a data processing method and electronic device provided in this application. First, let's combine... Figure 6 This application provides a method for binding an IoT device. Figure 6 The introduction will take the control application as an example of smart space application. Figure 6In this system, mobile phone A establishes a wireless communication connection with the large screen, and both mobile phone A and the large screen are within the same trust ring. This wireless communication connection can be a Wi-Fi connection or a Bluetooth connection. Optionally, mobile phone A and the large screen establish a Wi-Fi connection, for example, by accessing the same wireless local area network. Mobile phone A includes a first application such as a smart space application, a second module such as a preset module, a first module such as a trust ring module, and a networking module. The large screen includes a first application such as a smart space application, a second module such as a preset module (not shown in the figure), a first module such as a trust ring module, and a networking module. The second module, such as the preset module, is used to associate the first application such as the smart space application and the first module such as the trust ring module. The networking module is used to handle device connection, authentication, and other events. Optionally, mobile phone A and the large screen may also include a collaborative application such as a trust ring application (not shown in the figure).

[0086] The following section uses the smart space application as the first application, the trust ring module as the first module, and the preset module as the second module to introduce this solution.

[0087] For example, the method may include:

[0088] S601, in response to the second operation of adding a device card to the large screen, the Smart Space application of mobile phone A sends the first registration information to the networking module of the large screen.

[0089] The initial registration information is used to instruct the large screen to register for IoT (Internet of Things) services. Only after successful IoT registration can mobile phone A control the large screen. Specifically, the initial registration information triggers the large screen to send registration information to the business server to establish the initial binding relationship between the large screen and mobile phone A. This registration information can be, for example, IoT registration information.

[0090] Before executing S601, mobile phone A can display a device management interface. This device management interface can be, for example, as follows: Figure 1 As shown in interface 102. Specifically, this second operation can be adding a device card for the large screen in the device management interface.

[0091] Optionally, in response to the operation of adding a device card to the large screen, mobile phone A can exchange device information with the large screen. During this exchange, mobile phone A can obtain the large screen's IoT registration information and trust ring registration information. Then, the smart space application on mobile phone A can query the business server to see if it stores the large screen's IoT registration information. If the business server stores the large screen's IoT registration information, mobile phone A's smart space application can execute S604; if the business server does not store the large screen's IoT registration information, mobile phone A's smart space application can execute S601. If the large screen has completed IoT registration, the business server stores the large screen's IoT registration information. If the large screen has not completed IoT registration, the business server does not store the large screen's IoT registration information. The IoT registration information can be the device information used by the large screen to register for IoT. The IoT registration information includes a first device identifier. Optionally, the IoT registration information may also include one or more of the following: name, brand information, manufacturer information, media access control address (MAC), product serial number (SN), certificate information, and the account logged into by mobile phone A's smart space application. For example, the account logged into the Smart Space application on mobile phone A can be the first account, such as account B.

[0092] This application does not limit the specific form of adding a device card to a large screen. As an example, mobile phone A displays as follows: Figure 7 The main interface of the smart space application shown is interface 01. Interface 01 includes device cards for IoT devices already added to mobile phone A, such as device cards for headphones and speakers. Interface 01 includes controls 02, such as an add button. In response to user actions on control 02, such as a click, mobile phone A displays interface 03 of the smart space application. Interface 03 can be a device search interface. Simultaneously, mobile phone A can search for and discover nearby IoT devices. After finding nearby IoT devices, mobile phone A can display interface 04, which includes information about the nearby IoT devices found by mobile phone A. Figure 7 As shown, this information includes device names such as desk lamps and large screens, as well as the corresponding model numbers of IoT devices such as abc and edf. In response to user actions on the large screen, such as tapping or long-pressing, the phone can perform... Figure 6 This illustrates a method for adding IoT devices, and displays device cards for the large screen on the main interface of the smart space application, as shown in Interface 01, and as shown in Interface 05. In some embodiments, users can add the large screen manually or by scanning a QR code.

[0093] S602, in response to the first registration information, the networking module of the large screen sends the first request to the business server.

[0094] The first request is used to request IoT registration, i.e., registering the IoT device. IoT registration connects the IoT device to the IoT platform. After the IoT device is connected to the IoT platform, a control terminal, such as mobile phone A, can control the IoT device. The IoT platform refers to a software platform used to connect, manage, and control IoT devices, and this platform can be deployed on a second server. The business server and the second server can be the same server, or they can be different servers. Mobile phone A can send control commands to the IoT device through the IoT platform. The IoT device can send feedback information to mobile phone A through the IoT platform to indicate the execution status of the commands.

[0095] The first request may include the IoT registration information for the large screen. In some embodiments, before the IoT device, such as the large screen, leaves the factory, a certificate information for the IoT device has already been created on the IoT platform. This certificate information can be burned into the firmware of the IoT device. The certificate information may include the device name and device key. Therefore, IoT registration is specifically used for authentication. For example, the IoT platform can verify the IoT device based on the certificate information in the first request, and after successful verification, control the IoT device to perform corresponding actions based on control commands from mobile phone A.

[0096] S603, in response to the first request, the business server registers the large screen for IoT.

[0097] When the IoT platform is deployed on the business server, the business server can authenticate the large screen in response to the first request. When the IoT platform is not deployed on the business server, the business server forwards the first request to a server where the IoT platform is deployed, such as a second server. The second server then authenticates the large screen based on the first request. The second server can then forward the authentication result to the business server.

[0098] After the large screen's authentication is successful, the business server can save the large screen's IoT registration information. For example, the business server can save the large screen's IoT registration information in a first dataset. The first dataset includes the binding relationship between electronic devices such as mobile phone A and the large screen. For example, the business server stores the device information of mobile phone A and the large screen's IoT registration information in the first dataset, thus binding mobile phone A to the large screen, establishing a first binding relationship between them. In some embodiments, the first dataset includes a first account, device information of the control terminal (such as mobile phone A) logged into the first account, and IoT registration information of the IoT device (such as the large screen) bound to the control terminal. Furthermore, the first account can correspond to multiple control terminals, and the first account can correspond to the IoT registration information of multiple IoT devices. When multiple control terminals' smart space applications are all logged into the first account, multiple electronic devices can control each of the multiple IoT devices corresponding to the first account.

[0099] After the identity verification on the large screen is successful, the business server can send the first message to the large screen, which is used to inform the large screen that the IoT registration has been completed.

[0100] For example, the first dataset can be a data table. Taking IoT registration information, which includes device identifiers and serial numbers, as an example, this data table can be as shown in Table 1.

[0101] Table 1

[0102] First account Control terminal IoT device 152******46 Device identifier-SN of the mobile phone A First device identifier-SN of the large screen

[0103] In this way, the business server can bind mobile phone A to the large screen, that is, mobile phone A and the large screen have a binding relationship, such as the first binding relationship. The first dataset indicates that mobile phone A can control the large screen.

[0104] S604, the Smart Space application on mobile phone A found that the business server stored the IoT registration information of the large screen, and the Smart Space application on mobile phone A added the device card of the large screen on the first interface.

[0105] The Smart Space application on phone A retrieves the IoT registration information for the large screen from the business server. Phone A then adds the large screen's device card to the first screen of the Smart Space application. Simultaneously, the Smart Space application on phone A saves the large screen's IoT registration information. The first screen is the device management interface.

[0106] Because the Smart Space application on mobile phone A supports device collaboration, after adding a device card for the large screen, and if the large screen is already in the trust ring of mobile phone A, the mobile phone can perform device collaboration with the large screen in response to the user's collaborative operation. If the large screen is not in the trust ring of mobile phone A, mobile phone A can add the large screen to its trust ring. For example, mobile phone A can execute steps S605-S610 to add the large screen to its trust ring.

[0107] S605, the Smart Space application of mobile phone A triggers the trust ring module of mobile phone A to initiate device authentication.

[0108] Since the Smart Space application and the Trust Ring module are two different applications, mobile phone A can use a preset module to associate the Smart Space application and the Trust Ring module. For example, the Smart Space application can use the preset module to trigger the Trust Ring module to execute the business logic corresponding to the collaborative service. This business logic might include, for example, device authentication, initiating a collaborative service, or obtaining collaborative data. In some implementations, the preset module can be a preset interface. In other embodiments, the preset module can be a preset application, which can be an Android application package (APK).

[0109] S606, the trust ring module of mobile phone A triggers mutual authentication between the networking module of mobile phone A and the networking module of the large screen.

[0110] Mutual authentication is used to verify the identity of peer devices. The mutual authentication process may include: the networking module of mobile phone A sends authentication information 1 to the networking module of the large screen, and the networking module of the large screen verifies mobile phone A based on authentication information 1. The networking module of the large screen sends authentication information 2 to the networking module 1 of mobile phone A, and the networking module of mobile phone A verifies the large screen based on authentication information 2. The authentication messages (authentication message 1 and authentication message 2) may include device information. The authentication process can refer to existing technologies, and this application embodiment does not impose specific limitations on it.

[0111] S607: After mutual authentication is successful, the networking module of mobile phone A reports the large screen to the trust ring module of mobile phone A, and the networking module of the large screen reports the large screen to the trust ring module of the large screen.

[0112] Afterwards, mobile phone A can identify whether the large screen has joined the trust ring to which mobile phone A belongs. For example, the networking module of mobile phone A can query the service server to see if there is trust ring registration information for the large screen. This trust ring registration information may include, for example, a second device identifier. The trust ring registration information may also include one or more of the following: name, brand information, manufacturer information, MAC address, SN information, certificate information, and the device account that mobile phone A is logged into. The device account that mobile phone A is logged into may be, for example, a second account, which may be account A. The first account and the second account may be the same or different.

[0113] The trust ring module in the large screen can report the online status of mobile phone A to the smart space application through a preset module. The trust ring module in mobile phone A can also report the online status of the large screen to the smart space application through a preset module.

[0114] If the business server has trust ring registration information for the large screen, mobile phone A recognizes that the large screen has joined the trust ring to which mobile phone A belongs. In this case, the mobile phone does not need to execute S608. If the business server does not have trust ring registration information for the large screen, mobile phone A recognizes that the large screen has not joined the trust ring to which mobile phone A belongs. In this case, the mobile phone can execute S608-S610.

[0115] Specifically, when both mobile phone A and the large screen are logged into the same account (e.g., account A), both the large screen and mobile phone A can request to join the trust ring of the logged-in account from the server. In this way, mobile phone A and the large screen can be electronic devices within the same trust ring. Taking mobile phone A as an example, when mobile phone A is logged into its account and its device collaboration function is enabled, upon first launching a device collaboration application such as the trust ring module, mobile phone A can send a request to the server to join the trust ring corresponding to the account it is logged into. This request can include the account information of mobile phone A, the device information of mobile phone A, etc. In response to this request, the server can add mobile phone A to the trust ring corresponding to the account it is logged into. Similarly, when the large screen is logged into its account and its device collaboration function is enabled, upon first launching a device collaboration application such as the trust ring module, the large screen can also execute the same logic method as mobile phone A to join the trust ring corresponding to the account it is logged into. Thus, mobile phone A and the large screen can be electronic devices within the same trust ring.

[0116] This application embodiment uses the example of mobile phone A logging into an account while the large screen does not. When mobile phone A is logged into an account, but the large screen is not, and the large screen is not joined to the trust ring of the mobile phone, mobile phone A can request the server to add the large screen to the trust ring of the account logged into by mobile phone A. Specifically, mobile phone A can execute S608.

[0117] S608, the Smart Space application of mobile phone A triggers the trust ring module to send the second registration information to the business server.

[0118] The second registration information is used to add the large screen to the trust ring corresponding to the account logged in by mobile phone A. Specifically, the second registration information is used to register a second binding relationship between the large screen and mobile phone A in the business server. The second registration information includes the trust ring registration information of the large screen.

[0119] In response to the second registration information, the server can add the large screen to the trust ring corresponding to the account logged in by mobile phone A. In this way, mobile phone A and the large screen can be electronic devices within the same trust ring, and have a second binding relationship.

[0120] S609, in response to the second registration information, the business server performs trust ring registration for the large screen.

[0121] After the server adds the large screen to the trust ring of mobile phone A, the business server saves the large screen's trust ring registration information. For example, the business server can save the large screen's trust ring registration information in a second dataset. The second dataset includes the large screen's trust ring registration information and the device information of electronic devices such as mobile phone A that are in the same trust ring as the large screen. By storing the device information of mobile phone A and the trust ring registration information of the large screen in the second dataset, the business server can bind mobile phone A to the large screen, thus establishing a second binding relationship between them.

[0122] Both the first and second datasets include information from the dashboard, such as trust ring registration information and IoT registration information. Thus, the server in the first dataset stores two records from the dashboard: trust ring registration information and IoT registration information.

[0123] For example, the second dataset can be a data table. Taking the trust ring registration information, which includes device identifiers and serial numbers, as an example, this data table can be as shown in Table 2.

[0124] Table 2

[0125]

[0126] The information included in the IoT registration information and the trust ring registration information may be the same or different, and this application embodiment does not specifically limit this. In some embodiments, the first device identifier and the second device identifier may be a unique device identifier (UDID). Optionally, the first UDID in the IoT registration information and the second UDID in the trust ring registration information may be different. This is because, during the development phase, different UDIDs are configured for IoT devices according to different business types. For example, developers configure a first UDID for IoT devices that support IoT services. Developers configure a second UDID for IoT devices that support collaborative services. Then, a large screen that supports both IoT services and collaborative services has two different UDIDs. When the large screen registers for IoT, the first request information needs to carry the first UDID corresponding to the IoT service. When the large screen registers for the trust ring, the second registration information needs to carry the second UDID corresponding to the collaborative service. In some embodiments, the first UDID may be, for example, IYXO, and the second UDID may be JI88.

[0127] In some embodiments, before the trust ring module of mobile phone A sends the second registration information to the service server, the trust ring module may first send application information to the service server. This application information is used to apply for a trust ring identifier for the large screen. The trust ring identifier is used to uniquely identify an electronic device within the trust ring. Afterwards, the trust ring module of mobile phone A and the trust ring module of the large screen exchange information; for example, they may exchange their respective trust ring identifiers and their respective second UDIDs. After the information exchange is completed, the trust ring module in mobile phone A can send the second registration information to the service server. In this embodiment, the second registration information may also include the trust ring identifier of the large screen.

[0128] S610, the service server sends the second information to the trust ring module of mobile phone A.

[0129] This second piece of information is used to indicate that the large screen has completed the trust ring registration.

[0130] S611, the trust ring module of mobile phone A sends a second message to the smart space application of mobile phone A.

[0131] Upon receiving this second message, the Smart Space application on phone A can respond to the user's collaborative operations within the Smart Space application and perform device collaboration with the large screen. Furthermore, the Smart Space application on phone A can save the large screen's trust ring registration information.

[0132] S612, the business server sends the second information to the trust ring module of the large screen.

[0133] This second piece of information is used to indicate that the large screen has completed the trust ring registration.

[0134] After receiving the second message, the large screen can respond to the user's collaborative operation and perform device collaboration with mobile phone A.

[0135] As can be seen, during the process of adding the device card of the large screen to mobile phone A, the business server binds mobile phone A and the large screen twice. The business server saves two records for large screen A, such as IoT registration information and trust ring registration information. Mobile phone A saves two sets of device information for the large screen, such as IoT registration information and trust ring registration information.

[0136] Figure 6 The diagram illustrates the initial IoT registration and trust ring registration process for the large screen. Once the large screen has completed IoT and trust ring registration, mobile phone A can add a device card for the large screen using the following method: In response to the user's action of adding a device card for the large screen on mobile phone A, the smart space application on mobile phone A queries the large screen's IoT registration information in the first dataset of the business server. If the IoT registration information is found, mobile phone A adds the large screen's device card in the smart space application. Furthermore, mobile phone A can save the large screen's IoT registration information. Next, the smart space application on mobile phone A triggers mutual authentication between the trust ring module and the large screen through a preset module. After successful mutual authentication, mobile phone A then queries the large screen's trust ring registration information in the second dataset of the business server. If the trust ring registration information is found, mobile phone A can save the large screen's trust ring registration information.

[0137] After adding the large screen device card to the Smart Space of phone A, you can add the large screen device card to the Smart Space of phones B and C. That is, you can bind phone B to the large screen, and phone C to the large screen. The details are explained below.

[0138] The first method involves a mobile phone (Phone B) including a trust ring module. Phone B also includes a smart space application and a networking module. Phone B logs in to an account such as account A. The binding process can be as follows: Phone B establishes a wireless communication connection with the large screen, and both Phone B and the large screen are within the same trust ring. This wireless communication connection can be a Wi-Fi connection or a Bluetooth connection. Optionally, Phone B and the large screen establish a Wi-Fi connection, for example, by connecting to the same wireless local area network. In response to the user adding a device card for the large screen on Phone B, the smart space application on Phone B queries the IoT registration information of the large screen from the business server. The user's operation of adding a device card for the large screen on Phone B is similar to that of adding a device card for the large screen on Phone A, and will not be repeated here; please refer to the previous description. Upon finding the IoT registration information for the large screen, Phone B adds the device card for the large screen in the smart space application. Furthermore, the smart space application on Phone B can save the IoT registration information of the large screen. Because Phone B includes a trust ring module, with the collaboration function of Phone B enabled, Phone B and the large screen can authenticate each other. For example, the networking module in mobile phone B can mutually authenticate with the networking module of the large screen. The mutual authentication between mobile phone B and the large screen is similar to that between mobile phone A and the large screen, and will not be elaborated here. After successful authentication, the trust ring module of mobile phone B can obtain the device information of the electronic devices within the trust ring corresponding to account A from the business server. Mobile phone A and mobile phone B can be in the trust ring corresponding to account A, i.e., mobile phone B is in the second dataset. The method for adding mobile phone B to the second dataset can refer to existing trust ring networking technologies, and will not be elaborated here. When the electronic devices within the trust ring corresponding to account A include the large screen, the trust ring module of mobile phone B indicates that the large screen is online. Furthermore, the trust ring module of mobile phone B can store the trust ring registration information of the large screen. In this way, mobile phone B can have both a first binding relationship and a second binding relationship with the large screen.

[0139] The second scenario involves a mobile phone (C) that does not include a trust ring module. Mobile phone C includes a smart space application. The binding process may include: establishing a wireless communication connection between mobile phone C and the large screen, which can be a Wi-Fi connection or a Bluetooth connection. Optionally, mobile phone C and the large screen establish a Wi-Fi connection, for example, by connecting to the same Wi-Fi network. In response to the user adding a device card for the large screen on mobile phone C, the smart space application on mobile phone C queries the IoT registration information of the large screen from the business server. The user's operation of adding a device card for the large screen on mobile phone C is similar to that of adding a device card for the large screen on mobile phone A, and will not be repeated here; please refer to the previous description. Upon finding the IoT registration information for the large screen, mobile phone C adds the device card for the large screen in the smart space application. Furthermore, mobile phone C, as the smart space application can, can save the trust ring registration information of the large screen. Thus, mobile phone C can have a first binding relationship with the large screen, but not a second binding relationship.

[0140] In the above embodiment, mobile phone B and the smart space application of the mobile phone can log in to account B and interact with the business server. The business server can add the device information of mobile phone B and mobile phone C to the first dataset.

[0141] After binding mobile phone B and mobile phone C, the first dataset can be shown in Table 3.

[0142] Table 3

[0143]

[0144] The second dataset contains the binding relationships between multiple electronic devices, such as mobile phones A, B, and C, and IoT devices, such as a large screen, indicating that the bound electronic devices and IoT devices can perform a first service. Optionally, the first dataset also includes IoT registration information of other IoT devices that have a second binding relationship with mobile phones A-C. In other words, the first dataset includes binding relationships between multiple electronic devices, such as mobile phones A-C, and at least one IoT device, indicating that the bound electronic devices and IoT devices can perform IoT services. The large screen is one of the at least one IoT device.

[0145] After binding mobile phones B and C, the second dataset can be as shown in Table 4. The second dataset contains the binding relationships between multiple electronic devices such as mobile phones A and B and IoT devices such as large screens, which are used to indicate that the bound electronic devices and IoT devices can realize the second service.

[0146] Table 4

[0147]

[0148] Figure 6 The process of binding an electronic device to a large screen was introduced. Below, with reference to the accompanying drawings, a data processing method provided by an embodiment of this application is described. This method is applied to a first electronic device, such as mobile phone A or mobile phone B. The first electronic device and a first IoT device, such as a large screen, have a first binding relationship, and the first electronic device and the first IoT device also have a second binding relationship. The first binding relationship corresponds to a first service, such as an IoT service, and the second binding relationship corresponds to a second service, such as a device collaboration service. The first service and the second service are different services. The first IoT device also has a second binding relationship with at least one second electronic device. For example, at least one second electronic device can be mobile phone A and mobile phone B. The first electronic device is one of at least one second electronic device. Optionally, at least one second electronic device can be, for example, mobile phone A, and the first electronic device can be mobile phone A.

[0149] The first electronic device can receive a first instruction message sent by the service server, which instructs the service server to delete the first binding relationship between the first electronic device and the first IoT device. For example, the service server can send the first instruction message to the first electronic device after deleting the IoT registration information of the first IoT device in the first dataset. That is, after the service server deletes the IoT registration information of the first IoT device in the first dataset, it deletes the first binding relationship between the electronic devices in the first dataset and the first IoT device. The service server can, in response to a deletion instruction from any one of the electronic devices included in the first dataset, delete the first binding relationship between all electronic devices included in the first dataset and the first IoT device.

[0150] In response to the first instruction, the first electronic device sends a second instruction to the service server, which instructs the service server to delete the second binding relationship between the first IoT device and at least one second electronic device. In response to the second instruction, the service server can delete the trust ring registration information of the first IoT device in the second dataset, thereby deleting the second binding relationship between all electronic devices (i.e., at least one second electronic device) included in the second dataset and the first IoT device.

[0151] The following section introduces three different data processing methods based on user operations on different types of electronic devices, taking the first IoT device, a large screen, as an example.

[0152] The first scenario involves a user deleting the device card from the large screen on a first electronic device, such as mobile phone A, triggering the service server to delete the first and second binding relationships between the large screen and the electronic device. In this embodiment, the first electronic device is mobile phone A. Mobile phone A and mobile phone B are at least one second electronic device.

[0153] Figure 8 A data processing method provided in this application embodiment may include:

[0154] S801, Mobile Phone A displays the device management interface.

[0155] The device management interface could be, for example, the main interface of a smart space application, such as... Figure 2 Interface 201. The device management interface includes device cards corresponding to the large screen, used to indicate that mobile phone A has a first binding relationship with the first IoT device.

[0156] S802, in response to the first operation of deleting the device card on the large screen, the Smart Space application of mobile phone A sends a request message to the business server.

[0157] This request is used to remove the initial binding relationship between the large screen, the electronic device, and mobile phone A. Specifically, it's used to delete the IoT registration information of the large screen from the first dataset. The first operation could be, for example, on the user's main interface of a smart space application. Figure 7 Interface 01 describes how to operate the device cards on the large screen. This operation can include, for example, a long press or a tap.

[0158] S803, in response to the request information, the business server deletes the first binding relationship between the large screen and mobile phone A.

[0159] For example, the business server deletes the IoT registration information from the first centralized data screen. Deleting the IoT registration information from the first centralized data screen also simultaneously deletes the first binding relationship between the first centralized electronic devices, such as mobile phones A-C, and the screen.

[0160] After the business server deletes the initial binding relationship between the large screen and mobile phones A through C, it can send a first indication message to the electronic devices bound to the large screen, such as mobile phones A through C, to indicate that the large screen has been deleted. Specifically, the first indication message sent to mobile phone A indicates that the initial binding relationship between mobile phone A and the large screen has been deleted; the first indication message sent to mobile phone B indicates that the initial binding relationship between mobile phone B and the large screen has been deleted; and the first indication message sent to mobile phone C indicates that the initial binding relationship between mobile phone C and the large screen has been deleted.

[0161] S804, the service server sends the first instruction information to mobile phone A, mobile phone B and mobile phone C.

[0162] S805, the Smart Space application of mobile phone A responds to the first instruction information and deletes the device card and IoT registration information on the large screen.

[0163] In response to the first instruction, the Smart Space application on mobile phone A deletes the device card on the large screen and at the same time deletes the IoT registration information stored on the large screen of mobile phone A.

[0164] S806, the Smart Space application of mobile phone B responds to the first instruction information and deletes the device card and IoT registration information on the large screen.

[0165] In response to the first instruction, the Smart Space application on mobile phone B deletes the device card on the large screen and at the same time deletes the IoT registration information stored on the large screen of mobile phone B.

[0166] S807, the Smart Space application on mobile phone C responds to the first instruction message and deletes the device card and IoT registration information on the large screen.

[0167] In response to the first instruction, the Smart Space application on mobile phone C deletes the device card on the large screen and also deletes the IoT registration information stored on the large screen of mobile phone C.

[0168] Since mobile phone A includes a preset module, after the smart space application deletes the device card and IoT registration information from the large screen, the smart space application triggers the trust ring module through the preset module to trigger the business server to delete the second binding relationship between the large screen and electronic devices such as mobile phone A and mobile phone B. Mobile phone A can send a second instruction message to the business server, which instructs the business server to delete the second binding relationship between the large screen and the second electronic devices such as mobile phone A and mobile phone B.

[0169] S808, the Smart Space application of mobile phone A sends a second instruction message to the trust ring module through the preset module.

[0170] The second instruction message is used to instruct the trust ring module to trigger the business server to delete the second binding relationship between the large screen and electronic devices such as mobile phone A and mobile phone B. Specifically, it is used to delete the trust ring registration information of the large screen in the first data set. For example, the smart space application of mobile phone A sends the second instruction message to the preset module, and the preset module sends the second instruction message to the trust ring module.

[0171] S809, the trust ring module of mobile phone A sends the second instruction information to the service server.

[0172] S810, in response to the second instruction information, the business server deletes the second binding relationship between the large screen and mobile phone A.

[0173] For example, the business server deletes the trust ring registration record of the large screen in the second dataset. Deleting the trust ring registration record of the large screen in the second dataset also simultaneously deletes the second binding relationship between the electronic devices included in the second dataset, such as mobile phone A and mobile phone B, and the large screen.

[0174] S811, the service server sends a third instruction to the trust ring module of the electronic device within the trust ring corresponding to account A.

[0175] This third instruction indicates that the large screen has been removed from the trust ring corresponding to account A. In other words, the second binding relationship between the electronic device logged into account A and the large screen has been severed.

[0176] In response to the third instruction, electronic devices within the trust ring corresponding to account A, such as mobile phone A and mobile phone B, can delete the saved trust ring registration information on the large screen. For example, mobile phone A can execute S810, and mobile phone B can execute S811.

[0177] S812, the trust ring module of mobile phone A responds to the third instruction information and sends the third instruction information to the smart space application through the preset module.

[0178] S813, in response to the third instruction, the Smart Space application on phone A deletes the trust ring registration information on the large screen of phone A.

[0179] S814, in response to the third instruction, the trust ring module of mobile phone B deletes the trust ring registration information on the large screen of mobile phone B.

[0180] In this way, the business server can delete two records from the large screen, such as the IoT registration record and the trust ring registration record. Mobile phones A and B can delete information from the large screen (such as IoT registration information and trust ring registration information). Mobile phone C can delete the IoT registration information. Thus, there is no data residue on the business server, mobile phone A, mobile phone B, and mobile phone C.

[0181] The second scenario is that if phone A is unusable, the user can delete the large screen on phone B or phone C. Situations where phone A is unusable include: phone A is lost, phone A is down, phone A is malfunctioning and cannot be turned on, phone A cannot launch the Smart Space application, etc. In other words, phone A being unusable means that phone A cannot trigger the business server to delete the first and second binding relationships.

[0182] Figure 9 A data processing method provided in this application embodiment may include:

[0183] S901, in response to the user's first operation of deleting the device card on the large screen, the Smart Space application of mobile phone C sends a request message to the business server.

[0184] Before executing S901, mobile phone C can display a device management interface. This device management interface could be, for example, the main interface of a smart space application, such as... Figure 2 Interface 201. The device management interface includes device cards corresponding to the large screen, used to indicate that there is a first binding relationship between mobile phone C and the first IoT device.

[0185] Optionally, the above method can also be: S901, in response to the user's first operation of deleting the device card on the large screen, the Smart Space application of mobile phone B sends a request message to the service server. Before executing S901, mobile phone B can display a device management interface. This device management interface can be, for example, the main interface of the Smart Space application, such as... Figure 2 Interface 201. The device management interface includes device cards corresponding to the large screen, used to indicate that mobile phone B has a first binding relationship with the first IoT device. In this embodiment, the first electronic device is mobile phone A. Mobile phone A and mobile phone B are at least one second electronic device.

[0186] S902, in response to the request, the business server deletes the first binding relationship between the large screen and mobile phone C.

[0187] Optionally, the above method can also be: S902, in response to the request information, the business server deletes the first binding relationship between the large screen and mobile phone B.

[0188] For example, in response to this request, the business server deletes the IoT registration information of the first centralized data screen. Deleting the IoT registration information of the first centralized data screen also simultaneously deletes the first binding relationship between the first centralized electronic devices, such as mobile phones A-C, and the screen.

[0189] S903, the service server sends the first instruction information to mobile phone B and mobile phone C.

[0190] The first instruction message indicates that the large screen has been deleted. Specifically, the first instruction message sent to mobile phone B indicates that the first binding relationship between mobile phone B and the large screen has been deleted, and the first instruction message sent to mobile phone C indicates that the first binding relationship between mobile phone C and the large screen has been deleted.

[0191] S904, in response to the first instruction message, the Smart Space application of mobile phone C deletes the device card and IoT registration information on the large screen.

[0192] Deleting the device card on the large screen of phone C will also delete the IoT registration information stored on the large screen of phone C.

[0193] S905, in response to the first instruction, the Smart Space application of mobile phone B deletes the device card and IoT registration information from the large screen.

[0194] Deleting the device card on the large screen of phone B will also delete the IoT registration information stored on the large screen of phone B.

[0195] In this way, either phone C or phone B can trigger the business server to delete the IoT registration information of the large screen. Both phone B and phone C can delete the IoT registration information of the large screen. The business server still retains the trust ring registration information of the large screen. Phone B also retains the trust ring registration information of the large screen. In this situation, if phone B can identify whether the IoT registration information of the large screen has been deleted from the business server, and confirms that the IoT registration information of the large screen has been deleted, it can instruct the business server to delete the trust ring registration information of the large screen.

[0196] As an example, mobile phone B can send a query request to the business server. This query request includes the first device identifier of the large screen, and is used to check whether the business server still stores the large screen's IoT registration information. Based on the first device identifier in the query information, the business server can query the first dataset to see if it still stores the large screen's IoT registration information. The business server can return the query result to mobile phone B. Based on the query result, mobile phone B determines that the large screen's IoT registration information has been deleted from the business server.

[0197] As another example, to reduce data interaction and save power, mobile phone B can obtain the registration information corresponding to the first service from the service server. The registration information of the first service can be, for example, the first dataset shown in Tables 2 and 4. The registration information of the first service contains the binding relationships between multiple electronic devices such as mobile phone A and mobile phone B and IoT devices such as large screens, which are used to indicate that the bound electronic devices and IoT devices can realize the first service.

[0198] Optionally, mobile phone B can obtain the registration information corresponding to the first service from the service server when the triggering conditions are met.

[0199] The triggering condition can be any one of the following: mobile phone B switches to a different wireless network, mobile phone B logs out of its device account and then logs back in, mobile phone B disables and then enables the collaboration function, or mobile phone B restarts. In conventional technology, mobile phone B can obtain trust ring data from the server when the triggering condition is met. This solution follows the conventional logic, obtaining a third dataset from the business server when the triggering condition is met. This reduces development investment and avoids significant modifications to the original execution logic. Optionally, mobile phone B can obtain registration information corresponding to the first business and the second business from the business server when the triggering condition is met.

[0200] The following section uses the example of mobile phone B actively obtaining the registration information corresponding to the first service, such as the first dataset, for illustration. For example, mobile phone B can execute S906-S910.

[0201] S906, when the triggering condition is met, the trust ring module of mobile phone B obtains the first dataset from the business server.

[0202] For example, the trust ring module of mobile phone B sends a request to the business server to download the first dataset. In response to this request, the business server sends the first dataset to the mobile phone.

[0203] S907, the trust ring module of mobile phone B queries the first dataset, which does not include the second binding relationship between mobile phone B and the large screen.

[0204] For example, the mobile phone can store the first device identifier of the large screen in a preset location. When deleting IoT registration information, the mobile phone will not delete the first device identifier of the large screen. For example, the IoT registration information can be the first UDID+SN, and the first device identifier can be the first UDID. The trust ring registration information can be the second UDID+SN. The mobile phone can concatenate the first UDID and SN to obtain the IoT registration information.

[0205] The trust loop module of mobile phone B can determine the registration information corresponding to the first service, such as the first data, and whether it includes the first binding relationship between mobile phone B and the large screen. For example, when mobile phone B's trust loop module searches for the IoT registration record of the large screen in the first dataset, since the service server has deleted the IoT registration record of the large screen from the first dataset, mobile phone B's trust loop module cannot find the IoT registration record of the large screen in the first dataset. Therefore, the query of the first dataset by mobile phone B's trust loop module does not include the second binding relationship between mobile phone B and the large screen.

[0206] S908, the trust ring module of mobile phone B sends a second instruction message to the service server.

[0207] S909, in response to the second instruction information, the business server deletes the second binding relationship between the large screen and mobile phone B.

[0208] For example, the business server deletes the trust ring registration record of the large screen in the second dataset. Deleting the trust ring registration record of the large screen in the second dataset also simultaneously deletes the second binding relationship between the electronic devices included in the second dataset, such as mobile phone A and mobile phone B, and the large screen.

[0209] S910, the service server sends a third instruction to the trust ring module of the electronic device within the trust ring corresponding to account A.

[0210] The third instruction message indicates that the large screen has been removed from the trust ring corresponding to account A, that is, the second binding relationship between mobile phone A and mobile phone B and the large screen has been deleted.

[0211] In this way, the business server will not retain the trust ring registration information from the large screen. Optionally, the above methods also include:

[0212] S911, in response to instruction information B, the trust ring module of mobile phone B deletes the trust ring registration information on the large screen.

[0213] Thus, when a user deletes the device card of an IoT device on an electronic device that does not support device collaboration services, such as a mobile phone (C), they can delete the IoT device's IoT registration information in the business server, but they cannot delete the IoT device's trust ring registration information in the business server. However, if an electronic device that supports device collaboration services meets certain triggering conditions, it can identify whether the IoT device's IoT registration information in the business server has been deleted. If the IoT device's IoT registration information has been deleted, then the trust ring registration information of the IoT device in the business server will be deleted.

[0214] Thirdly, if phone A is usable, the user can delete the large screen on phone B or phone C.

[0215] Figure 10 A data processing method provided in this application embodiment may include:

[0216] S101, in response to the user's first operation of deleting the device card on the large screen, the Smart Space application of mobile phone C sends a request message to the business server.

[0217] Before executing S101, phone C can display the device management interface. This device management interface could be, for example, the main interface of a smart space application, such as... Figure 2 Interface 201. The device management interface includes device cards corresponding to the large screen, used to indicate that there is a first binding relationship between mobile phone C and the first IoT device.

[0218] Optionally, the above method can also be as follows: S101, in response to the user's first operation of deleting the device card on the large screen, the Smart Space application of mobile phone B sends a request message to the service server. Before executing S901, mobile phone B can display a device management interface. This device management interface can be, for example, the main interface of the Smart Space application, such as... Figure 2 Interface 201. The device management interface includes device cards corresponding to the large screen, used to indicate that mobile phone B has a first binding relationship with the first IoT device. In this embodiment, the first electronic device is mobile phone A. Mobile phone A and mobile phone B are at least one second electronic device.

[0219] S102, in response to the request, the business server deletes the first binding relationship between the large screen and mobile phone C.

[0220] Optionally, the above method can also be: S102, in response to the request information, the business server deletes the first binding relationship between the large screen and mobile phone B.

[0221] S101-S102 are similar to S901-S902, and will not be described again here. Please refer to the previous text.

[0222] S103, the service server sends the first instruction information to mobile phone A, mobile phone B and mobile phone C.

[0223] S104, the Smart Space application of mobile phone A responds to the first instruction information and deletes the device card and IoT registration information on the large screen.

[0224] In response to the first instruction, when the Smart Space application on mobile phone A deletes the device card on the large screen, it will also delete the IoT registration information stored on the large screen of mobile phone A.

[0225] S105, the Smart Space application of mobile phone B responds to the first instruction information and deletes the device card and IoT registration information on the large screen.

[0226] In response to the first instruction, when the Smart Space application on mobile phone B deletes the device card on the large screen, it will also delete the IoT registration information stored on the large screen of mobile phone B.

[0227] S106, the Smart Space application on mobile phone C responds to the first instruction information and deletes the device card and IoT registration information on the large screen.

[0228] In response to the first instruction, when the Smart Space application on mobile phone C deletes the device card on the large screen, it will also delete the IoT registration information stored on the large screen of mobile phone C.

[0229] In this way, phone C or phone B can trigger the business server to delete the IoT registration information of the large screen. Phones A, B, and C can all delete the IoT registration information of the large screen. The business server still retains the trust ring registration information of the large screen. Phones B and A also retain the trust ring registration information of the large screen. Since phone A includes a preset module, after the smart space application deletes the device card and IoT registration information of the large screen, the smart space application triggers the trust ring module through the preset module to delete the trust ring registration information of the large screen in the business server. Phones A, B, C, and the large screen can interactively execute S107-S113. Among them, S107-S113 is similar to S808-S814, as detailed above, and will not be repeated here.

[0230] S107, the Smart Space application of mobile phone A sends a second instruction message to the Trust Ring module through the preset module.

[0231] The second instruction message is used to instruct the trust ring module to trigger the business server to delete the second binding relationship between the large screen and electronic devices such as mobile phone A and mobile phone B. Specifically, it is used to delete the trust ring registration information of the large screen in the first data set. For example, the smart space application of mobile phone A sends the second instruction message to the preset module, and the preset module sends the second instruction message to the trust ring module.

[0232] S108, the trust ring module of mobile phone A sends the second instruction information to the service server.

[0233] S109, in response to the second instruction information, the business server deletes the second binding relationship between the large screen and mobile phone A.

[0234] For example, the business server deletes the trust ring registration record of the large screen in the second dataset. Deleting the trust ring registration record of the large screen in the second dataset also simultaneously deletes the second binding relationship between the electronic devices included in the second dataset, such as mobile phone A and mobile phone B, and the large screen.

[0235] S110, the service server sends a third instruction to the trust ring module of the electronic device within the trust ring corresponding to account A.

[0236] This third instruction indicates that the large screen has been removed from the trust ring corresponding to account A.

[0237] In response to the third instruction, electronic devices within the trust ring corresponding to account A, such as mobile phone A and mobile phone B, can delete the saved trust ring registration information on the large screen. For example, mobile phone A can execute S810, and mobile phone B can execute S811.

[0238] S111, the trust ring module of mobile phone A responds to the third instruction information and sends the third instruction information to the smart space application through the preset module.

[0239] S112, in response to the third instruction, the Smart Space application on mobile phone A deletes the trust ring registration information on the large screen of mobile phone A.

[0240] S113, the trust ring module of mobile phone B responds to the third instruction information and deletes the trust ring registration information on the large screen of mobile phone B.

[0241] In this way, phone C or phone B can trigger the business server to delete the IoT registration information of the large screen. Phones A, B, and C can all delete the IoT registration information of the large screen. The business server still retains the trust ring registration information of the large screen. Phones B and A also retain the trust ring registration information of the large screen. Since phone A includes a preset module, after the smart space application on phone A deletes the device card of the large screen, it can delete the trust ring registration information of the large screen from the business server through the preset module.

[0242] This application provides a data processing system, including a first electronic device and a business server. The business server includes a first binding relationship between the first electronic device and a first IoT device, and a second binding relationship between the first electronic device and the first IoT device. The first binding relationship corresponds to a first service. The first IoT device also has a second binding relationship with at least one second electronic device, which corresponds to a second service. The first service and the second service are different. The at least one second electronic device includes the first electronic device. The first electronic device is used to receive first indication information sent by the business server. The first indication information is used to indicate that the business server has deleted the first binding relationship. In response to the first indication information, the first electronic device sends second indication information to the business server, which is used to instruct the business server to delete the second binding relationship. For example, the system includes a business server and mobile phones A-C. Mobile phones A-C are used to interact with the business server to implement a data processing method provided in this application embodiment.

[0243] This application provides an electronic device including a memory, a display screen, and one or more processors. The display screen is coupled to the processors. The memory stores computer program code, which includes computer instructions. When the processor executes the computer instructions, the electronic device can perform various functions or steps performed by mobile phone A or mobile phone B in the above method embodiments. The structure of the electronic device can be referred to... Figure 4 The structure of the electronic device 400 shown.

[0244] This application embodiment also provides a computer storage medium, which includes computer instructions, when the computer instructions are executed in the aforementioned electronic device (such as...). Figure 4 When the electronic device 400 shown is run, it causes the electronic device to perform the various functions or steps in the above method embodiments.

[0245] This application also provides a computer program product that, when run on a computer, causes the computer to perform the various functions or steps described in the above method embodiments.

[0246] This application also provides a chip system including at least one processor and at least one interface circuit. The processor and the interface circuit are interconnected via lines. For example, the interface circuit can be used to receive signals from other devices (e.g., the memory of an electronic device). As another example, the interface circuit can be used to send signals to other devices (e.g., the processor). Exemplarily, the interface circuit can read instructions stored in the memory and send the instructions to the processor. When the instructions are executed by the processor, the electronic device can perform the steps in the above embodiments. Of course, the chip system may also include other discrete devices, and this application does not specifically limit this.

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

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

[0249] 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.

[0250] 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.

[0251] 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.

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

Claims

1. A data processing method, characterized in that, The first electronic device is applied to a first electronic device, which has a first binding relationship with a first IoT device. The first binding relationship corresponds to a first service. The first IoT device also has a second binding relationship with at least one second electronic device, which corresponds to a second service. The first service and the second service are different. The at least one second electronic device includes the first electronic device. The method includes: Receive a first indication message sent by the service server; the first indication message is used to indicate that the service server has deleted the first binding relationship. In response to the first instruction information, a second instruction information is sent to the business server, the second instruction information being used to instruct the business server to delete the second binding relationship.

2. The method according to claim 1, characterized in that, The first electronic device includes a first application, which supports the first electronic device and the first IoT device to perform the first service; the first electronic device supports the second service but does not support initiating the second service in the first application; Before sending the second indication information to the service server in response to the first indication information, the method further includes: The registration information corresponding to the first service is obtained from the service server. The registration information includes multiple sets of binding relationships between electronic devices and IoT devices, which are used to indicate that the bound electronic devices and IoT devices can realize the first service. It is determined that the registration information does not include the first binding relationship.

3. The method according to claim 2, characterized in that, The step of obtaining the registration information corresponding to the first service from the service server includes: If the triggering conditions are met, the registration information is obtained from the business server; The triggering conditions include one or more of the following: the first electronic device switches the connected wireless network, the first electronic device logs out of the device account and then logs back in to the device account, the first electronic device disables the collaboration function and then enables the collaboration function again, or the first electronic device restarts.

4. The method according to claim 2 or 3, characterized in that, The first electronic device includes a first module; the first module is used to support the first electronic device and the first IoT device to perform the second service; The step of obtaining the registration information corresponding to the first service from the service server includes: The first module obtains the registration information from the business server; The method further includes: The first module determines whether the registration information includes the first binding relationship.

5. The method according to claim 1, characterized in that, The first electronic device includes a first application, which supports the first electronic device and the first IoT device to perform the first service; the first electronic device supports the second service and supports initiating the second service in the first application.

6. The method according to claim 5, characterized in that, The first electronic device includes a first module and a second module; the first module is used to support the first electronic device and the first IoT device to perform the second service; the second module is used to support initiating the first electronic device and the first IoT device to perform the second service in the first application; The step of sending a second indication message to the service server in response to the first indication message includes: In response to the first indication information, the first application triggers the first module to send the second indication information to the business server through the second module.

7. The method according to any one of claims 1-6, characterized in that, Before receiving the first indication information sent by the service server, the method further includes: Display device management interface, the device management interface includes a device card corresponding to the first IoT device, used to indicate that the first electronic device and the first IoT device have the first binding relationship; Receive the first operation to delete the device card; In response to the first operation, a request message is sent to the business server, the request message being used to request the business server to delete the first binding relationship.

8. The method according to any one of claims 1-7, characterized in that, The method further includes: The first electronic device deletes the registration information corresponding to the first IoT device and the second service.

9. The method according to any one of claims 1-8, characterized in that, The first business is the Internet of Things (IoT) business, and the second business is the device collaboration business.

10. A data processing system, characterized in that, Including the primary electronic device and the business server; The service server includes a first binding relationship between the first electronic device and the first IoT device and a second binding relationship between the first electronic device and the first IoT device; the first binding relationship corresponds to a first service; the first IoT device also has a second binding relationship with at least one second electronic device. The second binding relationship corresponds to the second service; the first service is different from the second service; the at least one second electronic device includes the first electronic device; The first electronic device is used to receive first indication information sent by the service server; The first indication information is used to indicate that the business server has deleted the first binding relationship; In response to the first instruction information, a second instruction information is sent to the business server, the second instruction information being used to instruct the business server to delete the second binding relationship.

11. The system according to claim 10, characterized in that, The first electronic device includes a first application, which supports the first electronic device and the first IoT device to perform the first service; the first electronic device supports the second service but does not support initiating the second service in the first application.

12. The system according to claim 10, characterized in that, The first electronic device is further configured to obtain registration information from the service server before sending the second indication information to the service server in response to the first indication information, provided that a triggering condition is met; the registration information includes multiple sets of binding relationships between electronic devices and IoT devices, used to indicate that the bound electronic devices and IoT devices can realize the first service; and it is determined that the first binding relationship is not included in the registration information.

13. An electronic device, characterized in that, The electronic device includes: a memory and one or more processors; the memory is coupled to the processors; wherein the memory is used to store computer program code, the computer program code including computer instructions; when the computer instructions are executed by the processor, the electronic device performs the method as described in any one of claims 1-9.

14. A computer-readable storage medium, characterized in that, Includes computer instructions that, when executed on an electronic device, cause the electronic device to perform the method as described in any one of claims 1-9.

15. A computer program product comprising a computer program / instructions, characterized in that, When the computer program / instructions are executed by the processor, they implement the steps of the method as described in any one of claims 1-9.

Images