Data processing method and electronic equipment

Abstract

The embodiment of the invention relates to the field of communication, in particular to a data processing method and electronic equipment, which can delete residual data of a cloud side server such as a service server. The method comprises the following steps: receiving first indication information sent by a service server; the first indication information is used for indicating that the business server has deleted the first binding relationship; and in response to the first indication information, sending second indication information to the service server, the second indication information being used for indicating the service server to delete the second binding relationship.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communications, and in particular to a data processing method and electronic device. Background Art

[0002] With the development of the Internet of Things (IoT), various IoT devices are widely used in various fields, bringing convenience to people's lives. Users can add device cards for IoT devices in the first application of electronic devices, such as the Smart Space application, to facilitate user management of IoT devices.

[0003] When adding an IoT device card, the electronic device and the IoT device interact with a cloud-based server to register services. If the electronic device and the IoT device support multiple services, the cloud-based server stores registration information corresponding to the multiple services associated with the IoT device. Once the electronic device no longer controls the IoT device, the cloud-based server cannot delete the stored registration information, resulting in residual data on the cloud-based server and wasting storage space. Summary of the Invention

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

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

[0006] In a first aspect, a data processing method is provided, which is applied to a first electronic device, wherein the first electronic device has a first binding relationship with a first IoT device, the first binding relationship corresponding to a first service, and the first IoT device also has 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, and the at least one second electronic device including the first electronic device. The method comprises: receiving first indication information sent by a service server; the first indication information is used to indicate that the service server has deleted the first binding relationship; and 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 the second binding relationship.

[0007] In this application, after a first electronic device receives first indication information indicating that a service server has deleted a first binding relationship, it can proactively trigger the service server to delete a second binding relationship between the first IoT device and at least one second electronic device. In this way, when the electronic device is no longer using the first IoT device, the first electronic device can proactively trigger the service server to delete any remaining binding data, thereby avoiding wasting storage space on the service server.

[0008] In a possible implementation of the first aspect, a first electronic device includes a first application, the first application being used to support the first electronic device and the first IoT device in performing a first service; the first electronic device supports a 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 first electronic device obtains registration information corresponding to the first service from the service server. The registration information includes binding relationships between multiple sets of electronic devices and IoT devices, indicating that the first service can be implemented between the bound electronic devices and the IoT devices. The first electronic device determines that the registration information does not include the first binding relationship. Because the registration information does not include the first binding relationship, the first electronic device can, in response to the first indication information, actively trigger the service server to delete the second binding relationship between the first IoT device and at least one second electronic device. If the first electronic device does not support initiating the second service in the first application, the second electronic device can actively obtain the registration information corresponding to the first service and, based on the registration information corresponding to the first service, trigger the service server to delete the second binding relationship corresponding to the first IoT device.

[0009] In a possible implementation of the first aspect, the first electronic device obtains registration information from the business server when a trigger condition is met; the trigger condition includes one or more of the following conditions: the first electronic device switches the wireless network to which it is connected, the first electronic device logs out of the device account and then logs back into the device account, the first electronic device turns off the collaborative function and then turns it back on, or the first electronic device is restarted.

[0010] In conventional technology, mobile phone B can obtain trust ring data from the server when the trigger conditions are met. This solution follows the conventional logic and obtains the third data set from the service server when the trigger conditions are met. This can reduce development investment and avoid major changes to the original execution logic.

[0011] In one possible implementation of the first aspect, a first electronic device includes a first application and a first module; the first application is configured to support the first electronic device and a first IoT device in performing a first service; the first module is configured to support the first electronic device and the first IoT device in performing a second service; the first module obtains registration information from a service server and then determines whether the registration information includes a first binding relationship. The first module may be, for example, a trust ring module.

[0012] In a possible implementation of the first aspect, the first electronic device includes a first application, which is used to support the first electronic device and the first IoT device to perform a first service; the first electronic device supports a second service and supports initiating the second service in the first application.

[0013] In one possible implementation of the first aspect, a first electronic device includes a first application, a first module, and a second module. The first application is configured to support the first electronic device and a first IoT device in performing a first service. The first module is configured to support the first electronic device and the first IoT device in performing a second service. The second module is configured to support triggering the first electronic device and the IoT device to perform the second service in the first application, i.e., the second module is configured to support initiation of the second service in the first application. If the first electronic device supports the second service and supports initiation of the second service in the first application, in response to first indication information, the first application triggers the first module, via the second module, to send the second indication information to a service server.

[0014] In a possible implementation of the first aspect, the first electronic device can display a device management interface, the device management interface 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 information to the business server, the request information being used to request the business server to delete the first binding relationship.

[0015] In one possible implementation of the first aspect, a third electronic device may display a device management interface, the device management interface including a device card corresponding to the first IoT device, indicating a first binding relationship 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 to a service server, the request information being used to request the service server to delete the first binding relationship. The third electronic device includes the first application, and the third electronic device supports the first service but not the second service.

[0016] In a possible implementation of the first aspect, the first electronic device may also delete the registration information corresponding to the first IoT device and the second service stored in the first electronic device. Optionally, the registration information may be trust ring registration information. In this way, residual data in the first electronic device may be deleted, thereby avoiding waste of storage space of the first electronic device. The first electronic device may delete the registration information corresponding to the first IoT device and the second service stored in the first electronic device upon receiving the first indication information. Alternatively, the first electronic device may delete the registration information corresponding to the first IoT device and the second service stored in the first electronic device upon sending a request message. Alternatively, the first electronic device may receive third indication information from a service server, the third indication information being used to indicate that the service server has deleted the second binding relationship between the first electronic device and the first IoT device. Upon receiving the third indication information, the first electronic device deletes the registration information corresponding to the first IoT device and the second service stored in the first electronic device. The registration information corresponding to the first IoT device and the second service may, for example, be the trust ring registration information of the first IoT device.

[0017] In a possible implementation of the first aspect, the first service is an Internet of Things service, and the second service is a device collaboration service.

[0018] In a possible implementation of the first aspect, before performing the data processing provided in this application, the following method can be performed to bind a first IoT device to an electronic device. The method includes: receiving a second operation of adding a device card of the first IoT device in a device management interface; in response 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 service server to register a first binding relationship between the first IoT device and the second electronic device; and upon querying that the first binding relationship between the first IoT device and the second electronic device is successfully registered in the service server, sending second registration information to the service 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 service server.

[0019] In a second aspect, 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 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 the first business, 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 business, the first business is different from the second business, and the at least one second electronic device includes the first electronic device; the first electronic device is used to receive a first indication message sent by the business server; the first indication message is used to indicate that the business server has deleted the first binding relationship; in response to the first indication message, a second indication message is sent to the business server, and the second indication message is used to instruct the business server to delete the second binding relationship.

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

[0021] In a possible implementation of the second aspect, the first electronic device is also used to obtain registration information from the business server before sending the second indication information to the business server in response to the first indication information, when the trigger condition is met; the registration information includes binding relationships between multiple groups of electronic devices and IoT devices, which is used to indicate that the bound electronic devices and IoT devices can realize the first business; and it is determined that the first binding relationship is not included in the registration information.

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

[0023] In a fourth aspect, a chip system is provided, which can be applied to an electronic device including a memory. The chip system includes one or more interface circuits and one or more processors. The interface circuits and processors are interconnected via wiring. The interface circuits are configured to receive signals from the memory and send these signals to the processors, the signals including computer instructions stored in the memory. When the processors execute the computer instructions, the electronic device performs the method of the first aspect and any possible design thereof.

[0024] In a fifth aspect, a computer-readable storage medium is provided, comprising computer instructions. When the computer instructions are executed on an electronic device, the electronic device executes any one of the methods in the first aspect.

[0025] In a sixth aspect, a computer program product comprises a computer program / instruction, which implements the steps of any one of the methods in the first aspect when the computer program / instruction is executed by a processor.

[0026] To be understood, the beneficial effects that can be achieved by the electronic device of any possible design 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 be referred to the beneficial effects in the first aspect and any possible design thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0028] Figure 2 A schematic diagram of another device management interface provided in an embodiment of the present application;

[0029] Figure 3 A trust circle diagram provided in an embodiment of the present application;

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

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

[0032] Figure 6A schematic diagram of a method for binding IoT devices provided in an embodiment of the present application;

[0033] Figure 7 A schematic diagram of an interface for binding an IoT device provided in an embodiment of the present application;

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

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

[0036] Figure 10 A schematic diagram of another data processing method provided in an embodiment of the present application. DETAILED DESCRIPTION

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

[0038] Electronic devices can manage and control IoT devices. Specifically, the electronic device used to manage and control IoT devices can be a control terminal. The electronic device includes a control application for managing and controlling IoT devices, which can be, for example, a smart space application. The electronic device can add device cards for IoT devices to the control application, and the device cards of the added IoT devices can be displayed on the control application interface. When an IoT device is online, the electronic device can respond to user operations, such as operations on the device card, and control the IoT device to execute the corresponding control instructions. For example, the electronic device can control the IoT device to power on and off the large screen, adjust the volume, and switch channels.

[0039] For example, the electronic device is a mobile phone and the control application is a smart space application. Figure 1As shown, the mobile phone displays a main interface, which includes an application icon 101 corresponding to the Smart Space application. In response to a user's operation on application icon 101, the mobile phone displays an interface 102 for the Smart Space application. Interface 102 includes device cards for IoT devices that have been added to the mobile phone, such as a device card 103 for headphones and a device card 104 for speakers. The process of adding an IoT device to a mobile phone includes: the mobile phone discovering the IoT device and binding the mobile phone and the IoT device. Binding includes the mobile phone instructing the IoT device to register with the cloud server for the IoT. After the IoT device successfully registers with the IoT, the mobile phone has the authority to control the IoT device. Instructing the IoT device to register with the IoT includes: the mobile phone sending an instruction message to the IoT, instructing the IoT device to register with the IoT. In response to the instruction message, the IoT device exchanges data with the cloud server to complete 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 loop module, which is used to support the electronic device to collaborate with other electronic devices. Among them, device collaboration can include various collaborative services such as application continuation, screen sharing, call sharing, notification sharing, keyboard and mouse sharing, camera sharing, network sharing, etc. Taking the IoT device as an example of a large screen, electronic devices such as mobile phones can be projected on the large screen. Figure 2 As shown, after the large-screen device card 202 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 an interface 203, and the interface 203 includes a screen projection option 204. In response to the user's operation on the option, the mobile phone projects the screen on the large screen.

[0041] Optionally, the electronic device and the IoT device can be electronic devices within the same trust ring. The electronic device and the IoT device can establish a trust relationship through trusted authentication to form a trust ring. There are many ways for electronic devices and IoT devices to form a trust ring. For example, the electronic device and the IoT device log in to the same account, and multiple electronic devices under the same account trust each other, and the electronic device and the IoT device form a trust ring. For another example, the electronic device and the IoT device do not log in to the same account, and the electronic device and the IoT device perform trusted authentication through a protocol, establish a trust relationship, and form a trust ring. For example, Figure 3 As shown in the figure, mobile phones, smart watches, tablets, large screens, and personal computers (PCs) form a trust circle by logging into the same account.

[0042] If electronic device control applications, such as smart space applications, support device collaboration services, in response to a user adding an IoT device, the mobile phone can bind to the IoT device twice: once for IoT binding, after which the mobile phone and the IoT device can perform IoT services; and once for trust ring binding, after which the mobile phone and the IoT device can perform device collaboration services. Trust ring binding involves data exchange between the IoT device and the cloud server, and trust ring registration. After the IoT device completes trust ring registration, the cloud server can save the binding relationship between the IoT device and the mobile phone.

[0043] When adding a device card of 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 for the IoT service and one for the trust ring.

[0044] That is, if the electronic device and the IoT device support multiple services, the cloud-side server will store registration information corresponding to multiple services related to the IoT device. When the electronic device no longer controls the IoT device, the registration information stored by the cloud-side server cannot be deleted, resulting in residual data on the cloud-side server and wasting storage space.

[0045] To this end, an embodiment of the present application provides a data processing method and an electronic device, which can delete the binding relationship between electronic devices in a cloud server to avoid data residue.

[0046] The method provided in the embodiment of the present application can be applied to electronic devices with data processing capabilities, which may include mobile phones, tablet computers, laptop computers, netbooks, personal digital assistants (PDAs), wearable devices (such as smart watches, smart bracelets, etc.), vehicle-mounted devices, virtual reality devices, etc., and the embodiment of the present application does not impose any restrictions on this. In the embodiment of the present application, the above-mentioned electronic devices are electronic devices that can run operating systems and install applications. Optionally, the operating system running on the electronic device can be system, system, System, etc.

[0047] Take the 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] The processor 410 may include one or more processing units, for example: the processor 410 may include an application processor (AP), a central processing unit, a modem processor, a graphics processing unit (GPU), an ISP, a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Among them, different processing units can be independent devices or integrated into one or more processors. The controller can be the nerve center and command center of the electronic device 400. The controller can generate operation control signals based on instruction opcodes and timing signals to complete the control of instruction fetching and execution.

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

[0050] The memory 420 can be used to store computer executable program codes, which include 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. Among them, the program storage area can store an operating system, an application required for at least one function (such as a sound playback function, an interface display function, etc.). The data storage area can store data created during the use of the electronic device (such as notification messages), etc. In addition, the memory 420 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0051] In the embodiment of the present application, the memory 420 stores computer executable program code, which includes instructions. The processor 410 executes an image processing method provided by the embodiment of the present application 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 460, camera 480, and the like. The power management module 440 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In other embodiments, the power management module 440 can also be provided within the processor 410.

[0053] The communication module 450 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc. applied to the electronic device 400. 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, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 410. The communication module 450 can also receive the signal to be sent from the processor 410, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna.

[0054] In some embodiments, the antenna of the electronic device 400 is coupled to the communication module 450 so that the electronic device 400 can communicate with a network 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 technology. The GNSS may include global positioning system (GPS), Beidou navigation satellite system (BDS), global navigation satellite system (GLONASS), and / or Galileo satellite navigation system (GALILEO).

[0055] Electronic device 400 implements display functionality through a GPU, display screen 460, and an application processor. The GPU is a microprocessor for image processing that connects display screen 460 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 410 may include one or more GPUs that 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] The electronic device 400 can implement shooting and video recording functions through an ISP, a camera 480, a video codec, a GPU, a display screen 460, and an application processor.

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

[0059] Camera 480 is used to capture still images or videos. The object generates an optical image through the lens and projects it onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then passed to the ISP for conversion into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard format such as RGB or YUV.

[0060] The sensor module 490 may include a pressure sensor, a gyroscope sensor, an air pressure sensor, a magnetic sensor, an acceleration sensor, a distance sensor, a proximity light sensor, a fingerprint sensor, a temperature sensor, a touch sensor, an ambient light sensor, and a bone conduction sensor, etc.

[0061] It should be 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 shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0062] Take the above electronic device 400 as an example, which is a mobile phone. The software system of the electronic device 400 can adopt a layered architecture, an event-driven architecture, a micro-core architecture, a micro-service architecture, or a cloud architecture. Taking the system as an example, the software structure of the electronic device 400 is exemplified.

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

[0064] A layered architecture divides software into several layers, each with distinct roles and responsibilities. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers: application layer, application framework layer, system library layer, and kernel layer, from top to bottom.

[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, gallery, call, map, navigation, WLAN, Bluetooth, music, video, short message, social networking, and other applications. 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 an application programming interface (API) and programming framework for the 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, and the like.

[0069] The input system monitors the phone's input module (such as the touchscreen driver) and converts the parameters input by the input module into usable events, passing them to the relevant upper-level modules. For example, the input system monitors the phone's touchscreen through the touchscreen driver and converts the touch parameters generated by the touch input into usable events, passing them to the upper-level app.

[0070] Content providers are used to store and retrieve data and make it accessible to applications. Data can include videos, images, audio, calls made and received, browsing history and bookmarks, phone books, etc.

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

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

[0073] The first module is used to support device collaboration services of the electronic device 400. The first module may be a collaboration module such as a trust ring module. The networking module is used to implement events such as device connection and authentication.

[0074] Optionally, the application framework layer may further include a second module. The second module may be used to support the device collaboration function in the first application. The second module is used to manage the first application and the first module.

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

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

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

[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 drawing engine for 2D drawings.

[0080] The kernel layer is the layer between hardware and software. The kernel layer may include touch screen drivers, display drivers, camera drivers, sensor drivers, etc.

[0081] Embodiments of the present application include multiple electronic devices and a first IoT device. The multiple electronic devices may be control terminals for managing and controlling the first IoT device. The multiple electronic devices each include a control application, such as a smart space application, for managing and controlling 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 that supports device collaboration services for electronic devices. The first device may include electronic device 1 and electronic device 2. The smart space application of electronic device 1 supports collaboration services. The smart space application of electronic device 2 does not support collaboration services. Electronic device 1 supports device collaboration services and supports initiating device collaboration services in the smart space application. Electronic device 2 supports device collaboration services and supports initiating device collaboration services in the smart space application.

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

[0084] Electronic device 1 and electronic device 2 can be electronic devices in the same trust ring. For example, electronic device 1 and electronic device 2 can log in to the same device account, and when the device collaboration function and wireless communication function are turned on, electronic device 1 and electronic device 2 can both apply to join the trust ring of the logged-in device account. For example, data is interacted with the server on the cloud side, and an application is made to join the trust ring of the logged-in device account. Optionally, in the case where the first device includes a device that has not logged in to the device account, such as electronic device 2, a device that has logged in to the device account, such as electronic device 1, can add a device that has not logged in to the device account, such as electronic device 2, to the trust ring of the logged-in device account after joining the trust ring of the logged-in device account. Reference can be made to the existing technology here and will not be repeated. When the wireless communication function of the first IoT device is turned on, electronic device 1 can add the first IoT device to the trust ring where electronic device 1 is located while adding the device card of the first IoT device. Here, turning on the wireless communication function refers to turning on the WLAN function and / or Bluetooth function.

[0085] The following takes the example of electronic device 1 being mobile phone A, electronic device 2 being mobile phone B, electronic device 3 being mobile phone C, and the first IoT device being a large screen as an example to introduce a data processing method and electronic device provided by the embodiment of the present application. Figure 6 This invention introduces a method for binding IoT devices provided in an embodiment of the present application. Figure 6 The control application is introduced as an example of smart space application. Figure 6In the figure, mobile phone A establishes a wireless communication connection with the large screen, and mobile phone A and the large screen are in the same trust ring. The above-mentioned 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, mobile phone A and the large screen are connected to 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 with the first module such as the trust ring module. The networking module is used to implement events such as device connection and authentication. Optionally, mobile phone A and the large screen may also include collaborative applications such as a trust ring application (not shown in the figure).

[0086] The following describes this solution using the example of the smart space application being the first application, the trust ring module being the first module, and the preset module being the second module.

[0087] Exemplarily, the method may include:

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

[0089] The first registration information is used to instruct the large screen to register with the Internet of Things. Only after the Internet of Things registration is successful can mobile phone A control the large screen. Specifically, the first registration information is used to trigger the large screen to send registration information to the service server to register the first binding relationship between the large screen and mobile phone A. This registration information can be, for example, Internet of Things registration information.

[0090] Before executing S601, mobile phone A may display a device management interface. The device management interface may be, for example, Figure 1 The middle interface 102 is shown. The second operation may specifically be an operation of adding a large-screen device card in the device management interface.

[0091] Optionally, in response to adding the large screen's device card, mobile phone A can exchange device information with the large screen. During the device information exchange, mobile phone A can obtain the large screen's IoT registration information and trust ring registration information. Subsequently, mobile phone A's Smart Space application can query the service server to see whether the large screen's IoT registration information is stored. If the service server stores the large screen's IoT registration information, mobile phone A's Smart Space application can execute S604. If the service 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 service server stores the large screen's IoT registration information. If the large screen has not completed IoT registration, the service server does not store the large screen's IoT registration information. The IoT registration information may be device information used by the large screen to register with the IoT. The IoT registration information includes a first device identifier. Optionally, the IoT registration information also includes one or more of: name, brand information, manufacturer information, Media Access Control Address (MAC), product serial number (SN), certificate information, and the account used to log in to mobile phone A's Smart Space application. For example, the account logged into the smart space application of mobile phone A can be a first account such as account B.

[0092] The embodiment of the present application does not limit the specific form of the operation of adding a large-screen device card. As an example, mobile phone A displays Figure 7 The main interface of the smart space application shown is interface 01, which includes device cards of IoT devices that have been added to mobile phone A, such as device cards for headphones and devices for speakers. Interface 01 includes controls 02 such as an add button. In response to user operations on control 02, such as a click operation, mobile phone A displays interface 03 of the smart space application. Interface 03 can be a device search interface. At the same time, mobile phone A can search and discover surrounding IoT devices. After searching for surrounding IoT devices, mobile phone A can display interface 04, which includes information about surrounding IoT devices searched by mobile phone A. Figure 7 As shown in the figure, the information includes device names such as desk lamp and large screen, and also includes the models of IoT devices such as abc and edf. In response to the user's operation on the information on the large screen, such as clicking or long pressing, the mobile phone can perform Figure 6 A method for adding an IoT device is shown, and a device card of a large screen is displayed on the main interface of the smart space application, such as interface 01, as shown in interface 05. In some embodiments, the user can add a large screen by manually adding or scanning a code.

[0093] S602: In response to the first registration information, the networking module of the large screen sends a first request to the service server.

[0094] The first request is for IoT registration, i.e., IoT registration. 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. This IoT platform can be deployed on a second server. The service 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 then send feedback to mobile phone A via the IoT platform to provide feedback on the execution of the commands.

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

[0096] S603: In response to the first request, the service server registers the large screen with the Internet of Things.

[0097] If the IoT platform is deployed on a service server, the service server can authenticate the large screen in response to the first request. If the IoT platform is not deployed on the service server, the service server forwards the first request to a server deployed with the IoT platform, 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 service server.

[0098] After the identity authentication of the large screen is passed, the business server can save the IoT registration information of the large screen. For example, the business server can save the IoT registration information of the large screen in the first data set. The first data set includes the binding relationship between the electronic device, such as mobile phone A, and the large screen. For example, the business server stores the device information of mobile phone A and the IoT registration information of the large screen in the first data set. In this way, mobile phone A can be bound to the large screen, and mobile phone A and the large screen have a first binding relationship. In some embodiments, the first data set includes the first account, the device information of the control terminal logged in to the first account, such as mobile phone A, and the IoT registration information of the IoT device bound to the control terminal, such as the large screen. Moreover, 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 the smart space applications of multiple control terminals are all logged in to the first account, multiple electronic devices can control each IoT device among the multiple IoT devices corresponding to the first account.

[0099] After the identity authentication of the large screen is passed, the service server may send a first message to the large screen, where the first message is used to inform the large screen that the Internet of Things registration has been completed.

[0100] For example, the first data set may be a data table. Taking the IoT registration information including the device identifier and SN as an example, the data table may be as shown in Table 1.

[0101] Table 1

[0102] First Account Control Terminal IoT devices 152******46 Device ID of mobile phone A - SN The first device identifier of the large screen - SN

[0103] In this way, the service 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 data set indicates that mobile phone A can control the large screen.

[0104] S604: The smart space application of mobile phone A queries the service server to save the IoT registration information of the large screen, and the smart space application of mobile phone A adds the device card of the large screen on the first interface.

[0105] The Smart Space app on phone A finds that the service server has the large screen's IoT registration information. The Smart Space app on phone A then adds the large screen's device card to the first screen. The Smart Space app on phone A also saves the large screen's IoT registration information. The first screen is the device management screen.

[0106] Because mobile phone A's Smart Space app supports device collaboration, after adding the large screen's device card to the Smart Space app, if the large screen has already joined mobile phone A's trusted ring, the mobile phone can perform device collaboration with the large screen in response to the user's collaborative operation. If the large screen has not yet joined mobile phone A's trusted ring, mobile phone A can add the large screen to mobile phone A's trusted ring. For example, mobile phone A can execute S605-S610 to add the large screen to mobile phone A's trusted 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] Because the Smart Space application and the Trust Ring module are two different applications, mobile phone A can use a preset module to link 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. The business logic corresponding to the collaborative service may include device authentication, initiating collaborative services, and obtaining collaborative data. In some implementations, the preset module may be a preset interface. In other embodiments, the preset module may be a preset application, which may be an Android application package (APK).

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

[0110] Mutual authentication is used to authenticate the identity of the peer device. 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. Among them, the authentication messages (authentication message 1 and authentication message 2) may include device information. The authentication process can refer to the existing technology, and the embodiments of this application do not specifically limit this.

[0111] S607, after mutual authentication is passed, the networking module of mobile phone A reports to the trust ring module of mobile phone A that the large screen is online, and the networking module of the large screen reports to the trust ring module of the large screen that mobile phone A is online.

[0112] Afterwards, mobile phone A can determine whether the large screen has joined the trust ring where mobile phone A is located. For example, mobile phone A's networking module can query the service server for the large screen's trust ring registration information. This trust ring registration information may include, for example, the 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 logged in by mobile phone A. The device account logged in by mobile phone A may be, for example, the 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 the preset module. The trust ring module in mobile phone A can report the online status of the large screen to the smart space application through the preset module.

[0114] If the service server has the large screen's trust ring registration information, mobile phone A recognizes that the large screen has joined the same trust ring as mobile phone A. In this case, the mobile phone may not execute S608. If the service server does not have the large screen's trust ring registration information, mobile phone A recognizes that the large screen has not joined the same trust ring as mobile phone A. In this case, the mobile phone may execute S608-S610.

[0115] Specifically, when mobile phone A and the large screen log in to the same account, such as account A, both the large screen and mobile phone A can request the server to join the trust ring of the logged-in account. In this way, mobile phone A and the large screen can be electronic devices in the same trust ring. Taking mobile phone A as an example, mobile phone A logs in to the account and the device collaboration function of mobile phone A is turned on. When mobile phone A starts a device collaboration application such as a trust ring module for the first time, mobile phone A can send a request to the server, which is used to add mobile phone A to the trust ring corresponding to the account logged in by mobile phone A. The request may include the account information logged in by mobile phone A, the device information of mobile phone A, etc. In response to the request, the server can add mobile phone A to the trust ring corresponding to the account logged in by mobile phone A. Similarly, when the large screen logs in to the account and the device collaboration function of the large screen is turned on, when the large screen starts a device collaboration application such as a trust ring module for the first time, the large screen can also execute the logical method executed by mobile phone A and join the trust ring corresponding to the account logged in by the large screen. In this way, mobile phone A and the large screen can be electronic devices in the same trust ring.

[0116] This embodiment of the application uses the example of mobile phone A logging in to an account but the large screen not logging in. If mobile phone A logs in to an account but the large screen does not, and the large screen is not part of the trust ring where the mobile phone is located, mobile phone A can request the server to add the large screen to the trust ring of the account logged in 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 service 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 the second binding relationship between the large screen and mobile phone A in the service 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 in the same trust ring and have a second binding relationship.

[0120] S609: In response to the second registration information, the service server registers the large screen in the trust ring.

[0121] After the server adds the large screen to the trust ring that mobile phone A is in, the service server saves the large screen's trust ring registration information. For example, the service server can save the large screen's trust ring registration information in a second data set, which includes the large screen's trust ring registration information and the device information of electronic devices in the same trust ring as the large screen, such as mobile phone A. The service server stores mobile phone A's device information and the large screen's trust ring registration information in the second data set. In this way, mobile phone A and the large screen can be bound together, and mobile phone A and the large screen have a second binding relationship.

[0122] The first data set and the second data set both include information of the large screen, such as the trust ring registration information and the Internet of Things registration information. In this way, the first server stores two records of the large screen, such as the trust ring registration information and the Internet of Things registration information.

[0123] For example, the second data set may be a data table. Taking the trust ring registration information including the device identification and SN as an example, the data table may 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 is not specifically limited in the embodiments of the present application. 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 based on different service types. For example, developers configure a first UDID for an IoT device that supports IoT services. Developers configure a second UDID for an IoT device that supports collaborative services. Therefore, a large screen that supports both IoT and collaborative services has two different UDIDs. When the large screen registers for the 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 trusted ring module in mobile phone A sends the second registration information to the service server, the trusted ring module may first send an application to the service server, requesting a trusted ring identifier for the large screen. The trusted ring identifier uniquely identifies an electronic device within the trusted ring. Subsequently, the trusted ring module in mobile phone A and the trusted ring module in the large screen exchange information, for example, their respective trusted ring identifiers and their respective second UDIDs. After the information exchange is complete, the trusted ring module in mobile phone A may send the second registration information to the service server. In this embodiment, the second registration information may also include the large screen's trusted ring identifier.

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

[0129] The second 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 the second information to the smart space application of mobile phone A.

[0131] After receiving the second information, the smart space application of mobile phone A can respond to the user's collaborative operation in the smart space application and perform device collaboration with the large screen. In addition, the smart space application of mobile phone A can save the trust ring registration information of the large screen.

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

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

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

[0135] As can be seen, when adding the large screen device card to phone A, the service server binds phone A and the large screen twice. The service server saves two records of large screen A, including the IoT registration information and the trust ring registration information. Phone A also saves two pieces of device information for the large screen, including the IoT registration information and the trust ring registration information.

[0136] Figure 6 The process of the large screen performing the first registration of the Internet of Things and the trust ring shown is shown. When the large screen has completed the registration of the Internet of Things and the trust ring, mobile phone A can execute the following method to add the device card of the large screen. In response to the user's operation of adding the device card of the large screen on mobile phone A, the smart space application of mobile phone A queries the Internet of Things registration information of the large screen in the first data set of the business server. When the Internet of Things registration information of the large screen is queried, mobile phone A adds the device card of the large screen in the smart space application. In addition, mobile phone A can save the Internet of Things registration information of the large screen. Then, the smart space application of mobile phone A triggers the mutual authentication between the trust ring module and the large screen through the preset module. After the mutual authentication is passed, mobile phone A then queries the trust ring registration information of the large screen in the second data set of the business server. When the trust ring registration information of the large screen is queried, mobile phone A can save the trust ring registration information of the large screen.

[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 spaces of phone B and phone C. In other words, bind phone B to the large screen, and phone C to the large screen. The following describes the different scenarios.

[0138] The first method involves a mobile phone that includes a trusted ring module. Mobile phone B also includes a smart space application and a networking module. Mobile phone B logs in to an account, such as account A. The binding process can involve: mobile phone B establishing a wireless communication connection with the large screen, with both mobile phone B and the large screen within the same trusted ring. This wireless communication connection can be a Wi-Fi connection or a Bluetooth connection. Optionally, mobile phone B and the large screen establish a Wi-Fi connection, for example, if both mobile phone B and the large screen are connected to the same wireless local area network. In response to a user adding the large screen's device card on mobile phone B, the smart space application on mobile phone B queries the service server for the large screen's IoT registration information. The process of adding the large screen's device card on mobile phone B is similar to that of adding the large screen's device card on mobile phone A and will not be further described here; please refer to the previous description. Upon finding the large screen's IoT registration information, mobile phone B adds the large screen's device card to the smart space application. Furthermore, the smart space application on mobile phone B can save the large screen's IoT registration information. Because mobile phone B includes the trusted ring module, if the collaboration function on mobile phone B is enabled, mobile phone B and the large screen can mutually 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 the mutual authentication between mobile phone A and the large screen, and will not be repeated here. After the authentication is passed, the trust ring module of mobile phone B can obtain the device information of the electronic devices in the trust ring corresponding to account A from the business server. Among them, mobile phone A and mobile phone B can be in the trust ring corresponding to account A, that is, mobile phone B is in the second data set. The method for mobile phone B to join the second data set can refer to the existing trust ring networking technology, and this application will not be repeated. In the case that the electronic devices in the trust ring corresponding to account A include a large screen, the trust ring module of mobile phone B indicates that the large screen is online. In addition, the trust ring module of mobile phone B can save the trust ring registration information of the large screen. In this way, mobile phone B can have a first binding relationship and a second binding relationship with the large screen.

[0139] The second type is that mobile phone C does not include a trust ring module. Mobile phone C includes a smart space application. The binding process may include: mobile phone C establishes a wireless communication connection with the large screen, and the wireless communication connection 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, mobile phone C and the large screen are connected to the same wireless local area network. In response to the user's operation of adding the device card of the large screen on mobile phone C, the smart space application of mobile phone C queries the IoT registration information of the large screen on the service server. The operation of the user adding the device card of the large screen on mobile phone C is similar to the operation of the user adding the device card of the large screen on mobile phone A, which will not be repeated here. Please refer to the previous introduction. When the IoT registration information of the large screen is queried, mobile phone C adds the device card of the large screen to the smart space application. In addition, mobile phone C, such as the smart space application, can save the trust ring registration information of the large screen. In this way, 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 data set.

[0141] After binding mobile phone B and mobile phone C, the first data set may be as shown in Table 3.

[0142] Table 3

[0143]

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

[0145] After binding mobile phone B and mobile phone C, the second data set may be as shown in Table 4. The second data set includes binding relationships between multiple electronic devices such as mobile phone A and mobile phone B and IoT devices such as large screens, indicating that the second service can be implemented between the bound electronic devices and the IoT devices.

[0146] Table 4

[0147]

[0148] Figure 6 The process of binding an electronic device to a large screen is introduced. The following describes a data processing method provided in an embodiment of the present application in conjunction with the accompanying drawings. The method is applied to a first electronic device such as mobile phone A or mobile phone B. The first electronic device has a first binding relationship with a first IoT device such as a large screen, and the first electronic device also has a second binding relationship with the first IoT device. The first binding relationship corresponds to a first business such as an Internet of Things business, and the second binding relationship corresponds to a second business such as a device collaboration business. The first business and the second business are different businesses. The first IoT device also has a second binding relationship with at least one second electronic device. For example, the at least one second electronic device can be, for example, mobile phone A and mobile phone B. The first electronic device is one of the at least one second electronic device. Optionally, the 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 may receive a first indication message sent by the business server, and the first indication message is used to indicate that the business server has deleted the first binding relationship between the first electronic device and the first IoT device. For example, the business server may send the first indication message to the first electronic device after deleting the IoT registration information of the first IoT device in the first data set. That is, after the business server deletes the IoT registration information of the first IoT device in the first data set, the first binding relationship between the electronic device in the first data set and the first IoT device is deleted. The business server may delete the first binding relationship between all electronic devices included in the first data set and the first IoT device in response to a deletion instruction of any one of the electronic devices included in the first data set.

[0150] In response to the first indication information, the first electronic device sends a second indication information to the business server, where the second indication information is used to instruct the business server to delete the second binding relationship between the first IoT device and the at least one second electronic device. In response to the second indication information, the business server can delete the trust ring registration information of the first IoT device in the second data set, thereby deleting the second binding relationship between all electronic devices included in the second data set (i.e., the at least one second electronic device) and the first IoT device.

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

[0152] The first method: A user deletes the large-screen device card 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 an embodiment of the present application may include:

[0154] S801, mobile phone A displays the device management interface.

[0155] The device management interface can be, for example, the main interface of the smart space application, such as Figure 2 Interface 201 in. The device management interface includes a device card corresponding to the large screen, which is used to indicate that a first binding relationship exists between mobile phone A and the first IoT device.

[0156] S802 , in response to the first operation of deleting the large-screen device card, the smart space application of mobile phone A sends a request message to the service server.

[0157] The request information is used to delete the first binding relationship between the large screen, the electronic device and the mobile phone A. Specifically used to delete the IoT registration information of the large screen in the first data set. The first operation can be, for example, the user in the main interface of the smart space application such as Figure 7 Interface 01 in the diagram shows an operation on a device card on a large screen. This operation can be, for example, a long press operation or a click operation.

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

[0159] For example, the service server deletes the IoT registration information of the large screen in the first data set. Deleting the IoT registration information of the large screen in the first data set simultaneously deletes the first binding relationship between the electronic devices in the first data set, such as mobile phone A-mobile phone C, and the large screen.

[0160] After the service server deletes the first binding relationship between the large screen and mobile phones A and C, the service server may send a first indication message to the electronic devices bound to the large screen, such as mobile phones A and C, to indicate that the large screen has been deleted. Specifically, the first indication message sent to mobile phone A indicates that the first 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 first 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 first binding relationship between mobile phone C and the large screen has been deleted.

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

[0162] S805: The smart space application of mobile phone A deletes the device card and IoT registration information of the large screen in response to the first instruction information.

[0163] In response to the first instruction information, the smart space application of mobile phone A deletes the device card of the large screen and at the same time deletes the Internet of Things registration information saved 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 of the large screen.

[0165] In response to the first instruction information, the smart space application of mobile phone B deletes the device card of 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 of mobile phone C deletes the device card and IoT registration information of the large screen in response to the first instruction information.

[0167] In response to the first instruction information, the smart space application of mobile phone C deletes the device card of the large screen and deletes the Internet of Things registration information stored on the large screen of mobile phone C at the same time.

[0168] Because mobile phone A includes a preset module, after the Smart Space application deletes the large screen's device card and IoT registration information, the Smart Space application triggers the trusted ring module through the preset module to trigger the service 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 service server, instructing the service server to delete the second binding relationship between the large screen and the second electronic device, such as mobile phone A and mobile phone B.

[0169] S808, the smart space application of mobile phone A sends the second indication information to the trust ring module through the preset module.

[0170] The second indication information is used to instruct the trusted ring module to trigger the service 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 trusted ring registration information of the large screen in the first data set. For example, the smart space application on mobile phone A sends the second indication information to the preset module, and the preset module sends the second indication information to the trusted ring module.

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

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

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

[0174] S811, the business server sends third indication information to the trust circle module of the electronic device within the trust circle corresponding to account A.

[0175] The third indication information is used to indicate that the large screen has been deleted from the trust ring corresponding to account A. That is, the second binding relationship between the electronic device logged in to account A and the large screen has been released.

[0176] In response to the third instruction information, electronic devices such as mobile phone A and mobile phone B in the trust circle corresponding to account A can delete the saved trust circle registration information of 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 indication information and sends the third indication information to the smart space application through the preset module.

[0178] S813: The smart space application of mobile phone A deletes the trust ring registration information of the large screen of mobile phone A in response to the third instruction information.

[0179] S814: The trusted ring module of mobile phone B deletes the trusted ring registration information of the large screen of mobile phone B in response to the third instruction information.

[0180] In this way, the service server can delete the two records of the large screen, such as the IoT registration record and the trust ring registration record. Phone A and Phone B can delete the information of the large screen (such as the IoT registration information and the trust ring registration information). Phone C can also delete the IoT registration information. In this way, no data remains on the service server, Phone A, Phone B, and Phone C.

[0181] Second, if phone A is unusable, the user can delete the large screen in phone B or phone C. Cases where phone A is unusable include: phone A is lost, phone A is down, phone A cannot start due to a malfunction, or phone A cannot launch the Smart Space app. In other words, phone A being unusable means that phone A cannot trigger the service server to delete the first and second binding relationships.

[0182] Figure 9 A data processing method provided in an embodiment of the present application may include:

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

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

[0185] Optionally, the above method may also be: S901, in response to the user's first operation of deleting the large-screen device card, the smart space application of mobile phone B sends a request message to the service server. Before executing S901, mobile phone B may display the device management interface. The device management interface may be, for example, the main interface of the smart space application, such as Figure 2 Interface 201 in the device management interface includes a device card corresponding to the large screen, which is used to indicate that a first binding relationship exists between mobile phone B and 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 information, the service server deletes the first binding relationship between the large screen and the mobile phone C.

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

[0188] For example, in response to the request, the service server deletes the IoT registration information of the large screen in the first data set. Deleting the IoT registration information of the large screen in the first data set also deletes the first binding relationship between the electronic devices in the first data set, such as mobile phone A-mobile phone C, and the large screen.

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

[0190] Specifically, the first indication information sent to mobile phone B is used to indicate that the first binding relationship between mobile phone B and the large screen has been deleted, and the first indication information sent to mobile phone C is used to indicate that the first binding relationship between mobile phone C and the large screen has been deleted.

[0191] S904: In response to the first instruction information, the smart space application of mobile phone C deletes the device card and IoT registration information of the large screen.

[0192] When mobile phone C deletes the device card of the large screen, the IoT registration information saved on the large screen of mobile phone C will also be deleted.

[0193] S905: In response to the first instruction information, the smart space application of mobile phone B deletes the device card and IoT registration information of the large screen.

[0194] When mobile phone B deletes the device card of the large screen, the IoT registration information saved on the large screen of mobile phone B will also be deleted.

[0195] In this way, mobile phone C or mobile phone B can trigger the service server to delete the large screen's IoT registration information. Both mobile phone B and mobile phone C can delete the large screen's IoT registration information. The service server still has the large screen's trust ring registration information. Mobile phone B also has the large screen's trust ring registration information. In this case, if mobile phone B can identify whether the large screen's IoT registration information has been deleted from the service server, if it determines that the large screen's IoT registration information has been deleted from the service server, it can instruct the service server to delete the large screen's trust ring registration information.

[0196] As an example, mobile phone B can send a query request to the service server, including the first device identifier of the large screen, to inquire whether the service server still stores the large screen's IoT registration information. Based on the first device identifier in the query, the service server can query whether the large screen's IoT registration information is still stored in the first dataset. The service 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 service server.

[0197] As another example, to reduce data interaction and save power consumption, mobile phone B can obtain registration information corresponding to the first service from the service server. The registration information for the first service can be, for example, the first data set shown in Tables 2 and 4. The registration information for the first service includes binding relationships between multiple electronic devices, such as mobile phone A and mobile phone B, and IoT devices, such as large screens, indicating that the first service can be implemented between the bound electronic devices and the IoT devices.

[0198] Optionally, mobile phone B may obtain registration information corresponding to the first service from the service server when a trigger condition is met.

[0199] The trigger condition can be any of: mobile phone B switching wireless networks, logging out of the device account and then back in, disabling and then re-enabling the collaboration feature, or restarting the device. Conventional technology allows mobile phone B to obtain trusted ring data from a server when the trigger condition is met. This solution follows conventional logic and obtains the third data set from the service server when the trigger condition is met. This reduces development investment and avoids significant changes to the existing execution logic. Optionally, mobile phone B can obtain registration information corresponding to the first service and the second service from the service server when the trigger condition is met.

[0200] The following description will be made by taking the example of mobile phone B actively obtaining registration information corresponding to the first service, such as the first data set.

[0201] S906 , when the triggering condition is met, the trust ring module of mobile phone B obtains a first data set from the service server.

[0202] For example, the trust circle module of mobile phone B sends a request to the service server, where the request is used to request downloading of the first data set. In response to the request, the service server sends the first data set to the mobile phone.

[0203] S907 , the trust circle module of mobile phone B queries the first data set and finds that the first data set 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 the 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 ring module of mobile phone B can determine whether the registration information corresponding to the first service, such as the first data, includes the first binding relationship between mobile phone B and the large screen. For example, mobile phone B's trust ring module searches the first data set for the large screen's IoT registration record. Because the service server has deleted the large screen's IoT registration record from the first data set, mobile phone B's trust ring module cannot find the large screen's IoT registration record in the first data set. Therefore, mobile phone B's trust ring module searches the first data set and finds that the second binding relationship between mobile phone B and the large screen is not included.

[0206] S908: The trust ring module of mobile phone B sends second instruction information to the service server.

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

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

[0209] S910: The service server sends third indication information to the trust circle module of the electronic device within the trust circle corresponding to account A.

[0210] The third indication information is used to indicate that the large screen has been deleted 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 of the large screen. Optionally, the above method also includes:

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

[0213] In this way, when a user deletes the device card of an IoT device on an electronic device that does not support device collaboration services, such as mobile phone C, the user can delete the IoT device's IoT registration information on the service server, but cannot delete the IoT device's trust ring registration information on the service server. However, when a trigger condition is met, an electronic device that supports device collaboration services can identify whether the IoT device's IoT registration information on the service server has been deleted. If so, it will delete the IoT device's trust ring registration information on the service server.

[0214] The third method is that when mobile phone A is usable, the user can delete the large screen in mobile phone B or mobile phone C.

[0215] Figure 10 A data processing method provided in an embodiment of the present application may include:

[0216] S101 , in response to a user's first operation of deleting a large-screen device card, the smart space application of mobile phone C sends a request message to a service server.

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

[0218] Optionally, the above method may also be: S101, in response to the user's first operation of deleting the large-screen device card, the smart space application of mobile phone B sends a request message to the service server. Before executing S901, mobile phone B may display the device management interface. The device management interface may be, for example, the main interface of the smart space application, such as Figure 2 Interface 201 in the device management interface includes a device card corresponding to the large screen, which is used to indicate that a first binding relationship exists between mobile phone B and 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 information, the service server deletes the first binding relationship between the large screen and the mobile phone C.

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

[0221] Among them, S101-S102 are similar to S901-S902, which will not be repeated here. Please refer to the previous text.

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

[0223] S104: The smart space application of mobile phone A deletes the device card and IoT registration information of the large screen in response to the first instruction information.

[0224] In response to the first indication information, mobile phone A, such as the smart space application of mobile phone A, deletes the device card of the large screen and at the same time deletes the Internet of Things 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 of the large screen.

[0226] In response to the first indication information, mobile phone B, such as the smart space application of mobile phone B, deletes the device card of the large screen and at the same time deletes the Internet of Things registration information stored on the large screen of mobile phone B.

[0227] S106 , the smart space application of mobile phone C deletes the device card and IoT registration information of the large screen in response to the first instruction information.

[0228] In response to the first indication information, mobile phone C, such as the smart space application of mobile phone C, deletes the device card of the large screen and at the same time deletes the Internet of Things registration information stored on the large screen of mobile phone C.

[0229] In this way, mobile phone C or mobile phone B can trigger the business server to delete the IoT registration information of the large screen. Mobile phone A, mobile phone B, and mobile phone C can all delete the IoT registration information of the large screen. The business server still has the trust ring registration information of the large screen. Mobile phone B and mobile phone A still have the trust ring registration information of the large screen. Since mobile 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, and mobile phone A, mobile phone B, mobile phone C and the large screen can interactively execute S107-S113. Among them, S107-S113 are similar to S808-S814, please see the previous introduction for details, and will not be repeated here.

[0230] S107, the smart space application of mobile phone A sends the second indication information to the trust ring module through the preset module.

[0231] The second indication information is used to instruct the trusted ring module to trigger the service 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 trusted ring registration information of the large screen in the first data set. For example, the smart space application on mobile phone A sends the second indication information to the preset module, and the preset module sends the second indication information to the trusted ring module.

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

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

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

[0235] S110, the business server sends third indication information to the trust circle module of the electronic device within the trust circle corresponding to account A.

[0236] The third indication information is used to indicate that the large screen has been deleted from the trust ring corresponding to account A.

[0237] In response to the third instruction information, electronic devices such as mobile phone A and mobile phone B in the trust circle corresponding to account A can delete the saved trust circle registration information of 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 indication information and sends the third indication information to the smart space application through the preset module.

[0239] S112: The smart space application of mobile phone A deletes the trust ring registration information of the large screen of mobile phone A in response to the third instruction information.

[0240] S113: The trusted ring module of mobile phone B deletes the trusted ring registration information of the large screen of mobile phone B in response to the third instruction information.

[0241] In this way, phone C or phone B can trigger the service server to delete the large screen's IoT registration information. Phone A, phone B, and phone C can all delete the large screen's IoT registration information. The service server still has the large screen's Trust Ring registration information. Phones B and A also have the large screen's Trust Ring registration information. Because phone A includes a pre-set module, after phone A's Smart Space app deletes the large screen's device card, the pre-set module can delete the large screen's Trust Ring registration information from the service server.

[0242] The present 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 business, the first IoT device also has a second binding relationship with at least one second electronic device, the second binding relationship corresponds to a second business, the first business is different from the second business, and the at least one second electronic device includes the first electronic device; the first electronic device is used to receive a first indication message sent by the business server; the first indication message is used to indicate that the business server has deleted the first binding relationship; in response to the first indication message, a second indication message is sent to the business server, and the second indication message is used to instruct the business server to delete the second binding relationship. For example, the system includes a business server, mobile phone A-mobile phone C. Mobile phone A-mobile phone C are used to interact with the business server to implement a data processing method provided in an embodiment of the present application.

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

[0244] The embodiment of the present application further provides a computer storage medium, which includes computer instructions. When the computer instructions are in the above electronic device (such as Figure 4 When the method is executed on the electronic device 400 shown in the figure, the electronic device executes each function or step in the above method embodiment.

[0245] The embodiment of the present application further provides a computer program product, which, when executed on a computer, enables the computer to execute the functions or steps in the above method embodiment.

[0246] An embodiment of the present application further provides a chip system, which includes at least one processor and at least one interface circuit. The processor and the interface circuit can be interconnected via lines. For example, the interface circuit can be used to receive signals from other devices (such as a memory of an electronic device). For another example, the interface circuit can be used to send signals to other devices (such as a processor). Exemplarily, the interface circuit can read instructions stored in the memory and send the instructions to the processor. When the instruction is executed by the processor, the electronic device can perform the various steps in the above embodiments. Of course, the chip system can also include other discrete devices, which is not specifically limited in the embodiment of the present application.

[0247] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned 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 devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of modules or units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0249] Units described as separate components may or may not be physically separate, and components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0250] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0251] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes several instructions for enabling a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0252] The above content is only a specific embodiment of this application, but the scope of protection of this application is not limited to this. Any changes or replacements within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A data processing method, characterized in that: Applied to a first electronic device, the first electronic device has a first binding relationship with a first IoT device, the first binding relationship corresponding 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 corresponding to a second service, the first service and the second service are different, and the at least one second electronic device includes the first electronic device; The method comprises: receiving first indication information sent by a 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, second indication information is sent to the service server, where the second indication information is used to instruct the service 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, the first application being used to support 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 second indication information to the service server in response to the first indication information, the method further includes: Acquire registration information corresponding to the first service from the service server, the registration information including binding relationships between multiple groups of electronic devices and IoT devices, indicating that the first service can be implemented between the bound electronic devices and IoT devices; 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 acquiring, from the service server, registration information corresponding to the first service includes: When a trigger condition is met, obtaining the registration information from the service server; The trigger condition includes one or more of the following conditions: the first electronic device switches the wireless network to which it is connected, the first electronic device logs out of the device account and then logs back into the device account, the first electronic device turns off the collaborative function and then turns it back on, or the first electronic device is restarted.

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 acquiring, from the service server, registration information corresponding to the first service includes: The first module obtains the registration information from the service server; The method further comprises: The first module determines whether the registration information includes the first binding relationship.

5. The method according to claim 1, wherein The first electronic device includes a first application, and the first application is used to support 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 sending second indication information to the service server in response to the first indication information includes: In response to the first indication information, the first application triggers the first module through the second module to send the second indication information to the service server.

7. The method according to any one of claims 1 to 6, characterized in that Before receiving the first indication information sent by the service server, the method further includes: Displaying a device management interface, the device management interface including a device card corresponding to the first IoT device, for indicating that the first electronic device has the first binding relationship with the first IoT device; receiving a first operation of deleting the device card; In response to the first operation, a request message is sent to the service server, where the request message is used to request the service server to delete the first binding relationship.

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

9. The method according to any one of claims 1 to 8, characterized in that The first service is an Internet of Things service, and the second service is a device collaboration service.

10. A data processing system, characterized in that: comprising a first electronic device and a service server; The business 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 the first business; the first IoT device also has a second binding relationship with at least one second electronic device; The second binding relationship corresponds to a second service; the first service is different from the second service; and the at least one second electronic device includes the first electronic device; The first electronic device is used to receive the first indication information sent by the service server; The first indication information is used to indicate that the service server has deleted the first binding relationship; In response to the first indication information, second indication information is sent to the service server, where the second indication information is used to instruct the service server to delete the second binding relationship.

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

12. The system according to claim 10, wherein: The first electronic device is also used to obtain the registration information from the business server before sending the second indication information to the business server in response to the first indication information, if the trigger condition is met; the registration information includes binding relationships between multiple groups of electronic devices and IoT devices, which is used to indicate that the bound electronic devices and IoT devices can realize the first business; and determine 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 processor; wherein the memory is used to store computer program code, and the computer program code includes computer instructions; when the computer instructions are executed by the processor, the electronic device executes the method as described in any one of claims 1 to 9.

14. A computer-readable storage medium, characterized in that The method comprises computer instructions, which, when executed on an electronic device, cause the electronic device to execute the method according to any one of claims 1 to 9.

15. A computer program product comprising a computer program / instructions, characterized in that When the computer program / instructions are executed by a processor, the steps of the method according to any one of claims 1 to 9 are implemented.

Images