Method for adding devices in batches, and related device

Abstract

A method for adding devices in batches, and a device. The method for adding devices in batches comprises: receiving a first operation of a user (S131); in response to the first operation of the user, starting a smart device management application, and displaying a first interface, wherein the first interface comprises a plurality of controls (253) used for adding devices in batches (S132); receiving a second operation of the user for the controls (253) in the first interface (S133); in response to the second operation, initiating a batch addition of a plurality of devices to be added, wherein the controls (253) are used for triggering the selection of the plurality of devices to be added in the first interface and initiating the batch addition of the plurality of devices to be added (S134); and displaying a second interface, wherein a result of the batch addition from the plurality of devices to be added is displayed in the second interface (S135). Smart devices are added in batches by means of a smart device management application, such that the device adding and usage experience of users is improved.

Description

Method for adding devices in batches and related equipment Technical Field

[0001] The present application relates to the field of Internet of Things technology, and in particular to a method for adding devices in batches and related equipment. Background Art

[0002] With the development of smart home technology, the demand for smart home devices in homes and buildings is increasing. Many smart home devices need to be added to the application ecosystem after installation, so that users can manage smart home devices through applications installed on their terminal devices. For example, smart home devices may include sensors, alarms, smart lights, smart speakers, smart cameras, door locks, smart curtains, and more.

[0003] However, the smart device management applications in related technologies cannot add smart home devices in batches. Users often need to add smart home devices to the applications one by one. For a large number of smart home devices, it takes a lot of time and effort to add devices, and there is a possibility that devices will be missed.

[0004] Summary of the Invention

[0005] In view of this, it is necessary to provide a method for adding devices in batches to solve the problem that smart device management applications in the prior art cannot add smart devices in batches.

[0006] A first aspect of an embodiment of the present application discloses a method for adding devices in batches, which is applied to a terminal device, and the terminal device is installed with a smart device management application. The method for adding devices in batches includes: in response to a first operation of a user, starting the smart device management application, and displaying a first interface, the first interface including controls for adding devices in batches; in response to a second operation of the user on the controls in the first interface, initiating batch addition of multiple devices to be added, the controls are used to trigger selection of multiple devices to be added in the first interface and initiating batch addition of multiple devices to be added; and displaying a second interface, the second interface displaying batch addition results of multiple devices to be added.

[0007] By adopting the above technical solution, the smart device management application may include a first interface for adding devices in batches and a second interface for displaying the batch addition results. The first interface may display the various devices to be added scanned by the gateway device. The first interface may include one or more controls. The user can use the controls in the first interface to select multiple devices to be added on the first interface and initiate batch addition of the multiple devices to be added, and the batch addition results can be displayed, so that the user can add smart home devices in batches through the smart device management application, thereby improving the user's device addition and usage experience.

[0008] In one possible implementation, the control includes a first control for turning on or off the batch adding function. When the first control is in the turned-on state, the first interface allows selection of multiple devices to be added. When the first control is in the turned-off state, the first interface does not allow selection of multiple devices to be added.

[0009] Using the above technical solution, the batch add function can be enabled or disabled by configuring a first control on the first interface for enabling or disabling the batch add function. For example, when the first control is enabled, smart home devices can be selected and added in batches through the smart device management application. When the first control is disabled, individual smart home devices can be selected and added through the smart device management application.

[0010] In one possible implementation, when the first control is in the turned-on state, the first interface includes a first device display area and a second device display area, the first device display area is used to display devices that support batch addition, and the second device display area is used to display devices that do not support batch addition, and the second operation includes selecting multiple devices to be added in the first device display area.

[0011] By adopting the above technical solution, by displaying devices that support batch addition and devices that do not support batch addition in different areas, users can quickly know which devices support batch addition and which devices do not support batch addition. It also allows users to quickly select devices in batches when adding devices in batches, avoiding users from mistakenly selecting devices that do not support batch addition and initiating batch addition, thereby improving users' device addition and usage experience.

[0012] In one possible implementation, the terminal device establishes a communication connection with the gateway device and initiates batch addition of multiple devices to be added, including: controlling the gateway device to establish a connection with the multiple devices to be added, and registering the multiple devices to be added to the server corresponding to the smart device management application.

[0013] By adopting the above technical solution, the gateway device can respond to the user's operation on the first interface, establish connections with multiple devices to be added selected by the user, and register multiple devices to be added to the server corresponding to the smart device management application, thereby enabling users to add smart home devices in batches through the smart device management application, thereby improving the user's device addition and usage experience.

[0014] In one possible implementation, the method for adding devices in batches also includes: when the remaining number of connectable gateway devices is less than the number of multiple devices to be added selected in the first device display area, opening a first window, the first window covering part of the content of the first interface, and the first window including warning prompt information of the remaining number of connectable gateway devices.

[0015] With the above technical solution, since the gateway device can connect to a limited number of devices, if the remaining number of connectable devices of the gateway device is less than the number of multiple devices to be added selected in the first device display area, it indicates that the gateway device cannot establish connections with all of the multiple selected devices to be added. By opening the first window, the user is prompted to reselect the devices to be added, or to replace other gateway devices to connect to these devices to be added, so as to smoothly add these devices to be added. The content displayed in the first window may include warning information on the remaining number of connectable devices of the gateway device.

[0016] In one possible implementation, when the gateway device scans for devices to be added of a specified device category, the first interface includes a third device display area. When the first control is in an on state and the devices displayed in the third device display area are devices that support batch addition, the second operation includes selecting multiple devices to be added in the third device display area.

[0017] By adopting the above technical solution, for the scanning of devices to be added of a specified device category, since the scanned devices belong to the same device category, that is, the scanned devices are either all devices that support batch addition or all devices that do not support batch addition, there is no need to display them in different areas. One device display area can be used to display the scanned devices. When the first control is turned on and the devices displayed in the device display area are devices that support batch addition, it indicates that the scanned devices are devices that support batch addition. The user can select multiple devices to be added in the device display area to realize batch addition of devices.

[0018] In one possible implementation, the method for adding devices in batches also includes: when the remaining number of connectable gateway devices is less than the number of multiple devices to be added selected in the third device display area, opening a second window, the second window covering part of the content of the first interface, and the second window including warning prompt information of the remaining number of connectable gateway devices.

[0019] With the above technical solution, since the gateway device can connect to a limited number of devices, if the remaining number of connectable devices of the gateway device is less than the number of multiple devices to be added selected in the device display area, it indicates that the gateway device cannot establish connections with all of the multiple selected devices to be added. By opening a second window, the user is prompted to reselect the devices to be added, or to replace other gateway devices to connect to these devices to be added, so as to smoothly add these devices to be added. The content displayed in the second window may include warning information on the remaining number of connectable devices of the gateway device.

[0020] In one possible implementation, the batch addition results of multiple devices to be added include the addition results of each device to be added in the multiple devices to be added, and the addition results include successful addition or failed addition. Successful addition means establishing a connection with the gateway device and successfully registering on the server. Failed addition means failing to establish a connection with the gateway device or failing to register on the server.

[0021] Using the above technical solution, completing the addition of a device may mean that the device establishes a connection with the gateway device, and the gateway device successfully registers the device on the server. That is, for a device that is successfully added, it may mean that the device establishes a connection with the gateway device and is successfully registered on the server. For a device that fails to be added, it may mean that the device fails to establish a connection with the gateway device, or fails to register on the server.

[0022] In one possible implementation, the second interface includes a first connection result display area, a second connection result display area, and a connection suggestion display area. The first connection result display area is used to display devices that have been successfully added, the second connection result display area is used to display devices that have failed to be added, and the connection suggestion display area is used to display suggested solutions for failed additions.

[0023] By adopting the above technical solution, the batch addition results of multiple devices to be added are displayed in different areas, so that users can intuitively know which devices are added successfully and which devices fail to be added, and the suggested solutions for failed additions are displayed in the connection suggestion display area, so that users can try to add the added devices again based on the suggested solutions.

[0024] In a possible implementation, before displaying the second interface, the method further includes: displaying a third interface, where the third interface includes the adding progress of each device to be added among the multiple devices to be added and the total adding progress of the multiple devices to be added.

[0025] By adopting the above technical solution, before displaying the batch addition results of multiple devices to be added, the addition progress of each device to be added and the total addition progress of multiple devices to be added can be displayed, so that the user can know the addition progress and addition results of each device to be added in real time through the smart device management application.

[0026] In one possible implementation, the third interface also includes a first progress display area, a second progress display area, and a third progress display area. The first progress display area is used to display devices being added, the second progress display area is used to display devices that have been added successfully, and the third progress display area is used to display devices that have failed to be added.

[0027] By adopting the above technical solution, the devices being added, the devices successfully added, and the devices failed to be added are displayed in different areas, so that users can intuitively know the addition progress and results of each device to be added through the smart device management application.

[0028] In one possible implementation, the method for adding devices in batches also includes: when the first control is in a closed state, receiving a third operation from the user on the first interface, the third operation including selecting a device to be added on the first interface for addition; in response to the third operation, initiating the addition of the selected device to be added.

[0029] By adopting the above technical solution, when the first control is in the closed state, it indicates that the batch adding function is closed, and only devices can be added one by one. The first interface does not need to distinguish whether the device to be added is a device that supports batch adding or a device that does not support batch adding. The device to be added can be displayed in a device display area. By selecting a device to be added on the first interface and responding to the add operation, the addition of the selected device to be added is initiated, and the addition of a single smart home device can be executed through the smart device management application.

[0030] In one possible implementation, the terminal device establishes a communication connection with the gateway device and initiates the addition of the selected device to be added, including: controlling the gateway device to establish a connection with the selected device to be added, and registering the selected device to be added to the server corresponding to the smart device management application.

[0031] By adopting the above technical solution, the gateway device can respond to the user's operation on the first interface, establish a connection with the single device to be added selected by the user, and register the selected single device to be added to the server corresponding to the smart device management application, thereby enabling the user to add a single smart home device through the smart device management application, thereby improving the user's device addition and usage experience.

[0032] In one possible implementation, a communication connection is established between the terminal device and the gateway device, and in response to a first operation of the user, a smart device management application is started and a first interface is displayed, including: in response to the first operation of the user, the smart device management application is started and the home interface of the smart device management application is displayed; a third window is opened, the third window covers part of the content of the home interface, and the third window displays the information of the device to be added scanned by the gateway device; in response to a fourth operation of the user on the third window, the first interface is displayed.

[0033] By adopting the above technical solution, after entering the smart device management application, the information of the devices to be added scanned by the gateway device can be actively displayed in the form of a pop-up window, so that users can quickly initiate batch addition or individual addition of the devices to be added scanned by the gateway device based on the pop-up window information.

[0034] In one possible implementation, the third window includes a second control for triggering the addition of a device, a first pattern corresponding to the gateway device, and a second pattern corresponding to the device to be added scanned by the gateway device. The fourth operation is a click operation on the second control, and the number of second patterns is associated with the number of devices to be added scanned by the gateway device.

[0035] By adopting the above technical solution, the pattern of the gateway device and the number and pattern of the devices to be added scanned by the gateway device can be displayed through the third window, so that the user can intuitively obtain the information of the devices to be added scanned by the gateway device through the third window, and the user can quickly initiate batch addition or individual addition of the devices to be added scanned by the gateway device through the second control of the third window.

[0036] In one possible implementation, in response to the user's fourth operation on the third window, the first interface is displayed, including: in response to the user's fourth operation on the third window, and the remaining connectable number of gateway devices is less than or equal to the preset number, or the remaining connectable number of gateway devices is less than the number of devices to be added scanned by the gateway device, opening the fourth window, the fourth window covering part of the content of the home page interface, the fourth window including early warning prompt information of the gateway device and a third control for triggering device addition; in response to the user's click operation on the third control, the first interface is displayed.

[0037] With the above technical solution, since the gateway device can connect to a limited number of devices, if the remaining number of connectable devices of the gateway device is less than the number of devices to be added scanned by the gateway device, it indicates that the gateway device cannot establish connections with all of these devices to be added. By opening the fourth window, the user is prompted to partially connect the devices to be added, or to replace other gateway devices to connect these devices to be added, so as to smoothly add these devices to be added. The content displayed in the fourth window may include warning prompt information on the remaining number of connectable devices of the gateway device, and the third control may be a control for triggering the addition of a partial number of devices to be added.

[0038] In a second aspect, an embodiment of the present application provides a computer-readable storage medium comprising computer instructions. When the computer instructions are executed on a terminal device, the terminal device executes the method for adding devices in batches as described in the first aspect or the second aspect.

[0039] In a third aspect, an embodiment of the present application provides a terminal device, which includes a processor and a memory, the memory being used to store instructions, and the processor being used to call instructions in the memory, so that the terminal device executes the method for batch adding devices as described in the first aspect or the second aspect.

[0040] In a fourth aspect, a device is provided, wherein the device has the function of implementing the terminal device behavior provided in the method provided in the first or second aspect. The function can be implemented through hardware or through hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0041] It can be understood that the computer-readable storage medium described in the second aspect, the terminal device described in the third aspect, and the apparatus described in the fourth aspect all correspond to the method of the first aspect. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] FIG1 is a schematic structural diagram of a terminal device provided in one embodiment of the present application;

[0043] FIG2 is a schematic diagram of a software structure of a terminal device provided in one embodiment of the present application;

[0044] FIG3 is a schematic diagram of an application environment of a method for adding devices in batches according to an embodiment of the present application;

[0045] FIG4a is a schematic diagram of a process of adding a smart home device through a gateway device according to an embodiment of the present application;

[0046] FIG4 b is a schematic diagram of a process of adding a smart home device through a terminal device according to an embodiment of the present application;

[0047] 5a to 5g are schematic diagrams of an operation flow for adding a device to a smart home device scanned by a gateway device in response to an operation to add a device, according to an embodiment of the present application;

[0048] 6a to 6f are schematic diagrams of an operation flow for adding smart home devices scanned by a gateway device in response to a manual operation of adding a specified device category, according to an embodiment of the present application;

[0049] 7a to 7e are schematic diagrams of an operation flow for adding a smart home device that is self-discovered by a terminal device through a gateway device, according to an embodiment of the present application;

[0050] 8a to 8f are schematic diagrams of an operation flow of controlling a terminal device to add a smart home device scanned by a gateway device in response to a user's operation of adding a specified device category, according to an embodiment of the present application;

[0051] FIG9 is a schematic diagram of an operation flow for adding and viewing a gateway device model according to an embodiment of the present application;

[0052] FIG10a is a schematic diagram of possible interface states of a batch device connection interface provided by an embodiment of the present application;

[0053] FIG10b is a schematic diagram of possible interface states of a connection result interface provided by an embodiment of the present application;

[0054] FIG11 is a schematic diagram of an interface of a device discovery pop-up window provided in an embodiment of the present application;

[0055] 12a to 12c are schematic diagrams of warning interfaces that may appear when adding smart home devices and the number of remaining connectable gateway devices may exceed the number provided by an embodiment of the present application;

[0056] FIG13 is a flow chart of a method for adding devices in batches according to an embodiment of the present application;

[0057] FIG14 is a schematic structural diagram of a batch adding device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0058] To facilitate understanding, some illustrations of concepts related to the embodiments of the present application are given for reference.

[0059] It should be noted that the terms "first" and "second" involved in the embodiments of the present application are only used for descriptive purposes and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, the features defined as "first" and "second" may explicitly or implicitly include one or more of such features. In the description of the embodiments of the present application, words such as "exemplary" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design scheme described as "exemplary" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or design schemes. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way.

[0060] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the art to which this application belongs. The terms used in the specification of this application are for the purpose of describing specific embodiments only and are not intended to limit this application. It should be understood that, unless otherwise specified in this application, " / " means or. For example, A / B can mean A or B. "And / or" in this application is merely a way to describe the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can mean: A exists alone, A and B exist at the same time, and B exists alone. "At least one" means one or more. "Multiple" means two or more than two. For example, at least one of a, b or c can mean: a, b, c, a and b, a and c, b and c, a, b and c.

[0061] With the development of smart home technology, the demand for smart home devices in homes and buildings is increasing. Many smart home devices need to be added to the application ecosystem after physical installation, so that users can view and manage smart home devices through smart device management applications installed on their terminal devices. Related smart device management applications cannot add smart home devices in batches, forcing users to add smart home devices one by one, which is time-consuming and labor-intensive, and may cause devices to be missed.

[0062] In order to solve the above technical problems, an embodiment of the present application provides a method for adding devices in batches, which can solve the problem that existing smart device management applications cannot add smart home devices in batches.

[0063] The smart home devices in the embodiments of the present application include but are not limited to sensors, alarms, smart lighting, smart speakers, smart cameras, smart TVs, smart washing machines, smart refrigerators, smart door locks, smart curtains, etc.

[0064] In some embodiments, the gateway device is the brain of the smart home system (a smart home system may include one or more gateway devices and multiple smart home devices). It can be used to collect instructions, convert the instructions into a language that the smart home devices can understand, and transmit them to the smart home devices to achieve control of the smart home devices. The gateway device can also serve as a transfer station for devices to connect to the network. Through the gateway device, smart home devices that cannot be directly connected to the network can be connected to the network, thereby achieving the effect of remote control. At the same time, the gateway device can also be a converter between different communication protocols, allowing smart home devices with different protocols to connect to each other. In smart home systems, the more commonly used communication protocols include Bluetooth, Zigbee, Wireless Fidelity (Wi-Fi), etc.

[0065] The method for adding devices in batches according to the embodiment of the present application can be applied to terminal devices. The terminal device can be a mobile phone, a tablet computer (portable android device, Pad), a wearable device (such as a smart watch), a control panel, etc. The terminal device can be, for example, a device equipped with Windows Or devices with other operating systems, this application does not limit this. The embodiment of this application is described by taking the terminal device as a mobile phone as an example.

[0066] The user interface (UI) in the embodiments of the present application is a medium interface for interaction and information exchange between an application or operating system and a user, which can realize the conversion between the internal form of information and the form acceptable to the user (such as a visual operating environment). The term user interface may refer to the text contained in the user interface, and the text language may be Chinese, English, Japanese, Korean, Arabic, French, Russian, German, Portuguese, etc. The user interface of an application may be a source code written in a specific computer language such as JAVA or extensible markup language (XML). The interface source code is parsed and rendered on the terminal device, and is ultimately presented as content that the user can recognize, such as pictures, text, buttons and other controls. Controls are the basic elements of the user interface. Typical controls include buttons, widgets, toolbars, menu bars, text boxes, scroll bars, images and text. The properties and contents of controls in the interface are defined by tags or nodes, such as XML through <textview> 、 <imgview> 、 <videoview>The controls contained in the interface are specified by nodes such as <head> and <body>. A node corresponds to a control or attribute in the interface, and the node is presented as user-visible content after parsing and rendering. In addition, many applications, such as hybrid applications, usually also contain web pages in their interfaces. A web page, also known as a page, can be understood as a special control embedded in the application interface. A web page is a source code written in a specific computer language, such as hypertext markup language (HTML), cascading style sheets (CSS), JAVA scripts (JavaScript, JS), etc. The web page source code can be loaded and displayed as user-recognizable content by a browser or a web page display component with similar functions to a browser. The specific content contained in a web page is also defined by tags or nodes in the web page source code, such as HTML through <body>. 、 、 <video> 、 <canvas>To define the elements and attributes of a web page. The display interface, application program interface, and other interfaces in the embodiments of the present application can all be referred to as user interfaces.

[0067] A common form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operations that uses graphics to display. It can be an icon, window, control, or other interface element displayed on the display screen of a terminal device.

[0068] In some embodiments, the terminal device can install one or more applications (Application, APP). APP can be a software program that can realize one or more specific functions. For example, a call application, a text message application, an instant chat communication application, a smart device management application (for example, Honor Smart Space), etc. The applications mentioned in the following embodiments can be applications installed on the terminal device when it leaves the factory, or they can be third-party applications downloaded from the Internet or obtained from other terminal devices while the user is using the terminal device.

[0069] FIG1 is a schematic diagram of the hardware structure of a terminal device provided in an embodiment of the present application.

[0070] As shown in Figure 1, the terminal device 100 may include a processor 110, an external memory interface 120, an internal memory 121, a universal serial bus (USB) interface 130, a charging management module 140, a power management module 141, a battery 142, an antenna 1, an antenna 2, a mobile communication module 150, a wireless communication module 160, an audio module 170, a speaker 170A, a receiver 170B, a microphone 170C, an earphone interface 170D, a sensor module 180, a button 190, a motor 191, an indicator 192, a camera 193, a display screen 194, and a subscriber identification module (SIM) card interface 195, etc. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, an ambient light sensor 180L, a bone conduction sensor 180M, etc.

[0071] It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may include more or fewer components than shown, or may combine or separate certain components, or arrange the components differently. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0072] The processor 110 may include one or more processing units. For example, the processor 110 may include an application processor (AP), a modem processor, a graphics processing unit (GPU), an image signal processor (ISP), a controller, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU). The different processing units may be independent devices or integrated into one or more processors.

[0073] The controller can generate operation control signals according to the instruction operation code and timing signal to complete the control of instruction fetching and execution.

[0074] Processor 110 may also include a memory for storing instructions and data. In some embodiments, the memory in processor 110 is a cache memory. This memory can store instructions or data that have just been used or are being recycled by processor 110. If processor 110 needs to use these instructions or data again, it can directly access them from the memory. This avoids duplicate accesses, reduces processor 110 latency, and thus improves system efficiency.

[0075] In some embodiments, the processor 110 may include one or more interfaces. The interfaces may include an inter-integrated circuit (I2C) interface, an inter-integrated circuit sound (I2S) interface, a pulse code modulation (PCM) interface, a universal asynchronous receiver / transmitter (UART) interface, a mobile industry processor interface (MIPI), a general-purpose input / output (GPIO) interface, a subscriber identity module (SIM) interface, and / or a universal serial bus (USB) interface.

[0076] The I2C interface is a bidirectional synchronous serial bus that includes a serial data line (SDA) and a serial clock line (SCL). In some embodiments, the processor 110 may include multiple I2C busses. The processor 110 may be coupled to the touch sensor 180K, charger, flash, camera 193, etc. via different I2C bus interfaces. For example, the processor 110 may be coupled to the touch sensor 180K via the I2C interface, enabling communication between the processor 110 and the touch sensor 180K via the I2C bus interface, thereby implementing the touch function of the terminal device 100.

[0077] The I2S interface can be used for audio communication. In some embodiments, the processor 110 can include multiple I2S buses. The processor 110 can be coupled to the audio module 170 via the I2S bus to enable communication between the processor 110 and the audio module 170. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the I2S interface, enabling the function of answering calls through a Bluetooth headset.

[0078] The PCM interface can also be used for audio communication, sampling, quantizing, and encoding analog signals. In some embodiments, the audio module 170 and the wireless communication module 160 can be coupled via a PCM bus interface. In some embodiments, the audio module 170 can also transmit audio signals to the wireless communication module 160 via the PCM interface, enabling the function of answering calls via a Bluetooth headset. Both the I2S interface and the PCM interface can be used for audio communication.

[0079] The UART interface is a universal serial data bus used for asynchronous communication. The bus can be a bidirectional communication bus. It converts the data to be transmitted between serial communication and parallel communication. In some embodiments, the UART interface is typically used to connect the processor 110 and the wireless communication module 160. For example, the processor 110 communicates with the Bluetooth module in the wireless communication module 160 via the UART interface to implement Bluetooth functionality. In some embodiments, the audio module 170 can transmit audio signals to the wireless communication module 160 via the UART interface, enabling the function of playing music through Bluetooth headphones.

[0080] The MIPI interface can be used to connect the processor 110 to peripheral devices such as the display screen 194 and the camera 193. MIPI interfaces include the camera serial interface (CSI) and the display serial interface (DSI). In some embodiments, the processor 110 and the camera 193 communicate via the CSI interface to implement the camera function of the terminal device 100. The processor 110 and the display screen 194 communicate via the DSI interface to implement the display function of the terminal device 100.

[0081] The GPIO interface can be configured via software. The GPIO interface can be configured as either a control signal or a data signal. In some embodiments, the GPIO interface can be used to connect the processor 110 to the camera 193, display 194, wireless communication module 160, audio module 170, sensor module 180, etc. The GPIO interface can also be configured as an I2C interface, an I2S interface, a UART interface, a MIPI interface, etc.

[0082] The USB interface 130 is an interface that complies with USB standards and may be a Mini USB interface, a Micro USB interface, a USB Type-C interface, or the like. The USB interface 130 can be used to connect a charger to charge the terminal device 100, or to transfer data between the terminal device 100 and peripheral devices. It can also be used to connect headphones to play audio. The interface can also be used to connect to other terminal devices 100, such as AR devices.

[0083] It is understood that the interface connection relationship between the modules illustrated in the embodiment of the present invention is merely an illustrative illustration and does not constitute a structural limitation on the terminal device 100. In other embodiments of the present application, the terminal device 100 may also adopt a different interface connection method from the above embodiment, or a combination of multiple interface connection methods.

[0084] The charging management module 140 is configured to receive charging input from a charger. The charger can be either a wireless charger or a wired charger. In some wired charging embodiments, the charging management module 140 can receive charging input from the wired charger via the USB interface 130. In some wireless charging embodiments, the charging management module 140 can receive wireless charging input via the wireless charging coil of the terminal device 100. While charging the battery 142, the charging management module 140 can also provide power to the terminal device 100 via the power management module 141.

[0085] The power management module 141 is used to connect the battery 142, the charging management module 140, and the processor 110. The power management module 141 receives input from the battery 142 and / or the charging management module 140, and provides power to the processor 110, the internal memory 121, the display 194, the camera 193, and the wireless communication module 160. The power management module 141 can also be used to monitor parameters such as battery capacity, battery cycle count, and battery health status (leakage, impedance). In some other embodiments, the power management module 141 can also be set in the processor 110. In other embodiments, the power management module 141 and the charging management module 140 can also be set in the same device.

[0086] The wireless communication function of the terminal device 100 can be implemented through the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modem processor and the baseband processor.

[0087] Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in terminal device 100 can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, antenna 1 can be reused as a diversity antenna for a wireless local area network. In other embodiments, the antennas can be used in conjunction with a tuning switch.

[0088] The mobile communication module 150 can provide solutions for wireless communications including 2G / 3G / 4G / 5G applied to the terminal device 100. The mobile communication module 150 may include at least one filter, a switch, a power amplifier, a low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, and filter, amplify, and process the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and convert it into electromagnetic waves for radiation through the antenna 1. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the processor 110. In some embodiments, at least some of the functional modules of the mobile communication module 150 can be set in the same device as at least some of the modules of the processor 110.

[0089] The modem processor may include a modulator and a demodulator. The modulator is used to modulate the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used to demodulate 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 being processed by the baseband processor, the low-frequency baseband signal is passed to the application processor. The application processor outputs a sound signal through an audio device (not limited to the speaker 170A, the receiver 170B, etc.) or displays an image or video through the display screen 194. In some embodiments, the modem processor may be an independent device. In other embodiments, the modem processor may be independent of the processor 110 and be set in the same device as the mobile communication module 150 or other functional modules.

[0090] The wireless communication module 160 can provide wireless communication solutions including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), Bluetooth (BT), global navigation satellite system (GNSS), frequency modulation (FM), near field communication (NFC), infrared (IR), etc., which are applied to the terminal device 100. The wireless communication module 160 can be one or more devices that integrate at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2, frequency modulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signal to be sent from the processor 110, frequency modulate it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2.

[0091] In some embodiments, the antenna 1 of the terminal device 100 is coupled to the mobile communication module 150, and the antenna 2 is coupled to the wireless communication module 160, so that the terminal device 100 can communicate with other devices through wireless communication technology and the operator's mobile communication network. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), wideband code division multiple access (WCDMA), time-division code division multiple access (TD-SCDMA), long term evolution (LTE), BT, GNSS, WLAN, NFC, FM, and / or IR technology. The GNSS may include a global positioning system (GPS), a global navigation satellite system (GLONASS), a Beidou navigation satellite system (BDS), a quasi-zenith satellite system (QZSS) and / or a satellite based augmentation system (SBAS).

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

[0093] The display screen 194 is used to display images, videos, etc. The display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (AMOLED), a flexible light-emitting diode (FLED), Miniled, MicroLed, Micro-oled, a quantum dot light-emitting diode (QLED), etc. In some embodiments, the terminal device 100 may include one or N display screens 194, where N is a positive integer greater than 1. Among them, the display screen 194 in the embodiment of the present application can be a touch screen. That is, the touch sensor 180K is integrated into the display screen 194.

[0094] The digital signal processor is used to process digital signals. In addition to processing digital image signals, it can also process other digital signals. For example, when the terminal device 100 selects a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0095] Video codecs are used to compress or decompress digital video. Terminal device 100 may support one or more video codecs. This allows terminal device 100 to play or record videos in various encoding formats, such as Moving Picture Experts Group (MPEG) 1, MPEG2, MPEG3, and MPEG4.

[0096] The NPU is a neural network (NN) computing processor. Drawing on the structure of biological neural networks, such as the transmission patterns between neurons in the human brain, it rapidly processes input information and can continuously self-learn. The NPU can enable intelligent cognitive applications in the terminal device 100, such as image recognition, face recognition, speech recognition, and text comprehension.

[0097] The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

[0098] Random access memory may include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM, for example, the fifth generation of DDR SDRAM is generally referred to as DDR5 SDRAM), etc.

[0099] Non-volatile memory may include disk storage devices and flash memory.

[0100] Flash memory can be divided into NOR FLASH, NAND FLASH, 3D NAND FLASH according to the operating principle, single-level cell (SLC), multi-level cell (MLC), triple-level cell (TLC), quad-level cell (QLC) according to the storage cell potential level, and universal flash storage (UFS) and embedded multi-media card (eMMC) according to the storage specification.

[0101] The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (such as machine instructions) of the operating system or other running programs, and can also be used to store user and application data.

[0102] The non-volatile memory may also store executable programs and user and application data, etc., and may be loaded into the random access memory in advance for direct reading and writing by the processor 110 .

[0103] The external memory interface 120 can be used to connect to an external non-volatile memory to expand the storage capacity of the terminal device 100. The external non-volatile memory communicates with the processor 110 via the external memory interface 120 to implement data storage. For example, files such as music and videos can be stored in the external non-volatile memory.

[0104] The buttons 190 include a power button, a volume button, etc. The buttons 190 may be mechanical buttons or touch buttons. The terminal device 100 may receive key inputs and generate key signal inputs related to user settings and function control of the terminal device 100.

[0105] Motor 191 can generate vibration prompts. Motor 191 can be used for incoming call vibration prompts, and can also be used for touch vibration feedback. For example, touch operations acting on different applications (such as taking pictures, audio playback, etc.) can correspond to different vibration feedback effects. For touch operations acting on different areas of the display screen 194, motor 191 can also correspond to different vibration feedback effects. Different application scenarios (for example: time reminders, receiving messages, alarm clocks, games, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect can also support customization.

[0106] The indicator 192 may be an indicator light, which may be used to indicate the charging status, power level changes, messages, missed calls, notifications, etc.

[0107] The SIM card interface 195 is used to connect a SIM card. The SIM card can be connected to and disconnected from the terminal device 100 by inserting or removing it from the SIM card interface 195. The terminal device 100 can support one or N SIM card interfaces, where N is a positive integer greater than one. The SIM card interface 195 can support Nano SIM cards, Micro SIM cards, SIM cards, and the like. Multiple cards can be inserted into the same SIM card interface 195 simultaneously. The multiple cards can be of the same or different types. The SIM card interface 195 can also be compatible with different types of SIM cards. The SIM card interface 195 can also be compatible with external memory cards. The terminal device 100 interacts with the network through the SIM card to implement functions such as calls and data communications. In some embodiments, the terminal device 100 uses an eSIM, i.e., an embedded SIM card. The eSIM card can be embedded in the terminal device 100 and cannot be separated from the terminal device 100.

[0108] The software system of the terminal device 100 can adopt a layered architecture, an event-driven architecture, a micro-kernel architecture, a micro-service architecture, or a cloud architecture. In the embodiment of the present application, the Android system with a layered architecture is used as an example to illustrate the software structure of the terminal device 100.

[0109] FIG2 is a block diagram of the software structure of the terminal device according to an embodiment of the present application.

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

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

[0112] As shown in FIG2 , the application package may include applications such as battery management, camera, gallery, calendar, call, map, navigation, music, video, and short message.

[0113] The application framework layer provides an application programming interface (API) and programming framework for applications in the application layer. The application framework layer includes some predefined functions.

[0114] As shown in FIG2 , the application framework layer may include a window manager, an input manager, a sensor manager, a telephony manager, a resource manager, a notification manager, and the like.

[0115] The input manager can be used to monitor user input events, such as click events and sliding events performed by the user's finger on the display screen 193 of the terminal device 100. By monitoring the input events, the terminal device 100 can determine whether the terminal device is being used.

[0116] The sensor manager is used to monitor the data returned by various sensors in the terminal device, such as motion sensor data, proximity sensor data, temperature sensor data, etc. Using the data returned by each sensor, the terminal device can determine whether it is shaking or whether the display screen 193 is blocked.

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

[0118] The core library consists of two parts: one is the function that needs to be called by the Java language, and the other is the Android core library.

[0119] The application layer and application framework layer run in a virtual machine. The virtual machine executes Java files in the application layer and application framework layer as binary files. The virtual machine manages object lifecycles, stack management, thread management, security and exception management, and garbage collection.

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

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

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

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

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

[0125] The kernel layer is the layer between the hardware (hardware layer) and the software. The kernel layer contains at least the display driver, camera driver, audio driver, and sensor driver. The hardware layer can include the display, camera, sensors, etc.

[0126] As shown in Figure 3, the terminal device 100 (for example, a mobile phone) establishes a connection with the gateway device 200. The terminal device 100 is installed with a smart device management application. The server corresponding to the smart device management application is server 300. Server 300 can be a cloud server, or other types of servers or server clusters. This embodiment of the present application does not limit this.

[0127] The user can log in to the smart device management application installed on the terminal device 100 to control the gateway device 200 to register multiple smart home devices 400 on the server 300 at one time, so that the user can subsequently manage these smart home devices 400 through the smart device management application.

[0128] For example, multiple smart home devices 400 are in network distribution mode, and the gateway device 200 can scan the multiple smart home devices 400. When the user initiates an add request for the multiple smart home devices 400 through the smart device management application installed on the terminal device 100, the terminal device 100 can apply to the server 300 for registration information corresponding to each smart home device 400. The registration information may include a registration code and an activation code. After the terminal device 100 receives the multiple registration information returned by the server 300, it sends the multiple registration information to the gateway device 200. After establishing a connection with the multiple smart home devices 400, the gateway device 200 can initiate a registration request to the server 300 based on the registration information corresponding to each smart home device 400. The server 300 registers each smart home device 400 based on the multiple registration information sent by the gateway device 200, and returns the registration result to the gateway device 200. After these smart home devices 400 are successfully registered on the server 300, the user can manage these smart home devices 400 through the smart device management application.

[0129] In some embodiments, the terminal device 100 can also query the registration progress of these smart home devices 400 from the server 300 in real time, and query the connection progress of these smart home devices 400 from the gateway device 200, and then display the addition progress and results of each smart home device 400 in real time on the smart device management application.

[0130] Referring to FIG4a , the process of adding smart home devices through a gateway device is described. The smart home devices to be added may be devices scanned and discovered by the gateway device. In one possible implementation, the smart home devices to be added may be smart home devices scanned by the gateway device in response to an operation to add a device. In this case, the gateway device may scan smart home devices of one or more device categories. In another possible implementation, the smart home devices to be added may also be smart home devices scanned by the gateway device in response to an operation to add a specified device category (the operation to add a specified device category may also be referred to as the operation to manually add a specified device category). In this case, the gateway device scans smart home devices of the same device category.

[0131] For smart home devices scanned in response to the device addition operation, the following process can be used to add the smart home device. Adding the smart home device in the embodiment of the present application may refer to establishing a connection between the smart home device and the gateway device and registering the smart home device on the server, so that the user can subsequently manage the smart home device through the smart device management application:

[0132] (1) When the number of smart home devices scanned by the gateway device is greater than or equal to two, the smart home devices can be added in batches or individually.

[0133] In some embodiments, smart home devices can be categorized into multiple device categories based on their functionality. For example, smart home devices may include the following device categories: human sensors, door and window sensors, smoke sensors, downlights, spotlights, washing machines, refrigerators, air conditioners, and so on. The gateway device responds to the device addition operation, and the scanned smart home devices may include one or more device categories.

[0134] In some embodiments, smart home devices may be further divided into two types according to whether device connection authentication is required: first type smart home devices and second type smart home devices.

[0135] The first type of smart home device is a smart home device that requires device connection authentication on the device side, that is, when the gateway device connects to the first type of smart home device, the user is required to perform a specified confirmation operation on the smart home device side to complete the device connection authentication. Different smart home devices may have different confirmation operations, and the embodiments of the present application are not limited to this. The second type of smart home device is a smart home device that does not require device connection authentication on the device side, that is, when the gateway device connects to the second type of smart home device, the user is not required to perform a confirmation operation on the smart home device side. The first type of smart home device is generally a smart home device with a strong privacy, for example, a smart home device with a shooting function, a sound collection function or other strong privacy functions, such as a smart camera, a smart screen, a smart door lock, etc., and the device connection authentication requirement can be set before the device leaves the factory.

[0136] For the second type of smart home devices that do not require device connection authentication, batch addition or individual addition is supported. For the first type of smart home devices that require device connection authentication, batch addition is not supported, that is, only individual addition is supported.

[0137] In other embodiments, unified authentication or authorization management may be performed on the first type of smart home devices, and batch addition may be implemented after the authentication or authorization is passed.

[0138] In some embodiments, for multiple scanned smart home devices of the second type, multiple smart home devices can be added using a batch adding method in response to a user's operation of selecting multiple devices in batches, or smart home devices can be added using an individual adding method in response to a user's operation of selecting a single device.

[0139] In some embodiments, for smart home devices to be networked, after the smart home devices are powered on, the smart home devices may be in network configuration mode. In network configuration mode, the smart home devices may broadcast discovery requests, and then the gateway device may scan the smart home devices to be networked. The discovery requests broadcast by the smart home devices may include device identification information.

[0140] In some embodiments, after the smart home device completes the connection and registration with the gateway device, it can exit the network configuration mode and enter the normal working mode. In the normal working mode, the smart home device will not broadcast the discovery request.

[0141] (2) For multiple second-type smart home devices selected in batches, after obtaining legal authorization for connection of each smart home device, the gateway device can connect to the multiple second-type smart home devices and initiate batch registration to the server, and display the addition results of each smart home device selected in batches.

[0142] In some embodiments, the legal authorization for connecting a smart home device may refer to the user accepting the user agreement and privacy statement for connecting the smart home device.

[0143] The result of adding a smart home device can include a successful addition or a failed addition. A successful addition can mean that the smart home device has established a communication connection with the gateway device and the smart home device has successfully registered on the server. A failed addition can mean that the smart home device has not successfully established a communication connection with the gateway device or that the smart home device has failed to register on the server.

[0144] (3) For a selected single smart home device of the second type, after obtaining legal authorization for connection of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0145] (4) For a selected single smart home device of the first type, after obtaining the connection legal authorization and authentication verification information of the smart home device, the gateway device connects to the smart home device and initiates registration with the server, and displays the addition result of the smart home device.

[0146] In some embodiments, for a first type of smart home device, after initiating a connection request to the first type of smart home device, the user can perform an authentication and verification operation on the smart home device side. The smart home device can send authentication and verification information to the gateway device in response to the user's authentication and verification operation (for example, pressing a button on the smart home device, or clicking an icon on the display screen of the smart home device, etc.). After receiving the authentication and verification information sent by the smart home device, the gateway device can connect to the smart home device and initiate registration with the server after establishing the connection.

[0147] (5) When the number of smart home devices scanned by the gateway device is one, a separate adding method is adopted.

[0148] (6) If the smart home device is a first type of smart home device, after obtaining the connection legal authorization and authentication verification information of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0149] (7) If the smart home device is a second type of smart home device, after obtaining legal authorization for connection with the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0150] For smart home devices that are scanned in response to the manual addition of a specified device category, the following process can be used to add smart home devices:

[0151] (i) In response to the user clicking on the first manually added control, a device category list of smart home devices is displayed.

[0152] In some embodiments, the device category list may include smart home devices of multiple device categories, for example, it may include human body sensors, door and window sensors, smoke sensors, downlights, spotlights, etc.

[0153] (ii) In response to the user clicking on a device category in the device category list, a configuration wizard for the device category is displayed, so that the user can configure the smart home device of the corresponding device category based on the configuration wizard, so that the smart home device can be scanned and discovered by the gateway device.

[0154] In some embodiments, a configuration wizard may include configuration instructions for the smart home devices corresponding to the device category. Based on the configuration wizard, the user can operate the corresponding smart home devices to put them into network configuration mode, thereby enabling them to be scanned and discovered by the gateway device. For example, the configuration wizard may include instructions such as "Make sure XX is turned on and has sufficient power," "Make sure XX is turned on and connected to a power source," or "Make sure XX is turned on and connected to a power source. After the YY light turns on, press the ZZ key / button."

[0155] (iii) When the number of smart home devices scanned by the gateway device is greater than or equal to two, the smart home devices can be added in batches or individually.

[0156] (iv) For multiple smart home devices of the same device category selected in batches, and these smart home devices are second-type smart home devices, after obtaining legal authorization for connection of each smart home device, the gateway device can connect to the multiple smart home devices of the same device category and initiate batch registration to the server, and display the addition results of each smart home device selected in batches.

[0157] (v) For a single smart home device selected from multiple smart home devices of the same device category, and the smart home device is a second type of smart home device, after obtaining legal authorization for connection of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0158] (vi) For a single smart home device selected from multiple smart home devices of the same device category, and the smart home device is a first type of smart home device, after obtaining the connection legal authorization and authentication verification information of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0159] (vii) When the number of smart home devices scanned by the gateway device is one, a separate adding method is adopted.

[0160] (viii) If the smart home device is a first type of smart home device, after obtaining the connection legal authorization and authentication verification information of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0161] (ix) If the smart home device is a second type of smart home device, after obtaining legal authorization for connection with the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0162] 4b, the process of adding smart home devices through a terminal device (e.g., a mobile phone) is introduced. The smart home devices to be added can be smart home devices that are self-discovered by the terminal device through the gateway device, or they can be smart home devices that are scanned by the gateway device in response to the user's operation of adding a specified device category.

[0163] For smart home devices that are discovered by the terminal device through the gateway device, you can add smart home devices through the following process:

[0164] (1) When the number of smart home devices discovered by the terminal device through the gateway device is greater than or equal to two, the smart home devices can be added in batches or individually.

[0165] In some embodiments, the process of terminal devices self-discovering smart home devices through gateway devices may include: after the gateway device scans the smart home devices to be networked, it can push the discovery information of the smart home devices to the terminal devices connected to it; after receiving the discovery information pushed by the gateway device, the terminal device can display the information of the smart home devices to be networked discovered by the gateway device in the form of a pop-up window, so as to add smart home devices in response to user operations.

[0166] (2) For multiple second-type smart home devices selected in batches, after obtaining legal authorization for connection of each smart home device, the gateway device can connect to the multiple second-type smart home devices and initiate batch registration to the server, and display the addition results of each smart home device selected in batches.

[0167] (3) For a selected single smart home device of the second type, after obtaining legal authorization for connection of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0168] (4) For a selected single smart home device of the first type, after obtaining the connection legal authorization and authentication verification information of the smart home device, the gateway device connects to the smart home device and initiates registration with the server, and displays the addition result of the smart home device.

[0169] (5) When the number of smart home devices discovered by the terminal device through the gateway device is one, a separate adding method is adopted.

[0170] (6) If the smart home device is a first type of smart home device, after obtaining the connection legal authorization and authentication verification information of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0171] (7) If the smart home device is a second type of smart home device, after obtaining legal authorization for connection with the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0172] For smart home devices scanned in response to a user's operation to add a specified device category, the following process can be used to add smart home devices:

[0173] (i) In response to the user clicking on the second manual adding control, a device category list of smart home devices is displayed.

[0174] (ii) In response to the user clicking on a device category in the device category list, selecting a gateway device corresponding to the device category, or adding a gateway device corresponding to the device category, a configuration wizard for the device category is displayed, so that the user configures the smart home device of the corresponding device category based on the configuration wizard, so that the smart home device can be scanned and discovered by the gateway device.

[0175] In some embodiments, smart home devices based on different communication protocols may need to connect to different gateway devices. For example, for smart home devices that only support the ZigBee communication protocol, the corresponding connection is a gateway that supports the ZigBee communication protocol. For smart home devices that only support the Wi-Fi communication protocol, the corresponding connection is a gateway that supports the Wi-Fi communication protocol. For smart home devices that only support the Bluetooth low energy (BLE) communication protocol, the corresponding connection is a gateway that supports the BLE communication protocol. For smart home devices that only support the power line communication (PLC) protocol, the corresponding connection is a gateway that supports the PLC communication protocol. The PLC implementation mechanism is to modulate the IoT device data to be transmitted into a high-frequency signal and transmit it on the power line. For gateways that support both the PLC communication protocol and the BLE communication protocol, they can be connected to smart home devices that support the BLE communication protocol and smart home devices that support the PLC communication protocol.

[0176] In some embodiments, the number of smart home devices that can be connected to the gateway device has an upper limit. When selecting a gateway device, it is also necessary to ensure that the number of smart home devices to be connected does not exceed the remaining number of smart home devices that can be connected to the gateway device.

[0177] In some embodiments, after the user clicks a device category in the device category list, the user needs to first specify a gateway device corresponding to the device category, that is, specify which gateway device to establish a connection with.

[0178] If the gateway device that the user desires to designate has currently established a connection with the terminal device, a gateway device corresponding to the device category may be selected in response to the user's gateway selection operation.

[0179] If the gateway device that the user wishes to specify is not currently connected to the terminal device, the user needs to manually add the gateway device. Specifically, the terminal device can respond to the user's gateway addition operation by scanning for gateway devices to connect to. After the terminal device establishes a connection with the scanned gateway device, the user can use the added gateway device as the gateway device corresponding to the device category.

[0180] After completing the selection of the gateway device, a configuration wizard of the device category may be displayed, so that the user can configure the smart home devices of the corresponding device category based on the configuration wizard, so that the smart home devices can be scanned and discovered by the gateway device.

[0181] (iii) When the number of smart home devices scanned by the gateway device is greater than or equal to two, the smart home devices can be added in batches or individually.

[0182] (iv) For multiple smart home devices of the same device category selected in batches, and these smart home devices are second-type smart home devices, after obtaining legal authorization for connection of each smart home device, the gateway device can connect to the multiple smart home devices of the same device category and initiate batch registration to the server, and display the addition results of each smart home device selected in batches.

[0183] (v) For a single smart home device selected from multiple smart home devices of the same device category, and the smart home device is a second type of smart home device, after obtaining legal authorization for connection of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0184] (vi) For a single smart home device selected from multiple smart home devices of the same device category, and the smart home device is a first type of smart home device, after obtaining the connection legal authorization and authentication verification information of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0185] (vii) When the number of smart home devices scanned by the gateway device is one, a separate adding method is adopted.

[0186] (viii) If the smart home device is a first type of smart home device, after obtaining the connection legal authorization and authentication verification information of the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0187] (ix) If the smart home device is a second type of smart home device, after obtaining legal authorization for connection with the smart home device, the gateway device can connect to the smart home device and initiate registration with the server, and display the addition result of the smart home device.

[0188] The following uses the "Honor Smart Space" smart device management application as an example to explain in detail how to add devices individually and in batches.

[0189] 5a-5g, a schematic diagram of an operation flow for adding a device to a smart home device scanned by a gateway device in response to an operation of adding a device is described in detail below.

[0190] As shown in Figure 5a (a), the terminal device may be installed with a smart device management application. Users can use this application to manage various smart home devices online and view the operating status of each smart home device. In Figure 5a (a), the "Honor Smart Space" application is used as an example of a smart device management application.

[0191] Users can click the "Honor Smart Space" app icon 21 on the desktop to access the Smart Space homepage interface 22, as shown in Figure 5a(b). If a terminal device currently has a communication connection with a gateway device, a gateway management card 23 corresponding to the gateway device will be displayed in the Smart Space homepage interface 22, as shown in Figure 5a(b).

[0192] Assuming the terminal device is currently connected to a first gateway, the smart space homepage interface 22 shown in FIG5a(b) may display a gateway management card corresponding to the first gateway. If the terminal device is also currently connected to a second gateway, the smart space homepage interface 22 shown in FIG5a(b) may also display a gateway management card corresponding to the second gateway. Multiple gateway management cards may be presented in parallel or partially overlapping manners, for example, for illustrative purposes only and are not intended to be limiting in actual applications.

[0193] The user can click on the gateway management card 23 to enter the gateway details interface 24 of the first gateway as shown in FIG5b(a). The gateway details interface 24 shown in FIG5b(a) includes a "Sub-Device List" control and an "Add Sub-Device" control. The user can click on the "Sub-Device List" control or the "Add Sub-Device" control to enter the gateway scanning interface 25 shown in FIG5b(c). For example, the user can click on the "Sub-Device List" control to enter the sub-device list interface shown in FIG5b(b), and then click on a preset control with a device adding function in the sub-device list interface, such as the "+" control ac1 shown in FIG5b(b), to enter the gateway scanning interface 25 shown in FIG5b(c). Alternatively, the user can click on the "Add Sub-Device" control (e.g., the "Add Sub-Device" control shown in FIG5b(a)) to directly enter the gateway scanning interface 25 shown in FIG5b(c).

[0194] The sub-device list interface shown in (b) of Figure 5b may include one or more device categories of smart home devices, and the device categories displayed on the sub-device list interface may be the device categories of the smart home devices currently connected to the first gateway. For example, the device categories displayed on the sub-device list interface may be classified according to different communication protocols, and each communication protocol may include one or more device categories. For example, the sub-device list interface shown in (b) of Figure 5b includes two categories: BLE sub-devices and PLC sub-devices. The device categories of the BLE sub-devices currently connected to the first gateway include "human body sensor", "door and window sensor", "humidifier", "electric curtain" and "three-button switch". The device categories of the PLC sub-devices currently connected to the first gateway include "electric curtain" and "three-button switch".

[0195] The gateway scanning interface 25 shown in (c) of Figure 5b includes a gateway scanning animation, a scanning prompt 251, a "Manual Add" control 252, and a "Batch Connect" control 253. The gateway scanning animation can be a scanning pattern 254 in the form of a circle, ring, arc, or sector, rotating around a vertex a predetermined number of degrees (e.g., 360 degrees) during the scanning process. The scanning prompt 251 provides users with instructions on how to ensure the gateway can scan their device. For example, the scanning prompt 251 may include: "The gateway is scanning. Please ensure that the child device is powered on and located near the gateway."

[0196] The “manual add” control 252 is used to manually add smart home devices of the same device category. The function of the “manual add” control 252 will be described in detail in Figures 6a to 6f.

[0197] The "Batch Connect" control 253 is used to batch add smart home devices of one or more device categories. When the first gateway scans two or more smart home devices that can be added in batches, the "Batch Connect" control 253 becomes available. For example, the "Batch Connect" control 253 changes from gray to a preset color, such as blue, indicating that the user can click on it. Otherwise, if the "Batch Connect" control 253 is unavailable, it is grayed out and cannot be clicked by the user.

[0198] In one embodiment, the smart home devices that can be added in batches are the second type of smart home devices, that is, smart home devices that do not require device connection authentication.

[0199] In some embodiments, if the first gateway fails to scan any addable smart home devices (first type or second type smart home devices) after scanning for a first preset time, the gateway scanning interface 25 shown in (c) of FIG. 5b may be changed to the gateway scanning failure interface shown in (d) of FIG. 5b . The first preset time can be set according to actual needs and is not limited to this in the embodiment of the present application. For example, the first preset time is 60s. The gateway scanning failure interface may include a scanning failure prompt message and a "Rescan" control 26. For example, the scanning failure prompt message may include: "No sub-device was scanned" and "Please ensure that the sub-device is turned on and is near the gateway and try again." After the user clicks the "Rescan" control 26, the first gateway may scan again and may jump to the gateway scanning interface 25 shown in (c) of FIG. 5b again.

[0200] In some embodiments, if the first gateway scans an addable smart home device within a first preset time, the gateway scanning interface 25 shown in (c) of FIG. 5b may be changed to the gateway scanning result interface shown in (a) of FIG. 5c. The gateway scanning result interface shown in (a) of FIG. 5c is substantially identical to the gateway scanning interface 25 shown in (c) of FIG. 5b, except that the gateway scanning result interface further includes a scanning result display area 27, which is located below the scanning prompt information 251. The scanning result display area 27 may display the smart home devices scanned by the first gateway (the displayed content may include the name and image of the scanned smart home device). The display rules of the scanning result display area 27 may be: smart home devices of different device categories are displayed in a tiled manner, and smart home devices of the same device category are displayed in a stacked manner. The stacking manner may be to display the number of smart home devices of the same device category using superscript numbers, which may be located next to the name or image of the smart home device.

[0201] In some embodiments, the scanning prompt information 251 in the gateway scanning result interface shown in (a) in Figure 5c can also change from "The gateway is scanning, please ensure that the sub-device is turned on and located near the gateway" to "XX gateway scanned N devices" after the gateway scan is completed.

[0202] The user can add smart home devices individually by clicking on a smart home device in the scan result display area 27 shown in (a) of FIG5c. For example, when the user clicks on a smart home device in the scan result display area 27, the device individual addition interface shown in (b) of FIG5c may be displayed. The device individual addition interface displays a legal authorization prompt box 28 corresponding to the smart home device. The legal authorization prompt box 28 includes the name of the smart home device, legal authorization information, a "Cancel" control, and an "Agree" control. The legal authorization information may include: "To use the services of this device, you must read and agree to the User Agreement and Privacy Statement." The user can click on the User Agreement in the legal authorization information to view the specific content of the User Agreement, and click on the Privacy Statement in the legal authorization information to view the specific content of the Privacy Statement.

[0203] If the user clicks the "Cancel" control, indicating that they do not agree to the User Agreement and Privacy Statement, the legal authorization prompt box 28 disappears, and the interface display returns to the gateway scan result interface shown in Figure 5c (a), indicating that the smart home device cannot be added. If the user clicks the "Agree" control, indicating that they agree to the User Agreement and Privacy Statement, thus obtaining legal authorization to connect the smart home device, the device individual addition interface shown in Figure 5c (b) will be displayed, and the device connection interface 29 shown in Figure 5d (a) will be displayed.

[0204] The device connection interface 29 shown in (a) of FIG5d includes a device connection progress 291 and a connection prompt 292. The device connection progress 291 may be displayed as a percentage, and the connection prompt 292 may include: "Device connecting..." and "Please ensure that the gateway is close to the device and the wireless network is unobstructed."

[0205] If the smart home device is a second type of smart home device, and the first gateway establishes a connection with the smart home device, and the first gateway successfully registers the smart home device on the server, the device connection interface 29 shown in (a) of Figure 5d can be changed to the connection success interface shown in (b) of Figure 5d.

[0206] If the smart home device is a first type smart home device, since the smart home device requires device connection authentication, when the device connection progress reaches a preset progress, the device connection interface 29 shown in (a) of FIG. 5d may be changed to the device verification interface shown in (c) of FIG. 5d. The preset progress can be set according to actual needs and is not limited in this embodiment of the present application. For example, the preset progress is 50%. The device verification interface shown in (c) of FIG. 5d includes a device authentication countdown (x seconds) and a device authentication operation guide. The device authentication countdown prompts the user to complete the device authentication operation before the countdown ends. The user can authenticate the smart home device based on the device authentication operation guide to indicate that the user agrees to connect the smart home device to the first gateway. The content of the device authentication operation guide can be set according to the authentication operation required by the smart home device and is not limited in this embodiment of the present application. For example, the content of the device authentication operation guide may include: "After the device's X-color light turns on, press and hold the configuration button for X seconds to complete the binding." When the user successfully authenticates the smart home device, if the first gateway establishes a connection with the smart home device and the first gateway successfully registers the smart home device on the server, the device verification interface shown in (c) of Figure 5d may be changed to the connection success interface shown in (b) of Figure 5d.

[0207] In some embodiments, if the smart home device is a second type of smart home device and the first gateway fails to connect to the smart home device, or the smart home device fails to register on the server, the device connection interface 29 shown in (a) of FIG. 5d may be changed to the connection failure interface shown in (d) of FIG. 5d. The connection failure interface shown in (d) of FIG. 5d may include a connection failure prompt message and a "Reconnect" control 30. For example, the connection failure prompt message may include: "Connection failed" and "Please ensure that the gateway is close to the device and the wireless network is unobstructed and try again." After the user clicks the "Reconnect" control 30, the first gateway may retry connecting to the smart home device and initiating registration with the server, and may again jump to the device connection interface 29 shown in (a) of FIG. 5d.

[0208] If the smart home device is a first type of smart home device, and the first gateway fails to connect to the smart home device, or the smart home device fails to be authenticated, or the smart home device fails to register on the server, the device connection interface 29 shown in (a) of Figure 5d can be changed to the connection failure interface shown in (d) of Figure 5d, or the device verification interface shown in (c) of Figure 5d can be changed to the connection failure interface shown in (d) of Figure 5d.

[0209] In some embodiments, after the second preset time of the successful connection interface shown in (b) of Figure 5d is displayed, the device settings interface shown in (a) of Figure 5e may be automatically displayed. The second preset time can be set according to actual needs and is not limited in this embodiment of the present application. For example, the second preset time may be 3 seconds.

[0210] The device settings interface shown in (a) of FIG5e can be used to set the name of the smart home device and the room it belongs to in response to user operation. When setting the room to which the smart home device belongs, the user can select from existing room options (for example, "Living Room" and "Master Bedroom" as shown in (a) of FIG5e), or can use the "Add Room" control to add a new room option and set it as the room to which the smart home device belongs.

[0211] The device setting interface shown in (a) of Figure 5e also includes a "Done" control. After the user completes the setting of the device name and the room to which it belongs, he can click the "Done" control to jump to the sub-device list interface shown in (b) of Figure 5e to display the device categories of the smart home devices that the first gateway is currently connected to and successfully registered.

[0212] The content of the sub-device list interface shown in (b) in Figure 5e is basically the same as that of the sub-device list interface shown in (b) in Figure 5b. The difference is that if the device category of the smart home device that has just been added does not exist in the sub-device list interface shown in (b) in Figure 5b, the device category displayed in the sub-device list interface shown in (b) in Figure 5b can be updated according to the device category of the smart home device that has just been added, and the sub-device list interface shown in (b) in Figure 5e is obtained.

[0213] In some embodiments, the user can also add smart home devices in batches by clicking the "batch connection" control 253 shown in (a) of Figure 5c.

[0214] Specifically, when the user clicks the "Batch Connection" control 253 in the gateway scan result interface shown in FIG5f(a), the user is redirected to the batch device selection interface 31 shown in FIG5f(b). The gateway scan result interface shown in FIG5f(a) is substantially the same as the gateway scan result interface shown in FIG5c(a), and will not be further described in this embodiment of the present application.

[0215] The batch device selection interface 31 shown in (b) of Figure 5f may include an "Allow Batch Connection" control 311, a first device display area 312 for devices that can be connected in batches, a second device display area 313 for devices that cannot be connected in batches, and an "Agree and Connect" control 314. The first device display area 312 contains devices that support batch addition, while the second device display area 313 contains devices that do not support batch addition.

[0216] In some embodiments, the device display rules of the first device display area 312 and the second device display area 313 can be: smart home devices of different device categories are displayed using separate cards, multiple smart home devices of the same device category share one card, and the product serial number (SN) of each smart home device is displayed in the card.

[0217] In some embodiments, when a device is checked in the first device display area 312, the "Agree and Connect" control 314 is in an available state (clickable by the user) and indicates that the user agrees to the legal authorization to connect the checked device. When no device is checked in the first device display area 312, the "Agree and Connect" control 314 is in an unavailable state (the "Agree and Connect" control 314 is grayed out and cannot be clicked by the user). The user can toggle the switch state by clicking the "Allow Bulk Connection" control 311. For example, when the "Allow Bulk Connection" control 311 is in the on state (the color of the "Allow Bulk Connection" control 311 is a preset color, such as blue), the user clicks the "Allow Bulk Connection" control 311, and the "Allow Bulk Connection" control 311 turns gray, indicating that the "Allow Bulk Connection" control 311 is in the off state; if the user clicks the "Allow Bulk Connection" control 311 again, the "Allow Bulk Connection" control 311 can turn blue again, indicating that the "Allow Bulk Connection" control 311 is in the on state.

[0218] If the "Allow Batch Connections" control 311 is turned on, it indicates that batch addition of devices in the first device display area 312 is allowed. For the first device display area 312, the user can select each device one by one, or click the "Select All" control to select all devices in the first device display area 312.

[0219] When all devices in the first device display area 312 are checked, the "select all" control may be changed to a "deselect all" control.

[0220] After completing the selection of multiple devices in the first device display area 312, the user can click the "Agree and Connect" control 314 to initiate batch addition of the multiple selected devices, and can jump from the batch selection device interface 31 shown in (b) of Figure 5f to display the batch device connection interface 32 shown in (c) of Figure 5f.

[0221] The batch device connection interface 32 shown in (c) of Figure 5f includes a total connection progress 321, a connection prompt message 322, and a connection progress 323 of each device. For example, if the number of devices added in a batch is 6, the total connection progress 321 is the total connection progress of the 6 devices, and the total connection progress 321 can be displayed as a percentage. The connection prompt message 322 may include: "X devices are connecting..." and "Please make sure the gateway is close to the device and the wireless network is unobstructed." The connection progress 323 of each device can be displayed using a circular progress bar (for example, filling a circle of the gray circle with blue clockwise from the zero point of the gray circle).

[0222] After each selected device completes the connection action (the result is connection success or connection failure), the batch device connection interface 32 shown in (c) of Figure 5f can be jumped to the connection result interface 33 shown in (a) of Figure 5g.

[0223] As shown in (d) of Figure 5f, when the "Allow Batch Connection" control 311 is in the off state, the first device display area 312 and the second device display area 313 can be integrated into a device display area to display all currently unadded devices (i.e., the device display area does not distinguish between devices that support batch addition and those that do not support batch addition). For example, when a user clicks the "Allow Batch Connection" control 311 in the batch device selection interface 31 shown in (b) of Figure 5f, the "Allow Batch Connection" control 311 is turned off, and the display can jump to the batch device selection interface 31 shown in (d) of Figure 5f.

[0224] In the batch device selection interface 31 shown in FIG5f(d), the user can add devices one by one. For example, by clicking the "Connect" control to the right of a device name in FIG5f(d), the batch device selection interface 31 shown in FIG5f(d) will jump to the device connection interface 29 shown in FIG5d(a).

[0225] The connection result interface 33 shown in (a) of Figure 5g includes a successful connection display area 331, a failed connection display area 332, and a "Done" control 333. The successful connection display area 331 displays devices that have successfully connected (established a connection with the gateway and successfully registered with the server), while the failed connection display area 332 displays devices that have failed to connect (failed to establish a connection with the gateway or failed to complete registration with the server) and the reasons for the failure. For example, the reasons for failure may include: the distance between the smart home device and the gateway is too far, the smart device management application version is too low, etc.

[0226] If there are devices that fail to connect during the batch addition process, the connection result interface 33 may also include prompts for solutions to the connection failure. The prompts for solutions to the connection failure may include multiple recommended failure solutions. For example, the multiple failure solutions include "make sure the device is connected to a power source and turned on", "avoid excessive distances between the mobile phone, device, and gateway", "make sure the device is in a network configuration state", etc.

[0227] If the user clicks the "Done" control 333, the display may jump to the sub-device list interface shown in (b) of FIG5g to display the device categories of the smart home devices that the first gateway is currently connected to and successfully registered with.

[0228] The sub-device list interface shown in (b) of FIG5g is substantially identical to the sub-device list interface shown in (b) of FIG5b, except that if the device categories of the smart home devices that have just been added in batch do not exist in the sub-device list interface shown in (b) of FIG5b, the device categories displayed in the sub-device list interface shown in (b) of FIG5b may be updated based on the device categories of the smart home devices that have just been added in batch, resulting in the sub-device list interface shown in (b) of FIG5g. For example, the user may update the display of connected smart home devices by sliding or dragging downward on the interface (e.g., the sub-device list interface shown in (b) of FIG5b).

[0229] In some embodiments, the user can also add devices that do not support batch addition one by one when the "Allow batch connection" control 311 is turned off. The adding method can refer to the description of (d) in Figure 5f above.

[0230] 6a-6f, a schematic diagram of the operation flow of adding devices to the smart home devices scanned by the gateway device in response to the manual addition operation of the specified device category will be described in detail.

[0231] Assuming that the terminal device is currently connected to the first gateway, (a) in Figure 6a is the gateway details interface 24 of the first gateway. The gateway details interface 24 shown in (a) in Figure 6a is the same as the gateway details interface 24 shown in (a) in Figure 5b, and this embodiment of the application will not be described in detail. The user can click the "Sub-device List" control in the gateway details interface 24 to enter the sub-device list interface as shown in (b) in Figure 6a, and then click the "+" control ac1 in the sub-device list interface to enter the gateway scan interface 25 as shown in (c) in Figure 6a; the user can also click the "Add Sub-Device" control in the gateway details interface 24 to directly enter the gateway scan interface 25 as shown in (c) in Figure 6a.

[0232] The sub-device list interface shown in (b) in Figure 6a is basically the same as the sub-device list interface shown in (b) in Figure 5b, and the gateway scanning interface 25 shown in (c) in Figure 6a is the same as the gateway scanning interface 25 shown in (c) in Figure 5b. This embodiment of the present application will not be elaborated on this.

[0233] When the user clicks the "Manual Add" control 252 in the gateway scanning interface 25, he can enter the add device interface shown in (d) in Figure 6a. The add device interface can display smart home devices of multiple device categories that the first gateway can support. The user can click the control of any device category in the add device interface to add the smart home device of that device category.

[0234] After the user clicks a control of a certain device category in the add device interface, the user can jump to the configuration wizard interface 34 shown in (a) of FIG6 b .

[0235] The configuration wizard interface 34 shown in (a) of FIG6b includes device operation instructions 341, a "Completed" checkbox 342, and a "Next" control 343. Different device types correspond to different device operation instructions 341. Users can configure the smart home device based on the device operation instructions 341 to put the smart home device in network configuration mode, making it easier for the first gateway to scan it.

[0236] For example, for a smart home device that enters network configuration mode upon power-up, the device operation instructions 341 may include: "Ensure the device is powered on and has sufficient power." For a smart home device that requires additional operation to enter network configuration mode upon power-up, the device operation instructions 341 may include: "Ensure the device is powered on and has sufficient power. Perform XXX operation on the device to enter network configuration mode."

[0237] After the user completes the network configuration of the smart home device, they can select the "Completed" checkbox 342 and click the "Next" control 343 to enter the gateway scanning interface shown in FIG6b (b). If the user does not select the "Completed" checkbox 342, the "Next" control 343 is unavailable (grayed out), preventing the user from failing to complete the network configuration of the smart home device and causing the smart home device to be unable to be scanned by the first gateway.

[0238] If the scan result is a smart home device, a legal authorization prompt box 35 corresponding to the smart home device can be displayed on the gateway scanning interface shown in (b) of Figure 6b, as shown in (c) of Figure 6b. The legal authorization prompt box 35 includes a "Cancel" control and an "Agree" control. If the user clicks the "Cancel" control, indicating that they do not agree to the user agreement and privacy statement, the legal authorization prompt box 35 disappears, and the addition of the smart home device cannot be completed. The user can jump to the gateway details interface 24 shown in (a) of Figure 6a or the configuration wizard interface 34 shown in (a) of Figure 6b. If the user clicks the "Agree" control, indicating that they agree to the user agreement and privacy statement, that is, they obtain legal authorization for the connection of the smart home device, and can jump to the device connection interface shown in (a) of Figure 6c, which displays the connection progress between the first gateway and the smart home device. The device connection interface shown in (a) of Figure 6c is basically the same as the device connection interface shown in (a) of Figure 5d, and will not be described in detail in this embodiment of the application.

[0239] If the smart home device is a second type of smart home device and the first gateway is successfully connected to the smart home device (establishing a connection with the gateway and successfully registering with the server), the device connection interface shown in FIG6c(a) may be changed to the connection success interface shown in FIG6c(b). The connection success interface shown in FIG6c(b) is substantially the same as the connection success interface shown in FIG5d(b), and is not further described in this embodiment of the present application.

[0240] If the smart home device is a first type of smart home device, since the smart home device requires device connection authentication, when the device connection progress reaches a preset progress, the device connection interface shown in (a) of FIG. 6c may be changed to the device verification interface shown in (c) of FIG. 6c. The preset progress can be set according to actual needs and is not limited in this embodiment of the application. For example, the preset progress is 50%. The device verification interface shown in (c) of FIG. 6c is substantially the same as the device verification interface shown in (c) of FIG. 5d and is not further described in this embodiment of the application.

[0241] When the user successfully authenticates the smart home device, if the first gateway establishes a connection with the smart home device and the first gateway successfully registers the smart home device on the server, the device verification interface shown in (c) of Figure 6c may be changed to the connection success interface shown in (b) of Figure 6c.

[0242] In some embodiments, if the smart home device is a second type of smart home device and the first gateway fails to connect to the smart home device (failed to establish a connection with the gateway or failed to complete registration on the server), the device connection interface shown in (a) of FIG. 6c may be changed to the connection failure interface shown in (d) of FIG. 6c. The connection failure interface shown in (d) of FIG. 6c is substantially the same as the connection failure interface shown in (d) of FIG. 5d, and is not further described in this embodiment of the present application.

[0243] If the smart home device is a first type of smart home device, and the first gateway fails to connect to the smart home device, or the smart home device fails to authenticate, or fails to register on the server, the device connection interface shown in (a) of Figure 6c may be changed to the connection failure interface shown in (d) of Figure 6c, or the device verification interface shown in (c) of Figure 6c may be changed to the connection failure interface shown in (d) of Figure 6c.

[0244] In some embodiments, after the second preset time of the successful connection interface shown in (b) of Figure 6c is displayed, the device settings interface shown in (a) of Figure 6d may be automatically displayed. The second preset time can be set according to actual needs and is not limited in this embodiment of the application. The device settings interface shown in (a) of Figure 6d is basically the same as the device settings interface shown in (a) of Figure 5e, and will not be described in detail in this embodiment of the application.

[0245] After the user completes the device name and room settings in the device settings interface shown in (a) of Figure 6d, they can click the "Done" control to jump to the sub-device list interface shown in (b) of Figure 6d. The sub-device list interface shown in (b) of Figure 6d can be used to display the device categories of all devices currently connected and successfully registered with the first gateway. The sub-device list interface shown in (b) of Figure 6d is basically the same as the sub-device list interface shown in (b) of Figure 5e, and will not be described in detail in this embodiment of the application.

[0246] In some embodiments, after displaying the gateway scanning interface shown in FIG. 6b (b), if the first gateway scans multiple smart home devices (the multiple smart home devices belong to the same device category, i.e., the device category clicked by the user in the add device interface shown in FIG. 6a (d)), a scan result card 36 may be displayed within the gateway scanning interface shown in FIG. 6b (b), as shown in FIG. 6e (a). The scan result card 36 may display the name, image, and number of the smart home devices, with the number displayed in the form of a numeric superscript.

[0247] After the user clicks on the scan result card 36, the user may be directed to the device selection interface 37 shown in FIG6e(b) or the device selection interface 37 shown in FIG6e(c). For example, if the "Allow batch connection" control in the device selection interface 37 is off by default, the user clicks on the scan result card 36 and is directed to the device selection interface 37 shown in FIG6e(b); if the "Allow batch connection" control in the device selection interface 37 is on by default, the user clicks on the scan result card 36 and is directed to the device selection interface 37 shown in FIG6e(c).

[0248] As shown in Figure 6e (b), when the "Allow Batch Connections" control is off, each smart home device scanned by the first gateway has a corresponding "Connect" control. The user can click on the "Connect" control to individually add a smart home device. For example, clicking on the "Connect" control corresponding to a smart home device will connect and register that smart home device, and the device selection interface 37 shown in Figure 6e (b) will be displayed, transitioning to the device connection interface shown in Figure 6c (a).

[0249] In some embodiments, the device selection interface 37 shown in (b) of Figure 6e can also display the connection legal authorization information below each device card: "Using the services of this device means agreeing to the user agreement and privacy statement of this device." The display style of the connection legal authorization information can refer to the display style shown in (c) of Figure 6e.

[0250] As shown in (c) of FIG6e , when the "Allow Batch Connection" control is turned on, the device selection interface 37 also displays a "Select All" control and a "Agree and Connect" control, with a checkbox corresponding to each smart home device scanned by the first gateway. The user can select each device individually or click the "Select All" control to select all devices in batches.

[0251] In some embodiments, when every device in the device selection interface 37 is checked, the “select all” control may be changed to a “deselect all” control.

[0252] After selecting multiple devices, the user can click the "Agree and Connect" control to initiate batch addition of the selected devices. The device selection interface 37 shown in FIG. 6e (c) can be redirected to the batch device connection interface 32 shown in FIG. 6e (d). The batch device connection interface 32 shown in FIG. 6e (d) is substantially the same as the batch device connection interface 32 shown in FIG. 5f (c), and will not be further described in this embodiment of the present application.

[0253] In some embodiments, if the first gateway scans multiple smart home devices and does not support batch addition, after the user clicks the scan result card 36, he can also jump to the device selection interface 37 shown in (a) of Figure 6f. The device selection interface 37 does not include an "Allow batch connection" control.

[0254] After each selected device completes the connection action (the result is either a successful connection or a failed connection), the batch device connection interface 32 shown in (d) of FIG6e can be jumped to the connection result interface 33 shown in (b) of FIG6f. The connection result interface shown in (b) of FIG6f is basically the same as the connection result interface shown in (a) of FIG5g, and will not be described in detail in this embodiment of the application.

[0255] The connection result interface 33 shown in (b) of Figure 6f includes a "Done" control. If the user clicks the "Done" control, the sub-device list interface shown in (c) of Figure 6f will be displayed to display the device categories of the smart home devices that the first gateway is currently connected to and successfully registered.

[0256] 7a to 7e , a schematic diagram of an operation flow for adding a device to a smart home device that is self-discovered by a terminal device through a gateway device is described in detail below.

[0257] The user can click the "Honor Smart Space" application icon on the desktop to enter the smart space homepage interface 22 as shown in (a) in Figure 7a.

[0258] Taking the example of establishing a connection between a terminal device and a first gateway, after the first gateway scans for smart home devices to be networked, it can push discovery information about the smart home devices to the terminal device. After receiving the discovery information pushed by the first gateway, the terminal device can display a device discovery pop-up window 38 on the smart space homepage interface 22. The device discovery pop-up window 38 can cover a portion of the content of the smart space homepage interface 22. The device discovery pop-up window 38 may include a device discovery prompt, a "Cancel" control, and a "Connect" control. The user can use the device discovery prompt to learn which gateway discovered the smart home devices to be networked and the number of smart home devices to be networked. For example, the device discovery prompt may read: "XX gateway discovered n devices."

[0259] In some embodiments, if a terminal device has established connections with multiple gateways, each gateway can push discovery information about the smart home devices to the terminal device after scanning for the smart home devices to be connected. The terminal device can use the discovery information received first to generate a device discovery pop-up window 38, and other discovery information can be ignored. In other embodiments, the terminal device can also update the prompt information displayed in the notification based on the discovery information received later, for example, prompting the user that N connectable smart home devices have been discovered.

[0260] In some embodiments, if a gateway has reached its maximum number of connections, it can be configured not to push smart home device discovery information to the terminal device even if it scans for smart home devices to be networked. In another embodiment, a prompt message can be output to inform the terminal device of the newly scanned device information, the current number of gateway connections, and whether the preset number has been reached.

[0261] If the user clicks the "Cancel" control, it indicates that the smart home device to be networked scanned by the first gateway will not be connected and registered, and the device discovery pop-up window 38 disappears. If the user clicks the "Connect" control, it indicates that the smart home device to be networked scanned by the first gateway will be connected and registered.

[0262] As shown in (a) of Figure 7a, assuming that the first gateway scans a smart home device to be networked, the device discovery pop-up window 38 includes a gateway pattern 381 and a device pattern 382. The device discovery prompt information in the device discovery pop-up window 38 can be: "XX gateway discovered 1 device."

[0263] After the user clicks the "Connect" control, the device finds that the pop-up window 38 disappears, and a legal authorization prompt box 39 corresponding to the smart home device to be networked pops up. The legal authorization prompt box 39 can cover part of the content of the smart space homepage interface 22, as shown in (b) in Figure 7a.

[0264] The legal authorization prompt box 39 shown in (b) of FIG. 7 a is substantially the same as the legal authorization prompt box 28 shown in (b) of FIG. 5 c , and will not be described in detail in this embodiment of the present application.

[0265] If the user clicks the "Cancel" control in the legal authorization prompt box 39, indicating that he does not agree to the user agreement and privacy statement, the legal authorization prompt box 39 disappears, and only the smart space homepage interface 22 is displayed, that is, the addition of the smart home device cannot be completed. If the user clicks the "Agree" control, indicating that he agrees to the user agreement and privacy statement, that is, he obtains the legal authorization for the connection of the smart home device, the interface shown in (b) of Figure 7a can be changed to the device connection interface shown in (a) of Figure 7b to display the connection progress of the first gateway and the smart home device. The device connection interface shown in (a) of Figure 7b is basically the same as the device connection interface shown in (a) of Figure 5d, and will not be described in detail in this embodiment of the present application.

[0266] If the smart home device is a second type of smart home device and the first gateway is successfully connected to the smart home device (establishing a connection with the gateway and successfully registering on the server), the device connection interface shown in FIG. 7b (a) may be changed to the connection success interface shown in FIG. 7b (b). The connection success interface shown in FIG. 7b (b) is substantially the same as the connection success interface shown in FIG. 5d (b), and is not further described in this embodiment of the present application.

[0267] If the smart home device is a first type of smart home device, since the smart home device requires device connection authentication, when the device connection progress reaches a preset progress, the device connection interface shown in (a) of FIG. 7b may be changed to the device verification interface shown in (c) of FIG. 7b (c) of FIG. The device verification interface shown in (c) of FIG. 7b of FIG. 7d is substantially the same as the device verification interface shown in (c) of FIG. 5d of FIG. This embodiment of the present application will not be further described.

[0268] When the user successfully authenticates the smart home device, if the first gateway establishes a connection with the smart home device and the first gateway successfully registers the smart home device on the server, the device verification interface shown in (c) of Figure 7b may be changed to the connection success interface shown in (b) of Figure 7b.

[0269] In some embodiments, if the smart home device is a second type of smart home device and the first gateway fails to connect to the smart home device (failed to establish a connection with the gateway or failed to complete registration on the server), the device connection interface shown in (a) of FIG. 7b may be changed to the connection failure interface shown in (d) of FIG. 7b. The connection failure interface shown in (d) of FIG. 7b is substantially the same as the connection failure interface shown in (d) of FIG. 5d, and is not further described in this embodiment of the present application.

[0270] If the smart home device is a first type of smart home device, and the first gateway fails to connect to the smart home device, or the smart home device fails to authenticate, or fails to register on the server, the device connection interface shown in (a) of Figure 7b may be changed to the connection failure interface shown in (d) of Figure 7b, or the device verification interface shown in (c) of Figure 7b may be changed to the connection failure interface shown in (d) of Figure 7b.

[0271] In some embodiments, after the second preset time of the successful connection interface shown in (b) of Figure 7b is displayed, the device settings interface shown in (a) of Figure 7c can be automatically displayed. The second preset time can be set according to actual needs and is not limited in this embodiment of the application. The device settings interface shown in (a) of Figure 7c is basically the same as the device settings interface shown in (a) of Figure 5e, and will not be described in detail in this embodiment of the application.

[0272] After the user completes the device name and room settings on the device settings interface shown in FIG7c (a), they can click the "Done" control to jump to the display of the smart space homepage interface 22 shown in FIG7c (b). Alternatively, clicking the "Done" control can be set to jump to the display of the sub-device list interface, which displays the device categories of all devices currently connected and successfully registered with the first gateway.

[0273] As shown in FIG7d (a), assuming that the first gateway scans two or more smart home devices to be networked, if the user clicks the "Connect" control, the user may be directed to the batch device selection interface 31 shown in FIG7d (b) or the batch device selection interface 31 shown in FIG7d (c).

[0274] (a) in Figure 7d is illustrated by taking the example of the first gateway scanning three smart home devices to be networked. The device discovery pop-up window 38 includes a gateway pattern 381 and three device patterns 382. The device discovery prompt information in the device discovery pop-up window 38 can be: "XX gateway discovered 3 devices."

[0275] In some embodiments, if the "Allow batch connection" control in the batch device selection interface 31 is in the off state by default, after the user clicks the "Connect" control, the interface as shown in (a) of Figure 7d can be jumped to the batch device selection interface 31 as shown in (b) of Figure 7d; if the "Allow batch connection" control in the batch device selection interface 31 is in the on state by default, after the user clicks the "Connect" control, the interface as shown in (a) of Figure 7d can be jumped to the batch device selection interface 31 as shown in (c) of Figure 7d.

[0276] As shown in Figure 7d (b), when the "Allow Batch Connections" control is off, each smart home device scanned by the first gateway has a corresponding "Connect" control. The user can click on the "Connect" control to individually add a smart home device. For example, clicking on the "Connect" control corresponding to a smart home device allows the connection and registration of that smart home device. The batch device selection interface 31 shown in Figure 7d (b) will be redirected to the device connection interface shown in Figure 7b (a).

[0277] In some embodiments, the batch device selection interface 31 shown in (b) of Figure 7d can also display the connection legal authorization information below each device card: "Using the services of this device means agreeing to the user agreement and privacy statement of this device." The display style of the connection legal authorization information can refer to the display style shown in (c) of Figure 7d.

[0278] As shown in (c) of Figure 7d, when the "Allow Batch Connection" control is turned on, the batch device selection interface 31 also displays the "Select All" control and the "Agree and Connect" control. The smart home devices scanned by the first gateway are divided into devices that can be connected in batches and those that do not support batch connection. Devices that can be connected in batches are displayed in the first device display area 312, while devices that do not support batch connection are displayed in the second device display area 313. For devices that can be connected in batches, the user can select them one by one, or click the "Select All" control to select all of them to complete the batch selection.

[0279] In some embodiments, the user can also add devices that do not support batch connection one by one independently when the "Allow batch connection" control is turned off. For example, if the user clicks the "Allow batch connection" control that is in the on state, the "Allow batch connection" control turns off, and the batch device selection interface 31 shown in (c) of Figure 7d jumps to the batch device selection interface 31 shown in (b) of Figure 7d. The user can click the "Connect" control corresponding to a smart home device that does not support batch connection in the batch device selection interface 31 to connect and register the smart home device. The batch device selection interface 31 shown in (b) of Figure 7d jumps to the device connection interface shown in (a) of Figure 7b.

[0280] In some embodiments, when each device in the first device display area 312 is checked, the "select all" control may be changed to a "deselect all" control, as shown in (d) in FIG. 7d .

[0281] After completing the selection of multiple devices in the first device display area 312, the user can click the "Agree and Connect" control to initiate batch addition of the selected multiple devices, and the batch device selection interface 31 shown in (c) of Figure 7d can be jumped to the batch device connection interface 32 shown in (a) of Figure 7e. The batch device connection interface 32 shown in (a) of Figure 7e is basically the same as the batch device connection interface 32 shown in (c) of Figure 5f, and will not be further described in this embodiment of the application.

[0282] After each selected device completes the connection action (the result is either a successful connection or a failed connection), the batch device connection interface 32 shown in FIG7e (a) can be redirected to the connection result interface 33 shown in FIG7e (b). The connection result interface shown in FIG7e (b) is substantially the same as the connection result interface shown in FIG5g (a), and will not be further described in this embodiment of the present application.

[0283] After the user clicks the "Done" control in the connection result interface 33 shown in (b) of Figure 7e, the display can jump to the smart space homepage interface 22 shown in (c) of Figure 7e.

[0284] In some embodiments, if multiple smart home devices do not support batch addition, after the user clicks the "Unconnect" control in the card 38 shown in (a) in Figure 7d, he can also jump to the device selection interface 37 shown in (a) in Figure 6f. The device selection interface 37 does not include the "Allow batch connection" control.

[0285] 8a to 8f , a schematic diagram of an operation flow in which the terminal device controls the gateway device to scan smart home devices and add the scanned devices in response to the user's operation of adding a specified device category is described in detail.

[0286] The user can click the "Honor Smart Space" app icon on the desktop to enter the Smart Space homepage interface 22 shown in (a) of Figure 8a. After the user clicks the "+" control 221 on the Smart Space homepage interface 22, the "Add Device" control, "Create Scene" control, "Share Device" control, and "Connect to Third-Party Platform" control will pop up.

[0287] After the user clicks the "Add Device" control, they can enter the manual device addition interface shown in Figure 8a (b). The manual device addition interface shown in Figure 8a (b) includes a "Scan to Add" control and a "Manual Add" control. The "Scan to Add" control is used to initiate a QR code scan to add a smart home device to the network to be configured. For example, clicking the "Scan to Add" control enters the QR code scanning interface, where the user can scan the smart home device to be configured. After the scan is successful, the user can enter the gateway selection interface shown in Figure 8b (a) or the gateway selection interface shown in Figure 8b (b).

[0288] The "Manual Add" control is used to add smart home devices of a specified device category. After the user clicks the "Manual Add" control, they can enter the device category selection interface shown in Figure 8a (c).

[0289] The device category selection interface shown in (c) of Figure 8a can be divided into multiple categories based on device category, and each category can be further divided into multiple subcategories (device categories). For example, the major categories include sensors and lighting. Sensors can include multiple device categories such as human sensors, door and window sensors, smoke sensors, and water sensors. Lighting can include multiple device categories such as downlights and spotlights.

[0290] The user can click on a subcategory in the device category selection interface shown in (c) of FIG8a to enter the gateway selection interface shown in (a) of FIG8b or the gateway selection interface shown in (b) of FIG8b.

[0291] The gateway selection interface shown in (a) in 8b is that there is currently no gateway device that supports adding this device category, that is, a gateway device needs to be added before the subsequent smart home device addition can be completed. The gateway selection interface shown in (b) in 8b is that there is currently a gateway device that supports adding this device category, and there is no need to add a gateway device.

[0292] For example, if the user clicks on the human body sensor in the device category selection interface shown in (c) of Figure 8a, and the first gateway currently connected to the terminal device does not support connection with the human body sensor (for example, the communication protocol supported by the first gateway does not include the communication protocol of the human body sensor), the user needs to add a second gateway that can support the communication protocol of the human body sensor, that is, the device category selection interface shown in (c) of Figure 8a jumps to the gateway selection interface shown in (a) of Figure 8b to establish a connection between the terminal device and the second gateway.

[0293] For example, if the user clicks on the human body sensor in the device category selection interface shown in (c) of Figure 8a, and the first gateway currently connected to the terminal device supports connection with the human body sensor, the user does not need to add the gateway device, that is, the device category selection interface shown in (c) of Figure 8a jumps to the gateway selection interface shown in (b) of Figure 8b.

[0294] The gateway selection interface shown in FIG8b(a) includes a configuration wizard interface 34 and a gateway addition pop-up window 40, which covers a portion of the configuration wizard interface 34. The gateway addition pop-up window 40 includes a gateway addition prompt, a "Cancel" control, and an "Add Now" control. The gateway addition prompt may include: "This device requires a gateway connection. You can add a gateway to connect. You can also query the gateway models that support sub-devices." If the user clicks the "Cancel" control in the gateway addition pop-up window 40, the gateway addition is abandoned, and the subsequent addition of smart home devices of the specified device category cannot be completed. If the user clicks the "Add Now" control, the gateway addition interface shown in FIG9(a) is entered to add the gateway device. After the gateway device is added, the configuration wizard interface 34 shown in FIG8b(c) is entered. The configuration wizard interface 34 shown in FIG8b(c) is substantially the same as the configuration wizard interface 34 shown in FIG6b(a) and will not be described in detail in this embodiment of the present application. The gateway addition interface shown in FIG9(a) can display multiple gateway devices that support the pre-added device categories.

[0295] In some embodiments, if a user clicks the "Gateway Model" link in the gateway addition prompt, they can jump from the gateway selection interface shown in Figure 8b (a) to the gateway model viewing interface shown in Figure 9 (b). For example, if the user clicks on the human body sensor in the device category selection interface shown in Figure 8a (c), the user can view the various gateway models that support human body sensors through the gateway model viewing interface shown in Figure 9 (b). The user can also click on a specific gateway model in the gateway model viewing interface shown in Figure 9 (b) to jump from the gateway model viewing interface shown in Figure 9 (b) to the gateway details interface shown in Figure 9 (c).

[0296] The gateway selection interface shown in (b) of Figure 8b includes a configuration wizard interface 34 and a gateway selection pop-up window 41. The gateway selection pop-up window 41 covers a portion of the configuration wizard interface 34. The gateway selection pop-up window 41 includes a gateway selection area 410, an "Add New Gateway" control 411, a "Cancel" control, and an "OK" control. The gateway selection area 410 allows you to select all gateway devices currently connected to the terminal device. The user can select the gateway device in the gateway selection area 410 and click the "OK" control to complete the gateway device selection. If the user clicks the "Cancel" control in the gateway selection pop-up window 411, it means that the gateway selection is abandoned and the subsequent addition of smart home devices of the specified device category cannot be completed. The user can also enter the gateway addition interface shown in (a) of Figure 9 by clicking the "Add New Gateway" control 411 to add a new gateway device.

[0297] After the user completes the network configuration operation of the smart home device, he can check the "Completed the above operations" check box in the configuration wizard interface 34 shown in (c) of Figure 8b and click the "Next" control to enter the gateway scanning interface shown in (d) of Figure 8b.

[0298] If the scan result is a smart home device, a legal authorization prompt box 35 corresponding to the smart home device can be displayed on the gateway scanning interface shown in (d) in Figure 8b, as shown in (a) in Figure 8c. The legal authorization prompt box 35 includes a "Cancel" control and an "Agree" control. If the user clicks the "Cancel" control, it indicates that he does not agree to the user agreement and privacy statement, and the legal authorization prompt box 35 disappears, which means that the addition of the smart home device cannot be completed. If the user clicks the "Agree" control, it indicates that he agrees to the user agreement and privacy statement, and obtains the legal authorization for the connection of the smart home device, and can jump to the device connection interface shown in (b) in Figure 8c to display the connection progress of the selected smart home device. The device connection interface shown in (b) in Figure 8c is basically the same as the device connection interface shown in (a) in Figure 5d, and will not be described in detail in this embodiment of the present application.

[0299] If the smart home device is a second type of smart home device, and the selected target gateway establishes a connection with the smart home device, and the target gateway successfully registers the smart home device with the server, the device connection interface shown in FIG8c(b) may be changed to the connection success interface shown in FIG8c(c). The connection success interface shown in FIG8c(c) is substantially the same as the connection success interface shown in FIG5d(b), and is not further described in this embodiment of the application.

[0300] If the smart home device is a first type of smart home device, since the smart home device requires device connection authentication, when the device connection progress reaches a preset progress, the device connection interface shown in Figure 8c (b) may be changed to the device verification interface shown in Figure 8c (d). The device verification interface shown in Figure 8c (d) is basically the same as the device verification interface shown in Figure 5d (c), and is not further described in this embodiment of the application.

[0301] When the user successfully authenticates the smart home device, if the selected target gateway establishes a connection with the smart home device and the selected target gateway successfully registers the smart home device on the server, the device verification interface shown in (d) of Figure 8c may be changed to the connection success interface shown in (c) of Figure 8c.

[0302] In some embodiments, if the smart home device is a second type of smart home device and the first gateway fails to connect to the smart home device (for example, the reason for the connection failure may be that a connection with the gateway cannot be established, or registration cannot be completed on the server), the device connection interface shown in (b) in Figure 8c can be changed to a connection failure display interface.

[0303] If the smart home device is a first type of smart home device and the first gateway fails to connect to the smart home device, or the smart home device fails to authenticate, or fails to register with the server, the device connection interface shown in FIG8c(b) may be changed to a connection failure interface, or the device verification interface shown in FIG8c(d) may be changed to a connection failure interface. The connection failure interface may refer to the connection failure interface shown in FIG5d(d), which is not described in detail in this embodiment of the application.

[0304] In some embodiments, after the second preset time period of the successful connection interface shown in (c) of FIG. 8c is displayed, the device settings interface shown in (a) of FIG. 8d may be automatically displayed. The device settings interface shown in (a) of FIG. 8d is substantially the same as the device settings interface shown in (a) of FIG. 5e , and will not be described in detail in this embodiment of the present application.

[0305] After the user completes the device name and room settings on the device settings interface shown in Figure 8d (a), they can click the "Done" control to jump to the display of the smart space homepage interface 22 shown in Figure 8d (b). Alternatively, after clicking the "Done" control, the user can jump to the display of the sub-device list interface, which displays the device categories of all devices currently connected and successfully registered with the selected target gateway.

[0306] In some embodiments, after the gateway scanning interface shown in FIG. 8b (d) is displayed, if the selected target gateway scans multiple smart home devices (the multiple smart home devices belong to the same device category, i.e., the device category selected by the user in the device category selection interface shown in FIG. 8a (c)), a scan result card 36 may be displayed within the gateway scanning interface shown in FIG. 8b (d), as shown in FIG. 8e (a). The scan result card 36 may display the name, image, and number of the smart home devices, with the number displayed in the form of a numeric superscript.

[0307] After the user clicks on the scan result card 36, the user can jump to the device selection interface 37 shown in (b) of Figure 8e or the device selection interface 37 shown in (c) of Figure 8e. For example, if the "Allow Batch Connection" control in the device selection interface 37 is off by default, the user clicks on the scan result card 36 and jumps to the device selection interface 37 shown in (b) of Figure 8e; if the "Allow Batch Connection" control in the device selection interface 37 is on by default, the user clicks on the scan result card 36 and jumps to the device selection interface 37 shown in (c) of Figure 8e. The device selection interface 37 shown in (b) of Figure 8e is substantially the same as the device selection interface 37 shown in (b) of Figure 6e, and the device selection interface 37 shown in (c) of Figure 8e is substantially the same as the device selection interface 37 shown in (c) of Figure 6e. This embodiment of the present application will not be described in detail.

[0308] After selecting multiple devices in the device selection interface 37 shown in FIG8e (c), the user can click the "Agree and Connect" control to initiate batch addition of the selected devices. The device selection interface 37 shown in FIG8e (c) can then be redirected to the batch device connection interface 32 shown in FIG8e (d). The batch device connection interface 32 shown in FIG8e (d) is substantially the same as the batch device connection interface 32 shown in FIG6e (d), and will not be further described in this embodiment of the present application.

[0309] In some embodiments, if the selected target gateway scans multiple smart home devices and does not support batch addition, after the user clicks the scan result card 36, he can also jump to the device selection interface 37 shown in (a) of Figure 8f. The device selection interface 37 does not include an "Allow batch connection" control.

[0310] After each selected device completes the connection action (the result is a successful connection or a failed connection), the batch device connection interface 32 shown in (d) of Figure 8e can be jumped to the connection result interface 33 shown in (b) of Figure 8f. The connection result interface shown in (b) of Figure 8f is basically the same as the connection result interface shown in (b) of Figure 6f, and will not be described in detail in this embodiment of the application.

[0311] After the user clicks the "Done" control in the connection result interface 33 shown in (b) of Figure 8f, the display can jump to the smart space homepage interface 22 shown in (c) of Figure 8f.

[0312] The following describes in detail various interface status diagrams that may appear on the batch device connection interface when adding devices in batches, in conjunction with FIG. 10 a .

[0313] As shown in (a) of Figure 10a, the batch device connection interface 32 may include a total connection progress animation 320, a total connection progress 321, connection prompt information 322, and the connection progress 323 of each device. The total connection progress animation 320 can be displayed using a circular progress bar, and the circular progress bar of the total connection progress animation 320 can correspond to the percentage of the total connection progress 321. The total connection progress animation 320 can also be a circular rotating progress bar, that is, it does not correspond to the percentage of the total connection progress 321. The connection progress 323 of each device is displayed using a circular progress bar. When a device successfully connects (establishes a connection with the gateway and successfully registers on the server), the connection progress 323 of the device can change from a circular progress bar to a "√", as shown in (b) of Figure 10a. When a device fails to connect (failed to establish a connection with the gateway or failed to complete registration on the server), the connection progress 323 of the device can change from a circular progress bar to an "X", as shown in (c) of Figure 10a. The circular progress bar is only an example and is not limited to this in actual application.

[0314] As shown in (b) and (c) in Figure 10a, the batch device connection interface 32 can divide the connection progress 323 of each device into two fields or three fields for display. The two fields may include: a field for displaying the device connection in progress, a field for displaying the device connection is successful, or a field for displaying the device connection in progress, a field for displaying the device connection failure; the three fields may include: a field for displaying the device connection in progress, a field for displaying the device connection is successful, and a field for displaying the device connection failure.

[0315] The following describes in detail various interface status diagrams that may appear on the connection result interface when adding devices in batches, in conjunction with FIG. 10 b .

[0316] As shown in (a) of FIG10b , if each device selected in the batch is successfully connected (for example, a connection is established with the gateway and successfully registered on the server), the connection result interface 33 may only include a successful connection display area 331. If each device selected in the batch fails to connect (for example, a connection with the gateway cannot be established, or registration with the server cannot be completed), the connection result interface 33 may also only include a failed connection display area 332. For example, if all the "√"s shown in (a) of FIG10b are replaced by "×", the connection for each device has failed, and a suggested solution may be displayed below the failed connection display area 332.

[0317] As shown in (b) of Figure 10b, if some of the devices selected in batches are successfully connected and some are failed to connect, the result interface 33 may include a successful connection display area 331 and a failed connection display area 332, and a suggested solution may be displayed below the failed connection display area 332.

[0318] Please refer to FIG. 11 . The device discovery pop-up window 38 may display corresponding device discovery prompt information and a corresponding number of device patterns 382 according to the number of smart home devices to be networked discovered by the gateway.

[0319] As shown in (a) in Figure 11, if the number of smart home devices to be networked discovered by the gateway is two, the device discovery prompt information displayed in the device discovery pop-up window 38 can be: "XX gateway discovered 2 devices", and a gateway pattern 381 and two device patterns 382 can be displayed in the device discovery pop-up window 38.

[0320] As shown in (b) in Figure 11, if the number of smart home devices to be networked discovered by the gateway is four, the device discovery prompt information displayed in the device discovery pop-up window 38 can be: "XX gateway discovered 4 devices", and a gateway pattern 381 and four device patterns 382 can be displayed in the device discovery pop-up window 38.

[0321] As shown in (c) in Figure 11, if the number of smart home devices to be networked discovered by the gateway is five, the device discovery prompt information displayed in the device discovery pop-up window 38 can be: "XX gateway discovered 5 devices", and a gateway pattern 381 and five device patterns 382 can be displayed in the device discovery pop-up window 38.

[0322] As shown in (d) in Figure 11, if the number of smart home devices to be networked discovered by the gateway is six, the device discovery prompt information displayed in the device discovery pop-up window 38 can be: "XX gateway discovered 6 devices", and a gateway pattern 381 and six device patterns 382 can be displayed in the device discovery pop-up window 38.

[0323] In some embodiments, due to the limited size of the device discovery pop-up window 38, when the number of smart home devices to be networked discovered by the gateway reaches or exceeds a preset number, for example, seven or more, the device discovery prompt information can be: "XX gateway discovered 7 devices", "XX gateway discovered 8 devices", etc., but the maximum number of device patterns 382 displayed is 7.

[0324] In some embodiments, the number of smart home devices that a gateway device can connect to has an upper limit. When adding smart home devices through the gateway device, the number of connected smart home devices must not exceed the number of remaining connectable devices on the gateway device. This is followed by a detailed description of the warning situation in which the number of remaining connectable devices on the gateway device is exceeded when adding smart home devices, as described below with reference to Figures 12a-12c.

[0325] In one embodiment, the number of devices discovered by the gateway device displayed in the device discovery pop-up window 38 may also be set according to an upper limit of smart home devices that can be connected to the gateway device.

[0326] As shown in (a) of Figure 12a , when a user completes device selection in the batch device selection interface 31 and clicks the "Agree and Connect" control, if the number of selected devices exceeds the number of remaining connectable gateway devices required to connect these selected devices, an exception prompt box 315 may pop up. For example, the prompt message contained in exception prompt box 315 may read: "The gateway can only connect to x more sub-devices. Reduce the number of devices and try again." Based on this exception prompt box 315, the user can reduce the number of selected devices and click the "Agree and Connect" control to connect the devices.

[0327] Similarly, when the user completes the device selection in the device selection interface 37 and clicks the "Agree and Connect" control, if the number of checked devices is greater than the remaining connectable number of gateway devices used to connect these checked devices, an abnormal prompt box as shown in (a) in Figure 12a may also pop up to remind the user to reduce the number of checked devices and try again.

[0328] In the gateway scanning interface 25 shown in (b) of Figure 12a, when the user clicks on a device card in the gateway scanning interface 25 and the remaining number of connectable gateway devices used to connect to the device is less than or equal to the preset number, a warning prompt box 255 as shown in (c) of Figure 12a may pop up. The preset number can be set according to actual needs, and the embodiment of the present application does not limit this. For example, the preset number is 3. The warning prompt box 255 includes a "Continue connecting" control and a warning prompt message. The content of the warning prompt message may be: "The upper limit of the number of gateway connections is about to be reached, and only x sub-devices can be connected." The user can continue to connect the device by clicking the "Continue connecting" control.

[0329] Alternatively, when a user clicks on a device card in the gateway scanning interface 25 and the gateway device used to connect to the device has reached the upper limit of the number of connections, a full limit prompt box 256 as shown in (d) of Figure 12a may pop up. The full limit prompt box 256 includes a "Cancel connection" control and a full limit prompt message. The full limit prompt message may read: "The upper limit of the number of gateway connections has been reached. No further device connections can be made. You can change the gateway connection or connect to this device by deleting other sub-devices." The user can cancel the device connection by clicking the "Cancel connection" control.

[0330] As shown in the gateway scanning interface 25 in FIG. 12b (a), the gateway scans multiple smart home devices in response to the manual addition of a specified device category. If the user clicks the scan result card 36 and the number of remaining connectable gateway devices for connecting to these devices is less than or equal to the preset number, a warning prompt box 255 as shown in FIG. 12b (b) may pop up. The warning prompt box 255 shown in FIG. 12b (b) is substantially the same as the warning prompt box 255 shown in FIG. 12a (c), and will not be further described in this embodiment of the present application.

[0331] In some embodiments, if the user clicks on the scan result card 36 and the gateway device used to connect to the device has reached the upper limit of the number of connections, a full amount prompt box 256 as shown in (c) of Figure 12b may pop up. The full amount prompt box 256 shown in (c) of Figure 12b is basically the same as the full amount prompt box 256 shown in (d) of Figure 12a, and will not be described in detail in this embodiment of the present application.

[0332] In some embodiments, if the user clicks on the scan result card 36 and the number of devices displayed on the scan result card 36 is greater than the number of remaining connectable gateway devices used to connect to these devices, a partial connection prompt box may pop up. The style of the partial connection prompt box may be substantially the same as the warning prompt box 255 shown in (c) of Figure 12a, with the difference being that the content of the warning prompt message may be: "The gateway can only connect to x more sub-devices. Please confirm whether to continue connecting." When the user clicks the "Continue connecting" control in the partial connection prompt box, the connection of some devices may be completed. The rule for determining some devices may be based on the chronological order in which they are scanned by the gateway.

[0333] As shown in FIG12c(a), a device discovery pop-up window 38 is used to display the number of smart home devices to be networked that a gateway has discovered. When a user clicks the "Connect" control in the device discovery pop-up window 38, and the number of remaining connectable gateway devices used to connect to these devices is less than or equal to a preset number, a warning prompt box 255 as shown in FIG12c(b) may pop up. The warning prompt box 255 shown in FIG12c(b) is substantially the same as the warning prompt box 255 shown in FIG12a(c), and will not be further described in this embodiment of the present application.

[0334] In some embodiments, if the user clicks the "Connect" control in the device discovery pop-up window 38 and the number of devices displayed in the device discovery pop-up window 38 is greater than the number of remaining connectable gateway devices for connecting to these devices, a partial connection prompt box may also pop up. When the user clicks the "Continue Connecting" control in the partial connection prompt box, the connection of some devices may be completed.

[0335] As shown in FIG13 , an embodiment of the present application provides a method for adding devices in batches, which is applied to a terminal device. The terminal device has established a communication connection with a gateway device, and the terminal device has installed a smart device management application, for example, the smart device management application is the "Honor Smart Space" application. The method for adding devices in batches may include:

[0336] S131: Receive a first operation from the user.

[0337] In some embodiments, the first operation may be a click operation. For example, the first operation is to click on the icon of the smart device management application displayed on the desktop of the terminal device to start the smart device management application and enter the home page interface of the smart device management application, and to click on the home page interface to enter the first interface of the smart device management application.

[0338] S132: In response to the first operation, start the smart device management application and display a first interface, where the first interface includes a plurality of controls for adding devices in batches.

[0339] The smart device management application may include a first interface for batch adding devices and a second interface for displaying batch addition results. The first interface includes controls for batch adding devices, and the first interface may display all devices to be added that have been scanned by the gateway device. For example, the first interface may be the batch device selection interface shown in (b) of Figure 5f, and the second interface may be the connection result interface shown in (a) of Figure 5g. Controls in the first interface may include the "Allow Batch Connection" control, the "Select All" control, the "Agree and Connect" control, etc. shown in (b) of Figure 5f.

[0340] S133: Receive a second operation from the user on the control in the first interface.

[0341] In some embodiments, one or more controls in the first interface can be used to trigger the selection of multiple devices to be added in the first interface and the initiation of the addition operation for the multiple devices to be added. For example, the user can click the "Select All" control shown in (b) of Figure 5f to select multiple devices to be added, and click the "Agree and Connect" control to initiate the addition operation for the selected multiple devices to be added.

[0342] In some embodiments, the controls in the first interface further include a first control for turning on or off the batch adding function. When the first control is turned on, the first interface allows selection of multiple devices to be added. When the first control is turned off, the first interface does not allow selection of multiple devices to be added. For example, the first control may be the "Allow Batch Connection" control shown in (b) of Figure 5f.

[0343] In some embodiments, the first interface includes a first device display area and a second device display area, the first device display area is used to display devices that support batch addition, and the second device display area is used to display devices that do not support batch addition. The second operation includes selecting multiple devices to be added in the first device display area when the first control is in an open state. For example, the first device display area can be the first device display area that can be connected in batch as shown in (b) of Figure 5f, and the second device display area can be the second device display area that cannot be connected in batch as shown in (b) of 5f.

[0344] In some embodiments, if the number of remaining connectable gateway devices is less than the number of devices to be added selected in the first device display area, a first window is opened, covering a portion of the first interface. The first window may include a warning message regarding the number of remaining connectable gateway devices. For example, the first window may be the abnormality prompt box shown in (a) of Figure 12a, and the warning message may be: "The gateway can only connect to x more sub-devices. Reduce the number of devices and try again."

[0345] In some embodiments, the method for adding devices in batches may further include: receiving a third operation from the user on the first interface when the first control is in a closed state, the third operation including selecting a device to be added on the first interface for addition; and initiating the addition of the selected device to be added in response to the third operation. For example, initiating the addition of the selected device to be added may include controlling the gateway device to establish a connection with the selected device to be added, and registering the selected device to be added with a server corresponding to the smart device management application. For example, the server corresponding to the smart device management application is the server shown in FIG3 . In this way, devices that do not support batch addition can be independently added.

[0346] S134: In response to the second operation, initiate batch addition of multiple devices to be added.

[0347] In response to the second operation, the terminal device may initiate a batch addition of multiple devices to be added. For example, initiating the batch addition of multiple devices to be added may include controlling the gateway device to establish a connection with the multiple devices to be added and registering the multiple devices to be added with a server corresponding to the smart device management application, thereby implementing the batch addition of the multiple devices to be added. For example, after the user clicks the "Agree and Connect" control, the terminal device may control the gateway device to establish a connection with the multiple selected devices to be added and register the multiple devices to be added with the server corresponding to the smart device management application.

[0348] In some embodiments, when the gateway device scans for devices to be added of a specified device category, since the devices being added are devices of the specified device category, the specified device category may be a device category that supports batch addition or a device category that does not support batch addition, the first interface may include only one device display area (for example, referred to as the third device display area), which may be the device display area in the device selection interface shown in (c) of Figure 6e. When the first control is turned on and the devices displayed in the third device display area are devices that support batch addition, the second operation includes selecting multiple devices to be added in the third device display area for batch addition.

[0349] In some embodiments, the method for adding devices in batches may further include: if the number of remaining connectable gateway devices is less than the number of multiple devices to be added selected in the third device display area, opening a second window, the second window overlaying a portion of the first interface, and including a warning message regarding the remaining number of connectable gateway devices. For example, the warning message may read "The gateway can only connect to x more sub-devices. Reduce devices and try again." The second window may be designed with the same style as the first window.

[0350] S135, displaying a second interface, which displays batch addition results of multiple devices to be added.

[0351] In some embodiments, the batch addition results of multiple devices to be added may include the addition results of each device to be added in the multiple devices to be added, and the addition results include addition success or addition failure. Adding success can be that the device to be added establishes a connection with the gateway device and is successfully registered on the server. Adding failure can be that the device to be added fails to establish a connection with the gateway device or fails to register on the server. The addition results of each device to be added in the multiple devices to be added are displayed through a second interface. For example, the second interface can be the connection result interface shown in (a) of Figure 5g.

[0352] In some embodiments, the second interface includes a first connection result display area, a second connection result display area, and a connection suggestion display area. The first connection result display area is used to display successfully added devices, the second connection result display area is used to display failed devices, and the connection suggestion display area is used to display suggested solutions for failed additions. For example, the suggested solution may be the "Solution" in the connection result interface shown in (a) of Figure 5g.

[0353] In some embodiments, the smart device management application further includes a third interface. Before displaying the second interface, the method for adding devices in batches further includes: displaying the third interface, the third interface including the addition progress of each of the multiple devices to be added and the total addition progress of the multiple devices to be added. For example, the third interface is the batch device connection interface shown in (c) of Figure 5f.

[0354] In some embodiments, the third interface further includes a first progress display area, a second progress display area, and a third progress display area. The first progress display area is used to display devices being added, the second progress display area is used to display devices that have been successfully added, and the third progress display area is used to display devices that have failed to be added. For example, the third interface is the batch device connection interface shown in (c) of Figure 10a.

[0355] In some embodiments, launching the smart device management application in response to the first operation may include: launching the smart device management application in response to the first operation and entering the home page interface of the smart device management application; opening a third window, the third window covering part of the content of the home page interface; receiving a fourth operation from the user on the third window; and opening the first interface in response to the fourth operation. For example, the home page interface of the smart device management application is the smart space home page interface shown in (a) of Figure 8a. The third window may be the device discovery pop-up window shown in (a) of Figure 7a. The fourth operation may be an operation in which the user clicks on a control in the device discovery pop-up window.

[0356] In some embodiments, the third window includes a second control for triggering the addition of a device, a first pattern corresponding to a gateway device, and a second pattern corresponding to the devices to be added scanned by the gateway device, wherein the number of second patterns is associated with the number of devices to be added scanned by the gateway device. The third operation is a click operation on the second control. For example, the second control is the "Connect" control in the device discovery pop-up window shown in (a) of Figure 7a. The first pattern corresponding to the gateway device can be the gateway pattern shown in Figure 11, and the second pattern corresponding to the scanned devices to be added can be the multiple device patterns shown in Figure 11.

[0357] In some embodiments, opening the first interface in response to the fourth operation includes: opening a fourth window in response to the fourth operation, if the number of remaining connectable gateway devices is less than or equal to a preset number, or if the number of remaining connectable gateway devices is less than the number of devices to be added scanned by the gateway device, the fourth window overlaying a portion of the homepage interface, the fourth window including warning information about the gateway device and a third control for triggering device addition; and opening the first interface in response to clicking the third control. The fourth window may be the warning prompt box shown in (b) of FIG. 12c , and the third control may be the "Continue Connecting" control in the warning prompt box shown in (b) of FIG. 12c .

[0358] Figure 14 is a structural diagram of an apparatus for a batch adding device provided in an embodiment of the present application. As shown in Figure 14, the apparatus for the batch adding device may include: a display screen 1001, a memory 1002, a processor 1003, and a communication module 1004. The above-mentioned components may be connected via one or more communication buses 1005. The display screen 1001 may include a display panel 10011 and a touch sensor 10012, wherein the display panel 10011 is used to display an image, and the touch sensor 10012 may transmit the detected touch operation to the application processor to determine the type of touch event and provide a visual output related to the touch operation through the display panel 10011. The processor 1003 may include one or more processing units, for example: the processor 1003 may include an application processor, a modem processor, a graphics processor, an image signal processor, a controller, a video codec, a digital signal processor, a baseband processor, and / or a neural network processor, etc. Among them, different processing units may be independent devices or integrated into one or more processors. The memory 1002 is coupled to the processor 1003 and is used to store various software programs and / or computer instructions. The memory 1002 may include a volatile memory and / or a non-volatile memory. When the processor executes the computer instructions, the terminal device may perform the various functions or steps in the above method embodiments.

[0359] An embodiment of the present application also provides a computer storage medium, in which computer instructions are stored. When the computer instructions are executed on the terminal device 100, the terminal device 100 executes the above-mentioned related method steps to implement the method of batch adding devices in the above-mentioned embodiment.

[0360] An embodiment of the present application further provides a computer program product, which, when executed on a terminal device, enables the terminal device to execute the aforementioned related steps to implement the method for adding devices in batches in the aforementioned embodiment.

[0361] In addition, an embodiment of the present application also provides a device, which can specifically be a chip, component or module, and the device may include a connected processor and memory; wherein the memory is used to store computer-executable instructions, and when the device is running, the processor can execute the computer-executable instructions stored in the memory to enable the chip to execute the method of batch adding devices in the above-mentioned method embodiments.

[0362] Among them, the computer storage medium, computer program product or chip provided in the embodiments of the present application are all used to execute the corresponding methods provided above. Therefore, the beneficial effects that can be achieved can refer to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0363] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0364] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are schematic. For example, the division of the modules or units is a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

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

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

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

[0368] The above description is only a specific implementation method of the present application, but the protection scope of the present application is not limited thereto. Any changes or replacements within the technical scope disclosed in the present application should be included in the protection scope of the present application.< / canvas> < / video> < / videoview> < / imgview> < / textview>

Claims

1. A method for batch adding devices, applied to a terminal device, characterized in that, The terminal device is installed with a smart device management application, and the method includes: In response to a first operation of the user, start the smart device management application and display a first interface, where the first interface includes a control for batch adding devices; In response to a second operation of the user on the control in the first interface, initiate batch addition of multiple devices to be added. The control is used to trigger selection of the multiple devices to be added in the first interface and initiate batch addition of the multiple devices to be added; Display a second interface, where the second interface displays the batch addition results of the multiple devices to be added.

2. The method for batch adding devices according to claim 1, characterized in that, The control includes a first control for enabling or disabling the batch addition function. When the first control is in the enabled state, the first interface allows selection of the multiple devices to be added. When the first control is in the disabled state, the first interface does not allow selection of the multiple devices to be added.

3. The method for batch adding devices according to claim 2, wherein When the first control is in the enabled state, the first interface includes a first device display area and a second device display area. The first device display area is used to display devices that support batch addition, and the second device display area is used to display devices that do not support batch addition. The second operation includes selecting the multiple devices to be added in the first device display area.

4. The method for batch adding devices according to claim 3, wherein The terminal device has established a communication connection with a gateway device. The initiating batch addition of multiple devices to be added includes: Controlling the gateway device to establish connections with the multiple devices to be added and registering the multiple devices to be added to a server corresponding to the smart device management application.

5. The method for batch adding devices according to claim 4, characterized in that, The method further includes: When the remaining available connection number of the gateway device is less than the number of the multiple devices to be added selected in the first device display area, open a first window that covers part of the content of the first interface. The first window includes a warning prompt message about the remaining available connection number of the gateway device.

6. The method for batch adding devices according to claim 4, wherein When the gateway device scans devices to be added of a specified device category, the first interface includes a third device display area. When the first control is in the enabled state and the devices displayed in the third device display area are devices that support batch addition, the second operation includes selecting the multiple devices to be added in the third device display area.

7. The method for batch adding devices according to claim 6, characterized in that, The method further includes: When the remaining available connection number of the gateway device is less than the number of the multiple devices to be added selected in the third device display area, open a second window that covers part of the content of the first interface. The second window includes a warning prompt message about the remaining available connection number of the gateway device.

8. The method for batch adding devices according to claim 4, wherein The batch addition results of the multiple devices to be added include the addition results of each device to be added among the multiple devices to be added. The addition result includes addition success or addition failure. Addition success means establishing a connection with the gateway device and successfully registering on the server. Addition failure means failing to establish a connection with the gateway device or failing to register on the server.

9. The method for batch adding devices according to claim 8, characterized in that, The second interface includes a first connection result display area, a second connection result display area, and a connection suggestion display area. The first connection result display area is used to display the devices successfully added, the second connection result display area is used to display the devices with failed addition, and the connection suggestion display area is used to display the suggested solutions for the failed addition.

10. The method for the batch addition device according to any one of claims 1 to 9, characterized in that, Before displaying the second interface, it further includes: Displaying a third interface, which includes the addition progress of each device to be added among the multiple devices to be added and the total addition progress of the multiple devices to be added.

11. The method for batch adding devices according to claim 10, characterized in that, The third interface further includes a first progress display area, a second progress display area, and a third progress display area. The first progress display area is used to display the devices being added, the second progress display area is used to display the devices successfully added, and the third progress display area is used to display the devices with failed addition.

12. The method for batch adding devices according to claim 2, wherein The method further includes: In the case where the first control is in the closed state, receiving a third operation from the user for the first interface, where the third operation includes selecting a device to be added on the first interface for addition; In response to the third operation, initiating the addition of the selected device to be added.

13. The method for batch adding devices according to claim 12, wherein The terminal device has a communication connection with the gateway device. The initiating the addition of the selected device to be added includes: Controlling the gateway device to establish a connection with the selected device to be added, and registering the selected device to be added to the server corresponding to the intelligent device management application.

14. The method for batch adding devices according to claim 1, characterized in that, The terminal device has a communication connection with the gateway device. The responding to the user's first operation, starting the intelligent device management application, and displaying the first interface includes: Responding to the user's first operation, starting the intelligent device management application, and displaying the home page interface of the intelligent device management application; Opening a third window that covers part of the content of the home page interface, and the third window displays the information of the devices to be added scanned by the gateway device; Responding to the user's fourth operation for the third window, displaying the first interface.

15. The method for batch adding devices according to claim 14, characterized in that, The third window includes a second control for triggering device addition, a first pattern corresponding to the gateway device, and a second pattern corresponding to the devices to be added scanned by the gateway device. The fourth operation is a click operation on the second control, and the number of the second patterns is associated with the number of the devices to be added scanned by the gateway device.

16. The method for batch adding devices according to claim 14, characterized in that, The responding to the user's fourth operation for the third window and displaying the first interface includes: Responding to the user's fourth operation for the third window, and when the remaining connectable quantity of the gateway device is less than or equal to a preset quantity, or the remaining connectable quantity of the gateway device is less than the number of the devices to be added scanned by the gateway device, opening a fourth window that covers part of the content of the home page interface. The fourth window includes the warning prompt information of the gateway device and a third control for triggering device addition; Responding to the click operation of the user on the third control, displaying the first interface.

17. A computer-readable storage medium, characterized in that, Including computer instructions, when the computer instructions are run on a processor, the terminal device is caused to execute the method for batch adding devices as described in any one of claims 1 to 16.

18. A terminal device, characterized in that, The terminal device includes a processor and a memory, the memory is used for storing instructions, and the processor is used for calling the instructions in the memory, so that the terminal device executes the method for batch adding devices as described in any one of claims 1 to 16.

Images