A management method and a terminal for an IoT device

Abstract

A management method and terminal for IoT devices, which relate to the field of the Internet of Things, can simplify user operations, realize user - perceptionless network configuration and one - key access control experience, and improve the user experience. The method includes: after the IoT device receives a first input, it sends the identifier of the IoT device and the registration status of the IoT device by means of short - range communication; when the mobile terminal is within a preset distance from the IoT device, it can receive a first message; when the registration status of the IoT device indicates that the IOT device is registered, the mobile terminal displays the control interface of the IoT device; when the registration status of the IoT device indicates that the IOT device is not registered, the mobile terminal automatically starts to configure the network for the IoT device.

Description

Technical Field

[0001] The present application relates to the field of Internet of Things, and in particular to a management method and terminal for IoT devices. Background Art

[0002] With the rapid development of Internet of Things technology, more and more IoT devices are connected to home networks. Users can access and manage IoT devices by installing applications (applications, APPs) such as "Smart Life" (also known as home APPs, IoT APPs, etc.) on mobile terminals.

[0003] For example, Figure 1 (1) is a schematic diagram of the process of configuring the IoT device through the APP on the mobile phone. Specifically, the user needs to open the APP on the mobile phone, and then click the control to add the IoT device, and the mobile phone starts to scan the surrounding IoT devices. The mobile phone displays a list of scanned surrounding IoT devices. The user selects the IoT device that needs to be configured from the list, and then enters the WiFi network password, the PIN of the IoT device, etc. The mobile phone starts to configure the IoT device and register it. It can be seen that in the process of configuring the IoT device, the user needs to perform at least five steps. For example, Figure 1 As shown in (2), it is a schematic diagram of the process of controlling IoT devices through an APP on a mobile phone. Specifically, the user needs to open the APP, find the IoT device to be controlled from the list of IoT devices, then select the IoT device to be controlled, enter the control interface, and then select the action to be performed by the IoT device from the control interface. Then, the control command is sent to the IoT device, and the IoT device performs the corresponding action. It can be seen that in the process of controlling IoT devices, the user needs to perform at least four steps. In summary, it can be seen that the existing solutions in the industry for managing and controlling IoT devices through APP have the problem of lengthy and cumbersome user operation processes. Summary of the invention

[0004] The present application provides a control method for an IoT device, which can simplify user operations, realize seamless network configuration and one-click control experience, and improve user experience.

[0005] In order to achieve the above objectives, the embodiments of the present application provide the following technical solutions:

[0006] First aspect: Provide a management system for IoT devices, including: a mobile terminal and an IoT device, where the IoT device has short-range communication capabilities; the mobile terminal stores network configuration information and communicates with the server using the network configuration information; the IoT device is used to receive a first input, send a first message in a short-range communication manner, and the first message includes the identifier of the IoT device and the registration status of the IoT device; the mobile terminal is used to receive the first message sent by the IoT device within a preset distance from the IoT device; the mobile terminal is further used to, when the registration status indicates that the IoT device is not registered, request a registration code from the server and send the registration code and the network configuration information to the IoT device, and the registration code and the network configuration information are used for the IoT device to apply for registration with the server.

[0007] Among them, the short-range communication manner can be NFC, Wi-Fi Aware, low-power Bluetooth, etc.

[0008] It can be understood that when the IoT device sends the first information in a short-range communication manner, other devices (such as mobile terminals) can only receive the first information within an ultra-short distance (i.e., the distance threshold) from the IoT device. In other words, in a real usage scenario, if a device can receive the first information sent by the IoT device, it means that the device is very close to the IoT device, and this device can be considered a trusted device of the IoT device. In this article, the distance range that can receive the ultra-short-range wireless signal sent by the IoT device can be called the security distance. That is to say, the embodiments of the present application utilize the security distance of ultra-short-range wireless communication to physically ensure the security of the first information sent by the IoT device.

[0009] Thus, it can be seen that when the mobile terminal approaches the IoT device, if the IoT device is not registered, the mobile terminal can automatically configure the network for the IoT device. And in the network configuration process of the IoT device, there is no need for the user to scan the label of the IoT device, select the Wi-Fi network password, the IoT device PIN, and other cumbersome operations. It can be seen that the method provided by the embodiments of the present application simplifies the user operation and realizes the effect of seamless network configuration.

[0010] In a possible implementation manner, the IoT device is further used to, after receiving the first input or before sending the first message, prompt the user to bring the mobile terminal closer to the IoT device; among them, the prompting manner of the IoT device includes one or more of playing a prompting voice, flashing a prompting light, and displaying a prompting interface.

[0011] In this way, it is convenient for the user to bring the mobile terminal closer to the IoT device, so that the distance between the mobile terminal and the IoT device is within the preset distance, so as to receive the first message.

[0012] In one possible implementation, the first input includes any one of the operations of powering on the IoT device, operating a specific button on the IoT device, instructing the IoT device to enter the network configuration mode, and restarting the IoT device.

[0013] In one possible implementation, the identifier of the IoT device includes one or more of the device model, personal identification number (PIN), and media access control (MAC) address.

[0014] Among them, the device model can be used to identify the IoT device. Generally, the IoT device is named after the device model, and the device icon corresponding to the IoT device is determined according to the device model. The PIN is the root key for key negotiation in the subsequent network configuration process and is used for security authentication. The MAC address is the unique identifier of the IoT device and is used to distinguish it from other IoT devices. The network configuration status is used to mark whether the IoT device has been network-configured, and the subsequent mobile terminal executes different processes according to the network configuration status.

[0015] In one possible implementation, the mobile terminal is further configured to receive the message indicating the successful registration of the IoT device sent by the server and update the registration status of the IoT device.

[0016] In one possible implementation, the mobile terminal is further configured to display a control interface when the registration status indicates that the IoT device has been registered. The control interface includes controls for operating the IoT device.

[0017] Thus, when the mobile terminal approaches the IoT device, if the IoT device is not registered, the mobile terminal can automatically perform network configuration for the IoT device and display the control interface. If the IoT device is already registered, the mobile terminal can display the control interface. In this way, the user can directly operate the control interface to start operating the IoT device. That is, the method provided in the embodiments of the present application can automatically execute different processes, network configuration or control, according to the network configuration status of the IoT device, simplifies the user operation, achieves a one-touch control experience, and is conducive to enhancing user stickiness.

[0018] Moreover, since the mobile terminal can obtain the unique MAC address of the IoT device when approaching it. When there are multiple IoT devices of the same device model in the surrounding environment, the mobile terminal can also perform network configuration and operation on the IoT device that the user approaches.

[0019] In one possible implementation, when the registration status indicates that the IoT device has been registered, the mobile terminal displays the control interface, including: after receiving the first message, when the registration status indicates that the IoT device has been registered, the mobile terminal displays the control interface; or, after receiving the message indicating the successful registration of the IoT device sent by the server and updating the registration status of the IoT device to registered, the mobile terminal displays the control interface.

[0020] It can be understood that the mobile terminal controls the IoT device by adopting the GUI management method, which can be unaffected by the noise of the surrounding environment and has better robustness, facilitating more accurate control of the IoT device.

[0021] In a possible implementation manner, when the registration status indicates that the IoT device has been registered, the mobile terminal displays a control interface, including: the mobile terminal automatically launches the first application and displays the control interface of the first application; or, the mobile terminal calls the system service to display a pop-up window containing the control interface.

[0022] In some examples, the mobile terminal can automatically launch the first application to implement the function of the user controlling the IoT device. In other examples, the mobile terminal can also sink the capabilities and data related to the network configuration process and the control process in the first application to the framework layer. That is, set the services related to the network configuration process and the control process in the first application as system services. In this way, after receiving the first message, the mobile terminal can also directly use the system service to display the control interface of the IoT device without launching the first application to implement the user's control of the IoT device.

[0023] In a possible implementation manner, the mobile terminal is further configured to play a voice to prompt the user to control the IoT device by voice when the registration status indicates that the IoT device has been registered.

[0024] In a possible implementation manner, when the registration status indicates that the IoT device has been registered, the mobile terminal plays a voice to prompt the user to control the IoT device by voice, including: after receiving the first message, when the registration status indicates that the IoT device has been registered, the mobile terminal plays a voice; or, after receiving the message of successful registration of the IoT device sent by the server, when the mobile terminal updates the registration status of the IoT device to registered, the mobile terminal plays a voice.

[0025] It should be noted that in the existing management method of VUI, the user needs to wake up the control device (i.e., the mobile terminal) by saying the wake-up word, and then accept the user's voice command. In this solution, there is no need for the user to say the wake-up word. In addition, in the existing management method of VUI, the IoT device is generally referred to by its device model. For example, the user says "Turn on the smart speaker". Among them, the smart speaker is the device that the user wants to control. However, when there are IoT devices with the same device model in the surrounding environment, the control device will not be able to distinguish which IoT device the user wants to turn on. Then, in the solution of this application, when the user holds the mobile terminal close to an IoT device, the first information sent by the IoT device includes not only the device model of the IoT device, but also the MAC address of the IoT device, which can be used to distinguish the IoT device that the user wants to control this time.

[0026] In a second aspect, a mobile terminal is provided, including: a processor and a memory, the memory is coupled to the processor, the memory is used to store computer program code, the computer program code includes computer instructions, when the processor reads the computer instructions from the memory, so that the mobile terminal performs the following operations: within a preset distance from the IoT device, receive a first message sent by the IoT device, the first message includes the identifier of the IoT device and the registration status of the IoT device, and the first message is sent by the IoT device using short-range communication; when the registration status indicates that the IoT device is not registered, request a registration code of the IoT device from the server, and send the registration code and the network configuration information saved locally to the IoT device, the registration code and the network configuration information are used for the IoT device to apply for registration with the server.

[0027] In a possible implementation, the identifier of the IoT device includes one or more of a device model, a personal identification number PIN, and a media access control MAC address.

[0028] In a possible implementation, the mobile terminal also performs: receive a message indicating that the registration of the IoT device is successful sent by the server, and update the registration status of the IoT device.

[0029] In a possible implementation, the mobile terminal also performs: when the registration status indicates that the IoT device is already registered, display a control interface, and the control interface includes controls for controlling the IoT device.

[0030] In a possible implementation, when the registration status indicates that the IoT device is already registered, the mobile terminal displays a control interface, including: after receiving the first message, when the registration status indicates that the IoT device is already registered, the mobile terminal displays a control interface; or, after receiving a message indicating that the registration of the IoT device is successful sent by the server, when the mobile terminal updates the registration status of the IoT device to already registered, the mobile terminal displays a control interface.

[0031] In a possible implementation, when the registration status indicates that the IoT device is registered, the mobile terminal displays a control interface, including: the mobile terminal automatically launches a first application and displays the control interface of the first application; or, the mobile terminal invokes a system service to display a pop-up window containing the control interface.

[0032] In a possible implementation, the mobile terminal also performs: when the registration status indicates that the IoT device is registered, play a voice to prompt the user to control the IoT device by voice.

[0033] In a possible implementation, when the registration status indicates that the IoT device is registered, the mobile terminal plays a voice to prompt the user to control the IoT device by voice, including: after receiving a first message, when the registration status indicates that the IoT device is registered, the mobile terminal plays a voice; or, after receiving the message that the IoT device registration is successful sent by the server, when the mobile terminal updates the registration status of the IoT device to registered, the mobile terminal plays a voice.

[0034] In a third aspect, there is provided an IoT device, including: a processor, a memory, and a short-range communication module. The memory and the short-range communication module are coupled to the processor. The memory is used to store computer program code, and the computer program code includes computer instructions. When the processor reads the computer instructions from the memory, the IoT device is caused to perform the following operations: upon receiving a first input, send a first message through the short-range communication module, where the first message includes the identifier of the IoT device and the registration status of the IoT device; wherein, the identifier of the IoT device and the registration status of the IoT device are used to instruct the mobile terminal to apply for a registration code of the IoT device, and return the registration code and the network configuration information saved by the mobile terminal to the IoT device; after receiving the registration code and the network configuration information returned by the mobile terminal, apply for registration with the server.

[0035] In a possible implementation, it also performs: after receiving the first input, or before sending the first message, prompt the user to bring the mobile terminal close to the IoT device; wherein, the prompting method of the IoT device includes one or more of playing a prompting voice, flashing a prompting light, and displaying a prompting interface.

[0036] In a possible implementation, the first input includes any one of the operations of powering on the IoT device, operating a specific button on the IoT device, instructing the IoT device to enter the network configuration mode, and restarting the IoT device.

[0037] In a possible implementation, the identifier of the IoT device includes one or more of the device model, personal identification number (PIN), and media access control (MAC) address.

[0038] Fourth aspect: Provide a management method for IoT devices, which is applied to a mobile terminal. The method includes: within a preset distance from the IoT device, receiving a first message sent by the IoT device. The first message contains the identification of the IoT device and the registration status of the IoT device, and the first message is sent by the IoT device using short-range communication; when the registration status indicates that the IoT device is not registered, requesting a registration code for the IoT device from the server, and sending the registration code and the network configuration information saved locally to the IoT device. The registration code and the network configuration information are used for the IoT device to apply for registration with the server.

[0039] In a possible implementation, the identification of the IoT device includes one or more of the device model, personal identification number (PIN), and media access control (MAC) address.

[0040] In a possible implementation, it further includes: receiving a message indicating that the registration of the IoT device is successful sent by the server, and updating the registration status of the IoT device.

[0041] In a possible implementation, it further includes: when the registration status indicates that the IoT device is registered, displaying a control interface, and the control interface includes controls for operating the IoT device.

[0042] In a possible implementation, when the registration status indicates that the IoT device is registered, displaying the control interface includes: after receiving the first message, when the registration status indicates that the IoT device is registered, displaying the control interface; or, after receiving the message indicating that the registration of the IoT device is successful sent by the server and updating the registration status of the IoT device to registered, displaying the control interface.

[0043] In a possible implementation, when the registration status indicates that the IoT device is registered, displaying the control interface includes: automatically launching the first application and displaying the control interface of the first application; or, invoking the system service to display a pop-up window containing the control interface.

[0044] In a possible implementation, it further includes: when the registration status indicates that the IoT device is registered, playing a voice to prompt the user to control the IoT device by voice.

[0045] In a possible implementation, when the registration status indicates that the IoT device is registered, playing a voice to prompt the user to control the IoT device by voice includes: after receiving the first message, when the registration status indicates that the IoT device is registered, playing the voice; or, after receiving the message indicating that the registration of the IoT device is successful sent by the server and updating the registration status of the IoT device to registered, playing the voice.

[0046] Fifth aspect: Provide a management method for IoT devices, which is applied to IoT devices. The method includes: receiving a first input, and sending a first message through a short-range communication module. The first message contains the identifier of the IoT device and the registration status of the IoT device. The identifier of the IoT device and the registration status of the IoT device are used to instruct the mobile terminal to apply for a registration code for the IoT device, and return the registration code and the network configuration information saved by the mobile terminal to the IoT device. After receiving the registration code and the network configuration information returned by the mobile terminal, apply for registration with the server.

[0047] In a possible implementation, it further includes: after receiving the first input, or before sending the first message, prompting the user to bring the mobile terminal close to the IoT device. The prompting method of the IoT device includes one or more of playing a prompting voice, flashing a prompting light, and displaying a prompting interface.

[0048] In a possible implementation, the first input includes any one of the operations of powering on the IoT device, operating a specific key on the IoT device, instructing the IoT device to enter the network configuration mode, and restarting the IoT device.

[0049] In a possible implementation, the identifier of the IoT device includes one or more of the device model, personal identification number (PIN), and media access control (MAC) address.

[0050] Sixth aspect: Provide a computer program product. When the computer program product runs on a computer, it causes the computer to execute the method described in the above aspect and any one of the possible implementations thereof.

[0051] Seventh aspect: Provide a chip system, including a processor. When the processor executes instructions, the processor executes the method described in the above aspect and any one of the possible implementations thereof.

[0052] Eighth aspect: Provide a device. The device is included in a mobile terminal and has the function of implementing the behavior of the mobile terminal in any of the methods described in the above aspect and possible implementations. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above function. For example, a receiving module or unit, a display module or unit, and a processing module or unit, etc.

[0053] In a ninth aspect, a device is provided. The device is included in an IoT device and has the function of implementing the behavior of the IoT device in any of the methods in the above aspects and possible implementation manners. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above function. For example, a receiving module or unit, a sending module or unit, etc.

[0054] In a tenth aspect, a computer-readable storage medium is provided, including computer instructions. When the computer instructions run on a mobile terminal, the mobile terminal is caused to execute the method described in the above aspects and any of the possible implementation manners thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0055] Figure 1 It is a schematic diagram of the process of network configuration and control of an IoT device in the prior art;

[0056] Figure 2 It is a schematic diagram of the system architecture of an application scenario provided by an embodiment of the present application;

[0057] Figure 3A It is a schematic diagram of the structure of a mobile terminal provided by an embodiment of the present application;

[0058] Figure 3B It is a schematic diagram of the structure of another mobile terminal provided by an embodiment of the present application;

[0059] Figure 4 It is a schematic diagram of the structure of an IoT device provided by an embodiment of the present application;

[0060] Figure 5A It is a schematic diagram of the structure of another IoT device provided by an embodiment of the present application;

[0061] Figure 5B It is a schematic diagram of the structure of another IoT device provided by an embodiment of the present application;

[0062] Figure 6 It is a schematic diagram of the flow of a control method for an IoT device provided by an embodiment of the present application;

[0063] Figure 7A It is a schematic diagram of the graphical user interface of some other mobile terminals provided by an embodiment of the present application;

[0064] Figure 7B It is a schematic diagram of the graphical user interface of some other mobile terminals provided by an embodiment of the present application;

[0065] Figure 7C It is a schematic diagram of the voice user interface of some other mobile terminals provided by an embodiment of the present application;

[0066] Figure 8 Schematic diagram of a chip system provided by an embodiment of the present application;

[0067] Figure 9 Schematic diagram of another chip system provided by an embodiment of the present application. Detailed implementation manners

[0068] In the description of the embodiments of the present application, unless otherwise specified, " / " means "or". For example, A / B may mean A or B; herein, "and / or" is merely a description of the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B may mean: A exists alone, A and B exist simultaneously, and B exists alone.

[0069] Hereinafter, the terms "first" and "second" are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, features defined with "first" and "second" may explicitly or implicitly include one or more of such features. In the description of the embodiments of the present application, unless otherwise specified, the meaning of "a plurality" is two or more.

[0070] In the embodiments of the present application, words such as "exemplary" or "for example" are used to represent examples, illustrations or explanations. Any embodiment or design solution described as "exemplary" or "for example" in the embodiments of the present application should not be construed as being more preferred or having more advantages than other embodiments or design solutions. Rather, the use of words such as "exemplary" or "for example" is intended to present relevant concepts in a specific manner.

[0071] At present, with the rise of smart devices such as smart speakers and smart screens, the management method of voice user interface (VUI) can simplify the user operations involved in the network configuration and control process of IoT devices to a certain extent. Generally, in the VUI management method, users need to wake up the smart speaker or smart screen at home by saying the wake-up word, and then control the device through voice commands. However, the VUI management method still has some defects. For example, the VUI management method is not suitable for some processes that rely heavily on APP operations, such as the network configuration of IoT devices. For another example, because the VUI management method requires voice recognition and semantic recognition of the voice commands issued by the user. When the environment is noisy, it is easy to cause voice recognition errors or semantic recognition errors, which in turn leads to the control results of the IoT device being different from the user's expectations. For another example, if there are multiple IoT devices of the same type or model at home, the voice command method may not be able to accurately control which IoT device. For another example, every time an IoT device is controlled, the user needs to say the wake-up word to wake up the smart speaker or smart screen, and the user experience is not good. To this end, an IoT device control method provided in an embodiment of the present application can simplify user operations, realize user-free network configuration, and achieve a one-click control experience, which is conducive to improving the user experience.

[0072] like Figure 2 As shown, a schematic diagram of a system architecture of an application scenario provided in an embodiment of the present application is provided. The system architecture includes at least one mobile terminal 100, at least one IoT device 200, and a server 300.

[0073] The mobile terminal 100 is used to bind the IoT device 200. The mobile terminal 100 can configure the IoT device 200, and control the IoT device 200 to perform corresponding actions. In some examples, the mobile terminal 100 can be, for example, a mobile phone, a tablet computer, a personal computer (PC), a personal digital assistant (PDA), a smart watch, a netbook, a wearable electronic device, etc. The present application does not impose any special restrictions on the specific form of the mobile terminal 100.

[0074] The above IoT device 200 can be, for example, a hardware device for a smart home, and can include a mobile terminal, household appliances, sensor devices, etc. For example: The IoT device 200 can be a smart phone, smart speaker, smart refrigerator, smart TV, smart light, smart socket, air purifier, humidifier, smart range hood, smart table lamp, smart door lock, smart power strip, smart induction cooker, smart camera, etc. The IoT device 200 can also be a smoke sensor, human body sensor, temperature sensor, humidity sensor, door and window sensor, PM2.5 air sensor, etc.

[0075] The above server 300 can be, for example, a cloud server, a home cloud server, etc., or can also be a server cluster composed of multiple servers. In some embodiments, the mobile terminal 100 can request the server 300 to register the IoT device 200. In this way, the server 300 records the home APP account information bound to the IoT device 200. That is to say, the server 300 stores the relevant control information of the IoT device 200, such as the account of the home application (such as the "Smart Life" application) or the IoT device application (such as the smart speaker application) logged in by the IoT device 200, and the device identifier of the IoT device 200, etc. Further, when the mobile terminal 100 needs to control the IoT device 200 to perform corresponding actions, it can send the corresponding control commands to the IoT device 200 through the server 300.

[0076] Please refer to Figure 3A , Figure 3A which shows a schematic structural diagram of a mobile terminal 100.

[0077] The mobile terminal 100 can 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, a headphone 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. Among them, the sensor module 180 can include a pressure sensor 180A, a gyroscope sensor 180B, a barometric 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.

[0078] It can be understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the mobile terminal 100. In other embodiments of this application, the mobile terminal 100 may include more or fewer components than those illustrated, or combine certain components, or split certain components, or have different component arrangements. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

[0079] 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), etc. Among them, different processing units may be independent devices or integrated in one or more processors.

[0080] A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in the processor 110 is a cache memory. This memory may save the instructions or data that the processor 110 has just used or recycled. If the processor 110 needs to use the instruction or data again, it can directly call it from the memory. This avoids repeated accesses, reduces the waiting time of the processor 110, and thus improves the efficiency of the system.

[0081] 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, etc.

[0082] It can be understood that the interface connection relationships among the modules illustrated in the embodiments of the present application are only illustrative descriptions and do not constitute a structural limitation on the mobile terminal 100. In other embodiments of the present application, the mobile terminal 100 may also adopt different interface connection methods in the above embodiments, or a combination of multiple interface connection methods.

[0083] The charging management module 140 is configured to receive a charging input from a charger. The charger may be a wireless charger or a wired charger. In some embodiments of wired charging, the charging management module 140 may receive the charging input of the wired charger through the USB interface 130. In some embodiments of wireless charging, the charging management module 140 may receive the wireless charging input through the wireless charging coil of the mobile terminal 100. While charging the battery 142, the charging management module 140 may also supply power to the electronic device through the power management module 141.

[0084] 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 the inputs from the battery 142 and / or the charging management module 140 and supplies power to the processor 110, the internal memory 121, the display screen 194, the camera 193, the wireless communication module 160, etc. The power management module 141 may also be used to monitor parameters such as the battery capacity, the number of battery cycles, and the battery health status (leakage, impedance). In some other embodiments, the power management module 141 may also be disposed in the processor 110. In some other embodiments, the power management module 141 and the charging management module 140 may also be disposed in the same device.

[0085] The wireless communication function of the mobile terminal 100 can be implemented by the antenna 1, antenna 2, mobile communication module 150, wireless communication module 160, modulation and demodulation processor, baseband processor, etc.

[0086] The mobile communication module 150 can provide solutions for wireless communications such as 2G / 3G / 4G / 5G applied to the mobile terminal 100. The mobile communication module 150 can include at least one filter, switch, power amplifier, low noise amplifier (LNA), etc. The mobile communication module 150 can receive electromagnetic waves through the antenna 1, filter and amplify 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 through the antenna 1 for radiation. In some embodiments, at least some functional modules of the mobile communication module 150 can be provided in the processor 110. In some embodiments, at least some functional modules of the mobile communication module 150 and at least some modules of the processor 110 can be provided in the same device.

[0087] The wireless communication module 160 can provide solutions for wireless communications such as 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 technology (IR), etc. applied to the mobile terminal 100. The wireless communication module 160 can be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves through the antenna 2, performs frequency modulation and filtering processing on the electromagnetic wave signals, and sends the processed signals to the processor 110. The wireless communication module 160 can also receive the signals to be sent from the processor 110, perform frequency modulation and amplification on them, and convert them into electromagnetic waves through the antenna 2 for radiation.

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

[0089] Mobile terminal 100 implements a display function through a GPU, display screen 194, and an application processor, etc. The GPU is a microprocessor for image processing, and is connected to display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs, which execute program instructions to generate or change display information.

[0090] Mobile terminal 100 can implement a shooting function through an ISP, camera 193, video codec, GPU, display screen 194, and an application processor, etc.

[0091] The internal memory 121 can be used to store computer-executable program code, and the executable program code includes instructions. The internal memory 121 can include a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function (such as a sound playback function, an image playback function, etc.). The data storage area can store data created during the use of the mobile terminal 100 (such as audio data, phone book, etc.). In addition, the internal memory 121 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc. The processor 110 executes various functional applications and data processing of the mobile terminal 100 by running the instructions stored in the internal memory 121 and / or the instructions stored in the memory provided in the processor.

[0092] The mobile terminal 100 can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor, etc. For example, music playback, recording, etc.

[0093] The software system of the mobile terminal 100 can adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservices architecture, or a cloud architecture. In the embodiment of the present application, taking the Android system with a layered architecture as an example, the software structure of the mobile terminal 100 is exemplarily described.

[0094] Please refer to Figure 3B , Figure 3B which is the software structure block diagram of the mobile terminal 100 in the embodiment of the present application.

[0095] The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. The layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, from top to bottom, namely the application layer (referred to as the application layer for short), the application framework layer (referred to as the framework layer for short), the Android runtime, and the system libraries, and the kernel layer.

[0096] The above application layer can include a series of application program packages. In some embodiments of the present application, the application layer includes a first application for providing a human-computer interaction interface for the mobile terminal 100 to control the IoT device 200. Among them, the first application can be, for example, a home application (such as the "Smart Life" APP), or a dedicated application for a certain IoT device (such as a smart speaker APP).

[0097] In some examples, when the user brings the mobile terminal 100 close to the IoT device 200, if the IoT device 200 is in an unconfigured state, the mobile terminal 100 automatically starts the first application to configure the IoT device 200. During the configuration process, the first application can display the corresponding GUI to show the progress of the configuration process. After successful configuration, the first application displays the control interface of the IoT device 200. In this way, the user can operate the control interface of the IoT device 200 to control the IoT device 200.

[0098] When the user brings the mobile terminal 100 close to the IoT device 200, if the IoT device 200 is in a configured state, the mobile terminal 100 automatically starts the first application and displays the control interface of the IoT device. In this way, the user can directly operate the control interface of the IoT device to control the IoT device 200.

[0099] In other examples, the mobile terminal 100 can also sink the capabilities and data related to the configuration process and control process in the first application to the framework layer. That is, set the services related to the configuration process and control process in the first application as system services, such as the "IoT device management module". In this way, when the user brings the mobile terminal 100 close to the IoT device 200, if the IoT device 200 is in an unconfigured state, the mobile terminal 100 starts the configuration process of the IoT device by calling the IoT device management module. Among them, the IoT device management module can obtain the configuration information of the mobile terminal 100 from the settings application and send it to the IoT device. Optionally, during the configuration process, the mobile terminal 100 can also display the corresponding pop-up window in a semi-modal rendering manner, for example, to show the progress of the configuration process. After successful configuration, the mobile terminal 100 can also display the control pop-up window of the IoT device. The user can operate the control pop-up window of the IoT device 200 to control the IoT device 200.

[0100] When the user brings the mobile terminal 100 close to the IoT device 200, if the IoT device 200 is in a configured state, the mobile terminal 100 calls the IoT device management module and displays the control pop-up window of the IoT device in a semi-modal rendering manner, for example. In this way, the user can directly operate the control pop-up window of the IoT device 200 to control the IoT device 200.

[0101] That is to say, in this example, the mobile terminal 100 can achieve the configuration and control of the IoT device without starting the first application.

[0102] In addition, the application package can include applications such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, and short message.

[0103] The above framework layer provides application programming interfaces (APIs) and programming frameworks for the application programs in the application layer. The framework layer includes some predefined functions.

[0104] Such as Figure 3B As shown, the framework layer includes an IoT device management module, which is used to implement network configuration for IoT devices or control IoT devices according to user operations.

[0105] In addition, the framework layer may also include a window manager, a content provider, a view system, a phone manager, a resource manager, a notification manager, etc.

[0106] Among them, the window manager is used to manage window programs. The window manager can obtain the display screen size, determine whether there is a status bar, lock the screen, capture the screen, etc. The content provider is used to store and obtain data, and make this data accessible to application programs. The data may include videos, images, audio, dialed and answered calls, browsing history and bookmarks, phone books, etc. The view system includes visible controls, such as controls for displaying text, controls for displaying pictures, etc. The view system can be used to build application programs. The display interface can be composed of one or more views. For example, a display interface including a text message notification icon may include a view for displaying text and a view for displaying pictures. The phone manager is used to provide the communication function of the mobile terminal 100. For example, the management of call status (including connection, hanging up, etc.). The resource manager provides various resources for application programs, such as localized strings, icons, pictures, layout files, video files, etc. The notification manager enables application programs to display notification information in the status bar, can be used to convey notification-type messages, and can automatically disappear after a short stay without user interaction. For example, the notification manager is used to notify the completion of a download, message reminder, etc. The notification manager can also be a notification that appears in the system top status bar in the form of a chart or scroll bar text, such as a notification of a background-running application program, and can also be a notification that appears on the screen in the form of a dialogue window. For example, prompt text information in the status bar, emit a prompt tone, vibrate the electronic device, blink the indicator light, etc.

[0107] The above Android Runtime includes a core library and a virtual machine. The Android runtime is responsible for the scheduling and management of the Android system. The core library consists of two parts: one part is the functional functions that need to be called by the Java language, and the other part is the core library of Android. The application layer and the framework layer run in the virtual machine. The virtual machine executes the Java files of the application layer and the framework layer as binary files. The virtual machine is used to perform functions such as object life cycle management, stack management, thread management, security and exception management, and garbage collection.

[0108] The above system library may include multiple functional modules. For example: a surface manager, Media Libraries, a 3D graphics processing library (such as OpenGL ES), a 2D graphics engine (such as SGL), etc.

[0109] Among them, the surface manager is used to manage the display subsystem and provides the fusion of 2D and 3D layers for multiple applications. The media library supports the playback and recording of multiple common audio and video formats, as well as static image files, etc. The media library can support multiple audio and video coding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc. The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, synthesis, and layer processing, etc. The 2D graphics engine is a drawing engine for 2D drawing.

[0110] The above kernel layer is the layer between hardware and software. The kernel layer at least includes a display driver, a camera driver, an audio driver, and a sensor driver.

[0111] Please refer to Figure 4 , Figure 4 which is a schematic structural diagram of an IoT device 200 provided by an embodiment of the present application. The IoT device 200 may include one or more processors 210, one or more memories 220, and one or more communication interfaces 230, a wireless communication module 240, and one or more antennas, etc. The processor 210, the memory 220, the communication interface 230, and the wireless communication module 240 are connected through a bus.

[0112] Among them, the processor 210 may include a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or an integrated circuit for controlling the execution of the program of the present application solution, etc. In one example, the processor 210 may also include multiple CPUs, and the processor 210 may be a single-CPU processor or a multi-CPU processor. Here, the processor may refer to one or more devices, circuits, or processing cores for processing data (such as computer program instructions).

[0113] The memory 220 can be used to store computer-executable program code, and the executable program code includes instructions. The internal memory may include a program storage area and a data storage area. Among them, the program storage area can store an operating system and programs or instructions required by the embodiments of the present application, etc.

[0114] A communication interface 230 can be used to communicate with other devices or communication networks, such as Ethernet, wireless local area networks (WLAN), etc. In some examples, the IoT device 200 may also not include the communication interface 230, and the embodiments of the present application do not limit this.

[0115] The wireless communication module 240 can provide solutions for wireless communications including WLAN (such as Wi-Fi networks), Bluetooth, NFC, infrared technology, etc. applied to the IoT device 200. The wireless communication module 240 can be one or more devices integrating at least one communication processing module. The wireless communication module 240 receives electromagnetic waves via an antenna, performs frequency modulation and filtering processing on the electromagnetic wave signals, and sends the processed signals to the processor 210. The wireless communication module 240 can also receive signals to be sent from the processor 210, perform frequency modulation and amplification on them, and convert them into electromagnetic waves through the antenna for radiation.

[0116] In the embodiments of the present application, the IoT device 200 has very short distance wireless communication capabilities. That is, other devices can only receive the wireless signals sent by the IoT device 200 within a very short distance (such as 30 cm or 10 cm). Then, in a real usage scenario, if a certain device can receive the very short distance wireless signals sent by the IoT device 200, it means that the device is very close to the IoT device 200, and this device can be considered a trusted device of the IoT device 200. That is, the IoT device 200 authenticates trusted devices by sending very short distance wireless signals.

[0117] Therefore, the IoT device 200 can send its own device information, such as device type (prodID), PIN, MAC, network configuration status, etc. through very short distance wireless communication. In this way, when the mobile terminal 100 is within the safe distance (such as 30 cm or 10 cm) of the IoT device 200, it can receive the device information of the IoT device 200. Then, the mobile terminal 100 can automatically configure the network for the IoT device 200 according to the device information of the IoT device 200, or display a control interface, and send corresponding control commands to the IoT device 200 according to the control operations selected by the user, etc.

[0118] In a specific example, the wireless communication module 240 can provide NFC functionality. Then, the IoT device 200 can send its own device information through the NFC functionality. It should also be noted that the wireless communication module 240 can also provide Wi-Fi or Bluetooth functionality. The IoT device 200 can communicate with the mobile terminal 100 via Wi-Fi or Bluetooth. For example, it can receive Wi-Fi network information sent by the mobile terminal and access the home network. The IoT device 200 can also communicate with the server 300. For example, it can receive control commands and the like sent by the mobile terminal 100 through the server 300.

[0119] In another specific example, the wireless communication module 240 has short-range communication capabilities such as BLE and Wi-Fi Aware. For example, as Figure 5A shown, the IoT device 200 includes at least two antennas 2, denoted as antenna 2(a) (weak antenna) 0 and antenna 2(b) (normal antenna). The wireless communication module 240 can switch between antenna 2(a) and antenna 2(b). Among them, the transmission distance of antenna 2(b) is distance A. The transmission distance of antenna 2(a) is distance B, and distance B is less than distance A. For example, when the wireless communication module 240 switches to antenna 2(b) to send a wireless signal, other wireless devices within the range of distance A (for example, 6m to 10m) of the IoT device 200 can receive the wireless signal. When the wireless communication module 240 switches to antenna 2(a) to send a wireless signal, other wireless devices within the range of distance B (for example, 30cm) of the IoT device 200 can receive the wireless signal. In other words, when the IoT device 200 needs to send a very short-range wireless signal, it can control the wireless communication module 240 to connect to antenna 2(b) to send the very short-range wireless signal. When the IoT device 200 does not need to send a very short-range wireless signal, it can control the wireless communication module 240 to connect to antenna 2(a) to send a normal wireless signal. That is to say, the IoT device 200 can switch to antenna 2(b) to send its own IoT device information.

[0120] For another example, as Figure 5BAs shown, the IoT device 200 may include a variable resistance circuit module 250 and at least one antenna 2. The variable resistance circuit module 250 may change the magnitude of the resistance value under the control of the wireless communication module 240, so as to change the transmission distance of the antenna. That is, when the resistance value of the variable resistance circuit module 250 is adjusted to resistance value 1, the transmission distance of the antenna is distance A. When the resistance value of the variable resistance circuit module 250 is adjusted to resistance value 2, the transmission distance of the antenna is distance B, and distance B is less than distance A. For example, when the resistance value of the variable resistance circuit module 250 is adjusted to resistance value 1, the transmission power of the antenna is the first transmission power (higher transmission power). At this time, other wireless devices within the range of distance A (such as 6m to 10m) from the IoT device 200 can receive the wireless signal. When the resistance value of the variable resistance circuit module 250 is adjusted to resistance value 2, the transmission power of the antenna is the second transmission power (lower transmission power). At this time, other wireless devices within the range of distance B (for example, distance B is 30cm) from the IoT device 200 can receive the wireless signal. In other words, when the IoT device 200 needs to send a ultra-short range wireless signal, it can control the resistance value of the variable resistance circuit module 250 to be adjusted to resistance value 2 to send the ultra-short range wireless signal. When the IoT device 200 does not need to send a ultra-short range wireless signal, it can control the resistance value of the variable resistance circuit module 250 to be adjusted to resistance value 1 to send a normal wireless signal. That is to say, the IoT device 200 can control the resistance value of the variable resistance circuit module 250 to be adjusted to resistance value 2 to send its own IoT device information. In other words, in some other embodiments, when the resistance value of the variable resistance circuit module 250 is adjusted to resistance value 1, the IoT device 200 is connected to the first antenna. When the resistance value of the variable resistance circuit module 250 is adjusted to resistance value 2, the IoT device 200 is connected to the second antenna; wherein, the first antenna and the second antenna are the same, but the transmission distance of the first antenna is greater than that of the second antenna; the transmission distance of the second antenna is less than or equal to a preset safety distance, and the transmission distance of the first antenna is greater than the preset safety distance. The transmission distances of the first antenna and the second antenna are distance A and the second distance B as described above.

[0121] As Figure 6 shown, it is a schematic flowchart of a method for managing an IoT device provided by an embodiment of the present application. The method specifically includes:

[0122] S601. In response to the IoT device receiving a first input, the IoT device sends a first message, and the first message includes IoT device information.

[0123] Among them, the IoT device information includes information such as device model (prodID), Personal Identification Number (PIN), MAC address, and network configuration status (or registration status). Optionally, the IoT device may also include other information, such as the manufacturer, the room it belongs to, etc. Among them, the device model can be used to identify the IoT device. Generally, the IoT device is named after the device model, and the device icon corresponding to the IoT device is determined according to the device model. The PIN is the root key for key negotiation in the subsequent network configuration process and is used for security authentication. The MAC address is the unique identifier of the IoT device and is used to distinguish other IoT devices. The network configuration status is used to mark whether the IoT device has been network-configured, and the subsequent mobile terminal executes different processes according to the network configuration status.

[0124] In specific implementation, when the IoT device receives a first input, the IoT device broadcasts and sends the first information by means of short-range communication. For example, the IoT device periodically sends information through NFC, Wi-Fi aware, low-power Bluetooth, etc. The specific sending method can refer to the description of the relevant content in the above Figure 4 、 Figure 5A and Figure 5B and will not be elaborated here. Among them, the first input can be a specific operation performed by the user on the IoT device, such as pressing a specific button, manipulating a specific control on the touch screen, performing a specific air gesture, inputting a voice command, etc. The first input can also be an instruction sent by other electronic devices. For example, the user operates the control device of the IoT device (such as a remote control), so that the control device sends an instruction to the IoT device or sends an instruction to the IoT device through the server. Among them, the first information can be carried in one or more messages, and the embodiments of the present application do not make specific limitations.

[0125] In some embodiments, the IoT device can also write the IoT device information into the firmware. When a mobile terminal or the like approaches the IoT device, the first information can be read. Or, the IoT device can start broadcasting the first information after receiving an instruction from the user to enter the network configuration mode. Or, the IoT device can also start broadcasting the first information after being powered on.

[0126] Taking the IoT device as a smart speaker as an example. For example, when the user newly purchases a smart speaker, the smart speaker is connected to the power supply. In response to the user pressing the switch button, the smart speaker is powered on or the smart speaker is automatically powered on. After the smart speaker is powered on, it starts to broadcast the first information shown in Table 1 at a preset period. It can be seen that at this time, the network configuration status of the smart speaker is not network-configured. The first input is the operation of powering on or the operation of the user pressing the switch button. It should also be noted that the specific content of the first information in Table 1 is only an example and does not constitute a limitation on the content of the first information.

[0127] Table 1

[0128]

[0129] Alternatively, after the smart speaker is powered on and in response to a user instruction to enter the network configuration mode (e.g., pressing the power on / off button twice continuously), the smart speaker enters the network configuration mode and starts sending the first information as shown in Table 1. At this time, the first input is the operation of the user instructing to enter the network configuration mode.

[0130] For another example, the smart speaker has been successfully network-configured. When the smart speaker is powered off and then restarted, the smart speaker can automatically send the first information as shown in Table 2. It can be seen that at this time, the network configuration state of the smart speaker is already network-configured. At this time, the first input is the operation of the user restarting the smart speaker. It should also be noted that the first information in Table 2 is only an example and does not constitute a limitation on the content of the first information.

[0131] Table 2

[0132]

[0133] Optionally, in some other embodiments, when the IoT device receives the first input or after the IoT device sends the first message, the IoT device can also prompt the user to bring the mobile terminal closer to the IoT device so that the mobile terminal can receive the first message sent by the IoT device through the ultra-short-range communication method. Among them, the prompting method can be one or more of playing a prompting voice, flashing a prompting light, and displaying a prompting interface. Alternatively, the IoT device informs the user in the manual to use a mobile terminal connected to the network to approach the IoT device to complete the network configuration process or the control process. The embodiments of the present application do not limit the specific prompting method.

[0134] S602. When the distance between the mobile terminal and the IoT device is less than or equal to the distance threshold, the mobile terminal receives the first information.

[0135] When the user needs to use the mobile terminal to network-configure the IoT device or control the IoT device, the user can carry the mobile terminal closer to the IoT device so that the distance between the mobile terminal and the IoT device is less than or equal to the distance threshold. The distance threshold is, for example, 10 cm, 30 cm, etc. For example, the user can use the mobile terminal to touch the NFC tag of the IoT device. At this time, the distance between the mobile terminal and the IoT device is less than the distance threshold, and the mobile terminal receives the first information sent by the IoT device through NFC. Among them, the NFC tag is used to indicate the position of the IoT device configured with the NFC communication module.

[0136] It can be understood that when the IoT device sends the first information through short - range communication, other devices (such as mobile terminals) can only receive the first information when they are within an ultra - short distance (i.e., the distance threshold) from the IoT device. In other words, in a real - world usage scenario, if a device can receive the first information sent by the IoT device, it means that the device is very close to the IoT device, and this device can be considered a trusted device of the IoT device. In this article, the distance range within which an ultra - short - range wireless signal sent by the IoT device can be received can be called the security distance. That is to say, the embodiments of this application utilize the security distance of ultra - short - range wireless communication to physically ensure the security of the first information sent by the IoT device.

[0137] S603. The mobile terminal determines whether the IoT device is in a network - configured state according to the first information. When the IoT device is in an un - network - configured state, the mobile terminal executes the network - configuration process for the IoT device, that is, executes steps S604 - S610. Optionally, after executing steps S604 - S610, steps S611 - S618 can also be continued. When the IoT device is in a network - configured state, the mobile terminal displays the control interface of the IoT device and sends corresponding control commands to the IoT device according to the user's operation, that is, executes steps S611 - S618.

[0138] S604. The mobile terminal establishes a communication connection with the IoT device.

[0139] In some embodiments, the first information sent by the IoT device includes the device model (for example, the device name is the same as the device model), MAC address, PIN, etc. The mobile terminal can automatically establish a Wi - Fi connection or a Bluetooth connection with the IoT device according to the device name, MAC address, etc.

[0140] In other embodiments, the user can also manually connect the mobile terminal and the IoT device by operating the mobile terminal or the IoT device. For example, the user opens the system settings of the mobile terminal, selects to turn on the Wi - Fi function, and selects to connect to the IoT device, and the mobile terminal establishes a Wi - Fi connection with the IoT device. Or, the user opens the system settings of the mobile terminal, selects to turn on the Bluetooth function, and selects to connect to the IoT device, and the mobile terminal establishes a Bluetooth connection with the IoT device.

[0141] Of course, the mobile terminal and the IoT device can also be connected by wire. The embodiments of this application do not limit the connection method between the mobile terminal and the IoT device.

[0142] S605. The mobile terminal requests the registration code of the IoT device from the server.

[0143] Before the mobile terminal configures the network for the IoT device, the mobile terminal is already connected to the Wi-Fi network and can access the server through the Wi-Fi network. The mobile terminal sends a request to the server, requesting the server to generate a registration code for the IoT device. The request sent by the mobile terminal to the server may carry the device model of the mobile terminal, the account logged in to the mobile terminal, the device model of the IoT device, the MAC address, etc.

[0144] S606. The server returns the registration code of the IoT device to the mobile terminal.

[0145] After receiving the request sent by the mobile terminal, the server generates an identifier for the IoT device (i.e., the device ID) based on the device model and MAC address of the IoT device, etc., to uniquely identify the IoT device. And, the server generates a registration code for the IoT device based on the device model of the mobile terminal and the account logged in to the mobile terminal, etc. Then, the server returns the generated registration code and device ID to the mobile terminal.

[0146] S607. The mobile terminal sends the network configuration information and the registration code of the IoT device to the IoT device.

[0147] Among them, the network configuration information includes information such as the service set identifier (Service Set Identifier, SSID) and password of the Wi-Fi connected by the mobile terminal. In some examples, the network configuration information is included in the settings application in the mobile terminal.

[0148] In some examples, after the mobile terminal obtains the registration code of the IoT device, it sends a request to create a session to the IoT device, and this request carries the registration code of the IoT device and the PIN of the IoT device. The IoT device creates session information with the mobile terminal (such as the session identifier sessionID) and returns it to the mobile terminal. Subsequently, the mobile terminal uses this session information to send the network configuration information saved locally to the IoT device.

[0149] S608. The IoT device connects to the Wi-Fi network according to the network configuration information and requests registration from the server.

[0150] After receiving the network configuration information, the IoT device can connect to the Wi-Fi network and access the server. The IoT device requests registration from the server according to the registration code. The server binds the identifier of the IoT device to the account of the mobile terminal. Subsequently, when the server receives a control command for the IoT device sent by a device logging in to this account, it forwards the control command to the IoT device so that the IoT device can execute the action corresponding to the control command.

[0151] S609. The server returns the registration result to the mobile terminal.

[0152] S610. The mobile terminal updates the status of the IoT device according to the registration result.

[0153] Exemplarily, the network configuration status of the IoT device is updated, changing from the unconfigured state to the configured state. It can be understood that before the IoT device is network-configured, there is no relevant information about the IoT device in the first application. After the network configuration of the IoT device is completed, the first application stores the relevant information of the IoT device. At this time, the user can control the IoT device through the first application.

[0154] It should be noted that in the above network configuration process of the IoT device, the mobile terminal can also display some graphical user interfaces (GUI) in real time to inform the user of the progress of the network configuration process. Specifically, the mobile terminal can automatically start the first application and display the relevant GUI in the first application. Or, the mobile terminal may not start the first application and directly display a corresponding pop-up window on the current interface of the mobile terminal (such as the desktop) in a way such as semi-modal rendering. The embodiments of the present application do not make any limitations in this regard.

[0155] Taking the mobile terminal as a mobile phone and the IoT device as a smart speaker as an example for illustration. As Figure 7A shown in (1) below, when the user brings the mobile phone close to the smart speaker and the distance between the mobile phone and the smart speaker is less than or equal to the distance threshold, the mobile phone can read the first information of the smart speaker. At this time, the mobile phone can display the GUI as shown in Figure 7A (2) below, where the pop-up window 701 is used to prompt the user that the first information of the smart speaker is being read. Among them, the first information includes device model, MAC address, PIN, and network configuration status, etc. After receiving the first information, if the mobile phone determines that the smart speaker is in the unconfigured state according to the network configuration status, the mobile phone automatically starts the network configuration process for the smart speaker. When the mobile phone applies to the server for the registration code of the smart speaker and when the mobile phone sends the network configuration information to the smart speaker, the mobile phone can also display the corresponding interface to prompt the user of the current network configuration progress. For example, the mobile phone can display the GUI as shown in Figure 7A (3) below. Among them, the pop-up window 702 is used to prompt the user that the mobile phone is sending the network configuration information to the smart speaker, etc. Also for example, the mobile phone can display the GUI as shown in Figure 7B (1) below. Among them, the pop-up window 703 is used to prompt the user that the mobile phone is applying to the server for the registration code of the smart speaker. After the smart speaker is successfully registered, the mobile phone can also display the GUI as shown in Figure 7B (2) below. Among them, the pop-up window 704 is used to prompt that the smart speaker has been successfully registered under the account currently logged in on the mobile phone. It should be noted that the mobile phone can display more or fewer interfaces than the above-mentioned GUI. The embodiments of the present application do not make any limitations in this regard.

[0156] It should also be noted that the above steps S604 to S610 are an example of the IoT device network configuration process. Among them, the execution order between some steps can also be changed. For example, step S604 can also be executed simultaneously with step S605, or after step S605. In addition, the IoT device network configuration process can include more or fewer steps. For example, after step S607, the IoT device can also return a response to the mobile terminal upon receiving the registration code sent by the mobile terminal, informing the mobile terminal that the registration code has been received.

[0157] Thus, when the mobile terminal approaches the IoT device, if the IoT device is in an unconfigured state, the mobile terminal can automatically configure the network for the IoT device. And in the IoT device network configuration process, there is no need for the user to scan the label of the IoT device, select the Wi-Fi network password, the IoT device PIN, and other cumbersome operations. It can be seen that the method provided in the embodiment of the present application simplifies the user operation and achieves the effect of seamless network configuration.

[0158] Furthermore, after the mobile terminal successfully configures the network, the user can directly control the mobile terminal. Or, in step S603, if the mobile terminal determines that the IoT device is in a configured state according to the first information, it can directly execute step S611 and the subsequent steps.

[0159] S611. The mobile terminal displays the control interface of the IoT device.

[0160] In some embodiments, the mobile phone can display a pop-up window containing the control interface of the IoT device in the currently displayed interface. In some examples, the IoT device control interface can be a quick operation interface, that is, it only includes the brief device information of the IoT device and the main control functions.

[0161] Still taking the mobile terminal as the mobile phone and the IoT device as the smart speaker as an example. For example, the mobile phone displays as Figure 7BThe GUI shown in (3). Among them, the pop-up window 711 is the control interface of the smart speaker. Among them, the pop-up window 711 includes a device icon 705 (such as the icon of the smart speaker), a device name (such as HUAWEI SoundX), a network configuration status indicator 706 of the smart speaker, a play control function 707, a Bluetooth function control 708 of the smart speaker, and a volume 709, etc. Among them, the play control function 707 includes controls such as the name of the music, the singer, the album cover, the play mode (single loop, playlist loop, random play), previous, play (or pause), next, and favorite. Optionally, the pop-up window 711 may further include a "View More" control 710. In response to the user operating the "View More" control 710, the mobile phone displays more functions of the smart speaker in the pop-up window 711, or the mobile phone automatically opens the first application and enters the control interface of the smart speaker, that is, it displays as shown in Figure 7B the control interface 714 shown in (4). Among them, the control interface 714 contains more function controls than the pop-up window 711. For example, in the play control function, the control interface 714 further includes a control 712 for viewing lyrics, which can be used to display the lyrics of the currently playing music. Another example is that in the control area 713 of the control interface 714, there are also controls for entering function modules such as voice skills, XX storytelling, XX children's songs, and listening to novels.

[0162] Of course, in some other embodiments, after the mobile phone completes the network configuration process for the smart speaker, it can also automatically open the first application and display as shown in Figure 7B the control interface 714 shown in (4).

[0163] It can be understood that the mobile terminal controls the IoT device by adopting the management method of the GUI, which can be not affected by the noise in the surrounding environment, etc., and has better robustness, which is beneficial to more accurately control the IoT device.

[0164] In still some other embodiments, the mobile phone can also adopt the management method of the VUI to prompt the user that they can control the IoT device by voice. For example, as shown in Figure 7CAs shown in (1), the mobile phone plays a voice prompt. It should be noted that in the existing management method of VUI, the user needs to wake up the control device (i.e., the mobile terminal) by saying a wake-up word, and then accept the user's voice command. In this solution, there is no need for the user to say a wake-up word. In addition, in the existing management method of VUI, the IoT device is generally referred to by its device model. For example, the user says "Turn on the smart speaker". Among them, the smart speaker is the device that the user wants to control. However, when there are IoT devices with the same device model in the surrounding environment, the control device will not be able to distinguish which IoT device the user wants to turn on. Then, in the solution of this application, when the user holds the mobile terminal close to an IoT device, the first information sent by the IoT device includes not only the device model of the IoT device, but also the MAC address of the IoT device, which can be used to distinguish the IoT device that the user wants to control this time.

[0165] S612. The mobile terminal receives the user's first operation.

[0166] The user can operate on the control interface displayed on the mobile terminal, or the user can directly input a voice command. For example, the user can click the play control in the play control function 707 in the pop-up window as shown in (3). Another example is that as shown in (2), the user can say "Play the next song" to the mobile phone. Figure 7B As shown in (3) Figure 7C As shown in (2), the user can say "Play the next song" to the mobile phone.

[0167] S613. The mobile terminal determines the control command for the IoT device according to the user's first operation and sends it to the server.

[0168] S614. The server forwards the control command sent by the mobile terminal to the IoT device.

[0169] The server determines that the mobile terminal is the control device of the IoT device according to the control command sent by the mobile terminal and the control device information of the IoT device recorded by the server, and forwards the control command to the IoT device.

[0170] S615. The IoT device executes the action corresponding to the control command.

[0171] S616. The IoT device sends the control result to the server.

[0172] S617. The server forwards the control result to the mobile terminal.

[0173] S618. The mobile terminal updates the status of the IoT device according to the execution result.

[0174] For example, as shown in (3) Figure 7C The mobile phone plays a voice, prompting that the next song is being played.

[0175] It can be seen that when the mobile terminal approaches the IoT device, if the IoT device is in an unconfigured state, the mobile terminal can automatically configure the network for the IoT device and display the control interface. If the IoT device is in a configured state, the mobile terminal can display the control interface. In this way, the user can directly operate the control interface to start controlling the IoT device. That is, the method provided by the embodiments of the present application can automatically execute different processes, network configuration or control, according to the network configuration state of the IoT device, simplifies the user operation, achieves a one-touch control experience, and is beneficial to enhancing user stickiness.

[0176] Moreover, when the mobile terminal approaches the IoT device, it can obtain the unique MAC address of the IoT device. When there are multiple IoT devices of the same device model in the surrounding environment, the mobile terminal can also configure the network for and operate the IoT device that the user approaches.

[0177] The embodiments of the present application also provide a chip system, as Figure 8 shown. The chip system includes at least one processor 1101 and at least one interface circuit 1102. The processor 1101 and the interface circuit 1102 can be interconnected by a line. For example, the interface circuit 1102 can be used to receive signals from other devices (such as the memory of the mobile terminal 100). For another example, the interface circuit 1102 can be used to send signals to other devices (such as the processor 1101). Exemplarily, the interface circuit 1102 can read the instructions stored in the memory and send the instructions to the processor 1101. When the instructions are executed by the processor 1101, the electronic device can execute the various steps performed by the mobile terminal 100 (such as a mobile phone) in the above embodiments. Of course, the chip system can also include other discrete devices, and the embodiments of the present application do not make specific limitations on this.

[0178] The embodiments of the present application also provide a chip system, as Figure 9 shown. The chip system includes at least one processor 1201 and at least one interface circuit 1202. The processor 1201 and the interface circuit 1202 can be interconnected by a line. For example, the interface circuit 1202 can be used to receive signals from other devices (such as the memory of the IoT device 200). For another example, the interface circuit 1202 can be used to send signals to other devices (such as the processor 1201). Exemplarily, the interface circuit 1202 can read the instructions stored in the memory and send the instructions to the processor 1201. When the instructions are executed by the processor 1201, the electronic device can execute the various steps performed by the mobile terminal 100 (such as a smart speaker) in the above embodiments. Of course, the chip system can also include other discrete devices, and the embodiments of the present application do not make specific limitations on this.

[0179] An embodiment of the present application further provides a device, which is included in a mobile terminal and has the function of implementing the behavior of the mobile terminal in any of the above methods. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above function. For example, a receiving module or unit, a sending module or unit, and a determining module or unit, etc.

[0180] An embodiment of the present application further provides a device, which is included in an IoT device and has the function of implementing the behavior of the IoT device in any of the above methods. This function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes at least one module or unit corresponding to the above function. For example, a receiving module or unit, a sending module or unit, and a determining module or unit, etc.

[0181] An embodiment of the present application further provides a computer storage medium, including computer instructions, which when running on a mobile terminal, cause the mobile terminal to execute any of the methods in the above embodiments.

[0182] An embodiment of the present application further provides a computer storage medium, including computer instructions, which when running on an IoT device, cause the IoT device to execute any of the methods in the above embodiments.

[0183] An embodiment of the present application further provides a computer program product, which when running on a computer, causes the computer to execute any of the methods in the above embodiments.

[0184] An embodiment of the present application further provides a graphical user interface on a mobile terminal. The mobile terminal has a display screen, a memory, and one or more processors. The one or more processors are used to execute one or more computer programs stored in the memory. The graphical user interface includes the graphical user interface displayed when the mobile terminal executes any of the methods in the above embodiments.

[0185] It can be understood that, in order to implement the above functions, the above terminals, etc., include corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should easily realize that, combining the units and algorithm steps of each example described in the embodiments disclosed in this article, the embodiments of the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a certain function is executed in the way of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described function for each specific application, but such implementation should not be considered to exceed the scope of the embodiments of the present application.

[0186] Embodiments of the present application can divide the above-mentioned terminals, etc. into functional modules according to the above method examples. For example, each functional module can be divided corresponding to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of a software functional module. It should be noted that the division of modules in the embodiments of the present application is illustrative, only a logical function division, and there may be other division methods in actual implementation.

[0187] Through the description of the above embodiments, those skilled in the art can clearly understand that for the convenience and brevity of description, only the above division of each functional module is used as an example. In actual applications, the above functions can be allocated to different functional modules according to needs, that is, the internal structure of the device is divided into different functional modules to complete all or part of the functions described above. The specific working processes of the systems, devices, and units described above can refer to the corresponding processes in the foregoing method embodiments and will not be repeated here.

[0188] In each embodiment of the present application, each functional unit can be integrated into one processing unit, or each unit can exist physically alone, or two or more units can be integrated into one unit. The above integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0189] If the above 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 computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of the present application, in essence, or the part that contributes to the prior art, or all or part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) or a processor to execute all or part of the steps of the methods described in the various embodiments of the present application. The foregoing storage medium includes: various media that can store program codes such as flash memory, mobile hard disk, read-only memory, random access memory, magnetic disk, or optical disc.

[0190] The above is only the specific implementation manner of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions within the technical scope disclosed in the present application should be covered by the protection scope of the present application. Therefore, the protection scope of the present application should be subject to the protection scope of the claims.

Claims

1. A mobile terminal, characterized in that, Comprising: A processor and a memory, the memory being coupled to the processor, the memory being configured to store computer program code, the computer program code including computer instructions, when the processor reads the computer instructions from the memory, such that the mobile terminal performs the following operations: Receiving, within a preset distance from the IoT device, a first message sent by the IoT device, the first message including an identifier of the IoT device and a registration status of the IoT device, and the first message being sent by the IoT device in a short-range communication manner; When the registration status indicates that the IoT device is not registered, requesting a registration code for the IoT device from a server, and sending the registration code and locally saved network configuration information to the IoT device, the registration code and the network configuration information being used for the IoT device to apply for registration with the server; When the registration status indicates that the IoT device is registered, displaying a control interface, the control interface including controls for manipulating the IoT device.

2. The mobile terminal according to claim 1, characterized in that, The identifier of the IoT device includes one or more of a device model, a personal identification number (PIN), and a media access control (MAC) address.

3. The mobile terminal according to claim 1 or 2, characterized in that, The mobile terminal further performs: Receiving a message indicating successful registration of the IoT device sent by the server, and updating the registration status of the IoT device.

4. The mobile terminal according to claim 1, characterized in that, When the registration status indicates that the IoT device is registered, the mobile terminal displays a control interface, including: After receiving the first message, when the registration status indicates that the IoT device is registered, the mobile terminal displays the control interface; Or, after receiving the message indicating successful registration of the IoT device sent by the server, when the mobile terminal updates the registration status of the IoT device to registered, the mobile terminal displays the control interface.

5. The mobile terminal according to claim 1 or 4, characterized in that, When the registration status indicates that the IoT device is registered, the mobile terminal displays a control interface, including: The mobile terminal automatically launches a first application and displays the control interface of the first application; Or, the mobile terminal invokes a system service to display a pop-up window including the control interface.

6. The mobile terminal according to any one of claims 1, 2, and 4, characterized in that The mobile terminal further performs: When the registration status indicates that the IoT device is registered, playing a first voice, the first voice being used to prompt the user to control the IoT device by voice.

7. The mobile terminal according to claim 6, characterized in that, When the registration status indicates that the IoT device is registered, the mobile terminal plays a first voice, the first voice being used to prompt the user to control the IoT device by voice, including: After receiving the first message, when the registration status indicates that the IoT device is registered, the mobile terminal plays the first voice; Or, after receiving the message indicating successful registration of the IoT device sent by the server, when the mobile terminal updates the registration status of the IoT device to registered, the mobile terminal plays the first voice.

8. An IoT device, characterized in that, Comprising: A processor, a memory, and a short - range communication module, where the memory and the short - range communication module are coupled to the processor. The memory is used to store computer program code, and the computer program code includes computer instructions. When the processor reads the computer instructions from the memory, the IoT device is caused to perform the following operations: Receiving a first input, and sending a first message through the short - range communication module. The first message includes the identifier of the IoT device and the registration status of the IoT device; wherein, the identifier of the IoT device and the registration status of the IoT device are used to instruct the mobile terminal to apply for a registration code of the IoT device, and return the registration code and the network configuration information saved by the mobile terminal to the IoT device; After receiving the registration code and the network configuration information returned by the mobile terminal, applying for registration with the server.

9. The IoT device according to claim 8, wherein, Also perform: After receiving the first input, or before sending the first message, prompting the user to bring the mobile terminal close to the IoT device; wherein, the prompting method of the IoT device includes one or more of playing a prompting voice, flashing a prompting light, and displaying a prompting interface.

10. A management method for an IoT device, characterized in that, Applied to a mobile terminal, the method includes: Receiving, within a preset distance from the IoT device, a first message sent by the IoT device. The first message includes the identifier of the IoT device and the registration status of the IoT device, and the first message is sent by the IoT device using short - range communication; When the registration status indicates that the IoT device is not registered, requesting a registration code of the IoT device from the server, and sending the registration code and the network configuration information saved locally to the IoT device. The registration code and the network configuration information are used for the IoT device to apply for registration with the server; When the registration status indicates that the IoT device is already registered, displaying a control interface, where the control interface includes controls for operating the IoT device.

11. The method according to claim 10, wherein The identifier of the IoT device includes one or more of a device model, a personal identification number (PIN), and a media access control (MAC) address.

12. The method according to claim 10 or 11, characterized in that, Also includes: Receiving the message indicating the successful registration of the IoT device sent by the server, and updating the registration status of the IoT device.

13. The method according to claim 10, wherein When the registration status indicates that the IoT device is already registered, displaying a control interface, including: After receiving the first message, when the registration status indicates that the IoT device is already registered, displaying the control interface; Or, after receiving the message indicating the successful registration of the IoT device sent by the server, when updating the registration status of the IoT device to already registered, displaying the control interface.

14. The method according to claim 10 or 13, characterized in that, When the registration status indicates that the IoT device is already registered, displaying a control interface, including: Automatically starting a first application and displaying the control interface of the first application; or, calling a system service to display a pop - up window including the control interface.

15. The method according to claim 10 or 13, characterized in that Also includes: When the registration status indicates that the IoT device is already registered, playing a first voice, where the first voice is used to prompt the user to control the IoT device by voice.

16. The method according to claim 15, wherein When the registration status indicates that the IoT device has been registered, play a first voice, where the first voice is used to prompt the user to control the IoT device by voice, including: After receiving the first message, when the registration status indicates that the IoT device has been registered, play the first voice; Alternatively, after receiving the message indicating the successful registration of the IoT device sent by the server, play the first voice when updating the registration status of the IoT device to registered.

17. A management method for an IoT device, characterized in that, Applied to an IoT device, the method includes: Receiving a first input, and sending a first message through a short-range communication module, where the first message contains the identifier of the IoT device and the registration status of the IoT device; wherein, the identifier of the IoT device and the registration status of the IoT device are used to instruct the mobile terminal to apply for a registration code for the IoT device, and return the registration code and the network configuration information saved by the mobile terminal to the IoT device; After receiving the registration code and the network configuration information returned by the mobile terminal, apply for registration with the server.

18. The method according to claim 17, characterized in that, It further includes: After receiving the first input, or before sending the first message, prompt the user to bring the mobile terminal close to the IoT device; wherein, the prompting method of the IoT device includes playing a prompt voice, flashing a prompt light, displaying a prompt interface, or a combination of one or more of them.

Images