CN116055233A

CN116055233A - Internet of things equipment network distribution method, terminal and system

Info

Publication number: CN116055233A
Application number: CN202111267166.6A
Authority: CN
Inventors: 王斌; 代栓青; 晏国淇; 赵昕
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2021-10-28
Filing date: 2021-10-28
Publication date: 2023-05-02

Abstract

The application discloses a network distribution method, a terminal and a system of Internet of things equipment, wherein the method comprises the following steps: the terminal stores an identification of at least one IoT device. After the terminal stores the identity of the at least one IoT device, the terminal receives a broadcast sent by the first IoT device, where the broadcast carries the first identity of the first IoT device. The terminal scans a broadcast sent by the first IoT device and parses a first identifier carried in the broadcast. The terminal determines that the first identification is an identification of at least one IoT device, i.e., the first IoT device is one of the at least one IoT device. The terminal sends network information to the first IoT device according to the first identification. The first IoT device receives the network information and connects to the network according to the network information. In this way, the first IoT device automatically completes the distribution network without the user perceiving the distribution network operation, that is, without the user manually participating in the distribution network process of the IoT device, thereby improving the distribution network efficiency. Moreover, multiple IoT devices may implement automatic distribution network concurrently, resulting in higher distribution network efficiency.

Description

Internet of things equipment network distribution method, terminal and system

Technical Field

The embodiment of the invention relates to the technical field of communication, in particular to a network distribution method, a terminal and a system for equipment of the Internet of things.

Background

With the popularity of internet of things (internet of things, ioT) devices, there are increasing numbers of IoT devices in the user's home. Such as intelligent speakers, air conditioners, televisions, etc. These IoT devices need to access the internet. However, some IoT devices (such as smart speakers) do not have information input functions of a touch screen and a keyboard, and are limited by a hard disk, which requires access to the internet with the aid of a terminal device. The existing IoT device network allocation method generally requires a user to manually reset the IoT device into a network allocation state, and manually complete IoT device network allocation registration on an application of a terminal device, which requires the user to participate in the whole process. When the number of the IoT devices is large, the plurality of IoT devices need to be distributed one by one, and the operation is complex. Therefore, the existing network distribution method of the Internet of things equipment has the problem of low network distribution efficiency.

Disclosure of Invention

According to the network distribution method, terminal and system for the Internet of things equipment, the concurrent network distribution of a plurality of internet of things equipment is achieved, users do not need to participate in the network distribution, and the network distribution efficiency is high.

In order to achieve the above purpose, the following technical solutions are adopted in the embodiments of the present application.

In a first aspect, an embodiment of the present application provides a network allocation method for an internet of things device, where an execution body of the method may be a terminal, or may be a component (for example, a chip system, or a processor) located in the terminal, and the description below takes an execution body as an example of the terminal. The method comprises the following steps: the terminal stores an identification of at least one IoT device. After the terminal stores the identification of the at least one IoT device, the terminal receives a broadcast sent by the first IoT device, where the broadcast carries the first identification of the first IoT device. The terminal scans for broadcasts sent by the first IoT device. The terminal obtains a first identification according to the broadcast, wherein the first identification is the identification of at least one IoT device. The terminal sends network information to a first IoT device according to the first identity, the first IoT device being configured to connect to a network according to the network information.

The terminal stores the identity of the at least one IoT device, which can be understood as the terminal stores the identity of the at least one IoT device in advance. The opportunity for the terminal to store the identification of the at least one IoT device may be after the user purchases the IoT device through the terminal, or the user obtains the IoT device and stores the identification of the IoT device on the terminal. Wherein storing the identification of the IoT device on the terminal by the user may be accomplished in the following manner: in one approach, the user manually stores an identification of the IoT device on the terminal. In the second mode, the user may obtain the identifier by scanning the two-dimensional code of the IoT device through the terminal. Of course, other situations may exist, and the embodiments of the present application are not specifically limited.

In this way, the identity of the at least one IoT device is prestored in the terminal, and when the first IoT device needs to connect to the network, the terminal determines that the first IoT device is one of the at least one prestored IoT device and sends the network information to the first IoT device so that the first IoT device can connect to the network. In the whole distribution process of the first IoT device, the first IoT device automatically completes the distribution under the condition that the user does not perceive the distribution operation, that is, the user does not need to manually participate in the distribution process of the IoT device, and the distribution efficiency is improved.

In addition, in the process of the first IoT device performing the network configuration, the second IoT device, the third IoT device or the n-th IoT device needs to be connected to the network, the terminal determines that the second IoT device, the third IoT device and the n-th IoT device are one of at least one IoT device stored in advance, and sends the network information to the second IoT device, the third IoT device and the n-th IoT device, so that the second IoT device, the third IoT device and the n-th IoT device are connected to the network. It can be seen that multiple IoT devices may implement automatic distribution network concurrently, resulting in higher distribution network efficiency.

In one particular implementation, the terminal stores an identification of at least one IoT device, in particular: the terminal receives a first operation of a first IoT device displayed on the terminal by a user, the first IoT device displayed on a first interface of a first application of the terminal. In response to the first operation, the terminal requests a first server corresponding to the first application to generate order completion information of the first IoT device, the first server is configured to send the order completion information to the terminal, and push a notification to a second server of the first IoT device, the notification is configured to instruct the second server to push a first identifier of the first IoT device to the terminal. The terminal receives order completion information of the first IoT device sent by the first server. The terminal receives a first identification of a first IoT device pushed by a second server. The terminal stores a first identification of the first IoT device.

That is, a user purchases a first IoT device on a first application through a terminal, and after the first IoT device is purchased, a first server corresponding to the first application pushes an identification of the first IoT device to a second server corresponding to the first IoT device. The second server sends the identification of the first IoT device to the terminal.

The user account number adopted by the terminal when logging in the first application is the user account number which can be identified by the second server. The second server may push the identification of the first IoT device to the terminal according to the user account.

In the embodiment of the present application, after the user purchases the first IoT device, the identifier of the first IoT device may be stored on the terminal. In this way, when the subsequent first IoT device performs network connection, the terminal pushes the network information to the first IoT device according to the identifier of the first IoT device. In the process, a display interface of a user-loaded operation terminal is not needed, user operation is reduced, and the distribution efficiency of the IoT equipment is improved.

In some implementations, the first operation may include a user operation of a first control on a first interface of the first application. The first control is used for authorizing a user to push the identification of the first IoT device to a second server corresponding to the first IoT device by the first server, and the second server sends the identification of the first IoT device to the terminal.

In some implementations, the second server is configured to obtain, from a third server corresponding to the first IoT device, a first identifier of the first IoT device according to the notification, the first identifier being generated by the third server according to a second identifier of the first IoT device.

Wherein the second identifier may be understood as an intra-pair identifier. The second identification may include at least one of a serial number, a physical address, and an identifier. The first identification may also be an external identification of the first IoT device. The external identifier may be understood as an identifier, such as a string, an array, etc., presented externally to the vendor of the IoT device.

In the embodiment of the application, the second identifier (such as the serial number, the physical address and the like) of the first IoT device is converted into the first identifier, so that the second identifier can be effectively protected, the leakage risk is reduced, and the IoT device network allocation process is safer.

In some implementations, before the terminal receives the first operation of the first IoT device displayed on the terminal by the user, further comprising: and the terminal receives a second operation of the user on the first application, wherein the second operation is used for indicating the terminal to start the first application. Responding to the second operation, the terminal sends a first request to a first server, wherein the first request carries a first user account, and the first server is used for starting a first application according to the first request and returning login success information to the terminal. And the terminal receives the login success information.

In a specific implementation manner, the first application is a three-party application, the first user account is a login account of a fourth server corresponding to the terminal, and the first server is configured to push the first identifier of the first IoT device and the first user account to the fourth server after generating the order completion information. The fourth server is to push the first identification of the first IoT device and the first user account to the second server.

In some implementations, after the terminal obtains the first identification from the broadcast, the first identification is an identification of the at least one IoT device, further comprising: the terminal sends a second request to the first IoT device according to the first identification, wherein the second request is used for requesting to establish a communication channel with the first IoT device. The terminal receives the establishment success information sent by the first IoT device, wherein the establishment success information is generated after the first IoT device establishes a communication channel according to the second request.

In one particular implementation, the terminal also stores a first access credential of the at least one IoT device. The terminal sends network information to the first IoT device, specifically: and the terminal encrypts the network information by adopting a first access credential of the first IoT device to obtain an access ciphertext. And the terminal sends the access ciphertext to the first IoT device, and the first IoT device is used for decrypting the access ciphertext by adopting the first access credential to obtain network information.

In the embodiment of the application, the terminal encrypts the network information by adopting the first access credential of the first IoT device to obtain the credential ciphertext, so that the network information leakage can be effectively avoided, and the security of the network distribution process is improved.

In some implementations, before the terminal sends the network information to the first IoT device according to the first identification, further comprising: the terminal sends a third request to the second server, wherein the third request is used for requesting to acquire the second access credential of the second server. And the terminal receives a second access certificate returned by the second server according to the third request. The method further comprises the steps of: the terminal sends address information of the second server and the second access credential to the first IoT device. The first IoT device is configured to send a fourth request to the second server, where the fourth request is configured to request registration of the first IoT device, and the fourth request carries the second access credential. The second server registers the first IoT device according to the fourth request, generates registration success information, and feeds back the registration success information to the terminal. And the terminal receives the registration success information pushed by the second server. The first IoT device is displayed on a second interface of the terminal with successful addition.

In the embodiment of the application, the terminal acquires the address information and the second access credential from the second server instead of the first IoT. The first IoT device sends a registration request to the second server according to the address information, wherein the request carries the second access credential. The second server completes registration according to the second access credential and the registration request. In the whole first IoT device registration process, the first IoT device automatically completes registration under the condition that the user does not perceive the registration operation, that is, the user does not need to manually participate in the IoT device registration process, and efficiency is improved. Moreover, multiple IoT devices may implement automatic registration concurrently, making it more efficient.

In a second aspect, an embodiment of the present application provides an internet of things device distribution network system, where the system includes: the terminal is to store an identification of at least one IoT device. After the terminal stores the identity of the at least one IoT device, the first IoT device is configured to send a broadcast carrying the first identity of the first IoT device. The terminal is used for receiving and scanning the broadcast. The terminal is configured to obtain a first identification from the broadcast, the first identification being an identification of at least one IoT device. The terminal is to send network information to the first IoT device according to the first identification. The first IoT device is to connect to a network according to the network information. In this way, the first IoT device automatically completes the distribution network without the user perceiving the distribution network operation, that is, without the user manually participating in the distribution network process of the IoT device, thereby improving the distribution network efficiency. Moreover, multiple IoT devices may implement automatic distribution network concurrently, resulting in higher distribution network efficiency.

In some implementations, the terminal is further to receive a first operation by the user of a first IoT device displayed on the terminal, the first IoT device displayed on a first interface of a first application of the terminal. The terminal is further configured to request, in response to the first operation, a first server corresponding to the first application to generate order completion information for the first IoT device. The first server is configured to send order completion information to the terminal, and push a notification to a second server of the first IoT device, the notification being configured to instruct the second server to push a first identification of the first IoT device to the terminal. The second server is to push a first identification of the first IoT device to the terminal according to the notification. The terminal is also configured to receive order completion information of the first IoT device sent by the first server. The terminal is also to receive a first identification of a first IoT device pushed by the second server. The terminal is also to store a first identification of the first IoT device.

In some implementations, the terminal is further configured to receive a second operation of the first application by the user, where the second operation is configured to instruct the terminal to launch the first application. The terminal is also used for responding to the second operation and sending a first request to the first server, wherein the first request carries the first user account. The first server is used for starting a first application according to the first request and returning login success information to the terminal. The terminal is also used for receiving login success information.

In some implementations, the first application is a three-party application, and the first user account is a login account of a fourth server corresponding to the terminal. The first server is to push, to the fourth server, a first identification of the first IoT device and a first user account after generating the order completion information. The fourth server is to push the first identification of the first IoT device and the first user account to the second server.

In some implementations, the terminal is further configured to send a second request to the first IoT device according to the first identification, the second request requesting establishment of a communication channel with the first IoT device. The first IoT device establishes a communication channel with the terminal according to the second request, generates establishment success information, and sends the establishment success information to the terminal. The terminal is further configured to receive establishment success information sent by the first IoT device, where the establishment success information is generated after the first IoT device establishes a communication channel according to the second request.

In some implementations, the terminal also stores the first access credentials of the at least one IoT device. The terminal is further configured to encrypt the network information with a first access credential of the first IoT device to obtain an access ciphertext. The terminal is also to send the access ciphertext to the first IoT device. The first IoT device is configured to decrypt the access ciphertext using the first access credential to obtain the network information.

In some implementations, the terminal is further configured to send a third request to the second server, the third request being for requesting acquisition of the second access credentials of the second server. And the second server acquires a second access certificate of the second server according to the third request and sends the second access certificate to the terminal. The terminal is also configured to receive a second access credential. The terminal is also to send address information of the second server and the second access credential to the first IoT device. The first IoT device is configured to receive the address information and the second access credential, and send a fourth request to the second server, where the fourth request is configured to request registration of the first IoT device, and the fourth request carries the second access credential. The second server registers the first IoT device according to the fourth request, generates registration success information, and feeds back the registration success information to the terminal. And the terminal receives the registration success information pushed by the second server. The first IoT device is displayed on a second interface of the terminal with successful addition.

In a third aspect, an embodiment of the present application provides a terminal, which is characterized in that the terminal includes: one or more processors; and a memory in which the code is stored; and when the code is executed by the terminal, the terminal is caused to execute the network allocation method of the internet of things equipment according to the first aspect.

In a fourth aspect, embodiments of the present application provide a chip system, where the chip system is applied to an electronic device. The system-on-chip includes one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected through a circuit; the interface circuit is used for receiving signals from the memory of the electronic device and sending signals to the processor, wherein the signals comprise computer instructions stored in the memory; the computer instructions, when executed by the processor, cause the electronic device to perform the internet of things device networking method as described in the first aspect.

In a fifth aspect, an embodiment of the present application provides a computer storage medium, which includes computer instructions, where the computer instructions, when executed on an electronic device and a server, cause the electronic device to perform the network allocation method of the internet of things device according to the first aspect.

In a sixth aspect, an embodiment of the present application provides a computer program product, which is characterized in that, when the computer program product runs on a computer, the computer is caused to perform the internet of things device networking method according to the first aspect.

The corresponding advantages of the other aspects mentioned above may be found in the description of the advantages of the method aspects, and are not repeated here.

In an embodiment of the present application, the terminal stores an identification of at least one IoT device. After the terminal stores the identity of the at least one IoT device, the terminal receives a broadcast sent by the first IoT device, where the broadcast carries the first identity of the first IoT device. The terminal scans a broadcast sent by the first IoT device and parses a first identifier carried in the broadcast. The terminal determines that the first identification is an identification of at least one IoT device, i.e., the first IoT device is one of the at least one IoT device. The terminal sends network information to the first IoT device according to the first identification. The first IoT device receives the network information and connects to the network according to the network information. In this way, the first IoT device automatically completes the distribution network without the user perceiving the distribution network operation, that is, without the user manually participating in the distribution network process of the IoT device, thereby improving the distribution network efficiency. Moreover, multiple IoT devices may implement automatic distribution network concurrently, resulting in higher distribution network efficiency.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the following description will briefly introduce the drawings that are needed in the embodiments or the description of the prior art, it is obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

FIG. 1 is a schematic illustration of an interface of a terminal;

FIG. 2 is a schematic diagram of yet another interface of a terminal;

FIG. 3 is a schematic diagram of yet another interface of a terminal;

FIG. 4 is a schematic diagram of yet another interface of a terminal;

FIG. 5 is a schematic diagram of yet another interface of a terminal;

FIG. 6 is a schematic diagram of yet another interface of a terminal;

FIG. 7 is a schematic diagram of yet another interface of a terminal;

FIG. 8 is a schematic diagram of yet another interface of a terminal;

FIG. 9 is a schematic diagram of yet another interface of a terminal;

FIG. 10 is a schematic diagram of yet another interface of a terminal;

fig. 11 is a schematic diagram of an interface of a terminal according to an embodiment of the present application;

fig. 12 is a schematic diagram of yet another interface of a terminal according to an embodiment of the present application;

Fig. 13 is a schematic diagram of yet another interface of a terminal according to an embodiment of the present application;

FIG. 14 is a schematic diagram of a system according to an embodiment of the present disclosure;

fig. 15 is a schematic structural diagram of a terminal according to an embodiment of the present application;

fig. 16 is a schematic structural diagram of a server according to an embodiment of the present application;

fig. 17 is a schematic flow chart of a network allocation method for an internet of things device according to an embodiment of the present application;

fig. 18 is a schematic flow chart of a network allocation method for an internet of things device according to an embodiment of the present application;

fig. 19 is a flow chart of a network configuration method for an internet of things device according to an embodiment of the present application.

Detailed Description

The terms "first" and "second" are used below for descriptive purposes only and are not to be construed as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defining "a first" or "a second" may explicitly or implicitly include one or more such feature. In the description of the present embodiment, unless otherwise specified, the meaning of "plurality" is two or more.

Currently, ioT device networking methods are typically: the user manually resets the IoT device into the network configuration state and manually completes the IoT device network configuration registration on the application of the terminal device, requiring the user to participate in the whole process.

Exemplary, as shown in fig. 1, a schematic diagram of a main interface of a terminal device is shown. The user clicks on an application (e.g., smart life application, etc.) on the terminal device 110. The smart life application is started. Terminal device 110 displays interface 111 as shown in fig. 2. The user enters a user account (e.g., hua as an account) and password on the interface 111 and clicks the "login" control. The interface of the terminal device 110 jumps from the interface 111 shown in fig. 2 to the interface 112 shown in fig. 3. An IoT device, such as a smart lipid scale, is displayed on the interface 112. A control 1121 is also displayed on the interface 112. When the user clicks control 1121, control 113 is displayed on interface 112 of terminal device 110 as shown in FIG. 4. When the user clicks the "Add device" option in control 113, interface 112 of terminal device 110 becomes interface 114. The interface 114 represents the IoT device being scanned for by the terminal device 110 and displays the scanned IoT device. If the user wants to add a certain class of IoT devices (e.g., sports IoT devices, health IoT devices, etc.), the user may click on a "manually add" control 1142 displayed on interface 114. The terminal device 110 may search for IoT devices and add according to user needs. If the user does not know the particular model or name of a particular IoT device, the user may click on a "scan add" control 1143 displayed on interface 114 to add the IoT device by scanning the bar code on the IoT device. When the user clicks the "connect" control on the smart speaker card 1141 on the interface 114 of the terminal device 110, the interface of the terminal device 110 jumps from the interface 114 shown in fig. 5 to the interface 115 shown in fig. 6. An icon of the smart box, a network device name of the smart box, and an input box of a password are displayed on the interface 115. The user may manually enter a network name and password in the input box. After the user enters the network name and password, click on the "next" control. The interface of the terminal device 110 jumps to the interface 116 shown in fig. 7. The connection progress of the terminal device 110 with the IoT device is displayed on the interface 116. Terminal device 110 displays interface 117 shown in fig. 8 when the connection of terminal device 110 with the IoT device is successful. After the terminal device 110 completes the connection with the IoT device, the interface of the terminal device 110 displays an interface 118 as shown in fig. 9. Networking progress of the IoT devices is displayed on the interface 118. After the IoT device is successfully configured, the card of the IoT device is added to the interface 112 shown in fig. 3, so as to obtain an interface 119 shown in fig. 10.

In the IoT device networking process described above, the user needs to click on control 1121 shown in fig. 3, the user needs to click on control 113 shown in fig. 4, the user needs to click on the "connect" control on the smart speaker card 1141 shown in fig. 5, and the user needs to enter a password on interface 115 shown in fig. 6. As can be seen, the user is required to participate throughout the IoT device networking process. When the number of the IoT devices is large, the plurality of IoT devices need to be distributed one by one, and the operation is complex. Therefore, the existing network distribution method of the Internet of things equipment has the problem of low network distribution efficiency.

In order to solve the above technical problem, in an embodiment of the present application, a terminal stores an identification of at least one IoT device. After the terminal stores the identity of the at least one IoT device, the terminal receives a broadcast sent by the first IoT device, where the broadcast carries the first identity of the first IoT device. The terminal scans a broadcast sent by the first IoT device and parses a first identifier carried in the broadcast. The terminal determines that the first identification is an identification of at least one IoT device, i.e., the first IoT device is one of the at least one IoT device. The terminal sends network information to the first IoT device according to the first identification. The first IoT device receives the network information and connects to the network according to the network information. In this way, the identity of the at least one IoT device is prestored in the terminal, and when the first IoT device needs to connect to the network, the terminal determines that the first IoT device is one of the at least one prestored IoT device and sends the network information to the first IoT device so that the first IoT device can connect to the network. In the whole distribution process of the first IoT device, the first IoT device automatically completes the distribution under the condition that the user does not perceive the distribution operation, that is, the user does not need to manually participate in the distribution process of the IoT device, and the distribution efficiency is improved. Moreover, multiple IoT devices may implement automatic distribution network concurrently, resulting in higher distribution network efficiency.

In one particular implementation, after an IoT device purchases, the terminal stores an identification of the IoT device. The terminal receives the broadcast sent by the IoT device. The terminal determines that the identifier carried in the broadcast is consistent with the stored identifier. The terminal sends a channel setup request to the IoT device. The IoT device establishes a communication channel with the terminal according to the request and sends establishment success information to the terminal. The terminal receives the establishment success information. The terminal sends network information to the IoT via the communication channel to facilitate the IoT device to connect to a network in accordance with the network information.

In some embodiments, a user may purchase a first IoT device through a first application on a terminal. The first application may be a system application or a three-party application. The first application is a system application, which can be understood that the terminal, the first application, a server corresponding to the first application, the first IoT device, a server corresponding to the first IoT device, and the like are all of the same manufacturer. The first application is a three-party application, and it is understood that the first application and the server corresponding to the first application are different vendors.

In some embodiments, after a user purchases a first IoT device through a first application of a terminal, a server corresponding to the first application pushes a first identification of the first IoT device to the server of the first IoT device. The server of the first IoT device pushes the first identification of the first IoT device to the terminal. The terminal pre-stores a first identification of the first IoT device. Specifically, assuming that the first application is a three-party application, the server corresponding to the first application pushes the first identifier of the first IoT device to the server corresponding to the terminal. The server corresponding to the terminal pushes the first identification of the first IoT device to the server of the first IoT device.

For example, in comparison with the above-mentioned IoT device network allocation method provided in the embodiments of the present application, in the network allocation process of the first IoT device (e.g., the smart speaker), the terminal does not need to display the interfaces shown in fig. 2-8, i.e., the user does not need to operate on the interfaces shown in fig. 2-8 displayed by the terminal. The method comprises the following steps: and the user purchases the intelligent sound box through the terminal. Illustratively, the user clicks on an application (e.g., smart life application, etc.) shown in FIG. 1 on terminal device 110. The smart life application is started. Terminal device 110 displays interface 111 as shown in fig. 2. The user enters a user account (e.g., hua as an account) and password on the interface 111 and clicks the "login" control. The interface of the terminal device 110 jumps from the interface 111 shown in fig. 2 to the interface 112 shown in fig. 3. The user clicks on the "mall" control on the interface 112 and the interface of the terminal 110 displays merchandise information. After the user finds the merchandise information of the smart speaker and clicks to view, the interface of the terminal 110 jumps to the interface 1101 shown in fig. 11. Information of the intelligent speaker is displayed on the interface 1101. After the user selects the color, number, and the user clicks the "associate purchased device to Hua as an account" control displayed on the interface 1101 and clicks the "purchase immediately" control, the interface of the terminal jumps from the interface 1101 shown in fig. 11 to the interface 1103 shown in fig. 12. The user clicks on the "submit order" control on this interface 1103 and the interface of the terminal jumps to interface 1104 shown in fig. 13. Thus, the user has completed the purchase of the intelligent sound box. At this time, the server corresponding to the intelligent life application program sends the identification of the intelligent sound box to the server corresponding to the intelligent sound box. The server of the intelligent sound box pushes the identification of the intelligent sound box to the terminal, and the terminal stores the identification in advance. After the intelligent sound box purchase is completed, the user energizes the intelligent sound box. The intelligent sound box can send the identification to the terminal in a broadcasting mode, and the terminal compares the identification of the intelligent sound box with the prestored identification and establishes a communication channel with the intelligent sound box. And the terminal sends network information to the intelligent sound box through the communication channel. The intelligent sound box receives the network information and performs network connection according to the network information. At this time, the user enters the interface shown in fig. 3 as described above, and the interface shown in fig. 3 becomes the interface 119 shown in fig. 10. A card of the intelligent sound box is displayed on the interface 119, that is, the intelligent sound box is distributed with a network. Therefore, in the intelligent sound box network distribution process, a user does not have a frequent operation interface, automatic network distribution of the intelligent sound box is realized, and network distribution efficiency is high.

The network allocation method for the internet of things equipment provided by the embodiment of the application can be applied to a system shown in fig. 14. As shown in fig. 14, the system 100 may include a terminal 110, a plurality of IoT devices (e.g., a first IoT device 120, a second IoT device 130), and a plurality of servers (e.g., a first server 140, a second server 150, a third server 160).

Wherein the IoT device may comprise: intelligent household equipment, intelligent wearing equipment, intelligent traffic equipment, intelligent medical equipment, intelligent vehicle-mounted equipment and the like. The intelligent household equipment can comprise an intelligent sound box, a television, an air conditioner, a refrigerator and the like. The intelligent wearable device can comprise an intelligent watch, intelligent glasses, an intelligent bracelet and the like. The intelligent transportation device may include: solar devices, tachometers, cameras, etc. The smart medical device may include: intelligent thermometer, intelligent sphygmomanometer, intelligent electronic scale, etc. The intelligent in-vehicle apparatus may include: vehicle event data recorder, on-vehicle camera, on-vehicle stereo set etc.. Of course, ioT devices in the implementations of the present application are not limited to the devices listed above.

The terminal may be a device with a display function, such as a mobile phone, a tablet computer, a desktop, a laptop, a notebook, an Ultra-mobile personal computer (Ultra-mobile Personal Computer, UMPC), a handheld computer, a netbook, a personal digital assistant (Personal Digital Assistant, PDA), a wearable terminal, a television, a virtual reality device, or the like, and the specific form of the terminal is not particularly limited in the embodiment of the present application.

For example, as shown in fig. 14, the terminal 110 may be a cell phone and the first IoT device 120 and the second IoT device 130 may each be a smart speaker. The first server 140 may be a production line server, the second server 150 may be a mall server, and the third server 160 may be an IoT server.

For example, in the embodiment of the present application, taking the first IoT device (e.g., the smart speaker) 120 as an example, as described above, the user logs in the smart phone with the smart phone as an account number, and the smart phone server and the IoT server store the correspondence between the identity of the smart phone and the smart phone account number. After the user purchases the intelligent sound box in the Hua Cheng mall on the mobile phone, the Hua Cheng mall server sends a purchase success notification to the IoT server, wherein the notification carries the identification of the intelligent sound box and the Hua Cheng account number. After receiving the purchase success notice, the IoT server pushes the identification of the intelligent sound box to the mobile phone logging in the internet of things (IoT) as an account according to the internet of things (IoT) as an account, and the mobile phone stores in advance. After the intelligent sound box is electrified, the intelligent sound box sends a broadcast, and the broadcast carries the identification of the intelligent sound box. The mobile phone scans the broadcast sent by the intelligent sound box and analyzes the identification of the intelligent sound box carried in the broadcast. The mobile phone compares the identification of the intelligent sound box with the pre-stored information. After the comparison is successful, the mobile phone and the intelligent sound box are in communication connection. And the mobile phone sends information such as network information and the like to the intelligent sound box. The intelligent sound box receives the network information and performs network connection according to the network information.

Fig. 15 is a block diagram of the structure of the terminal.

As shown in fig. 15, the terminal 110 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (universal serial bus, USB) interface 230, a charge management module 240, a power management module 241, a battery 242, an antenna 1, an antenna 2, a mobile communication module 250, a wireless communication module 260, an audio module 270, a speaker 270A, a receiver 270B, a microphone 270C, an earphone interface 270D, a sensor module 280, a key 290, a motor 291, an indicator 292, a camera 293, a display 294, a subscriber identity module (subscriber identification module, SIM) card interface 295, and the like. The sensor module 280 may include a pressure sensor 280A, a gyroscope sensor 280B, a barometric sensor 280C, a magnetic sensor 280D, an acceleration sensor 280E, a distance sensor 280F, a proximity sensor 280G, a fingerprint sensor 280H, a temperature sensor 280J, a touch sensor 280K, an ambient light sensor 280L, a bone conduction sensor 280M, and the like.

It should be understood that the structure illustrated in the embodiments of the present invention does not constitute a specific limitation on the terminal 110. In other embodiments of the present application, terminal 110 may include more or less components than illustrated, or certain components may be combined, or certain components may be split, or different arrangements of components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

Processor 210 may include one or more processing units such as, for example: the processor 210 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), a controller, a video codec, a digital signal processor (digital signal processor, DSP), a baseband processor, and/or a neural network processor (neural-network processing unit, NPU), etc. Wherein the different processing units may be separate devices or may be integrated in one or more processors.

The controller can generate operation control signals according to the instruction operation codes and the time sequence signals to finish the control of instruction fetching and instruction execution.

A memory may also be provided in the processor 210 for storing instructions and data. In some embodiments, the memory in the processor 210 is a cache memory. The memory may hold instructions or data that the processor 210 has just used or recycled. If the processor 210 needs to reuse the instruction or data, it may be called directly from the memory. Repeated accesses are avoided and the latency of the processor 210 is reduced, thereby improving the efficiency of the system.

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

It should be understood that the interfacing relationship between the modules illustrated in the embodiment of the present invention is only illustrative, and does not limit the structure of the terminal 110. In other embodiments of the present application, the terminal 110 may also use different interfacing manners in the above embodiments, or a combination of multiple interfacing manners.

The charge management module 240 is configured to receive a charge input from a charger. The charger can be a wireless charger or a wired charger. In some wired charging embodiments, the charge management module 240 may receive a charging input of a wired charger through the USB interface 230. In some wireless charging embodiments, the charge management module 240 may receive wireless charging input through a wireless charging coil of the terminal 110. The charging management module 240 may also provide power to the electronic device through the power management module 241 while charging the battery 242.

The power management module 241 is used for connecting the battery 242, and the charge management module 240 and the processor 210. The power management module 241 receives input from the battery 242 and/or the charge management module 240 and provides power to the processor 210, the internal memory 221, the display 294, the camera 293, the wireless communication module 260, and the like. The power management module 241 may also be configured to monitor battery capacity, battery cycle times, battery health (leakage, impedance), and other parameters. In other embodiments, the power management module 241 may also be disposed in the processor 210. In other embodiments, the power management module 241 and the charge management module 240 may be disposed in the same device.

The wireless communication function of the terminal 110 may be implemented by the antenna 1, the antenna 2, the mobile communication module 250, the wireless communication module 260, a modem processor, a baseband processor, and the like.

The antennas 1 and 2 are used for transmitting and receiving electromagnetic wave signals. Each antenna in terminal 110 may be configured to cover a single or multiple communication bands. Different antennas may also be multiplexed to improve the utilization of the antennas. For example: the antenna 1 may be multiplexed into a diversity antenna of a wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 250 may provide a solution including 2G/3G/4G/5G wireless communication applied on the terminal 110. The mobile communication module 250 may include at least one filter, switch, power amplifier, low noise amplifier (low noise amplifier, LNA), etc. The mobile communication module 250 may receive electromagnetic waves from the antenna 1, perform processes such as filtering, amplifying, and the like on the received electromagnetic waves, and transmit the processed electromagnetic waves to the modem processor for demodulation. The mobile communication module 250 can amplify the signal modulated by the modem processor, and convert the signal into electromagnetic waves through the antenna 1 to radiate. In some embodiments, at least some of the functional modules of the mobile communication module 250 may be disposed in the processor 210. In some embodiments, at least some of the functional modules of the mobile communication module 250 may be provided in the same device as at least some of the modules of the processor 210.

The modem processor may include a modulator and a demodulator. The modulator is used for modulating the low-frequency baseband signal to be transmitted into a medium-high frequency signal. The demodulator is used for demodulating the received electromagnetic wave signal into a low-frequency baseband signal. The demodulator then transmits the demodulated low frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and then transferred to the application processor. The application processor outputs sound signals through an audio device (not limited to speaker 270A, receiver 270B, etc.), or displays images or video through display screen 294. In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be provided in the same device as the mobile communication module 250 or other functional module, independent of the processor 210.

The wireless communication module 260 may provide solutions for wireless communication including wireless local area network (wireless local area networks, WLAN) (e.g., wireless fidelity (wireless fidelity, wi-Fi) network), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field wireless communication technology (near field communication, NFC), infrared technology (IR), etc. applied on the terminal 110. The wireless communication module 260 may be one or more devices that integrate at least one communication processing module. The wireless communication module 260 receives electromagnetic waves via the antenna 2, modulates the electromagnetic wave signals, filters the electromagnetic wave signals, and transmits the processed signals to the processor 210. The wireless communication module 260 may also receive a signal to be transmitted from the processor 210, frequency modulate it, amplify it, and convert it to electromagnetic waves for radiation via the antenna 2.

In some embodiments, antenna 1 and mobile communication module 250 of terminal 110 are coupled, and antenna 2 and wireless communication module 260 are coupled, so that terminal 110 may communicate with a network and other devices through wireless communication techniques. The wireless communication techniques may include the Global System for Mobile communications (global system for mobile communications, GSM), general packet radio service (general packet radio service, GPRS), code division multiple access (code division multiple access, CDMA), wideband code division multiple access (wideband code division multiple access, WCDMA), time division code division multiple access (time-division code division multiple access, TD-SCDMA), long term evolution (long term evolution, LTE), BT, GNSS, WLAN, NFC, FM, and/or IR techniques, among others. The GNSS may include a global satellite positioning system (global positioning system, GPS), a global navigation satellite system (global navigation satellite system, GLONASS), a beidou satellite navigation system (beidou navigation satellite system, BDS), a quasi zenith satellite system (quasi-zenith satellite system, QZSS) and/or a satellite based augmentation system (satellite based augmentation systems, SBAS).

In some embodiments, the wireless communication module 260 receives the broadcast sent by the IoT device, scans the broadcast sent by the first IoT device, and parses the first identifier carried in the broadcast. The wireless communication module 260 sends network information to the first IoT device according to the first identification. In some embodiments, the processor determines the first identification as an identification of the at least one IoT device, i.e., the first IoT device is one of the at least one IoT device.

Terminal 110 implements display functions via a GPU, display screen 294, application processor, etc. The GPU is a microprocessor for image processing, and is connected to the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 210 may include one or more GPUs that execute program instructions to generate or change display information.

The display 294 is used to display images, videos, and the like. The display 294 includes a display panel. The display panel may employ a liquid crystal display (liquid crystal display, LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode (AMOLED) or an active-matrix organic light-emitting diode (matrix organic light emitting diode), a flexible light-emitting diode (flex), a mini, a Micro led, a Micro-OLED, a quantum dot light-emitting diode (quantum dot light emitting diodes, QLED), or the like. In some embodiments, terminal 110 may include 1 or N displays 294, N being a positive integer greater than 1. In some embodiments, display 294 displays an interface as shown in FIGS. 1-13.

Terminal 110 may implement shooting functions through an ISP, a camera 293, a video codec, a GPU, a display 294, an application processor, and the like.

The ISP is used to process the data fed back by the camera 293. For example, when photographing, the shutter is opened, light is transmitted to the camera photosensitive element through the lens, the optical signal is converted into an electric signal, and the camera photosensitive element transmits the electric signal to the ISP for processing and is converted into an image visible to naked eyes. ISP can also optimize the noise, brightness and skin color of the image. The ISP can also optimize parameters such as exposure, color temperature and the like of a shooting scene. In some embodiments, the ISP may be provided in the camera 293.

The camera 293 is used to capture still images or video. The object generates an optical image through the lens and projects the optical image onto the photosensitive element. The photosensitive element may be a charge coupled device (charge coupled device, CCD) or a Complementary Metal Oxide Semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, which is then transferred to the ISP to be converted into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. The DSP converts the digital image signal into an image signal in a standard RGB, YUV, or the like format. In some embodiments, terminal 110 may include 1 or N cameras 293, N being a positive integer greater than 1.

The digital signal processor is used for processing digital signals, and can process other digital signals besides digital image signals. For example, when the terminal 110 selects a frequency bin, the digital signal processor is used to fourier transform the frequency bin energy, etc.

Video codecs are used to compress or decompress digital video. The terminal 110 may support one or more video codecs. In this way, terminal 110 may play or record video in multiple encoding formats, such as: dynamic picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4, etc.

The NPU is a neural-network (NN) computing processor, and can rapidly process input information by referencing a biological neural network structure, for example, referencing a transmission mode between human brain neurons, and can also continuously perform self-learning. Applications such as intelligent cognition of the terminal 110 can be implemented by the NPU, for example: image recognition, face recognition, speech recognition, text understanding, etc.

The external memory interface 120 may be used to connect an external memory card, such as a Micro SD card, to realize the memory capability of the extension terminal 110. The external memory card communicates with the processor 210 through the external memory interface 120 to implement data storage functions. For example, files such as music, video, etc. are stored in an external memory card.

Internal memory 221 may be used to store computer executable program code that includes instructions. The internal memory 221 may include a storage program area and a storage data area. The storage program area may store an application program (such as a sound playing function, an image playing function, etc.) required for at least one function of the operating system, etc. The storage data area may store data (e.g., audio data, phonebook, etc.) created during use of the terminal 110, etc. In addition, the internal memory 221 may include a high-speed random access memory, and may further include a nonvolatile memory such as at least one magnetic disk storage device, a flash memory device, a universal flash memory (universal flash storage, UFS), and the like. The processor 210 performs various functional applications of the terminal 110 and data processing by executing instructions stored in the internal memory 221 and/or instructions stored in a memory provided in the processor.

In some embodiments, the internal memory 221 may store an identification of the at least one IoT device. Alternatively, the internal memory 221 may store an identification of the at least one IoT device and an access credential of the at least one IoT device. Still alternatively, the internal memory 221 may also store an identification of the at least one IoT device in association with the user account. Still alternatively, the internal memory 221 may also store an identification of the at least one IoT device, an access credential, in association with the user account.

Terminal 110 may implement audio functions via audio module 270, speaker 270A, receiver 270B, microphone 270C, ear-headphone interface 270D, and an application processor, among others. Such as music playing, recording, etc.

The audio module 270 is used to convert digital audio information into an analog audio signal output and also to convert an analog audio input into a digital audio signal. The audio module 270 may also be used to encode and decode audio signals. In some embodiments, the audio module 270 may be disposed in the processor 210, or some functional modules of the audio module 270 may be disposed in the processor 210.

Speaker 270A, also referred to as a "horn," is used to convert audio electrical signals into sound signals. Terminal 110 may listen to music, or to hands-free calls, through speaker 270A.

A receiver 270B, also referred to as a "earpiece", is used to convert the audio electrical signal into a sound signal. When terminal 110 receives a call or voice message, it can receive voice by placing receiver 270B close to the human ear.

Microphone 270C, also referred to as a "microphone" or "microphone," is used to convert sound signals into electrical signals. When making a call or transmitting voice information, the user can sound near the microphone 270C through the mouth, inputting a sound signal to the microphone 270C. Terminal 110 may be provided with at least one microphone 270C. In other embodiments, the terminal 110 may be provided with two microphones 270C, and may implement a noise reduction function in addition to collecting sound signals. In other embodiments, the terminal 110 may be further provided with three, four or more microphones 270C to collect sound signals, reduce noise, identify the source of sound, implement directional recording functions, etc.

The earphone interface 270D is for connecting a wired earphone. Earphone interface 270D may be USB interface 230 or a 3.5mm open mobile electronic device platform (open mobile terminal platform, OMTP) standard interface, american cellular telecommunications industry association (cellular telecommunications industry association of the USA, CTIA) standard interface.

The pressure sensor 280A is used to sense a pressure signal, and may convert the pressure signal into an electrical signal. In some embodiments, pressure sensor 280A may be disposed on display 294. The pressure sensor 280A is of various types, such as a resistive pressure sensor, an inductive pressure sensor, a capacitive pressure sensor, and the like. The capacitive pressure sensor may be a capacitive pressure sensor comprising at least two parallel plates with conductive material. When a force is applied to the pressure sensor 280A, the capacitance between the electrodes changes. Terminal 110 determines the strength of the pressure based on the change in capacitance. When a touch operation is applied to the display 294, the terminal 110 detects the intensity of the touch operation according to the pressure sensor 280A. The terminal 110 may also calculate the location of the touch based on the detection signal of the pressure sensor 280A. In some embodiments, touch operations that act on the same touch location, but at different touch operation strengths, may correspond to different operation instructions. For example: and executing an instruction for checking the short message when the touch operation with the touch operation intensity smaller than the first pressure threshold acts on the short message application icon. And executing an instruction for newly creating the short message when the touch operation with the touch operation intensity being greater than or equal to the first pressure threshold acts on the short message application icon.

The gyro sensor 280B may be used to determine a motion gesture of the terminal 110. In some embodiments, the angular velocity of terminal 110 about three axes (i.e., x, y, and z axes) may be determined by gyro sensor 280B. The gyro sensor 280B may be used for photographing anti-shake. Illustratively, when the shutter is pressed, the gyro sensor 280B detects the shake angle of the terminal 110, calculates the distance to be compensated by the lens module according to the angle, and makes the lens counteract the shake of the terminal 110 through the reverse motion, thereby realizing anti-shake. The gyro sensor 280B may also be used for navigating, somatosensory game scenes.

The air pressure sensor 280C is used to measure air pressure. In some embodiments, terminal 110 calculates altitude from barometric pressure values measured by barometric pressure sensor 280C, aiding in positioning and navigation.

The magnetic sensor 280D includes a hall sensor. The terminal 110 may detect the opening and closing of the flip cover using the magnetic sensor 280D. In some embodiments, when the terminal 110 is a flip machine, the terminal 110 may detect the opening and closing of the flip according to the magnetic sensor 280D. And then according to the detected opening and closing state of the leather sheath or the opening and closing state of the flip, the characteristics of automatic unlocking of the flip and the like are set.

The acceleration sensor 280E may detect the magnitude of acceleration of the terminal 110 in various directions (typically three axes). The magnitude and direction of gravity may be detected when terminal 110 is stationary. The electronic equipment gesture recognition method can also be used for recognizing the gesture of the electronic equipment, and is applied to horizontal and vertical screen switching, pedometers and other applications.

A distance sensor 280F for measuring distance. The terminal 110 may measure the distance by infrared or laser. In some embodiments, the terminal 110 may range using the distance sensor 280F to achieve fast focusing.

Proximity light sensor 280G may include, for example, a Light Emitting Diode (LED) and a light detector, such as a photodiode. The light emitting diode may be an infrared light emitting diode. The terminal 110 emits infrared light outward through the light emitting diode. The terminal 110 detects infrared reflected light from nearby objects using a photodiode. When sufficient reflected light is detected, it may be determined that there is an object near the terminal 110. When insufficient reflected light is detected, the terminal 110 may determine that there is no object in the vicinity of the terminal 110. The terminal 110 can detect that the user holds the terminal 110 close to the ear by using the proximity light sensor 280G, so as to automatically extinguish the screen for the purpose of saving power. The proximity light sensor 280G may also be used in holster mode, pocket mode to automatically unlock and lock the screen.

The ambient light sensor 280L is used to sense ambient light level. The terminal 110 may adaptively adjust the brightness of the display 294 according to the perceived ambient light level. The ambient light sensor 280L may also be used to automatically adjust white balance during photographing. The ambient light sensor 280L may also cooperate with the proximity light sensor 280G to detect whether the terminal 110 is in a pocket to prevent false touches.

The fingerprint sensor 280H is used to collect a fingerprint. The terminal 110 can utilize the collected fingerprint characteristics to realize fingerprint unlocking, access an application lock, fingerprint photographing, fingerprint incoming call answering and the like.

The temperature sensor 280J is used to detect temperature. In some embodiments, terminal 110 performs a temperature processing strategy using the temperature detected by temperature sensor 280J. For example, when the temperature reported by temperature sensor 280J exceeds a threshold, terminal 110 performs a reduction in the performance of a processor located in the vicinity of temperature sensor 280J in order to reduce power consumption for thermal protection. In other embodiments, terminal 110 heats battery 242 when the temperature is below another threshold to avoid low temperatures causing terminal 110 to shut down abnormally. In other embodiments, terminal 110 performs boosting of the output voltage of battery 242 when the temperature is below a further threshold to avoid abnormal shutdown caused by low temperatures.

The touch sensor 280K, also referred to as a "touch device". The touch sensor 280K may be disposed on the display screen 294, and the touch sensor 280K and the display screen 294 form a touch screen, which is also referred to as a "touch screen". The touch sensor 280K is used to detect a touch operation acting on or near it. The touch sensor may communicate the detected touch operation to the application processor to determine the touch event type. Visual output related to touch operations may be provided through the display 294. In other embodiments, touch sensor 280K may also be disposed on a surface of terminal 110 at a different location than display 294.

Bone conduction sensor 280M may acquire a vibration signal. In some embodiments, bone conduction sensor 280M may acquire a vibration signal of a human vocal tract vibrating bone pieces. The bone conduction sensor 280M may also contact the pulse of the human body to receive the blood pressure pulsation signal. In some embodiments, bone conduction sensor 280M may also be provided in a headset, in combination with an osteoinductive headset. The audio module 270 may analyze the voice signal based on the vibration signal of the sound portion vibration bone piece obtained by the bone conduction sensor 280M, so as to implement the voice function. The application processor can analyze heart rate information based on the blood pressure beat signal acquired by the bone conduction sensor 280M, so as to realize a heart rate detection function.

Keys 290 include a power on key, a volume key, etc. The keys 290 may be mechanical keys. Or may be a touch key. Terminal 110 may receive key inputs, generating key signal inputs related to user settings of terminal 110 and function control.

The motor 291 may generate a vibration alert. The motor 291 may be used for incoming call vibration alerting or for touch vibration feedback. For example, touch operations acting on different applications (e.g., photographing, audio playing, etc.) may correspond to different vibration feedback effects. The motor 291 may also correspond to different vibration feedback effects by touch operations applied to different areas of the display 294. Different application scenarios (such as time reminding, receiving information, alarm clock, game, etc.) can also correspond to different vibration feedback effects. The touch vibration feedback effect may also support customization.

The indicator 292 may be an indicator light, which may be used to indicate a state of charge, a change in power, a message indicating a missed call, a notification, etc.

Of course, the terminal 110 may also include other functional units, which are not limited in this embodiment of the present application.

Fig. 16 is a block diagram of the structure of the server.

By way of example, fig. 16 shows a schematic diagram of the structure of the servers (e.g., the first server 140, the second server 150, and the third server 160). In a specific implementation, each server (e.g., the first server 140, the second server 150, the third server 160, etc.) shown in fig. 16 may adopt the composition structure shown in fig. 14 or include the components shown in fig. 15. Fig. 16 is a schematic diagram of a server according to an embodiment of the present application, where the server may include a processor 301 and a memory 304. Further, the server may also include a communication line 302 and a communication interface 303. The processor 301, the memory 304, and the communication interface 303 may be connected by a communication line 302.

The processor 301 may be a central processing unit (central processing unit, CPU), a general purpose processor, a network processor (network processor, NP), a digital signal processor (digital signal processing, DSP), a microprocessor, a microcontroller, a programmable logic device (programmable logic device, PLD), or any combination thereof. The processor 301 may also be any other device having a processing function, such as a circuit, a device, or a software module, without limitation.

Communication line 302 for conveying information between the components included in the server.

A communication interface 303 for communicating with other devices or other communication networks. The other communication network may be an ethernet, a radio access network (radio access network, RAN), a wireless local area network (wireless local area networks, WLAN), etc. The communication interface 303 may be a module, a circuit, a transceiver, or any device capable of enabling communication.

Memory 304 for storing instructions. Wherein the instructions may be computer programs.

The memory 304 may be, but not limited to, a read-only memory (ROM) or other type of static storage device capable of storing static information and/or instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device capable of storing information and/or instructions, and an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc (compact disc read-only memory, CD-ROM), or other optical disc storage, optical disc storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc), magnetic disc storage medium, or other magnetic storage device.

It should be noted that, the memory 304 may exist separately from the processor 301, or may be integrated with the processor 301. Memory 304 may be used to store instructions or program code or some data, etc. Memory 304 may be located within the server or outside the server, without limitation.

The processor 301 is configured to execute the instructions stored in the memory 304, so as to implement a service switching method provided in the following embodiments of the present application. For example, when the server is a chip or a system on a chip in a network device, the processor 301 executes instructions stored in the memory 304 to implement steps performed by the network device in the embodiments described below in this application.

In one example, processor 301 may include one or more CPUs, such as CPU0 and CPU1 in fig. 16.

As an alternative implementation, the server includes multiple processors, e.g., processor 307 may be included in addition to processor 301 in fig. 16.

As an alternative implementation, the server further comprises an output device 305 and an input device 306. Illustratively, the input device 306 is a keyboard, mouse, microphone, or joystick device, and the output device 305 is a display screen, speaker (spaker), or the like.

It should be noted that the server may be a desktop computer, a portable computer, a web server, a mobile phone, a tablet computer, a wireless terminal, an embedded device, a chip system, or a device having a similar structure in fig. 16. Further, the constituent structure shown in fig. 16 does not constitute a limitation of the server, and the server may include more or less components than those shown in fig. 16, or may combine some components, or may be arranged in different components, in addition to those shown in fig. 16.

In the embodiment of the application, the chip system may be formed by a chip, and may also include a chip and other discrete devices.

Further, the actions, terms, etc. referred to between the embodiments of the present application are not limited to each other. In the embodiment of the present application, the name of the message or the name of the parameter in the message, etc. interacted between the devices are only an example, and other names may also be adopted in the specific implementation, and are not limited.

Fig. 17 is a schematic flow chart of a network configuration method for an internet of things device according to an embodiment of the present application. As shown in fig. 17, the method can be described in the following stages, specifically:

first stage, preparation stage

S400, when the first IoT device is produced, the first server writes the first identifier of the first IoT device, or the first identifier and the preset first access credential, into the first IoT device.

The first server may be configured to store information generated during the production process of the device, such as a serial number, a physical address, etc. of the device. The first server may be a server for a production line, for example.

Wherein the first identification may be used to uniquely identify the first IoT device.

The first identification may be an intra-pair identification of the first IoT device, which may be understood as an identification presented internally to the vendor of the IoT device, such as a serial number, a physical address, an identifier (unique device identifier, UDID), etc.

The first identification may also be an external identification of the first IoT device. The external identifier may be understood as an identifier, such as a string, an array, etc., presented externally to the vendor of the IoT device.

In one implementation manner, taking the first identifier as an external identifier as an example, the generation manner of the first identifier may be: the first server generates from a second identification of the first IoT device, wherein the second identification can be understood as an intra-pair identification. Wherein the second identification may comprise at least one of a serial number, a physical address, and an identifier.

For example, the first server may hash a sequence number of the first IoT device to obtain a first identification. Alternatively, the first server may hash the sequence number and the physical address of the first IoT device to obtain the first identification. Still alternatively, the first server may hash the UDID of the first IoT device to obtain the first identification. Of course, embodiments of the present application are not limited to the implementations listed above. In addition, embodiments of the present application are not limited to hash processing, and other algorithms, such as an identification algorithm, may also be used. The embodiment of the present application is not particularly limited.

The preset first access credential may be used to encrypt or decrypt the network information. The network information may include a network name (e.g., wifi name) and a password. The first server may store a preset first access credential in association with a first identification of a first IoT device.

S401, the first IoT device is put on shelf to the second server, and the first identity is registered on the second server.

The second server may be a server of the same vendor as the first IoT device, or the second server may be a third party server. The application program or the client corresponding to the second server is installed on the terminal.

The second server may be used to push device information to an application or client on the terminal to display the device information on the terminal for viewing or manipulation by the user.

Wherein, as described above, if the first identification is an intra-pair identification of the first IoT device, the first identification is registered on the second server. If the first identifier is an external identifier of the first IoT device, the first identifier is generated according to a second identifier of the first IoT device, the second identifier is an internal identifier of the first IoT device, and the second identifier is registered on the second server.

In some embodiments, the network configuration method for the internet of things device provided by the embodiment of the application further includes: s402, the second server sends the first identification of the first IoT device and the preset first access credential to the third server. Correspondingly, the third server receives the first identifier and the preset first access credential.

Wherein the third server may be understood as a server corresponding to the first IoT device. The third server may become an IoT server.

The third server is used for pushing the first identification of the equipment purchased by the user and the preset first access certificate to the terminal after the user purchases the equipment.

In a specific implementation manner, S402 may specifically be that, before the user purchases the first IoT device, the second server sends the first identifier of the first IoT device and the preset first access credential to the third server.

In another specific implementation, S402 may specifically be that, after the user purchases the first IoT device, the second server sends a notification to the third server, where the notification includes the first user account. The notification is to instruct the third server to obtain a first identification of the first IoT device and a preset first access credential from the second server. And the third server sends an acquisition request to the second server, wherein the request carries the first user account. The second server receives the acquisition request and pushes the first identification of the first IoT device and the preset first access credential to the third server according to the request.

In another specific implementation manner, S402 may specifically be that, after the user purchases the first IoT device, the second server sends a notification to the third server, where the notification carries the first user account and the second identifier. And the third server sends an acquisition request to the second server according to the notification, wherein the request carries the second identifier and the first user account. The second server receives the acquisition request and pushes the first identification of the first IoT device and the preset first access credential to the third server according to the request.

Illustratively, taking the example where the second server is a server of the same vendor as the first IoT device:

after the application on the user operation terminal purchases the first IoT device, the second server sends a notification message to the third server, wherein the notification message carries the first identification of the first IoT device and the first user account. And the third server sends an acquisition request to the first server according to the notification message, wherein the acquisition request carries the first identification of the first IoT device and the first user account. The first server searches a preset first access certificate corresponding to the first identifier according to the acquisition request, and sends the first identifier and the preset first access certificate to the third server.

Illustratively, taking the example that the second server is a three-way server:

after the user operates an application program on the terminal to purchase the first IoT device, the second server sends a notification message to the server of the terminal, wherein the notification message carries a first identification of the first IoT device and a first user account. The server of the terminal sends the notification message to a third server, and the third server sends an acquisition request to the first server according to the notification message, wherein the acquisition request carries a first identifier of the first IoT device and a first user account. The first server searches a preset first access certificate corresponding to the first identifier according to the acquisition request, and sends the first identifier and the preset first access certificate to the third server.

Second stage, purchasing stage

S410, the terminal receives a first operation of a user on the first application, wherein the first operation is used for indicating the terminal to start the first application by adopting the first user account.

Wherein the first application may be a system application. The system application may be understood as an application of the same manufacturer as the terminal. For example, the terminal is a mobile phone and the first application is a mall application. Alternatively, the first application may be a three-way application.

The first user account may be understood as a login account of the first application. In an exemplary embodiment of the present application, the first user account may be a Hua account.

Wherein the first operation may refer to a gesture operation, which may include a click operation, a press operation, a slide operation, or the like. The click operation may also include a single click operation, a double click operation, and the like.

The first operation is used for indicating the terminal to start the first application by adopting the first user account. The first operation may be operating a control on an interface of the first application.

First, the first operation is to operate a user icon.

Exemplary, specific implementations of S410 may be: the user clicks a first application on the desktop of the first mobile phone, the first mobile phone receives clicking operation of the user on the first application, and the first mobile phone displays an interface of the first application. When a user operates a user icon on an interface of a first application, the first mobile phone starts the first application by adopting a first user account.

Second, the first operation is to operate an input box on the first application.

Exemplary, specific implementations of S410 may be: the user clicks a first application on the desktop of the first mobile phone, the first mobile phone receives clicking operation of the user on the first application, and the first mobile phone displays an interface of the first application. The user inputs a first user account in an input box of an interface of a first application. When a user submits a first user account input on an interface of a first application, the first mobile phone starts the first application by adopting the first user account.

S411, responding to the first operation, and sending a first request to a second server by the terminal, wherein the first request carries a first user account. Accordingly, the second server receives the first request.

And S412, the second server starts the first application according to the first request and returns login success information to the terminal.

As described above, the first application may be a system application or a three-way application. Correspondingly, the second server can be a server of the system application or a three-party server.

In a specific implementation, as shown in fig. 18, the first application is a system application, and the second server is a server of the system application. S412 may specifically be: and S412a, the second server starts the first application according to the first request and returns login success information to the terminal.

In another specific implementation, as shown in fig. 18, the first application is a three-party application and the second server is a three-party server. S412 may specifically be: and S412b1, the second server sends a second request to the fourth server according to the first request, wherein the second request is used for requesting the fourth server to authorize the second server to log in the first application by adopting the first user account. Accordingly, the fourth server receives the second request. The first user account is an account of an application corresponding to the fourth server, and a manufacturer of the fourth server and a manufacturer of the second server achieve a protocol for logging in the first application corresponding to the second server by adopting the first user account. And S412b2, the fourth server feeds back authorization information to the second server according to the second request. Correspondingly, the second server receives the authorization information returned by the fourth server. And S412b3, the second server starts the first application according to the authorization information and returns login success information to the terminal.

S413, the terminal receives a second operation of the first IoT device displayed on the interface of the first application by the user.

The second operation may include one or more of a click operation, a press operation, a slide operation, a select operation. The click operation may include a single click operation, a double click operation, and the like.

The second operation may be to indicate completion of the order of the first IoT device.

Illustratively, the user clicks on the "mall" control on the interface 112 and the interface of the terminal 110 displays merchandise information. After the user finds the merchandise information of the smart speaker and clicks to view, the interface of the terminal 110 jumps to the interface 1101 shown in fig. 11. Information of the intelligent speaker is displayed on the interface 1101. After the user selects the color, number of smart speakers, and clicks the "buy immediately" control, the interface of the terminal jumps from interface 1101 shown in FIG. 11 to interface 1103 shown in FIG. 12. The user clicks on the "submit order" control on this interface 1103 and the interface of the terminal jumps to interface 1104 shown in fig. 13. And the terminal receives the operation of the user, namely the second operation.

The second operation may also be used to establish an association of information of the first IoT device with the first user account. Wherein, the information of the first IoT device establishes an association relationship with the first user account, meaning: the second server may push information of the first IoT device to a device associated with the first user account, such as a third server. Illustratively, the second operation may further comprise, as compared to the above: before the user clicks the "buy immediately" control, the user also clicks the "associate purchased device to Hua as an account" control displayed on interface 1101.

Of course, in one specific implementation, before the user clicks the "buy immediately" control, the user does not click the "associate purchased device to" account "control displayed on interface 1101, i.e., the information of the first IoT device does not establish an association with the first user account, meaning: the second server may not push information of the first IoT device to a device associated with the first user account. Then, the present application does not perform S417 and following steps.

S414, in response to the second operation, the terminal requests the second server to generate order details of the first IoT device.

Along with the above example, the terminal receives a user operation (i.e., a second operation), the terminal sends a request to the second server requesting the second server to generate order details for the first IoT device, and sends the order details to the terminal.

S415, the second server generates order details.

S416, the second server sends the order details to the terminal, and the terminal receives the order details correspondingly.

S417, the second server sends a notification message to the third server. Correspondingly, the second server receives the notification message.

The notification message carries information of the first IoT device and a first user account, where the information of the first IoT device may include a first identifier of the first IoT device and a preset first access credential. Of course, the information of the first IoT device may also include a second identification of the first IoT device.

Of course, as described above, if the second server is a three-party server, as shown in fig. 18, S417 may specifically be: the second server sends a notification message to a fourth server, and the fourth server is a server corresponding to the terminal. The fourth server sends a notification message to the third server.

And S418, the third server searches the information of the first IoT device according to the notification message and sends the information of the first IoT device to the terminal. Accordingly, the terminal receives information of the first IoT device.

S418 may be implemented in the following manner:

in the first mode, the third server pushes information of the first IoT device to the terminal according to the first user account. It should be noted that, after the terminal logs in the application by using the first user account, the third server may learn that the terminal logs in the first user account. And the third server pushes the information of the first IoT device to the terminal according to the first user account. The terminal may be understood as all terminals that log into the application using the first user account.

And secondly, the terminal can actively acquire the information of the first IoT device from the third server according to the first user account. Specifically, the terminal sends a first request to the third server, where the first request carries the first user account. The third server receives the first request sent by the terminal. And the third server searches the terminal identification corresponding to the first user account and the information of the first IoT device according to the first request. And the third server sends the information of the first IoT device to the terminal according to the terminal identification. The terminal receives information of the first IoT device sent by the third server.

S419 the terminal stores at least one IoT device information.

That is, a user purchases multiple IoT devices, information of which may all reside on the terminal.

Of course, the terminal establishes an association between the information of the first IOT device and the first user account, and stores the association on the terminal.

Third stage, network distribution stage

Fig. 19 is a flow chart of a network configuration method for an internet of things device according to an embodiment of the present application. As shown in fig. 19:

s420, the first IoT device is powered on.

S421, if the first IoT device determines that the first IoT device is not registered, the first IoT device sends a broadcast. Accordingly, the terminal receives the broadcast sent by the first IoT device.

The broadcast may be referred to as a bluetooth broadcast. The broadcast carries information of the first IoT device, e.g., a first identification of the first IoT device.

In some embodiments, the bluetooth broadcast carries a first identification of the first IoT device for the server or terminal to identify the identity of the first IoT device. Specifically, when the first IoT device is not logged into the third server, a first identification of the first IoT device is sent to the terminal. Subsequently, the terminal matches the pre-stored identification of the IoT device with the first identification.

In some implementations, the bluetooth module of the first IoT device performs bluetooth broadcasting at a preset transmission frequency when transmitting the bluetooth broadcasting, e.g., once every preset T time, and the duration of transmitting the bluetooth broadcasting is X seconds, during which the bluetooth broadcasting information is continuously transmitted. Correspondingly, when the Bluetooth module of the terminal scans signals, the Bluetooth module scans at a preset scanning frequency, the preset terminal scans every y seconds, and the scanning time length is z seconds each time. Wherein the terminal may receive the broadcast whenever the first IoT device initiates the broadcast. The terminal may scan every 600ms, with a scan duration of 100ms, for example.

S422, the terminal scans the broadcast sent by the first IoT device and analyzes the information of the first IoT device in the broadcast.

The information of the first IoT device may include a first identification of the first IoT device. The information of the first IoT device may also include a first access credential of the first IoT device.

S423, the terminal compares the information of the first IoT device with the pre-stored information.

The pre-stored information may refer to information of at least one IoT device stored by the terminal in the second stage.

And S424, after the comparison is successful, the terminal sends network information to the first IoT device according to the first identification.

In one specific implementation, S424 may be implemented as: s425, after the comparison is successful, the terminal sends a communication request to the first IoT device. Accordingly, the first IoT device receives the communication request. The successful comparison may be understood that the information of the first IoT device exists in the pre-stored information. S426, the first IoT device establishes communication connection according to the communication request and sends connection success information to the terminal.

In one specific implementation manner, in order to ensure the security of the transmitted network information, S424 may be specifically implemented as: s427, the terminal encrypts the network information by adopting a first access credential of the first IoT device to obtain a credential cryptogram. The network information may include, among other things, a network name, a password, a verification code, etc. For example, the network name is a WiFi name. The terminal sends the credential cryptogram to the first IoT device. Accordingly, the first IoT device receives the credential cryptogram. S428, the first IoT device decrypts the credential cryptogram using the first access credential to obtain the network information.

S429, the first IoT device performs network connection according to the network information.

In some embodiments, as shown in fig. 19, a network configuration method for an internet of things device provided in the embodiments of the present application may further include:

and S430, the terminal sends a second request to the third server, wherein the request is used for requesting to acquire the information of the third server. Correspondingly, the third server receives a second request sent by the terminal.

The information of the third server may include address information of the third server, second access credentials, and the like.

In another implementation, S430 is performed prior to S426.

And S431, the third server sends the information of the third server to the terminal according to the third request, and correspondingly, the terminal receives the information of the third server.

S432, the terminal sends information of the third server to the first IoT device. Accordingly, the first IoT device receives the information of the third server.

In one implementation, S426 is specifically: and the terminal encrypts the network information and the information of the third server by adopting a first access credential of the first IoT device to obtain a credential cryptogram. S427 specifically comprises: the terminal sends a credential cryptogram to the first IoT device, the credential cryptogram carrying information of the third server. Accordingly, the first IoT device receives the credential cryptogram.

S433, the first IoT device sends a third request to a third server requesting binding of the first user account. Accordingly, the third server receives the third request.

The third request carries information such as the second access certificate and address information of the third server.

And S434, the third server registers the first IoT device with the first user account according to the third request.

S435, the third server sends registration success information to the first IoT device. Accordingly, the first IoT device receives the registration success information.

And S436, the third server pushes the registration success information to the terminal, and correspondingly, the terminal receives the registration success information.

S437, the terminal displays the registration success information.

Illustratively, the information card of the intelligent sound box shown in fig. 10 is displayed on the interface of the terminal, that is, the intelligent sound box is successfully added.

Specific implementation manners of the embodiments of the present application are detailed in the above related matters, and the embodiments of the present application are not repeated.

The various schemes in the embodiments of the present application may be combined on the premise of no contradiction.

The embodiment of the application provides another terminal. The terminal performs any of the methods described above.

The embodiment of the application provides a system which executes any one of the methods.

Embodiments of the present application also provide a computer-readable storage medium comprising instructions that, when run on a computer, cause the computer to perform any of the methods described above.

Embodiments of the present application also provide a computer program product comprising instructions which, when run on a computer, cause the computer to perform any of the methods described above.

The embodiment of the application also provides a chip, which comprises a processor and an interface circuit, wherein the interface circuit is coupled with the processor, the processor is used for running a computer program or instructions to realize the method, and the interface circuit is used for communicating with other modules outside the chip.

In the description of the present application, "/" means "or" unless otherwise indicated, for example, a/B may mean a or B. "and/or" herein is merely an association relationship describing an association object, and means that three relationships may exist, for example, a and/or B may mean: a exists alone, A and B exist together, and B exists alone. Furthermore, "at least one" means one or more, and "a plurality" means two or more. The terms "first," "second," and the like do not limit the number and order of execution, and the terms "first," "second," and the like do not necessarily differ.

In the description of the present application, words such as "exemplary" or "such as" are used to mean serving as an example, instance, or illustration. Any embodiment or design described herein as "exemplary" or "for example" should not be construed as preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "such as" is intended to present related concepts in a concrete fashion.

It will be apparent to those skilled in the art from this description that, for convenience and brevity of description, only the above-described division of the functional modules is illustrated, and in practical application, the above-described functional allocation may be performed by different functional modules according to needs, i.e. the internal structure of the apparatus is divided into different functional modules to perform all or part of the functions described above.

In the several embodiments provided in this application, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical functional division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another apparatus, or some features may be omitted, or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate parts may or may not be physically separate, and the parts displayed as units may be one physical unit or a plurality of physical units, may be located in one place, or may be distributed in a plurality of different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in software functional units.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a readable storage medium. Based on such understanding, the technical solution of the embodiments of the present application may be essentially or a part contributing to the prior art or all or part of the technical solution may be embodied in the form of a software product stored in a storage medium, including several instructions for causing a device (may be a single-chip microcomputer, a chip or the like) or a processor (processor) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read Only Memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely a specific embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions within the technical scope of the present disclosure should be covered in the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A network distribution method for Internet of things equipment is characterized in that,

the terminal storing an identification of the at least one IoT device;

after the terminal stores the identifier of at least one IoT device, the terminal receives a broadcast sent by a first IoT device, wherein the broadcast carries a first identifier of the first IoT device;

the terminal scanning the broadcast sent by the first IoT device;

the terminal obtains the first identification according to the broadcast, wherein the first identification is the identification of the at least one IoT device;

the terminal sends network information to the first IoT device according to the first identifier, and the first IoT device is used for connecting a network according to the network information.

2. The method of claim 1, wherein the terminal stores an identification of at least one IoT device, comprising:

the terminal receives a first operation of the first IoT device displayed on the terminal by a user, the first IoT device being displayed on a first interface of a first application of the terminal;

In response to the first operation, the terminal requests a first server corresponding to the first application to generate order completion information of the first IoT device, the first server is used for sending the order completion information to the terminal, and pushing a notification to a second server of the first IoT device, the notification is used for indicating the second server to push a first identifier of the first IoT device to the terminal;

the terminal receives order completion information of the first IoT device sent by the first server;

the terminal receives a first identification of the first IoT device pushed by the second server;

the terminal stores a first identification of the first IoT device.

3. The method of claim 2, wherein the first interface comprises a first control, the first operation comprising a user operation of the first control, the first operation to authorize the first server to push notifications to the second server.

4. The method of claim 2 or 3, wherein the second server is configured to obtain, from a third server corresponding to the first IoT device, the first identifier based on the notification, the first identifier generated by the third server based on a second identifier of the first IoT device.

5. The method of any of claims 2-4, further comprising, prior to the terminal receiving a first operation by a user of the first IoT device displayed on the terminal:

the terminal receives a second operation of the user on the first application, wherein the second operation is used for indicating the terminal to start the first application;

responding to the second operation, the terminal sends a first request to the first server, wherein the first request carries a first user account, and the first server is used for starting the first application according to the first request and returning login success information to the terminal;

and the terminal receives the login success information.

6. The method of claim 5, wherein the first application is a three-party application, the first user account is a login account of a fourth server corresponding to the terminal, the first server configured to push the first identification of the first IoT device and the first user account to the fourth server after generating order completion information; the fourth server is to push the first identification of the first IoT device and the first user account to the second server.

7. The method of any of claims 1-6, further comprising, after the terminal obtains the first identification from the broadcast, the first identification being an identification of the at least one IoT device:

the terminal sends a second request to the first IoT device according to the first identifier, wherein the second request is used for requesting to establish a communication channel with the first IoT device;

the terminal receives the establishment success information sent by the first IoT device, wherein the establishment success information is generated after the first IoT device establishes the communication channel according to the second request.

8. The method of any of claims 1-7, wherein the terminal further stores a first access credential of the at least one IoT device;

the terminal sending network information to the first IoT device, comprising:

the terminal encrypts network information by adopting a first access credential of the first IoT device to obtain an access ciphertext;

the terminal sends the access ciphertext to the first IoT device, and the first IoT device is configured to decrypt the access ciphertext using the first access credential to obtain the network information.

9. The method of any of claims 2-8, further comprising, prior to the terminal sending network information to the first IoT device according to the first identification:

the terminal sends a third request to the second server, wherein the third request is used for requesting to acquire a second access credential of the second server;

the terminal receives the second access certificate returned by the second server according to the third request;

the method further comprises the steps of:

the terminal sending address information of the second server and the second access credential to the first IoT device; the first IoT device is configured to send a fourth request to the second server, where the fourth request is configured to request registration of the first IoT device, and the fourth request carries the second access credential; the second server registers the first IoT device according to the fourth request, generates registration success information, and feeds back the registration success information to the terminal;

the terminal receives the registration success information pushed by the second server;

the first IoT device is displayed on a second interface of the terminal with successful addition.

10. An Internet of things equipment distribution system is characterized in that,

the terminal is to store an identification of at least one IoT device;

after the terminal stores the identity of at least one IoT device, a first IoT device is configured to send a broadcast, where the broadcast carries a first identity of the first IoT device;

the terminal is used for receiving and scanning the broadcast;

the terminal is configured to obtain the first identifier according to the broadcast, where the first identifier is an identifier of the at least one IoT device;

the terminal is used for sending network information to the first IoT device according to the first identifier;

the first IoT device is configured to connect to a network in accordance with the network information.

11. The system of claim 10, wherein the system further comprises a controller configured to control the controller,

the terminal is further configured to receive a first operation by a user on the first IoT device displayed on the terminal, the first IoT device displayed on a first interface of a first application of the terminal;

the terminal is further configured to request, in response to the first operation, a first server corresponding to the first application to generate order completion information of the first IoT device;

the first server is configured to send the order completion information to the terminal, and push a notification to a second server of the first IoT device, the notification being configured to instruct the second server to push a first identification of the first IoT device to the terminal;

The second server is configured to push a first identification of the first IoT device to the terminal according to the notification;

the terminal is further configured to receive order completion information of the first IoT device sent by the first server;

the terminal is further configured to receive a first identification of the first IoT device pushed by the second server;

the terminal is also to store a first identification of the first IoT device.

12. The system of claim 10, wherein the first interface comprises a first control, the first operation comprising a user operation of the first control, the first operation to authorize the first server to push notifications to the second server.

13. The system according to claim 11 or 12, wherein,

the second server is configured to obtain, according to the notification, a first identifier of the first IoT device from a third server corresponding to the first IoT device, where the first identifier is generated by the third server according to a second identifier of the first IoT device.

14. The system according to any one of claims 11-13, wherein,

the terminal is further used for receiving a second operation of the first application by a user, and the second operation is used for indicating the terminal to start the first application;

The terminal is further used for responding to the second operation and sending a first request to the first server, wherein the first request carries a first user account;

the first server is used for starting the first application according to the first request and returning login success information to the terminal;

the terminal is also used for receiving the login success information.

15. The system of claim 14, wherein the first application is a three-party application, and the first user account is a login account of a fourth server corresponding to the terminal;

the first server is configured to push, to the fourth server, a first identification of the first IoT device and the first user account after generating order completion information;

the fourth server is to push the first identification of the first IoT device and the first user account to the second server.

16. The system of any one of claims 10-15, wherein,

the terminal is further configured to send a second request to the first IoT device according to the first identifier, where the second request is used to request establishment of a communication channel with the first IoT device;

The first IoT device establishes a communication channel with the terminal according to the second request, generates establishment success information, and sends the establishment success information to the terminal;

the terminal is further configured to receive establishment success information sent by the first IoT device, where the establishment success information is generated after the first IoT device establishes the communication channel according to the second request.

17. The system of any of claims 10-16, wherein the terminal further stores a first access credential of the at least one IoT device;

the terminal is further configured to encrypt network information by using a first access credential of the first IoT device, to obtain an access ciphertext;

the terminal is further to send the access ciphertext to the first IoT device;

the first IoT device is configured to decrypt the access ciphertext using the first access credential to obtain the network information.

18. The system of any one of claims 11-17, wherein,

the terminal is further configured to send a third request to the second server, where the third request is used to request to obtain a second access credential of the second server;

The second server obtains the second access certificate of the second server according to the third request and sends the second access certificate to the terminal;

the terminal is further configured to receive the second access credential;

the terminal is further to send address information of the second server and the second access credential to the first IoT device;

the first IoT device is configured to receive the address information and the second access credential, and send a fourth request to the second server, where the fourth request is configured to request registration of the first IoT device, and the fourth request carries the second access credential;

the second server registers the first IoT device according to the fourth request, generates registration success information, and feeds back the registration success information to the terminal;

19. A terminal, comprising: one or more processors; and a memory in which the code is stored; the code, when executed by the terminal, causes the terminal to perform the internet of things device networking method of any of claims 1-9.

20. A chip system for application to an electronic device, the chip system comprising one or more interface circuits and one or more processors; the interface circuit and the processor are interconnected through a circuit; the interface circuit is used for receiving signals from the memory of the electronic device and sending signals to the processor, wherein the signals comprise computer instructions stored in the memory; when the processor executes the computer instructions, the electronic device is caused to perform the internet of things device networking method of any one of claims 1-9.

21. A computer storage medium comprising computer instructions which, when run on an electronic device and a server, cause the electronic device to perform the internet of things device networking method of any of claims 1-9.

22. A computer program product, characterized in that the computer program product, when run on a computer, causes the computer to perform the internet of things device networking method of any of claims 1-9.