Equipment control method, communication system and related device

Abstract

The invention provides an equipment control method, a communication system and a related device, electronic equipment logs in a first cloud account and a second cloud account, but large-screen equipment does not log in the first cloud account and the second cloud account. The electronic device can bind the device information of the large-screen device with the first cloud account and the second cloud account on the cloud server. Although the large-screen device cannot complete account binding on the cloud server side by logging in the cloud account, the electronic device can help the large-screen device complete account binding on the cloud server, so that the first application installed on the electronic device can be selected through the large-screen device and projected to the large-screen device for display. Therefore, the user can conveniently and quickly use the application on the electronic equipment on the large-screen equipment.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a device control method, communication system and related apparatus. Background Technology

[0002] Currently, mobile phones and other electronic devices can interconnect with large-screen devices by logging into the same account in the same system application. However, the mobile phone and the large-screen device must be from the same manufacturer to log into the same account in the system application. If the mobile phone and the large-screen device do not have the system application developed by the same manufacturer installed, they cannot interconnect. Summary of the Invention

[0003] This application provides a device control method, a communication system, and related apparatus. The electronic device can help a large-screen device complete account binding on a cloud server, allowing the large-screen device to select a first application installed on the electronic device and project its content onto the large-screen device. This enables users to quickly and easily use applications on the electronic device on the large-screen device.

[0004] In a first aspect, embodiments of this application provide a device control method applied to an electronic device, the electronic device being logged into a first cloud account and a second cloud account; the method includes: the electronic device receiving a first broadcast packet sent by a large-screen device, the large-screen device not logged into the first cloud account and the second cloud account, the first broadcast packet including device information of the large-screen device, the device information of the large-screen device including the device name of the large-screen device; in response to the received first broadcast packet, the electronic device displaying a first discovery window, the first discovery window including the device name of the large-screen device; after receiving a first operation confirming connection to the large-screen device from a user, the electronic device sending a registration request to a cloud server, the registration request carrying the first cloud account, the second cloud account, and the third cloud account; The registration request is used to request the cloud server to bind the device information of the large screen device with the first cloud account and the second cloud account. After receiving the registration success result sent by the cloud server, the electronic device sends the application information of one or more applications installed on the electronic device to the large screen device. The application information includes application icons and application identifiers. The electronic device receives an application launch request sent by the large screen device. The application launch request carries the application identifier of the first application. The one or more applications include the first application. In response to receiving the application launch request, the electronic device sends first data to the large screen device. The first data is used to instruct the large screen device to display the interface of the first application.

[0005] The device control method provided in this application allows electronic devices to bind the device information of the large-screen device to both the first and second cloud accounts on the cloud server, even if the large-screen device is not logged into the first or second cloud account. In other words, although the large-screen device cannot complete account binding on the cloud server side by logging into a cloud account, the electronic device can help it complete account binding on the cloud server, thereby adding the large-screen device to the smart space application and into the trust ring of the electronic device. Therefore, while adding the large-screen device to the second application, the electronic device can also add it to the trust ring of the electronic device. The large-screen device and the electronic device can then trust each other. Consequently, the electronic device and the large-screen device can achieve some interconnection functions (e.g., gesture control). This also simplifies the user's operation process when using applications on the electronic device on the large-screen device, making it convenient for users to quickly use applications on the electronic device on the large-screen device.

[0006] In one possible implementation, the registration request includes a first registration request and a second registration request. The first registration request carries the first cloud account and the device information of the large-screen device, and is used to request the cloud server to bind the device information of the large-screen device to the first cloud account. The second registration request carries the second cloud account and the device information of the large-screen device, and is used to request the cloud server to bind the device information of the large-screen device to the second cloud account. The registration success result includes a first registration success result and a second registration success result. The first registration success result is used to indicate that the cloud server has successfully bound the device information of the large-screen device to the first cloud account, and the second registration success result is used to indicate that the cloud server has successfully bound the device information of the large-screen device to the second cloud account.

[0007] In this way, since the device information of the large-screen device can only be interconnected with the electronic device after the device information of the first cloud account and the second cloud account are bound together, the electronic device can bind the device information of the large-screen device to the first cloud account after the device information of the large-screen device is successfully bound to the first cloud account. This avoids the situation where the device information of the large-screen device is successfully bound to the second cloud account but not to the first cloud account, and prevents the device information of the large-screen device from being invalidly bound to the second cloud account.

[0008] In one possible implementation, sending a registration request to the cloud server includes: the electronic device sending the first registration request to the cloud server; and the electronic device sending the second registration request to the cloud server.

[0009] In one possible implementation, the electronic device receiving a registration success result from the cloud server includes: the electronic device receiving a first registration success result from the cloud server; and the electronic device receiving a second registration success result from the cloud server.

[0010] In one possible implementation, the electronic device sending the second registration request to the cloud server includes: after receiving the first registration success result from the cloud server, the electronic device sends the second registration request to the cloud server; after receiving the registration success result from the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large-screen device, including: after receiving the second registration success result from the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large-screen device.

[0011] In this way, after receiving confirmation from the user in the discovery window of the large-screen device, the electronic device can first bind a first cloud account with the device information of the large-screen device on the cloud server, thus completing the IoT registration of the large-screen device. Then, the electronic device binds a second cloud account with the device information of the large-screen device on the cloud server, thus completing the trust ring registration of the large-screen device. That is to say, although the large-screen device cannot complete the account binding on the cloud server side by logging in with a cloud account, the electronic device can help the large-screen device complete the account binding on the cloud server side.

[0012] In one possible implementation, before the electronic device sends the first registration request to the cloud server, the method further includes: the electronic device sending a first connection code request to the large-screen device, the first connection code request being used to request the large-screen device to display a first connection code page, the first connection code page including a first connection code; the electronic device receiving a first page display result sent by the large-screen device, the first page display result being used to indicate that the large-screen device has successfully displayed the first connection code page; in response to the first page display result, the electronic device displaying a first connection code input window; a second connection code entered by the user of the electronic device in the first connection code input window; the electronic device sending a first authentication request to the large-screen device, the first authentication request carrying the second connection code, the first authentication request being used to request the large-screen device to perform a first authentication on the electronic device based on the first connection code and the second connection code; the electronic device sending the first registration request to the cloud server includes: after receiving a first authentication success result sent by the large-screen device, the electronic device sending the first registration request to the cloud server, the first authentication success result being used to indicate that the large-screen device has successfully completed the first authentication of the electronic device.

[0013] In this way, before binding the primary cloud account to the device information of the large-screen device on the cloud server, the electronic device can first perform initial authentication with the large-screen device. After successful initial authentication, it indicates that the electronic device and the large-screen device have mutually authenticated. Therefore, binding the primary cloud account to the large-screen device information on the cloud server only after successful initial authentication ensures that the large-screen device has the permissions to be bound to the primary cloud account, thus improving the security between the electronic device and the large-screen device.

[0014] In one possible implementation, after receiving the first registration success result from the cloud server, the electronic device sends the second registration request to the cloud server, including: after receiving the first registration success result from the cloud server, the electronic device sends a second authentication request to the large-screen device, the second authentication request carrying the second connection code, the second authentication request being used to request the large-screen device to perform a second authentication on the electronic device based on the first connection code and the second connection code; after receiving the second authentication success result from the large-screen device, the electronic device sends the second registration request to the cloud server, the second authentication success result being used to indicate that the large-screen device has successfully completed the second authentication of the electronic device.

[0015] In this way, before binding the second cloud account to the device information of the large-screen device on the cloud server, the electronic device can first undergo a second authentication with the large-screen device. After successful second authentication, it indicates that the electronic device and the large-screen device have mutually authenticated. Therefore, binding the second cloud account to the large-screen device information on the cloud server only after successful second authentication ensures that the large-screen device has the permissions to be bound to the second cloud account, thus improving the security between the electronic device and the large-screen device.

[0016] In one possible implementation, after receiving the first registration success result from the cloud server, the electronic device sends a second authentication request to the large-screen device, including: after receiving the first registration success result from the cloud server, the electronic device sends an acquisition request to the large-screen device, the acquisition request being used to request to acquire a registration file in a specified format, the registration file including device information of the large-screen device; after receiving the registration file from the large-screen device, the electronic device sends the second authentication request to the large-screen device; wherein the second registration request carries the registration file.

[0017] In this way, during the trust ring registration process, the device information of the large-screen device needs to be packaged into a registration file in a specified format (e.g., JSON format). Therefore, after receiving the registration file from the large-screen device, the electronic device can send the second cloud account and the large-screen device's registration file to the cloud server. Upon receiving the second cloud account and the large-screen device's registration file, the cloud server can bind the second cloud account to the device information of the large-screen device, thus improving the success rate of binding the second cloud account to the device information of the large-screen device.

[0018] In one possible implementation, the method further includes: after receiving the second registration success result sent by the cloud server, the electronic device displays a first interface of the second application, the first interface of the second application including a control card of the large screen device, the control card of the large screen device including the device name and icon of the large screen device; wherein, the first cloud account is the account logged in to the second application.

[0019] In this way, after the electronic device completes the binding of the device information of the large screen device to the first cloud account and the second cloud account respectively, the electronic device displays the control card in the second application, so that the user can easily control the large screen device on the electronic device.

[0020] In one possible implementation, the first broadcast packet further includes a first service identifier and a first service identifier, wherein the first service identifier is the service identifier of the manufacturer of the electronic device, and the first service identifier is used to indicate that the first broadcast packet is used to display a discovery pop-up.

[0021] This allows electronic devices to filter out large-screen devices that can be interconnected with them through broadcast packets, preventing electronic devices from frequently displaying pop-up windows indicating the discovery of invalid devices.

[0022] In one possible implementation, the method further includes: the electronic device receiving a second operation performed by a user on the control card, the second operation being used to delete the large-screen device; in response to the second operation, the electronic device sending a first deregistration request to the cloud server, the first deregistration request carrying the first cloud account and the device information of the large-screen device, the first deregistration request being used to request the cloud server to unbind the device information of the large-screen device from the first cloud account; after receiving a first deregistration success result from the cloud server, the electronic device sending a second deregistration request to the cloud server, the first deregistration success result being used to indicate that the cloud server has successfully unbound the device information of the large-screen device from the first cloud account, the second deregistration request being used to request the cloud server to unbind the device information of the large-screen device from the second cloud account; after receiving the second deregistration success result from the cloud server, if the electronic device displays the first interface, the first interface not including the control card, the second deregistration success result being used to indicate that the cloud server has successfully unbound the device information of the large-screen device from the second cloud account.

[0023] In this way, when deleting a large-screen device from an electronic device, the device information of the large-screen device can be simultaneously unbound from the first and second cloud accounts. This ensures that the electronic device can completely delete the device information of the large-screen device, guaranteeing that the large-screen device cannot be controlled by the electronic device after deletion, thus ensuring the device security of the large-screen device.

[0024] In one possible implementation, the first data includes an image stream and an audio stream; in response to the received application launch request, the electronic device sends the first data to the large-screen device, including: in response to the received application launch request, the electronic device launches a source-side projection service and a source-side audio virtual service, and creates a virtual display screen; after creating the virtual display screen, the electronic device launches the first application, wherein, after being launched, the first application sends an image stream to the virtual display screen and an audio stream to the source-side audio framework of the electronic device; the electronic device obtains the image stream from the virtual display screen through the source-side projection service and sends the image stream to the large-screen device; the electronic device obtains the audio stream from the source-side audio framework through the source-side audio virtual service and sends the audio stream to the large-screen device.

[0025] In this way, users can control the first application installed on their electronic device on the larger screen and view the interface of the first application installed on the electronic device on the larger screen, thus improving the user experience of using the application.

[0026] In one possible implementation, the electronic device displays a first discovery window in response to the received first broadcast packet, including: in response to the received first broadcast packet, if the signal strength of the first broadcast packet is greater than a first strength threshold and the electronic device does not display a second discovery window, the electronic device displays the first discovery window, the second discovery window being different from the first discovery window.

[0027] In this way, after the electronic device receives the BLE broadcast packet from the large screen device, the large screen device's discovery window will only pop up when the electronic device is relatively close to the large screen device and the electronic device is not displaying the discovery window of other devices, thus avoiding the overlap of multiple discovery windows.

[0028] In one possible implementation, before sending the registration request to the cloud server, the method further includes: after receiving a first operation confirming the connection to the large screen device from the user, the electronic device scans for the large screen device within the local area network to which the electronic device is connected; sending the registration request to the cloud server includes: after the electronic device scans for the large screen device within the local area network, it sends the registration request to the cloud server.

[0029] In one possible implementation, before scanning the large-screen device within the local area network to which the electronic device is connected, the method further includes: after receiving the first operation, if the electronic device supports projecting the interface of an application installed on the electronic device onto the large-screen device, displaying a first privacy window, the first privacy window being used to prompt the user to agree to the first privacy policy; the electronic device receiving a third operation from the user agreeing to the first privacy policy; the scanning of the large-screen device within the local area network to which the electronic device is connected includes: in response to the third operation, the electronic device scanning the large-screen device within the local area network.

[0030] This ensures that electronic devices initiate registration for large-screen devices only after users are aware of the privacy policy, thus improving user privacy and security.

[0031] In one possible implementation, the first discovery window further includes a connection control, and the first operation is an operation performed on the connection control.

[0032] In one possible implementation, the first cloud account may be the same as or different from the second cloud account.

[0033] Secondly, embodiments of this application provide a communication system including an electronic device and a large-screen device; wherein the electronic device is logged into a first cloud account and a second cloud account, while the large-screen device is not logged into either the first cloud account or the second cloud account; the large-screen device sends a first broadcast packet to the electronic device, the first broadcast packet including the device information of the large-screen device, the device information including the device name of the large-screen device; in response to the received first broadcast packet, the electronic device displays a first discovery window, the first discovery window including the device name of the large-screen device; after receiving a first operation confirming connection to the large-screen device from a user, the electronic device sends a registration request to a cloud server, the registration request carrying the first cloud account, the second cloud account, and the device information of the large-screen device, the registration request being used to request the cloud server to register the large-screen device... The device information is bound to the first cloud account and the second cloud account; after receiving the registration success result sent by the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large screen device, the application information including application icons and application identifiers; after receiving the application information of the one or more applications, the large screen device displays the application information of the one or more applications, the one or more applications including the first application; the large screen device receives a fourth operation from the user selecting the first application; in response to the fourth operation, the large screen device sends an application launch request to the electronic device, the application launch request carrying the application identifier of the first application; in response to receiving the application launch request, the electronic device sends first data to the large screen device, the first data being used to instruct the large screen device to display the interface of the first application.

[0034] In one possible implementation, the registration request includes a first registration request and a second registration request. The first registration request carries the first cloud account and the device information of the large-screen device, and is used to request the cloud server to bind the device information of the large-screen device to the first cloud account. The second registration request carries the second cloud account and the device information of the large-screen device, and is used to request the cloud server to bind the device information of the large-screen device to the second cloud account. The registration success result includes a first registration success result and a second registration success result. The first registration success result is used to indicate that the cloud server has successfully bound the device information of the large-screen device to the first cloud account, and the second registration success result is used to indicate that the cloud server has successfully bound the device information of the large-screen device to the second cloud account.

[0035] In one possible implementation, sending a registration request to the cloud server includes: the electronic device sending the first registration request to the cloud server; and the electronic device sending the second registration request to the cloud server.

[0036] In one possible implementation, the electronic device receiving a registration success result from the cloud server includes: the electronic device receiving a first registration success result from the cloud server; and the electronic device receiving a second registration success result from the cloud server.

[0037] In one possible implementation, the electronic device sending the second registration request to the cloud server includes: after receiving the first registration success result from the cloud server, the electronic device sends the second registration request to the cloud server; after receiving the registration success result from the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large-screen device, including: after receiving the second registration success result from the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large-screen device.

[0038] In one possible implementation, before the electronic device sends the first registration request to the cloud server, the electronic device sends a first connection code request to the large-screen device. The first connection code request is used to request the large-screen device to display a first connection code page, which includes a first connection code. The electronic device receives a first page display result from the large-screen device, which indicates that the large-screen device has successfully displayed the first connection code page. In response to the first page display result, the electronic device displays a first connection code input window. The user of the electronic device inputs a second connection code in the first connection code input window. The electronic device sends a first authentication request to the large-screen device, which carries the second connection code and is used to request the large-screen device to perform a first authentication on the electronic device based on the first and second connection codes. The electronic device sending the first registration request to the cloud server includes: after receiving a first authentication success result from the large-screen device, the electronic device sends the first registration request to the cloud server, whereby the first authentication success result indicates that the large-screen device has successfully completed the first authentication of the electronic device.

[0039] In one possible implementation, after receiving the first registration success result from the cloud server, the electronic device sends the second registration request to the cloud server, including: after receiving the first registration success result from the cloud server, the electronic device sends a second authentication request to the large-screen device, the second authentication request carrying the second connection code, the second authentication request being used to request the large-screen device to perform a second authentication on the electronic device based on the first connection code and the second connection code; after receiving the second authentication success result from the large-screen device, the electronic device sends the second registration request to the cloud server, the second authentication success result being used to indicate that the large-screen device has successfully completed the second authentication of the electronic device.

[0040] In one possible implementation, after receiving the second registration success result sent by the cloud server, the electronic device displays the first interface of the second application. The first interface of the second application includes the control card of the large screen device, which includes the device name and icon of the large screen device. The first cloud account is the account logged in to the second application.

[0041] In one possible implementation, the first data includes an image stream and an audio stream; in response to the received application launch request, the electronic device sends the first data to the large-screen device, including: in response to the received application launch request, the electronic device launches a source-side projection service and a source-side audio virtual service, and creates a virtual display screen; after creating the virtual display screen, the electronic device launches the first application, wherein, after being launched, the first application sends an image stream to the virtual display screen and an audio stream to the source-side audio framework of the electronic device; the electronic device obtains the image stream from the virtual display screen through the source-side projection service and sends the image stream to the large-screen device; the electronic device obtains the audio stream from the source-side audio framework through the source-side audio virtual service and sends the audio stream to the large-screen device.

[0042] Thirdly, embodiments of this application provide an electronic device including one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store a computer program, which, when executed by the one or more processors, causes the device control method in any possible implementation of the first aspect to be executed.

[0043] Fourthly, this application provides another electronic device, including one or more functional modules for performing the device control method in any of the possible implementations of the first aspect above.

[0044] Fifthly, this application provides a chip system including a processing circuit and an interface circuit. The interface circuit is used to receive instructions and transmit them to the processing circuit, which is used to execute the instructions to perform the device control method in any possible implementation of any of the above aspects.

[0045] In a sixth aspect, this application provides a computer-readable storage medium storing a computer program that, when executed by a processor, causes the device control method in any possible implementation of the first aspect to be performed.

[0046] In a seventh aspect, embodiments of this application provide a computer program product, including a method for implementing any possible implementation of any of the above aspects when the computer program product is run on a processor.

[0047] The beneficial effects of aspects two through seven, and any possible implementation of aspects two through seven, can be referred to the beneficial effects of aspects one and any possible implementation of aspects one above, and will not be repeated here. Attached Figure Description

[0048] Figure 1 This application provides a schematic diagram of the architecture of a communication system.

[0049] Figures 2A-2Q A schematic diagram of the interface for adding and using a large-screen device to a group of first electronic devices provided in this application embodiment;

[0050] Figures 3A-3S A schematic diagram of the interface for possible scenarios during the addition and use of a large-screen device by a group of first electronic devices provided in this application embodiment;

[0051] Figures 4A-4H This is a schematic diagram of the interface for a first electronic device to share a large-screen device with a second electronic device, as provided in an embodiment of this application.

[0052] Figures 5A-5K This is a schematic diagram of the interface of a large-screen device shared by a set of second electronic devices in an embodiment of this application, whereby the first electronic device shares the interface of the device.

[0053] Figures 6A-6C This is a schematic diagram of the interface of a group of second electronic devices receiving a large-screen device shared by a first electronic device, as provided in the embodiments of this application.

[0054] Figures 7A-7F This is a schematic diagram of the interface for a set of large-screen devices to actively enable the air vision function provided in the embodiments of this application;

[0055] Figures 8A-8B This is a schematic diagram of the interface of a set of large-screen devices actively activating the air vision function in the embodiments of this application.

[0056] Figures 9A-9C This is a schematic diagram of the interface for switching between a set of large-screen devices and other devices to enable the air-viewing function in the embodiments of this application.

[0057] Figures 10A-10C This is a schematic diagram of the interface for adding a large-screen device to a set of first electronic devices provided in this application embodiment in a smart space application.

[0058] Figure 11This is a schematic diagram of the software architecture of a communication system provided in the embodiments of this application;

[0059] Figure 12 This is a schematic diagram of a screen mirroring software framework for an electronic device and a large screen device provided in an embodiment of this application;

[0060] Figure 13 This is a schematic diagram illustrating the process of the first electronic device discovering the large-screen device in the device control method provided in this application embodiment;

[0061] Figures 14A-14B This illustration shows a flowchart of the process of adding and using a large-screen device for the first time in the device control method provided in the embodiments of this application;

[0062] Figure 15 This is a schematic diagram illustrating the specific process of obtaining the registration file of a large-screen device in the device control method provided in this application embodiment;

[0063] Figure 16 This is a schematic diagram of the process of enabling the air-to-view function between the first electronic device and the large-screen device in the device control method provided in the embodiments of this application;

[0064] Figures 17A-17B This is a schematic diagram of the process of the second electronic device using the large-screen device for the first time after receiving the shared large-screen device in the device control method provided in this application embodiment;

[0065] Figure 18 This is the process by which the first electronic device actively deletes the large-screen device after adding it in the device control method provided in this application embodiment;

[0066] Figure 19 This is the process of passively deleting a large-screen device after the first electronic device has been added in the device control method provided in this application embodiment;

[0067] Figure 20 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application;

[0068] Figure 21 This is a schematic diagram of the hardware structure of a large-screen device provided in the embodiments of this application;

[0069] Figure 22 This is a schematic diagram of the hardware structure of a cloud server provided in an embodiment of this application. Detailed Implementation

[0070] The technical solutions in the embodiments of this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B; the word "and / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[0071] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.

[0072] The following describes the architecture of a communication system provided in the embodiments of this application.

[0073] Figure 1 A schematic diagram of the architecture of a communication system 10 provided in an embodiment of this application is shown.

[0074] like Figure 1 As shown, the communication system 10 may include an electronic device 100, a large-screen device 200, an electronic device 300, and a cloud server 400. Optionally, the communication system 10 may also include an electronic device 500.

[0075] Electronic device 100 can establish a communication connection with cloud server 400. Electronic device 300 can also establish a communication connection with cloud server 400. Therefore, electronic device 100 can communicate with electronic device 300 and electronic device 500 through cloud server 400.

[0076] The electronic device 100 can also establish a communication connection with the large-screen device 200. Specifically, the electronic device 100 and the large-screen device 200 can communicate via Bluetooth (including classic Bluetooth and Bluetooth Low Energy (BLE)), WLAN, etc. Optionally, the electronic device 100 and the large-screen device 200 can communicate via a cloud server 400.

[0077] In the embodiments of this application, the device type of electronic device 100, electronic device 300, or electronic device 500 can be any of the following: mobile phone, tablet computer, handheld computer, desktop computer, laptop computer, ultra-mobile personal computer (UMPC), netbook, cellular phone, personal digital assistant (PDA), as well as smart home devices such as smart screens and smart speakers, wearable devices such as smart bracelets, smartwatches, and smart glasses, extended reality (XR) devices such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), in-vehicle devices, or smart city devices, etc.

[0078] Among them, electronic devices 100, 300 and 500 may be of the same or different types.

[0079] In this application embodiment, the large-screen device 200 can be any of the following: a television, projector, tablet computer, handheld computer, desktop computer, laptop computer, super mobile personal computer, netbook, cellular phone, personal digital assistant, as well as wearable devices such as smart large screens and smart glasses, extended reality devices such as augmented reality, virtual reality, and mixed reality, in-vehicle devices, or smart city devices, etc.

[0080] The following describes some terms and concepts used in the embodiments of this application.

[0081] 1. Trust loop.

[0082] Multiple devices can establish connections with cloud server 400 by logging in with the same specified cloud account. These devices can then interact with each other through cloud server 400. Because of this mutual interaction within a trust ring, these devices form a mutually trusting system, which can be called a trust ring.

[0083] 2. Remote viewing function.

[0084] The air gesture control function can refer to the following: electronic device 100 can send application information of some applications installed on electronic device 100 to large-screen device 200. Large-screen device 200 can display an application list based on this application information. Large-screen device 200 can receive and respond to user input selecting a target application among these applications, and obtain the interface data of the target application from electronic device 100. After obtaining the interface data of the target application, large-screen device 200 can display the interface of the target application on large-screen device 200.

[0085] When multiple devices log in to the same cloud account, for example, when multiple devices are manufactured by the same company, each device logged in with that cloud account can bind the cloud account to its own device information on the cloud server 400. Therefore, after the cloud account and the device information of these multiple devices are bound, these multiple devices can trust each other. Thus, these multiple devices can be in the same trust loop.

[0086] When two devices are not logged into the same cloud account—for example, because they are not from the same manufacturer—they cannot log into the same cloud account. Or, for example, device A has a cloud account logged in, but the user has not logged into a cloud account on device B. Device A can only project the interface of its application onto device B by scanning device B's QR code. However, after scanning device B's QR code, device A can only be trusted by device B, while device B cannot be trusted by device A. Therefore, device A and device B cannot interconnect; device A can only send display data to device B for display, and device B cannot control which display data device A sends to device B.

[0087] For two devices to achieve interconnectivity features such as the gesture-based viewing function, mutual trust is required. For example, electronic device 100 and large-screen device 200 need to be in the same trust ring to trust each other. However, large-screen device 200 is not logged into its cloud account. Therefore, large-screen device 200 cannot voluntarily join the trust ring of electronic device 100. If large-screen device 200 is not joined to the trust ring of electronic device 100, certain interconnectivity features (such as the gesture-based viewing function) will be unavailable between electronic device 100 and large-screen device 200.

[0088] In the device control method provided in this application embodiment, the electronic device 100 is logged into a first cloud account and a second cloud account. However, the large-screen device 200 can obtain the device information of the large-screen device 200 after receiving a broadcast packet sent by the large-screen device 200, even without being logged into a first cloud account (e.g., cloud account A) or a second cloud account (e.g., cloud account B). After obtaining the device information of the large-screen device 200, the electronic device 100 can bind the first cloud account and the second cloud account logged into on the electronic device 100 with the device information of the large-screen device 200 on the cloud server 400. After receiving a registration success result sent by the cloud server 400, the electronic device 100 can send application information of one or more applications installed on the electronic device 100 to the large-screen device 200. The application information includes application icons and application identifiers. After receiving the application identifier of the first application (also referred to as the target application) sent by the large screen device 200, the electronic device 100 can send first data to the large screen device 200 in response to receiving the application identifier of the first application. The one or more applications include the first application, and the first data is used to instruct the large screen device to display the interface of the first application.

[0089] The first cloud account can be the account logged in to the second application (also known as the smart space application) of the electronic device 100, and the second cloud account is the account of the trust ring in which the electronic device 100 is located.

[0090] In this way, even if the large-screen device 200 is not logged into the first cloud account and the second cloud account, the electronic device 100 can still bind the device information of the large-screen device 200 to the first cloud account and the second cloud account respectively on the cloud server 400. That is to say, although the large-screen device cannot complete account binding on the cloud server side by logging into a cloud account, the electronic device can help the large-screen device complete account binding on the cloud server, thereby adding the large-screen device 200 to the smart space application and into the trust ring of the electronic device 100. Therefore, while adding the large-screen device 200 to the second application, the electronic device 100 can also add the large-screen device 200 to the trust ring of the electronic device 100. The large-screen device 200 and the electronic device 100 can then trust each other. Consequently, the electronic device 100 can achieve some interconnection functions with the large-screen device 200 (e.g., gesture view function, etc.). This also simplifies the user's operation process when using the application of the electronic device 100 on the large-screen device 200.

[0091] In one possible implementation, this embodiment of the application utilizes the process of an electronic device discovering a large-screen device in a device control method. When the electronic device 100 approaches the large-screen device 200, it receives a broadcast packet sent by the large-screen device 200. Upon receiving the broadcast packet, the electronic device 100 obtains the device information of the large-screen device 200 and displays its discovery window. This quickly guides the user to add the large-screen device 200 to the smart space application on the electronic device 100. The electronic device 100 itself helps the large-screen device 200 complete account binding on the cloud server, thereby adding the large-screen device 200 to the smart space application and placing it within the trust ring of the electronic device 100.

[0092] In one possible implementation, through the process of electronic device 100 adding and using large-screen device 200 for the first time according to the embodiments of this application, after receiving the user's input confirming the connection to the large-screen device in the discovery window of the large-screen device, electronic device 100 can first bind a first cloud account with the device information of large-screen device 200 on the IoT device cloud of cloud server 400, thereby completing the IoT registration of large-screen device 200. Then, electronic device 100 binds a second cloud account with the device information of large-screen device 200 on the trust ring device cloud of cloud server 400, thereby completing the trust ring registration of large-screen device 200. That is to say, although large-screen device 200 cannot complete the account binding on the cloud server side by logging in to a cloud account, electronic device 100 can help large-screen device complete the account binding on the cloud server side.

[0093] In this way, while adding the large-screen device 200 to the smart space application, electronic device 100 can also add the large-screen device 200 to the trust ring of electronic device 100. The large-screen device 200 and electronic device 100 can then trust each other. This allows users to securely and quickly use the applications on electronic device 100 on the large-screen device 200, and also simplifies the user's workflow when using applications on electronic device 100 on the large-screen device 200.

[0094] In one possible implementation, the process of enabling a remote viewing function between an electronic device and a large-screen device, provided by this application embodiment, involves the electronic device 100 sending application information of one or more applications installed on the large-screen device 200. Upon receiving the application information, the large-screen device 200 can draw and display the application information based on its display layout and configuration. Since the application information displayed on the large-screen device 200 is drawn by the device itself and is likely different from the display layout of the electronic device 100, if the large-screen device 200 simply sends the touch coordinates corresponding to the user's input to the electronic device 100 after receiving input from the user selecting the first application among one or more applications, the electronic device 100 cannot recognize the application being operated. Therefore, in this application, after receiving input from the user selecting the first application among one or more applications, the large-screen device 200 needs to determine the first application corresponding to the user's input based on the coordinates of the user's input, and then send the application identifier of the first application to the electronic device 100. This allows the electronic device 100 to send first data to the large-screen device after receiving the application identifier of the first application. The large-screen device 200, upon receiving the first data, can then display the interface of the first application based on the first data.

[0095] In this way, users can control the first application installed on the electronic device 100 from the large screen device 200, and view the interface of the first application installed on the electronic device 100 from the large screen device 200, thus improving the user experience of using the application.

[0096] In one possible implementation, after a user accepts a large-screen device 200 shared by electronic device 100 on electronic device 300, electronic device 300 can send an acceptance response to the IoT device cloud on cloud server 400. Upon receiving this response, the IoT device cloud on cloud server 400 can bind the device information of the large-screen device 200 with the cloud account C logged into the smart space application on electronic device 300. At this point, the device information of the large-screen device 200 is bound to at least cloud account A and cloud account C in the IoT device cloud. In this way, cloud server 400 can directly complete the IoT registration of large-screen device 200 on behalf of electronic device 300, eliminating the need for electronic device 300 to initiate IoT registration for large-screen device 200. Electronic device 300 can directly initiate trust ring registration for large-screen device 200, allowing electronic device 300 to quickly establish interconnection functions with large-screen device 200. In this way, the cloud server 400 can directly replace the electronic device 300 to complete the IoT registration of the large-screen device 200, thus eliminating the need for the electronic device 300 to initiate the IoT registration of the large-screen device 200. The electronic device 300 can directly initiate the trust ring registration of the large-screen device 200. This allows the electronic device 300 to quickly establish some interconnection functions with the large-screen device 200.

[0097] In one possible implementation, after electronic device 100 successfully adds large-screen device 200, the device information of large-screen device 200 is simultaneously bound to both cloud account A and cloud account B. Cloud account A may act as the management account for large-screen device 200, sharing it with cloud account C. In this case, the device information of large-screen device 200 is also bound to cloud account C. Therefore, after receiving input from the user to delete the added large-screen device 200 in the smart space application, electronic device 100 can first request the IoT device cloud to unbind the device information of large-screen device 200 from cloud account A. If cloud account A is the management account for large-screen device 200, the IoT device cloud will not only unbind the device information of large-screen device 200 from cloud account A, but also unbind the sharing account of cloud account A (e.g., cloud account C) from the device information of large-screen device 200. This ensures that when unbinding cloud account A from large-screen device 200, the sharing account of cloud account A is also unbound from large-screen device 200. After unbinding the device information of large-screen device 200 from cloud account A, electronic device 100 then requests to unbind the device information of large-screen device 200 from cloud account B on the Trust Ring device cloud. This way, when large-screen device 200 is deleted from electronic device 100, the binding relationship between the device information of large-screen device 200 and cloud accounts A and B can be simultaneously unbound. This ensures that electronic device 100 can completely delete the device information of large-screen device 200, guaranteeing that after large-screen device 200 is deleted by electronic device 100, it cannot be controlled by electronic device 100 or other devices, thus ensuring the security of large-screen device 200.

[0098] In one possible implementation, after the device information of the large-screen device 200 is unbound from cloud account A, the IoT device cloud of the cloud server 400 updates the IoT device list corresponding to cloud account A. The IoT device cloud can then send the updated IoT device list to devices logged into cloud account A. When electronic device 100 compares the IoT device list of cloud account A with the trust ring device list of cloud account B and determines that the device information of the large-screen device 200 has been unbound from cloud account A, it indicates that the binding relationship between cloud account A and large-screen device 200 has been severed. Therefore, electronic device 100 cannot display the control card of large-screen device 200. The user can no longer control large-screen device 200 through electronic device 100. Therefore, even if large-screen device 200 and electronic device 100 are in the same trust ring, electronic device 100 and large-screen device 200 cannot perform normal interconnection. Therefore, after determining that the device information of large-screen device 200 has been unbound from cloud account A, electronic device 100 can trigger the unbinding of the device information of large-screen device 200 from cloud account B on the trust ring device cloud. This ensures that the device information of the large-screen device 200 can be deleted from both the IoT device cloud and the trust ring device cloud, thereby guaranteeing the security of using the large-screen device 200.

[0099] The following is an exemplary description of the process by which an electronic device 100 approaches and discovers a large-screen device 200 in an embodiment of this application, and adds the large-screen device 200 to the smart space application.

[0100] Figures 2A-2Q This is a schematic diagram illustrating the interface for adding and using a large-screen device to a set of electronic devices provided in this application embodiment.

[0101] like Figure 2A As shown, the electronic device 100 can display a desktop 310. This desktop 310 displays a page containing application icons, including icons for multiple applications (e.g., weather app, stock app, calculator app, settings app, email app, gallery app, music app, video app, browser app, smart space app, etc.). A status bar 311 is displayed in the upper part of the desktop 310. This status bar 311 can include one or more indicators, such as one or more signal strength indicators for mobile communication signals (also known as cellular signals), battery status indicators, time indicators, Wi-Fi signal indicators, etc.

[0102] After being powered on, the large-screen device 200 can send broadcast information (e.g., broadcast information sent via BLE or broadcast information sent via a local area network). When the electronic device 100 is near the large-screen device 200, it can receive the broadcast information sent by the large-screen device 200. After receiving the broadcast information from the large-screen device 200, the electronic device 100 can display, for example... Figure 2B The discovery window 320 is shown.

[0103] like Figure 2B As shown, the discovery window 320 may include an icon 321 of the large-screen device 200, a device name 322 of the large-screen device 200 (e.g., "HH TV"), a prompt message 323, a "Don't show again" control 324, a "Connect" control 325, and an "OK" control 326. The prompt message 323 can be used to prompt the user to connect the electronic device 100 to the large-screen device 200. For example, the prompt message 323 can be a text prompt, such as "If you have this device, you can try clicking 'Connect' to experience the smart control service." The "Don't show again" control 324 can be used to trigger the electronic device 100 to stop displaying the discovery window 320 for a period of time. The "Connect" control 325 can be used to trigger the electronic device 100 to add the large-screen device 200. The "OK" control 326 can be used to trigger the electronic device 100 to close the discovery window 320.

[0104] Electronic device 100 can receive and respond to user input (e.g., a click) to the connection control 325, displaying, for example... Figure 2C The connection device interface 330 is shown, and a connection preparation prompt 331 is displayed on the connection device interface 330. This connection preparation prompt 331 can be used to indicate to the user that the electronic device 100 is preparing to connect to the large screen device 200.

[0105] Since the electronic device 100 has not previously added the large-screen device 200, the electronic device 100 can display the device privacy window 340.

[0106] like Figure 2D As shown, the device privacy window 340 may include the device name 341 of the large-screen device 200 (e.g., "HH TV"), a prompt message 342, an agreement control 343, and a cancellation control 344. The prompt message 342 can be used to prompt the user to agree to the user agreement and privacy policy of the large-screen device 200. The prompt message 342 can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt may be "To use the services of this device, you need to read and agree to the user agreement and privacy policy." The agreement control 343 can be used to receive the user's input agreeing to the user agreement and privacy policy of the large-screen device 200. The cancellation control 344 can be used to receive the user's input disagreeing to the user agreement and privacy policy of the large-screen device 200.

[0107] Electronic device 100 can receive and respond to user input (e.g., a click) to consent control 343, displaying, for example... Figure 2E The smart interconnected privacy window 350 is shown.

[0108] like Figure 2E As shown, the smart interconnected privacy window 350 may include a prompt message 351, an agreement control 352, and a cancellation control 353. The prompt message 351 can be used to prompt the user to agree to the user agreement and privacy policy of the smart interconnected service. The prompt message 351 can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt may be "To use the smart interconnected service, you need to read and agree to the user agreement and privacy policy of the smart interconnected service." The agreement control 352 can be used to receive the user's input indicating agreement to the user agreement and privacy policy of the smart interconnected service. The cancellation control 353 can be used to receive the user's input indicating disagreement with the user agreement and privacy policy of the smart interconnected service.

[0109] like Figure 2F As shown, the electronic device 100 can receive and respond to the user's above-mentioned... Figure 2E Input to the consent control 352 (e.g., clicking) displays a connecting prompt 332 in the device connection interface 330. This connecting prompt 332 can be used to indicate to the user the progress (e.g., 10%) of the electronic device 100 connecting to the large-screen device 200.

[0110] like Figure 2G As shown, after discovering the large-screen device 200 within the local area network, the electronic device 100 can send a connection code request to the large-screen device 200. Upon receiving the connection code request, the large-screen device 200 can display a connection code page 360. The connection code page 360 ​​may include a connection code 361 (e.g., "878787") and a prompt message 362. The prompt message 362 can be used to prompt the user to enter the connection code 361 on the electronic device 100. The prompt message 362 can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt could be "Please keep your mobile phone and TV in the same WLAN state, and enter the connection code on your mobile phone according to the instructions to enable the 'AirVision' function."

[0111] After the large-screen device 200 successfully displays the above connection code page 360, as follows: Figure 2H As shown, the electronic device 100 can display a connection code input window 370. The connection code input window 370 may include a connection code input area 371, a confirm control 372, a cancel control 373, and a virtual keyboard 374. The connection code input area 371 can be used to display the connection code entered by the user.

[0112] The electronic device 100 can receive input from the user via the virtual keyboard 374 and click the OK control 372. In response to the click of the OK control 372, the electronic device 100 can verify with the large screen device 200 whether the connection code entered by the user is the same as the connection code 361 displayed by the large screen device 200.

[0113] like Figure 2I As shown, after the electronic device 100 and the large screen device 200 verify that the connection code entered by the user is the same as the connection code 361 mentioned above, the electronic device 100 can display a connection prompt 333 in the connection device interface 330. This connection prompt 333 can be used to indicate to the user the progress (e.g., 36%) of the electronic device 100 connecting to the large screen device 200.

[0114] In one possible implementation, such as Figure 2J As shown, after the electronic device 100 and the large-screen device 200 verify that the connection code entered by the user is the same as the connection code 361, the large-screen device 200 can display a "Connecting" page 380. The "Connecting" page 380 may include a "Connecting" prompt 381. This prompt 381 can be used to inform the user that the large-screen device 200 is establishing a connection with the electronic device 100. The "Connecting" prompt 381 can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt could be "Connecting to 'Mobile Magic7'", and the product model of the electronic device 100 could be "Mobile Magic7".

[0115] In one possible implementation, after electronic device 100 and large-screen device 200 verify that the user-input connection code matches the aforementioned connection code 361, electronic device 100 can bind the device information of large-screen device 200 to cloud account A on the IoT device cloud of cloud server 400. If the device information of large-screen device 200 is successfully bound to cloud account A, then devices logged into cloud account A in the smart space application (e.g., electronic device 100 and electronic device 500) can control large-screen device 200 through the smart space application. Since large-screen device 200 can be controlled by electronic device 100 as an IoT device and can also perform interconnection functions such as the air-to-view function with electronic device 100, and interconnection functions can only be performed when electronic device 100 and large-screen device 200 are within the same trust ring, when electronic device 100 adds large-screen device 200 for the first time, it needs to bind the device information of large-screen device 200 to cloud account A not only on the IoT device cloud but also on the trust ring device cloud to cloud account B. If the device information of the large-screen device 200 is successfully bound to the cloud account B, it means that both the large-screen device 200 and the electronic device 100 are in the trust ring corresponding to the cloud account B. The electronic device 100 and the large-screen device 200 are mutually trusting devices and have the right to access each other's resources. For example, a user can operate the applications installed on the electronic device 100 on the large-screen device 200 and have the interface of the applications installed on the electronic device 100 projected onto the large-screen device 200.

[0116] like Figure 2K As shown, after electronic device 100 successfully connects to large screen device 200 within the local area network (LAN), electronic device 100 can establish a point-to-point (P2P) connection with large screen device 200 through the LAN connection. After establishing the P2P connection between electronic device 100 and large screen device 200, electronic device 100 can display a prompt message 334 on the connection interface 330. This prompt message 334 can be used to notify the user that electronic device 100 has successfully connected to large screen device 200.

[0117] Optionally, if the electronic device 100 supports the air gesture function, the electronic device 100 can also display a prompt capsule 313 on the display screen after establishing a P2P connection with the large screen device 200. For example, the prompt capsule 313 can be displayed at the top of the display screen. After the P2P connection between the electronic device 100 and the large screen device 200 is disconnected, the electronic device 100 can stop displaying the prompt capsule 313 on the display screen. The prompt capsule 313 can be used to inform the user that the electronic device 100 is currently using the air gesture function with the large screen device 200. Optionally, if the electronic device 100 does not support the air gesture function, the electronic device 100 can also choose not to display the aforementioned prompt capsule 313 on the display screen after establishing a P2P connection with the large screen device 200.

[0118] Optionally, the display screen of the electronic device 100 can be a punch-hole screen, with a front-facing camera typically placed in the punch-hole area, and the front-facing camera can be located at the top of the display screen. To fully utilize the display area, the electronic device 100 displays a notification capsule 313 around the punch-hole area at the top of the display screen. The punch-hole area can be located in the center of the notification capsule 313, while the non-center area of ​​the notification capsule 313 can display the words "AirView," the device icon or device name of the large-screen device 200, etc. Since the display color of the punch-hole area is black, the background color of the notification capsule 313 can also be set to black, making it difficult for users to notice the punch-hole area. The notification capsule 313 can also float on top of other interfaces.

[0119] like Figure 2L As shown, if the duration of the prompt message 334 displayed by the electronic device 100 in the connection device interface 330 exceeds a certain threshold, the electronic device 100 can display the device settings interface 390. This device settings interface 390 may include a family settings bar 391, a device name editing bar 392, a room addition control 393, one or more room options, and a completion control 395. The family settings bar 391 can be used to set the family to which the large-screen device 200 belongs. The device name editing bar 392 can be used to edit the name of the large-screen device 200, and the room addition control 393 can be used to add other types of room options. One or more room options can be used to receive user settings regarding the room to which the large-screen device 200 belongs. For example, one or more room options may include a living room 394, master bedroom, kitchen, dining room, bathroom, etc. Figure 2L As shown, the user can set the room to which the large-screen device 200 belongs as the living room. The completion control 395 can be used to trigger the electronic device 100 to associate with the large-screen device 200 based on the setting information filled in by the user in the device settings interface 390 (e.g., the family to which the large-screen device 200 belongs, the device name of the large-screen device 200, the room described by the large-screen device 200, etc.).

[0120] Electronic device 100 can receive user input (e.g., a click) applied to completion control 395, and in response to this input, electronic device 100 can display, for example... Figure 2M The device details interface shown is 410.

[0121] like Figure 2M As shown, the device details interface 410 may include the device name 411 of the large-screen device 200 (e.g., "HH TV"), the icon 412 of the large-screen device 200, a switch control 413, a remote control function control 414, an air gesture function control 415, and more controls 416. The switch control 413 can be used to trigger the electronic device 100 to turn the large-screen device 200 on or off. The remote control function control 414 can be used to trigger the electronic device 100 to display a remote control interface, and receive and respond to user input on the remote control interface to control the large-screen device 200. The air gesture function control 415 can be used to trigger the electronic device 300 to perform air gesture functionality with the large-screen device 200.

[0122] Since the electronic device 100 is adding the large-screen device 200 for the first time, the electronic device 100 can display a jump prompt 417 after entering the device details interface 410. This jump prompt 417 can be used to indicate to the user that they are being redirected to the remote control interface. When the duration of the jump prompt 417 exceeds a certain threshold (e.g., 3 seconds), the electronic device 100 can display something like... Figure 2N The remote control interface shown is 420.

[0123] like Figure 2N As shown, the remote control interface 420 may include a cursor control area 421, one or more control buttons, and a voice input button 423. The one or more control buttons may include a power button 422A, a volume up button 422B, a volume down button 422C, an exit button 424D, a screenshot button 422E, a home button 422F, a back button 422G, and a menu button 422H. Optionally, when the electronic device 100 first enters the remote control interface 420, the electronic device 100 may display control guidance information 424 on the remote control interface 420. This control guidance information 424 can be used to guide the user to control the large-screen device 200 on the remote control interface 420. When the electronic device 100 enters the remote control interface 420 for the first time, the electronic device 100 may not display the aforementioned control guidance information 424.

[0124] If the electronic device 100 does not support the air gesture function, the electronic device 100 can respond to the input applied to the aforementioned completion control 395 by displaying the device details interface 410, and will not display the air gesture function control 415 or the aforementioned jump prompt 417 on the device details page 410. If the electronic device 100 receives input for the remote control function control 414 on the device details page 410, the electronic device 100 can display the aforementioned... Figure 2N The remote control interface shown is 420.

[0125] like Figure 2O As shown, after the large-screen device 200 establishes a P2P connection with the electronic device 100, the large-screen device 200 can display a function introduction interface 430. This function introduction interface 430 may include introductory information 431 of the AirView function (e.g., "AirView, seamless connection, no installation required on the TV, easily use mobile desktop applications") and a start-up control 432.

[0126] The large-screen device 200 can receive and respond to user input to the start-up control 432 (e.g., clicking the start-up control 432 via the remote control interface 420 of the electronic device 100) or when it detects that the duration of the feature introduction interface 430 exceeds a duration threshold (e.g., 2 seconds), and sends an application list request to the electronic device 100 via a P2P connection. Upon receiving the application list request, the electronic device 100 can obtain application information for one or more whitelisted applications installed on the electronic device 100, and send this application information to the large-screen device 200 via a P2P connection. The application information for the whitelisted applications may include the icons and application identifiers (e.g., application names) of the whitelisted applications. After obtaining the application information for one or more whitelisted applications installed on the electronic device 100, the large-screen device 200 can display, as shown below... Figure 2P The interface 440 for the remote view function is shown.

[0127] like Figure 2PAs shown, the AirView function interface 440 may include device controls 441, more function controls 442, and a page displaying application icons. This page includes icons for one or more whitelisted applications installed on the electronic device 100. For example, the icons for the one or more whitelisted applications may include icons for weather applications, stock applications, calculator applications, email applications, gallery applications, music applications, camera applications, video applications, browser applications, dialer applications, messaging applications, and contact applications. Optionally, a page indicator 444 may be displayed below the page displaying application icons to indicate the total number of pages in the AirView function interface 440 and the positional relationship between the currently displayed page and other pages. For example, the AirView function interface 440 may include two pages; the black dot in the page indicator, located on the far left, indicates that the currently displayed page is the leftmost of the two pages. Optionally, the air gesture interface 440 may also include operation prompts 445, which can be used to prompt the user to operate on the electronic device 100 and control the switching of the currently displayed page in the air gesture interface 440. The device control 441 can display the device name 441 (e.g., "Magic7") of the electronic device 100 that is performing air gesture functionality with the large screen device 200. The device control 441 can be used to trigger the large screen device 200 to switch devices performing air gesture functionality. The more functions control 442 can be used to trigger the large screen device 200 to display controls for more sub-functions of the air gesture functionality.

[0128] When the large-screen device 200 detects that the user has selected the icon of the target application in the AirView function interface 440, in response to this input, the large-screen device 200 can send an activation request for the target application to the electronic device 100 via a P2P connection. The electronic device 100 can respond to the activation request sent by the large-screen device 200 by sending image data including the interface of the target application to the large-screen device 200 via the P2P connection. After receiving the image data including the interface of the target application, the large-screen device 200 can display the interface of the target application. Optionally, the electronic device 100 can also send audio data generated by the target application to the large-screen device 200 via a P2P connection. After receiving the audio data, the large-screen device 200 can play the audio data.

[0129] For example, when the large-screen device 200 detects user input selecting the video application icon 443, in response to this input, the large-screen device 200 can send a request to the electronic device 100 to open the video application via a P2P connection. The electronic device 100 can respond to this request by sending data including the video application's interface to the large-screen device 200 via the P2P connection. After receiving the data including the video application's interface, the large-screen device 200 can display, as shown below. Figure 2Q The video application interface shown is 446.

[0130] Figures 3A-3S This is a schematic diagram of the interface for possible scenarios during the addition and use of a large-screen device by a group of first electronic devices provided in this application embodiment.

[0131] In one possible implementation, after the electronic device 100 approaches the large-screen device 200, it can receive broadcast information sent by the large-screen device 200. Upon receiving the broadcast information from the large-screen device 200, the electronic device 100 can determine whether it has downloaded the Smart Space application. If the electronic device 100 has the Smart Space application installed, it can display the aforementioned... Figure 2B The discovery window 320 is shown.

[0132] If the electronic device 100 does not have the Smart Space application installed, the electronic device 100 can display as follows: Figure 3A The download window 450 shown is shown. This download window 450 may include an icon 451 of the large-screen device 200, a device name 452 of the large-screen device 200, a prompt message 453, a download control 454, and a cancel control 455. The prompt message 453 can be used to prompt the user to download the Smart Space application. The prompt message 453 can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt could be "Please download the Smart Space application to experience more functions." The download control 454 can be used to trigger the electronic device 100 to download and install the Smart Space application. The cancel control 455 can be used to trigger the electronic device 100 to close the download window 450. The electronic device 100 can receive user input (e.g., a click) to the download control 454. In response to this input, the electronic device 100 can download and install the Smart Space application, and log in to cloud account A in the Smart Space application according to the user's input. After logging in to cloud account A, the electronic device 100 can display the above-mentioned... Figure 2B The discovery window 320 is shown.

[0133] In one possible implementation, since the electronic device 100 needs to use Bluetooth, smart connectivity services, and WLAN functions to perform the air-to-view function with the large-screen device 200, the electronic device 100 can receive user input for the aforementioned functions. Figure 2D The input (e.g., clicking) of the consent control 343 in the device privacy window 340 shown allows the electronic device 100 to determine whether the smart connectivity service, Bluetooth function, and WLAN function on the electronic device 100 are enabled.

[0134] If the smart interconnection service, Bluetooth function, and WLAN function of electronic device 100 are all enabled, electronic device 100 can display the above. Figure 2E The smart interconnected privacy window 350 is shown.

[0135] If the WLAN function of electronic device 100 is enabled but the smart interconnection service and Bluetooth function are not enabled, electronic device 100 can display as follows: Figure 3B The shown opening window 460A may include a prompt message 461A, an activation control 462A, and a cancellation control 463A. The prompt message 461A may prompt the user to activate the smart connectivity service and Bluetooth function of the electronic device 100. The prompt message 461A may be one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt may be "To connect to a large-screen device using 'AirView,' you need to activate the device's Bluetooth and smart connectivity service." The activation control 462A may trigger the electronic device 100 to activate its smart connectivity service and Bluetooth function. The cancellation control 463A may trigger the electronic device 100 to close the opening window 460A. The electronic device 100 receives and responds to the user's input to the activation control 462A (e.g., clicking), activates the smart connectivity service and Bluetooth function, and displays the above-mentioned... Figure 2E The smart interconnected privacy window 350 is shown.

[0136] If the WLAN function, smart interconnection service, and Bluetooth function of electronic device 100 are all disabled, electronic device 100 can display the following: Figure 3CThe shown is an open window 460B. This open window 460B may include a prompt message 461B, an enable control 462B, and a cancel control 463B. The prompt message 461B can be used to prompt the user to enable the WLAN, Bluetooth, and smart connectivity services of the electronic device 100. The prompt message 461B can be any one or more of text prompts, image prompts, and video prompts. For example, the text prompt could be "To connect to a large-screen device using 'AirView,' you need to enable the local WLAN, Bluetooth, and smart connectivity services." The enable control 462B can be used to trigger the electronic device 100 to enable its smart connectivity services, WLAN, and Bluetooth functions. The cancel control 463B can be used to trigger the electronic device 100 to close the open window 460B. The electronic device 100 receives and responds to the user's input to the enable control 462B (e.g., clicking), enables the smart connectivity services, WLAN, and Bluetooth functions, and displays the aforementioned information. Figure 2E The smart interconnected privacy window 350 is shown.

[0137] If the Bluetooth function of electronic device 100 is enabled but the WLAN function and smart interconnection service are not enabled, electronic device 100 can display as follows: Figure 3D The shown opening window 460C may include a prompt message 461C, an activation control 462C, and a cancellation control 463C. The prompt message 461C prompts the user to activate the WLAN function and smart connectivity service of the electronic device 100. The prompt message 461C may be one or more of text prompts, image prompts, or video prompts; for example, the text prompt may read, "To connect to a large-screen device using 'AirView,' you need to activate the local WLAN and smart connectivity services." The activation control 462C triggers the electronic device 100 to activate its smart connectivity service and WLAN function. The cancellation control 463C triggers the electronic device 100 to close the opening window 460C. The electronic device 100 receives and responds to user input to the activation control 462C (e.g., clicking), activates the smart connectivity service and WLAN function, and displays the above-mentioned... Figure 2E The smart interconnected privacy window 350 is shown.

[0138] If the Bluetooth and WLAN functions of electronic device 100 are both enabled, but the smart interconnection service is not enabled, then electronic device 100 can display as follows: Figure 3EThe shown window 460D can be opened. This window 460D may include a prompt message 461D, an activation control 462D, and a cancellation control 463D. The prompt message 461D can be used to prompt the user to activate the smart interconnection service of the electronic device 100. The prompt message 461D can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt could be "To connect to a large-screen device using 'AirView,' you need to activate the smart interconnection service on this device." The activation control 462D can be used to trigger the electronic device 100 to activate its smart interconnection service. The cancellation control 463D can be used to trigger the electronic device 100 to close the window 460D. The electronic device 100 receives and responds to the user's input to the activation control 462D (e.g., clicking), activates the smart interconnection service, and displays the above-mentioned... Figure 2E The smart interconnected privacy window 350 is shown.

[0139] If the smart connectivity service and WLAN function of electronic device 100 are enabled but the Bluetooth function is not enabled, electronic device 100 can display as follows: Figure 3F The shown window 460E can be opened. This window 460E may include a prompt message 461E, an enable control 462E, and a cancel control 463E. The prompt message 461E can prompt the user to enable the Bluetooth function of the electronic device 100. The prompt message 461E can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt could be “'Smart Space Application' requires Bluetooth to be enabled to discover and add devices. Enable it?” The enable control 462E can be used to trigger the electronic device 100 to enable its Bluetooth function. The cancel control 463E can be used to trigger the electronic device 100 to close the window 460E. The electronic device 100 receives and responds to user input to the enable control 462E (e.g., clicking), enables the Bluetooth function, and displays the above-mentioned prompt message. Figure 2E The smart interconnected privacy window 350 is shown.

[0140] If the smart connectivity service and Bluetooth function of electronic device 100 are enabled but the WLAN function is not enabled, electronic device 100 can display as follows: Figure 3GThe shown window 460F is an open window. This open window 460F may include a prompt message 461F, an enable control 462F, and a cancel control 463F. The prompt message 461F can be used to prompt the user to enable the Bluetooth function of the electronic device 100. The prompt message 461F can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt could be “'Smart Space Application' requires WLAN to be enabled to discover and add devices. Enable it?” The enable control 462F can be used to trigger the electronic device 100 to enable its WLAN function. The cancel control 463F can be used to trigger the electronic device 100 to close the open window 460F. The electronic device 100 receives and responds to the user's input to the enable control 462F (e.g., clicking), enables the WLAN function, and displays the above-mentioned... Figure 2E The smart interconnected privacy window 350 is shown.

[0141] If the smart interconnection service of electronic device 100 is enabled but the WLAN and Bluetooth functions are not enabled, electronic device 100 can display the following: Figure 3H The shown window 460G can be opened. This window 460G may include a prompt message 461G, an enable control 462G, and a cancel control 463G. The prompt message 461G can prompt the user to enable the Bluetooth function of the electronic device 100. The prompt message 461G can be one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt could be “'Smart Space Application' requires WLAN and Bluetooth to be enabled to discover and add devices. Enable?” The enable control 462G can trigger the electronic device 100 to enable its WLAN and Bluetooth functions. The cancel control 463G can trigger the electronic device 100 to close the window 460G. The electronic device 100 receives and responds to user input to the enable control 462G (e.g., clicking), enables the WLAN and Bluetooth functions, and displays the above-mentioned prompt message. Figure 2E The smart interconnected privacy window 350 is shown.

[0142] In one possible implementation, the electronic device 100 receives the user's... Figure 2H After entering the connection code in the connection code input window 370 and clicking the OK control 372, the electronic device 100 can establish a P2P connection with the large screen device 200 through the connection code entered by the user.

[0143] like Figure 3IAs shown, if the electronic device 100 fails to establish a P2P connection with the large screen device 200 due to reasons such as Bluetooth being turned off, WLAN being turned off, or the large screen device 200 verifying that the connection code entered by the user is different from the aforementioned connection code 361, the electronic device 100 can display a connection failure message 335, a solution message 336, a retry control 337, and a cancellation control 338 in the connection device interface 330. The connection failure message 335 can be used to inform the user that the connection between the electronic device 100 and the large screen device 200 has failed. The solution message 336 can be used to inform the user of the operation method after a successful connection. The retry control 337 can be used to trigger the electronic device 100 to re-display the aforementioned... Figure 2H The connection code input window 370 is shown. The cancellation control 338 can be used to trigger the electronic device 100 to cancel adding the large screen device 200 to the smart space application.

[0144] When electronic device 100 fails to establish a P2P connection with large screen device 200, such as Figure 3J As shown, the large-screen device 200 can display a connection error page 480. This connection error page 480 may include a connection error message 481 and a notification control 482. The connection error message 481 can be used to prompt the user to check the cause of the connection error. The notification control 482 can be used to trigger the electronic device 100 to redisplay the above-described connection error. Figure 2G The connection code page 360 ​​is shown, and the connection code is redisplayed on the connection code page 360. The redisplayed connection code may be the same as or different from the previously displayed connection code.

[0145] In one possible implementation, if the electronic device 100 does not support the air gesture control function, the large-screen device 200, after successfully connecting to the electronic device 100, can display something like... Figure 3K The shown interface is a function introduction screen 470. This interface may include information 471 introducing the remote control functions (e.g., "Air mouse remote control, flexible touch control, easily achieve selection, sliding, dragging, and other control methods") but does not include information about the AirView function. Optionally, the interface may also include a device model viewing prompt 472, which can be used to prompt the user to view the types of devices that support the AirView function.

[0146] In one possible implementation, such as Figure 3LAs shown, when the electronic device 100 approaches the large-screen device 200 and receives a broadcast message from the large-screen device 200, if the electronic device 100 receives and responds to user input (e.g., swiping down from the top of the display screen), it displays a notification interface 483. The electronic device 100 can display a discovery notification 484 on the notification interface 483. This discovery notification 484 may include discovery information 485, which can be used to notify the user that the large-screen device 200 has been discovered. The electronic device 100 can receive and respond to user input on the discovery notification 484 (e.g., clicking), expanding the discovery notification 484 as shown... Figure 3M The discovery details notification 486 is shown. This notification 486 may include a discovery prompt 487, a connection control 488, and an ignore control 489. The discovery prompt 487 can be used to notify the user that the large-screen device 200 has been discovered. The connection control 488 can be used to trigger the electronic device 100 to connect to the large-screen device 200. The ignore control 489 can be used to trigger the electronic device 100 to close the discovery details notification 486.

[0147] In one possible implementation, when the electronic device 100 exits the above... Figure 2N Even after the remote control interface 420 is displayed, the electronic device 100 can still display the aforementioned prompt capsule 313 on the screen. For example, as shown... Figure 3N As shown, when electronic device 100 exits the above... Figure 2N When the remote control interface 420 is displayed and the desktop 310 is shown, the electronic device 100 can display a prompt capsule 313 on the screen. For example... Figure 3O As shown, the electronic device 100 can receive and respond to user input on the aforementioned prompt capsule 313 (e.g., a click), cancel the display of the prompt capsule 313, and display a notification box 314 on the screen. The notification box 314 may include a prompt message 315, a disconnection control 316, and a remote control control 317. The prompt message 315 can be used to inform the user that the electronic device 100 has activated the AirView function with the large screen device 200. The disconnection control 316 can be used to trigger the electronic device 100 to disconnect the P2P connection with the large screen device 200. The remote control control 317 can be used to trigger the electronic device 100 to display the aforementioned... Figure 2N The remote control interface shown is 420.

[0148] In one possible implementation, such as Figure 3PAs shown, after the electronic device 100 establishes a P2P connection with the large-screen device 200, if the electronic device 100 displays a notification interface 483, the electronic device 100 can display an AirView notification 490A in the notification interface 483. The AirView notification 490A may include a prompt message 491A, a disconnection control 492A, and a remote control control 493A. The prompt message 491A can be used to notify the user that the electronic device 100 has enabled the AirView function with the large-screen device 200. The disconnection control 492A can be used to trigger the electronic device 100 to disconnect the P2P connection with the large-screen device 200. The remote control control 493A can be used to trigger the electronic device 100 to display the aforementioned notification. Figure 2N The remote control interface shown is 420.

[0149] In one possible implementation, if the device information of the large-screen device 200 and the cloud account B used by the smart interconnection service of the electronic device 100 are successfully bound on the trust ring device cloud on the cloud server 400, it indicates that the large-screen device 200 has joined the trust ring of the cloud account B. Therefore, when the electronic device 100 detects that the large-screen device 200 is online within the local area network, the electronic device 100 can display the device options of the large-screen device 200 in the smart interconnection interface. Since the electronic device 100 can quickly invoke the smart interconnection interface through user input regardless of the interface displayed, displaying the device options of the large-screen device 200 in the smart interconnection interface can quickly trigger the air-to-view functionality between the electronic device 100 and the large-screen device 200.

[0150] For example, electronic device 100 can receive a swipe operation from a user at the top of the display screen (e.g., swiping down from the top right side of the display screen), and in response to this operation, electronic device 100 can display as shown in the image. Figure 3Q The control center interface shown is 490B.

[0151] like Figure 3Q As shown, the control center interface 490B may include one or more functional controls (e.g., a wireless local area network (WLAN) switch control, a Bluetooth switch control, a low power mode switch control, a brightness adjustment control, and a volume adjustment control), a music control card, and a smart interconnection control card 491B.

[0152] Electronic device 100 can receive user operations (e.g., clicks) on the smart interconnected control card 491B, and in response to the operation, electronic device 100 can display, for example... Figure 3R The smart interconnected interface shown is 490C.

[0153] like Figure 3RAs shown, the smart interconnection interface 490C may include device options 491C for electronic device 100 and an avatar 493C for cloud account B used by the smart interconnection service on electronic device 100. After obtaining online information of other devices within the trust ring of cloud account B, electronic device 100 can display device options for other devices logged in or bound to cloud account B in the smart interconnection interface 490C. Other devices logged in or bound to cloud account B may include large-screen device 200. For example, after electronic device 100 discovers that large-screen device 200 is online in the local area network, it can display device option 492C for printer 200 in the smart interconnection interface 490C.

[0154] like Figure 3S As shown, the electronic device 100 can receive a drag operation from the user to move device option 492C to the area where device option 491C is located. In response to the user's drag operation, the electronic device 100 can return to the display of the above-mentioned device option 491C. Figure 3N The desktop 310 shown above is displayed on the screen. Figure 3N The prompt capsule 313 is shown.

[0155] The following is an exemplary description of the process by which the electronic device 100 shares the large-screen device 200 with the electronic device 300 after adding the large-screen device 200 in an embodiment of this application.

[0156] Figures 4A-4H This is a schematic diagram of the interface provided in this application embodiment, showing a first electronic device sharing a large-screen device with a second electronic device.

[0157] When the electronic device 100 receives the above Figure 2L After completing control 395 as shown, electronic device 100 can add large screen device 200 to the smart space application.

[0158] like Figure 4A As shown, after adding the large-screen device 200 to the Smart Space application, if the electronic device 100 receives input from the user to open the main interface 510 of the Smart Space application, in response to this input, the electronic device 100 can display the control card 511 of the large-screen device 200 on the main interface 510. The main interface 510 may also display the cloud account (e.g., "186xxxxxx54") that the electronic device 100 is logged into in the Smart Space application. The control card 511 may display the device name (e.g., "HH TV") and icon of the large-screen device 200. Optionally, the control card 511 may also display the on or off status of the large-screen device 200.

[0159] Electronic device 100 can receive user input to the control card 511 (e.g., long press), and in response to the input, electronic device 100 can display, for example, Figure 4B The shortcut menu shown is 512.

[0160] like Figure 4B As shown, the shortcut menu 512 may include a share device control 513 and a delete device control 514. Optionally, the shortcut menu 512 may also include an add to desktop control and an add to top frequently used controls. The share device control 513 can be used to trigger the electronic device 100 to share the large-screen device 200 with other devices. The delete device control 514 can be used to trigger the electronic device 100 to delete the control card 511 of the large-screen device 200 in the Smart Space application. The add to desktop control can be used to trigger the electronic device 100 to add the control card 511 to the desktop. The add to top frequently used controls can be used to trigger the electronic device 100 to add the control card 511 to the top of the main interface 510 of the Smart Space application.

[0161] Electronic device 100 can receive and respond to user input (e.g., a click) to the shared device control 513, displaying, for example... Figure 4C The sharing method selection interface shown is 520.

[0162] like Figure 4C As shown, the sharing method selection interface 520 may include a QR code sharing option 521 and a cloud account addition option 522. The QR code sharing option 521 can be used to trigger the electronic device 100 to scan a QR code using its camera and share the large-screen device 200 with the device corresponding to the QR code. The cloud account addition option 522 can be used to trigger the electronic device 100 to share the large-screen device 200 with the device corresponding to the cloud account entered by the user.

[0163] Electronic device 100 can receive input from the user to add an option to the cloud account (e.g., a click), and in response to this input, electronic device 100 can display, as shown below. Figure 4D The cloud account addition interface shown is 530.

[0164] like Figure 4D As shown, the cloud account addition interface 530 may include a cloud account input box 531, a contact control 532, and a confirmation control 533. The cloud account input box 531 can be used to display the shared cloud account entered by the user. The contact control 532 can be used to trigger the electronic device 100 to display the cloud account corresponding to a contact in the contact list, allowing the user to select the shared cloud account corresponding to the contact being shared with.

[0165] like Figure 4EAs shown, after receiving the shared cloud account (e.g., "180xxxxxx49") entered by the user in the cloud account input box 531, the electronic device 100 can receive and respond to the user's input (e.g., click) on the confirmation control 533, and the electronic device 100 can display as shown in the image. Figure 4F The sharing interface shown is 540.

[0166] like Figure 4F As shown, the sharing interface 540 may include the user-inputted shared cloud account (e.g., "180xxxxxx49"), the device name 542 of the large-screen device 200 (e.g., "HH TV"), a sharing control 543, and a cancellation control 544. The sharing control 543 can be used to trigger the electronic device 100 to share the large-screen device 200 with devices logged into the Smart Space application with the shared cloud account. The cancellation control 544 can be used to trigger the electronic device 100 to cancel sharing with the large-screen device 200.

[0167] Electronic device 100 can receive and respond to user input (e.g., a click) on shared control 543, and send a sharing request via cloud server 400 to electronic device 300 that is logged into the shared cloud account in the smart space application. This sharing request is used to request the sharing of device information of large screen device 200 to electronic device 300.

[0168] In one possible implementation, the electronic device 100 can receive and respond to the user's above-mentioned... Figure 4A Another input (e.g., a click) to the control card 511 in the main interface 510 shown can trigger the electronic device 100 to display, in response to which the device can display, as shown in the image. Figure 4G The device details interface 410 is shown below. For a textual description of the device details interface 410, please refer to the above. Figure 2M The textual details of the illustrated embodiment will not be repeated here. The electronic device 100 can receive and respond to user input on the more controls 416 in the device details interface 410, displaying, for example... Figure 4H The menu 550 shown may include a share device control 551 and a delete device control 552. Optionally, the shortcut menu 550 may also include an add to desktop control. The share device control 551 can be used to trigger the electronic device 100 to share the large-screen device 200 with other devices. The delete device control 552 can be used to trigger the electronic device 100 to delete the control card 511 of the large-screen device 200 in the Smart Space application. The add to desktop control can be used to trigger the electronic device 100 to add the control card 511 to the desktop. The electronic device 100 can receive and respond to user input (e.g., a click) to the share device control 551, displaying the above... Figure 4CThe sharing method selection interface 520 is shown below. For a textual description of this sharing method selection interface 520, please refer to the above. Figure 4C The textual details of the illustrated embodiments will not be repeated here.

[0169] The following is an exemplary description of the process by which electronic device 300 accepts and adds large-screen device 200 shared by electronic device 100 in an embodiment of this application.

[0170] Figures 5A-5K This is a schematic diagram of the interface of a large-screen device shared by a first electronic device and a group of second electronic devices provided in this application embodiment.

[0171] like Figure 5A As shown, electronic device 300 can display the main interface 560 of the smart space application. This main interface 560 displays the cloud account C (e.g., "180xxxxxx49") that electronic device 300 is logged into in the smart space application. After receiving a sharing request from electronic device 100, which is relayed through the IoT device cloud via cloud server 400, electronic device 300 can display a sharing notification 561. This sharing notification 561 can include a sharing prompt 562, an accept control 563, a reject control 564, and a view control 565. The sharing prompt 562 can be used to notify the user that a device has been shared by another account. This sharing prompt 562 can be one or more of the following: text prompt, image prompt, video prompt, etc. For example, the text prompt could be "186xxxxxx54 has shared a device with you, do you accept?".

[0172] like Figure 5B As shown, the electronic device 100 can receive and respond to user input (e.g., a click) applied to the aforementioned receiving control 563, displaying a control card 566 of the large-screen device 200 on the main interface 560 of the smart space application. The control card 566 can display the device name (e.g., "HH TV") and icon of the large-screen device 200. Optionally, the control card 566 can also display the on or off status of the large-screen device 200.

[0173] Electronic device 300 can receive and respond to user input (e.g., a click) to the control card 566, displaying, for example... Figure 5C The device details page shown is 570.

[0174] like Figure 5CAs shown, the device details interface 570 may include the device name 571 of the large-screen device 200 (e.g., "HH TV"), the icon 572 of the large-screen device 200, a switch control 573, an air gesture control 574, a remote control control 575, and more controls 576. The switch control 573 can be used to trigger the electronic device 100 to turn the large-screen device 200 on or off. The remote control control 575 can be used to trigger the electronic device 100 to display a remote control interface, and receive and respond to user input on the remote control interface to control the large-screen device 200. The air gesture control 574 can be used to enable air gesture functionality between the electronic device 300 and the large-screen device 200.

[0175] Optionally, if the electronic device 100 does not support the air vision function, the electronic device 100 may not display the air vision function control 574 in the device details interface 410.

[0176] Optionally, since the electronic device 300 needs to obtain user authorization and consent to use the user agreement and privacy policy of the large-screen device 200 before it can normally use the remote control function and the air gesture function, when the electronic device 300 first opens the device details interface 570 of the large-screen device 200. Therefore, when the electronic device 300 first displays the device details interface 570, it can display as follows: Figure 5C The device privacy window 580 shown may include the device name 581 of the large-screen device 200 (e.g., "HH TV"), a prompt message 582, an agreement control 583, and a cancellation control 584. The prompt message 582 may prompt the user to agree to the user agreement and privacy policy of the large-screen device 200. The prompt message 582 may be one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt may be "To use the services of this device, you need to read and agree to the user agreement and privacy policy." The agreement control 583 may be used to receive the user's input agreeing to the user agreement and privacy policy of the large-screen device 200. The cancellation control 584 may be used to receive the user's input disagreeing with the user agreement and privacy policy of the large-screen device 200. The electronic device 100 may receive and respond to the user's input to the agreement control 583 (e.g., clicking) and continue displaying the aforementioned device details interface 570.

[0177] like Figure 5D As shown, the electronic device 300 can receive and respond to user input (e.g., clicking) to the consent control 583, and the aforementioned air gesture control 574 and remote control control 575 can be triggered by user input. The electronic device 300 can receive and respond to user input (e.g., clicking) to the air gesture control 574, displaying... Figure 5E The interface shown is 590, which introduces the remote view function.

[0178] like Figure 5E As shown, the interface 590 for the AirView function introduction can include AirView function introduction information 591 and operation guidance information 592. For example, the AirView function introduction information 591 can include the text "Seamlessly connect to the TV to use the mobile application" and "No installation required on the TV, the mobile application can be easily shared to the TV, and you can view the mobile application's chat messages, news, application videos, etc." The operation guidance information 592 can be used to guide the user to keep the screen of the electronic device 300 on, Bluetooth and WLAN functions enabled, and the electronic device 300 and the large-screen device 200 connected to the same local area network. Since the electronic device 300 has not yet added the large-screen device 200 to the trust ring corresponding to the cloud account D used by the smart interconnection service on the electronic device 300 after receiving the large-screen device 200 shared by the electronic device 100, the electronic device 300 can also display the "Experience Now" control 593 on the AirView function introduction interface 590. The instant experience control 593 can be used to trigger the electronic device 300 to obtain the user's authorization to add the large screen device 200 to the trust ring corresponding to the cloud account D used for the smart interconnection service on the electronic device 300.

[0179] Electronic device 300 can receive and respond to user input (e.g., a click) on the immediate experience control 593, displaying, for example... Figure 5F The smart interconnected privacy window shown is 594.

[0180] like Figure 5F As shown, the Smart Connectivity Privacy Window 594 may include a prompt message 595, an agreement control 596, and a cancellation control 597. The prompt message 595 can be used to prompt the user to agree to the user agreement and privacy policy of the Smart Connectivity service. The prompt message 595 can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt may be "To use the Smart Connectivity service, you need to read and agree to the Smart Connectivity service's user agreement and privacy policy." The agreement control 596 can be used to receive the user's input indicating agreement to the Smart Connectivity service's user agreement and privacy policy. The cancellation control 597 can be used to receive the user's input indicating disagreement with the Smart Connectivity service's user agreement and privacy policy.

[0181] Electronic device 100 can receive and respond to user input to consent control 596 (e.g., click), can search for large screen device 200 within the local area network, and after connecting to large screen device 200 within the local area network, send a connection code request to large screen device 200.

[0182] like Figure 5GAs shown, after receiving a connection code request, the large-screen device 200 can display a connection code page 610. The connection code page 610 can include a connection code 611 and a prompt message 612. The prompt message 612 can be used to prompt the user to enter the connection code 611 on the electronic device 300. The prompt message 612 can be any one or more of text prompts, image prompts, video prompts, etc. For example, the text prompt could be "Please keep your mobile phone and TV in the same WLAN state, and enter the connection code on your mobile phone according to the instructions to enable the 'AirVision' function."

[0183] After the large-screen device 200 successfully displays the above connection code page 610, as follows: Figure 5H As shown, the electronic device 300 can display a connection code input window 620. The connection code input window 620 may include a connection code input area 621, a confirm control 622, a cancel control 623, and a virtual keyboard 624. The connection code input area 621 can be used to display the connection code entered by the user.

[0184] Electronic device 300 can receive input from a user via virtual keyboard 624 and click the OK control 622. In response to the click of the OK control 622, electronic device 100 can verify with large screen device 200 whether the connection code entered by the user is the same as the connection code 611 displayed by large screen device 200.

[0185] like Figure 5I As shown, after the electronic device 300 and the large screen device 200 verify that the connection code entered by the user is the same as the connection code 361 mentioned above, the electronic device 300 can jump to the air gesture function introduction interface 590 and display a "Starting" prompt 631. This "Starting" prompt 631 can be used to remind the user that the air gesture function is being started.

[0186] In one possible implementation, the electronic device 300 receives the user's action on the above... Figure 5A Upon receiving input from the accept control 563, the electronic device 300 can respond by sending an acceptance response to the IoT device cloud on the cloud server 400. After receiving this acceptance response, the IoT device cloud on the cloud server 400 can bind the device information of the large-screen device 200 to the cloud account C logged into the smart space application on the electronic device 300. At this point, the device information of the large-screen device 200 is bound to at least cloud account A and cloud account C in the IoT device cloud. Therefore, both the electronic device 100 logged into cloud account A in the smart space application and the electronic device 300 logged into cloud account C in the smart space application can control the large-screen device 200.

[0187] Once the electronic device 300 and the large-screen device 200 verify that the connection code entered by the user matches the aforementioned connection code 611, the electronic device 300 can bind the device information of the large-screen device 200 with the cloud account D used by the smart interconnection service of the electronic device 300 on the trust ring device cloud on the cloud server 400. If the device information of the large-screen device 200 and the cloud account D used by the smart interconnection service of the electronic device 300 are successfully bound on the trust ring device cloud on the cloud server 400, it means that the large-screen device 200 has joined the trust ring of the cloud account D. Therefore, the electronic device 300 and the large-screen device 200 can be in the same trust ring, and the electronic device 300 and the large-screen device 200 have the right to access each other's resources. For example, the user can operate the applications installed on the electronic device 300 on the large-screen device 200 and have the interface of the applications installed on the electronic device 300 projected onto the large-screen device 200 for display.

[0188] Optionally, the cloud account C logged in to the smart space application of the aforementioned electronic device 300 may be the same as or different from the cloud account D used for the smart interconnection service of the electronic device 300.

[0189] After the device information of the large screen device 200 and the cloud account D used for the smart interconnection service of the electronic device 300 are successfully bound on the trust ring device cloud on the cloud server 400, the electronic device 300 can establish a P2P connection with the large screen device 200.

[0190] like Figure 5J As shown, after the electronic device 300 establishes a P2P connection with the large-screen device 200, the large-screen device 200 can display a remote control interface 640. This remote control interface 640 may include a cursor control area 641, one or more control buttons, and a voice input button 643. The one or more control buttons may include a power button 642A, a volume up button 642B, a volume down button 642C, an exit button 642D, a screenshot button 642E, a home button 642F, a back button 642G, and a menu button 642H. Optionally, when the electronic device 300 first enters the remote control interface 640, the electronic device 100 may display control guidance information 644 on the remote control interface 640. This control guidance information 644 can be used to guide the user to control the large-screen device 200 on the remote control interface 640. When the electronic device 300 enters the remote control interface 640 for the first time, the electronic device 100 may not display the aforementioned control guidance information 644.

[0191] Optionally, if the electronic device 300 supports the air gesture control function, the electronic device 300 can also display a prompt capsule 632 on the display screen after establishing a P2P connection with the large screen device 200. For example, the prompt capsule 632 can be displayed at the top of the display screen. After the P2P connection between the electronic device 300 and the large screen device 200 is disconnected, the electronic device 300 can stop displaying the prompt capsule 632 on the display screen. The prompt capsule 632 can be used to inform the user that the electronic device 300 is currently using the air gesture control function with the large screen device 200. Optionally, if the electronic device 300 does not support the air gesture control function, the electronic device 300 can also choose not to display the aforementioned prompt capsule 632 on the display screen after establishing a P2P connection with the large screen device 200.

[0192] After the large-screen device 200 establishes a P2P connection with the electronic device 300, the large-screen device 200 can display the above-mentioned... Figure 2O The large-screen device 200 can receive and respond to user input to the start-up control 432 in the function introduction interface 430 (e.g., clicking the start-up control 432 via the remote control interface 420 of the electronic device 300 or via other remote control devices) or when it detects that the display duration of the function introduction interface 430 exceeds a certain threshold (e.g., 2 seconds), and sends an application list request to the electronic device 300 via a P2P connection. After receiving the application list request, the electronic device 300 can obtain application information of one or more whitelisted applications installed on the electronic device 300, and send this application information to the large-screen device 200 via a P2P connection. The application information of the whitelisted applications may include the icons and application identifiers (e.g., application names) of the whitelisted applications. After obtaining the application information of one or more whitelisted applications installed on the electronic device 300, the large-screen device 200 can display as shown below. Figure 5K The interface for the remote view function is shown as 650.

[0193] like Figure 5KAs shown, the AirView function interface 650 may include device controls 651, more function controls 652, and pages displaying application icons. These pages include icons for one or more whitelisted applications installed on the electronic device 300. For example, the icons for these whitelisted applications may include icons for a gallery application, a music application, a camera application, a video application, a browser application, a dialer application, a messaging application, a contacts application, etc. Optionally, a page indicator 654 may be displayed below the page displaying application icons to indicate the total number of pages in the AirView function interface 650 and the positional relationship between the currently displayed page and other pages. For example, the AirView function interface 650 may include two pages; the black dot in the page indicator, located on the far left, indicates that the currently displayed page is the leftmost of the two pages. Optionally, the air gesture interface 650 may also include an operation prompt 655, which can be used to prompt the user to operate on the electronic device 300 and control the switching of the currently displayed page in the air gesture interface 650. The device control 651 can display the device name 651 (e.g., "Magic6") of the electronic device 300 that is performing air gesture functionality with the large screen device 200. The device control 651 can be used to trigger the large screen device 200 to switch devices performing air gesture functionality. The more functions control 652 can be used to trigger the large screen device 200 to display controls for more sub-functions of the air gesture functionality.

[0194] When the large-screen device 200 detects that the user has selected the icon of the target application in the AirView function interface 650, in response to this input, the large-screen device 200 can send an opening request for the target application to the electronic device 300. The electronic device 300, in response to the opening request sent by the large-screen device 200, can send data including the interface of the target application to the large-screen device 200. After receiving the data including the interface of the target application, the large-screen device 200 can display the interface of the target application.

[0195] In one possible implementation, if the electronic device 300 has already added the large-screen device 200 to the trust ring corresponding to the cloud account D used for the smart interconnection service on the electronic device 300, the electronic device 300 will display the above again. Figure 5E When the device details interface 570 is displayed, if the electronic device 300 receives the user's request for the above-mentioned... Figure 5D The electronic device 300 can respond to the input of the air-view function control 574 and display the above-mentioned information. Figure 5EThe interface 590 showing the AirView function introduction is shown, but the aforementioned "Instant Experience" control 593 is not displayed in the AirView function introduction interface 590. At this time, the large-screen device 200 can receive and respond to the user's command to activate the AirView function on the electronic device 300 via the remote control interface 640 on the electronic device 300 or other remote control devices, establishing a P2P connection with the electronic device 300. After establishing a P2P connection with the electronic device 300, the electronic device 300 can send application information of one or more whitelisted applications to the large-screen device 200 through the P2P connection. After obtaining the application information of one or more whitelisted applications installed on the electronic device 100, the large-screen device 200 can display as shown... Figure 5K The interface for the remote view function is shown as 650.

[0196] In one possible implementation, if the electronic device 300 has already added the large-screen device 200 to the trust ring corresponding to the cloud account D used for the smart interconnection service on the electronic device 300, the electronic device 300 will display the above again. Figure 5E When the device details interface 570 is displayed, if the electronic device 300 receives the user's request for the above-mentioned... Figure 5D Upon input to the air-view function control 574, the electronic device 300 can respond to this input and establish a P2P connection with the large-screen device 200. The electronic device 300 can then send application information of one or more whitelisted applications to the large-screen device 200 via the P2P connection. After receiving the application information of one or more whitelisted applications installed on the electronic device 100, the large-screen device 200 can display, as shown below... Figure 5K The interface for the remote view function is shown as 650.

[0197] Figures 6A-6C This illustration shows a schematic diagram of the interface of a group of second electronic devices receiving a large-screen device shared by a first electronic device, as provided in an embodiment of this application.

[0198] In one possible implementation, the electronic device 300 allows the user to access the aforementioned... Figure 5F The input of the "Agree" control 596 in the Smart Interconnected Privacy Window 594 (e.g., clicking it) allows the system to search for the large-screen device 200 within the local area network. After connecting to the large-screen device 200 within the local area network, a connection code request is sent to the large-screen device 200. Upon receiving the connection code request, the large-screen device 200 determines whether it is currently using the AirView function with other devices.

[0199] If the large-screen device 200 is using the AirView function with other devices, it returns a wait response to the electronic device 300. This wait response indicates that the large-screen device 200 is using the AirView function with other devices. Upon receiving the wait response, the electronic device 300 can display something like... Figure 6A The occupation notification 661 shown is used to inform the user that the large-screen device 200 is being used. This occupation notification 661 can be any one or more of text, image, or video notifications; for example, the text notification could be "The TV is in use, please try again later."

[0200] If the large-screen device 200 is not using the air-to-view function with other devices, it can display the connection code page and send page display result A to the electronic device 300. Page display result A indicates that the large-screen device 200 has successfully displayed the connection code page. Upon receiving page display result A, the electronic device 300 can display the aforementioned... Figure 5H The connection code input window 620 is shown.

[0201] In one possible implementation, the electronic device 300 can receive and respond to the user's above-mentioned... Figure 5F By entering the "Agree" control 596 in the Smart Interconnected Privacy Window 594 (for example, clicking it), the large screen device 200 can be searched for and connected within the local area network. If the Bluetooth function of both the electronic device 300 and the large screen device 200 is turned off, or if WLAN is turned off, causing the electronic device 300 to fail to connect to the large screen device 200 within the local area network, the electronic device 300 may display the following... Figure 6B The shown is an opening failure window 662A. This opening failure window 662A may include an opening failure message 663A, a retry control 664A, and a cancel control 665A. The opening failure message 663A can be used to inform the user that the air gesture control function on the electronic device 300 has failed to be enabled. The opening failure message 663A can be any one or more of text prompts, image prompts, and video prompts. For example, the text prompt could be "Please ensure the TV is powered on and the screen is on, the mobile phone is close to the TV, Bluetooth is enabled, and the device is connected to the same local area network." The retry control 664A can be used to trigger the electronic device 300 to reconnect to the large-screen device 200 within the local area network and send the aforementioned connection code request to the large-screen device 200. The cancel control 665A can be used to trigger the electronic device 300 to exit the air gesture control function introduction interface 590.

[0202] In one possible implementation, after the electronic device 300 sends the user-inputted connection code to the large-screen device 200, the electronic device 300 can establish a P2P connection with the large-screen device 200 through the user-inputted connection code.

[0203] like Figure 6CAs shown, if the electronic device 300 fails to establish a P2P connection with the large-screen device 200 due to reasons such as Bluetooth being turned off, WLAN being turned off, or the large-screen device 200 failing to verify the connection code entered by the user, the electronic device 100 can display an opening failure window 662B. This opening failure window 662B may include an opening failure message 663B, a retry control 664B, and a cancel control 665B. Specifically, the opening failure message 663B can be used to inform the user that the electronic device 300 has failed to enable the AirView function. This opening failure message 663B can be any one or more of text prompts, image prompts, and video prompts. For example, the text prompt could be: "Please ensure the TV is powered on and the screen is on, the mobile phone is close to the TV, Bluetooth is enabled and connected to the same local area network, and confirm that the connection code is correct." The retry control 664B can be used to trigger the electronic device 300 to reconnect to the large-screen device 200 within the local area network and send the aforementioned connection code request to the large-screen device 200. The cancellation control 665B can be used to trigger the electronic device 300 to exit the Air Vision function introduction interface 590.

[0204] The following is an exemplary description of the process by which the large-screen device 200 actively activates the air-viewing function in an embodiment of this application.

[0205] Figures 7A-7F This is a schematic diagram of the interface for a set of large-screen devices to actively enable the air vision function provided in the embodiments of this application.

[0206] like Figure 7A As shown, the large-screen device 200 can display a main interface 710. This main interface 710 can include pages corresponding to one or more titles. For example, one or more titles can include "Discovery" title, "Application Center" title, "Homepage" title 711, "TV Series" title, "Movie" title, "Anime" title, "Documentary" title, etc. Figure 7A In the main interface 710, the page corresponding to the homepage title 711 can be displayed. This page can include one or more options. For example, these options can include all category options, the virtual reality option 712, TV series options, movie options, variety show options, anime options, etc.

[0207] The large-screen device 200 can receive and respond to the user's input when selecting the air gesture option 712, and display as shown... Figure 7B The interface shown is 720, which introduces the remote view function.

[0208] like Figure 7BAs shown, the AirView feature introduction interface 720 may include AirView feature introduction information 721 and a loading prompt 722. The AirView feature introduction information 721 is used to introduce the AirView feature to the user. The AirView feature introduction information 721 can be one or more of text, image, or video information. For example, the text information could be "AirView, seamless integration, no installation required on TV, easily use your mobile phone's desktop application." The loading prompt 722 is used to indicate to the user that the AirView feature is loading.

[0209] like Figure 7C As shown, after the large-screen device 200 loads the AirView function, it can display a device selection interface 730. This device selection interface 730 may include an available device list 731, a history list 733, and an option to connect to other devices 736. The available device list 731 may include device options for one or more devices that are online within the same cloud account's trust ring and the same local area network as the large-screen device 200 (e.g., device option 732 for electronic device 100). The history list 733 may include options for one or more devices that have previously enabled the AirView function with the large-screen device 200 but are not online (e.g., device option 734, device option 735 for electronic device 300). The option to connect to other devices 734 can be used to trigger the large-screen device 200 to select other devices for the AirView function. Optionally, the device selection interface 730 may also display an AirView function introduction information 737 and a view of supported models 738. The AirView function introduction information 737 may be one or more of text, image, or video information. For example, the text message could be "AirView, seamless integration, no installation required on TV, easily use mobile desktop applications." The "View Supported Models" option 738 can be used to trigger the display of device types that support the AirView function on large-screen devices 200.

[0210] The large-screen device 200 can receive and respond to the user's input of selecting the device option 732 corresponding to the electronic device 100, and display as shown. Figure 7D The system displays an activation prompt message 723 and sends an activation request to the electronic device 100. This activation prompt message 723 can be one or more of text, image, or video information. For example, the text message could be: "Magic7 (ID: 186xxxxxx54) has been detected. Please ensure your phone and TV are on the same local network and click 'Activate' in the pop-up window on your phone."

[0211] Because electronic device 100 and large-screen device 200 are in the same trust ring and on the same local area network, electronic device 100 can receive the air gesture activation request sent by large-screen device 200. For example... Figure 7EAs shown, after receiving the air gesture activation request sent by the large-screen device 200, the electronic device 100 can display the following: Figure 7E The authorization window shown is 740.

[0212] like Figure 7E As shown, the authorization window 740 may include an icon 741 of the large-screen device 200, a device name 742 of the large-screen device 200 (e.g., "HH TV"), an activation prompt message 743, an activation control 744, and a cancellation control 745. The activation prompt message 743 can be used to prompt the user to authorize the activation of the AirView function. The activation prompt message 743 can be one or more of text, image, or video information. The text information may include "Request to activate the 'AirView' function. After activation, the mobile application can be used on the TV." The activation control 744 can be used to trigger the electronic device 100 to activate the AirView function with the large-screen device 200. The cancellation control 745 can be used to trigger the electronic device 100 to cancel the activation of the AirView function with the large-screen device 200.

[0213] Electronic device 100 can receive and respond to user input to open control 744 (e.g., click) to establish a P2P connection with large screen device 200.

[0214] like Figure 7F As shown, after the electronic device 100 establishes a P2P connection with the large-screen device 200, the electronic device 100 can display the remote control interface 750. For a textual description of the remote control interface 750, please refer to the above. Figure 2N The text description of the remote control interface 420 shown will not be repeated here. Optionally, when the electronic device 100 displays the remote control interface 750, the electronic device 100 may also display an operation prompt 751. This operation prompt 751 can be used to prompt the user to use the air gesture control function while simultaneously controlling the large screen device 200 with the electronic device 100. The operation prompt 751 can be one or more of text information, image information, video information, etc. For example, the text information could be "Air gesture control can be performed using an 'air mouse remote control'".

[0215] Optionally, the electronic device 100 may also display a prompt capsule 313 on its display screen after establishing a P2P connection with the large-screen device 200. For example, the prompt capsule 313 may be displayed at the top of the display screen. After the P2P connection between the electronic device 100 and the large-screen device 200 is disconnected, the electronic device 100 may stop displaying the prompt capsule 313 on the display screen.

[0216] After the electronic device 100 establishes a P2P connection with the large-screen device 200, the electronic device 100 can send application information of one or more whitelisted applications installed on the electronic device 100 to the large-screen device 200. The application information of the whitelisted applications may include the icons and application identifiers (e.g., application names) of the whitelisted applications. After receiving the application information of one or more whitelisted applications installed on the electronic device 100, the large-screen device 200 can display the information as described above. Figure 2P The interface 440 for the remote view function is shown. For a textual description of this remote view function interface 440, please refer to the above. Figure 2P The embodiments shown are not described in detail here.

[0217] When the large-screen device 200 detects that the user has selected the icon of the target application in the AirView function interface 440, in response to this input, the large-screen device 200 can send an opening request for the target application to the electronic device 100. The electronic device 100, in response to the opening request sent by the large-screen device 200, can send image data including the interface of the target application to the large-screen device 200. After receiving the image data including the interface of the target application, the large-screen device 200 can display the interface of the target application. Optionally, the electronic device 100 can also send audio data generated by the target application to the large-screen device 200. After receiving the audio data, the large-screen device 200 can play the audio data.

[0218] Figures 8A-8B This is a schematic diagram of the interface of a set of large-screen devices actively activating the air vision function in the embodiments of this application.

[0219] In one possible implementation, since the large-screen device 200 has been added to the smart space application by the electronic device 100, and the smart space application of the electronic device 100 is logged in with cloud account A, cloud account A can serve as the administrator account for the large-screen device 200. The electronic device 100 can also be shared in the smart space application with the electronic device 300 logged in with cloud account C. Therefore, the large-screen device 200 can be used by both the electronic device 100 (logged in with cloud account A) and the electronic device 300 (logged in with cloud account C) in the smart space application.

[0220] For example, such as Figure 8AAs shown, when the large-screen device 200 displays the device selection interface 730, if no device is found that is in the same cloud account's trust ring and within the same local area network as the large-screen device 200, a "No Available Device Found" message 739A can be displayed in the available device list 731. This "No Available Device Found" message 739A can be used to inform the user that the large-screen device 200 has not found any devices with the AirView function available. Optionally, if no device is found that is in the same cloud account's trust ring and within the same local area network as the large-screen device 200, the large-screen device 200 can also display a binding prompt message 739B. This binding prompt message 739B can be used to prompt the user to contact the administrator to share usage rights for the large-screen device 200.

[0221] The large-screen device 200 can receive and respond to user input on option 736 for connecting other devices, and display such as Figure 8B The prompt window shown is 810.

[0222] like Figure 8B As shown, the prompt window 810 may include a prompt message 811, a "know" option 812, and an "unbind" option 813. The prompt message 811 can be used to prompt the user to contact the administrator to share usage rights for the large-screen device 200. The "know" option 812 can be used to trigger the large-screen device 200 to close the prompt window 810. The "unbind" option 813 can be used to trigger the large-screen device 200 to unbind itself from cloud account A (e.g., "186xxxxxx54").

[0223] The following is an exemplary description of the process by which the large-screen device 200, having already enabled the air gesture function with the electronic device 100, switches to enabling the air gesture function with another device in this application embodiment.

[0224] Figures 9A-9C This is a schematic diagram of the interface for switching between a set of large-screen devices and other devices to enable the remote viewing function, as provided in this embodiment of the application.

[0225] like Figure 9A As shown, the large-screen device 200 can establish a P2P connection with the electronic device 100 and display the air gesture function interface 440. A textual description of the air gesture function interface 440 can be found above. Figure 2P The illustrated embodiment will not be described in detail here. The device control 441 in the air-view function interface 440 may display the device name of the electronic device 100 (e.g., "Magic7").

[0226] The large-screen device 200 can receive and respond to user input to the device control 441, displaying, for example... Figure 9B The device selection interface shown is 910.

[0227] like Figure 9B As shown, the device selection interface 910 can include device options corresponding to one or more devices that have already established a remote viewing function with the large screen device 200. These device options may include device option 911 corresponding to electronic device 100. Since the large screen device 200 and electronic device 100 have established a P2P connection, the large screen device 200 marks device option 911 as selected. For example, these device options may also include device option 912 corresponding to electronic device 300 and device option 913 corresponding to another device. The device options can display the device information corresponding to that option. For example, device option 911 displays "186xxxxxx54's Magic7", device option 912 displays "180xxxxxx49's Magic6", and device option 913 displays "181xxxxxx22's Magic5". Here, "186xxxxxx54" can be the cloud account logged into in the smart space application on electronic device 100, and "Magic7" can be the device name of electronic device 100. "180xxxxxx49" can be the cloud account logged into the Smart Space application on electronic device 300, and "Magic6" can be the device name of electronic device 300. "181xxxxxx22" can be the cloud account logged into the Smart Space application on another device, and "Magic5" can be the device name of that other device.

[0228] If electronic device 300 and large-screen device 200 are on the same local area network (LAN) and large-screen device 200 can detect that electronic device 300 is online within the LAN, large-screen device 200 can receive and respond to user input on device option 912. In response to this input, large-screen device 200 can establish a P2P connection with electronic device 300. It then sends an application list request to electronic device 300 via the P2P connection. Upon receiving the application list request, electronic device 300 can obtain application information for one or more whitelisted applications installed on its device and send this information to large-screen device 200 via the P2P connection. The application information for whitelisted applications may include the application's icon and application identifier (e.g., application name). After obtaining the application information for one or more whitelisted applications installed on electronic device 300, large-screen device 200 can display the information as described above. Figure 5K The interface 650 for the air vision function is shown. For a textual description of the air vision function interface 650, please refer to the above. Figure 5K The textual details of the illustrated embodiments will not be repeated here.

[0229] If the above Figure 9BIf the other devices corresponding to device option 913 shown are not on the same local area network as the large screen device 200, or if the large screen device 200 can detect that the other devices corresponding to device option 913 are not online within the local area network, the large screen device 200 can receive and respond to the user's input on device option 913, displaying as shown below. Figure 9C The device selection interface 730 is shown, and a reconnection prompt 739C is displayed within the device selection interface. This reconnection prompt 739C can be used to trigger the large-screen device 200 to reselect the device for the air gesture control function. In the case of... Figure 9C In the device selection interface 730 shown, since the large screen device 200 has discovered that both electronic devices 100 and 300 are online on the local area network, the large screen device 200 can display the device option 731 corresponding to electronic device 100 and the device option 735 corresponding to electronic device 300 in the available device list 731 of the device selection interface 730.

[0230] The following is an exemplary description of the process by which the electronic device 100 adds a large-screen device 200 to a smart space application in an embodiment of this application.

[0231] Figures 10A-10C This is a schematic diagram of the interface for adding a large-screen device to a set of first electronic devices provided in this application embodiment in a smart space application.

[0232] like Figure 10A As shown, the electronic device 100 can display the main interface 1010 of the smart space application. The main interface 1010 may include a plus sign control 1011.

[0233] Electronic device 100 can receive and respond to user input to the plus sign control 1011, displaying, for example... Figure 10B The shortcut menu shown is 1012.

[0234] like Figure 10B As shown, the shortcut menu 1012 may include an add device control 1013. Optionally, the shortcut menu 1012 may also include creating scene controls and sharing device controls. The add device control 1013 can be used to add devices in the smart space application.

[0235] Electronic device 100 can receive and respond to user input (e.g., a click) to the added device control 1013, and in response to the input, electronic device 100 can display, as shown below. Figure 10C The Add Device interface shown is 1020.

[0236] like Figure 10CAs shown, when the electronic device 100 displays the device addition interface 1020, it can search for devices via Bluetooth and / or a local area network. When the large-screen device 200 is found, the electronic device 100 can display the icon 1021 of the large-screen device 200, the device name 1022 of the large-screen device 200 (e.g., "HH TV"), and the corresponding addition control 1023 of the large-screen device 200 in the device addition interface 1020. The addition control 1023 can be used to trigger the electronic device 100 and the large-screen device 200 to complete the above-mentioned process. Figures 2C to 2Q The illustrated embodiment shows the process of adding a large-screen device 200.

[0237] The software architecture of the communication system provided in the embodiments of this application is described below.

[0238] Figure 11 This is a schematic diagram of the software architecture of a communication system provided in the embodiments of this application.

[0239] like Figure 11 As shown, the communication system 10 may include an electronic device 100, a large-screen device 200, and a cloud server 400. The electronic device 100 may include smart interconnection services, a floating ball and / or a dynamic island and / or a notification center, smart space applications, a remote viewing service, an air sharing module, a smart middleware platform, and an interconnection middleware platform.

[0240] The smart space application can include smart space services and interconnection middleware. Smart space services can be used for device discovery, addition, and authentication. Smart space services can also include device control cards and air gesture control kits. These kits provide display logic for air gesture control, air mouse, control, and device status functions for large-screen devices.

[0241] The remote vision service may include the remote vision service application programming interface (API).

[0242] The interconnection platform may include a connectivity service (iConnect), a device access module, a data transmission module, a device management module, and a distributed mobile sensing development platform (DMSDP). iConnect can be used to discover other devices (e.g., large-screen devices, in-vehicle devices, etc.) via Bluetooth proximity. The device access module can be used for trust loop authentication with the large-screen device 200. The data transmission module can be used for device transmission between the electronic device 100 and the large-screen device 200. DMSDP can be used to control the projection of audio and / or video data with other devices. DMSDP may include source-side DMSDP services and destination-side DMSDP services. When the electronic device 100 acts as the source of projection control, it can use the source-side DMSDP service; when it acts as the destination of projection control, it can use the destination-side DMSDP service.

[0243] The large-screen device 200 may include a Bluetooth broadcast discovery protocol, a gesture-to-view application, a gesture-to-view SDK, and an IoT SDK. The gesture-to-view application may include gesture-to-view services and controlled services.

[0244] The following is in conjunction with the above. Figure 11 The software architecture of the communication system 10 shown illustrates the function of each module.

[0245] 1. The large-screen device 200 can send BLE broadcasts via the Bluetooth broadcast discovery protocol.

[0246] 2. After the iConnect on the electronic device 100 detects the BLE broadcast sent by the large screen device 200 via the Bluetooth module, it can launch the Smart Space application to add the large screen device 200 based on the device information of the large screen device 200 carried in the BLE broadcast.

[0247] The process of electronic device 100 discovering large-screen device 200 via iConnect and adding large-screen device 200 through the smart space application can be referred to the above. Figures 2A-2F The embodiments shown are not described in detail here.

[0248] 3. In smart space applications, users can also trigger the search for devices and add the large-screen device 200 as an IoT device.

[0249] The process of adding the large-screen device 200 as an IoT device in smart space applications can be referenced above. Figures 10A-10C The embodiments shown are not described in detail here.

[0250] 4. After adding the large screen device 200 to the smart space application, the electronic device 100 can realize the functions of air mouse control, large screen control and air vision control of the large screen device 200 through the device control card developed by the manufacturer of the large screen device 200.

[0251] 5. The large-screen device 200 can be interconnected with the smart space application in the electronic device 100 through the IoT SDK.

[0252] 6. The AirView service on electronic device 100 can provide an interface for non-interface display capabilities within the AirView function.

[0253] 7. In the smart space application of electronic device 100, the ability to call the remote vision service can be obtained through the remote vision kit, and the calling interface of the remote vision service can be provided to the device control card for calling.

[0254] 8. Large screen devices 200 can obtain the ability of the AirView function through the AirView SDK.

[0255] 9. Large screen devices 200 can negotiate the capabilities of the remote viewing service and display the UI interface through the remote viewing service.

[0256] 10. The large-screen device 200 can connect to the IoT device cloud by calling the IoT SDK through the controlled service, thereby sending the device status of the large-screen device 200 to the device control card of the electronic device 100, and cooperating with the device control card on the electronic device 100 to complete the control functions of the large-screen device 200.

[0257] 11. The smart space service on electronic device 100 can call the interconnection middleware to communicate with the IoT device cloud on cloud server 400, thereby sending the device information of the large screen device 200 discovered by electronic device 100 and the cloud account A logged in in the smart space application of electronic device 100 to the IoT device cloud for binding.

[0258] 12. Electronic device 100 can communicate with the Trust Ring Device Cloud on cloud server 400 through the device management module in the interconnection platform. It sends the device information of the large-screen device 200 discovered by electronic device 100 and the cloud account B used by electronic device 100's smart interconnection service to the Trust Ring Cloud for binding, thereby allowing the large-screen device 200 to enter the trust ring of cloud account B. This cloud account B can be the same as or different from the aforementioned cloud account A.

[0259] 13. Electronic device 100 can also delete and synchronize devices in the trust ring of cloud account B through the device management module in the interconnection platform.

[0260] 14. Electronic device 100 can display device information of the device added to the trust ring of cloud account B on the smart interconnection interface through the smart interconnection service.

[0261] The device information displayed in the smart interconnection interface for devices that have been added to the trust ring of cloud account B can be found above. Figures 30 to 3S The embodiments shown are not described in detail here.

[0262] 15. The large screen device 200 can activate the remote viewing service of the large screen device 200 by transmitting the instructions issued by the smart space application on the controlled service transparently to the electronic device 100, thereby enabling the remote viewing service to identify abnormal situations.

[0263] Abnormal situations may include the air vision function of the large screen device 200 being occupied by other devices, or the large screen device 200 failing to display the connection code interface.

[0264] 16. Electronic device 100 can display notifications or prompts for the AirView function via a floating ball and / or a dynamic island and / or a notification center.

[0265] 17. Electronic device 100 can use the Air Sharing module to project screen data to the Air Sharing client of large screen device 200 for playback.

[0266] Among them, the Air Sharing client in the large-screen device 200 can be encapsulated into the Air Sharing SDK.

[0267] Figure 12 This is a schematic diagram of a screen mirroring software framework for an electronic device and a large screen device provided in an embodiment of this application.

[0268] like Figure 12 As shown, the electronic device 100 may include a smart space application, a remote vision service API, a remote vision service, an interconnection platform, an air sharing module, and an operating system (MagicOS).

[0269] The remote viewing service includes functional modules such as access device management, source-side super desktop service, data fusion service, connection component (Magic LinkKit), device management module, and distributed fusion perception platform component (DMSDP Kit). The source-side super desktop service includes modules such as application manager (AppManager), state manager (StateManager), hardware key (HardKey), and audio splitter (Audio Split).

[0270] The interconnection platform can include source-side DMSDP services and a basic platform. The source-side DMSDP services can be used to implement functions such as display virtualization, audio virtualization, camera virtualization, and reverse control. The basic platform provides interconnection capabilities with the trust ring system of large-screen devices.

[0271] The Air Sharing module can include a source-end casting service, which can support casting protocols such as Miracast, Cast+, and the Digital Alliving Network Alliance (DLNA).

[0272] The operating system (MagicOS) provides a basic framework and a media framework, creating a runtime environment for smart space applications, the Remote View service API, Remote View services, the interconnected platform, and the Remote Sharing module. The basic framework can be used to provide features such as parallel views and multi-screen frameworks. The media framework can be used to provide media processing and playback functions.

[0273] Large-screen device 200 may include the GestureView application, GestureView SDK, Trust Ring service, and Android Open Source Project (AOSP).

[0274] The Trust Ring service can include the destination super desktop service, Magic Link Kit, DMSDP Kit, destination DMSDP service, destination screen mirroring service, and the Trust Ring system. The destination super desktop service can include modules such as AppManager, StateManager, HardKey, and SurfaceView. The destination DMSDP service can be used to implement functions such as display virtualization, audio virtualization, camera virtualization, and reverse control. The destination screen mirroring service can build screen mirroring capabilities through Hisight objects.

[0275] The Android operating system (AOSP) provides a runtime environment for modules such as the AirView application, AirView SDK, and Trust Ring service.

[0276] The software structures of electronic devices 300 and 500 can refer to the above. Figure 11 , Figure 12 The software structure of the electronic device 100 in the illustrated embodiment will not be described in detail here.

[0277] The following is in conjunction with the above. Figures 2A to 2B as well as Figure 3AThe illustrated embodiment specifically describes the process by which electronic device 100 discovers large-screen device 200.

[0278] Figure 13 This is a schematic diagram illustrating the process of the first electronic device discovering the large-screen device in the device control method provided in this application embodiment.

[0279] Because electronic device 100 is logged into cloud account A in the smart space application and is within the trust ring of cloud account B, while large-screen device 200 is not logged into the same cloud account as electronic device 100. For example, the two devices may not be manufactured by the same company, preventing them from logging into the same cloud account. Alternatively, device A may be logged into a cloud account, but the user may not be logged into a cloud account on device B. Therefore, large-screen device 200 cannot proactively add itself to the smart space application of electronic device 100, nor can it proactively join the trust ring of electronic device 100.

[0280] Therefore, the embodiments of this application are implemented through Figure 13 The device control method shown illustrates a process where the electronic device 100 discovers the large-screen device. When the electronic device 100 approaches the large-screen device 200, it receives a broadcast packet from the large-screen device 200. Upon receiving the broadcast packet, the electronic device 100 obtains the device information of the large-screen device 200 and displays its discovery window. This quickly guides the user to add the large-screen device 200 to the smart space application on the electronic device 100. The electronic device 100 itself then helps the large-screen device 200 complete account binding on the cloud server, thereby adding the large-screen device 200 to the smart space application and placing it within the trust ring of the electronic device 100.

[0281] like Figure 13 As shown, the process of an electronic device discovering a large-screen device can be applied to a communication system that includes an electronic device 100 and a large-screen device 200. The electronic device 100 may include iConnect 101 and a Bluetooth module 102. The large-screen device 200 may include an IoT SDK 201 and a gesture-based viewing application 202.

[0282] The process by which electronic device 100 detects large-screen device 200 may include the following steps:

[0283] S101.iConnect101 sets filtering rules for Bluetooth module 102.

[0284] After the electronic device 100 is powered on, iConnect 101 can set filtering rules for the Bluetooth module 102. The Bluetooth module 102 can determine whether received BLE broadcast packets meet the filtering rules, and thus decide whether to report discovery information to iConnect 101. These filtering rules allow the Bluetooth module 102 to filter out BLE broadcast packets from whitelisted devices from the received BLE broadcast packets and report the discovery information of these whitelisted devices to iConnect 101. Whitelisted devices are devices that the electronic device 100 can add. This prevents the Bluetooth module 102 from frequently reporting the discovery information of invalid devices to iConnect 101.

[0285] S102. Bluetooth module 102 returns the setting results to iConnect 101.

[0286] After setting the filtering rules, Bluetooth module 102 can return the setting result to iConnect 101. If the setting result is successful, iConnect 101 can wait for Bluetooth module 102 to report discovery information. If the setting result is unsuccessful, iConnect 101 can re-set the filtering rules to Bluetooth module 102 until Bluetooth module 102 returns a setting result of success.

[0287] S103. The remote vision application 202 sends a query request to the IoT SDK 201, wherein the query request can be used to query the IoT registration results of the large screen device 200.

[0288] Steps S103 to S107 can be executed periodically. The remote vision application 202 can send query requests to the IoT SDK 201 at regular intervals.

[0289] In one possible implementation, the large-screen device 200 can trigger the execution of steps S103 to S107 when certain conditions are met. For example, the large-screen device 200 can execute steps S103 to S107 when switching from a power-off state to a power-on state. As another example, the large-screen device 200 can execute steps S103 to S107 when entering a configuration state.

[0290] S104.IoT SDK201 sends a query response to the AirView application 202, wherein the query response can be used to carry the IoT registration results of the large-screen device 200.

[0291] S105. The remote vision application 202 determines whether the large screen device 200 has completed IoT registration based on the IoT registration result of the large screen device 200.

[0292] If the large-screen device 200 has completed IoT registration, it means that its device information has already been bound to the cloud account of other devices. Therefore, the large-screen device 200 does not need to send BLE broadcast packets to be discovered by other devices. If the large-screen device 200 has not completed IoT registration, it means that its device information has not been bound to the cloud account of other devices. Therefore, the large-screen device 200 can send BLE broadcast packets to be discovered by other devices.

[0293] S106. If the large screen device 200 has not completed IoT registration, the Gesture Vision application 202 can determine whether the large screen device 200 is connected to the local area network.

[0294] If the large-screen device 200 is connected to the local area network (LAN), it can communicate with other devices within the LAN. Therefore, the large-screen device 200 can send BLE broadcast packets to be discovered by other devices, thus establishing a P2P connection. If the large-screen device 200 is not connected to the LAN, it cannot communicate with other devices within the LAN, even if it sends BLE broadcast packets. Therefore, when the large-screen device 200 is not connected to the LAN, it can stop sending BLE broadcast packets to save power.

[0295] It should be noted that step S106 is optional. In one possible implementation, the large-screen device 200 can send BLE broadcast packets regardless of whether it is connected to the local area network.

[0296] S107. If the large screen device 200 has completed IoT registration or the large screen device 200 is not connected to the local area network, the AirView application 202 can control the large screen device 200 not to send BLE broadcast packets.

[0297] S108. If the large screen device 200 is already connected to the local area network, the AirView application 202 can control the large screen device 200 to send BLE broadcast packets.

[0298] S109. Bluetooth module 102 can scan for BLE broadcast packets from large screen device 200.

[0299] The BLE broadcast packet of the large-screen device 200 may include a service identifier, a product identifier, a device identifier, a device sub-identifier, and a device name (e.g., "HH TV"). The service identifier can indicate whether the BLE broadcast packet is used to display a discovery pop-up. The service identifier can indicate the device manufacturer. For example, the service identifier can use a universally unique identifier (UUID), which can be used to uniquely identify a BLE service. The product identifier can indicate the identifier issued by the manufacturer of the electronic device 100 to the manufacturer of the large-screen device 200. The device sub-identifier can indicate the product number assigned to the large-screen device 200 by the manufacturer of the large-screen device 200. The device identifier can indicate the device serial number (SN) information of the large-screen device 200 (e.g., the last two digits of the SN), which allows the electronic device 100 to distinguish the large-screen device 200 from multiple large-screen devices.

[0300] S110. Bluetooth module 102 can determine whether the BLE broadcast packets of the large screen device 200 meet the filtering rules.

[0301] For example, the filtering rule could include a first service identifier and a first service identifier in the BLE broadcast packet. The first service identifier indicates whether the BLE broadcast packet is used to display a discovery pop-up, and the first service identifier is the service identifier of the electronic device manufacturer. For example, the first service identifier could be a first UUID, which is a proprietary BLE service identifier issued by the Bluetooth standards organization to the manufacturer of electronic device 100.

[0302] In one example, the BLE broadcast packet of the large-screen device 200 can be referred to as the first broadcast packet.

[0303] S111. If the BLE broadcast packet of the large screen device 200 meets the filtering rules, the Bluetooth module 102 can report the discovery information of the large screen device 200 to iConnect 101. The discovery information of the large screen device 200 includes the device information of the large screen device 200 and the signal strength of the BLE broadcast packet.

[0304] The device information of the large-screen device 200 may include one or more of the following: product identifier of the large-screen device 200, device name of the large-screen device 200, device identifier of the large-screen device 200, and device sub-identifier of the large-screen device 200.

[0305] S112.iConnect101 can determine whether the signal strength of BLE broadcast packets is greater than the strength threshold.

[0306] If the signal strength of the BLE broadcast packet is greater than the strength threshold, it indicates that the electronic device 100 is close to the large screen device 200. Therefore, the electronic device 100 needs to display the discovery window of the large screen device 200. If the signal strength of the BLE broadcast packet is less than the strength threshold, it indicates that the electronic device 100 is not close to the large screen device 200. Therefore, the electronic device 100 does not need to display the discovery window of the large screen device 200.

[0307] S113. If the signal strength of the BLE broadcast packet is greater than the strength threshold, iConnect101 can determine whether the electronic device 100 is displaying the discovery window of other devices.

[0308] S114. If the electronic device 100 is displaying the discovery window of another device, iConnect101 can cache the discovery information of the large screen device 200 and wait for the discovery window of the other device to finish displaying.

[0309] After the discovery window for other devices finishes displaying, step S115 can be executed.

[0310] In one example, the discovery window of other devices can be referred to as the second discovery window.

[0311] S115. If the electronic device 100 is not displaying the discovery window of other devices, iConnect 101 can pop up the discovery window of the large screen device 200 based on the discovery information.

[0312] The discovery window for the large-screen device 200 can be referenced as described above. Figure 2B Window 320 is found in the embodiment shown, and will not be described in detail here.

[0313] In this way, after the electronic device 100 receives the BLE broadcast packet from the large screen device 200, the discovery window of the large screen device 200 will only pop up when the electronic device 100 is relatively close to the large screen device 200 and the electronic device 100 does not display the discovery window of other devices, thereby avoiding the overlap of multiple discovery windows.

[0314] In one possible implementation, iConnect101 can also determine whether the electronic device 100 has downloaded the Smart Space application. If the electronic device 100 has not downloaded the Smart Space application and is not currently displaying a discovery window for other devices, iConnect101 can also display the aforementioned... Figure 3A The download window 450 in the illustrated embodiment. The electronic device 100 can receive and respond to user input regarding the download of the Smart Space application, download and install the Smart Space application, and log in to cloud account A within the Smart Space application based on user input. After logging in to cloud account A, the electronic device 100 can display the aforementioned... Figure 2BThe discovery window 320 is shown.

[0315] S116. If iConnect101 detects that the user has not operated on the discovery window of the large screen device 200 for more than a specified time, iConnect101 stops displaying the discovery window of the large screen device 200.

[0316] For example, the specified duration can be 10 seconds.

[0317] Since the discovery window is generally displayed on the top layer of the display screen, stopping the display of the discovery window of the large screen device 200 when it is detected that the user has not operated on the discovery window of the large screen device 200 for a specified period of time can prevent the discovery window of the large screen device 200 from obscuring other content displayed on the screen.

[0318] In one possible implementation, step S116 is optional.

[0319] By using the process of electronic device discovering large screen device in the device control method provided in this application embodiment, when electronic device 100 approaches large screen device 200, it can quickly discover large screen device 200 that can perform air-to-ground communication with electronic device 100 and display the discovery window of large screen device 200, thereby quickly guiding the user to add large screen device 200 to electronic device 100 and use the application of electronic device 100 on large screen device 200.

[0320] The following is in conjunction with the above. Figures 2B-2Q The illustrated embodiment specifically describes the process of adding and using the large-screen device 200 for the first time on the electronic device 100.

[0321] Figures 14A-14B This illustration shows a flowchart of the process of adding and using a large-screen device for the first time in the device control method provided in the embodiments of this application.

[0322] Because electronic device 100 is logged into cloud account A in the smart space application and is within the trust ring of cloud account B, while large-screen device 200 is not logged into the same cloud account as electronic device 100. For example, the two devices may not be manufactured by the same company, preventing them from logging into the same cloud account. Alternatively, device A may be logged into a cloud account, but the user may not be logged into a cloud account on device B. Therefore, large-screen device 200 cannot proactively add itself to the smart space application of electronic device 100, nor can it proactively join the trust ring of electronic device 100. If large-screen device 200 is not joined to the trust ring of electronic device 100, certain interconnection functions (e.g., gesture control) between electronic device 100 and large-screen device 200 will be unavailable.

[0323] Through the embodiments of this application Figure 14A and Figure 14B The process of adding a large-screen device to an electronic device for the first time, as shown, involves electronic device 100 receiving confirmation from the user in the large-screen device's discovery window to connect. Electronic device 100 then completes the IoT registration and trust ring registration of the large-screen device 200 by linking the device information of the large-screen device 200 with cloud account A and cloud account B on the cloud server 400. In other words, although the large-screen device 200 cannot directly log in to its cloud account to complete the account binding on the cloud server side, electronic device 100 can assist the large-screen device in doing so.

[0324] In this way, while adding the large-screen device 200 to the smart space application, electronic device 100 can also add the large-screen device 200 to the trust ring of electronic device 100. The large-screen device 200 and electronic device 100 can then trust each other. This allows users to securely and quickly use the applications on electronic device 100 on the large-screen device 200, and also simplifies the user's workflow when using applications on electronic device 100 on the large-screen device 200.

[0325] In one possible implementation, electronic device 100 can send a registration request to cloud server 400. The registration request carries a first cloud account (i.e., cloud account A), a second cloud account (i.e., cloud account B), and device information of the large-screen device 200. The registration request is used to request the cloud server to bind the device information of the large-screen device 200 with the first and second cloud accounts. After receiving a registration success result from cloud server 400, electronic device 100 can perform a gesture-based communication function with the large-screen device 200. Optionally, there can be one or two registration requests, and one or two registration success results.

[0326] In one possible implementation, when there are two registration requests and two registration success results, the registration request can include a first registration request (also known as an IoT registration request) and a second registration request (also known as a trust ring registration request). The registration success result can include a first registration success result (also known as an IoT registration success result) and a second registration success result (also known as a trust ring registration success result). The first registration request carries a first cloud account (i.e., cloud account A) and the device information of the large-screen device. The first registration request is used to request the cloud server 400 to bind the device information of the large-screen device 200 to the first cloud account. The second registration request carries a second cloud account (i.e., cloud account B) and the device information of the large-screen device 200. The second registration request is used to request the cloud server 400 to bind the device information of the large-screen device 200 to the second cloud account. The registration success result can include a first registration success result and a second registration success result. The first registration success result indicates that the cloud server 400 has successfully bound the device information of the large-screen device 200 to the first cloud account, and the second registration success result indicates that the cloud server 400 has successfully bound the device information of the large-screen device 200 to the second cloud account.

[0327] In one possible implementation, after receiving the first registration success result from the cloud server 400, the electronic device 100 sends a second registration request to the cloud server 400. After receiving the second registration success result from the cloud server 400, the electronic device 100 can perform the air gesture communication function with the large-screen device 200.

[0328] like Figure 14A , Figure 14B As shown, the process of adding and using the large-screen device 200 to the electronic device 100 can be applied to a communication system that includes both the electronic device 100 and the large-screen device 200. The electronic device 100 may include iConnect 101, Smart Space Service 103, Gesture View Service 104, Smart Interconnection Service 105, Interconnection Middleware 106, Device Access Module 107, and Device Management Module 108. The large-screen device 200 may include IoT SDK 201 and Gesture View Application 202.

[0329] The process of adding a large-screen device 200 to an electronic device 100 may include the following steps:

[0330] S201.iConnect101 detected the user's confirmation of connecting to the large screen device 200 in the discovery window of the large screen device 200.

[0331] The discovery window for the large-screen device 200 can be referenced as described above. Figure 2BThe discovery window 320 in the illustrated embodiment will not be described in detail here. The user's input for confirming connection to the large-screen device 200 in the discovery window of the large-screen device 200 can be as described above. Figure 2B The illustrated embodiment shows user input to the connection control 325 in the discovery window 320. Input to confirm connection to the large-screen device 200 is not limited to the connection control 325; it can also be input by voice or other means.

[0332] In one example, the discovery window of the large-screen device 200 can be referred to as the first discovery window. The user's confirmation of the connection to the large-screen device can be referred to as the first operation.

[0333] S202. In response to the user's confirmation of connection to the large screen device 200 in the discovery window of the large screen device 200, iConnect 101 sends a startup request to the smart space service 103, wherein the startup request carries the device information of the large screen device 200.

[0334] The device information of the large screen device 200 may include one or more of the following: product identifier of the large screen device 200, device name of the large screen device 200, device identifier of the large screen device 200, and device sub-identifier of the large screen device 200.

[0335] S203. Smart Space Service 103 sends a query request A to Air Vision Service 104, wherein the query request A is used to query whether the electronic device 100 supports the Air Vision function.

[0336] S204. Remote Vision Service 104 returns query result B to Smart Space Service 103.

[0337] S205. Smart Space Service 103 determines whether electronic device 100 supports the air vision function based on query result B.

[0338] S206. If the electronic device 100 supports the air vision function, the electronic device 100 can send a query request C to the air vision service 104, wherein the query request C can be used to query whether the electronic device 100 has enabled the smart interconnection service 105.

[0339] S207. Remote Vision Service 104 returns query result D to Smart Space Service 103.

[0340] S208. Smart Space Service 103 Based on the query result D, determine whether the electronic device 100 has enabled the smart interconnection service 105.

[0341] S209. If the smart interconnection service 105 is not enabled on the electronic device 100, the smart space service 103 will display an enable window.

[0342] This opening window can be used to request the user to enable the smart interconnection service 105. This opening window can be referenced as described above. Figure 3B The opening window 460A in the illustrated embodiment or Figure 3C The open window 460B in the illustrated embodiment or Figure 3D The opening window 460C in the illustrated embodiment or Figure 3E The opening window 460D, etc., in the above embodiments will not be described again here.

[0343] S210. Smart Space Service 103 detected that the user entered the input to open Smart Interconnection Service 105 in the open window.

[0344] S211. In response to the user's input to open the smart interconnection service 105 in the open window, the smart space service 103 opens the smart interconnection service 105 through the remote vision service 104.

[0345] S212. Smart Space Service 103 checks whether Smart Interconnection Service 105 has been enabled.

[0346] S213. If the Smart Interconnection Service 105 is enabled, the Smart Space Service 103 will display the Smart Interconnection Privacy Window.

[0347] The smart interconnected privacy window can be referenced as described above. Figure 2E The smart interconnected privacy window 350 in the above embodiment will not be described in detail here.

[0348] Among them, the smart interconnected privacy window can be used to prompt users to agree to the first privacy policy.

[0349] In one example, the smart interconnected privacy window can be referred to as the first privacy window.

[0350] S214. Smart Space Service 103 detected that the user agreed to the first privacy policy in the Smart Interconnection Privacy Window.

[0351] In one example, the user's agreement to the first privacy policy entered in the smart interconnected privacy window can be referred to as a third action.

[0352] S215. If the electronic device 100 does not support the air vision function or the smart space service 103 detects that the user has entered the privacy policy in the smart interconnection privacy window, the smart space service 103 may display the connected device interface.

[0353] The interface for connecting devices can be referenced as described above. Figure 2F The interface of the connection device in the illustrated embodiment will not be described in detail here.

[0354] After execution Figure 14AAfter step S215 as shown, the following steps can be performed: Figure 14B Step S216 is shown.

[0355] S216. Smart Space Service 103 sends a discovery request to Interconnect Middleware 106.

[0356] Among them, the smart space service 103 can send a discovery request to the interconnect middleware 106 by calling the discovery interface. The discovery request can carry the device information of the large screen device 200.

[0357] S217. Interconnect middleware 106 scans for large screen device 200 within the local area network based on the device information of large screen device 200.

[0358] S218. After scanning the large screen device 200, the interconnection middleware 106 reports a discovery notification to the smart space service 103, wherein the discovery notification can be used to indicate that the large screen device 200 has been discovered.

[0359] S219. After receiving the discovery notification, the smart space service 103 can send a connection code request A to the IoT SDK 201 of the large screen device 200 through the interconnection middleware 106.

[0360] Among them, the connection code request A can be used to request the large screen device 200 to generate a connection code.

[0361] In response to connection code request A, S220.IoT SDK201 generates the first connection code.

[0362] After generating the first connection code, S221.IoT SDK201 sends a display request A to the AirView application, wherein the display request A carries the first connection code.

[0363] S222. After receiving the display request A, the remote vision application 202 displays the connection code page A, wherein the connection code page A includes a first connection code.

[0364] For example, page A with the connection code can be referenced as described above. Figure 2G The connection code page 360 ​​in the illustrated embodiment will not be described in detail here.

[0365] In one example, link code page A can be referred to as the first link code page.

[0366] S223. The remote vision application 202 returns the page display results to the smart space service 103 through the IoT SDK 201 and the interconnection middleware 106.

[0367] S224. If the page display result indicates that the connection page A has been successfully displayed, the Smart Space Service 103 displays the connection code input window A.

[0368] In one example, the page display result indicating that the linked page A has been successfully displayed can be referred to as the first page display result.

[0369] The connection code input window A can be referenced as described above. Figure 2H The connection code input window 370 in the illustrated embodiment will not be described in detail here.

[0370] In one example, connection code input window A can be referred to as the first connection code input window.

[0371] S225. Smart Space Service 103 detected the second connection code entered by the user in the connection code input window A.

[0372] S226. Smart Space Service 103 Cache Second Connection Code.

[0373] Since the large-screen device 200 can be controlled by the electronic device 100 as an IoT device and can also perform interconnection functions such as screen mirroring with the electronic device 100, and the interconnection function can only be performed if the electronic device 100 and the large-screen device 200 are within the same trust ring, when the electronic device 100 adds the large-screen device 200 for the first time, it needs to bind the device information of the large-screen device 200 with cloud account A on the IoT device cloud, and also bind the device information of the large-screen device 200 with cloud account B on the trust ring device cloud. Before binding the device information of the large-screen device 200 with cloud account A on the IoT device cloud, in order to avoid binding the device information of a device that has not been authorized by the user for IoT registration with cloud account A, the electronic device 100 can use a second connection code to perform IoT authentication on the large-screen device 200. After the IoT authentication is successful, that is, the large-screen device 200 is a device authorized by the user for IoT registration, the electronic device 100 can then bind the device information of the large-screen device 200 with cloud account A on the IoT device cloud. Before binding the device information of the large-screen device 200 to the cloud account B on the Trust Ring Device Cloud, the electronic device 100 also needs to perform Trust Ring authentication on the large-screen device 200 using the second connection code. After the Trust Ring authentication is successful, meaning the large-screen device 200 is a user-authorized device for Trust Ring registration, the electronic device 100 can then bind the device information of the large-screen device 200 to the cloud account B on the Trust Ring Device Cloud. Although both IoT authentication and Trust Ring authentication use the second connection code, their authentication mechanisms are different. Therefore, after obtaining the second connection code, the smart space service 103 can cache the second connection code and then send it to the interconnection middleware 106 and the device access module 107 respectively. This allows the interconnection middleware 106 to complete IoT authentication with the large-screen device 200, and the device access module 107 to complete Trust Ring authentication with the large-screen device 200.

[0374] For example, the IoT authentication mechanism can use password authentication. If the second connection code is the same as the first connection code displayed on the large screen device 200, the IoT authentication is successful; if the second connection code is different from the first connection code displayed on the large screen device 200, the IoT authentication fails.

[0375] For example, the trust ring authentication mechanism can employ both cryptographic authentication and public key authentication. If the electronic device 100 and the large screen device 200 successfully authenticate each other and the second connection code matches the first connection code displayed on the large screen device 200, then the trust ring authentication succeeds. If the electronic device 100 and the large screen device 200 fail to authenticate each other or the second connection code differs from the first connection code displayed on the large screen device 200, then the trust ring authentication fails.

[0376] For example, the trust ring authentication mechanism can employ both password authentication and device certificate authentication. If the device certificate authentication between electronic device 100 and large screen device 200 is successful and the second connection code matches the first connection code displayed on large screen device 200, then the trust ring authentication is successful. If the device certificate authentication between electronic device 100 and large screen device 200 fails, or if the second connection code differs from the first connection code displayed on large screen device 200, then the trust ring authentication fails.

[0377] S227. Smart Space Service 103 sends an IoT authentication request to IoT SDK 201 through Interconnect Middleware 106, wherein the IoT authentication request carries a second connection code.

[0378] In one example, an IoT authentication request can be referred to as a first authentication request.

[0379] S228.IoT SDK201 responds to IoT authentication requests by performing IoT authentication based on a first connection code and a second connection code.

[0380] S229.IoT SDK201 returns a successful IoT authentication result to Smart Space Service 103.

[0381] S230. In response to the successful IoT authentication result, the smart space service 103 sends an IoT registration request to the interconnection middleware 106, wherein the IoT registration request carries the cloud account A and the device information of the large screen device 200.

[0382] Among them, cloud account A is the cloud account logged into the smart space application of electronic device 100.

[0383] S231. Interconnect middleware 106 binds the device information of large screen device 200 to cloud account A on the IoT device cloud.

[0384] S232. Interconnect middleware 106 returns an IoT registration success result to smart space service 103.

[0385] S233. In response to the successful IoT registration result, the smart space service 103 obtains the registration file of the large screen device 200, wherein the registration file of the large screen device 200 includes the device information of the large screen device 200.

[0386] S234. The smart space service 103 sends a trust ring authentication request to the device access module 107, wherein the trust ring authentication request carries a second connection code.

[0387] In one example, the trust ring authentication request can be referred to as the second authentication request.

[0388] S235. The device access module 107 performs trust ring authentication with the large screen device 200 based on the second connection code.

[0389] S236. Device access module 107 returns a successful trust ring authentication result to smart space service 103.

[0390] S237. The smart space service 103 sends a trust ring registration request to the device management module 108, wherein the trust ring registration request carries the cloud account B and the registration file of the large screen device 200.

[0391] Cloud account B is the cloud account used by the smart interconnection service of electronic device 100. That is, it is the account corresponding to the trust ring to which electronic device 100 belongs. Cloud account B may be the same as or different from cloud account A mentioned above.

[0392] S238. The device management module 108 binds the device information of the large screen device 200 to the cloud account B on the trust ring device cloud according to the registration file.

[0393] During the trust ring registration process, the device information of the large-screen device 200 needs to be packaged into a registration file in a specified format (e.g., JSON format). Therefore, after receiving the registration file from the large-screen device 200, the device management module 108 can send cloud account B and the registration file of the large-screen device 200 to the trust ring device cloud. After receiving cloud account B and the registration file of the large-screen device 200, the trust ring device cloud can bind cloud account B to the device information of the large-screen device 200.

[0394] S239. If the registration file of the large screen device 200 is successfully bound to the cloud account B on the Trust Ring device cloud, the device management module 108 returns a successful Trust Ring registration result to the smart space service 103.

[0395] Because the "AirView" function projects the interface of an application on electronic device 100 onto a large-screen device 200, it raises concerns about user privacy and security. Therefore, before using the AirView function with the large-screen device 200, the user must trigger the binding of the device information of the large-screen device 200 to the cloud account B used for the smart interconnection service on electronic device 100 within the trusted ring device cloud. After binding the device information of the large-screen device 200 to the cloud account B used for the smart interconnection service on electronic device 100, both electronic device 100 and large-screen device 200 are within the same trusted ring. Therefore, the large-screen device 200 is a trusted device for electronic device 100, and user privacy is guaranteed.

[0396] S240. Smart Space Service 103 establishes a session with the Remote Vision application based on P2P connection through Interconnect Middleware 106 and IoT SDK 201.

[0397] S241. Smart Space Service 103 displays the remote control interface of the large screen device 200.

[0398] After establishing a session with the remote vision application 202 via the interconnection middleware 106 and IoT SDK 201 based on a P2P connection, the smart space service 103 can display the above-mentioned information sequentially. Figures 2K to 2N The interface shown will not be described in detail here.

[0399] The remote control interface can be referenced from the above. Figure 2N The remote control interface 420 in the illustrated embodiment will not be described in detail here.

[0400] S242. The Air Vision application 202 displays a function introduction interface, which includes introductory information about the Air Vision function and controls for getting started.

[0401] For example, the feature introduction interface can refer to the above. Figure 2O The functional description interface 430 in the illustrated embodiment will not be described in detail here.

[0402] S243. The AirView application detected that the user's input or the duration of the function introduction interface for starting to use the control exceeded the duration threshold.

[0403] S244. In response to the user's input or display of the function introduction interface for starting to use the control exceeding the duration threshold, the Air Vision application 202 and the Smart Space Service 103 execute the Air Vision function.

[0404] For example, the remote vision application 202 and the smart space service 103 can perform remote vision functions as described above. Figures 2P to 2Q The specific implementation examples will not be described in detail here.

[0405] S245. If binding the device information of the large screen device 200 to the cloud account B fails on the Trust Ring device cloud, the device management module 108 returns a Trust Ring registration failure result to the smart space service 103.

[0406] S246. The smart space service 103 sends an IoT deregistration request to the interconnect middleware 106, wherein the IoT deregistration request carries the device information of the large screen device 200.

[0407] S247. In response to the IoT deregistration request, the interconnect middleware 106 unbinds the device information of the large screen device 200 from the cloud account A on the IoT device cloud.

[0408] If binding the device information of the large-screen device 200 to cloud account B fails on the Trust Ring device cloud, it means that the large-screen device 200 cannot perform the AirSight function with the electronic device 100. Therefore, unbinding the device information of the large-screen device 200 from cloud account A on the IoT device cloud allows the large-screen device 200 to revert to its incomplete IoT registration state. This way, when the large-screen device 200 approaches the electronic device 100 again, it can send a BLE broadcast packet to trigger the electronic device 100 to display the discovery window of the large-screen device 200, prompting the user to authorize the electronic device 100 to re-add the large-screen device 200 and re-register for IoT and Trust Ring. This allows users to easily re-register the large-screen device 200 for IoT and Trust Ring when Trust Ring registration fails.

[0409] In one possible implementation, steps S246 to S247 are optional. After receiving the trust ring registration failure result, the smart space service 103 can trigger the device management module 108 to send the trust ring registration request again after detecting the user's input to enable the air vision function. This allows the device management module 108 to re-bind the device information of the large screen device 200 with the cloud account B on the trust ring device cloud according to the registration file of the large screen device 200.

[0410] The device control method provided in this application, which includes the initial addition of a large-screen device to an electronic device, allows the electronic device 100 to operate without complex steps such as scanning QR codes on the large-screen device 200, or logging into the same account as the large-screen device 200. A discovery pop-up window appears simply by the electronic device 100 being near the large-screen device 200. Upon receiving confirmation from the user in the discovery pop-up window, the electronic device 100 binds its logged-in cloud account A and cloud account B to the device information of the large-screen device 200 on the cloud server. This completes the IoT registration and trust ring registration of the large-screen device 200, making it a trusted device. This allows users to securely and quickly use applications on the electronic device 100 on the large-screen device 200. This also simplifies the user's workflow when using applications on the large-screen device 200.

[0411] The above is introduced below. Figure 14B The embodiment shown illustrates the specific process of obtaining the registration file of the large-screen device 200.

[0412] Figure 15 This is a schematic diagram illustrating the specific process of obtaining the registration file of a large-screen device in the device control method provided in this application embodiment.

[0413] like Figure 15 As shown, the specific process of obtaining the registration file of the large-screen device 200 can be applied to a communication system that includes the electronic device 100 and the large-screen device 200. The electronic device 100 may include iConnect 101, Smart Space Service 103, Gesture View Service 104, and Device Management Module 108. The large-screen device 200 may include IoT SDK 201, Gesture View Application 202, and Gesture View SDK 203.

[0414] The process by which the smart space service 103 obtains the registration file of the large-screen device 200 may include the following steps:

[0415] S301. The Air Vision application 202 sends an initialization request to the Air Vision SDK 203.

[0416] S302. In response to the initialization request, the AirView SDK generates device information for the large screen device 200.

[0417] The device information of the large screen device 200 may include one or more of the following: product identifier of the large screen device 200, device name of the large screen device 200, device identifier of the large screen device 200, and device sub-identifier of the large screen device 200.

[0418] S303. Air Vision Application 202 controls large screen device 200 to send BLE broadcast packets.

[0419] The S304.iConnect101 displays a discovery window for the large-screen device 200.

[0420] The S305.iConnect101 receives input from the user confirming the connection to the large screen device 200 in the discovery window.

[0421] The discovery window for the large-screen device 200 can be referenced as described above. Figure 2B The discovery window 320 in the illustrated embodiment will not be described in detail here. The user's input for confirming connection to the large-screen device 200 in the discovery window of the large-screen device 200 can be as described above. Figure 2B The illustrated embodiment shows the user's input to the connection control 325 in the discovery window 320.

[0422] S306.iConnect101 responds to the user's input confirming the connection to the large screen device 200 in the discovery window and starts the smart space service 103.

[0423] After activating the smart space service 103, the smart space service 103 can work with other modules to perform the aforementioned tasks. Figures 14A-14B Steps S202 to S226 in the illustrated embodiment will not be repeated here.

[0424] S307. Smart Space Service 103 and IoT SDK 201 perform IoT certification and IoT registration.

[0425] The process of IoT certification and registration for Smart Space Service 103 and IoT SDK 201 can be found above. Figure 14B Steps S227 to S232 in the illustrated embodiment.

[0426] After successful IoT registration, S308. Smart Space Service 103 sends a request to IoT SDK 201 to obtain the registration file.

[0427] Upon receiving a request, S309.IoT SDK201 can send a request to the GeekVision SDK203 through the GeekVision application202.

[0428] S310. In response to the request, IoT SDK201 generates a registration file based on the device information of the large screen device 200.

[0429] The registration documents for the large-screen device 200 include the device information of the large-screen device 200.

[0430] S311. The AirView application 203 returns the registration file of the large screen device 200 to the IoT SDK 201.

[0431] S312.IoT SDK201 returns the registration file of the large-screen device 200 to the smart space service 103.

[0432] S313. The Smart Space Service 103 calls the Registration Trust Ring Interface to transmit the registration file to the Device Management Module 108 through the Remote Vision Service 104.

[0433] After receiving the registration file, the device management module 108 can bind the registration file of the large screen device 200 to the cloud account B on the Trust Ring device cloud.

[0434] By using the device control method provided in this embodiment to obtain the registration file of the large-screen device, the electronic device 100 can add the large-screen device 200 to the trust ring corresponding to the cloud account B used by the smart interconnection service on the electronic device 100. This allows the large-screen device 200 to be a trusted device of the electronic device 100, enabling it to call applications on the electronic device 100. This improves the security of users using applications on the electronic device 100 on the large-screen device 200.

[0435] The following is in conjunction with the above. Figures 20 to 2Q or Figures 7A to 7F The illustrated embodiment specifically describes the process of enabling the air-to-view function between the electronic device 100 and the large-screen device 200.

[0436] Figure 16 This is a schematic diagram illustrating the process of enabling the first electronic device and the large screen device to perform a remote viewing function in the device control method provided in this application embodiment.

[0437] Through the embodiments of this application Figure 16 The illustrated process describes the interaction between the electronic device 100 and the large-screen device 200 using a gesture-of-view function. The electronic device 100 can send application information of one or more applications installed on it to the large-screen device 200. Upon receiving this application information, the electronic device 100 can display the application information of one or more applications. Upon receiving input from the user selecting a target application from one or more applications, the large-screen device 200 can send the application identifier of the target application to the electronic device 100. Upon receiving the application identifier, the electronic device 100 can send first data to the large-screen device. Upon receiving the first data, the large-screen device 200 can display the interface of the target application based on the first data.

[0438] In this way, users can control the target application installed on the electronic device 100 from the large screen device 200, and view the interface of the target application installed on the electronic device 100 from the large screen device 200, thus improving the user experience of using the application.

[0439] like Figure 16 As shown, the specific process of the air gesture communication function between electronic device 100 and large screen device 200 can be applied to a communication system including electronic device 100 and large screen device 200. Electronic device 100 may include an air gesture communication service 104, a basic middleware platform 109, a source-end projection service 110, a source-end audio virtual service 111, a source-end audio framework 112, and a target application 113. Large screen device 200 may include an air gesture communication application 202, an air gesture communication SDK 203, a trust ring system 204, a destination-end projection service 205, and a destination-end audio virtual service 206.

[0440] S401. The AirView application 202 detected user input to enable the AirView function.

[0441] In one possible implementation, the user's input to activate the air vision function could be the user's input of the above... Figure 2O The example shown begins with the input of control 432. For details, please refer to the above. Figure 2O The embodiments shown are not described in detail here.

[0442] In another possible implementation, the input for the user to activate the air vision function could be as described above. Figure 7A In the illustrated embodiment, the user selects the "Air View" option 712 and then selects... Figure 7C The illustrated embodiment shows the input of device option 732. For details, please refer to the above. Figures 7A-7D The embodiments shown are not described in detail here.

[0443] S402. In response to the user's input to turn on the AirView function, the AirView application 202 can launch the AirView SDK 203.

[0444] After the S403.AirView SDK203 is started, the Trust Ring System 204 can be started.

[0445] After startup, the S404 Trust Ring System 204 can establish a session with the Basic Platform 109.

[0446] After establishing a session with the Trust Ring System 204, the Basic Platform 109 can start the Remote Vision Service 104.

[0447] S406. The Remote View service 104 can display an authorization window after it is started.

[0448] The authorization window can be referenced as described above. Figure 7E The authorization window 740 in the illustrated embodiment will not be described in detail here.

[0449] S407. The Remote View service 104 detected that the user entered an agreement to authorize in the authorization window.

[0450] The user's input in the authorization window to agree to the authorization can be the user's consent to the above. Figure 7E The input of the control 744 is enabled in the illustrated embodiment, and will not be described in detail here.

[0451] In one possible implementation, as described above Figures 20 to 2Q When the electronic device 100 and the large screen device 200 are using the air-to-view function, Figure 16 Steps S405 to S407 shown are optional. If the user activates the air-view function, the input is for the user's... Figure 2O In the illustrated embodiment, when the user begins inputting using control 432, the electronic device 100 has already started the AirView service 104, therefore there is no need to start the AirView service 104 again. The AirView application 202 in the large-screen device 200 can respond to the user's input as described above. Figure 2O In the illustrated embodiment, the AirView SDK 203 is activated when input from control 432 is initiated, or when the duration of the function introduction interface 430 is detected to exceed a duration threshold (e.g., 2 seconds). After activation, the AirView SDK 203 can activate the Trust Ring System 204. After activation, the Trust Ring System 204 can establish a session with the base platform 109. The AirView application 202 can send an application list request to the AirView service 104 via the session. In response to the application list request, the AirView service 104 can obtain application information for one or more installed applications on the electronic device 100 and identify one or more whitelisted applications from among the installed applications.

[0452] S408. In response to the user's input of consent in the authorization window, the AirView service 104 obtains application information of the applications installed on the electronic device 100 and identifies one or more whitelisted applications from among the multiple installed applications.

[0453] Because some installed applications on electronic device 100 have high privacy requirements or high system permissions, making them unsuitable for screen mirroring, electronic device 100 can filter out one or more whitelisted applications that can be mirrored. This ensures the security and privacy of some applications on electronic device 100.

[0454] The electronic device 100 may store a whitelist, which may include identifiers of applications that are allowed to be projected using the AirView function. Therefore, the electronic device 100 can filter out one or more whitelisted applications that are allowed to be projected using the AirView function from its installed applications based on the whitelist.

[0455] S409. The Remote Vision Service 104 sends application information of one or more whitelisted applications to the Remote Vision Application 202 through the Basic Platform 109, Trust Ring System 204, and Remote Vision SDK 203. The application information may include application icons and application identifiers.

[0456] S410. AirView application 202 displays application information for one or more whitelisted applications.

[0457] The "Air View" application 202 can display application information for one or more whitelisted applications on the Air View function interface. Since one or more whitelisted applications are not necessarily all applications of the electronic device 100, the desktop layout of the electronic device 100 cannot be directly used by the large-screen device 200. The application information for one or more applications displayed on the large-screen device 200 is drawn by the large-screen device itself and is likely different from the desktop layout of the electronic device 100. Therefore, when the large-screen device 200 receives input from the user selecting a target application from one or more whitelisted applications, if it only sends the touch coordinates corresponding to the user input to the electronic device 100, the electronic device 100 cannot recognize the application operated by the user. Therefore, in this embodiment, when the large-screen device 200 receives input from the user selecting a target application from one or more whitelisted applications, the large-screen device 200 needs to determine the first application corresponding to the user input based on the coordinates corresponding to the user input, and then send the application identifier of the target application to the electronic device 100. This allows the electronic device 100 to send first data to the large-screen device after receiving the application identifier of the target application. After receiving the first data, the large-screen device 200 can display the interface of the first application based on the first data. Therefore, after receiving application information from one or more whitelisted applications, the AirView application 202 on the large-screen device 200 needs to rearrange the application information of one or more whitelisted applications and draw the AirView function interface.

[0458] Large screen devices 200 do not have one or more of these whitelisted applications installed.

[0459] For example, the application information displayed by the AirView application 202 for one or more whitelisted applications can be found in the above description. Figure 2P The embodiments shown are not described in detail here.

[0460] S411. The AirView app 202 detected that the user selected one or more whitelisted target apps.

[0461] For example, the target application could be a video application, and the user could select one or more whitelisted applications. The input for the target application could be the user's choice of the above-mentioned applications. Figure 2P For details regarding the input of icon 443 for the video application in the illustrated embodiment, please refer to the above. Figure 2P The embodiments shown are not described in detail here.

[0462] In one example, the user's selection of the target application's input from one or more whitelisted applications can be referred to as the fourth operation.

[0463] S412. In response to the user's input of selecting one or more whitelisted applications as the target application, the AirView application 202 sends an application casting request to the AirView SDK 203, wherein the application casting request carries the application identifier of the target application.

[0464] S413. In response to the application's screen mirroring request, AirView SDK 203 starts the destination screen mirroring service 205.

[0465] S414. In response to the application's screen mirroring request, AirView SDK 203 starts the destination audio virtual service 206.

[0466] After receiving the application's screen mirroring request, the S415.AirView SDK203 sends an audio and video channel creation request to the Trust Ring System 204.

[0467] Since the AirView application 202 on the large-screen device 200 displays one or more whitelisted target applications through the AirView function interface, only the AirView application 202 on the large-screen device 200 knows which application the user has selected from the AirView function interface. When the AirView application 202 on the large-screen device 200 detects the user's input of selecting the target application, since the target application is not installed on the large-screen device 200, the large-screen device 200 cannot directly draw the target application's interface. Therefore, the large-screen device 200 needs to request the electronic device 100 to launch the target application and project the target application's interface onto the large-screen device 200 for display.

[0468] S416. In response to the audio / video channel creation request, the trust ring system 204 and the basic middleware 109 establish an audio / video transmission channel on the session.

[0469] S417. The Remote Vision SDK 203 sends an application startup request to the Remote Vision Service 104 through the Trust Ring System 204 and the Basic Platform 109. The application startup request carries the application identifier of the target application.

[0470] S418. In response to the application startup request, the AirView service 104 starts the source screen mirroring service 110.

[0471] S419. In response to the application startup request, the AirView service 104 starts the source audio virtual service 111.

[0472] After the S420 source-side projection service 110 is started, it creates a virtual display screen.

[0473] S421. After successfully creating a virtual display screen, the source-end projection service 110 returns information about the virtual display screen to the air-view service 104.

[0474] S422. After receiving the information from the virtual display screen, the remote viewing service 104 starts the target application 113 and sends the information from the virtual display screen to the target application 113.

[0475] S423. After startup, target application 113 can send an image stream to the virtual display screen based on the information of the virtual display screen.

[0476] After the target application 113 starts up and receives information from the virtual display screen, it can determine that the image stream generated by the target application 113 needs to be sent to the virtual display screen, rather than to the physical display screen on the electronic device 100.

[0477] S424. Source casting service 110 can acquire image streams from virtual displays.

[0478] When the target application 113 sends an image stream to the virtual display screen, the source screen mirroring service 110 can continuously acquire the image stream from the virtual display screen in chronological order.

[0479] S425. Source screen mirroring service 110 can send image streams to destination screen mirroring service 205 through audio and video transmission channels.

[0480] In this process, the source-end projection service 110 can first send an image stream to the basic middleware platform 109. Then, the basic middleware platform 109 can send the image stream to the trust ring system 204 through the audio and video transmission channel. The trust ring system 204 can then send the received image stream to the destination-end projection service 205.

[0481] S426. Destination screen mirroring service 205 sends an image stream to AirView application 202.

[0482] S427. AirView application 202 decodes and renders the display image stream.

[0483] Since the image stream includes the interface of the target application 113, when the AirView application 202 decodes and renders the image stream, the interface of the target application 113 can be displayed on the large screen device 200.

[0484] S428. After startup, the target application 113 can send an audio stream to the source audio framework 112.

[0485] S429. The source audio virtual service 111 can obtain audio streams from the source audio framework 112.

[0486] Specifically, the source-side audio virtual service 111 obtains the audio stream from the source-side audio framework 112, allowing the source-side audio framework 112 to redirect the audio stream from the electronic device 100 to the large-screen device 200 for playback. This improves the user experience when using the target application installed on the electronic device 100 on the large-screen device 200.

[0487] S430. Source audio virtual service 111 sends an audio stream to destination audio virtual service 206 through the audio and video transmission channel.

[0488] In this system, the source audio virtual service 111 can first send the audio stream to the basic middleware 109. Then, the basic middleware 109 can send the audio stream to the trust ring system 204 through the audio and video transmission channel. The trust ring system 204 can then send the received audio stream to the destination audio virtual service 206.

[0489] S431. The destination audio virtual service 206 can play audio streams.

[0490] When the destination audio virtual service 206 receives an audio stream, it can send the audio stream to the destination audio framework. Figure 16 (Not shown in the image) will be played.

[0491] Since the target application is not installed on the large-screen device 200, when displaying the target application's interface on the electronic device 100, the large-screen device 200 cannot know what content is present on the target application's interface. Therefore, when displaying the target application's interface, if the large-screen device 200 receives user actions on the target application's interface, it cannot directly identify which specific instructions the user is using. Therefore, the large-screen device 200 needs to send the coordinates of the user's actions on the target application's interface to the electronic device 100. The electronic device 100 can then identify the user's selected instruction on the target application's interface based on these coordinates, such as switching videos or changing interfaces. Then, the electronic device 100 can determine the next interface corresponding to the user's action through the target application. Finally, the electronic device 100 can send the next interface drawn by the target application to the large-screen device 200 for display. This allows the user to directly use the application on the electronic device 100 on the large-screen device 200, without having to switch back and forth between the two devices.

[0492] Through the device control method provided in this application embodiment, electronic device 100 can send application information of one or more applications installed on electronic device 100 to large-screen device 200. After receiving the application information of one or more applications, electronic device 100 can display the application information of one or more applications. After receiving input from a user selecting a target application among one or more applications, large-screen device 200 can send the application identifier of the target application to electronic device 100. After receiving the application identifier of the target application, electronic device 100 can send first data to large-screen device. After receiving the first data, large-screen device 200 can display the interface of the target application based on the first data.

[0493] In this way, users can control the target application installed on the electronic device 100 from the large screen device 200, and view the interface of the target application installed on the electronic device 100 from the large screen device 200, thus improving the user experience of using the application.

[0494] The following is in conjunction with the above. Figures 5A-5J The illustrated embodiment specifically describes the process by which electronic device 300 uses large-screen device 200 after receiving a shared large-screen device 200.

[0495] Figures 17A-17B This is a schematic diagram illustrating the process of the second electronic device using the large-screen device for the first time after receiving the shared large-screen device in the device control method provided in this application embodiment.

[0496] like Figure 17A , Figure 17BAs shown, the process of electronic device 300 using large-screen device 200 for the first time after receiving a shared device can be applied to a communication system including electronic device 300 and large-screen device 200. Electronic device 300 may include smart space service 3001, device control card 3002, air vision service 3003, interconnection middleware 3004, device access module 3005, and device management module 3006. Large-screen device 200 may include IoT SDK 201 and air vision application 202.

[0497] After a user accepts a share of a large-screen device 200 from electronic device 100 on electronic device 300, electronic device 300 can send an acceptance response to the IoT device cloud on cloud server 400. Upon receiving this response, the IoT device cloud on cloud server 400 can bind the device information of the large-screen device 200 to the cloud account C logged into the smart space application on electronic device 300. At this point, the device information of the large-screen device 200 is bound to at least cloud account A and cloud account C in the IoT device cloud. In this way, cloud server 400 can directly complete the IoT registration of large-screen device 200 on behalf of electronic device 300, eliminating the need for electronic device 300 to initiate IoT registration for large-screen device 200. Electronic device 300 can directly initiate trust ring registration for large-screen device 200, allowing electronic device 300 to quickly establish interconnection functions with large-screen device 200.

[0498] Therefore, both electronic device 100, logged into cloud account A in the smart space application, and electronic device 300, logged into cloud account C in the smart space application, can control the large-screen device 200. After the IoT device cloud of cloud server 400 binds the device information of the large-screen device 200 with the cloud account C logged into the smart space application on electronic device 300, it can return a successful IoT device registration result to electronic device 300. Electronic device 300 can respond to the successful IoT device registration result by displaying the control card of the large-screen device 200 on the main interface of the smart space application. The control card of the large-screen device 200 can be referenced as described above. Figure 5B The control card 566 in the illustrated embodiment will not be described in detail here.

[0499] The process of electronic device 300 using large-screen device 200 for the first time after receiving a shared large-screen device 200 may include the following steps:

[0500] S501. Smart Space Service 3001 detected that the user opened the device details interface of the large screen device 200 and entered information.

[0501] For example, the input for a user to open the device details page of the large-screen device 200 can be the user's input regarding the above-mentioned... Figure 5BFor details regarding the input of the control card 566 of the large-screen device 200 in the illustrated embodiment, please refer to the above. Figure 5B The embodiments shown are not described in detail here.

[0502] S502. In response to the user's input to open the device details interface of the large screen device 200, the smart space service 3001 sends a loading request to the device control card 3002, wherein the loading request is used to load the device details interface of the large screen device 200.

[0503] S503. In response to the loading request, the device control card 3002 sends a capability query request to the smart space service 3001.

[0504] Among them, the capability query request is used to query whether the electronic device 300 supports the air vision function.

[0505] S504. Smart Space Service 3001 sends a capability query request to Remote Vision Service 3003.

[0506] S505. In response to the capability query request, the Remote Vision Service 3003 returns the query result E to the Smart Space Service 3001.

[0507] S506. Smart Space Service 3001 returns query result E to Device Control Card 3002.

[0508] S507. Based on the query result E, the device control card 3002 determines whether the electronic device 300 supports the air-viewing function.

[0509] S508. If the electronic device 300 supports the air gesture control function, the device control card 3002 displays the device details interface of the large screen device 200, and displays the air gesture control on the device details interface of the large screen device 200.

[0510] For example, the device details interface of the large-screen device 200 can be referenced as described above. Figure 5C The device details interface 570 in the illustrated embodiment, the air view control can be referenced as described above. Figure 5C The air view function control 575 in the device details interface 570 of the illustrated embodiment will not be described in detail here.

[0511] In one possible implementation, if the electronic device 300 does not support the air gesture control function, the device control card 3002 can display the device details interface of the large screen device 200, and the air gesture control will not be displayed in the device details interface of the large screen device 200.

[0512] S509. Device control card 3002 detected user input to the remote view control.

[0513] S510. In response to the user's input to the remote vision control, the device control card 3002 sends a registration query request to the smart space service 3001.

[0514] Among them, the registration query request can be used to query whether the device information of the large screen device 200 is bound to the cloud account D used by the smart interconnection service of the electronic device 300.

[0515] S511. Smart Space Service 3001 forwards a registration query request to Device Management Module 3006 through Remote Vision Service 3003.

[0516] S512. In response to the registration query request, the device management module 3006 returns the registration query result to the smart space service 3001 through the remote vision service 3003.

[0517] The device management module 3006 can store a list of trusted ring devices corresponding to cloud account D. This list can store device information for devices logged into or bound to cloud account D. Therefore, if the trusted ring device list for cloud account D includes the device information for large screen device 200, then large screen device 200 is bound to cloud account D. If the trusted ring device list for cloud account D does not include the device information for large screen device 200, then large screen device 200 is not bound to cloud account D.

[0518] S513. Smart Space Service 3001 returns the registration query results to Device Control Card 3002.

[0519] S514. Based on the registration query results, the device control card 3002 determines whether the device information of the large screen device 200 has been bound to the cloud account D used by the smart interconnection service of the electronic device 300.

[0520] S515. If the device information of the large screen device 200 is already bound to the cloud account D used by the smart interconnection service of the electronic device 300, the device control card 3002 can display the introduction interface of the air vision function, and the immediate experience control is not displayed on the air vision function introduction interface.

[0521] Before initiating the binding of device information of large-screen device 200 with cloud account D, Smart Space Service 3001 needs to respond to user input via the "Instant Experience" control, triggering the display of the Smart Interconnection Privacy Window on electronic device 300. Only after the user authorizes and agrees to add large-screen device 200 to the trust ring corresponding to cloud account D on electronic device 300 in the Smart Interconnection Privacy Window can Smart Space Service 3001 initiate the binding of device information of large-screen device 200 with cloud account D. If device information of large-screen device 200 is already bound to cloud account D, it means that large-screen device 200 and electronic device 300 are already in the same trust ring, and Smart Space Service 3001 does not need to initiate the binding of device information of large-screen device 200 with cloud account D again. Therefore, Smart Space Service 3001 does not need to display the "Instant Experience" control on the AirView function interface.

[0522] When device control card 3002 detects that large screen device 200 is online in the local area network, it displays the introduction interface for the Air View function and displays the "Experience Now" control on the Air View function introduction interface.

[0523] For example, the interface for introducing the Air View feature can be referenced as described above. Figure 5E The interface 590 for introducing the air-view function in the illustrated embodiment, and the immediate experience controls can be found above. Figure 5E The immediate experience control 593 in the illustrated embodiment will not be described in detail here.

[0524] S517. Device control card 3002 detected user input to the immediate experience control.

[0525] S518. In response to the user's input to the immediate experience control, the device control card 3002 sends a request to the smart space service 3001 to open the remote vision.

[0526] S519. After receiving the request to enable the remote vision, the smart space service 3001 sends a smart interconnection enable request to the remote vision service 3003.

[0527] Among them, the Smart Space Service 3001 can respond to the request to open the remote vision and first display the above. Figure 5F The illustrated embodiment shows a smart interconnected privacy window 594. The smart space service 3001 can respond to user input on the consent control 596 in the smart interconnected privacy window 594 by sending a smart interconnection activation request to the remote vision service 3003.

[0528] S520. The Remote Vision Service 3003 returns the result that Smart Interconnection has been activated to the Smart Space Service 3001.

[0529] S521. In response to the result that smart interconnection has been enabled, smart space service 3001 sends connection code request B to IoT SDK201 through interconnection middleware 3004.

[0530] Among them, connection code request B can be used to request the large screen device 200 to generate and display a connection code.

[0531] S522. In response to connection code request B, IoT SDK201 generates a third connection code.

[0532] S523.IoT SDK201 sends a display request B to the AirView application 202, wherein the display request B carries a third connection code.

[0533] S524. Air Vision Application 202 displays Connection Code Page B, wherein Connection Code Page B includes a third connection code.

[0534] For example, page B with the connection code can refer to the above. Figure 5G The connection code page 610 in the illustrated embodiment will not be described in detail here.

[0535] S525. The Remote Vision Application 202 returns the page display results to the Smart Space Service 3001 through the IoT SDK 201 and the Interconnection Middleware 3004.

[0536] S526. If the page displays the result that the large screen device 200 has successfully displayed the connection code page B, the smart space service 3001 displays the connection code input window B.

[0537] For example, connection code input window B can refer to the above. Figure 5H The connection code input window 620 in the illustrated embodiment will not be described in detail here.

[0538] If the page displays a result indicating that the large screen device 200 has failed to display the connection code page B, the smart space service 3001 can display a connection failure message. This connection failure message can be used to indicate that the electronic device 300 has failed to connect to the large screen device 200.

[0539] S527. Smart Space Service 3001 receives the fourth connection code entered by the user in the connection code input window B.

[0540] S528. In response to the fourth connection code entered by the user in the connection code input window B, the Smart Space Service 3001 can display a "Starting" prompt.

[0541] The "Activating" message indicates that the AirView feature is being activated. For example, the "Activating" message can be found above. Figure 5I The "Starting" prompt 631 in the illustrated embodiment will not be described again here.

[0542] S529. Smart Space Service 3001 obtains the registration file of large screen device 200, wherein the registration file of large screen device 200 includes device information of large screen device 200.

[0543] The registration file for the large-screen device 200 can be in JSON format. The process for obtaining the registration file for the large-screen device 200 using the Smart Space Service 3001 can be referenced above. Figure 15 The process by which the electronic device 100 obtains the registration file of the large-screen device 200 in the illustrated embodiment will not be described in detail here.

[0544] S530. The smart space service 3001 sends a trust ring authentication request to the device access module 3005, wherein the trust ring authentication request carries a fourth connection code.

[0545] S531. The device access module 3005 performs trust ring authentication with the large screen device 200 based on the fourth connection code.

[0546] For example, the trust ring authentication mechanism can employ both cryptographic authentication and public key authentication. If the electronic device 300 and the large screen device 200 successfully authenticate each other and the fourth connection code matches the third connection code displayed on the large screen device 200, then the trust ring authentication succeeds. If the electronic device 300 and the large screen device 200 fail to authenticate each other, or if the fourth connection code differs from the third connection code displayed on the large screen device 200, then the trust ring authentication fails.

[0547] For example, the trust ring authentication mechanism can employ both password authentication and device certificate authentication. If the device certificate authentication between electronic device 300 and large screen device 200 is successful and the fourth connection code matches the third connection code displayed by large screen device 200, then the trust ring authentication is successful. If the device certificate authentication between electronic device 300 and large screen device 200 fails, or if the fourth connection code differs from the third connection code displayed by large screen device 200, then the trust ring authentication fails.

[0548] S532. Device access module 3005 returns a successful trust ring authentication result to smart space service 3001.

[0549] S533. The smart space service 3001 sends a trust ring registration request to the device management module 3006, wherein the trust ring registration request carries the registration file of the large screen device 200.

[0550] S534. In response to the trust ring registration request, the device management module 3006 binds the device information of the large screen device 200 with the cloud account D on the trust ring device cloud according to the registration file of the large screen device 200.

[0551] During the trust ring registration process, the device information of the large-screen device 200 needs to be packaged into a specified format (e.g., JSON format). Therefore, after receiving the registration file from the large-screen device 200, the device management module 3006 can send the cloud account D and the registration file of the large-screen device 200 to the trust ring device cloud. After receiving the cloud account D and the registration file of the large-screen device 200, the trust ring device cloud can bind the cloud account D to the device information of the large-screen device 200.

[0552] S535. Device Management Module 3006 returns a successful trust ring registration result to Smart Space Service 3001.

[0553] Because the "AirView" function projects the interface of an application on electronic device 300 onto a large-screen device 200, it raises concerns about user privacy and security. Therefore, before the "AirView" function can be used between electronic device 300 and large-screen device 200, the user must trigger the binding of the device information of large-screen device 200 with the cloud account D used for the smart interconnection service on electronic device 300 within the trusted ring device cloud. After binding the device information of large-screen device 200 with the cloud account D used for the smart interconnection service on electronic device 300, both electronic device 300 and large-screen device 200 are within the same trusted ring. Therefore, large-screen device 200 is a trusted device for electronic device 300, and user privacy is guaranteed.

[0554] S536. Smart Space Service 3001 and Remote Vision Application 202 establish a session based on P2P connection.

[0555] S537. After the Smart Space Service 3001 and the Remote View Application 202 establish a session based on a P2P connection, the remote control interface of the large screen device 200 is displayed.

[0556] After establishing a session with the remote vision application 202 via the interconnection middleware 3004 and IoT SDK 201 based on a P2P connection, the smart space service 3001 can display the above-mentioned information sequentially. Figure 5J The remote control interface 640 shown above; for details, please refer to the above. Figure 5J The embodiments shown are not described in detail here.

[0557] S538. After establishing a session with the Smart Space Service 3001 based on a P2P connection, the Remote Vision Application 202 displays a function introduction interface, which includes controls for getting started.

[0558] For example, the feature introduction interface can refer to the above. Figure 2O The functional description interface 430 in the illustrated embodiment will not be described in detail here.

[0559] S539. The Air Vision application detected that the user's input to the start-up control or the duration of the function introduction interface exceeded the duration threshold.

[0560] S540. In response to detecting that the user's input to the start-up control or the duration of the function introduction interface exceeds the duration threshold, the Air Vision application 202 and the Smart Space Service 3001 execute the Air Vision function.

[0561] For example, the remote vision application 202 and the smart space service 3001 can implement remote vision functionality by referring to the above. Figure 5K The embodiments shown are not described in detail here.

[0562] The device control method provided in this application, which describes the process of an electronic device using a large-screen device for the first time after receiving a shared large-screen device, allows the IoT device cloud of the cloud server 400 to directly assist the electronic device 300 in completing the IoT registration of the large-screen device 200 after the electronic device 300 receives the shared large-screen device 200 from the electronic device 100. Therefore, the electronic device 300 only needs to bind the device information of the large-screen device 200 with the cloud account D used for the smart interconnection service of the electronic device 300 on the trusted ring device cloud. This enables the electronic device 300 and the large-screen device 200 to perform a remote viewing function, allowing users to quickly use applications on the electronic device 300 on the large-screen device 200 without installation.

[0563] The following describes in detail the process of actively deleting the large-screen device 200 after adding it to the electronic device 100.

[0564] Figure 18 This describes the process by which the first electronic device actively deletes the large-screen device after it has been added, as part of the device control method provided in this application embodiment.

[0565] After electronic device 100 successfully adds large-screen device 200, the device information of large-screen device 200 is simultaneously bound to both cloud account A and cloud account B. Cloud account A may act as the management account for large-screen device 200, sharing it with cloud account C. In this case, the device information of large-screen device 200 is also bound to cloud account C. Therefore, when electronic device 100 receives input from the user to delete the added large-screen device 200 in the smart space application, it can first request the IoT device cloud to unbind the device information of large-screen device 200 from cloud account A. If cloud account A is the management account for large-screen device 200, the IoT device cloud will not only unbind the device information of large-screen device 200 from cloud account A, but also unbind the sharing account of cloud account A (e.g., cloud account C) from the device information of large-screen device 200. This ensures that when unbinding cloud account A from large-screen device 200, the sharing account of cloud account A is also unbound from large-screen device 200.

[0566] After unbinding the device information of large-screen device 200 from cloud account A, electronic device 100 then requests to unbind the device information of large-screen device 200 from cloud account B on the Trust Ring device cloud. This way, when large-screen device 200 is deleted from electronic device 100, the binding relationship between the device information of large-screen device 200 and cloud accounts A and B can be simultaneously unbound. This ensures that electronic device 100 can completely delete the device information of large-screen device 200, guaranteeing that after large-screen device 200 is deleted by electronic device 100, it cannot be controlled by electronic device 100 or other devices, thus ensuring the security of large-screen device 200.

[0567] like Figure 18 As shown, the process of an electronic device actively deleting a large-screen device after adding it is applied to a communication system including an electronic device 100 and a cloud server 400. The electronic device 100 may include a smart space service 103, a remote viewing service 104, an interconnection middleware 106, and a device management module 108. The cloud server 400 may include an IoT device cloud 4001 and a trust ring device cloud 4002.

[0568] The process of actively deleting a large-screen device after it has been added to an electronic device may include the following steps:

[0569] S601. Smart Space Service 103 detected the user's input to delete the large screen device 200.

[0570] For example, a user deleting input from the large-screen device 200 can be done by the user on the above. Figure 4B The embodiment shown deletes the input of device control 514. For details, please refer to the above. Figure 4B The embodiments shown are not described in detail here.

[0571] In one example, the user's input to delete the large screen device 200 can be referred to as the second operation.

[0572] S602. The smart space service 103 sends an IoT deletion request to the interconnect middleware 106, wherein the IoT deletion request carries the device information of the large screen device 200.

[0573] S603. Interconnect middleware 106 sends IoT deregistration request 1 to IoT device cloud 4001, wherein IoT deregistration request 1 carries cloud account A and device information of large screen device 200.

[0574] S604.IoT Device Cloud 4001 determines whether cloud account A is the management account for large screen device 200.

[0575] Among them, the management account of the large-screen device 200 is the first cloud account on the IoT device cloud 4001 to form a binding relationship with the device information of the large-screen device 200. For example, when the large-screen device 200 has not completed IoT registration, it will send a BLE broadcast packet. After receiving the BLE broadcast packet, if the electronic device 100 binds the device information of the large-screen device 200 with the cloud account A logged in in the smart space application of the electronic device 100 on the IoT device cloud 4001 to complete the IoT registration of the large-screen device 200, then the cloud account A is the management account of the large-screen device 200.

[0576] S605. If cloud account A is the management account of large screen device 200, IoT device cloud 4001 removes the binding between cloud account A and the device information of large screen device 200, and removes the binding between the sharing account of cloud account A (including cloud account C) and the device information of large screen device 200.

[0577] In this scenario, electronic device 100 shares the device information of large-screen device 200 with electronic device 300, which is logged into the smart space application using cloud account A. Cloud account A is the management account for large-screen device 200, and management accounts have higher administrative privileges than non-management accounts. Therefore, when electronic device 100, logged into the smart space application using cloud account A, wants to unbind cloud account A from the device information of large-screen device 200, it also needs to unbind cloud account C from the device information of large-screen device 200, thus ensuring the secure use of large-screen device 200.

[0578] S606. If cloud account A is not the management account for large screen device 200, unbind cloud account A from the device information of large screen device 200.

[0579] S607.IoT Device Cloud 4001 returns a successful registration result to Interconnect Middleware 106.

[0580] S608. Interconnect middleware 106 returns a successful IoT deletion result to smart space service 103.

[0581] S609. Smart Space Service 103 determines whether the large screen device 200 supports the air gesture function based on the product identification of the large screen device 200.

[0582] If the large-screen device 200 supports the AirView function, it means that the device information of the large-screen device 200 may already be bound to cloud account B used by the smart interconnection service of electronic device 100. After unbinding the device information of the large-screen device 200 from the cloud account C, electronic device 100 will also be unable to provide the user with any operation entry point to trigger the AirView function between electronic device 100 and large-screen device 200. Therefore, large-screen device 200 does not need to be bound to cloud account D.

[0583] S610. If the large screen device 200 supports the air gesture function, the smart space service 103 sends a capability detection request to the air gesture service 104.

[0584] Among them, the capability detection request is used to detect whether the electronic device 100 supports the air vision function.

[0585] S611. Air Vision Service 104 determines whether electronic device 100 supports the Air Vision function.

[0586] If electronic device 100 supports the air gesture control function, it means that electronic device 100 has already bound the device information of large screen device 200 to cloud account B on the trust ring device cloud 4002. At this time, since the device information of large screen device 200 has been unbound from cloud account A on IoT device cloud 4001, it is necessary to continue unbinding the device information of large screen device 200 from cloud account B on trust ring device cloud 4002. This prevents electronic device 100 from having an unusable device in the trust ring corresponding to cloud account B.

[0587] S612. If the electronic device 100 supports the air gesture function, the air gesture service 104 returns a capability detection result 1 to the smart space service 103, wherein the capability detection result 1 is used to indicate that the large screen device 200 supports the air gesture function.

[0588] S613. The smart space service 103 sends a trust ring deletion request to the device management module 108 through the remote vision service 104. The trust ring deletion request carries the device information of the large screen device 200.

[0589] S614. In response to the trust ring deletion request, the device management module 108 sends a trust ring deregistration request 1 to the trust ring device cloud 4002, wherein the trust ring deregistration request 1 carries the cloud account B and the device information of the large screen device 200.

[0590] S615. Trust Ring Device Cloud 4002 unbinds the cloud account B from the device information of the large screen device 200.

[0591] S616. The Trust Ring Device Cloud 4002 returns a successful registration result to the Device Management Module 108.

[0592] S617. In response to the successful registration result of the trust ring, the device management module 108 returns the successful deletion result of the trust ring to the smart space service 103 through the remote vision service 104.

[0593] S618. If the electronic device 100 does not support the air vision function, the air vision service 103 returns a capability detection result 2 to the smart space service 101, wherein the capability detection result 2 is used to indicate that the large screen device 200 does not support the air vision function.

[0594] S619. If the large screen device 200 does not support the air vision function, or if the smart space service 103 receives a successful deletion result of the trust ring device, or if the smart space service 103 receives capability detection result 2, the smart space service 103 can delete the control card of the large screen device 200.

[0595] For example, the Smart Space Service 103 can prevent the control card of the large screen device 200 from being displayed on the main interface of the Smart Space application.

[0596] In one example, the smart space application can be referred to as the second application, and the main interface of the smart space application can be referred to as the first interface.

[0597] The process provided in this application, which allows an electronic device to actively delete a large-screen device after it has been added, enables the electronic device 100 to, upon receiving input from a user in the smart space application to delete the added large-screen device 200, unbind the device information of the large-screen device 200 from cloud account A on the IoT device cloud and unbind the device information of the large-screen device 200 from cloud account B on the trust ring device cloud. This ensures the security of using the large-screen device 200.

[0598] The following details the process of passively deleting the large-screen device 200 after adding it to the electronic device 100.

[0599] Figure 19 This describes the process of passively deleting a large-screen device after it has been added in the device control method provided in this application embodiment.

[0600] After the device information of large-screen device 200 is unbound from cloud account A, the IoT device cloud of cloud server 400 will update the IoT device list corresponding to cloud account A. The IoT device cloud can then send the updated IoT device list to devices logged into cloud account A. When electronic device 100 compares the IoT device list of cloud account A with the trust ring device list of cloud account B and determines that the device information of large-screen device 200 has been unbound from cloud account A, it indicates that the binding relationship between cloud account A and large-screen device 200 has been severed. Therefore, electronic device 100 cannot display the control card of large-screen device 200. Users can no longer control large-screen device 200 through electronic device 100. Therefore, even if large-screen device 200 and electronic device 100 are in the same trust ring, electronic device 100 and large-screen device 200 cannot perform normal interconnection. Therefore, after determining that the device information of large-screen device 200 has been unbound from cloud account A, electronic device 100 can trigger the unbinding of the device information of large-screen device 200 from cloud account B on the trust ring device cloud. This ensures that the device information of the large-screen device 200 can be deleted from both the IoT device cloud and the trust ring device cloud, thereby guaranteeing the security of using the large-screen device 200.

[0601] like Figure 19 As shown, the process of passively deleting a large-screen device after it has been added is applied to a communication system including electronic device 100, cloud server 400, and electronic device 500. Electronic device 100 may include smart space service 103, interconnection middleware 106, and device management module 108. Cloud server 400 may include IoT device cloud 4001 and trust ring device cloud 4002.

[0602] In this application, both electronic devices 500 and 100 are logged into cloud account A in the smart space application. Both electronic devices 500 and 100 use cloud account B for their smart interconnection services, meaning they are both within the trust ring of cloud account B. However, electronic device 500 does not support the gesture control feature, and therefore cannot bind or unbind cloud account B from the device information of the large-screen device 200 on the trust ring device cloud 4002. Therefore, when deleting the large-screen device 200, electronic device 500 can unbind the device information of the large-screen device 200 from cloud account A on IoT device cloud 4001, but cannot unbind the device information of the large-screen device 200 from cloud account B on trust ring device cloud 4003. However, electronic device 100 supports the gesture control feature, and can bind or unbind cloud account B from the device information of the large-screen device 200 on trust ring device cloud 4002. Therefore, when electronic device 100 discovers that cloud account A on IoT device cloud 4001 has been unbound from the device information of large screen device 200, but cloud account B has not been unbound, it can unbind the device information of large screen device 200 from cloud account B on trust ring device cloud 4002. This ensures that the device information of large screen device 200 can be deleted from both the IoT device cloud and trust ring device cloud, thereby guaranteeing the security of using large screen device 200.

[0603] In one possible implementation, cloud account A and cloud account B can be the same or different.

[0604] The process of passively removing a large-screen device after it has been added to an electronic device may include the following steps:

[0605] S701. Electronic device 500 sends IoT deregistration request 2 to IoT device cloud 4001, wherein IoT deregistration request 2 carries cloud account A and device information of large screen device 200.

[0606] S702.IoT Device Cloud 4001 unbinds the cloud account A from the device information of the large screen device 200.

[0607] After unbinding the device information of cloud account A from the large screen device 200, S703.IoT Device Cloud 4001 returns the IoT device list corresponding to cloud account A to smart space service 103 through interconnection middleware 106. The IoT device list corresponding to cloud account A does not include the device information of large screen device 200.

[0608] The IoT device list for cloud account A stores device information bound to cloud account A. Since IoT device cloud 4001 unbound the device information of large-screen device 200 from cloud account A, IoT device cloud 4001 deleted the device information of large-screen device 200 from the IoT device list of cloud account A.

[0609] S704. Smart Space Service 103 determines that the IoT device list of cloud account A does not include the device information of large screen device 200, and deletes the control card of large screen device 200.

[0610] For example, the Smart Space Service 103 can prevent the control card of the large screen device 200 from being displayed on the main interface of the Smart Space application.

[0611] S705. Device management module 108 satisfies the refresh conditions of the trust ring device list.

[0612] For example, the refresh conditions for the trust ring device list can include reaching a refresh time point, where the refresh time point can be periodic, for example, every hour. Therefore, the device management module 108 can obtain the trust ring device list of cloud account B from the trust ring device cloud 4002 once every hour.

[0613] S706. In response to the refresh conditions of the trust ring device list, the device management module 108 sends a trust ring refresh request to the trust ring device cloud 4002, wherein the trust ring refresh request carries the cloud account B.

[0614] S707. In response to the trust ring refresh request, the trust ring device cloud 4002 returns the list of trust ring devices for cloud account B to the device management module 108.

[0615] S708. Device management module 108 sends an IoT device query request to interconnect middleware 106.

[0616] S709. Interconnect middleware 106 returns a list of IoT devices for cloud account A to device management module 108.

[0617] S710. Device Management Module 108 determines, based on the IoT device list of Cloud Account A and the trust ring device list of Cloud Account B, that the trust ring device list of Cloud Account B contains device information for large screen device 200, but the IoT device list does not contain device information for large screen device 200.

[0618] S711. Device management module 108 sends Trust Ring Device Deregistration Request 2 to Trust Ring Device Cloud 4002, wherein Trust Ring Device Deregistration Request 2 carries cloud account B and device information of large screen device 200.

[0619] S712. In response to the trust ring device deregistration request 2, the trust ring device cloud 4002 unbinds the cloud account B from the device information of the large screen device 200.

[0620] S713. Trust Ring Device Cloud 4002 returns a successful registration result to Device Management Module 108.

[0621] The process provided in this application embodiment, which passively removes a large-screen device after it has been added, allows electronic devices 100 logged into cloud account A in the smart space application to determine that the device information of large-screen device 200 has been unbound from cloud account A after the device information of large-screen device 200 is unbound from cloud account A. This triggers the unbinding of the device information of large-screen device 200 from cloud account B on the trust ring device cloud. This ensures that the device information of large-screen device 200 can be deleted from both the IoT device cloud and the trust ring device cloud, thus guaranteeing the security of using large-screen device 200.

[0622] The hardware structure of an electronic device provided in the embodiments of this application is described below.

[0623] Figure 20 This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application.

[0624] It should be understood that, Figure 20 The electronic device 100 shown is merely an example, and the electronic device 100 may have more than Figure 20 The more or fewer components shown can be combined into two or more components, or they can have different component configurations. Figure 20 The various components shown can be implemented in hardware, software, or a combination of hardware and software, including one or more signal processing and / or application-specific integrated circuits.

[0625] Electronic device 100 may include: processor 1100, antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, audio module 170, speaker 170A, receiver 170B, microphone 170C, headphone jack 170D, sensor module 180, camera 193, and display screen 194. The sensor module 180 may include a touch sensor 180K, etc.

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

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

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

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

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

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

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

[0633] The modem processor may include a modulator and a demodulator. The modulator modulates the low-frequency baseband signal to be transmitted into a mid-to-high frequency signal. The demodulator demodulates the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. After processing by the baseband processor, the low-frequency baseband signal is transmitted to the application processor. The application processor outputs sound signals through audio devices (not limited to speaker 170A, receiver 170B, etc.) or displays images or videos through the display screen 194. In some embodiments, the modem processor may be a separate device. In other embodiments, the modem processor may be independent of the processor 1100 and may be housed in the same device as the mobile communication module 150 or other functional modules.

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

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

[0636] Electronic device 100 can perform shooting functions through an ISP, camera 193, video codec, GPU, display 194, and application processor. The ISP is used to process data fed back by the camera 193. The camera 193 is used to capture still images or videos.

[0637] Electronic device 100 can implement audio functions through an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, a headphone jack 170D, and an application processor. The audio module 170 is used to convert digital audio information into analog audio signals for output, and also to convert analog audio input into digital audio signals. The speaker 170A, also called a "loudspeaker," is used to convert audio electrical signals into sound signals. The receiver 170B, also called a "handpiece," is used to convert audio electrical signals into sound signals. When electronic device 100 answers a phone call or voice message, the receiver 170B can be brought close to the user's ear to hear the voice. The microphone 170C, also called a "microphone" or "voice transducer," is used to convert sound signals into electrical signals. The headphone jack 170D is used to connect wired headphones. The touch sensor 180K is used to detect touch operations applied to or near it. The touch sensor can transmit the detected touch operation to the application processor to determine the type of touch event. Visual output related to the touch operation can be provided through the display screen 194. In other embodiments, the touch sensor 180K may also be located on the surface of the electronic device 100, in a different position than the display screen 194.

[0638] It should be noted that the above Figure 20 The structures of electronic devices 300 and 500 in the illustrated embodiments can both refer to the above description. Figure 20 The electronic device 100 shown will not be described in detail here.

[0639] The hardware structure of the large-screen device 200 provided in the embodiments of this application is described below.

[0640] Figure 21 This is a schematic diagram of the hardware structure of a large-screen device provided in the embodiments of this application.

[0641] like Figure 21 As shown, the large-screen device 200 may include: a processor 211, a memory 212, a wireless communication module 213, a power switch 214, and a display screen 215. Optionally, the large-screen device 200 may also include an audio module 216 and a speaker 217.

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

[0643] The controller can serve as the central nervous system and command center of the large-screen device 200. The controller can generate operation control signals based on instruction operation codes and timing signals to control the fetching and execution of instructions.

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

[0645] In some embodiments, the processor 211 can be used to parse the signals received by the wireless communication module 213 and demodulate the signals. The processor 211 can respond according to the parsing results and perform corresponding operations, such as performing sensing operations. In some embodiments, the processor 211 can also be used to generate signals to be transmitted outward by the wireless communication module 213, such as Wi-Fi signals, Bluetooth signals, etc.

[0646] Memory 212 is coupled to processor 211 and is used to store various software programs and / or multiple sets of instructions. In specific implementations, memory 212 may include high-speed random access memory and may also include non-volatile memory, such as one or more disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory 212 may store an operating system, such as uCOS, VxWorks, RTLinux, or other embedded operating systems. Memory 212 may also store communication programs that can be used to communicate with devices such as electronic device 100, electronic device 300, or routing devices in a local area network, or other devices.

[0647] The wireless communication module 213 may include a Wi-Fi module. The Wi-Fi module can provide a Wi-Fi wireless communication solution for use on the large-screen device 200. The Wi-Fi protocol used in the Wi-Fi module may be IEEE 802.11a, 802.11b, 802.11n, 802.11ac, 802.11ax, etc.

[0648] Possibly, the wireless communication module 213 may also include other communication modules to provide solutions for other wireless communications (e.g., Bluetooth, GNSS, FM, NFC, IR).

[0649] It is possible that the Wi-Fi module can be integrated with other communication modules (such as Bluetooth communication modules). The Wi-Fi module can listen to signals emitted by other devices, such as measurement signals, scanning signals, etc., and can send response signals, such as measurement responses, scanning responses, etc., so that other devices can discover the large screen device 200 and establish wireless communication connections with other devices through one or more of WLAN, Bluetooth, or other short-range wireless communication technologies for data transmission.

[0650] In other embodiments, one or more of the Wi-Fi modules may also transmit signals, such as broadcast detection signals or beacon signals, enabling other devices to discover the large-screen device 200 and establish wireless communication connections with other devices via WLAN or other short-range wireless communication technologies for data transmission.

[0651] The power switch 214 can be used to turn the large screen device 200 on or off.

[0652] Display screen 215 is used to display images, videos, etc. The display screen includes a display panel. In some embodiments, the large-screen device 200 may include one or N displays, where N is a positive integer greater than 1.

[0653] Audio module 216. The audio module is used to convert digital audio information into analog audio signal output, and also to convert analog audio input into digital audio signal. The audio module can also be used for encoding and decoding audio signals.

[0654] The loudspeaker 217, also known as a "horn", is used to convert audio electrical signals into sound signals.

[0655] In some embodiments, the hardware structure of the large-screen device 200 may further include a microphone. Figure 21 (Not shown in the image). A microphone, also called a "voice transducer" or "microphone," is used to convert sound signals into electrical signals. When making a phone call or sending a voice message, the user can speak by bringing their mouth close to the microphone, inputting the sound signal into the microphone. The printer 200 can be equipped with at least one microphone.

[0656] It should be noted that, Figure 21 The large screen device 200 shown is merely one implementation of the embodiment of this application. In actual applications, the large screen device 200 may include more or fewer components, which is not limited here.

[0657] The hardware structure of the cloud server 400 provided in this application embodiment is described below.

[0658] Figure 22 This is a schematic diagram of the hardware structure of a cloud server provided in an embodiment of this application.

[0659] like Figure 22 As shown, the cloud server 400 includes one or more processors 4011, a communication interface 4012, and a memory 4013. The processors 4011, communication interface 4012, and memory 4013 can be connected via a bus or other means; this embodiment uses a connection via bus 4014 as an example. Wherein:

[0660] Processor 4011 may consist of one or more general-purpose processors, such as a CPU. Processor 4011 can be used to run the relevant program code for device control methods.

[0661] The communication interface 4012 can be a wired interface (e.g., an Ethernet interface) or a wireless interface (e.g., a cellular network interface or a wireless LAN interface) for communicating with other nodes. In this embodiment, the communication interface 4012 can specifically be used to communicate with devices such as electronic device 100, electronic device 300, and electronic device 500.

[0662] Memory 4013 may include volatile memory, such as RAM; memory may also include non-volatile memory, such as ROM, flash memory, HDD, or solid-state disk (SSD); memory 4013 may also include combinations of the above types of memory. Memory 4013 can be used to store a set of program code so that processor 4011 can call the program code stored in memory 4013 to implement the server implementation method of the embodiments of this application. In the embodiments of this application, memory 4013 may also be a storage array, etc.

[0663] In some embodiments, the cloud server 400 may include multiple servers, such as a device cloud server, a remote field cloud server, etc. The hardware structure of these multiple servers can refer to the above description. Figure 22 The hardware structure of the cloud server 400 is shown.

[0664] It needs to be explained that, Figure 22 The cloud server 400 shown is merely one implementation of this application embodiment. In practical applications, the cloud server 400 may include more or fewer components, which is not limited here. In one possible implementation, the IoT device cloud and the trust ring device cloud on the cloud server 400 may be two hardware-isolated cloud servers, or the IoT device cloud and the trust ring device cloud may be two functional units that share the hardware of the cloud server 400 but are software-functionally isolated.

[0665] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, can implement the steps in the above-described method embodiments.

[0666] This application also provides a computer program product, including a computer program that, when run on a processor, can implement the steps executed by the electronic device in the above-described method embodiments.

[0667] This application also provides a chip system, which includes a processing circuit interface circuit. The interface circuit receives instructions and transmits them to the processing circuit, which executes the instructions to cause the chip system to perform the steps executed by the electronic device in any of the method embodiments of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0668] The term "user interface (UI)" used in the specification and accompanying drawings of this application refers to the medium through which an application or operating system interacts and exchanges information with the user. It converts the internal form of information into a form acceptable to the user. The user interface of an application is source code written in a specific computer language such as Java or Extensible Markup Language (XML). This source code is parsed and rendered on the terminal device, ultimately presenting user-recognizable content, such as images, text, buttons, and other controls. Controls, also known as widgets, are the basic elements of the user interface. Typical controls include toolbars, menu bars, text boxes, buttons, scroll bars, images, and text. The attributes and content of controls in the interface are defined through tags or nodes, such as XML. <textview> 、 <imgview> 、 <videoview>Nodes define the controls contained in the interface. A node corresponds to a control or property in the interface, and after parsing and rendering, the node is presented as the content visible to the user. In addition, many applications, such as hybrid applications, often contain web pages within their interfaces. A web page, also known as a webpage, can be understood as a special control embedded in the application interface. Web pages are source code written in a specific computer language, such as Hypertext Markup Language (HTML), Cascading Style Sheets (CSS), JavaScript (JS), etc. Web page source code can be loaded and displayed as user-readable content by a browser or a web page display component with browser-like functionality. The specific content contained in a webpage is also defined through tags or nodes in the webpage source code; for example, HTML uses tags or nodes to define the content. 、 、 <video> 、 <canvas>Used to define the elements and attributes of a webpage.

[0669] The most common form of user interface is the graphical user interface (GUI), which refers to a user interface related to computer operation displayed graphically. It can be an icon, window, control, or other interface element displayed on the screen of an electronic device. Controls can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

[0670] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.

[0671] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.

[0672] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.< / canvas> < / video> < / videoview> < / imgview> < / textview>

Claims

1. A device control method, characterized in that, Applied to an electronic device, the electronic device being logged into a first cloud account and a second cloud account; the method includes: The electronic device receives a first broadcast packet sent by the large screen device. The large screen device is not logged into the first cloud account or the second cloud account. The first broadcast packet includes the device information of the large screen device, which includes the device name of the large screen device. In response to the received first broadcast packet, the electronic device displays a first discovery window, which includes the device name of the large screen device; After receiving the user's confirmation of connecting to the large screen device, the electronic device sends a registration request to the cloud server. The registration request carries the first cloud account, the second cloud account, and the device information of the large screen device. The registration request is used to request the cloud server to bind the device information of the large screen device with the first cloud account and the second cloud account. After receiving the registration success result sent by the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large screen device. The application information includes application icons and application identifiers. The electronic device receives an application launch request sent by the large screen device. The application launch request carries the application identifier of a first application, and the one or more applications include the first application. In response to receiving the application launch request, the electronic device sends first data to the large-screen device, the first data being used to instruct the large-screen device to display the interface of the first application.

2. The method according to claim 1, characterized in that, The registration request includes a first registration request and a second registration request. The first registration request carries the first cloud account and the device information of the large screen device. The first registration request is used to request the cloud server to bind the device information of the large screen device to the first cloud account. The second registration request carries the second cloud account and the device information of the large screen device. The second registration request is used to request the cloud server to bind the device information of the large screen device to the second cloud account. The registration success result includes a first registration success result and a second registration success result. The first registration success result indicates that the cloud server has successfully bound the device information of the large screen device to the first cloud account, and the second registration success result indicates that the cloud server has successfully bound the device information of the large screen device to the second cloud account.

3. The method according to claim 2, characterized in that, Sending a registration request to the cloud server includes: The electronic device sends the first registration request to the cloud server; The electronic device sends the second registration request to the cloud server.

4. The method according to claim 2 or 3, characterized in that, The electronic device receives a registration success message from the cloud server, including: The electronic device receives the first registration success result sent by the cloud server; The electronic device receives a second registration success result sent by the cloud server.

5. The method according to claim 3 or 4, characterized in that, The electronic device sends the second registration request to the cloud server, including: After receiving the first registration success result sent by the cloud server, the electronic device sends the second registration request to the cloud server. After receiving the registration success result from the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large-screen device, including: After receiving the second registration success result sent by the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large-screen device.

6. The method according to claim 5, characterized in that, Before the electronic device sends the first registration request to the cloud server, the method further includes: The electronic device sends a first connection code request to the large screen device. The first connection code request is used to request the large screen device to display a first connection code page. The first connection code page includes the first connection code. The electronic device receives a first page display result sent by the large screen device. The first page display result is used to indicate that the large screen device has successfully displayed the first connection code page. In response to the result displayed on the first page, the electronic device displays a first connection code input window; The second connection code entered by the user of the electronic device in the first connection code input window; The electronic device sends a first authentication request to the large screen device. The first authentication request carries the second connection code. The first authentication request is used to request the large screen device to perform a first authentication on the electronic device based on the first connection code and the second connection code. The electronic device sends the first registration request to the cloud server, including: After receiving the first authentication success result sent by the large-screen device, the electronic device sends the first registration request to the cloud server. The first authentication success result is used to indicate that the large-screen device has successfully completed the first authentication of the electronic device.

7. The method according to claim 5 or 6, characterized in that, After receiving the first registration success result sent by the cloud server, the electronic device sends a second registration request to the cloud server, including: After receiving the first registration success result sent by the cloud server, the electronic device sends a second authentication request to the large screen device. The second authentication request carries the second connection code and is used to request the large screen device to perform a second authentication on the electronic device based on the first connection code and the second connection code. After receiving the second authentication success result sent by the large-screen device, the electronic device sends the second registration request to the cloud server. The second authentication success result is used to indicate that the large-screen device has successfully completed the second authentication of the electronic device.

8. The method according to claim 7, characterized in that, After receiving the first registration success result sent by the cloud server, the electronic device sends a second authentication request to the large-screen device, including: After receiving the first registration success result sent by the cloud server, the electronic device sends an acquisition request to the large screen device. The acquisition request is used to request a registration file in a specified format, and the registration file includes the device information of the large screen device. After receiving the registration file sent by the large-screen device, the electronic device sends the second authentication request to the large-screen device; wherein the second registration request carries the registration file.

9. The method according to any one of claims 5-8, characterized in that, The method further includes: After receiving the second registration success result sent by the cloud server, the electronic device displays the first interface of the second application. The first interface of the second application includes the control card of the large screen device, which includes the device name and icon of the large screen device. The first cloud account is the account logged in to the second application.

10. The method according to any one of claims 1-9, characterized in that, The first broadcast packet also includes a first service identifier and a first service identifier. The first service identifier is the service identifier of the manufacturer of the electronic device, and the first service identifier is used to indicate that the first broadcast packet is used to display a discovery pop-up.

11. The method according to claim 9, characterized in that, The method further includes: The electronic device receives a second operation from the user on the control card, the second operation being used to delete the large-screen device; In response to the second operation, the electronic device sends a first deregistration request to the cloud server. The first deregistration request carries the first cloud account and the device information of the large screen device. The first deregistration request is used to request the cloud server to unbind the device information of the large screen device from the first cloud account. After receiving the first deregistration success result sent by the cloud server, the electronic device sends a second deregistration request to the cloud server. The first deregistration success result is used to indicate that the cloud server has successfully unbound the device information of the large screen device from the first cloud account, and the second deregistration request is used to request the cloud server to unbind the device information of the large screen device from the second cloud account. After the electronic device receives the second deregistration success result sent by the cloud server, if the first interface is displayed, the first interface does not include the control card. The second deregistration success result is used to indicate that the cloud server has successfully unbound the device information of the large screen device from the second cloud account.

12. The method according to any one of claims 1-11, characterized in that, The first data includes an image stream and an audio stream; In response to the received application launch request, the electronic device sends first data to the large-screen device, including: In response to the received application launch request, the electronic device launches the source-side screen mirroring service and the source-side audio virtual service, and creates a virtual display screen; After creating the virtual display screen, the electronic device launches the first application, wherein the first application, after being launched, sends an image stream to the virtual display screen and an audio stream to the source audio frame of the electronic device. The electronic device obtains the image stream from the virtual display screen through the source-end projection service and sends the image stream to the large-screen device; The electronic device obtains the audio stream from the source audio framework through the source audio virtual service and sends the audio stream to the large screen device.

13. The method according to any one of claims 1-12, characterized in that, In response to the received first broadcast packet, the electronic device displays a first discovery window, including: In response to the received first broadcast packet, if the signal strength of the first broadcast packet is greater than a first strength threshold and the electronic device does not display a second discovery window, the electronic device displays the first discovery window, wherein the second discovery window is different from the first discovery window.

14. The method according to any one of claims 1-13, characterized in that, Before sending the registration request to the cloud server, the method further includes: After receiving the user's first confirmation of connecting to the large screen device, the electronic device scans for the large screen device within the local area network to which the electronic device is connected. Sending the registration request to the cloud server includes: After the electronic device scans the large-screen device within the local area network, it sends the registration request to the cloud server.

15. The method according to claim 14, characterized in that, Before scanning the large-screen device within the local area network to which the electronic device is connected, the method further includes: After receiving the first operation, if the electronic device supports projecting the interface of the application installed on the electronic device onto the large screen device, a first privacy window is displayed. The first privacy window is used to prompt the user to agree to the first privacy policy. The electronic device receives a third action from the user agreeing to the first privacy policy; The step of scanning the large-screen device within the local area network to which the electronic device is connected includes: In response to the third operation, the electronic device scans the large-screen device within the local area network.

16. The method according to any one of claims 1-15, characterized in that, The first discovery window also includes a connection control, and the first operation is an operation performed on the connection control.

17. The method according to any one of claims 1-16, characterized in that, The first cloud account may be the same as or different from the second cloud account.

18. A communication system, characterized in that, This includes electronic devices and large-screen devices; wherein, the electronic devices are logged into a first cloud account and a second cloud account, while the large-screen devices are not logged into either the first cloud account or the second cloud account; The large-screen device sends a first broadcast packet to the electronic device. The first broadcast packet includes the device information of the large-screen device, which includes the device name of the large-screen device. In response to the received first broadcast packet, the electronic device displays a first discovery window, which includes the device name of the large screen device. After receiving the user's confirmation of connecting to the large screen device, the electronic device sends a registration request to the cloud server. The registration request carries the first cloud account, the second cloud account, and the device information of the large screen device. The registration request is used to request the cloud server to bind the device information of the large screen device with the first cloud account and the second cloud account. After receiving the registration success result sent by the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large screen device. The application information includes application icons and application identifiers. After receiving the application information from one or more applications, the large-screen device displays the application information from one or more applications, including the first application. The large-screen device receives a fourth operation from the user selecting the first application; In response to the fourth operation, the large-screen device sends an application launch request to the electronic device, the application launch request carrying the application identifier of the first application; In response to receiving the application launch request, the electronic device sends first data to the large-screen device, the first data being used to instruct the large-screen device to display the interface of the first application.

19. The communication system according to claim 18, characterized in that, The registration request includes a first registration request and a second registration request. The first registration request carries the first cloud account and the device information of the large screen device. The first registration request is used to request the cloud server to bind the device information of the large screen device to the first cloud account. The second registration request carries the second cloud account and the device information of the large screen device. The second registration request is used to request the cloud server to bind the device information of the large screen device to the second cloud account. The registration success result includes a first registration success result and a second registration success result. The first registration success result indicates that the cloud server has successfully bound the device information of the large screen device to the first cloud account, and the second registration success result indicates that the cloud server has successfully bound the device information of the large screen device to the second cloud account.

20. The communication system according to claim 19, characterized in that, Sending a registration request to the cloud server includes: The electronic device sends the first registration request to the cloud server; The electronic device sends the second registration request to the cloud server.

21. The communication system according to claim 19 or 20, characterized in that, The electronic device receives a registration success message from the cloud server, including: The electronic device receives the first registration success result sent by the cloud server; The electronic device receives a second registration success result sent by the cloud server.

22. The communication system according to claim 20 or 21, characterized in that, The electronic device sends the second registration request to the cloud server, including: After receiving the first registration success result sent by the cloud server, the electronic device sends the second registration request to the cloud server. After receiving the registration success result from the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large-screen device, including: After receiving the second registration success result sent by the cloud server, the electronic device sends application information of one or more applications installed on the electronic device to the large-screen device.

23. The communication system according to claim 22, characterized in that, Before the electronic device sends the first registration request to the cloud server, the electronic device sends a first connection code request to the large screen device. The first connection code request is used to request the large screen device to display a first connection code page, and the first connection code page includes a first connection code. The electronic device receives a first page display result sent by the large screen device. The first page display result is used to indicate that the large screen device has successfully displayed the first connection code page. In response to the result displayed on the first page, the electronic device displays a first connection code input window; The second connection code entered by the user of the electronic device in the first connection code input window; The electronic device sends a first authentication request to the large screen device. The first authentication request carries the second connection code. The first authentication request is used to request the large screen device to perform a first authentication on the electronic device based on the first connection code and the second connection code. The electronic device sends the first registration request to the cloud server, including: After receiving the first authentication success result sent by the large-screen device, the electronic device sends the first registration request to the cloud server. The first authentication success result is used to indicate that the large-screen device has successfully completed the first authentication of the electronic device.

24. The communication system according to claim 22 or 23, characterized in that, After receiving the first registration success result sent by the cloud server, the electronic device sends a second registration request to the cloud server, including: After receiving the first registration success result sent by the cloud server, the electronic device sends a second authentication request to the large screen device. The second authentication request carries the second connection code and is used to request the large screen device to perform a second authentication on the electronic device based on the first connection code and the second connection code. After receiving the second authentication success result sent by the large-screen device, the electronic device sends the second registration request to the cloud server. The second authentication success result is used to indicate that the large-screen device has successfully completed the second authentication of the electronic device.

25. The communication system according to any one of claims 22-24, characterized in that, After receiving the second registration success result sent by the cloud server, the electronic device displays the first interface of the second application. The first interface of the second application includes the control card of the large screen device, which includes the device name and icon of the large screen device. The first cloud account is the account logged in to the second application.

26. The communication system according to any one of claims 18-25, characterized in that, The first data includes an image stream and an audio stream; In response to the received application launch request, the electronic device sends first data to the large-screen device, including: In response to the received application launch request, the electronic device launches the source-side screen mirroring service and the source-side audio virtual service, and creates a virtual display screen; After creating the virtual display screen, the electronic device launches the first application, wherein the first application, after being launched, sends an image stream to the virtual display screen and an audio stream to the source audio frame of the electronic device. The electronic device obtains the image stream from the virtual display screen through the source-end projection service and sends the image stream to the large-screen device; The electronic device obtains the audio stream from the source audio framework through the source audio virtual service and sends the audio stream to the large screen device.

27. An electronic device, characterized in that, It includes one or more processors and one or more memories; wherein the one or more memories are coupled to the one or more processors, and the one or more memories are used to store a computer program that, when executed by the one or more processors, causes the electronic device to perform the device control method as described in any one of claims 1-17.

28. A computer-readable storage medium comprising instructions, characterized in that, When the instructions are executed on the processor of the first electronic device, the first electronic device causes the first electronic device to perform the device control method as described in any one of claims 1-17.

29. A computer program product, characterized in that, It includes a computer program that, when executed by a processor, implements the device control method as described in any one of claims 1-17.

Images