A device management method, communication system and related devices

Abstract

The application provides a device management method, a communication system and related devices. When a first electronic device logs in a cloud account and a second electronic device does not log in the cloud account, the first electronic device can bind device information of the second electronic device to the cloud account logged in the first electronic device through negotiation with a cloud server after the second electronic device is connected to a local area where the first electronic device is located. In this way, the first electronic device can manage other devices that do not log in the cloud account logged in the first electronic device.

Description

Technical Field

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

[0002] Currently, when users want to control a target device to perform related tasks through electronic devices, they need to first download a third-party application developed by the target device manufacturer, then open the third-party application, add and configure the target device within the application, and subsequently control the target device only through the same third-party application. This process of adding and using a target device on an electronic device is cumbersome, makes managing the target device difficult, and impacts the efficiency of using the target device. Summary of the Invention

[0003] This application provides a device management method, communication system, and related apparatus, which can facilitate the management of other devices that are not logged into the cloud account logged in on the first electronic device by a first electronic device.

[0004] In a first aspect, this application provides a device management method applied to a first electronic device, which has a cloud account logged in. The method includes: the first electronic device connecting to a first local area network (LAN) and saving the network name and password of the LAN; the first electronic device receiving a first message from a second electronic device, wherein the second electronic device is not logged into the cloud account, the first message including device information and a network configuration status identifier of the second electronic device, the network configuration status identifier indicating that the second electronic device has not stored the network configuration information of the LAN; in response to receiving the first message, the first electronic device sending first network configuration information to the second electronic device, wherein the first network configuration information includes the network name and password of the first LAN, the first network configuration information indicating that the second electronic device is connected to the first LAN; after the first electronic device finds the second electronic device through the first LAN, it sends a proxy registration request to a cloud server, the proxy registration request carrying the device information of the second electronic device and the cloud account, the proxy registration request being used to request the cloud server to bind the device information of the second electronic device to the cloud account.

[0005] The device management method provided in this application allows for the following scenario: when a first electronic device is logged into a cloud account, but a second electronic device is not, the first electronic device can, after configuring the second electronic device to connect to the local area network where the first electronic device is located, negotiate with the cloud server to bind the device information of the second electronic device to the cloud account logged in on the first electronic device. This facilitates the first electronic device's management of other devices that are not logged into the same cloud account as the first electronic device.

[0006] The cloud server can store a list of devices corresponding to the cloud account, which records device information for all devices logged in or bound to the cloud account. The cloud server can manage and update the status information of all devices in the device list corresponding to the cloud account, and can synchronize the status information of all devices in the device list to devices logged in with the cloud account. In this way, devices logged in with the cloud account can view the status of the second electronic device or access the second electronic device.

[0007] In one possible implementation, the method further includes: the first electronic device receiving a binding success response sent by the cloud server, the binding success response indicating that the cloud server has successfully bound the device information of the second electronic device to the cloud account; after receiving the binding success response sent by the cloud server, the first electronic device receiving a first operation from the user to open a first interface; in response to the first operation, the first electronic device displays the first interface and displays options for multiple devices on the first interface, the multiple devices logging in or binding to the cloud account, the multiple devices including the first electronic device and the second electronic device.

[0008] In this way, users can quickly view or call up the second electronic device from the first interface displayed on the first electronic device (e.g., the smart interconnection interface of the control center).

[0009] In one possible implementation, the response to the first operation to display the first interface includes: in response to the first operation, obtaining the status information of the second electronic device; if the status information of the second electronic device is online, the first electronic device displays the first interface and displays the options of the second electronic device in the first interface.

[0010] In one possible implementation, after the first electronic device finds the second electronic device through the first local area network, it sends a proxy registration request to the cloud server, including: after the first electronic device finds the second electronic device through the first local area network, it determines, based on the device information of the second electronic device, whether the second electronic device is in the binding whitelist and is not bound to the cloud account, the binding whitelist including one or more devices that are allowed to be bound to the cloud account logged in on the first electronic device; if the second electronic device is in the binding whitelist and is not bound to the cloud account, it sends a proxy registration request to the cloud server.

[0011] This allows the device information of the second electronic device to be bound to the cloud account even when the second electronic device is not logged into or bound to the cloud account, but the second electronic device has the permission to bind the cloud account, thereby improving the security of devices logged into or bound under the cloud account.

[0012] In one possible implementation, after the first electronic device receives the binding success response sent by the cloud server, the method further includes: the first electronic device detecting that the second electronic device is online through the first local area network; and the first electronic device sending the online status of the second electronic device and the device information of the second electronic device to a third electronic device logged into the cloud account through the cloud server.

[0013] In this way, after the first electronic device binds the device information of the second electronic device to the cloud account, it can synchronize the status information of the second electronic device with other devices logged in with the cloud account, so that other devices logged in with the cloud account can view the status of the second electronic device or access the second electronic device.

[0014] In one possible implementation, after the first electronic device sends the agent registration request to the cloud server, the method further includes: the first electronic device receiving a second operation from the user to unbind the second electronic device from the cloud account; in response to the second operation, the first electronic device sends an unbinding notification to the cloud server, the unbinding notification carrying the device information of the second electronic device and the cloud account, the unbinding notification being used to notify the cloud server to unbind the device information of the second electronic device from the cloud account.

[0015] After the cloud server unbinds the device information of the second electronic device from the cloud account, it can delete the device information of the second electronic device from the device list corresponding to the cloud account. In this way, devices logged in with the cloud account will not be able to obtain the status information of the second electronic device through the cloud server.

[0016] In one possible implementation, after the first electronic device sends an unbinding notification to the cloud server, the method further includes: the first electronic device receiving an unbinding response from the cloud server, the unbinding response indicating that the cloud server has unbound the device information of the second electronic device from the cloud account; the first electronic device receiving a first operation from a user to open the first interface; in response to the first operation, displaying the first interface and showing options for one or more devices on the first interface, the one or more devices logging in or binding to the cloud account, wherein the one or more devices include the first electronic device but not the second electronic device.

[0017] In this way, after the device information of the second electronic device is unbound from the cloud account, the first electronic device will not display its options on the first interface.

[0018] In one possible implementation, the second electronic device is a printer; the method further includes: when the first electronic device displays the options of the second electronic device on the first interface, the first electronic device receives a third operation from the user regarding the options of the second electronic device; in response to the third operation, the first electronic device controls the second electronic device to perform a printing task.

[0019] In this way, after binding the printer's device information to the cloud account, the user can quickly call up the printer to perform printing tasks by opening the first interface of the first electronic device (for example, the smart interconnection interface of the control center).

[0020] In one possible implementation, the first electronic device controls the second electronic device to perform a printing task, specifically including: the first electronic device receiving a target file and target printing parameters selected by the user; in response to receiving the target file and target printing parameters selected by the user, the first electronic device sending the target printing parameters and the target file to the second electronic device through the first local area network, wherein the target file and target printing parameters are used to trigger the second electronic device to print the target file with the target printing parameters.

[0021] In one possible implementation, after the first electronic device controls the second electronic device to perform a printing task, the method further includes: the first electronic device sending configuration information to a third electronic device through the cloud server, the third electronic device being logged into the cloud account, the configuration information including a first parameter and a target printing parameter; wherein, the configuration information is used to instruct the third electronic device to set the initial printing parameter on the third electronic device to the target printing parameter, and the first parameter is used to grant the third electronic device permission to call the second electronic device to perform printing.

[0022] In this way, devices logged into the cloud account can share printer configuration information with each other, so that users do not have to manually set the printer parameters repeatedly when calling the printer on different devices.

[0023] In one possible implementation, the second electronic device is a printer. The first electronic device includes a control center, a shared service management framework, a print service framework, and a distributed print service. In response to the first operation, the first electronic device displays a first interface with multiple device options, including: in response to the first operation, the control center sends a call request to the shared service management framework, the call request being used to invoke the shared service management framework; the shared service management framework initializes one or more shared services, including the print shared service; after initialization, the print shared service registers a device discovery callback with the distributed print service; after registering the device discovery callback, the distributed print service, upon discovering the second electronic device, determines the second electronic device's status as online; the distributed print service sends device... A device discovery notification is sent to the print sharing service, the notification carrying the online status of the second electronic device. Upon receiving the notification, the print sharing service registers with the sharing service management framework and returns the printer's online status to the framework. After receiving the registration from the print sharing service, the sharing service management framework obtains the online status of the second electronic device. Upon obtaining the online status, the framework sends it to the control center. Upon receiving the online status, the control center displays the first interface, showing the options for both the first and second electronic devices.

[0024] In one possible implementation, the second electronic device is a printer; the first electronic device includes a printing assistant, an ecosystem access framework, and a device management service. The first electronic device sends a proxy registration request to the cloud server, including: the printing assistant sending a binding request to the device management service, the binding request carrying the device information of the second electronic device; in response to receiving the binding request, the device management service sending a proxy binding request to the ecosystem access framework, the proxy binding request carrying the printer's device information and the cloud account; and the ecosystem access framework, upon receiving the proxy binding request, sending the proxy registration request to the cloud server.

[0025] In a second aspect, this application provides an electronic device, which is a first 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 computer program code, the computer program code including computer instructions, which, when the one or more processors execute the computer instructions, cause the method in any possible implementation of the first aspect to be performed.

[0026] Thirdly, this application provides another electronic device, including one or more functional modules for performing the methods in any of the possible implementations of the first aspect above.

[0027] Fourthly, 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 method in any possible implementation of any of the above aspects.

[0028] Fifthly, this application provides a computer-readable storage medium including instructions that, when executed on a processor of a first electronic device, cause the first electronic device to perform the method in any of the possible implementations of the first aspect described above.

[0029] Sixthly, embodiments of this application provide a computer program product that, when run on a computer, causes the computer to execute the method in any of the possible implementations of any of the above aspects.

[0030] The beneficial effects of the second to sixth aspects can be referenced from the beneficial effects of the first aspect and any possible implementation of the first aspect. Attached Figure Description

[0031] Figure 1 This application provides a schematic diagram of the architecture of a communication system. Figures 2A-2S This is a set of schematic diagrams illustrating the interface for binding a printer to a designated cloud account in a smart space application, as provided in the embodiments of this application. Figures 3A-3C This document illustrates a set of interface diagrams provided in this application embodiment for binding printer device information to a designated cloud account in a smart space application. Figures 4A-4G This document illustrates a set of interface diagrams provided in this application embodiment, showing how to call the printer assistant in the settings application to bind the printer's device information to a specified cloud account; Figures 5A-5B This document illustrates a set of interface diagrams provided in an embodiment of this application, showing how to add device information for a printer in the control center and bind it to a specified cloud account. Figures 5C-5E This document illustrates a set of interface diagrams provided in an embodiment of this application, showing how to add device information for a printer in the control center and unbind it from a specified cloud account. Figure 6 This is a schematic diagram of the software architecture of an electronic device provided in an embodiment of this application; Figure 7 This is a flowchart illustrating a device management method provided in an embodiment of this application; Figure 8 This is a flowchart illustrating a device management method provided in another embodiment of this application; Figure 9 This is a schematic diagram of a process for going online on a control center display device, provided in an embodiment of this application. Figure 10 This is a schematic diagram of a process for going online on a control center display device, provided in another embodiment of this application; Figure 11 This is a schematic diagram illustrating a process for unbinding a device from a cloud account, as provided in an embodiment of this application. Figure 12 This is a flowchart illustrating a printer configuration synchronization process provided in an embodiment of this application; Figure 13 This is a flowchart illustrating a printer configuration synchronization process provided in another embodiment of this application; Figure 14A This is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of this application; Figure 14B This is a schematic diagram of the hardware structure of a printer provided in an embodiment of this application; Figure 14C This is a schematic diagram of the hardware structure of a cloud server 400 provided in an embodiment of this application. Detailed Implementation

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

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

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

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

[0036] like Figure 1 As shown, the communication system 10 may include electronic device 101, electronic device 102, printer 200, wireless access device 300 and cloud server 400.

[0037] Electronic device 101 can establish a connection with cloud server 400. Electronic device 102 can also establish a connection with cloud server 400. Therefore, electronic device 101 can communicate with electronic device 102 through cloud server 400.

[0038] Electronic device 101 can also establish a Wi-Fi connection with wireless access device 300. Printer 200 can also establish a Wi-Fi connection with wireless access device 300. Therefore, electronic device 101 can communicate with printer 200 through wireless access device 300.

[0039] Electronic device 101 and electronic device 102 can both be logged into the same designated cloud account, while printer 200 is not logged into that designated cloud account. Electronic devices 101 and 102 can access cloud server 400 through the logged-in cloud account.

[0040] It should be noted that the printer 200 in the above communication system 10 can also be replaced with other types of devices (such as speakers, cameras, etc.), which are not limited here.

[0041] In this embodiment of the application, electronic device 101 can be referred to as the first electronic device, printer 200 can be referred to as the second electronic device, and electronic device 102 can be referred to as the third electronic device.

[0042] The trust ring involved in the embodiments of this application is described below.

[0043] Multiple devices (e.g., electronic devices 101 and 102) can establish connections with cloud server 400 by logging into the same designated cloud account. These devices can then interact with each other through cloud server 400. This interaction between devices logged into the designated cloud account creates a mutually trusting system, which can be termed a trust ring.

[0044] Some devices do not support logging into cloud accounts. For example, printer 200 does not have an input device, so it cannot receive the cloud account and password manually entered by the user. Another example is printer 200, which is manufactured by a third-party vendor and is not from the same manufacturer as the several devices mentioned above that support logging into specific cloud accounts; therefore, printer 200 does not support logging into specific cloud accounts.

[0045] In this way, devices that are not logged into the designated cloud account (such as printer 200) will find it difficult to trust each other with the multiple devices that are logged into the designated cloud account, and thus will be unable to join the trust loop of the designated cloud account by logging into the designated cloud account.

[0046] Therefore, this application provides a device management method where a first electronic device (e.g., electronic device 101) is logged into a cloud account (e.g., a designated cloud account). A second electronic device (e.g., printer 200) is not logged into the same cloud account (e.g., no designated cloud account is logged in). After configuring the second electronic device to join the local area network where the first electronic device is located, the first electronic device can send the device information of the second electronic device along with the cloud account to a cloud server. The cloud server can then bind the device information of the second electronic device to the cloud account.

[0047] Because the device information of the second electronic device is bound to the cloud account, the first electronic device can synchronize the status and configuration information of the second electronic device with other devices logged into the cloud account through the cloud server. In this way, the second electronic device can trust the devices logged into the cloud account, that is, the second electronic device joins the trust loop of the cloud account.

[0048] In this embodiment of the application, devices within the same trust ring are logged into or bound to the same cloud account. For example, electronic device 101 and electronic device 102 are both logged into a specified cloud account, and printer 200 is bound to a specified cloud account.

[0049] The following is an exemplary description of the process by which a user binds the device information of a printer 200 to a designated cloud account in the smart space application on an electronic device 101 in this application embodiment.

[0050] Figures 2A-2S The illustration shows a set of interface diagrams for binding a printer to a designated cloud account in a smart space application, as provided in the embodiments of this application.

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

[0052] Electronic device 101 can receive user actions (such as clicking) on ​​the smart space application icon 312, and in response to the action, electronic device 101 can display as follows: Figure 2B The smart space application interface 320 is shown.

[0053] like Figure 2B As shown, the smart space application interface 320 can display add controls 323 and service cards for one or more devices (e.g., service card 321 for a TV and service card 322 for a speaker). The smart space application for electronic device 101 is logged into a designated cloud account.

[0054] Electronic device 101 can receive user actions (e.g., clicks) on the added control 323, and in response to the action, electronic device 101 can display, as shown below. Figure 2C The menu shown is 324.

[0055] like Figure 2C As shown, the menu 324 may include an add device control 325. The electronic device 101 can receive user actions (e.g., clicks) on the add device control 325, and in response to such actions, the electronic device 101 may display... Figure 2D The device addition interface 330 is shown.

[0056] like Figure 2D As shown, the device addition interface 330 can display devices that electronic device 101 has searched for via short-range communication technologies (e.g., Wi-Fi, Bluetooth, etc.). After electronic device 101 searches for printer 200 via short-range communication, it can display device options 331 and connection controls 332 on the device addition interface 330. Device options 331 display the device name of printer 200 (e.g., "Printer P1"). The connection control 332 can be used to trigger electronic device 101 to configure printer 200 to connect to the local area network where electronic device 101 is located.

[0057] Electronic device 101 can receive user operations on connection control 332 (e.g., click), and in response to the operation, electronic device 101 can send the network name and network password of the local area network to which electronic device 101 is connected to printer 200, thereby configuring printer 200 to use the network name and network password of the local area network to connect to the local area network to which electronic device 101 is connected.

[0058] like Figure 2E As shown, after the printer 200 is connected to the local area network to which the electronic device 101 is connected, the electronic device 101 can display the service card 326 of the printer 200 in the smart space application interface 320.

[0059] Optionally, after configuring printer 200 to use the local area network name and password to connect to the local area network to which electronic device 101 is connected, electronic device 101 can send the device information of printer 200 and the specified cloud account logged in on electronic device 101 to cloud server 400. After receiving the device information of printer 200 and the specified cloud account, cloud server 400 can bind the device information of printer 200 with the specified cloud account. In this way, printer 200 can be added to the trust ring of the specified cloud account.

[0060] Electronic device 101 can receive user input on the service card 326 (e.g., a click), and in response to the input, electronic device 101 can activate the printing assistant and display, as shown below. Figure 2F The printing assistant interface shown is 340.

[0061] like Figure 2F As shown, the printing assistant interface 340 may include a current printer settings bar 341 and one or more printing options. The current printer settings bar 341 displays device information (e.g., "Printer P1") and status information (e.g., "Idle"). The one or more printing options may include options for printing incorrect answers, restoring test papers, printing handwritten newspapers, origami, printing documents, printing images 342, scanning, printing large images, and printing regional data, etc.

[0062] Electronic device 101 can receive user input (e.g., a click) on the image printing option 342, and in response to this input, electronic device 101 can display, as shown below. Figure 2G The image selection interface shown is 350.

[0063] like Figure 2G As shown, the image selection interface 350 can display thumbnails (including thumbnails 351) of one or more images stored locally on the electronic device 101.

[0064] Electronic device 101 can receive user input (e.g., a click) on the thumbnail 351, and in response to the input, electronic device 101 can display the above-mentioned thumbnail. Figure 2H The printing interface shown is 360°.

[0065] like Figure 2HAs shown, the printing interface 360 ​​may include a print preview area 361, one or more print parameter setting options, and a start print control 367. The print preview area 361 can be used to display the printed effect of the image 362 corresponding to the thumbnail 351. The one or more print parameter setting options may include a print count setting option 363, a single / double-sided printing setting option 364, a paper size setting option 365, and a color printing setting option 366. The print count setting option 363 can be used to set the number of copies of the image 362 that the printer 200 will print. The single / double-sided printing setting option 364 can be used to set whether the image 362 is printed on one side or two sides. The paper size setting option 365 can be used to set the size of the image 362 printed by the printer 200. The color printing setting option 366 can be used to set whether the printer 200 prints the image 362 in color or in black and white. The start print control 367 can be used by the electronic device 101 to trigger the printer 200 to print the image 362 with the user-set print parameters.

[0066] The electronic device 101 can determine the target printing parameters of the image 362 based on the user's operation on the printing interface 360. The electronic device 101 can receive and respond to the user's operation on the start printing control 367, sending the image 362 and the user-set target printing parameters (e.g., 5 copies, single-sided printing, A4 paper size, black and white printing, etc.) to the printer 200. The electronic device 101 can control the printer 200 to print the image 362 according to the target printing parameters via a local area network.

[0067] like Figure 2I As shown, during the printing process of image 362 by printer 200 with target printing parameters, printer 200 can send the printing status to electronic device 101. Upon receiving the printing status, electronic device 101 can display printing interface 370, which may include a print preview area 371, a print status indicator 372, and a stop printing control 373. The print preview area 371 can be used to display the printing effect of image 362. The print status indicator 372 can be used to indicate the current printing status of the printer. For example, the print status indicator 372 could be "Printing copy 1 / (out of 5)". The stop printing control 373 can be used to trigger electronic device 101 to control printer 200 to stop printing the current print job via electronic device 102.

[0068] After the printer 200 finishes printing the image 362 with the target printing parameters, the printer 200 can send the printing completion information to the electronic device 101.

[0069] like Figure 2JAs shown, after receiving the print completion information, the electronic device 101 can display a print interface 380. This print interface 380 may include a print preview area 381, a print completion notification 382, ​​a completion control 383, and a continue printing control 384. The print preview area 381 can be used to display the print result of the aforementioned image 362. The print completion notification 382 can be used to indicate to the printer that the print job has been completed. The completion control 383 can be used to exit the print interface 380. The continue printing control 384 can be used to trigger the electronic device 101 to continue selecting files for printing by the printer 200.

[0070] Electronic device 101 can receive user actions (e.g., clicks) on completion control 383, and in response to such actions, electronic device 101 can display, as shown below. Figure 2K The binding pop-up window shown is 390.

[0071] like Figure 2K As shown, the binding pop-up window 390 may include the device name 391 of the printer 200 (e.g., PrinterP1), a binding prompt 392, a confirmation control 393, and a cancellation control 394. The binding prompt 392 can be used to prompt the user whether to bind the printer 200 to the specified cloud account. For example, the binding prompt 392 may be the text prompt "Bind the printer through Honor account trust authentication?". The confirmation control 393 can be used to trigger the electronic device 101 to request the cloud server 400 to bind the device information of the printer 200 to the specified cloud account. The cancellation control 394 can be used to trigger the electronic device 101 to cancel the request to the cloud server 400 to bind the device information of the printer 200 to the specified cloud account.

[0072] Electronic device 101 can receive user actions on confirmation control 393 (e.g., clicking). In response to this action, electronic device 101 can send the device information of printer 200 and a specified cloud account to the cloud server. The cloud server can then bind the device information of printer 200 to the specified cloud account, thereby adding printer 200 to the trust ring corresponding to the specified cloud account. Optionally, electronic device 101 can also add the device information of printer 200 to a locally stored list of bound devices.

[0073] In one possible implementation, electronic device 101 can receive and respond to a user's operation on completion control 383 (e.g., clicking) by sending the device information of printer 200 and a designated cloud account to cloud server 400. Upon receiving the device information and designated cloud account, cloud server 400 can bind the device information and designated cloud account. In this way, printer 200 can be added to the trust loop of the designated cloud account.

[0074] like Figure 2LAs shown, electronic device 101 can receive a swipe operation from the user at the top of the screen (e.g., swiping down from the top of the screen), and in response to this operation, electronic device 101 can display as shown in the image. Figure 2M The control center interface 410 is shown.

[0075] like Figure 2M As shown, the control center interface 410 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 411.

[0076] Electronic device 101 can receive user operations (such as clicking) on ​​the smart interconnected control card 411, and in response to the operation, electronic device 101 can display such as Figure 2N The smart interconnected interface 420 is shown.

[0077] like Figure 2N As shown, the smart interconnection interface 420 may include device options 421 for electronic device 101, an avatar 425 for a specified cloud account, and a delete control 424. After obtaining online information of other devices within the trust ring, electronic device 101 can display device options for other devices logged in or bound to a specified cloud account on the smart interconnection interface 420. Other devices logged in or bound to a specified cloud account may include electronic device 102 and printer 200. For example, after discovering that printer 200 is online, electronic device 101 can display device options 422 for printer 200 on the smart interconnection interface 420. Optionally, when electronic device 101 discovers that electronic device 102 is online through cloud server 400, it can display device options 423 for electronic device 102 on the smart interconnection interface 420. The delete control 424 can be used to trigger electronic device 101 to request cloud server 400 to unbind the device information of the user-selected device from the specified cloud account, thereby deleting the user-selected device from the trust ring of the specified cloud account.

[0078] like Figure 2O As shown, the electronic device 101 can receive a drag operation from the user to drag the device option 422 to the area where the device option 421 is located.

[0079] like Figure 2PAs shown, in response to a user dragging device option 422 to the area where device option 421 is located, electronic device 101 can return to the desktop 310 and display the print capsule 431 on the screen. The screen of electronic device 101 is a punch-hole screen, and the punch-hole typically houses a front-facing camera, which is located at the top of the screen. To fully utilize the display area, electronic device 101 displays the print capsule 431 around the punch-hole at the top of the screen. The punch-hole can be located in the center of the print capsule 431, while the non-center areas can display a print icon, print text, and the printer manufacturer, model (e.g., Printer P1), or device identification for printer 200, etc. Since the punch-hole area is black, the background color of the print capsule 431 can also be set to black, making it difficult for the user to spot the punch-hole. The print capsule 431 can float on top of other interfaces and can be used to call a print assistant to print documents currently displayed on the interface of electronic device 101. The files include any of the following: documents, images, videos, spreadsheets, PowerPoint presentations, etc.

[0080] Electronic device 101 can receive user actions (e.g., clicks) on the gallery application icon 313 on desktop 310, and in response to the user's actions, electronic device 101 can display, for example... Figure 2Q The image gallery application interface shown is 440.

[0081] like Figure 2Q As shown, the gallery application interface 440 may include thumbnails of one or more images, such as thumbnail 441. When displaying the gallery application 440, the electronic device 101 may also display the aforementioned printed capsule 431.

[0082] Electronic device 101 can receive user operations on thumbnail 441, and in response to such operations, electronic device 101 can display as follows: Figure 2R The image browsing interface shown is 450.

[0083] like Figure 2R As shown, when the electronic device 101 displays the image browsing interface 450, it can display the aforementioned printed capsule 431. The image browsing interface 450 may include the image 451. Optionally, the image browsing interface 450 may also include a menu 452, which may include share controls, favorite controls, edit controls, delete controls, and more controls.

[0084] Electronic device 101 can receive user actions on printing capsule 431 (e.g., click), and in response to such actions, such as Figure 2SAs shown, the electronic device 101 can switch the printing capsule 431 to a printing notification bar 432, which is displayed at the top of the screen.

[0085] like Figure 2S As shown, the print notification bar 432 may include the filename of the currently opened file and the print control 433. The currently opened file may be an image 451; therefore, the print notification bar 432 may display the filename of image 451, "IMG_2023 / 9 / 20_1.JPG".

[0086] Electronic device 101 can receive user actions (such as clicking) on ​​the printing control 433, and in response to the action, electronic device 101 can display as shown above. Figure 2H The printing interface shown is 360°. Subsequent printing procedures can be referenced above. Figures 2H to 2J The embodiments shown are not described in detail here.

[0087] In this embodiment, the aforementioned smart interconnection interface 420 can be referred to as the first interface, and the user's operation on the smart interconnection control card 411 can be referred to as the first operation. The aforementioned dragging operation of the device option 422 to the area where the device option 421 is located can be referred to as the third operation.

[0088] In one possible implementation, if the electronic device 101 does not receive any user operation on the printing capsule 431 after displaying the printing capsule 431 for a certain period of time (e.g., 10 seconds), then it exits the display of the printing capsule 431.

[0089] In one possible implementation, if the electronic device 101 receives a user's click on an area outside the print notification bar 432 after displaying the print notification bar 432, the electronic device 101 can switch the print notification bar 432 back to the print capsule 431 displayed at the top of the screen.

[0090] In some application scenarios, printer 200 can be a new printer that is not yet network-configured. When printer 200 is powered on or enters network configuration mode, it can send a broadcast message (which can be called the first message). This broadcast message includes printer 200's device information and network configuration status identifier. The network configuration status identifier indicates that printer 200 has not stored local area network (LAN) configuration information, meaning it is in an unconfigured state. Upon receiving the broadcast message from printer 200, electronic device 101 can obtain printer 200's device information from the broadcast message and display a discovery window. This discovery window prompts the user whether to connect printer 200 to the LAN where electronic device 101 is located. After receiving the user's instruction to connect printer 200 to the first LAN where electronic device 101 is located, electronic device 101 can obtain the network name and password of the first LAN stored locally on electronic device 101 through the smart space application. Electronic device 101 can then send the first network configuration information to printer 200 through the smart space application. This first network configuration information includes the network name and password of the first LAN. After receiving the first network configuration information, printer 200 can connect to the local area network (LAN) to which electronic device 101 is connected, using the LAN's network name and password. Once electronic device 101 detects printer 200 on the LAN, it indicates that printer 200 has successfully connected. At this point, electronic device 101 can request cloud server 400 to bind printer 200's device information to the specified cloud account logged into on electronic device 101. In this way, printer 200 is added to the specified cloud account's trust ring.

[0091] Figures 3A-3C This document illustrates a set of interface diagrams provided in this application embodiment for binding the device information of printer 200 to a designated cloud account in a smart space application.

[0092] For example, such as Figure 3A As shown, electronic device 101 can display desktop 310. Upon receiving a broadcast signal from printer 200, electronic device 101 can obtain device information of printer 200 from the broadcast signal and display a discovery window 460. The discovery window 460 includes an icon and name of printer 200 (e.g., Printer P1), a connection control 461, and a cancellation control 462. The connection control 461 can be used to trigger electronic device 101 to configure network for printer 200, and the cancellation control 462 can be used to trigger electronic device 101 to cancel network configuration for printer 200.

[0093] like Figure 3BAs shown, electronic device 101 can receive and respond to user operations on the connection control 461 (e.g., clicking), displaying the smart space application interface 320 and the network configuration pop-up window 470. The network configuration pop-up window 470 may include the printer 200's icon and name (e.g., Printer P1), network configuration prompt information 471, an allow control 472, and a manual input control. For example, the network configuration prompt information 471 may be "Do you want to synchronize the connected LAN (Wi-Fi name and password) to the printer (Printer P1) with one click for network configuration?" The allow control 472 can be used to trigger electronic device 101 to obtain the network name and password of the LAN connected to by electronic device 101 through the smart space application and send the network name and password to printer 200. The manual input control can be used to trigger electronic device 101 to receive the user-inputted LAN network name and password and send the user-inputted LAN network name and password to printer 200.

[0094] Electronic device 101 can receive and respond to user operations (e.g., clicks) on the aforementioned permitted control 472, obtain the network name and password of the local area network to which electronic device 101 is connected through the smart space application, and send the network name and password to printer 200. Printer 200 can then connect to the local area network to which electronic device 101 is connected based on the received network name and password.

[0095] like Figure 3C As shown, when electronic device 101 detects printer 200 on the local area network, it can display a successful network configuration pop-up window 480. This successful network configuration pop-up window can be used to notify the user that printer 200 has been successfully configured on the network. After successful network configuration, electronic device 101 can display printer 200's service card 326 in the smart space application interface 320. After successfully configuring printer 200 on the network, electronic device 101 can also request cloud server 400 to bind printer 200's device information to a specified cloud account. In this way, printer 200 is added to the trust ring of the specified cloud account.

[0096] In some application scenarios, printer 200 can be a new printer that is not yet network-configured. Electronic device 101 can launch the printing assistant through the settings application and search for and configure the printer in the printing assistant. When printer 200 is powered on or enters network configuration mode, printer 200 can send a broadcast message (which can be called the first message). The broadcast message includes the device information of printer 200 and the network configuration status identifier. The network configuration status identifier indicates that printer 200 has not stored the local area network configuration information, that is, it is in an unconfigured state. After receiving the broadcast message sent by printer 200, electronic device 101 can obtain the device information of printer 200 from the broadcast message and display that printer 200 is unconfigured in the printing assistant interface. When electronic device 101 receives the user's operation to configure printer 200, electronic device 101 can send the first network configuration information to printer 200 through the smart space application. The first network configuration information includes the network name and network password of the first local area network. After receiving the first network configuration information, printer 200 can connect to the first local area network (LAN) to which electronic device 101 is connected, using the LAN's network name and password. Once electronic device 101 detects printer 200 on the first LAN, it indicates that printer 200 has successfully connected. At this point, electronic device 101 can request cloud server 400 to bind printer 200's device information to a designated cloud account. This adds printer 200 to the designated cloud account's trust ring.

[0097] Figures 4A-4G This document illustrates a set of interface diagrams provided in this application embodiment, showing how to call the printer assistant in the settings application to bind the device information of printer 200 to a specified cloud account.

[0098] like Figure 4A As shown, the electronic device 101 can display a desktop 310. The textual description of the desktop 310 can be found above. Figure 2A The textual details of the illustrated embodiments will not be repeated here.

[0099] Electronic device 101 can receive user actions (e.g., clicks) on settings application 314, and in response to such actions, electronic device 101 can display, for example... Figure 4B The settings interface shown is 490.

[0100] The settings interface 490 may include one or more settings items. For example, one or more settings items may include WLAN settings, Bluetooth settings, mobile network settings, more connection settings 491, desktop and wallpaper settings, display and brightness settings, sound and vibration settings, battery settings, system settings, etc.

[0101] Electronic device 101 can receive user actions (e.g., clicks) on more connection settings 491, and in response to such actions, electronic device 101 can display, for example... Figure 4C The more connections interface shown is 510.

[0102] like Figure 4C As shown, the more connection interfaces 510 may include printing settings 511, NFC settings, Honor sharing settings, Honor car connectivity settings, and wireless screen projection settings, etc.

[0103] Electronic device 101 can receive user actions on the print setting 511 (e.g., clicking), and in response to the action, electronic device 101 can display, as shown below. Figure 4D The printing interface shown is 520.

[0104] like Figure 4D As shown, the printing interface 520 may include a printing assistant startup control 521.

[0105] Electronic device 101 can be activated by a user's operation (e.g., clicking) on ​​the print assistant launch control 521. In response to this operation, electronic device 101 can launch the print assistant and display, as shown below. Figure 4E The printing assistant interface shown is 530.

[0106] like Figure 4E As shown, the print assistant interface 530 may include a printer display area 531 and an add control 532. The printer display area 531 can be used to display the printers 200 that have been added by the electronic device 101. Since the electronic device 101 has not currently added any printers, it can display an add prompt in the printer display area 531, such as "Multiple printers can be added". The add control 532 can be used to trigger the electronic device 101 to add a printer.

[0107] Electronic device 101 can receive user actions (e.g., clicks) on the added control 532, and in response to such actions, electronic device 101 can display, as shown below. Figure 4F The printer addition interface shown is 540.

[0108] like Figure 4FAs shown, when electronic device 101 enters the printer adding interface 540, it can search for printers using near-field communication technologies (e.g., Bluetooth, Wi-Fi, etc.). Electronic device 101 can display the options corresponding to the searched printers in the printer adding interface 540. For example, when electronic device 101 finds a network-configured printer "PrinterA1" within the local area network, it can display the connection control 541 corresponding to printer "Printer A1" in the list of available printers in the printer adding interface 540. Electronic device 101 can receive broadcast messages sent by printer 200, which include device information of printer 200 (e.g., device name "Printer P1") and a network configuration status indicator, indicating that printer 200 has not stored local area network configuration information. Therefore, electronic device 101 can display the connection control 542 corresponding to printer 200 in the list of available printers and indicate that printer 200 is in an unconfigured state.

[0109] Electronic device 101 can receive user actions (e.g., clicks) on the connection control 542. In response to this action, electronic device 101 can obtain the network name and password of the local area network to which it is connected, and send the network name and password to printer 200. Printer 200 can then connect to the local area network to which electronic device 101 is connected based on the received network name and password.

[0110] like Figure 4G As shown, after electronic device 101 obtains the online information of printer 200 within the local area network, electronic device 101 can display the status information 543 of printer 200 (e.g., idle) in the current printer list of the printer addition interface 540. Furthermore, after successfully configuring printer 200 for network access, electronic device 101 can also request cloud server 400 to bind the device information of printer 200 to a specified cloud account. In this way, printer 200 is added to the trust ring of the specified cloud account.

[0111] In some application scenarios, printer 200 may be connected to the same local area network as electronic device 101, but not bound to a specific cloud account. When electronic device 101 displays the smart interconnection interface of the control center, it can search for printers within the local area network. After finding printer 200, if it is determined that printer 200 is bound to a specific cloud account, electronic device 101 can display a binding pop-up window, prompting the user to bind printer 200 to the specific cloud account, so that printer 200 can be viewed or used in the smart interconnection interface of the control center. After receiving the user's confirmation of binding, electronic device 101 can request cloud server 400 to bind the device information of printer 200 to the specific cloud account. In this way, printer 200 is added to the trust ring of the specific cloud account.

[0112] Figures 5A-5B This document illustrates a set of interface diagrams provided in an embodiment of this application, showing how to add device information of printer 200 to the control center and bind it to a designated cloud account.

[0113] like Figure 5A As shown, in the electronic device 101, the user receives the above... Figure 2M After an operation (e.g., clicking) is performed on the smart interconnection control card 411 in the control center interface 410 shown, the electronic device 101 can first display the smart interconnection interface 420. The electronic device 101 can search for the online information of other devices within the trust ring corresponding to the specified cloud account through near-field communication technology (e.g., Bluetooth, WiFi) or cloud servers.

[0114] like Figure 5B As shown, since a designated cloud account is logged into electronic device 102, electronic device 101 can obtain the online information of electronic device 102 through the cloud server. Therefore, electronic device 101 can display the device option 423 of electronic device 102 on the smart interconnection interface 420. Electronic device 101 can also search for nearby devices not bound to the designated cloud account through near-field communication technologies (e.g., Bluetooth, WiFi). For example, if electronic device 101 discovers printer 200 through near-field communication technology, and printer 200 is not bound to the designated cloud account, electronic device 101 can display a list of devices to be bound 550, which includes the device name 551 of printer 200 and an add control 552. The add control 552 can be used to trigger electronic device 101 to request cloud server 400 to bind the device information of printer 200 to the designated cloud account. The cancel control 553 can be used to trigger electronic device 101 to cancel the request to cloud server 400 to bind the device information of printer 200 to the designated cloud account.

[0115] Electronic device 101 can receive user actions (e.g., clicks) on the add control 552. In response to this action, electronic device 101 sends the device information of printer 200 and a specified cloud account to cloud server 400, allowing cloud server 400 to bind the device information of printer 200 to the specified cloud account, thereby adding printer 200 to the trust ring corresponding to the specified cloud account. Electronic device 101 can also add the device information of printer 200 to the local list of devices already in the ring.

[0116] After binding the device information of printer 200 to the designated cloud account, electronic device 101 can display the above information on the smart interconnection interface 420 upon receiving the online notification from printer 200. Figure 2N Device option 422 for printer 200.

[0117] Figures 5C-5E This illustration shows a schematic diagram of an interface in a control center provided in this application embodiment, in which the device information of a printer is unbound from a specified cloud account.

[0118] like Figure 5C After detecting that printer 200 is online, electronic device 101 can display device option 422 of printer 200 on the smart interconnection interface 420. Electronic device 101 can receive the user's operation of dragging device option 422 to the vicinity of delete control 424.

[0119] like Figure 5D As shown, in response to a user dragging device option 422 near delete control 424, electronic device 101 can display a delete prompt box 560. This delete prompt box 560 can display a delete prompt 561, a confirmation control 562, and a cancel control 563. The delete prompt 561 prompts the user whether to delete printer 200 from the trust ring corresponding to the specified account. For example, the delete prompt 561 can be the text prompt "Delete printer P1 from the trust ring?". The confirmation control 562 can be used to trigger electronic device 101 to delete printer 200 from the trust ring corresponding to the specified account. The cancel control 563 can be used to trigger electronic device 101 to cancel the deletion of printer 200 from the trust ring corresponding to the specified account.

[0120] Electronic device 101 can receive user operations on confirmation control 562 (e.g., clicking). In response to the operation, electronic device 101 can request the cloud server to unbind printer 200 from the specified account and delete the device information of printer 200 from the local whitelist of devices already in the ring, thereby removing printer 200 from the trust ring corresponding to the specified account.

[0121] like Figure 5CAs shown, after removing printer 200 from the trust ring corresponding to the specified account, electronic device 101 can cancel the display of device option 422 for printer 200 in the smart interconnection interface 420.

[0122] In this embodiment of the application, the user's operation on the above-mentioned confirmation control 562 (e.g., clicking) can be referred to as the second operation.

[0123] The following describes the software architecture of an electronic device provided in the embodiments of this application.

[0124] Figure 6 A schematic diagram of the software architecture of an electronic device provided in an embodiment of this application is shown.

[0125] like Figure 6 As shown, the software architecture of an electronic device can include an application layer, a business middleware platform, and a basic middleware platform. The application layer can include a system interaction entry point and a printing entry point. The system interaction entry point can include a control center. The printing entry point can include a printing assistant, smart space applications, system settings printing, shared printing, and third-party applications, etc.

[0126] The business middle platform can include an intelligent multimodal human-computer interaction framework and a basic service framework. The intelligent multimodal human-computer interaction framework can include a shared service management framework. The basic service framework can include printing services.

[0127] The basic middleware platform can include a Magic Ring framework. The Magic Ring framework can include basic Magic Ring services and system hardware and software resource sharing protocol components.

[0128] The trust ring infrastructure services may include a print sharing service. This service supports functions such as printer entry and exit from the trust ring, printer selection, print management, and print expansion capabilities. System hardware and software resource sharing protocol components may include distributed printing services, device management services, far-field communication services, data transmission services, nearby network access services, a distributed invocation framework, and an ecosystem access framework (Magic Link).

[0129] Distributed printing services may include one or more functional application programming interfaces (APIs), print scheduling modules, near-field and far-field print management modules, authorization management modules, protocol packet shelves, third-party printing protocol packets, and Mopria protocol packets. These functionalities may include status management, task management, device information management, device discovery, near-field connectivity, device authentication, and device configuration.

[0130] The device management service can manage the device status, online / offline status, etc., of one or more devices within the trust ring. The far-field communication service can establish communication connections with the far-field cloud server, thereby establishing far-field transmission channels with the far-field communication services of other devices. The data transmission service can be invoked by the printing service to send file data on either the far-field or near-field transmission channels. The near-field access networking service can identify and discover printers via near-field communication and establish near-field transmission channels with printers. The distributed invocation framework enables functions that can be invoked by other devices. The ecosystem access framework (Magic Link) can establish communication connections with the device cloud server (e.g., message queuing telemetry transport (MQTT) connection).

[0131] The system hardware and software resource sharing protocol component can provide a distributed printing protocol interface to the print sharing service. Therefore, the print sharing service can use this interface to call the distributed printing service to perform printing functions such as printer device selection, print management, and print expansion capabilities. The system hardware and software resource sharing protocol component can also provide interfaces for printer trust loop management, discovery, and online / offline status. Therefore, the print sharing service can obtain control over printer trust loops from the distributed printing service through these interfaces.

[0132] The Trust Ring Basic Sharing Service can provide the printing service with its API call interface. The printing service can then provide the printing entry point with its API call interface. The printing sharing service can register itself with the sharing service management framework. This framework can manage the sharing services of multiple devices within the Trust Ring, including the printing sharing service. The sharing service management framework can obtain printer online / offline status from the printing sharing service and send this information to the control center.

[0133] The control center can obtain online / offline information for multiple devices within the trust ring from the shared service management framework. This information may include printer online / offline status. The smart interconnection interface displays device options for multiple devices entering the trust ring, along with their online / offline information. These devices may include printer 200, electronic device 101, and electronic device 102, among others. Multiple devices within the same trust ring are logged in or bound to the same cloud account.

[0134] The following is in conjunction with the above. Figures 2A-2S The illustrated embodiment specifically describes the method and process of adding a printer in a smart space application.

[0135] The device management method provided in this embodiment allows electronic device 101 to request cloud server 400 to bind printer 200's device information to a designated cloud account after adding and configuring printer 200 in the smart space for printing. This allows users to quickly access printer 200 from the smart interconnection interface in the control center of electronic device 101. Furthermore, other devices logged into the designated cloud account can receive printer 200's status information and also access printer 200 for printing, making it convenient for users to use the same printer on different devices.

[0136] Figure 7 A flowchart illustrating a device management method provided in an embodiment of this application is shown.

[0137] like Figure 7 As shown, this method can be applied to a communication system including an electronic device 101 and a cloud server 400. The electronic device 101 may include smart space applications, device management services, an ecosystem access framework (Magic Link), printing services, and a printing assistant, etc. The cloud server 400 may include a device cloud server.

[0138] The method may include the following steps: S701. The Smart Space application detected that the user selected printer 200 to print.

[0139] The user can select printer 200 to print as described above. Figure 2E For details regarding the operation of the service card 326 for printer 200 in the illustrated embodiment, please refer to the above. Figure 2E The embodiments shown are not described in detail here.

[0140] S702. The Smart Space application sends a print request to the print assistant. The print request includes device information for printer 200.

[0141] The device information of printer 200 includes the product identifier (proID) (e.g., "P1"), device identifier, and device name (e.g., "Printer P1"). The device identifier can include any one of the following: unique device identifier (UDID), MAC address, etc.

[0142] S703. Electronic device 101 displays the printing assistant interface.

[0143] For example, the printing assistant interface can be referenced as described above. Figure 2FThe printing assistant interface 340 in the illustrated embodiment will not be described in detail here.

[0144] S704. The Print Assistant detects that the user has selected a target file in the Print Assistant interface.

[0145] For example, the process of selecting a target file in the print assistant interface can be referenced as described above. Figures 2F-2G The embodiments shown are not described in detail here.

[0146] S705. Print Assistant displays the printing interface.

[0147] For example, the printing interface can refer to the above. Figure 2H The printing interface 360 ​​in the illustrated embodiment is described above. Figure 2H The embodiments shown are not described in detail here.

[0148] S706. The printing assistant detects that the target printing parameters entered by the user in the printing interface have been received, and detects the user's start printing operation.

[0149] Users can select the target printing parameters for the target file in the printing interface.

[0150] For example, the user's steps to start printing can refer to the above. Figure 2H In the illustrated embodiment, the specific details of the operation for the start printing control 367 can be found above. Figure 2H The embodiments shown are not described in detail here.

[0151] S707. The Print Assistant sends a print job to the print service. The print job includes the target print parameters, the target file, and the device information of printer 200.

[0152] S708. Print service controls printer 200 to print the target file using the target print parameters.

[0153] Specifically, the printing service can load a target printing protocol package that matches the printer 200 by calling the protocol package shelf based on the device information of the printer 200, and send the target printing parameters and target file to the printer 200 through the target printing protocol package to control the printer 200 to print the target file with the target printing parameters.

[0154] S709. The print service sends a print completion notification to the print assistant.

[0155] After printing the target file according to the target printing parameters, printer 200 can send a print completion message to the print service. This print completion message notifies printer 200 that printing the target file has been completed. Upon receiving the print completion message, the print service can send a print completion notification to the print assistant. The print assistant can then display the print completion notification. Figure 7 (Not shown in the text), this print completion notification is used to indicate that printer 200 has completed printing the target file.

[0156] S710. Print Assistant determines that printer 200 is in the binding whitelist based on the device information of printer 200.

[0157] The whitelist can store product identifiers of printers that can be added to the trust ring corresponding to a specified cloud account. Upon receiving a print completion notification, the print assistant can check if the product identifier for printer 200 is in the whitelist. If it is, the print assistant confirms that printer 200 is in the whitelist. If it is not, the print assistant can skip further steps.

[0158] S711. Print Assistant sends a binding determination request to the device management service.

[0159] The binding determination request includes the device information for printer 200. This binding determination request can be used to request the device management service to determine whether printer 200 is already bound to a specified cloud account.

[0160] S712. The device management service determines, based on the device information of printer 200, that printer 200 is not bound to the specified cloud account.

[0161] The device management service can store a list of bound devices for a specified cloud account. The device management service can determine whether the list of bound devices includes printer 200. If the list includes printer 200, the device management service can determine that printer 200 is bound to the specified cloud account. If the list does not include printer 200, the device management service can determine that printer 200 is not bound to the specified cloud account.

[0162] S713. The device management service returns a binding judgment result of 1. This result indicates that printer 200 is not bound to the specified cloud account.

[0163] S714. Print Assistant displays a binding pop-up window.

[0164] The S715 Print Assistant detected that the user authorized printer 200 to bind a specified cloud account in the binding pop-up window.

[0165] The binding pop-up can be referenced as described above. Figure 2K In the illustrated embodiment, the user's operation of authorizing the printer 200 to bind a specified cloud account in the binding pop-up window 390 can be an operation of the confirmation control 393 in the binding pop-up window 390. For details, please refer to the foregoing. Figure 2K The embodiments shown are not described in detail here.

[0166] In one possible implementation, after receiving the binding judgment result 1, the printing assistant can display a binding pop-up window and directly execute the subsequent step S716.

[0167] S716. The Print Assistant sends a binding request to the Device Management Service. This binding request carries the device information for printer 200.

[0168] S717. The Device Management Service sends a proxy binding request to the Ecosystem Access Framework. This proxy binding request includes the device information for printer 200 and the specified cloud account.

[0169] Because the device management service records the cloud account currently logged into electronic device 101 as a specified cloud account and a list of devices bound to that specified cloud account, the device management service can obtain the device information of printer 200 from the binding request sent by the printing assistant after receiving the binding request. It then sends a proxy binding request carrying the device information of printer 200 and the specified cloud account to the ecosystem access framework.

[0170] The ecosystem access framework is used to communicate with the device cloud server.

[0171] S718. The ecosystem access framework sends a proxy registration request to the device cloud server. This proxy registration request can include the printer 200's device information, a specified cloud account, and registration authentication credentials.

[0172] Specifically, the ecosystem access framework can negotiate a challenge word with the device cloud server, and then obtain the pre-set fixed key of the printer 200. Next, the ecosystem access framework can calculate the registration authentication credential based on the printer 200's device information, the challenge word, and the fixed key.

[0173] S719. The device cloud server binds the device information of printer 200 to a designated cloud account.

[0174] The device cloud server verifies the registration authentication credential and, upon successful verification, binds the printer 200's device information to the designated cloud account. Specifically, the device cloud server can recalculate the registration authentication credential using a challenge word, a fixed key, and the printer 200's device information. If the recalculated credential matches the one carried in the proxy registration request, the verification is successful. After successful verification, the device cloud server can bind the printer 200's device information to the designated cloud account.

[0175] After the device cloud server binds the device information of printer 200 to the designated cloud account, printer 200 enters the trust ring corresponding to the designated cloud account. The device cloud server can store a device list corresponding to the designated cloud account, which records the device information of all devices logged in or bound to the designated cloud account. The device cloud server can manage and update the status information of all devices in the device list corresponding to the designated cloud account, and can synchronize the status information of all devices in the device list to devices logged in with the designated cloud account. Thus, devices logged in with the cloud account can view the status of printer 200 or access printer 200. Therefore, the device cloud server can synchronize the status information of printer 200 to all devices logged in with the designated cloud account (e.g., electronic device 102). In this way, all devices logged in with the designated cloud account can access printer 200 to print.

[0176] S720. The device cloud server returns a binding success response to the ecosystem access framework. This binding success response indicates that printer 200 has been successfully bound to the specified cloud account.

[0177] S721. The ecosystem access framework returns a successful binding response to the device management service.

[0178] S722. Device Management Service adds printer 200's device information to the list of bound devices for a specified cloud account.

[0179] The device management service periodically retrieves status information of each device logged in or bound to a specified cloud account from the device cloud server via the ecosystem access framework and sends this information to the control center. The control center can then display this status information on the smart interconnection interface. Therefore, after adding printer 200 to the list of bound devices for a specified cloud account, the device management service can retrieve printer 200's status information and send it to the control center. The control center can then display this status information on the smart interconnection interface, allowing users to select printer 200 for printing within the interface. This way, users can access printer 200 at any time from the control center without having to manually select it in the smart space application each time.

[0180] S723. The device management service returns a binding success message to the printing assistant. This binding success message indicates that printer 200 has been successfully bound to the specified cloud account.

[0181] S724. The Print Assistant displays a message indicating successful binding.

[0182] The successful binding notification indicates that printer 200 has been successfully bound to the specified cloud account. Step S724 is optional; the printing assistant may choose not to display the successful binding notification.

[0183] In one possible implementation, electronic device 101 can first configure printer 200 to connect to the local area network (LAN) where electronic device 101 is located in the smart space application, and then use printer 200 to print. After the smart space application successfully configures printer 200 to connect to the LAN where electronic device 101 is located, it can trigger electronic device 101 to request cloud server 400 to bind the device information of printer 200 with a specified cloud account through the printing assistant. The process of the printing assistant triggering electronic device 101 to request cloud server 400 to bind the device information of printer 200 with the specified cloud account can be referred to the above. Figure 7 Steps S710 to S722 in the illustrated embodiment will not be described again here.

[0184] In one possible implementation, electronic device 101 can launch a printing assistant through a settings application and configure printer 200 to connect to the local area network (LAN) where electronic device 101 is located. After configuring printer 200 to connect to the LAN, the printing assistant can request cloud server 400 to bind printer 200's device information to a specified cloud account. The process by which the printing assistant triggers electronic device 101 to request cloud server 400 to bind printer 200's device information to the specified cloud account can be referred to the above. Figure 7Steps S710 to S722 in the illustrated embodiment will not be described again here.

[0185] The following is in conjunction with the above. Figures 5A-5B The illustrated embodiment specifically describes the method and process of adding a printer in the control center.

[0186] The device management method provided in this embodiment enables electronic device 101 to request cloud server 400 to bind printer 200's device information to the designated cloud account when the user triggers the smart interconnection interface of the display control center and discovers that printer 200 is not bound to a designated cloud account. The smart interconnection interface can be used to control devices within the trust ring corresponding to the designated cloud account to perform relevant services. This allows users to quickly access printer 200 from the smart interconnection interface of electronic device 101's control center. Furthermore, other devices logged into the designated cloud account can receive printer 200's status information and can also access printer 200 for printing, facilitating the use of the same printer on different devices.

[0187] Figure 8 A flowchart illustrating a device management method provided in another embodiment of this application is shown.

[0188] like Figure 8 As shown, this method can be applied to a communication system including an electronic device 101 and a cloud server 400. The electronic device 101 may include a control center, device management service, Nearby service, printer discovery protocol, printing assistant, and ecosystem access framework (Magic Link), etc. The cloud server 400 may include a device cloud server.

[0189] The method may include the following steps: S801. The control center detected the user's action of opening the smart interconnection interface.

[0190] For example, a smart interconnected interface can be as described above. Figure 5A The smart interconnection interface 420 in the illustrated embodiment. Users can open the smart interconnection interface as described above. Figure 2M The illustrated embodiment shows the user clicking the smart interconnection card 411. For details, please refer to the foregoing. Figure 2M , Figure 5A The embodiments shown are not described in detail here.

[0191] In this embodiment of the application, the aforementioned smart interconnection interface may be referred to as the first interface.

[0192] S802. The control center registers device online / offline monitoring with the device management service.

[0193] The device online / offline monitoring is used to request the device management service to report the status information of devices logged in or bound to a specified cloud account to the control center after obtaining the status information of such devices.

[0194] S803. The Device Management Service sends a registration request to the Nearby Service. This registration request includes a list of devices already bound to the specified cloud account.

[0195] The device management service can manage and store a list of bound devices for a specified cloud account. The list of bound devices includes device information for devices logged into or bound to one or more devices within the specified cloud account. Therefore, the control center can display the status information of one or more devices logged into or bound to the specified cloud account on the smart interconnection interface.

[0196] The device information of printer 200 includes its product identifier (proID) (e.g., "P1"), device identifier, and device name (e.g., "Printer P1"). The device identifier can include any one of the following: unique device identifier (UDID), MAC address, etc.

[0197] The S804.Nearby service sends a callback to the printer discovery protocol to register the device status.

[0198] After obtaining the list of bound devices, the Nearby service can match the discovery protocols corresponding to each device within the trust ring based on the device information in the list. This allows it to search for devices logged in or bound to a specified cloud account using the discovery protocols corresponding to each device within the trust ring. Since the list of bound devices includes device information for other printers, the Nearby service can use the printer discovery protocol to search for printer 200. The Nearby service can register device status callbacks with the printer discovery protocol. These callbacks are used by the printer discovery protocol to send a device discovery notification to the Nearby service after discovering a printer.

[0199] S805. Printer discovery protocol discovers printer 200.

[0200] The printer discovery protocol discovers the communication methods of printer 200, including but not limited to Bluetooth and Wi-Fi.

[0201] S806. The printer discovery protocol calls back a device discovery notification to the Nearby service. This device discovery notification carries the device information for printer 200.

[0202] The S807.Nearby service determines whether printer 200 is bound to a specified cloud account based on the list of bound devices and the device information of printer 200.

[0203] If the device information for printer 200 is in the list of bound devices, then printer 200 has been bound to the specified cloud account, and steps S808 to S810 are executed.

[0204] If the device information for printer 200 is in the list of bound devices, and printer 200 is not bound to the specified cloud account, then proceed to steps S811 to S830.

[0205] The S808.Nearby service sends the printer 200 status information to the device management service.

[0206] The status information includes online and offline status. The online status can include idle status, printing status, etc. Specifically, in this embodiment, the Nearby service sends the online status of printer 200 to the device management service.

[0207] S809. The device management service sends the status information of the bound devices to the control center. This status information includes the status information of printer 200.

[0208] Among them, bound devices can include devices that are logged in or bound to a specified cloud account.

[0209] S810. The control center displays the status information of the bound devices.

[0210] For example, as mentioned above Figure 2N As shown, after receiving the status information of the bound device, the control center can display the device option 422 of printer 200 on the smart interconnection interface 420. When the device option 422 of printer 200 is displayed on the smart interconnection interface 420, it indicates that the status information of printer 200 is online. When the device option 422 of printer 200 is not displayed on the smart interconnection interface 420, it indicates that the status information of printer 200 is offline. Optionally, the control center can also display the status information of the loop-connected device through other display styles, which is not limited here.

[0211] The S811.Nearby service sends a discovery notification for the device to be bound to the device management service. This notification includes device information for printer 200.

[0212] S812. The Device Management Service sends a discovery notification for the devices to be bound to the control center.

[0213] S813. The control center displays a list of devices to be bound, including the device name of printer 200.

[0214] S814. The control center detected the operation of binding the user-authorized printer 200 to a specified cloud account.

[0215] For example, the list of devices to be bound can be referenced above. Figure 5B In the illustrated embodiment, the operation of binding the printer 200 to a specified cloud account in the device list 550 to be bound can be the operation of adding control 552 to the device list 550 described above. For details, please refer to the foregoing. Figure 5B The embodiments shown are not described in detail here.

[0216] S815. The control center sends a binding instruction to the printing assistant.

[0217] The binding instruction carries the device information of printer 200. This binding instruction is used to instruct the printing assistant to bind printer 200 to a specified cloud account.

[0218] Because different types of devices bind to designated cloud accounts in different ways, the control center can trigger the binding of different devices to designated cloud accounts separately through the corresponding business applications of each type of device. For example, the method of binding a speaker device to a designated cloud account is different from that of binding a printer to a cloud account; the business application for the speaker device is Speaker Assistant, and the business application for the printer is Print Assistant. Therefore, the control center can trigger the binding of printer 200 to a designated cloud account through Print Assistant, and the control center can trigger the binding of printer 200 to a designated cloud account through Speaker Assistant.

[0219] S816. The Print Assistant sends a binding request to the Device Management Service. The binding request carries the device information for printer 200.

[0220] S817. The Device Management Service sends a proxy binding request to the Ecosystem Access Framework. This proxy binding request carries the device information for printer 200 and the specified cloud account.

[0221] The S818 ecosystem access framework sends a request for registration information to the device cloud server.

[0222] The "Application for Registration Information Request" is used to request the device cloud server to register the device.

[0223] S819. The device cloud server returns the request response to the ecosystem access framework.

[0224] The application response is used to instruct the device cloud server to agree to the registration of the device by the ecosystem access framework.

[0225] The S820 ecosystem access framework sends a challenge word exchange request to the device cloud server.

[0226] The challenge number exchange request is used to obtain the challenge number. The challenge number is used together with the printer 200's device information and the fixed key to calculate the registration authentication credential.

[0227] S821. The device cloud server returns a challenge word exchange response to the ecosystem access framework.

[0228] The challenge word exchange response contains the challenge word.

[0229] In this way, the ecosystem access framework and the device cloud server can store the same challenge word.

[0230] The S822. Ecosystem Access Framework can obtain the pre-installed fixed key for printer 200.

[0231] S823. The ecosystem access framework calculates the registration authentication credential based on the printer 200's device information, challenge word, and fixed key.

[0232] S824. The ecosystem access framework sends a proxy registration request to the device cloud server. This proxy registration request can include the printer 200's device information, a specified cloud account, and registration authentication credentials.

[0233] S825. The device cloud server verifies the registration and authentication credentials and binds the device information of printer 200 to the designated cloud account.

[0234] The device cloud server can recalculate the registration authentication credential using the challenge word, fixed key, and printer 200's device information. If the recalculated credential matches the one carried in the proxy registration request, the registration authentication credential verification is successful. After successful verification, the device cloud server can bind printer 200's device information to a designated cloud account.

[0235] The device cloud server can store a list of devices corresponding to a specified cloud account. This list contains device information for all devices logged in or bound to the specified cloud account. The device cloud server can manage and update the status information of all devices in the device list corresponding to the specified cloud account, and can synchronize the status information of all devices in the list to devices logged in with the specified cloud account. In this way, devices logged in with the specified cloud account can view the status of printer 200 or access printer 200.

[0236] S826. After binding the device information of printer 200 to a designated cloud account, the device cloud account can return a binding success response to the ecosystem access framework. This binding success response indicates that printer 200 has successfully joined the trust ring corresponding to the designated cloud account.

[0237] S827. The ecosystem access framework can return a successful binding response to the device management service.

[0238] S828. The Device Management Service can return a successful binding response to the Print Assistant.

[0239] After receiving a successful binding response, the printing assistant can send a similar response back to the control center. The control center can then display a successful binding notification upon receiving this response. This notification indicates that printer 200 is bound to the specified cloud account.

[0240] S829. The device management service can invoke callbacks from various services to notify the control center of the status information of the bound devices. This status information includes the status information of printer 200.

[0241] S830. The control center displays the status information of the bound devices.

[0242] For example, as mentioned above Figure 2N As shown, after receiving the status information of the bound device, the control center can display the device option 422 of printer 200 on the smart interconnection interface 420. When the device option 422 of printer 200 is displayed on the smart interconnection interface 420, it indicates that the status information of printer 200 is online. When the device option 422 of printer 200 is not displayed on the smart interconnection interface 420, it indicates that the status information of printer 200 is offline. Optionally, the control center may also display the status information of the bound device through other display styles, which are not limited here.

[0243] The following is in conjunction with the above. Figures 2M-2N The illustrated embodiment specifically describes the process of displaying the printer online in the control center.

[0244] By enabling the online display device in the control center as provided in this embodiment, after the electronic device 101 requests the cloud server 400 to bind the device information of the printer 200 to the specified cloud account, the status information of the printer 200 can be quickly displayed in the smart interconnection interface of the control center when the user triggers the display of the smart interconnection interface of the control center, so that the user can use the printer 200 in the smart interconnection interface of the control center.

[0245] Figure 9This illustration shows a flowchart of a process for going online on a control center display device, as provided in an embodiment of this application.

[0246] like Figure 9 As shown, this method can be applied to a communication system including an electronic device 101 and a printer 200. The electronic device 101 may include a control center, a shared service management framework, a print sharing service, a distributed print service, and the printer 200. The cloud server 400 has bound the printer 200's device information to a designated cloud account, and the electronic device 101 locally stores a list of bound devices for the designated cloud account, which includes the printer 200's device information.

[0247] The method may include the following steps: S901. The control center detected the user's action of opening the smart interconnection interface.

[0248] For example, the user can open the smart interconnection interface as described above. Figure 2M For details regarding the operation of the smart interconnection control card 411 in the illustrated embodiment, please refer to the foregoing. Figure 2N The embodiments shown are not described in detail here.

[0249] S902. The control center sends a call request to the shared service management framework.

[0250] The call request can include the device type of the device that is bound to or logged into a specified cloud account. The call request can be used by the shared service management framework to initialize the corresponding shared services for each device already in the trust ring, thereby discovering various types of devices already in the trust ring through these shared services. For example, devices bound to or logged into a specified cloud account can include printers, speakers, cameras, and televisions; therefore, the shared services initialized by the shared service management framework can include shared services corresponding to devices such as printer sharing services, speaker sharing services, camera sharing services, and television sharing services.

[0251] S903. The shared service management framework sends an initialization request to the print shared service.

[0252] Since the device type of devices that are already bound to or logged into a specified cloud account includes printers, the shared service management framework can send an initialization request to the print sharing service.

[0253] S904. Print Sharing Service registers a device discovery callback in the Distributed Print Service.

[0254] After receiving the initialization request, the print sharing service can register a device discovery callback with the distributed print service, so that the distributed print service can send a device discovery notification to the print sharing service after discovering the printer.

[0255] S905. Distributed printing service scans multicast domain name system (mDns) broadcasts.

[0256] Distributed printing services can discover printers through various methods. These methods may include scanning mDns broadcasts sent by the printer within the local area network. In one possible implementation, printer discovery may also include scanning Bluetooth broadcasts sent by the printer, etc.

[0257] S906. Printer 200 is powered on and online.

[0258] S907. Printer 200 sends mDns broadcast 1. mDns broadcast 1 carries device information of printer 200.

[0259] After going online, printer 200 can connect to the local area network (LAN) and send mDns broadcast 1 within the LAN. The device information of printer 200 includes its product identifier (proID) (e.g., "P1"), device identifier, and device name (e.g., "Printer P1"). The device identifier can include any of the following: unique device identifier (UDID), MAC address, etc.

[0260] S908. After receiving mDns broadcast 1, the distributed printing service updates the status of printer 200 to online.

[0261] S909. The distributed printing service calls back the device discovery notification to the printer sharing service. The distributed printing service carries the online status of printer 200.

[0262] S910. The print sharing service registers itself with the shared service management framework. During the registration process, the print sharing service sends the online status of printer 200 to the shared service management framework.

[0263] S911. The shared service management framework sends the online status of printer 200 to the control center.

[0264] S912. The control center displays printer 200 as online in the smart interconnection interface.

[0265] For example, as mentioned above Figure 2N As shown, after receiving the online status of printer 200, the control center can display device option 422 of printer 200 in the smart interconnection interface 420. When device option 422 of printer 200 is displayed in the smart interconnection interface 420, it indicates that printer 200 is online. Optionally, the control center can also display the status information of devices that are logged in or bound to a specified cloud account through other display styles, which is not limited here.

[0266] The following is in the above Figure 9 Based on the illustrated embodiment, the process of going online on the control center display device will be described in detail.

[0267] Figure 10 A flowchart illustrating the online process of a control center display device is shown in another embodiment of this application.

[0268] like Figure 10 As shown, this method can be applied to a communication system including electronic device 101 and printer 200. Electronic device 101 may include a control center, a shared service management framework, a print sharing service, a distributed printing service, and printer 200. The Nearby service may include an authentication manager module and a device monitor service. The distributed printing service may include an mDns monitor, a printer discovery protocol, and a network service discovery management module (NSD manager).

[0269] The method may include the following steps: S1001. The control center detected the user's action of opening the smart interconnection interface.

[0270] For example, the user can open the smart interconnection interface as described above. Figure 2M For details regarding the operation of the smart interconnection control card 411 in the illustrated embodiment, please refer to the foregoing. Figure 2M The embodiments shown are not described in detail here.

[0271] S1002. The control center sends a call request to the shared service management framework.

[0272] The call request can include the device type of the device that is logged in or bound to a specified cloud account. The call request can be used by the shared service management framework to initialize the corresponding shared services for each logged-in or bound cloud account device, thereby discovering various types of devices logged in or bound to the specified cloud account through these shared services. For example, logged-in or bound cloud account devices can include printers, speakers, cameras, televisions, etc. Therefore, the shared services initialized by the shared service management framework can include shared services corresponding to devices such as printer sharing services, speaker sharing services, camera sharing services, and television sharing services.

[0273] S1003. The shared service management framework sends an initialization request to the print shared service.

[0274] Since the device type of devices that are logged in or bound to a specified cloud account includes printers, the shared service management framework can send an initialization request to the print sharing service.

[0275] S1004. The print sharing service registers a device discovery callback with the device listening service.

[0276] After receiving the initialization request, the print sharing service can first register a device discovery callback in the device listening service of the Nearby service. The device discovery callback is used to trigger the device listening service to return the obtained printer status information to the print sharing service after obtaining it.

[0277] S1005. Enable mDns listener for device listening service.

[0278] The distributed printing service can manage one or more listeners that discover printers. These listeners may include mDns listeners, Bluetooth listeners, etc. Figure 10 (not shown in the image). Therefore, the device monitoring service can enable mDns and Bluetooth listeners to search for printers.

[0279] The S1006.mDns listener sends a printer discovery information retrieval request to the printer discovery protocol.

[0280] This printer monitoring information retrieval request is used to obtain printer monitoring information.

[0281] S1007. The printer discovery protocol sends printer listening information to the mDns listener.

[0282] The printer monitoring information includes the interface of the module used to monitor printers as defined in the printer discovery protocol. For example, the module used to monitor printers as defined in the printer discovery protocol could be the network service discovery management module.

[0283] The S1008.mDns listener determines which network service discovery management module to use to monitor the printer's online / offline status based on the printer's monitoring information.

[0284] The S1009.mDns listener registers a printer listener with the Network Service Discovery Management module.

[0285] S1010 printer 200 is now online.

[0286] Printer 200 can connect to the local area network after going online and send mDns broadcast 1 in the local area network.

[0287] S1011. Printer 200 sends mDns broadcast 1. mDns broadcast 1 carries print service information.

[0288] S1012. After receiving mDns broadcast 1, the network service discovery management module obtains print service information from mDns broadcast 1.

[0289] The printer service information includes the service types supported by printer 200 (e.g., print services) and device information. The device information for printer 200 includes its product identifier (proID) (e.g., "PrinterP1"), device identifier, and device name (e.g., "XX Printer P1"). The device identifier can include any of the following: unique device identifier (UDID), MAC address, etc.

[0290] The S1013 network service discovery management module sends print service information to the mDns listener.

[0291] The S1014.mDns listener sends print service information to the printer discovery protocol.

[0292] S1015. The printer discovery protocol determines printer information based on printer service information. This printer information includes the device information and authentication method of printer 200.

[0293] S1016. The printer discovery protocol sends printer information to the mDns listener.

[0294] The S1017.mDns listener sends printer information to the device listening service.

[0295] S1018. The device monitoring service determines whether to perform whitelist authentication on printer 200 through the authentication management module based on printer information.

[0296] Specifically, the authentication method for printer 200 in the device monitoring service is determined to be whitelist authentication of printer 200 through the authentication management module.

[0297] S1019. The device monitoring service sends a device authentication request to the authentication management module.

[0298] This device authentication request is used to request the authentication management module to perform whitelist authentication for printer 200. The device authentication request carries the device information of printer 200.

[0299] The S1020 authentication management module performs whitelist authentication on printer 200.

[0300] The authentication management module stores a whitelist of printers that can be added to the trust ring of a specified cloud account. The authentication management module can determine whether the whitelist contains the product identifier for printer 200.

[0301] If the whitelist contains the product identifier of printer 200 and printer 200 is already bound to a designated cloud account, then proceed to steps S1021 to S1025.

[0302] If the product identifier of printer 200 is stored in the whitelist and printer 200 is not bound to a specified cloud account, then proceed to steps S1026 to S1030.

[0303] If the product identifier of printer 200 is not stored in the whitelist, the authentication management module notifies the device monitoring service that whitelist authentication for printer 200 has failed. The device monitoring service does not report the status information of printer 200 to the print sharing service.

[0304] S1021. The authentication management module sends authentication result 1 to the device monitoring service. Authentication result 1 indicates that printer 200 is on the ring whitelist and that printer 200 has entered the trust ring corresponding to the specified cloud account.

[0305] S1022. The device monitoring service calls back the device discovery notification to the print sharing service.

[0306] S1023. The print sharing service registers with the print sharing service management framework.

[0307] S1024. The shared service management framework sends the online status of printer 200 to the control center.

[0308] S1025. The control center displays on the smart interconnection interface that printer 200 is online.

[0309] For example, as mentioned above Figure 2NAs shown, after receiving notification of the printer 200's online status, the control center can display the printer 200's device option 422 on the smart interconnection interface 420. When the printer 200's device option 422 is displayed on the smart interconnection interface 420, it indicates that the printer 200 is online. Optionally, the control center can also display the status information of the bound device using other display styles; this is not limited here.

[0310] S1026. The authentication management module sends authentication result 2 to the device monitoring service. Authentication result 2 indicates that printer 200 is on the whitelist and that printer 200 is not bound to the specified cloud account.

[0311] S1027. The Device Listening Service sends an Unbound Callback Notification to the Print Sharing Service. This Unbound Callback Notification carries device information for printer 200.

[0312] S1028. The print sharing service sends unbound device information to the sharing service management framework. This unbound device information includes the device information for printer 200.

[0313] S1029. The shared service management framework sends information about unbound devices to the control center.

[0314] S1030. The control center displays a list of devices to be bound, including the device name of printer 200.

[0315] For example, the list of devices to be bound can be referenced above. Figure 5B In the illustrated embodiment, the operation of authorizing the user to bind the printer 200 to a specified cloud account, as described above, can be the operation of adding control 552 to the list of devices to be bound 550. For details, please refer to the foregoing. Figure 5B The embodiments shown are not described in detail here.

[0316] After the control center displays the list of devices to be bound, it can trigger the cloud server 400 to bind the printer 200 to the specified cloud account when it detects an operation to bind the printer 200 to the specified cloud account. The process by which the control center triggers the binding of the printer 200 to the specified cloud account can be referred to the aforementioned steps. Figure 8 The embodiments shown are not described in detail here.

[0317] Through the process of going online on the control center display device provided in this application embodiment, after the electronic device 101 binds the printer 200 to the designated cloud account logged in on the electronic device 101, when the user triggers the display of the smart interconnection interface of the control center, the electronic device 101 can quickly display the status information of the printer 200 in the smart interconnection interface of the control center, so that the user can use the printer 200 in the smart interconnection interface of the control center.

[0318] The following is in conjunction with the above. Figures 5C-5E The illustrated embodiment specifically describes the process of unbinding a device from a cloud account.

[0319] Figure 11 This illustration shows a flowchart of a process for unbinding a device from a cloud account, as provided in an embodiment of this application.

[0320] like Figure 11 As shown, this method can be applied to a communication system including an electronic device 101 and a cloud server 400. The electronic device 101 may include a control center, device management services, an ecosystem access framework (Magic Link), a printing assistant, etc. The cloud server 400 may include a device cloud server.

[0321] S1101. The control center detected that the user unbound printer 200 from the designated cloud account.

[0322] The process of unbinding printer 200 from the designated cloud account can be found in the previous section. Figures 5C to 5E The embodiments shown will not be described in detail here.

[0323] S1102. The control center sends an unbinding request to the printing assistant. The loopback request includes the specified cloud account and device information for printer 200.

[0324] S1103. The Print Assistant sends an unbinding instruction to the Device Management Service. The unbinding instruction includes the specified cloud account and device information for printer 200.

[0325] S1104. The Device Management Service sends an unbinding notification to the Ecosystem Access Framework. The unbinding notification includes the specified cloud account and device information for printer 200.

[0326] S1105. The ecosystem access framework sends an unbinding notification to the device cloud server.

[0327] S1106. Remove the device information of printer 200 from the designated cloud account on the device cloud server.

[0328] After the cloud server unbinds the device information of the second electronic device from the cloud account, it can delete the device information of printer 200 from the device list corresponding to the cloud account. In this way, the device logged in with the cloud account will not be able to obtain the status information of printer 200 through the cloud server.

[0329] S1107. The device cloud server sends a successful unbinding response to the ecosystem access framework.

[0330] The unbinding success response indicates that the device information of printer 200 has been unbound from the specified cloud account.

[0331] S1108. The ecosystem access framework sends a message to the device management service indicating successful unbinding.

[0332] S1109. Device Management Service removes printer 200's device information from the list of bound devices.

[0333] S1110. The device management service sends the updated status information of the bound devices to the control center.

[0334] The updated status information for bound devices does not include the device information for printer 200. After deleting printer 200's device information from the list of bound devices, the device management service can obtain the updated list of bound devices. Then, the device management service can retrieve the updated status information of the bound devices and send it to the control center through the services of each device.

[0335] S1111. The control center displays the updated bound devices on the smart interconnection interface. Printer 200 is not included in the updated bound devices.

[0336] Through the process of unbinding the device from the cloud account provided in this application embodiment, after the electronic device 101 binds the printer 200 to the specified cloud account logged in on the electronic device 101, the user can quickly trigger the unbinding of the printer 200 from the specified cloud account through the control center.

[0337] The following describes the process by which electronic device 101 triggers cloud server 400 to bind printer 200 to a specified cloud account, and then electronic device 101 synchronizes the configuration information of printer 200 to electronic device 102, which is also logged into the specified cloud account.

[0338] After binding the device information of printer 200 to the designated cloud account logged in on electronic device 101, electronic device 101 can synchronize the configuration information to electronic device 102, which is also logged in with the designated cloud account. In this way, electronic device 102 can control printer 200 to print without separate configuration when using printer 200.

[0339] Figure 12 A flowchart illustrating a printer configuration synchronization process provided in an embodiment of this application is shown.

[0340] like Figure 12 As shown, this method can be applied to a communication system that includes electronic device 101, electronic device 102, printer 200 and cloud server 400.

[0341] The method may include the following steps: S1201. An operation was detected in which the user set the target printing parameters for printer 200.

[0342] The operation of the target printing parameters for printer 200 can be referred to the above. Figure 2H The illustrated embodiment will not be described in detail here. Target printing parameters may include the number of copies to be printed, single-sided or double-sided printing, paper size, color or black-and-white printing, etc.

[0343] S1202. Electronic device 101 synchronizes the configuration information of printer 200 to cloud server 400.

[0344] The configuration information for printer 200 includes loopback credentials and target printing parameters. Loopback credentials can be used to grant other devices logged in with a specified cloud account permission to access printer 200.

[0345] S1203. Cloud server 400 encrypts and stores the configuration information of printer 200.

[0346] S1204. Cloud server 400 synchronizes the configuration information of printer 200 to electronic device 102.

[0347] S1205. Electronic device 102 detected that printer 200 is online.

[0348] Specifically, electronic device 101 can send the online status of printer 200 to cloud server 400 after detecting its online status. After receiving the online status of printer 200, cloud server 400 can send the online status of printer 200 to electronic device 102 logged into a specified cloud account.

[0349] S1206. Electronic device 102 detects a user's operation to call printer 200.

[0350] In this embodiment, electronic device 102 detects the user's operation of calling printer 200. This can be referred to as electronic device 101 detecting the user's operation of calling printer 200 in the previous embodiment, and will not be repeated here.

[0351] S1207. Electronic device 102 sets the initial printing parameters of printer 200 to the target printing parameters.

[0352] S1208. Electronic device 102 can use the entry credential to control printer 200 to perform printing tasks.

[0353] The following is in the above Figure 12 Based on the illustrated embodiment, the process of electronic device 101 triggering cloud server 400 to bind printer 200 to a specified cloud account, and then electronic device 101 synchronizing the configuration information of printer 200 to electronic device 102 which is also logged into the specified cloud account, is described in detail.

[0354] Figure 13 A flowchart illustrating a printer configuration synchronization process provided in another embodiment of this application is shown.

[0355] like Figure 13 As shown, this method can be applied to a communication system including electronic device 101, electronic device 102, and cloud server 400. Electronic device 101 may include a device management module 1011 and a printing assistant 1012. Electronic device 102 may include a device management module 1021 and a printing assistant 1022. Cloud server 400 may include a device cloud server and a space cloud server. Both electronic device 101 and electronic device 102 are logged into with a designated cloud account.

[0356] The method may include the following steps: S1301. Print Assistant 1012 detected the user's operation of setting the target printing parameters for printer 200.

[0357] The operation of the target printing parameters for printer 200 can be referred to the above. Figure 2H The illustrated embodiment will not be described in detail here. Target printing parameters may include the number of copies to be printed, single-sided or double-sided printing, paper size, color or black-and-white printing, etc.

[0358] After the user sets the target printing parameters for the printer 200 on the electronic device 101, the electronic device 101 can synchronize the printer 200's configuration information to the electronic device 102 using the following two configuration synchronization methods.

[0359] Configuring synchronization method 1 may include the following steps S1302 to S1307. Configuring synchronization method 2 may include the following steps S1308 to S1313.

[0360] Configure synchronization method 1: S1302. Print Assistant 1012 sends the target printing parameters to Device Management Module 1011.

[0361] For example, printing parameter 1 could be 5 copies, single-sided printing, A4 paper size, black and white printing, etc.

[0362] S1303. Device management module 1011 sends the configuration information of printer 200 to device cloud server 401.

[0363] S1304. The device cloud server synchronizes the configuration information of printer 200 to the device management module 1021.

[0364] S1305. Device management module 1021 parses the target printing parameters from the configuration information of printer 200.

[0365] S1306. Device management module 1021 sends target printing parameters to printing assistant 1022.

[0366] S1307. Print Assistant 1022 sets the initial print parameters to the target print parameters.

[0367] Configure synchronization method 2: S1308. Print Assistant 1012 uploads the target printing parameters of printer 200 to the space cloud server 402.

[0368] S1309. Space cloud server 402 sends the version number of the target printing parameters to printing assistant 1022.

[0369] S1310. Print Assistant 1022 determines whether the target print parameters need to be updated and downloaded locally based on the version number of the target print parameters.

[0370] S1311. If it is necessary to download the target print parameters, the print assistant 1022 sends a print parameter download request to the space cloud server 402. The print parameter download request carries the device information of the printer 200.

[0371] S1312. The space cloud server 402 returns the target printing parameters of printer 200 to the printing assistant 1022.

[0372] S1313. Print Assistant 1022 sets the initial print parameters to the target print parameters.

[0373] The printer configuration synchronization process provided in this embodiment enables electronic device 101 to synchronize configuration information with electronic device 102 that is logged into the designated cloud account after adding printer 200 to the trust ring corresponding to the designated cloud account logged in on electronic device 101. This allows electronic device 102 to control printer 200 for printing without separate configuration during use.

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

[0375] Figure 14A A schematic diagram of the hardware structure of an electronic device 100 provided in an embodiment of this application is shown.

[0376] It should be understood that, Figure 14A The electronic device 100 shown is merely an example, and the electronic device 100 may have more than Figure 14A The more or fewer components shown can be combined into two or more components, or they can have different component configurations. Figure 14A 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.

[0377] Electronic device 100 may include: processor 110, 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.

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

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

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

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

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

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

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

[0385] 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 an audio device (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 110 and may be housed in the same device as the mobile communication module 150 or other functional modules.

[0386] 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 110. The wireless communication module 160 can also receive signals to be transmitted from processor 110, perform frequency modulation and amplification, and convert them into electromagnetic waves for radiation via antenna 2.

[0387] 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 and for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or modify display information.

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

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

[0390] In this embodiment of the application, the device type of electronic device 100 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.

[0391] It should be noted that the above Figure 1 The structures of electronic devices 101 and 102 in the illustrated embodiments can both refer to the above description. Figure 14A The electronic device 100 shown will not be described in detail here.

[0392] The hardware structure of the printer 200 provided in the embodiments of this application is described below.

[0393] Figure 14B A schematic diagram of the hardware structure of a printer 200 provided in an embodiment of this application is shown.

[0394] like Figure 14B As shown, the printer 200 may include: a processor 211, a memory 212, a wireless communication module 213, a power switch 214, and a printing module 215. Wherein: 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.

[0395] The controller can serve as the nerve center and command center of the printer 200. Based on the instruction opcode and timing signals, the controller generates operation control signals to control the fetching and execution of instructions.

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

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

[0398] Memory 212 is coupled to processor 211 and is used to store various software programs and / or 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 wireless access device 300 or other devices.

[0399] 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 printer 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.

[0400] 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).

[0401] Possibly, the Wi-Fi module can be integrated with other communication modules (e.g., 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., enabling other devices to discover the wireless access device 300 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.

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

[0403] The power switch 214 can be used to turn the printer 200 on or off.

[0404] The printing module 215 can be used to print paper documents. In one possible implementation, the printing module 215 can also copy paper documents or scan electronic documents from paper documents.

[0405] In some embodiments, the hardware structure of printer 200 may further include an audio module. Figure 14B (not shown in the image) and loudspeaker ( Figure 14B (Not shown in the image). The audio module 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 audio module can also be used for encoding and decoding audio signals. The loudspeaker, also called a "horn," is used to convert audio electrical signals into sound signals.

[0406] In some embodiments, the hardware structure of the printer 200 may also include a microphone. Figure 14B (Not shown in the image). A microphone, also called a "voice transducer," 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.

[0407] In some embodiments, the hardware structure of the printer 200 may further include a display screen. Figure 14B (Not shown in the image). The display screen is used to display images, videos, etc. The display screen includes a display panel. In some embodiments, the printer 200 may include one or N display screens, where N is a positive integer greater than 1.

[0408] It should be noted that, Figure 14B The printer 200 shown is merely one implementation of the embodiments of this application. In actual applications, the printer 200 may include more or fewer components, which is not limited here.

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

[0410] Figure 14C This document shows a schematic diagram of the hardware structure of a cloud server 400 provided in an embodiment of this application.

[0411] like Figure 14C 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: 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.

[0412] 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 the wireless access device 300, electronic device 101, and electronic device 102.

[0413] 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-side implementation method of the embodiments of this application. In the embodiments of this application, memory 4013 may also be a storage array, etc.

[0414] 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 14C The hardware structure of the cloud server 400 is shown.

[0415] It needs to be explained that, Figure 14C The cloud server 400 shown is merely one implementation of the embodiment of this application. In actual applications, the cloud server 400 may include more or fewer components, which is not limited here.

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

[0417] This application also provides a computer program product that, when run on an electronic device, enables the electronic device to perform the steps described in the various method embodiments above.

[0418] This application also provides a chip system, which includes a processor coupled to a memory. The processor executes a computer program stored in the memory to implement the steps of any method embodiment of this application. The chip system can be a single chip or a chip module composed of multiple chips.

[0419] 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 in 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 page, 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. The source code of a web page 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 web page is also defined through tags or nodes in the web page's source code; for example, HTML uses tags or nodes to define the content. 、 、 <video> 、 <canvas>To define the elements and attributes of a webpage.

[0420] 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 interface element such as an icon, window, or control displayed on the screen of an electronic device. The control can include visual interface elements such as icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, and widgets.

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

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

[0423] 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 method for managing equipment, characterized in that, A communication system comprising a first electronic device, a second electronic device, and a cloud server, wherein the first electronic device and the second electronic device are connected to a first local area network, and the first electronic device is logged into a cloud account; the method includes: The first electronic device receives a first operation to open the first interface; In response to the first operation, the first electronic device displays the first interface and displays options for one or more devices on the first interface, wherein the one or more devices log in or bind to the cloud account, and the one or more devices include the first electronic device; The first electronic device obtains the device information of the second electronic device through a printer discovery protocol; The first electronic device determines whether the second electronic device has been bound to the cloud account based on the device information of the second electronic device and the list of bound devices. The list of bound devices includes device information of one or more devices that are logged in or bound to the cloud account. If the second electronic device is not bound to the cloud account, the first electronic device displays a list of devices to be bound on the first interface, wherein the list of devices to be bound includes the device name of the second electronic device; When the operation of binding the second electronic device to the cloud account is received, the first electronic device sends a challenge word exchange request to the cloud server, wherein the challenge word exchange request is used to obtain a challenge word; The cloud server sends a challenge word exchange response to the first electronic device, wherein the challenge word exchange response carries the challenge word; The first electronic device calculates the first registration authentication credential based on the preset fixed key of the second electronic device, the challenge word, and the device information of the second electronic device; The first electronic device sends a proxy registration request to the cloud server. The proxy registration request carries the device information of the second electronic device, the first registration authentication certificate, and the cloud account. The proxy registration request is used to request the cloud server to bind the device information of the second electronic device with the cloud account. When the cloud server calculates a second registration authentication credential based on the fixed key of the second electronic device, the device information of the second electronic device, and the challenge word, and the second registration authentication credential is the same as the first registration authentication credential, the cloud server binds the device information of the second electronic device to the cloud account; The cloud server sends a binding success response to the first electronic device, wherein the binding success response is used to indicate that the cloud server has successfully bound the device information of the second electronic device to the cloud account; After the first electronic device receives the binding success response, the first electronic device displays the device options of the first electronic device and the device options of the second electronic device on the first interface; In response to the operation of dragging the device option of the second electronic device to the area where the device option of the first electronic device is located, the first electronic device displays a second interface, the second interface including a gallery application icon, and a print capsule displayed at the top of the second interface, the print capsule displaying the icon and device model of the second electronic device; In response to an operation on the gallery application icon, a thumbnail of the first image is displayed while the printed capsule remains displayed; In response to an operation on the thumbnail of the first image, the first image is displayed while the printed capsule remains displayed; In response to the operation on the printed capsule, a print notification bar is displayed, which shows the file name of the first image and print controls; In response to an operation on the print control, the print interface is displayed; The first electronic device controls the second electronic device to perform the printing task according to the target printing parameters in the printing interface.

2. The method according to claim 1, characterized in that, After the first electronic device receives the successful binding response, the method further includes: The first electronic device detects that the second electronic device is online via the first local area network; The first electronic device sends the online status and device information of the second electronic device to the third electronic device logged into the cloud account through the cloud server.

3. The method according to claim 1, characterized in that, After the first electronic device controls the second electronic device to perform a printing task according to the target printing parameters in the printing interface, the method further includes: The first electronic device receives a second operation from the user to unbind the second electronic device from the cloud account; In response to the second operation, the first electronic device sends an unbinding notification to the cloud server. The unbinding notification carries the device information of the second electronic device and the cloud account. The unbinding notification is used to notify the cloud server to unbind the device information of the second electronic device from the cloud account.

4. The method according to claim 3, characterized in that, After the first electronic device sends an unbinding notification to the cloud server, the method further includes: The first electronic device receives an unbinding response from the cloud server, the unbinding response indicating that the cloud server has unbound the device information of the second electronic device from the cloud account; The first electronic device receives a first operation from the user to open the first interface; In response to the first operation, the first interface is displayed, and options for one or more devices are displayed on the first interface, wherein the one or more devices are logged in or bound to the cloud account, wherein the one or more devices include the first electronic device but do not include the second electronic device.

5. The method according to claim 1, characterized in that, The printing interface also includes a start printing control; The first electronic device controls the second electronic device to perform a printing task according to the target printing parameters in the printing interface, including: In response to an operation on the start printing control, the first electronic device sends the target printing parameters and the first image to the second electronic device via the first local area network, wherein the first image and the target printing parameters are used to trigger the second electronic device to print the first image with the target printing parameters.

6. The method according to claim 5, characterized in that, After the first electronic device controls the second electronic device to perform a printing task according to the target printing parameters in the printing interface, the method further includes: The first electronic device sends configuration information to the third electronic device through the cloud server. The third electronic device is logged into the cloud account. The configuration information includes a first parameter and the target printing parameter. The configuration information is used to instruct the third electronic device to set the initial printing parameter on the third electronic device to the target printing parameter. The first parameter is used to grant the third electronic device permission to call the second electronic device to print.

7. The method according to claim 1, characterized in that, The second electronic device is a printer; the first electronic device includes a control center, a shared service management framework, a print service framework, and a distributed print service. After the first electronic device controls the second electronic device to perform a printing task according to the target printing parameters in the printing interface, the method further includes: In response to the first operation, the control center sends a call request to the shared service management framework, the call request being used to invoke the shared service management framework; The shared service management framework initializes one or more shared services, wherein the one or more shared services include a printing shared service; After being initialized, the print sharing service registers a device discovery callback with the distributed printing service. After the distributed printing service registers the device discovery callback, when it discovers the second electronic device, it determines the status information of the second electronic device as online. The distributed printing service sends a device discovery notification to the print sharing service, wherein the device discovery notification carries the online status of the second electronic device; After receiving the device discovery notification, the print sharing service registers with the sharing service management framework and returns the printer's online status to the sharing service management framework. After receiving the registration of the print sharing service, the shared service management framework obtains the online status of the second electronic device; After obtaining the online status of the second electronic device, the shared service management framework sends the online status of the second electronic device to the control center. After the control center obtains the online status of the second electronic device, it displays the first interface and shows the device options of the first electronic device and the second electronic device on the first interface.

8. The method according to claim 1, characterized in that, The second electronic device is a printer; the first electronic device includes a printing assistant, an ecosystem access framework, and device management services. When the operation to bind the second electronic device to the cloud account is received, the first electronic device sends a challenge word exchange request to the cloud server, including: The printing assistant sends a binding request to the device management service, and the binding request carries the device information of the second electronic device. In response to receiving the binding request, the device management service sends a proxy binding request to the ecosystem access framework, the proxy binding request carrying the printer's device information and the cloud account; After receiving the proxy binding request, the ecosystem access framework sends a challenge word exchange request to the cloud server.

9. An electronic device, specifically a first 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 computer program code, the computer program code including computer instructions, which, when executed by the one or more processors, cause the first electronic device to perform the method as described in any one of claims 1-8.

10. 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 method as described in any one of claims 1-8.

Images